Re: ODBC/QZDASOINIT Messages

[fbocch2595@xxxxxxx]

So, just this clp and that's it?  If that's all I'm gonna give it a try.  I 
could run it right b4 our backup.  
Thanks 
 
-----Original Message-----
From: gary.monnier@xxxxxxxxxxxxx
To: midrange-l@xxxxxxxxxxxx
Sent: Fri, 2 Mar 2007 2:23 PM
Subject: RE: ODBC/QZDASOINIT Messages


Frank,

You can also change TESTCL to monitor for messages and resend them to a
message queue of your choice.  Something like this.  Message ID USR9805
could state "ODBC error occurred in job 123456/QUSER/QZDASOINIT.  You
may have to end this job manually."

  CALLPRC A
  MONMSG(CPF000 MCH000 SQL000) EXEC(DO)
  
    RCVMSG MSGTYPE(*DIAG) MSGDTA(&MSGDTA) MSGID(&MSGID) +
           MSGF(&MSGF) MSGFLIB(&MSGFLIB)               
    MONMSG MSGID(CPF0000 MCH0000) EXEC(RETURN)
                                                         
    IF (&MSGID *NE ' ') THEN(DO)                 
    SNDPGMMSG  MSGID(USR9805) MSGF(USERMSGLIB/USERMSGF) +       
               MSGDTA(&JOBNAME) TOUSR(QSYSOPR) MSGTYPE(*INFO)
    MONMSG     MSGID(CPF0000 MCH0000) EXEC(RETURN)
                                                         
                                                         
    RCVMSG  MSGTYPE(*EXCP) MSGDTA(&MSGDTA) MSGID(&MSGID) +
            MSGF(&MSGF) MSGFLIB(&MSGFLIB)               
    MONMSG  MSGID(CPF0000 MCH0000) EXEC(RETURN) 
                                                          
    IF (&MSGID *NE ' ') THEN(DO)                 
    SNDPGMMSG  MSGID(USR9805) MSGF(USERMSGLIB/USERMSGF) +       
               MSGDTA(&JOBNAME) TOUSR(QSYSOPR) MSGTYPE(*INFO)
    MONMSG     MSGID(CPF0000 MCH0000) EXEC(RETURN)

  ENDDO


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Walden H. Leverich
Sent: Friday, March 02, 2007 11:06 AM
To: Midrange Systems Technical Discussion
Subject: RE: ODBC/QZDASOINIT Messages


> I'm hoping that changing the msgq delivery to *BREAK will force the
msgw. 

But as far as the System I is concerned, it's not stalled. So there's no
error to report, hence, no MSGW. You need the PC side to report the hang
to the System I if you want to see it there.

-Walden