HCL Workload Automation resource instance reports fail status or HCL Workload Automation user jobs go in the abend state
Problem: If you run more than three instances of HCL Workload Automation on
the same node with jobs running it is possible to have the following
behavior:
- The HCL Workload Automation cluster resource instance is in fail status.
- HCL Workload Automation user jobs go in the abend or fail state.
- In this case you can find the following error message in <TWS_HOME>\stdlist\date\TWSUSERNAME:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + AWSBIJ139E An internal error has occurred. Jobmon was unable to create a + new desktop on the window station associated with the calling process. + The error occurred in the following source code file: + ../../src/jobmon/monutil.c at line: 2454. The error mess + +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ AWSBIJ140E An internal error has occurred. Jobmon was unable to create the Windows process environment to launch jobs. The error occurred in the following source code file: ../../src/jobmon/monutil.c at line: 830.The following error message is in the <TWS_HOME>\stdlist\logs\date_TWSMERGE.log file,e: 06:00:28 19.05.2006|BATCHMAN:* AWSBHT061E Batchman has received a mailbox record indicating that the following job has terminated unexpectedly: The system has run out of desktop heap.06:00:28 19.05.2006|BATCHMAN:* AWSBHT061E Batchman as received a mailbox record indicating that the following job has terminated unexpectedly: The system has run out of desktop heap.Solution: The solution to this problem has a number of different options, and is described in Resolving desktop heap size problems on workstations with more than three agents