|
|
|
|
|
This group includes messages for the IOA (infrastructure) product.
Explanation: The number of blocks in the file, indicated by the ddName DD statement, does not match the CNDREC# parameter defined in the IOAPARM member. The IOACCND verification program terminates with a return code of 04.
Corrective Action: Correct the number of blocks specified in the CNDREC# parameter table, or increase the file size so that it contains at least as many blocks as specified in the table.
Explanation: The actual size of the file pointed to by the ddName DD statement was greater than the size defined in the parameter table by a factor of more than one track.
The size of the file is defined in IOAPARM, CTMPARM or CTDPARM, depending on the product in which the file is used.
The verification program terminates with a return code of 04.
Corrective Action: Correct the number of blocks specified in the parameter table, or change the file size, so that they correspond more closely.
Explanation: File utilization data cannot be obtained because the Active Jobs file pointed to by the ddName DD statement is currently being formatted.
Processing of the Active Jobs file terminates with a return code of 08.
Corrective Action: Try running the IOAVERFY utility later.
Explanation: QNAME qName1 defined in CTMPARM differs from QNAME qName2 specified in the file pointed to by the ddName DD statement.
In a correctly installed system, the qnames of the files must be identical to the QNAME specified in CTMPARM.
Processing of the current command terminates with a return code of 8.
Corrective Action: Reformat the file pointed to by the ddName DD statement using the proper installation procedures.
Explanation: An incorrect record length was specified for the file pointed to by the ddName DD statement. The record length should be the length len specified in the message for the version of the product versn indicated in the message.
Processing of the current command terminates with a return code of 08.
Corrective Action: Delete and redefine the file with the proper record length.
Explanation: The IOA version found in the file pointed to by the ddName DD statement was not recognized.
Processing of the current command terminates with a return code of 08.
Corrective Action: Reformat the file and rerun the IOAVERFY utility. If the problem persists, notify BMC Customer Support.
Explanation: The file pointed to by the ddName DD statement is defined with data set organization org. It should be defined as DA (Direct Access) or sequential.
Processing of the current command terminates with a return code of 08.
Corrective Action: Define the file according to the specifications contained in the IOA Installation Guide.
Explanation: The file pointed to by the ddName DD statement has the record format recFormat. It should be defined as F (Fixed).
Processing of the current command terminates with a return code of 08.
Corrective Action: Define the file according to the specifications contained in the IOA Installation Guide.
Explanation: The file pointed to by the ddName DD statement has an invalid device type (device_type).
Valid device types, as indicated in the message, are 3340, 3350, 3375, 3380, 3390 and 9345.
Processing of the current command terminates with a return code of 08.
Corrective Action: Define a valid device type for the file.
Explanation: The number of real blocks in the file, indicated by the ddname DD statement, does not match the CNDREC# parameter defined in the IOAPARM member. The IOACCND verification program terminates with a return code of 04.
Corrective Action: Correct the number of blocks specified in the CNDREC# parameter table, or increase the file size so that it contains at least as many blocks as specified in the table.
Explanation: An internal error occurred during the INIT or PROCESS stage of the IOAVERFY run.
Corrective Action: Try running IOAVERFY again. If the problem persists, contact BMC Customer Support.
Explanation: The alternative index file cannot be read by the IOAVERFY utility.
Corrective Action: Check that the alternative index file exists. If necessary, contact BMC Support.
Explanation: IOAVERFY found that the alternative index of the active file is identical to that of the specified file:
Corrective Action: No action required.
Explanation: IOAVERFY found that the alternative index of the active file differs from that of the specified file:
Corrective Action: Compare the differing files and resolve the differences.
Explanation: No MIG partitions found, the IOAVERFY utility will not run.
Corrective Action: No action required.
Explanation: The IOAVERFY utility could not access the MIG partition. The IOAVERFY utility will not run.
Corrective Action: Try again later. If the problem persists, contact BMC Customer Support.
Explanation: Title of the Migration Partition report within the DAVRFOUT DDcard. Generated by the IOAVERFY utility.
Corrective Action: No action required.
Explanation: IOAVERFY detected a routine that finished NOT OK.
Corrective Action: No action required.
Explanation: IOAVERFY will now begin comparison of the Active Alternative Index list with the ALTERNATIVE INDEX list of the other user files. Due to the length of the files, only the first 100 lines will be included in the comparison.
Corrective Action: No action required.
Explanation: IOAVERFY found that this routine ended without errors.
Corrective Action: No action required.
Explanation: IOAVERFY found that this routine ended with errors.
Corrective Action: Use this information to troubleshoot the routine.
Explanation: The file pointed to by the ddName DD statement is defined on more than one volume. Volume volser indicates the first volume.
Processing of the current command terminates with a return code of 08.
Corrective Action: Make sure that the file is defined on one volume only.
Explanation: Volume volser, which contains the file pointed to by the ddName DD statement is not available.
Processing of the current command terminates with a return code of 16.
Corrective Action: Make sure that the volume volser is online, and rerun the IOAVERFY utility.
Explanation: No format-1 DSCB was found on volume volser for the file pointed to by the ddName DD statement.
The file pointed to by the ddName DD statement is not defined on volume volser.
Processing of the current command terminates with a return code of 16.
Corrective Action: Make sure that the correct volume is referenced in the JCL of the ddName DD statement, or that the file is correctly cataloged.
Explanation: An error has occurred when accessing the VTOC of volume volser.
Processing of the current command terminates with a return code of 16.
Corrective Action: Contact BMC Customer Support.
Explanation: The block size of the file pointed to by the ddName DD statement is larger than the size of a track on the disk on which the file resides.
Processing of the current command terminates with a return code of 08.
Corrective Action: Define the block size of the file to be no greater than one track.
Explanation: The file pointed to by the ddName DD statement does not contain any records.
Processing of the current command terminates with a return code of 16.
Corrective Action: Format the file (using the appropriate formatting step in the ICE CUSTOMIZE process), and rerun the IOAVERFY utility.
Explanation: The specified command cannot be used to obtain system information under Fujitsu.
Processing of the current command terminates with a return code of 08.
Corrective Action: No action is required.
Explanation: A LIST SUBSYSTEM command was specified for a subsystem (subsys) which is not defined.
The LIST SUBSYSTEM command lists the control blocks for the specified subsystem. If the subsystem name is omitted, the default is taken from IOAPARM.
Processing of the current command terminates with a return code of 08.
Corrective Action: Specify the LIST SUBSYSTEM command either with a correct subsystem name or without a subsystem name.
Explanation: This information message is generated when the IOAVERFY utility determines (using the LIST SUBSYSTEM command) that subsystem subsys is not active.
Processing of the current command terminates with a return code of 04.
Corrective Action: No action is required.
Explanation: This information message is generated if the IOA environment in the subsystem control blocks does not match the environment the IOAVERFY utility belongs to.
This message is accompanied by messages VRFJ22I and VRFJ23I, which provide additional information about the mismatched environments.
Blocks SSCT and SSVT are printed, and the command terminates.
Corrective Action: Provide BMC Customer Support with the information presented in messages VRFJ22I and VRFJ23I.
Explanation: This information message displays the environment (env) found in the control blocks of the subsys subsystem.
This messages accompanies message VRFJ21I, which indicates an environment mismatch between the subsystem and the IOAVERFY utility.
Corrective Action: No action is required.
Explanation: This information message displays the environment (env) of the IOAVERFY utility.
This message accompanies message VRFJ21I, which indicates an environment mismatch between the subsystem and the IOAVERFY utility.
Corrective Action: No action is required.
Explanation: The IOAVERFY utility detected an internal error while scanning the subsystem control blocks.
Processing of the current command terminates with a return code of 16.
Corrective Action: Notify BMC Customer Support.
Explanation: The value of the CKPSIZE parameter in CTMPARM is not equal to the value in the MI0SIZE field of Active Jobs File (AJF) record0 (the first record in the AFJ).
DSECT CTMMI0 describes AJF record0.
The number of records in the AJF (the value in the MI0SIZE field) must equal the number specified by CKPSIZE in CTMPARM.
Processing of the current statement stops and a return code of 16 is issued.
Corrective Action: Make sure that the ALCIOVFY library member in PARM points to the correct AJF.
Explanation: A table (identified by RBA YYYYYY) contains a job (identified by RBA XXXXXX), but the job does not include a reference to the table.
Corrective Action: Run the utility again with the CORRECT parameter.
Explanation: A job (identified by RBA XXXXXX) includes a reference to a table (identified by RBA YYYYYY), but the table does not contain the job.
Corrective Action: Run the utility again with the CORRECT parameter.
Explanation: A job (identified by RBA XXXXXX) includes a reference to a non-table entity (identified by RBA YYYYYY), but the job is not contained in any table.
Corrective Action: Run the utility again with the CORRECT parameter.
Explanation: During the execution of the IOA IOAVERFY utility in which the following request was issued:
DIAGNOSE AJF FORMAT OID=oid
the utility determined that the job associated with order-ID oid was ordered as part of (contained in) a SMART table. Since the utility supports the OID parameter for stand-alone jobs only, but not for jobs that are part of SMART tables, the DIAGNOSE FORMAT request is performed for the entire AJF. The utility continues processing the entire AJF.
Corrective Action: No action is required.
Explanation: The value of the CNDREC# parameter in IOAPARM, which specifies a number of records, does not match the number of records specified in the SNC record.
A number of records is set during installation to determine file sizes. CNDREC# specifies the number of records in the IOA Conditions file. This value must equal the number of records that SNCCND# specifies in the SNC record.
The system stops processing the current statement and issues a return code of 16.
Corrective Action: Make sure that the ALCIOVFY library member in IOAPARM points to the correct SNC file.
Explanation: Two VER statements occur in succession.
One REP statement must follow each VER statement.
Only the second VER statement is processed.
Corrective Action: Correct the VER and REP statements, and rerun the IOAVERFY utility.
Explanation: A REP statement precedes a VER statement.
Each REP statement must follow a VER statement.
Only the VER statement is processed. The REP statement is ignored.
Corrective Action: Correct the VER and REP statements, and rerun the IOAVERFY utility.
Explanation: Two REP statements occur in succession.
One VER statement must precede each REP statement.
Only the second REP statement is processed. The first REP statement is ignored.
Corrective Action: Correct the VER and REP statements, and rerun the IOAVERFY utility.
Explanation: There is no VER statement before the current REP statement.
One VER statement must precede each REP statement.
The REP statement is ignored.
Corrective Action: Correct the VER and REP statements, and rerun the IOAVERFY utility.
Explanation: This information message indicates that the Control-M Active Jobs file, the Control-M History file, the IOA Conditions file, or the Control-M Resources file, was updated by a set of VER and REP statements.
Corrective Action: No action is required.
Explanation: The VERIFY utility found that the number of units of this resource currently in use exceeds the maximum defined for it.
Corrective Action: Use the ADD, CHANGE and/or DELETE options on screen 4 to manually balance the resource file.
Explanation: This information message indicates that the DIAGNOSE command of the IOAVERFY utility did not find any errors in the specified file.
In this message, verifyType is one of the following:
Corrective Action: No action is required.
Explanation: When a file is to be modified by means of the VER and REP statements using the IOAVERFY utility, the file to be modified must be identified in a ZAP statement that must precede the VER and REP statements.
The ZAP statement must be in the format
ZAP FILE fileId
where fileId is one of the following:
Corrective Action: No action is required.
Explanation: This informational message indicates that the IOAVERFY utility was invoked with the VERIFY ENQ parameter on the system-id system to verify the locking mechanism for the qname QNAME.
Corrective Action: No action is required.
Explanation: An error occurred when executing the IOAVERFY utility with the VERIFY ENQ parameter. The utility terminated with return code 12. The error type and reason codes displayed in the message indicate the type of error.
Corrective Action: Keep the IOAVERFY job log of the failed run and contact BMC Customer Support.
Explanation: This informational message indicates that the IOAVERFY utility, invoked with the VERIFY ENQ parameter, finished verifying the locking mechanism for the qname QNAME on the system-id system.
Corrective Action: Verify that the list produced by the IOAVERFY utility (beginning with the VRFJ44I title message and continuing with the VRFJ45I informational messages) includes all the systems where the instances of IOAVERFY (with the VERIFY ENQ parameter) were simultaneously invoked. Any system that is not included has a problem with the ENQ related definition. For further information about the QNAME and SHRQNAM parameters, see the chapter about IOA in the INCONTROL for z/OS Installation Guide.
Explanation: This informational message indicates that the IOAVERFY utility, with the VERIFY ENQ parameter, is ready to start checking the locking mechanism.
Corrective Action: Do one of the following:
Explanation: This title message precedes the VRFJ45I informational messages that display the systems that correctly share the ENQ resources.
Corrective Action: No action is required.
Explanation: This informational message contains the name of a system (detected by the IOAVERFY utility with the VERIFY ENQ parameter) that correctly shares the ENQ resources. The list of VRFJ45I messages is preceded with the VRFJ44I title message.
Corrective Action: Verify that the list produced by the IOAVERFY utility includes all the systems where the instances of IOAVERFY (with the VERIFY ENQ parameter) were simultaneously invoked. Any system that is not included has a problem with the ENQ related definition. For further information about the QNAME and SHRQNAM parameters, see the chapter about IOA in the INCONTROL for z/OS Installation Guide.
Explanation: The IOAVERFY utility (with the VERIFY ENQ parameter) detected that ENQ requests (with the QNAME specified in the utility parameters) are excluded from cross-system serialization. If the z/OS Global Resource Serialization is being used, this occurs when RNLDEF RNL(EXCL) is defined for qname in the GRS resource name list. The utility terminates with a return code of 8.
Corrective Action: If the z/OS Global Resource Serialization is used, remove the RNLDEF RNL(EXCL) definition for qname. If another cross-system serialization facility is used, ensure that the ENQ requests for qname are correctly handled by the facility. For further information about the QNAME and SHRQNAM parameters, see the chapter about IOA in the INCONTROL for z/OS Installation Guide.
Explanation: The IOAVERFY utility (with the VERIFY ENQ parameter) detected that the global resource serialization is not active on the system where the utility ran. The utility terminates with a return code of 8.
Corrective Action: If the IOA and Control-M files are accessed from several systems (in a multi-system environment), the global resource serialization facility must be activated to provide serialized file access and update, while preventing file corruption. For further information about the QNAME and SHRQNAM parameters, see the chapter about IOA in the INCONTROL for z/OS Installation Guide.
Parent Topic |