RE: Solution : RE: GO SAVE 21 and V5R3

This used to drive our operators crazy.  I don't remember where I got
this bit of code, but it displays the messages in the message queue on
line 27 so they could see that the backup was progressing...

LIN27MON:   PGM        PARM(&MSGQ &MSGQLIB &MSGKEY)                   
            DCL        VAR(&MSGQ) TYPE(*CHAR) LEN(10)                 
            DCL        VAR(&MSGQLIB) TYPE(*CHAR) LEN(10)              
            DCL        VAR(&MSGKEY) TYPE(*CHAR) LEN(4)                
            DCL        VAR(&MSGDTA) TYPE(*CHAR) LEN(132)              
                                                                      
            RCVMSG     MSGQ(&MSGQLIB/&MSGQ) MSGKEY(&MSGKEY) +         
                         RMV(*NO) MSG(&MSGDTA)                        
            SNDPGMMSG  MSGID(CPF9897) MSGF(QCPFMSG) MSGDTA(&MSGDTA) + 
                         TOPGMQ(*EXT) MSGTYPE(*STATUS)                
                                                                      
END:        ENDPGM              

Then just add CHGMSGQ MSGQ(QSYSOPR) DLVRY(*BREAK) SEV(xx)
PGM(*LIBL/LIN27MON) and/or CHGMSGQ MSGQ(*USRPRF) DLVRY(*BREAK) SEV(xx)
PGM(*LIBL/LIN27MON)at the beginning of your backup CL.

Regards,
 
Scott Ingvaldson
iSeries System Administrator
GuideOne Insurance Group                                      

-----Original Message-----
date: Thu, 10 Feb 2005 15:18:03 +0100
from: "MITTELHEISSER Jean Claude" <mitteljc@xxxxxxx>
subject: Solution : RE: GO SAVE 21 and V5R3

<Snip>

What's a little bit frightening is that console is not available while
saving. 

</Snip>