RE: ODBC/QZDASOINIT Messages

Frank,

Looks like you are correct.  SQL0204 does look like the message id.  On
our system it is defined with a severity of 30.  This means, generally,
it is sent as an escape message so no *INQ message would exist to be
answered and no MSGW status occurs.

TESTCL will need to be altered to handle the error.  If it is an OPM
model program you can try RCLRSC if an error occurs.

Until then see if the QZDASOINIT job is still active.  If it is then
scan its joblog to see what client is using it.  You should find
something like the following in the job log for message ID CPIAD02.

User userID from client 10.20.15.100 connected to server.

You can then contact the user and find out what is going on.

There is also the intrusive method for getting your resources released -
Bounce QSERVER and all host jobs.  This will more than likely have
adverse effects on your users so you will want to do it at a very quiet
time.  Here are the steps.

1.  Run ENDHOSTSVR SERVER(*ALL) ENDACTCNN(*DATABASE *FILE).
2.  End subsystem QSERVER - ENDSBS SBS(QSERVER).  You may want to use
*IMMED.  That
    is up to you.
2.  If subsystem QUSRWRK is active end the host server jobs running in
it.
    Jobs are QNPSERVS, QZDASOINIT, QZDASSINIT, QZHQSSRV, QZRCSRVS, and
QZSOSIGN.
3.  Restart subsystem QSERVER - STRSBS SBSD(QSERVER).
4.  Restart the host servers STRHOSTSVR SERVER(*ALL) RQDPCL(*ANY).
5.  End the host server pre-start jobs.  They will more than likely be
in subsystem 
    QSERVER.  It depends upon how your system is configured.
    Jobs are QNPSERVS, QZDASOINIT, QZDASSINIT, QZHQSSRV, QZRCSRVS, and
QZSOSIGN.


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


Here's the joblog of the error;
 
  Job name . . . . . . . . . . :   QZDASOINIT      User  . . . . . . :
QUSER        Number . . . . . . . . . . . :   637130      
  Job description  . . . . . . :   QDFTSVR         Library . . . . . :
QGPL                                                      
MSGID      TYPE                    SEV  DATE      TIME             FROM
PGM     LIBRARY     INST     TO PGM      LIBRARY     INST  
                                     Message . . . . :   P54OPRAL in
TESTCL type *FILE not found.                                  
                                     Cause . . . . . :   P54OPRAL in
TESTCL type *FILE was not found. If this is an                
                                       ALTER TABLE statement and the
type is *N, a constraint or partition was not                 
 
So, there's nothing for the MSGID but right b4 it there's a SQL0204 so
I'm thinking that's the msg.  
 
The delivery is *HOLD, if I change that to *INQ will that create a msgw?

 
  
 
 
 
-----Original Message-----
From: gary.monnier@xxxxxxxxxxxxx
To: midrange-l@xxxxxxxxxxxx
Sent: Fri, 2 Mar 2007 12:34 PM
Subject: RE: ODBC/QZDASOINIT Messages


Frank,

Is the message an IBM message or a user defined message?  I cannot tell
from your description.  Also, is it being sent as an *INQ type message?
If not, then the application program where the error occurred will need
to be modified to prevent such hard halts.



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


Hi folks, we're having an issue with an odbc/QZDASOINIT job that caused
some jobs to abend due because the QZDASOINIT never ended properly and
as a result files were open that couldn't be allocated or were in use
when other jobs ran.        
 
In the QZDASOINIT joblog that caused the issue the last entry is
"P54OPRAL in TESTCL type *FILE not found" but the job is not in msgw. Is
that the way it is w/QZDASONIT's?  Is there any way to change them to
msgw or a way to end them in a clp?
 
How do you folks deal w/this situation?    
 
Thanks, Frank 
 
  
________________________________________________________________________
AOL now offers free email to everyone.  Find out more about what's free
from AOL at AOL.com.