PK57345: NOTIFY= GETS NULLED OUT ON JOB STATEMENT, ISPF PANEL DGOOJOBM NOTIFY=&SYSUID WHEN USED NO JOB0XXXX $HASP165 MESSAGE ISSUED.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• If I submit the job from option 4.
  4. Submit the job stream for background execution
  in panel DGOOJOBM, then yes I do not get the notify.
  from using the ISPF Online Monitor interface.
  .
  The jobcards from panel DGOOJOBM are passed as-is to the ISPF
  EDIT Macro.
  When the jobcard text includes variable names preceded by
  an ampersand (&), they are incorrectly interpreted by the
  dialog manager prior to being passed as a variable name to JES.
  
  
  The ISPF dialog manager replaces the string "NOTIFY=&SYSUID,"
  by "NOTIFY=," because there is no ISPF variable "&SYSUID"
  available.
  

Local fix

• Circumvention:
  On panel DGOOJOBM enter
  "NOTIFY=&&&&SYSUID," instead of "NOTIFY=&SYSUID,".
  Do not enter the double-quote chars.
  Just use 4 "&" before the string "SYSUID" and it should work.
  
  
  Typing just "NOTIFY=&SYSUID," should work too.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 - ISPF Monitoring dialogs                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: The jobcards from panel DGOOJOBM are    *
  *                      passed as-is to the ISPF EDIT Macro.    *
  *                      When the jobcard text includes variable *
  *                      names preceded by an ampersand (&),     *
  *                      they are incorrectly interpreted by the *
  *                      dialog manager prior to being passed    *
  *                      as a variable name to JES.              *
  *                      The ISPF dialog manager replaces the    *
  *                      string "NOTIFY=&SYSUID," by "NOTIFY=,"  *
  *                      because there is no ISPF variable       *
  *                      "&SYSUID" available.                    *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  ****************************************************************
  PROBLEM SUMMARY:
  The jobcards from panel DGOOJOBM are passed as-is to the ISPF
  EDIT Macro. When the jobcard text includes variable names
  preceded by an ampersand (&), they are incorrectly interpreted
  by the dialog manager prior to being passed as a variable name
  to JES. The ISPF dialog manager replaces the string
  "NOTIFY=&SYSUID," by "NOTIFY=," because there is no ISPF
  variable "&SYSUID" available.
  
  PROBLEM CONCLUSION:
  Code corrected: The ampersand character is passed as-is to JES.
  
  KEYWORDS: IRF JOBCARD AMPERSAND &SYSUID
  

Problem conclusion

• Code corrected: The ampersand character is passed as-is to JES.
  
  KEYWORDS: IRF JOBCARD AMPERSAND &SYSUID
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UK31874 UK31875

Modules/Macros

• DGOOJOBU FPEUSCHC
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R310 PSY UK31874

     UP07/12/05 P F712

• R410 PSY UK31875

     UP07/12/05 P F712

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.