Cross-platform dependency, using the correct machine xtype definition.

Products

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

Issue/Introduction

Description:

When creating a CA Workload Automation AE job that is dependent on the success of a CA-7 job, you must use the correct xtype value in the cross-platform xinst definition. If the incorrect xtype value is entered dependant job will not be allowed to start as it should. The message, "CAUAJM_I_40162 This job's starting conditions have not been met - cannot be started." will be displayed when AutoSys attempts to start the job.

Solution:

When creating the xinst definition for cross-platform, identify if Unicenter AutoSys JM Connect is being used on the mainframe. This will determine the value you should enter for xtype in the xinst definition. If Unicenter AutoSys JM Connect is being used, the xtype value that should be entered is "c". If Unicenter AutoSys JM Connect is not being used, the xtype value should be "u" (For UUJMA).

Example 1:
When Unicenter AutoSys JM Connect is being used on the Mainframe:
jil>>1> insert_xinst: CA7
jil>>2> xtype: c
jil>>3> xmachine: SYSA
jil>>4> exit

Example 2:
When only using CCI and Unicenter AutoSys JM Connect is not installed on the Mainframe:
jil>>1> insert_xinst: CA7
jil>>2> xtype: u
jil>>3> xmachine: SYSA
jil>>4> exit

Additional details regarding creating the proper xinst definition can be found in the Unicenter AutoSys Job Management User Guide r11.0 under the section titled, Configure Enterprise Job Scheduling.

Environment

Release:
Component: ATSYS