SAP Jobs stuck in READY status

book

Article ID: 124959

calendar_today

Updated On:

Products

DSERIES- SERVER CA Workload Automation DE - System Agent (dSeries)

Issue/Introduction

An SAP job when submitted by the DE Manager becomes stuck in READY state. The agent shows active in DE Topology as does the plugin for the SAP instance.

Cause

The agentparm.txt file may not contain all of the necessary details/parameters to allow SAP jobs to process.

Environment

Release:
Component: SYSAGT

Resolution

In this particular instance, the agent had the plugin installed and the DE Manager showed the agent as available. However, the agentparm did not contain the communication alias name for the SAP plugin. After adding the communication.alias_n parameter to agentparm.txt and recycling agent, the SAP job processed as expected.

Reference: https://docops.ca.com/ca-workload-automation-agent-for-sap/11-4/en/installing/install-agent-for-sap/set-up-an-alias-for-the-agent-plug-in