104

CA 1 has allocated all available DSNBs. The number of DSNBs available is equal to the number generated minus 1.

Execute TMSBINQ or use CA 1 online facilities to determine if the DSNB allocation has been exhausted, or only appears to be exhausted (the number of used DSNBs is not equal to the number allocated minus 1). If the DSNB allocation has reached capacity, DSNBs can be released by using the TMSCLEAN utility to scratch tapes that have associated DSNBs. If this is a common occurrence, you should consider EXTENDing the TMC with the TMSFORMT utility to add new DSNBs. If the DSNB allocation has not reached capacity, there are chaining errors within the allocation. Execute TMSPTRS to generate a report on the errors, and then correct them with CA 1 batch or online facilities. Monitor the output of TMSCOPY to prevent this from occurring in the future.

108

CA 1 has allocated all available DSNBs. The DSNB being allocated is the last DSNB.

Execute TMSBINQ or use CA 1 online facilities to determine if the DSNB allocation has been exhausted, or only appears to be exhausted (the number of DSNBs is not equal to the number allocated minus 1). If the DSNB allocation has reached capacity, DSNBs can be released by using the TMSCLEAN utility to scratch tapes that have associated DSNBs. If this is a common occurrence, you should consider EXTENDing the TMC with the TMSFORMT utility to add new DSNBs. If the DSNB allocation has not reached capacity, there are chaining errors within the allocation. Execute TMSPTRS to generate a report on the errors, and then correct them with CA 1 batch or online facilities. Monitor the output of TMSCOPY to prevent this from occurring in the future.