Error: TRACWARN - GJTRUJV2 UNABLE TO LOCATE JCT after z/OS or JES2 upgrade
search cancel

Error: TRACWARN - GJTRUJV2 UNABLE TO LOCATE JCT after z/OS or JES2 upgrade

book

Article ID: 20534

calendar_today

Updated On:

Products

Jobtrac

Issue/Introduction

Following an upgrade for the  z/ OS operating system or  JES2 may result in message TRACWARN - GJTRUJV2 UNABLE TO LOCATE JCT.  This results in AUTO-SCHD jobs remaining held in the JES2 input queue and AUTO-SCHD feature not functioning properly.     



Environment

Jobtrac r11.0    z/OS 3.1, 2.5, or 2.4

Cause

 

  • The following warning messages are observed in the Jobtrac log: TRACWARN - GJTRUJV2 UNABLE TO LOCATE JCT, Reason=A $H J#### /* CA-JOBTRAC AUTO-HOLD */
  • AUTO-SCHD jobs remain held in the JES2 input queue.                                                                                                                                                                                                                                                                                                                                                                                                                                                         

Upgrading the operating system or JES2 changes the mapping of JES2 control blocks. If the Jobtrac usermod UM00001 is not reassembled against the current z/OS MACLIB, the GJTRUJV2 module cannot correctly locate the Job Control Table (JCT).

 

Resolution

To resolve this issue, reassemble the GJTRJES exit by re-applying the usermod.

  1. Verify that PTF RO73335 is applied to your Jobtrac environment to prevent potential S0C4 abends.
  2. Use the SAMPJCL member HD11JES2 as a model to re-apply usermod UM00001.
  3. Ensure the job points to the correct z/OS 3.1 MACLIB libraries.
  4. Perform a Library Lookaside (LLA) refresh: F LLA,REFRESH
  5. Recycle Jobtrac using the BACK parameter to back out the old internals and reload the IEFUJV exit: F jobtrac,PARM=BACK S jobtrac

Note: This procedure must be performed on each system in the complex where the upgrade occurred.

 

 

Additional Information

For additional information see How to re-APPLY Usermod UM00001