|
|
|
|
|
This group includes messages for Control-M/JCL Verify products.
Explanation: The message is issued when Control-M/JCL Verify detects that the list of the volumes in the catalog is not match the list of volumes specified in the JCL. Wrong volumes list in the JCL that override the catalog list, might corrupt the data in the file.
Corrective Action: Verify that the list of volumes specified in the JCL is correct.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset, specified by DISP=NEW in the JCL, already exists.
Corrective Action: Verify that the DISP and the DSN are correct.
Explanation: The message is issued when Control-M/JCL Verify starts validating the dataset, but fails to allocate workarea. The validation is aborted. This is an internal error.
Corrective Action: Try again. If the problem reoccurs, call BMC Customer Support.
Explanation: The message is issued when Control-M/JCL Verify starts validating the dataset, but fails to access the DSN block. The validation is aborted. This is an internal error.
Corrective Action: Try again. If the problem reoccurs, call BMC Customer Support.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset specified by DISP=OLD or DISP=SHR does not exist, is not cataloged, or has been deleted during the job processing.
Corrective Action: Verify that the DISP and the DSN are correct.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset specified by DISP=DELETE does not exist, or has been previously deleted during the job processing.
Corrective Action: Verify that the DISP and the DSN are correct.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset name is invalid because it does not comply with the syntax rules.
The validation continues without validating this dataset.
Corrective Action: Provide a valid dataset name.
Explanation: The message is issued when Control-M/JCL Verify starts the dataset validation and detects DISP CATLG. However, the file has already been cataloged so when the job is executed a "NOT CATLGD 2" message might be issued by the system.
Corrective Action: Validate that the DSN and DISP=(status,CATLG) are correct.
Explanation: The message is issued when Control-M/JCL Verify starts the dataset validation and detects DISP CATLG. However, the file has already been cataloged in a previous step so when the job is executed a "NOT CATLGD 2" message might be issued by the system.
Corrective Action: Remove the CATLG from the DISP=(status,CATLG).
Explanation: The message is issued when Control-M/JCL Verify starts the dataset validation process, but detects that the list of datasets is empty.
The validation is aborted. This is an internal error.
Corrective Action: Try again. If the problem reoccurs, call BMC Customer Support.
Explanation: The message is issued when Control-M/JCL Verify checks the data SMS class, but detects that the SMS class does not exist.
Corrective Action: Verify that the DATA CLASS is correct.
Explanation: The message is issued when Control-M/JCL Verify checks the storage SMS class, but detects that the SMS class does not exist.
Corrective Action: Verify that the STORAGE CLASS is correct.
Explanation: The message is issued when Control-M/JCL Verify checks the management SMS class, but detects that the SMS class does not exist.
Corrective Action: Verify that the MANAGEMENT CLASS is correct.
Explanation: The message is issued when Control-M/JCL Verify checks the VOLSER of a dataset, but detects that the VOLSER is different from the CATALOG information.
Corrective Action: Verify that the VOLSER and DSN are correct.
Explanation: The message is issued when Control-M/JCL Verify checks if the dataset is cataloged, but it does not exist.
Corrective Action: Verify that the DSN is correct.
Explanation: The message is issued when Control-M/JCL Verify checks the VOLSER of a dataset, but detects that the VOLSER is not mounted.
Corrective Action: Verify that the VOLSER is correct.
Explanation: The message is issued when Control-M/JCL Verify detects the SMS CLASSES, while SMS is not active.
Corrective Action: Check if DFSMS is active and rerun the job after DFSMS has been started.
Explanation: The message is issued when Control-M/JCL Verify detects that either the SMS CLASS does not exist or it is invalid.
Corrective Action: Verify that the SMS CLASS is correct.
Explanation: The message is issued when Control-M/JCL Verify is retrieving information from the DFSMS interface and the process ends with an error.
Corrective Action: Check the previous messages from the SMS that might appear in the JOB LOG.
Explanation: The message is issued when Control-M/JCL Verify detects that the specified UNIT does not exist.
Corrective Action: Verify that the UNIT name is correct.
Explanation: The message is issued when Control-M/JCL Verify detects that the specified UNIT is offline.
Corrective Action: Verify that the UNIT name is correct.
Explanation: The message is issued when Control-M/JCL Verify detects that the specified VOLSER does not match the provided UNIT.
Corrective Action: Verify that the VOLSER and the UNIT are correct.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is migrated.
Corrective Action: Verify that the dataset is correct.
Explanation: The message is issued when Control-M/JCL Verify detects that the specified member does not exist in the specified dataset.
Corrective Action: Verify that the member and the dataset are correct.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is a VSAM (index or data) component rather than a cluster.
Corrective Action: Verify that the dataset is using the correct DSNAME.
Explanation: The message is issued when Control-M/JCL Verify detects that DISP=NEW, but SPACE was not set in the JCL statement.
Corrective Action: Verify if the SPACE setting is required or the space can be set by SMS ACS routines.
Explanation: The message is issued when Control-M/JCL Verify detects DISP=NEW, but the DD statement is part of the CONCATENATION files. Since this is not valid, the job might abend due to an OPEN error.
Corrective Action: Change the DISP=NEW to SHR or OLD, or remove the DD statement from the CONCATENATION group.
Explanation: The message is issued when Control-M/JCL Verify detects that the CTJDSC module either did not receive any parameter list or it received an incorrect one. The validation is aborted. This is an internal error.
Corrective Action: Verify that the parameter list is correct.
Explanation: The message is issued when Control-M/JCL Verify detects the above DD statement and the UNIT keyword is missing. When DISP=OLD or SHR and VOL is specified, the dataset is accessed directly without checking the catalog and therefore the UNIT is required.
Corrective Action: Correct the statement and rerun job verification.
Explanation: The message is issued when Control-M/JCL Verify detects the above DD statement and it detects that the dataset is referred to twice; once with DISP=NEW and once with DISP=SHR/OLD. The dataset will not be found because the dataset does not exist when the system tries to allocate the dataset as an existing dataset.
Corrective Action: Correct the statement and rerun job verification.
Explanation: The message is issued when Control-M/JCL Verify detects the above DD statement and that the dataset is created with DISP=(NEW,PASS). In addition, it detects that the dataset is referred to twice in the same step with either DISP=(OLD,CATLG) or DISP=(SHR,CATLG). The second statement fails because the system removes the pass flag when handling the first DD statement. Refer to the MVS JCL Reference and MVS JCL Guide.
Corrective Action: Correct the statement and rerun job verification.
Explanation: The message is issued when Control-M/JCL Verify detects that the DISP=NEW, but SPACE was not set in the JCL statement.
Corrective Action: Add the missing SPACE keyword.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset, specified by DISP=NEW in the JCL, was already allocated in a previous step.
Corrective Action: Verify that the DISP and the DSN are correct.
Explanation: The message is issued when Control-M/JCL Verify detects that the specified dataset has been deleted (or renamed by a IDCAMS ALTER NEWNAME command) during the job processing.
Corrective Action: Verify that the DISP and the DSN are correct.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset specified by ALIAS with SYMBOLICRELATE, but the symbol is not found in the system symbolic variables.
Corrective Action: Verify that the SYMBOL can be resolved in the system.
Explanation: The message is issued when Control-M/JCL Verify detects that the specified dataset was CREATED or DELETED in a previous job. When the current job and the previous job are not on the same level, the last section of the message, "and may not exist | and may exist," is not relevant and therefore it is not displayed.
When the jobs are at the same level, the message changes according to the case as follows:
Corrective Action: Verify that the DISP and the dataset are correct.
Explanation: The message is issued when Control-M/JCL Verify detects that the file was created in the job with the PASS attribute, but was not cataloged or kept. The z/OS operation system deletes a file with the PASS attribute either during the last step of the job that references the file, or at the termination of the job.
Note: Control-M/JCL Verify does not issue this message for temporary datasets.
Corrective Action: No action is required.
Explanation: The message is issued when Control-M/JCL Verify detects that the file was created in the job with the UNCATLG attribute and was not cataloged or kept. The z/OS operation system deletes a file with the UNCATLG attribute either during the last step of the job that references the file, or at the termination of the job.
Note: Control-M/JCL Verify does not issue this message for temporary datasets.
Corrective Action: No action is required.
Explanation: The message is issued when Control-M/JCL Verify detects that the file was created in the job with the disp_type attribute and was not cataloged or kept. The z/OS operation system deletes a file with the disp_type attribute either during the last step of the job that references the file, or at the termination of the job.
Note: Control-M/JCL Verify does not issue this message for temporary datasets.
Corrective Action: No action is required.
Explanation: The message is issued when Control-M/JCL Verify detects that the file was created in the job with the disp_type attribute and was not cataloged or kept. The z/OS operation system deletes a file with the disp_type attribute either during the last step of the job that references the file, or at the termination of the job.
Note: Control-M/JCL Verify does not issue this message for temporary datasets.
Corrective Action: No action is required.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset specified was CREATED or DELETED in a previous job.
Corrective Action: Verify that the DISP and the DSN are correct.
Explanation: The message is issued when Control-M/JCL Verify, using the job dependency awareness feature for Control-M jobs (VD=Y), detects that the dataset specified in jcl_number with DISP2=DELETE was used with DISP=SHR/OLD in a previous job job_id at the same job hierarchy level. The JOB might fail because the file might have been deleted.
Corrective Action: Verify that the DISP and the DSN are correct.
Explanation: The message is issued when Control-M/JCL Verify detects that the system symbol is used, but symbol is not found in the system symbolic variables.
Corrective Action: Verify that the symbol can be resolved in the system.
Explanation: The message is issued when Control-M/JCL Verify detects a DD statement without a DSN keyword or VOLSER.
Corrective Action: Provide the DSN keyword or VOLSER with the required value.
Explanation: The message is issued when the catalog search interface fails during processing of a catalog query request. For more information refer to IBM message IDC3009I.
Corrective Action: Re-invoke the JCL Verify validation process for accurate results.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset, specified by DISP=NEW in the JCL, was already allocated in the preceding conditional step.
Corrective Action: Make sure that the current step and the preceding conditional step are mutually exclusive.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset, specified by DISP=OLD or DISP=SHR has been created or deleted by a conditional step earlier in the job.
Corrective Action: Make sure that the current step and the preceding conditional step are mutually exclusive.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset GDS with a relative positive number that is greater than zero specified by DISP=NEW in the JCL, that was already allocated in a preceding conditional step.
Corrective Action: Make sure that the current step and the preceding conditional step are mutually exclusive.
Explanation: The message is issued when Control-M/JCL Verify detects DISP CATLG but the file was cataloged in a preceding conditional step.
When the job is executed a "NOT CATLGD 2" message might be issued.
Corrective Action: Make sure that the current step and the preceding conditional step are mutually exclusive.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset, specified by DISP=SHR or OLD, is GDG and therefore all GDS in the GDG will be allocated.
Corrective Action: If this situation is not what is required, correct the DSNAME or add the GDS relative number.
Explanation: The message is issued when Control-M/JCL Verify detects that the relative GDS number is higher than the GDG LIMIT in the GDG catalog entry. The job will fail with a JCL error.
Corrective Action: Correct the relative GDS number so that it is within the limit set in the GDG catalog entry.
Explanation: The message is issued when the Control-M/JCL Verify relative GDS number is higher than 255. The job will fail with a JCL error.
Corrective Action: 1) For DISP=SHR or OLD, correct the relative GDS number to be within the limit set in the GDG catalog entry. 2) For DISP=NEW, set the relative GDS number to a value lower than 255.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is a GDS with a relative number, but the string number is not numeric. The job will fail with a JCL error.
Corrective Action: Correct the relative number.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is a GDS with a relative number, but the string contains more than three characters. Since the maximum number of characters is three, the relative number is invalid. The job will fail with a JCL error.
Corrective Action: Correct the relative string number so that it is no more than three characters.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is a GDG but does not contain any GDS. The job will fail with a JCL error.
Corrective Action: Correct the name of the file or add a GDS to the GDG.
Explanation: The message is issued when Control-M/JCL Verify detects that the GDS relative sign is not valid. (The valid values are: "+', "-" or "0".) The job will fail with a JCL error.
Corrective Action: Correct the relative GDS number.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is a GDS with a relative number of zero or negative, but the DISP=NEW. The job will fail with a JCL error.
Corrective Action: Correct the relative GDS number so that it is a positive number, or change the DISP=NEW to DISP=SHR/OLD/MOD.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is a GDS with a relative positive number (greater than zero), but the DISP=SHR or OLD. The job will fail with a JCL error.
Corrective Action: Correct the relative GDS number so that it is zero or negative, or change the DISP=SHR/OLD/MOD to DISP=NEW.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is a GDS with DISP=NEW and with the same relative positive number that was already used in a previous step.
The job will fail with a JCL error.
Corrective Action: Correct the GDS relative number to be a different positive number (greater than zero).
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is a new GDS, but the termination DISP value is not CATLG and therefore, the GDS will be part of the GDG. In a SMS environment the file will be cataloged and the GDG will be marked as pending ROLE IN. A None-SMS file will not be cataloged and can exist on the volume.
Corrective Action: Correct the DISP= to be DISP=(NEW,CATLG).
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is a GDS, but the termination DISP=(status,UNCATLG) will cause the file to be uncataloged, removed from GDG, and deleted from the volume it is allocated on.
Corrective Action: Correct the DISP= with the correct termination value.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is a GDG name with DISP=NEW in the JCL. A GDG cannot be a new file. A GDG with a relative positive number that is larger than zero can exist and it is called a GDS. The job will fail with a JCL error.
Corrective Action: If the DSNAME is correct, add a GDS positive relative number that is greater than 0. Otherwise, change the DSNAME.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is in a GDS format but it is not part of a GDG. The job will fail with a JCL error.
Corrective Action: Provide a valid GDS or add the file to the GDG using the IDCAMS ALTER ROLLIN command.
Explanation: The message is issued when Control-M/JCL Verify starts the dataset validation and the internal validation failed. The validation is aborted.
Corrective Action: Try again. If the problem reoccurs, call BMC Customer Support.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is a GDS with a relative number, but the name is longer than 35 characters. When the GDG name, together with the relative number, is transformed to the full DSNAME, it cannot be longer than 44 characters. The relative number format ID ".GxxxxVyy". The job will fail with a JCL error.
Corrective Action: Correct the dataset name.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is in a GDS format, but the GDG does not exist in the MVS Catalog. The job will fail with a JCL error.
Corrective Action: Check whether the GDS name must be corrected.
Explanation: The message is issued when Control-M/JCL Verify detects that a GDS file was allocated or deleted. Note that the "V%%" suffix added to the GDS name indicates that it is a psuedo GDS DSNAME, not a real and cataloged GDS name.
Corrective Action: No action is required.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is a SMS-MANAGED file.
Corrective Action: No action is required.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is not a SMS-MANAGED file.
Corrective Action: No action is required.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is not a SMS-MANAGED file.
Corrective Action: No action is required.
Explanation: The message is issued when Control-M/JCL Verify detects that the DSNTYPE=PIPE was specified without specifying PATH=parameter.
Corrective Action: No action is required.
Explanation: The message is issued when Control-M/JCL Verify received an unidentified return code or reason code from the DFSMS subsystem.
Corrective Action: Review the return and reason codes.
In most cases the problem is because of ACS routines or exit violations.
Explanation: The message is issued when Control-M/JCL Verify detects an error return from the Storage Management Subsystem.
Corrective Action: Verfy that the DFSMS subsystem has not stopped during the Control-M/JCL Verify process. Review the return codes as described in the IBM DFSMSdfp Diagnosis Reference, in the Storage Management Subsystem interface return codes section.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is a SMS-MANAGED file and the above classes were selected by the ACS routine or exits.
Corrective Action: No action is required.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is a SMS-MANAGED file and the above storage group was selected by the ACS routine or exits.
Corrective Action: No action is required.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is not an SMS-MANAGED file, but an SMS-MANAGED VOLUME was specified.
Corrective Action: No action is required.
Explanation: The message is issued when Control-M/JCL Verify detects that the dataset is a SMS-MANAGED file but the volume in the DD statement is not SMS-MANAGED volume.
Corrective Action: Correct the VOLUME and change it to an SMS MANAGED volume serial number.
Explanation: The message is issued when Control-M/JCL Verify detects that the SMS DATA/STORAGE/MANAGEMENT class selected by the ACS routine is not the same as specified in the previous DD statement.
Corrective Action: Verify that the selected class is correct.
Explanation: The message is issued when Control-M/JCL Verify detects that a file should be an SMS managed file, but the ACS rejects the file as not being an SMS-MANAGED file and therefore ignored the SMS DATA/STORAGE/MANAGEMENT class settings in the DD statement.
Corrective Action: Verify that the file should not be an SMS MANAGED file.
Explanation: The message is issued when Control-M/JCL Verify received reason code 1011 from the DFSMS SUBSYSTEM, which means that the ACS routine assigned a DATA/STORAGE/MANAGEMENT class that does not exit.
Corrective Action: For more information, refer to the description of the IBM message IGD01011I.
Explanation: The message is issued when Control-M/JCL Verify received an error reason code from the DFSMS SUBSYSTEM, which means that the ACS routine did not assign a storage group, as it was supposed to.
Corrective Action: For more information, refer to the description of the IBM message IGD01013I.
Explanation: The message is issued when Control-M/JCL Verify detects that the SMS CLASS specified by DATACLAS/STORCLAS/MGMCLAS does not exist.
Corrective Action: For more information, refer to the description of the IBM message IGD01014I.
Explanation: The message is issued when Control-M/JCL Verify detects that the ACS STORAGE GROUP ROUTINE ASSIGNED an incorrect storage group.
Corrective Action: For more information, refer to the description of the IBM message IGD01012I.
Explanation: The message is issued when Control-M/JCL Verify detects that the SMS CLASS specified by DATACLAS/STORCLAS/MGMCLAS does not exist.
Corrective Action: For more information, refer to the description of the IBM message IGD01001I.
Explanation: The message is issued when Control-M/JCL Verify received an AUTHORITY error from the DFSMS SUBSYSTEM, which means that the ACS routine or the SMS EXIT failed to fulfill the allocation request.
Corrective Action: Refer to the previous message(s).
Explanation: The message is issued when Control-M/JCL Verify received reason code 1001 from a DFSMS subsystem, meaning that the ACS or SMS exit failed to fulfill the allocation request.
Corrective Action: Refer to previous message(s).
Explanation: The message is issued when Control-M/JCL Verify detects that the space requested for a new allocation might not be available in the volume or storage group.
Corrective Action: Refer to previous message(s).
Explanation: The message is issued when Control-M/JCL Verify detects that the user tried to allocate a new dataset without specifying the space parameter.
Corrective Action: Refer to previous message(s).
Explanation: The message is issued when Control-M/JCL Verify detects that the user tried to allocate a new partitioned dataset (PDS/PDSE), but the space requested for the directory exceeds the available primary space.
Corrective Action: Refer to previous message(s).
Explanation: The message is issued when Control-M/JCL Verify detects that the user tried to allocate a new dataset with a space request exceeding 65535 tracks for a data set type that is limited to 65535 tracks per volume.
Corrective Action: Refer to previous message(s).
Explanation: The message is issued when Control-M/JCL Verify detects that the user tried to allocate a new dataset with a partitioned and multi-volume structure. However, partitioned datasets cannot be multi-volume datasets.
Corrective Action: Correct the dataset allocation parameters.
Explanation: This warning message is specified when Control-M/JCL Verify detects that the user is trying to allocate a new data set with GUARANTEE SPACE=YES in the SMS defenition but the volume that is specified is not compatible with the storage class.
Parent Topic |