search cancel

U2007018 'Invalid Run Control ID. (65,33)' Automic & RIT Peoplesoft each reporting different status.

book

Article ID: 89156

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

U2007018 'Invalid Run Control ID. (65,33)' Automic & RIT Peoplesoft each reporting different status.

Environment

Release: AOATAM99000-9.0-Automic-One Automation Tools-Application Manager
Component:

Resolution

Detailed Description and Symptoms

Automic and RIT Peoplesoft are each reporting different statuses for executed jobs. The RIT Peoplesoft status will show as successful, while in the Last Report of the Automic job, the Activation tab shows an error. Example:

U2000005  Job 'JOBS.PS.RITSR061_CLAWS' with RunID '6048173' started.
U2004018  The job was successfully interpreted. 
                      PS_RUN_PROCESS PROCESSNAME='RITSR061',PROCESSTYPE='SQR Process', RUNCONTROLID='DCO_ADCLAWS_2 ',RUNLOCATION='PSUNX',OUTDESTTYPE='NONE'
U2007018  'Invalid Run Control ID. (65,33)'
U2004025  Job-script execution was aborted.


Investigation

The line "U2007018  'Invalid Run Control ID. (65,33)' " is pointing to the "RUNCONTROLID=" parameter in the PS_RUN_PROCESS. In this particular example, there's an extra space at the end of the RUNCONTROLID, just after the 2: RUNCONTROLID='DCO_ADCLAWS_2 '


Solution

Getting rid of the space after the 2 will clear this up.

Example: 

RUNCONTROLID='DCO_ADCLAWS_2 '     < Incorrect

 - as opposed to - 

RUNCONTROLID='DCO_ADCLAWS_2'      < Correct