When an SMI-S client cannot correctly process entries of tape libraries from the DFSMSrmm CIM agent

If you request either DFSMSrmm tape libraries or their contents from a SMI-S CIM client and no data is returned, check these items:

SLP regestration should be initiated. While building the OpenPegasus package on your own, ensure the PEGASUS_ENABLE_SLP environment variable is set to true. On z/OS, the following console message should accompany the start of cimserver:
```
CFZ00001I: PGS18204: SLP Registration Initiated
```
Both on z/OS and Linux, you can issue the following command within z/OS USS to enquire the configuration status of SLP registration:
```
cimconfig -g slp -c
```
If the answer is false, issue the following command:
```
cimconfig -p -s slp=true
```
and restart the CIM server.
Log file rmmcim.log should not contain any error messages reporting incorrect requests to the DFSMSrmm CIM agent. If any messages occur, correct the error on the client side. For example, if the format of the compound key for Tag attribute of IBMRMM_Location class is violated, then the following message is issued:
```
EDGC0031I: Key "Tag" is not of the required format "LocationName+LocationType+CdsID"
```
Displaying the messages obtained from CIM server on the CIM client side simplifies the tracking of the requests processed.
If errors occur in communication between clients and OpenPegasus CIMOM, the analysis of the errors is outside DFSMSrmm capability. Before using a client, check out if the client has any limitations on exploiting OpenPegasus.