Re: CPYSPLF - but don't know the spooled file number

[CRPence <CRPbottle@xxxxxxxxx>]

  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>>