×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
The RCVMSG immediately after SBMJOB should probably be coded to
receive message type *LAST, if the request did not fail, to best ensure
receiving the completion message. That is how I have always coded it,
and it has never failed me. Or all prior messages in that program
message queue need to be deleted, before the SBMJOB is issued. That is
because the order of messages coming off of the *PGMQ [program message
queue] for a *COMP [completion message type; in fact for non-exception
messages, per MSGTYPE(*EXCP) doc] is FIFO instead of LIFO. That would
explain why the RCVMSG would be getting a diagnostic "from up above in"
the CLP.
http://groups.google.com/group/comp.sys.ibm.as400.misc/browse_thread/thread/a29b73945c9f6cbe/77b127d42d078244?hl=en&lnk=st&q=rcvmsg+msgtype+cpc1221+group%3Acomp.sys.ibm.as400.misc#77b127d42d078244
Regards, Chuck
Don Cavaiani wrote:
No, if fact it is a message ID from up above in my CLP where a file
would be created, but it already exists (this happens BEFORE the RPGLE
print program is submitted). So, how do I get it to reflect the
"submitted job" parameters?
<<SNIP>>
"Crispin Bates" wrote:
Is the value of &MID = 'CPC1221' ?
<<SNIP>>
This mailing list archive is Copyright 1997-2024 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.
midrange.com
