Some Microfocus jobs complete on MF server successfully, but Workload Automation didn't get status update.
search cancel

Some Microfocus jobs complete on MF server successfully, but Workload Automation didn't get status update.

book

Article ID: 4030

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent

Issue/Introduction

Some Microfocus jobs complete on MF server successfully, but Workload Automation didn't get status update. So, Microfocus job stays in READY.

Environment

Microfocus server version 6.0 SP3

Cause

One possible cause is relating to Microfocus server regions.

Resolution

In the MF server regions affected, comment out the ES_EMP_EXIT_1=event_manager variable.

The ES_EMP_EXIT_n variables should have been set in the Es-Environment and not at the Micro Focus Directory Server (mfds) level. When a region is started from the command line the region processes are spawned from a copy of the users shell and not mfds. So all environment variables that otherwise would usually be set for mfds will need to be set in the users profile. This allows MicroFocus to control the use of Event Managers at the region level and not globally. Setting the variable in the mfds environment also might cause problems if one were to want to disable the Event Manager for a particular region.