WA ESP dSeries (DE): External job in different scheduler do not complete

book

Article ID: 197292

calendar_today

Updated On:

Products

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

Issue/Introduction

WA dSeries or DE has external scheduler monitor job.  It allows one manager to monitor job(s) on another scheduler/manager.  The two managers must have a common agent between them, i.e. the same agent must be on topology of both the managers.

 

Cause

If the external job is not completing, check the time limit on the external job and the time home application and job started.

The agent will have messages about the external and home job and application.  E.g.

06/06/2020 00:00:19.072+0000 5 TCP/IP Controller Plugin.Receiver pool thread <Regular:2>.CybReceiverSession.accept[:285] - Message accepted: 20200729 02001900+0000 AGENT123 MANAGER1 HOME_JOB_TEST/HOME_APPL_EXAMPLE.1/MAIN EXTSCH WAIT Extscheduler(MANAGER1) Scheduled('20200729 01301893+0000','20200729 02301893+0000') Applid(HOME_APPL_EXAMPLE)

Environment

Release : 12.1

Component : CA WORKLOAD AUTOMATION DE (DSERIES)

Resolution

From the agent logs we can see what are the limits set for the external job.  If the job is not completing then check the scheduled limit fied.

Scheduled('20200606 0130000+0000','202007606 0230000+0000')

The above example shows that external will look for home application that ran between 1:30 and 2:30 of 6 July.  Check the home application start and end times.  Adjust the From and To fields in the external job