In our development LPAR I am having a problem where my job "Notify" no longer seems to work. That is, when I submit a job with NOTIFY=&SYSUID on the JOB card. When the job ends I no longer receive a message like: 09.07.37 JOB02829 $HASP165 FJSBR14 ENDED AT ZOS MAXCC=0 CN(INTERNAL)
No one else appears to be having this issue, and in fact on our production LPAR I also do not have this issue. Our ISPF profiles are not shared between PROD and DEV (argh!) so I'm thinking I must have changed something somewhere to cause this. Systems has not been able to determine what the issues is, and they have better things to do anyway. Any thoughts on what the cause might be? Oh, I forgot to note, once I log off and log back on I receive all of the notify messages that are queued up for me! Frank -- Frank Swarbrick Applications Architect - Mainframe Applications Development FirstBank Data Corporation Lakewood, CO USA P: 303-235-1403 F: 303-235-2075 >>> The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
