• Subject: Re: Error CPA3311 when using CPYSPLF
  • From: "Simon Coulter" <shc@xxxxxxxxxxxxxxxxx>
  • Date: Tue, 21 Nov 00 23:40:33 +1100


Hello Albert and Richard,

Richard wrote:
>Assuming that the program that uses the CPYSPLF is a
>CLP, you could insert a MONMSG CPA3311 immediately
>after the CPYSPLF.  If message CPA3311 is encountered
>the program will then continue.

It's an inquiry message (hence CPA for Action) and as such cannot be monitored. 
 You can 
only monitor exception messages (i.e., *ESCAPE, *NOTIFY, and *STATUS messages).

Albert wrote:
> Is there any way to prevent this message from coming
> up? If not is there any
> way to automatically respond with 'G'? I don't want
> to add the message to
> the system reply list. I only want it to default to
> 'G' in my job.

Just adding the message to the SysRpyL won't make it affect every job.  You 
have to 
change the job using CHGJOB INQMSGRPY(*SYSRPYL).

Regards,
Simon Coulter.


 FlyByNight Software         AS/400 Technical Specialists       
 Eclipse the competition - run your business on an IBM AS/400.  
                                                                
 Phone: +61 3 9419 0175      Mobile: +61 0411 091 400           
 Fax:   +61 3 9419 0175      mailto: shc@flybynight.com.au      
                                                                
 Windoze should not be open at Warp speed.                      

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].