During tape OPEN volume verification processing for file sequence 1 with DISP=NEW, the library was unable to assign construct names from the automatic class selection (ACS) routine. Consequently, the library sets policy names for the mounted volume to the default policy name. Even though the default policy names might be associated with the volume, the default policy actions might not always be used. There are times when the library will bind policy actions (for example, logical WORM, volume size, copy modes, and so on.) to the volume early in the mount process. In this case, the policy actions used by the library might be a mixture of both the requested and the default actions.
Either the library incurred an internal processing error and could not assign the specified policy names to the volume, or a policy name was to be created (not already defined for the library) when the maximum number of 255 unique construct names per construct type had already been reached.
This message can also be issued (except file sequence 1, DISP=NEW), if one or more of the construct definitions associated with an existing volume have been removed from the library. Default policy actions will be used for the construct definitions that are not found, and the library will maintain the volume’s construct assignments. The default policy name will not be substituted for an unfound construct definition. Also, note that in this special case, the message text does not include the “SG=, SC=, DC= and MC=” values. This information can be obtained by issuing the DISPLAY SMS,VOLUME command.
In the message text:
For file sequence 1, (DISP=NEW), the mount proceeds with the default policy name (blanks) and actions being used for the volume. The default policy name is assigned and used for each construct. For other than file sequence 1, (DISP=NEW), see explanation above.
Contact your system programmer.
If the failure was due to a limitation being reached on the number of unique construct names allowed for the library, determine the necessary adjustments to your ACS routines. You can later use the LIBRARY LMPOLICY command to reassign policy names to the volume. If the failure is because of one or more construct definitions being removed from the library, verify whether this was done intentionally. If not, the policy definitions and associated actions can be redefined using the library’s management interface.
Contact your system programmer.
Determine the cause of the warning. For an internal processing error, contact the IBM® Support Center to determine the cause of the internal processing error at the library.
DFSMSdfp