|
Hi Simon Thanks for yet another gem. I have been coding CLs for ages and always wondered about messages like this in the job log - the MCH3601 message in particular annoyed me when coding RTV type commands. I was never shown to do this and can't recall seeing it in the manual (is it there ?) As you observed coding MONMSG without the RCVMSG seems to be standard practise so seeing all these messages in my joblogs didn't seem unusual when they were in practically every other job log I ever looked at. I'll be adding this to my standard coding practise from tomorrow. regards Evan Harris Simon Coulter wrote: <SNIP>
You should also remove the MCH3601 message from the joblog. There is no point in cluttering the joblog with unnecessary messages. That is the difference between a good programmer and a merely competent one. You should be coding: CHGVAR VAR(&IPNAME) VALUE(&RIPNAME) MONMSG MSGID(MCH3601) EXEC(DO) RCVMSG MSGTYPE(*EXCP) ENDDO or MONMSG MSGID(MCH3601) EXEC(RCVMSG MSGTYPE(*EXCP)) The same thing is true for all instances where messages are monitored and handled in the program. A classic example is CHKOBJ followed by MONMSG and then a CRTxxx command. Clean up the joblog. A certain automated operations software house should practice this technique.
</SNIP>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.