Scheduling Job Integrations with HCL Workload Automation
- Job integrations 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.
  - 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.
    - The return code mapping feature
    - Configuring the tracing utility
      Learn how to configure the trace utility for all the access methods.
- Integration with SAP

Mapping return codes for intercepted jobs

About this task

To set up return code mapping for intercepted jobs, after defining the appropriate return code conditions in the r3batch-joblog.rcm file, do the following:

Create a customized template file named rctemplate.jdf in the following directory:
TWA_DATA_DIR/methods/r3batch_icp/
```
TWA_home\methods\r3batch_icp\
```
The file must contain the following:
```
alias;rccondsucc "Success Condition"
```
where, the "Success Condition" must match a condition saved in the rcm file.
Modify the XANAME_r3batch.icp file, located in the same path, to refer to the jdf file you created in the previous step as follows:
```
client job_mask user_mask rctemplate
```
HCL Workload Automation manages the intercepted R/3 job as a docommand job with all the options specified in the customized jdf file. You can check if your intercepted job is correctly submitted by reading the job_interceptor joblog.