Cross-instance job status shows *UNDEFINED* in QuickView
Article ID: 35362
Updated On:
Products
Issue/Introduction
In QuickView under "Starting Conditions", the "Current Status" column for a cross-instance dependency shows as *UNDEFINED*.
Cause
1. The instance referenced in the cross-instance dependency is not defined to the same WCC server in which the user is accessing QuickView. WCC needs to retrieve the status for the dependent job from the instance in which it resides. If that instance is not defined to the same WCC, it is unable to retrieve the status.
OR
2. The instance referenced in the cross-instance dependency is defined in WCC but the "Application Server Host Address" field for that instance's server definition in WCC does not match the "xmachine" attribute within the WAAE xinst definition. These two values must match or WCC will not be able to locate the xinst definition in WAAE.
Resolution
Note the instance name referenced in the cross-instance dependency.
For Cause #1:
Click on the "Configuration" tab in WCC and create a new server definition for the instance referenced in the cross-instance dependency.
Restart the WCC services.
For Cause #2:
Click on the "Configuration" tab in WCC and access the server definition for the instance referenced in the cross-instance dependency. Note the value for the "Application Server Host Address" field.
Go to the WAAE server for the instance where the job that contains the cross-instance dependency is defined.
Run 'autorep -X <INS> -q' where <INS> is the instance name referenced in the cross-instance dependency. Note the value for the "xmachine" attribute.
Either change the "Application Server Host Address" field to match the "xmachine" attribute within the xinst definition, or change the "xmachine" attribute to match the "Application Server Host Address".
Restart the WCC services.
Feedback
