|
The situation: V5R2. A CL program is doing a CPYF. We anticipated the condition where the destination file becomes full, so we monitored for it with a MONMSG CPF4903. But the DO body of the MONMSG does not run when the error occurs. We can see from the job log that CPF4903 (notify, file full) occurs. Very very shortly afterward, the message somehow gets an I (ignore?). This 'I' evidently comes from the reply specification in the CPF4903 message description, but I'm not sure why it auto-answers instead of behaving normally and executing the DO body of the MONMSG. Anyway, CPA5305 (escape, file full) shows up in the QSYSOPR message queue wanting a response, which is of course fouling things up. The job runs with INQMSGRPY(*RQD). CPF4903 is not in the system reply list. If anyone understands why this MONMSG is failing to act like the previous million MONMSGs I've done, I would really appreciate a hint. TIA.
As an Amazon Associate we earn from qualifying purchases.
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
