Jobtrac Job Management r11.0 receives TRAC845E message

Products

• Jobtrac

Issue/Introduction

Jobtrac is unable to obtain the GSS Node name during initialization and receives message TRAC845E.

 

Environment

Jobtrac 11.0

GSS

 

Cause

If Jobtrac is unable to obtain the GSS Node Name  during initialization, the  GSS subtask will issue error message TRAC845E and terminate. 

Resolution

 Explanations of the return codes and reason codes associated with the TRAC845E error message are contained in the Jobtrac Message Guide under TRAC822I.  If the TRAC845E return code and reason     code indicate that the IMOD cannot be found, use the following information to determine and resolve the problem:     

1.  Ensure  the correct GSS subsystem being used                                                                                           

     GSS  allocates a sysout file called ISRVLOG.  Select this file from SYSVIEW/E or SDSF and search for the keyword SSNAME (the
     subsystem name specified in the RUNPARMS member of the GSS   PARMLIB.  Ensure this matches the ISERVE Subsystem name in the
     Jobtrac Global Options (SYS OPTS ; 1) .  The ISERVE Subsystem name is ISRV by default, but it can be changed.

     Example in the Jobtrac Global Options

     ISERVE Subsystem Name      => ISRV   ISERVE STC Procedure Name  => GSSA                     
                                                                   

2.  Confirm  Jobtrac ISET library being processed  

 
    In the ISRVLOG, search for the keyword ISET.  This keyword defines the IMOD libraries available to GSS at startup.   
    This is a VSAM file and is loaded in the second STAGE2 job.  It should be defined in the RUNPARMS member of the GSS PARMLIB 
    example as follows:

     ISET JOBTRAC_PROD DSN Jobtrac.iset.dataset.name load -
       write DESC /JOBTRAC Release 11.0 PROD / SSID ISRV                                                    
                                                                       

3.  Verify the IMOD loaded when GSS started                                              

    Examine the file ISRVLOG written by GSS.  Search for the IMOD named in the TRAC845E message.  Look for a 
    SRV168 message indicating the IMOD was loaded.  If  not found, access the ISERVE editor (the Jobtrac ISERVE
    command, or TSO SRVEDIT), and verify the status of the $JOBT IMODS.  The first two characters under the
    STATUS column should be C(ompiled) & P(roduction).  If this is not the case, use the 'G' line command to compile 
    and load the IMOD.                                                    
                                                               

4.  Verify that one of the GSS started tasks that is running executes the GSSMAIN program 

   One of the GSS started task on the LPAR must be executing GSSMAIN.  Other GSS started task may run executing SRVSYS.