QZRCSRVS doesn’t go into MSGW

380 pts.
Tags:
AS/400
iSeries
MSGW
In AS/400, QZRCSRVS doesn't go into MSGW. What can I do?
1

Answer Wiki

Thanks. We'll let you know when a new response is added.

I don’t know how it lost my question details, I am posting question details here….

I have WAS connection to iSeries to call COBOL/RPG program. It connects to QZRCSRVS, but if my program has any error (ex: calling program not found), it doesn’t go into MSGW, instead it shows message in log and stays in “TIMW” status. Also when it hits error Commitment control already active while doing STRCMTCTL, the message is cancelled with Default reply answer (I have *RQD for Inquiry message reply).

Can anyone let me know what should I change more to keep job in MSGW in above scenarios?

Here is my Job Log and Attribues and JobD

Client request – run program QSYS/QWCRTVCA.                          
Client request – run program XXXXXXXX/GCW9000.                      
Cannot resolve to object GCW9119A. Type and Subtype X’0201′ Authority
  X’0000′.                                    

    Commitment control already active.                             
    CPF8351 received by procedure GCW900C. (C D I R)               
  ? C                                                              
    Library RBTSYSLIB added to library list.                       
    Ownership of object HSCURLIB in QTEMP type *DTAQ changed.      
    Library RBTSYSLIB removed from library list.                   
    Library RBTSYSLIB added to library list.                       
    Library RBTSYSLIB removed from library list.                   
    Application error.  CPF8351 unmonitored by GCW900C at statement
      0000002000, instruction X’0000′.                             
Function check. CEE9901 unmonitored by GCW9000 at statement 0000000247,
  instruction X’0000′.                                                
Message ‘CEE9901’ in called program ‘GCW900C’ (C D F G).  

                       Display Job Definition Attributes                        
                                                             
 Job:   QZRCSRVS       User:   QUSER          Number:   940013                 
                                                                               
 Job description . . . . . . . . . . . . . . . . . :   QZBSJOBD                
   Library . . . . . . . . . . . . . . . . . . . . :     QSYS                  
   ASP device  . . . . . . . . . . . . . . . . . . :     *SYSBAS               
 Job queue . . . . . . . . . . . . . . . . . . . . :                           
   Library . . . . . . . . . . . . . . . . . . . . :                           
   ASP device  . . . . . . . . . . . . . . . . . . :                           
 Job priority (on job queue) . . . . . . . . . . . :   5                       
 Output priority (on output queue) . . . . . . . . :   5                       
 End severity  . . . . . . . . . . . . . . . . . . :   30                      
 Message logging:                                                              
   Level . . . . . . . . . . . . . . . . . . . . . :   4                       
   Severity  . . . . . . . . . . . . . . . . . . . :   0                       
   Text  . . . . . . . . . . . . . . . . . . . . . :   *NOLIST                 
 Log CL program commands . . . . . . . . . . . . . :   *NO                     
 Job log output  . . . . . . . . . . . . . . . . . :   *PND                    

 Printer device  . . . . . . . . . . . . . . . . . :   PRT01            
 Default output queue  . . . . . . . . . . . . . . :   *DEV             
   Library . . . . . . . . . . . . . . . . . . . . :                    
 Job date  . . . . . . . . . . . . . . . . . . . . :   2016/01/29       
 Date format . . . . . . . . . . . . . . . . . . . :   *YMD             
 Date separator  . . . . . . . . . . . . . . . . . :   /                
 Time separator  . . . . . . . . . . . . . . . . . :   :                
 Job time:                                                              
   Current date  . . . . . . . . . . . . . . . . . :   2016/01/29       
   Current time  . . . . . . . . . . . . . . . . . :   16:30:38         
 Day of week . . . . . . . . . . . . . . . . . . . :   *FRI             

                            Display Job Description                            
                                                             
 Job description:   QZBSJOBD       Library:   QSYS2924                        
                                                                              
 User profile . . . . . . . . . . . . . . . . . . :   *RQD                    
 CL syntax check  . . . . . . . . . . . . . . . . :   *NOCHK                  
 Hold on job queue  . . . . . . . . . . . . . . . :   *NO                     
 End severity . . . . . . . . . . . . . . . . . . :   30                      
 Job date . . . . . . . . . . . . . . . . . . . . :   *SYSVAL                 
 Job switches . . . . . . . . . . . . . . . . . . :   00000000                
 Inquiry message reply  . . . . . . . . . . . . . :   *RQD                    
 Job priority (on job queue)  . . . . . . . . . . :   5                       
 Job queue  . . . . . . . . . . . . . . . . . . . :   QBATCH                  
   Library  . . . . . . . . . . . . . . . . . . . :     QGPL                  
 Output priority (on output queue)  . . . . . . . :   5                       
 Printer device . . . . . . . . . . . . . . . . . :   *USRPRF                 
 Output queue . . . . . . . . . . . . . . . . . . :   *USRPRF                 
   Library  . . . . . . . . . . . . . . . . . . . :                           

 Message logging:                                                  
   Level  . . . . . . . . . . . . . . . . . . . . :   4            
   Severity . . . . . . . . . . . . . . . . . . . :   0            
   Text . . . . . . . . . . . . . . . . . . . . . :   *NOLIST      
 Log CL program commands  . . . . . . . . . . . . :   *NO          
 Job log output . . . . . . . . . . . . . . . . . :   *PND         
 Accounting code  . . . . . . . . . . . . . . . . :   *USRPRF      
 Print text . . . . . . . . . . . . . . . . . . . :   *SYSVAL      
                                                                   
 Routing data . . . . . . . . . . . . . . . . . . :   QCMDI        
                                                                   
 Request data . . . . . . . . . . . . . . . . . . :   *NONE        

Discuss This Question: 3  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • TheRealRaven
    QZRCSRVS is a server job instance and should not go into MSGW status. The server should not be stopped to wait for someone to respond to a message. The proper direction to go is to fix the process to handle the messages.

    Is there a reason that cannot be done?
    35,630 pointsBadges:
    report
  • sim400
    We nee to alert Production support team as soon as process failed on iSeris, this is done based on MSGW status of Job. So if QZRCSRVS goes into MSGW, tool can alert support person.
    380 pointsBadges:
    report
  • TheRealRaven
    The server job has built in handling of errors, and it could make significant trouble to try to change that. If you run this command:
    DSPLOG PERIOD((*AVAIL 012616)) JOB(QZRCSRVS) MSGID(CPF1124)
    How many instances show in the history log? Today is Monday, Feb. 1st, so the command checks back to Friday, Jan. 26th. If there are too many to review, try changing the date to (013116) to check only back to Sunday.

    An exact count isn't needed, but a close approximation will let us know what impact might come from some kinds of changes.

    35,630 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: