Re: RTV???? command question

[Neil Palmer <neilp@xxxxxxxxxxx>]

Yes - despite my sarcasm in the previous note, it was an excellent tip.
One that IBM themselves would do well to always follow, especially for
that huge disgusting mess that gets written to your joblog when a job
executes their STRHOSTSVR command !  ;-)

...Neil





Evan Harris <spanner@ihug.co.nz>


        To:     midrange-l@midrange.com
        cc:
        Subject:        Re: RTV???? command question


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>