Scheduling

The Job Management Administration panel of Solution Manager has two entry points for scheduling jobs:
  • The Schedule Jobs item in Common Tasks, a direct way of scheduling, where you pick the job from the HCL Workload Automation database and you set the scheduling options and time definitions.
  • The Job Documentation object, where you can create and edit job documentation, schedule, monitor, and manage jobs.

The jobs scheduled from Solution Manager on HCL Workload Automation must have been previously defined in the HCL Workload Automation database.

A job scheduled from the Schedule Jobs or Job Documentation panels in Solution Manager to be run by HCL Workload Automation, is automatically mapped in a job stream that is expressly created to include the job. The job stream is (automatically) defined in the HCL Workload Automation database with a specific prefix defined in the smseadapter.properties file.

Best practice for job security and stability

To ensure system stability and prevent known security conflicts, set the streamlogon user to match the agent installation owner (wauser) or root when submitting SAP jobs on the extended agent.

By aligning the streamlogon user with the owner of the TWSDATA directory, you avoid the permissions problem that occurs when the job attempts to write necessary diagnostic files.

If environmental constraints require using a streamlogon user that differs from the agent installation owner, the job successfully initializes but is expected to fail with ABEND (Return Code 139) upon execution.

This failure occurs because the non-default streamlogon user lacks the required write permissions to create and access essential log and trace files used by the r3batch method.

Required manual workaround

To resolve the RC=139 error and allow the SAP job to complete, the administrator must manually adjust the file system permissions on the agent host before running the job. The administrator must grant full write access (chmod 777) to the streamlogon user for the following locations:

  1. The stdlist folder within the DATA_DIR.
  2. The trace-r3batch.log file located in the TWA_DATA_DIR/methods/trace/ directory.