Troubleshooting › Custom CFGFILE Member for User

Custom CFGFILE Member for User

Symptom:

The following message is issued for the Object Migrator analysis, but the status remains Submitted in the UI and never changes:

Migration Analysis successfully submitted.

The job appears to be stuck.

Solution:

Verify that the background job was submitted for the user. The job could have failed because of incorrect accounting information. In this case, the UI is not updated.

Each user may require their own member in the Object Migrator configuration file (CFGFILE). The member name has to be the same as the users logon ID. The users may specify JOBCARD and CA RC/Migrator Utility Model Services.

To ensure that the job was submitted for the user, complete the following steps:

1. Verify that the logon ID member exists in the CFGFILE.
2. If a logonid does not exist, review the JOBCARD in the @DEFAULT member.