Re: Another V6.1 issue: CPF3837

Robert Ostrowski wrote:

Since upgrading to V6.1, in our overnight save we keep
encountering CPF3837 in testing the backup. I added a MONMSG
MSG(CPF3837) for it, but it still comes up. Do I need to do more
than just add the MONMSG? I would love to avoid getting up at
2:00 AM to type "I" to ignore the message every night!!

AFaIK the message CPF3837 is issued as a /completion/ message and sent to the history log [QHST]; i.e. it is not an /escape/ message which could be monitored. Review the command help text for messages that can be monitored. The spooled joblog would show which message resulted in the inquiry being sent.

What is "the message" which is being ignored by the "I" reply? Certainly not the CPF3837.? And did the MONMSG really not function? Perhaps there was an error in moving the changed program into production; i.e. if the message CPF3837 was properly monitored as alluded, then "it" should no longer impact the save unless "it" refers instead to the default handler for the application program doing the save, and there is just some other message effecting that inquiry.? A MONMSG without any specific EXEC() for recovery, would just ignore the condition which caused a failure, and that should be effectively the same effect as having replied "I"=Ignore. Also FWiW, the job could define its inquiry message reply handling [INQMSGRPY] to effect a default reply of "I" for whatever message, to avoid manually replying; e.g. if one were assured they would always just reply with "I" anyhow.

Regards, Chuck