Messages › GTAF and TPCF Messages › MIM2003

MIM2003

NO MANAGED DEVICES

Reason:

If this message is issued in response to the RESYNCH command, then CA MIM issues message MIM2115, allowing you to resubmit the RESYNCH command. This WTO clears as soon as CA MIA is managing at least one device. Otherwise, this message indicates that CA MIM is terminating at startup because no devices were placed under CA MIA management.

One or more of the following conditions causes this:

• CA MIA does not recognize the local names of any of the devices listed in this member. Verify the local names for these devices.
• None of the entries in this member were directed to the local system.

  Note: Entries may be directed to certain systems or to a group of systems using IFSYS and ENDIF statements.

• If a category of devices was placed under the management of CA MIA (in addition to the devices listed in the CA MIM device control member), then this message indicates that no local device falls into this category and that one of the conditions mentioned above exists for the CA MIM device control member.
• (z/OS) No entries were placed in the MIMUNITS member.
• (z/OS) DEVLIST=NO was specified in the initialization member and no class of devices was placed under the management of CA MIA on the local system (using the DEVCLASS parameter).
• (z/VM) The UNITS MIM file does not exist or no entries were placed in the file.

The DEVCLASS parameter on the MIMINIT statement is used to place a category of devices under the management of CA MIA.

(z/OS) CA MIA examines the CA MIM device control member for device control information unless DEVLIST=NO is specified on the MIMINIT statement. The name of the device control member is specified by the DEVLIST parameter. The default name for this member is MIMUNITS.

(z/VM) Note: A 3480 or 3490 tape drive identified during system generation as an unsupported device will be controlled only if that device is explicitly included in the UNITS MIM file.

Action:

If the DEVCLASS or DEVLIST parameters were incorrectly specified, correct them and restart CA MIM. Otherwise, review and modify the entries in the device control member before restarting.