A job which is bound to a JBS agent following ThruPut Manager Analysis is put on hold despite the fact the required agent is ACTIVE on the required system: DTM1459I 2023.134 00:10:18 NO VTS MOUNTS Job JOBNAME Managed by Control Center 'WLMSC' Type 'TMBI3MED' - Held The output of the $DJOB12345,LONG command shows that the SYSAFF has been removed from the job and that the job has a SYSAFF for a different system. In the scenario below, the job is in JBS hold because there is a bind to an agent named SYS2 which is not active on system: SYS1, which is the only system where the job is eligible for selection. $HASP890 JOB(JOBNAME) $HASP890 JOB(JOBNAME) STATUS=(AWAITING EXECUTION),CLASS=1, $HASP890 PRIORITY=10,HOLD=(RESOURCE), $HASP890 CMDAUTH=(LOCAL),OFFS=(),SECLABEL=, $HASP890 USERID=TSOID,SPOOL=(VOLUMES=(JES001), $HASP890 TGS=1,PERCENT=0.0001),ARM_ELEMENT=NO, $HASP890 CARDS=54,DUBIOUS=NO,PRIVILEGE=NO,DJC=NO, $HASP890 REBUILD=NO,SRVCLASS=TMSLMBI3,SCHENV=, $HASP890 SCHENV_AFF=(ANY),DUPL_EXEMPT=NO,CC=(), $HASP890 DELAY=(SYSAFF), $HASP890 CRTIME=(2023.134,07:10:17),JOBGROUP=, $HASP890 BERTNUM=3,JOENUM=0,JOEBERTS=0 DTM0220I Job Display JOB12345 JOBNAME Awaiting Execution For more than 1 day Class : 1 (General_Services) Priority: 10 Sysaff : SYS1 TM-HOLD Managed: SLM JBS HOLD JCS At 13:00:23, job was not selected because it is held by ThruPut Manager DTM6420I JBS BINDING DISPLAY JOB12345 JOBNAME HELD BY JBS SYS=SYS1 BINDS TO - SYS2 |
Make sure that the CONTROLO started task is active on all members of the JESplex (MAS). |