IJ35108: WORKLOAD SCHEDULER NOT TRAPPING SUCCESSFUL CONDITION

APAR status

• Closed as program error.

Error description

• Executable job not trapping successful output condition to set a
  job to successful based on a string within the jobs output.
  When the job runs the successful output condition that customer
  has defined is not trapped when it occurs in the jobs output as
  per the screen(sent to Cudar). No error is returned.
  
  Steps performed:
  Under Workload Designer> Create New Job Definition of type Unix
  Fill the other values and also under "Successful Output
  Conditions" section, entered the Condition Name as "Dummy" and
  Condition Value as "contains(${this.stdlist},"error")".
  
  Job 0AAAAAAAAAAAAI5P - 108001164 - Failed RC=100 at 14/04/2021
  08:05:38
  This one had in the output:
  ---> 08:05:32 JCLCM0191I STEP ENDED     STEP010.ORB0010 - COND
  CODE 0100
  
  So should have been set to OK as per its successful output
  condition rule (ENDED-OK2):
  = TWSRCMAP  : {"SUCCOC":[{"value":"$RC<=4","key":"ENDED-OK"},{"
  value":"contains(${this.stdlist},\"STEP010.ORB0010- COND CODE 01
  
  This was not trapped:
  = Status Message:  AWSITA030E The job failed.
  = Exit Status           : 100
  = Successful Output Conditions:
  =   ENDED-OK : false
  =   ENDED-OK2 : false
  

Local fix

• NA
  

Problem summary

•  se apar description
  

Problem conclusion

•  apar fixed into 9.5 FP6
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TIV WKLD SCHDL

• Fixed component ID

  5698WKB95

Applicable component levels