Scheduling Applications with HCL Workload Automation
- Overview
  Learn about plug-ins and access methods and how you can use them to extend HCL Workload Automation scheduling capabilities to external applications and systems.
- Job plug-ins to extend workload scheduling capabilities
- Access methods
  - Installing and configuring the access methods
    The access methods documented in this guide are packaged with HCL Workload Automation and are automatically installed with the product on dynamic and fault-tolerant agents.
  - Access method for PeopleSoft
    What you need and what you can do with Access method for PeopleSoft.
  - Access method for z/OS
    What you need to know and to do before using the Access method for z/OS.
  - Common serviceability for the access methods
    This section provides information common to all the access methods including return code mapping, configuring the tracing utility, and troubleshooting the access method.
- Integration with SAP

Diagnostic information

z/OS jobs submitted by HCL Workload Automation can fail to complete for a number of reasons. The step in the submission process in which a job fails determines how much information is available and is provided by HCL Workload Automation as follows:

If a job fails before it is actually initiated (usually the result of a JCL or security problem), HCL Workload Automation recognizes that it no longer exists, and marks it as abend in the conman command line displays. No further information is provided.
If a job fails after being started, HCL Workload Automation:
1. Obtains its condition code and user abend code, if any
2. Writes them to the job standard list file
3. Marks the job as abend in the conman command line or Dynamic Workload Console displays
Job standard lists can be displayed with the conman command line and with the Dynamic Workload Console.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.