Re: Weird Message During System Save

Yeah, been there, done that. Had a similar problem with OptiConnected LPARs in a previous life. Rather than change the entire message queue not to break, we added code into our custom save code to temporarily change the severity of specific messages to Zero during the save, and then put them back when we are done. This way we don't accidentally miss a message we may really need to see.

0029.00 /* GET READY */
0030.00 CHGMSGD MSGID(CPI8009) MSGF(QSYS/QCPFMSG) SEV(0)
0031.00 CHGMSGD MSGID(CPF2753) MSGF(QSYS/QCPFMSG) SEV(0)
0032.00 CHGMSGD MSGID(CPI5906) MSGF(QSYS/QCPFMSG) SEV(0)
0033.00 CHGMSGD MSGID(CPF9E72) MSGF(QSYS/QCPFMSG) SEV(0)
0034.00 /* CHANGE THE MESSAGE SEVERITY TO ZERO SO IT DOESN'T BREAK

0076.00 /* PUT THINGS BACK THE WAY THEY BELONG */
0077.00 CHGMSGD MSGID(CPI8009) MSGF(QSYS/QCPFMSG) SEV(70)
0078.00 CHGMSGD MSGID(CPF2753) MSGF(QSYS/QCPFMSG) SEV(30)
0079.00 CHGMSGD MSGID(CPI5906) MSGF(QSYS/QCPFMSG) SEV(70)
0080.00 CHGMSGD MSGID(CPF9E72) MSGF(QSYS/QCPFMSG) SEV(40)
0081.00 /* CHANGE THE MESSAGE SEVERITY TO BACK TO WHERE IT BELONGS

Brian Dolinar.
<sodonnell@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:mailman.1067.1232203639.21608.midrange-l@xxxxxxxxxxxxxxx

I had a very weird (to me) message pop up during my GO Save (Option 21) last night.

The message was "APPN Not Replying... "(MSGID CPA58E0) and then it had a controller description
name which we use to connect to a mainframe.

This was during a system save so the system was in a restricted state (the SYSTEM IN RESTRICTED
state message (forget the exact text on that but it's the restricted message you'd normally see
when you do a ENDSBS(*ALL)) and to my knowledge, nothing else was running.

The backup did not complete. In fact, the back never even started because between the time we hit
the enter key after filling in the parms on the Go Save option 21 screen and the time that message
popped up was almost an hour and a half so we'd already left by that time as we thought it the
bakckup was running.

Did not discover this message waiting then until we came back in this morning.

My question then (finally) is...what would cause an APPN controller to do anything when the system
is in a restricted state like this and what can I do to prevent it tonight when I attempt the full
system save again?



Shannon O'Donnell