Messages › CA MIM Messages › MIM0076W

MIM0076W

{DDNAME|MEMBER} name not found - initialization data set not processed

For CA MIM for z/OS

Reason:

CA MIM could not find the specified data set or member during initialization. If CA MIM was trying to locate the MIMSYNCH member, then it will continue without that member. Otherwise, it will terminate on the local system with a user abend code U0040.

If a DDNAME is shown, then one of these conditions produced this message:

• A //MIMPARMS DD statement was not specified in the startup procedure.
• CA MIM cannot access the data set specified on the DD statement.

If a member name is shown, then one of these conditions produced this message:

• The member was incorrectly identified.
• This error message may be referring to a member name specified on the COMMANDS, DEVLIST, MEMBER, QNAMES, or SYNCH parameters on a MIMINIT statement, the EXEMPT parameter on a GDIINIT statement, or the MEMBER parameter on an EDIINIT statement.
• The member name was not specified, and CA MIM cannot find the member that it uses by default.
• CA MIM cannot access the library in which this member resides.

Action:

Take one of the following actions:

• Identify the CA MIM parameter data set through a //MIMPARMS DD statement. Then restart CA MIM.
• Compare the member name with the name of the member that you are trying to use to see if they match. If not, then correct the statement.
• Make sure that CA MIM can access the data set specified on the DD statement.

For CA MIM for z/VM

Reason:

This message indicates that CA MIM could not find the file associated with the DDNAME during initialization. The DDNAME that could not be found is shown in name.

If name is MIMSYNCH, this message is issued as a warning. CA MIM continues processing without the specified file. For any other DDNAME, CA MIM terminates on the local system with a user abend U028 (Hex).

This error is caused by one of the following:

• Not providing or misnaming a standard file that should be on the MIMGR A-disk (for example, the INIT MIM file).
• Incorrect use of a FILEDEF command to rename a standard file.

Action:

Check that all standard initialization files needed are in place. If you have used your own FILEDEF commands, be sure they are correct.