As mentioned above, data set rejection reasons are listed in the job log following CTT356W messages.
Table 15 Data Set Rejection Reason Code
Reason Code |
Description |
---|---|
10 |
Control-M/Tape is running in Global Test mode. |
11 |
Exit 2 disallowed stacking for the data set. |
12 |
No rule was found for the data set. |
13 |
A rule was found for the data set but the DO STACK=YES statement was not included in the rule. |
14 |
The data set is managed by an external data manager (EDM). |
15 |
Control-M/Tape rules for the data set were run in Test mode. |
16 |
The rule associated with the data set being created specifies a vault pattern for the data set, but neither V nor A was specified for the STKMODE parameter. |
17 |
No statistics were found for the data set and no default statistics were specified in the STKDEFSZ parameter. |
18 |
The data set is not stackable (for example, because //NOSTACK was specified in the JCL). |
19 |
The DO POOL statement in the relevant rule specifies a pool that was not defined to Control-M/Tape. |
20 |
Internal error. Contact your local INCONTROL representative for more information. |
21 |
An eligible volume with sufficient space for the data set could not be found in the specified pool. |
22 |
No media was specified in the CTTMEDDF Control-M/Tape installation. |
23 |
Stacking for the data set was stopped due to a request from Control-M/Tape Exit 10. |
24 |
Either the unit specified in the JCL was not specified in the STKUNIT Control-M/Tape installation parameter, or the data set is managed by DFSMS but was not assigned storage group of type TAPE. |
Parent Topic |