Re: ODBC/QZDASOINIT Messages

Hi Elvis, but when an sql is completed it should not keep files open.   
 
Here's info on WINSQL, 
 
http://www.synametrics.com/SynametricsWebApp/WinSQL.jsp 
 
I think it's time to start running traces and send them to IBM. 
 
Frank
 
 
-----Original Message-----
From: ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx
To: midrange-l@xxxxxxxxxxxx
Sent: Fri, 9 Mar 2007 4:30 PM
Subject: RE: ODBC/QZDASOINIT Messages


Well... I don't know what WINSQL is, but is it possible it caches the result
set if you run the same exact SQL statement twice, and doesn't even hit the
iSeries 2nd time around?

Celebrating 10-Years of SQL Performance Excellence


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of fbocch2595@xxxxxxx
Sent: Friday, March 09, 2007 1:44 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: ODBC/QZDASOINIT Messages


No, the same job but no open files.  It's the only odbc job running on the
iSeries.  
 
 
 
-----Original Message-----
From: ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx
To: midrange-l@xxxxxxxxxxxx
Sent: Fri, 9 Mar 2007 2:24 PM
Subject: RE: ODBC/QZDASOINIT Messages


You got a different ODBC job 2nd time around?

Celebrating 10-Years of SQL Performance Excellence


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of fbocch2595@xxxxxxx
Sent: Friday, March 09, 2007 12:57 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: ODBC/QZDASOINIT Messages


Another question on these jobs.  
 
When I run the select statement (using winsql) and I get the results on my
screen I wrkjob qzdasoinit and I see open files (via option 14 from wrkjob).
Then, when I run the very same select statement again I don't see any open
files.  I'm waiting for IBM to get back to me on this but does anyone know
why the job would display files then when the same statement is run again,
no open files? 
 
Thanks, Frank 
 
 
-----Original Message-----
From: gary.monnier@xxxxxxxxxxxxx
To: midrange-l@xxxxxxxxxxxx
Sent: Fri, 2 Mar 2007 3:16 PM
Subject: RE: ODBC/QZDASOINIT Messages


Frank,

I can't say my example will satisfy what you want to do.  Maybe you want to
make your version of USR9805 be an inquiry message.  It depends upon what
you want to do.  If all you want to do is force a message to be answered you
can use the following.


 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)                 
      SNDUSRMSG  MSGID(USR9805) MSGF(USERMSGLIB/USERMSGF) +       
                 VALUES(C) DFT(C)                         + 
                 MSGDTA(&JOBNAME) MSGTYPE(*INQ) TOUSR(*QSYSOPR) 
      MONMSG     MSGID(CPF0000 MCH0000) EXEC(RETURN)
      RETURN
    ENDDO
                                                         
                                                         
    RCVMSG  MSGTYPE(*EXCP) MSGDTA(&MSGDTA) MSGID(&MSGID) +
            MSGF(&MSGF) MSGFLIB(&MSGFLIB)               
    MONMSG  MSGID(CPF0000 MCH0000) EXEC(RETURN) 
                                                          
    IF (&MSGID *NE ' ') THEN(DO)                 
      SNDUSRMSG  MSGID(USR9805) MSGF(USERMSGLIB/USERMSGF) +       
                 VALUES(C) DFT(C)                         + 
                 MSGDTA(&JOBNAME) MSGTYPE(*INQ) TOUSR(*QSYSOPR) 
      MONMSG     MSGID(CPF0000 MCH0000) EXEC(RETURN)
      RETURN
    ENDDO

    RETURN
 ENDDO


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of fbocch2595@xxxxxxx
Sent: Friday, March 02, 2007 12:02 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: ODBC/QZDASOINIT Messages


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