Re: SAVSYS & Break Messages - V5R4

[CRPence <crpbottle@xxxxxxxxx>]

Cyndi Bradberry wrote:
> <<SNIP>> Message queue delivery . . . .   *NOTIFY  <<SNIP>>
>
> And yet, the system sat and waited at a break message, CPF3777 to
> let us know that there were 2 libraries partially saved !  I
> discovered this Sunday morning when I tried to VPN into my system
> and TCP was not running. I ended up making a trip to town to
> answer the message and allow the system to complete the save.
> <<SNIP>>

  The delivery choices of *BREAK & *NOTIFY are effectively 
unrelated to an inquiry message; i.e. presumably they refer to how 
the *SYSOPR message queue should be changed with CHGMSGQ QSYSOPR 
DLVRY().  The mention of having "to answer the message" implies the 
message was an inquiry, not a break message.  CPF3777 is not an 
inquiry message.

  If the inquiry was CPA0701 for the condition CPF3777, then change 
the CLP to monitor for the CPF3777, if that error should not stop 
the save; i.e. CPA0701 T/*EXT is issued in the job to indicate that 
the CLP encountered an *unmonitored* exception, and the inquiry is 
being sent to request how to proceed.  A change to the CLP to 
monitor for the error condition prevents the inquiry; the EXEC() of 
the MONMSG CPF37777 can be empty to ignore that error condition.

Regards, Chuck