Reason:
The reorganization step indicated began executing.
Action:
None.
Reason:
The reorganization step that has just ended and its return code.
Action:
None.
Reason:
The current reorganization step being processed, the substep it is in, and the amount of time it has been there.
Action:
None.
Reason:
The page range for the area being processed.
Action:
None.
Reason:
The number of the current page and the percentage of pages thathave been processed.
Action:
None.
Reason:
The number of records contained in the input file.
Action:
None.
Reason:
The number of the current record and the percentage of records thathave been read.
Action:
None.
Reason:
The index set being processed and its sequence in the total numberof index sets.
Action:
None.
Reason:
The number of IXDET records read.
Action:
None.
Reason:
A message number cannot be found in the designated module message table.
Action:
Contact Computer Associates Product Support.
Reason:
USRAUDT received an invalid communication switch.
Action:
Contact Computer Associates Product Support.
Reason:
The utility is still executing, but it is not performing one of the primary steps.
Action:
None.
Reason:
Module could not be called because of an internal problem.
Action:
Contact Computer Associates Product Support.
Reason:
Module cannot be located in the available load or core-imagelibraries.
Action:
Locate the load or core-image library that contains module and make it available to the job.
Reason:
Module cannot be loaded due to insufficient GETVIS area (VSE/ESAonly).
Action:
Resubmit the job with a smaller SIZE= parameter or run in larger partition.
Reason:
An internal error has been detected.
Action:
Contact Computer Associates Product Support.
Reason:
An internal error has been detected.
Action:
Contact Computer Associates Product Support.
Reason:
A DBIO error has occurred. The program indicated was executing atthe time of the error.
Action:
The action required depends on interpretation of the DBIO error code given in Message: DBST002E.
Reason:
A DBIO error has occurred.
Action:
To find the meaning of the first two digits of the error code,refer to the CA IDMS major error codes listed in the CA IDMS Messages and Codes Guide or the supplemental list in the following figure. If the third and fourth digits of the error code fall within the ranges 00-99, see the list of CA IDMS minor error codes found in the CA IDMS Messages and Codes Guide.
Reason:
A DBIO error has occurred. The record indicated was the last oneprocessed successfully before the error occurred.
Action:
The action required depends on interpretation of the DBIO error code given in Message: DBST002E.
Reason:
A DBIO error has occurred. The area indicated was the last oneprocessed successfully before the error occurred.
Action:
The action required depends on interpretation of the DBIO error code given in Message: DBST002E.
Reason:
A DBIO error has occurred. The set indicated was being processedwhen the error occurred.
Action:
The action required depends on interpretation of the DBIO error code given in Message: DBST002E.
Reason:
A DBIO error has occurred. The record indicated was beingprocessed when the error occurred.
Action:
The action required depends on interpretation of the DBIO error code given in Message: DBST002E.
Reason:
A DBIO error has occurred. The area indicated was being processed when the error occurred.
Action:
The action required depends on interpretation of the DBIO error code given in Message: DBST002E.
Reason:
A DBIO error has occurred. The value of the current db-key when the error occurred is indicated.
Action:
The action required depends on interpretation of the DBIO error code given in Message: DBST002E.
Reason:
A DBIO error has occurred. The value of the direct db-key when the error occurred is indicated.
Action:
The action required depends on interpretation of the DBIO error code given in Message: DBST002E.
DBIO Error Codes:
DBIO MAJOR ERROR STATUS CODES
GP = FIND/OBTAIN PAGE
PR = PAGE RETURN
DBIO MINOR ERROR STATUS CODES
A1 = New page returned
A2 = Function not supported
A3 = Invalid page range
A4 = Invalid qualifier
A5 = Page not current of transaction
A6 = Area not bound
A7 = Page return not on
A8 = Page return already on
A9 = Fast scan not on
B1 = Fast scan already on
B2 = SR4 chain error
B3 = SR2/SR3 chain error
B4 = HDR/FTR page number mismatch
B5 = Error closing file
B6 = Record not logically deleted
B7 = SMP currency error with page return on
B8 = Bad 'line space used' length in footer
B9 = No space in page
C1 = Duplicate DBKEY
C2 = Invalid Store
C3 = Skipped index
C4 = Broken chain
C5 = IXDET member of multiple sets
C6 = Ignored page reserve
C7 = Invalid record length. Discrepancy in RDW lengths encountered
during attempt to MODIFY RECORD. Run CLEANUP utility to remove
LDELs from all areas to be processed by REORG.
C8 = DMCL/SCHEMA CA IDMS release mismatch
C9 = Decompress error
D1 = Invalid record length
D3 = FSTRIGGER not less than FSBUFFER, or FSTRIGGER equal to 0
D4 = Invalid page displacement
D5 = Invalid request
D7 = GSDTPARM cannot be loaded
D8 = Record not found in PSUB
D9 = Segment names in the DBNAME table entry is mismatched with
current DMCL
DA = DBNAME not valid or segment name cannot be used as DBNAME
Minor return codes prefixed with an I to indicate an internal error:
I1 = Invalid parameter list
I2 = Function not supported
I3 = File already open/closed
I4 = Insufficient work space--record read is larger
than subschema description
I5 = Invalid currency data
I6 = VSAM block error
I7 = Bad fast scan DMCL block
I8 = file not assigned
Reason:
An attempt was made to ready an area with a different page group to those areas already readied.
Action:
CA IDMS/DB Reorg cannot be run against a subschema that contains mixed page groups.
Reason:
An unrecoverable error condition has been detected by USRDEXT.
Action:
Contact Computer Associates Product Support.
Reason:
The number of records read from the IIXEXOL file.
Action:
None.
Reason:
The number of records written to the IIXEXTR file.
Action:
None.
Reason:
The number of records read from the IIXSRKY file.
Action:
None.
Reason:
The number of records written to the IIXSRKY file.
Action:
None.
Reason:
The allocation extract file was created by CA IDMS/DB Reorg, but has been corrupted.
Action:
Verify that the allocation extract file (IIXEXOL) is valid and resubmit the job.
Reason:
The specified module cannot be called because of an internal error.
Action:
Contact Computer Associates, Inc. Product Support.
Reason:
The specified program cannot be located in the available library.
Action:
Locate the library that contains the module and make it availableto the job. Resubmit the job.
Reason:
The specified program cannot be loaded because of insufficient region size.
Action:
Increase the region size and resubmit the job.
Reason:
An internal error has been detected.
Action:
Contact Computer Associates Product Support.
Reason:
The file handler is unable to open the file.
Action:
See the tables in Return Codes for an explanation and appropriate action for the return codes indicated.
Reason:
The file handler is unable to read the file.
Action:
See the tables in Return Codes for an explanation and appropriate action for the return codes indicated.
Reason:
The file handler is unable to write to the file.
Action:
See the tables in Return Codes for an explanation and appropriate action for the return codes indicated.
Reason:
The file handler is unable to update the file.
Action:
See the tables in Return Codes for an explanation and appropriate action for the return codes indicated.
Reason:
The file handler is unable to close the file.
Action:
See the tables in Return Codes for an explanation and appropriate action for the return codes indicated.
Reason:
The indicated file is not a VSAM file. The message is preceded by asystem message indicating an open error for a VSAM file. If the attempt to open the file for QSAM processing is successful, CA IDMS/DB Reorg will continue with normal processing.
Note: The CA IDMS/DB Reorg file PAGUTIL needs direct access, either VSAM or BDAM.
Action:
None.
Reason:
Message table module does not contain an entry with the named message-id.
Action:
Contact Computer Associates Product Support.
Reason:
Module cannot be located in the available load or core-imagelibraries.
Action:
Locate the load or core-image library that contains module and make it available to the job.
Reason:
Module cannot be loaded due to insufficient GETVIS area (VSE/ESAonly).
Action:
Resubmit the job with a smaller SIZE= parameter or run with a larger partition.
Reason:
An internal processing error has been detected while processing thenamed message table.
Action:
Contact Computer Associates Product Support.
Reason:
An internal processing error has been detected by the message tableprocessor.
Action:
Contact Computer Associates Product Support.
Reason:
An unrecoverable error condition has been detected by USRMTCH.
Action:
Contact Computer Associates Product Support.
Reason:
The number of allocation extract records read from the EXTRACT,PRIREAL, and SECREAL files.
Action:
None.
Reason:
The number of allocation extract records written.
Action:
None.
Reason:
The number of IIXEXOL records written.
Action:
None.
Reason:
The allocation extract file was not created by CA IDMS/DB Reorg, or it isa legitimate file that has been corrupted.
Action:
Verify that the allocation extract file is valid. The allocation extract file consists of the EXTRACT, PRIREAL, and SECREAL files, sorted on first six bytes.
Reason:
Action:
Reason:
The allocation extract file was created by CA IDMS/DB Reorg, but has been corrupted.
Action:
Verify that the allocation extract file (EXTRACT, PRIREAL, and SECREAL files) is valid and resubmit the job.
Reason:
An extract record on either of the EXTRACT, PRIREAL, or SECREAL input files contains a set-ID that does not match to any subschema set-ID's.
Action:
Contact Computer Associates Product Support.
Reason:
The major keyword underscored by asterisks (*******) in the AuditReport is misspelled or is in error and cannot be processed.
Action:
Correct the spelling of the keyword and resubmit the job.
Reason:
The minor keyword underscored by asterisks (*******) in the AuditReport has already been entered on the parameter statement underscored.
Action:
Delete the duplicate minor keyword phrase and resubmit the job.
Reason:
The required equal sign and value after the keyword are missing.
Action:
Enter an equal sign followed by an appropriate value at thelocation underscored by an asterisk (*) in the Audit Report and resubmit the job.
Reason:
A set of open and closed parentheses is required.
Action:
Enter a right parenthesis to enclose the phrase or list, thenresubmit the job.
Reason:
The last phrase on this statement is a list enclosed in parenthesesthat ends with a comma. However, the next statement entered does not continue the list.
Action:
Supply a continuation card and resubmit the job.
Reason:
The previous statement ended with a comma, but this statementbegins with a major keyword.
Action:
Supply a continuation card and resubmit the job.
Reason:
You supplied more than 500 record types and/or record names in thepriority list.
Action:
Correct and resubmit.
Reason:
Value underscored by an asterisk (*) in the Audit Report isincorrect for the keyword.
Action:
Supply the appropriate value specified in the message and resubmit the job.
Reason:
Each keyword phrase must be separated by a comma.
Action:
Supply a comma at the location underscored by an asterisk (*)in the Audit Report and resubmit the job.
Reason:
The minor keyword underscored by asterisks (*******) in the AuditReport is misspelled or is in error and was not processed.
Action:
Correct the spelling of the minor keyword and resubmit the job.
Reason:
A minor keyword was omitted at the location underscored by anasterisk (*) in the Audit Report.
Action:
Enter the missing minor keyword and resubmit the job.
Reason:
The minor keyword(s) listed in the message was omitted. CA IDMS/DB Reorgcannot continue processing unless the keyword(s) shown is entered.
Action:
Supply the missing keyword(s) and resubmit the job.
Reason:
A keyword was entered without a value. The variable portion of theerror message lists the acceptable values.
Action:
Enter the correct value at the location underscored by an asterisk (*) in the Audit Report and resubmit the job.
Reason:
The value underscored by asterisks (****) on the Audit Report was already entered in the list. CA IDMS/DB Reorg cannot process this parameter unless you supply two different values.
Action:
Correct the value and resubmit the job.
Reason:
The value underscored by asterisks (******) on the Audit Report must be in ascending numerical sequence from the previous value in the list.
Action:
Rearrange the values in the list in ascending sequence and resubmit the job.
Reason:
The value underscored by asterisks (*******) on the Audit Report must be in descending numerical sequence from the previous value in the list.
Action:
Rearrange the values in the list in descending sequence and resubmit the job.
Reason:
A list or sublist cannot be empty. It must contain at least one valid record type or record name.
Action:
Insert one or more record types or record names in the PRIORITY statement at the location underscored by an asterisk (*) in the Audit Report.
Reason:
You supplied more than 10 record types and/or record names in a single, second-level-priority list. The eleventh entry is underscored by an asterisk (*) in the Audit Report.
Action:
Break the second-level-priority list into several second-level-priority lists and resubmit the job.
Reason:
An internal error has been detected.
Action:
Contact Computer Associates Product Support.
Reason:
Module call processor error occurred.
Action:
Possible return codes are:
Reason:
Module load processor error occurred.
Action:
Contact Computer Associates Product Support.
Reason:
Error occurred during call of printer module.
Action:
Contact Computer Associates Product Support.
Reason:
A JCL DD card must be supplied.
Action:
Correct the JCL and resubmit the job.
Reason:
An ASSGN card must be supplied.
Action:
Correct the JCL and resubmit the job.
Reason:
A parameter file with an LRECL other than 80 was supplied.
Action:
Create a parameter file with an LRECL of 80 and resubmit the job.
Reason:
The file handler is unable to open the file.
Action:
See the tables in Return Codes for an explanation and appropriate action for the indicated return codes.
Reason:
The file handler is unable to read the file.
Action:
See the tables in Return Codes for an explanation and appropriate action for the indicated return codes.
Reason:
The file handler is unable to close the file.
Action:
See the tables in Return Codes for an explanation and appropriate action for the indicated return codes.
Reason:
Because of a previous error, the phrase(s) underscored by the capital letter X in the Audit Report has not been processed.
Action:
None.
Reason:
Because of a previous error, the value(s) underscored by the capital letter X in the Audit Report has not been processed.
Action:
None.
Reason:
An CA IDMS/DB Reorg input parameter statement has been read. The entire80-byte image is displayed. Columns 1-72 will be processed.
Action:
None.
Reason:
The parameter statement continues a previous statement entered.
Action:
None.
Reason:
The parameter statement contains an asterisk (*) as the first non-blank character. The asterisk indicates that this is a comment statement, and it will not be processed.
Action:
None.
Reason:
All parameters that were entered have been read and processed by CA IDMS/DB Reorg.
Action:
None.
Reason:
The parameter statement contains blanks in columns 1-72 and will not be processed.
Action:
None.
Reason:
A value was entered that contains an odd number of apostrophes.Literal values must begin and end with single apostrophes. To represent a single apostrophe within a literal, you must enter two apostrophes. The variable portion of the error message lists the acceptable values.
Action:
Correct the value underscored by asterisks (****) and resubmit the job.
Reason:
A literal value was entered with improperly placed apostrophes.Literal values must begin and end with single apostrophes. To represent a single apostrophe within a literal, you must enter two apostrophes. The variable portion of the error message lists the acceptable values.
Action:
Correct the value underscored by asterisks (****) and resubmit the job.
Reason:
The release numbers of CA IDMS/DB Reorg's main program (USREORG) and USRNLYZ do not match. This error occurs if a new release of CA IDMS/DB Reorg is partially installed over a prior release, or if two releases of CA IDMS/DB Reorg are present and the available load or core-image libraries caused mixed releases of the program modules to be used.
Action:
Verify that CA IDMS/DB Reorg is correctly installed and that the proper load or core-image libraries are used. Resubmit the job.
Reason:
An unrecoverable error condition has been detected.
Action:
Contact Computer Associates Product Support.
Reason:
You requested a NOSWEEP for an area containing a record owning a multi-member set that also has a member record in a NOSWEEP area.
Action:
Remove the NOSWEEP parameter statement for the area and resubmit the job.
Reason:
The subschema does not have a description of the record.
Action:
Correct the subschema and resubmit the job.
Reason:
The Analysis Reports have been completed.
Action:
None.
Reason:
Size information.
Action:
None.
Reason:
Size information
Action:
None.
Reason:
Size information
Action:
None.
Reason:
Size information.
Action:
None.
Reason:
Subschema compile information.
Action:
None.
Reason:
Size information.
Action:
None.
Reason:
Size information
Action:
None.
Reason:
The OR52 subschema control block, for the indicated index set, points to an AM57 subschema control block whose page ranges do not correspond to any AC56 page ranges in the subschema.
Action:
Contact Computer Associates Product Support. To verify the page ranges, you can browse the subschema load module to find the OR52 control block for the indicated set. The last fullword in the OR52 indicates the offset to the AM57. The HI-LO page ranges are in the fifth and sixth full words of the AM57. Compare these page ranges to the page ranges in the AC56 control blocks.
Reason:
The number of records obtained through area sweeps.
Action:
None.
Reason:
The number of records obtained through set walks.
Action:
None.
Reason:
The number of EXTRACT records written.
Action:
None.
Reason:
The number of PRIOPTA records written.
Action:
None.
Reason:
The number of SECOPTA records written.
Action:
None.
Reason:
The release numbers of CA IDMS/DB Reorg's main program (USREORG) and USROPTX do not match. This error occurs if a new release of CA IDMS/DB Reorg is partially installed over a prior release, or if two releases of CA IDMS/DB Reorg are present and the available load or core-image libraries cause mixed releases of the program modules to be used.
Action:
Verify that CA IDMS/DB Reorg is correctly installed and that the proper load or core-image libraries are used. Resubmit the job.
Reason:
An unrecoverable error condition has been detected.
Action:
Contact Computer Associates Product Support.
Reason:
CALC record cannot be stored on suggested page because page number returned is outside record type's page range.
Action:
If GSSCALC was relinked to include IDMSCLCX, validate that link executed correctly. Validate also that IDMSCLCX routine is returning valid page numbers. If no problems exist, call Computer Associates Product Support.
Reason:
The number of bottom level records for IIX sorted db-keys with duplicate symbolic keys.
Action:
Use this figure in the calculation of the space needed for the IIXEXOL and IIXEXTR work files.
Reason:
The number of records that will be created for the IIXSRKY work file.
Action:
Use the number of records to estimate the space needed for the IIXSRKY work file.
Reason:
The number of IIX sorted db-key containing duplicates that point to upper levels.
Action:
Use the number in the calculation to estimate space needed for the IIXEXOL and IIXEXTR files.
Reason:
CA IDMS/DB Reorg found an area containing integrated index sets sorted by db-key. The IIXDBK step will be executed.
Action:
You must allocate space for the work files IIXEXOL, IIXSRKY, and SPFEXTR. See Overview.
Reason:
While sweeping the old database CA IDMS/DB Reorg encountered an SR7 record whose name (or CALC key) does not match any set name in any OR52 in the subschema.
Action:
Check the database to be sure it is correct. Ensure that the old subschema contain a definition for set-name.
Reason:
The OR52 subschema control block, for the indicated index set, points to an AM57 subschema control block whose page ranges do not correspond to any AC56 page ranges in the subschema.
Action:
Contact Computer Associates Product Support. To verify the page ranges, you can browse the subschema load module to find the OR52 control block for the indicated set. The last fullword in the OR52 indicates the offset to the AM57. The HI-LO page ranges are in the fifth and sixth fullwords of the AM57. Compare these page ranges to the page ranges in the AC56 control blocks.
Reason:
The indicated record or set has a page range of one page and that page is a space management page. The record or set cannot be stored.
Action:
Modify the schema to increase the page range.
Reason:
The indicated record was retrieved while walking the indicated SR8 set, but the record is not defined as a member of the set.
Action:
Contact Computer Associates Product Support.
Reason:
Decompression of symbolic keys in an SR8 record required more buffer space than is available.
Action:
Check whether the SR8 records are correct. Contact Computer Associates Product Support.
Reason:
The number of the target page for an SR8 record does not fall within the page range of the owner of the indicated integrated index set.
Action:
Contact Computer Associates Product Support.
Reason:
While performing an area sweep, these records were encountered on the old database.
Action:
Proceed with the reorganization and these records will be eliminated from the new database, or begin the job again,providing an OLD SUBSCHEMA that defines these records.
If the record is a member of the CALC set, nnn will be twice as large as the actual number of record occurrences on the database.
Reason:
PROCESS statement keywords RPT or RESTART cause all following statements to be ignored.
Action:
None.
Reason:
The RESTART parameter is being used with the RPT parameter in the same run.
Action:
Initiate another run of CA IDMS/DB Reorg using either the RPT parameter or the RESTART parameter.
Reason:
An unrecoverable error condition has been detected. When the module name is GSDBLDP, possible error codes are:
100--Unable to build DMCL
104--Unable to load subschema
108--Unable to obtain storage for PSUB
2xx--GSSCALL error xx=CALLRC. See NKWP051E.
Action:
Correct the situation or contact Computer Associates Product Support.
Reason:
More than one PROCESS statement was found in file SYSIPT. Only one PROCESS statement is allowed.
Action:
Correct and resubmit the job.
Reason:
CA IDMS/DB Reorg did not find a valid PROCESS parameter statement in file SYSIPT.
Action:
A valid PROCESS statement is required and must be the first parameter statement in file SYSIPT. Correct and resubmit the job.
Reason:
CA IDMS/DB Reorg did not find a valid COPY parameter statement in file SYSIPT.
Action:
At least one valid COPY parameter statement must be given in file SYSIPT. Correct and resubmit the job.
Reason:
Member loaded is not a subschema. If subschema name is correct,then the subschema has been corrupted in the load or core-image library.
Action:
Verify subschema name. If subschema has been corrupted, then recreate it and resubmit the job.
Reason:
Member loaded for DMCL of subschema is invalid. If DMCL name iscorrect, the DMCL has been corrupted in the load or core-image library.
Action:
Verify subschema name. If DMCL has been corrupted, recreate it and resubmit the job.
Reason:
There is insufficient storage for CA IDMS/DB Reorg to execute.
Action:
Under VSE/ESA, use a larger partition or a smaller SIZE=parameter. Under z/OS or OS/390, use a larger REGION. Resubmit the job.
Reason:
The subschema name from the parameter input file and the control file of a previous run must be the same. When this error occurs, it is likely that the wrong parameter input or control file from a previous run is being used.
Action:
Verify that parameter input and control files are correct. Verify that the load module core image library name and the CSECT name of the subschema are equal. Resubmit the job.
Reason:
An attempt was made to restart CA IDMS/DB Reorg after it finished executing.
Action:
None.
Reason:
The step name specified in not a valid CA IDMS/DB Reorg step.
Action:
Correct the step name and resubmit the job.
Reason:
CA IDMS/DB Reorg has not completed all steps prior to the one specified by the RESTART parameter.
Action:
Specify a step for RESTART that has completed processing in a prior run or the step that immediately follows the last step processed in a prior run.
Reason:
The specified NOSWEEP area only exists within one of thesubschemas.
Action:
NOSWEEP can only be specified for areas that exist in both the old and new subschemas. Correct and resubmit the job.
Reason:
The specified NOSWEEP area does not have set linkage with any COPY areas.
Action:
A NOSWEEP parameter statement is not necessary for an area that does not have set linkage to at least one COPY area. Correct and resubmit the job.
Reason:
Action:
The specified set must exist with the same participating records in both old and new subschemas. Correct and resubmit the job.
Reason:
Specified db-key displacements for a given record type did not match between the old and new subschemas.
Action:
Db-key displacements for member and owner records must match between the old and new subschemas. Correct and resubmit the job.
Reason:
Member of the set designated does not exist in both the old and new subschemas.
Action:
Member of the set must exist in both the old and new subschemas. Correct and resubmit the job.
Reason:
The record exists in only one subschema.
Action:
Verify the subschemas. Correct and resubmit the job.
Reason:
The record indicated does not reside in the same area in both the old and new subschemas. Both areas must be copied to move the record to a different area.
Action:
Supply a copy statement for the additional area indicated in the message and resubmit the job.
Reason:
The step specified in the STOP AFTER parameter is processed before the step specified in the RESTART parameter.
Action:
Change the incorrect STOP AFTER or RESTART value. Resubmit the job.
Reason:
Record-name records for index set are missing.
Action:
Correct this condition and resubmit the job.
Reason:
An area was specified in a COPY or NOSWEEP statement that does not exist in both the old and the new subschemas.
Action:
Correct this condition and resubmit the job.
Reason:
The same area cannot be specified in two copy statements.
Action:
Correct the input parameters and resubmit the job.
Reason:
For NOSWEEP or COPY, this parameter statement has already been given for this area.
Action:
Remove the conflicting NOSWEEP or COPY parameter statement. Resubmit the job.
Reason:
The COPY statement PRIORITY parameter specifies a record that does not reside in the area named in the copy statement area parameter for the subschema named.
Action:
Correct the record name. Resubmit the job.
Reason:
A COPY statement and a NOSWEEP statement specify the same area.
Action:
Remove the conflicting NOSWEEP or COPY parameter statement.Resubmit the job.
Reason:
The COPY statement PAGE RESERVE parameter specifies a value that is too large.
Action:
Correct the PAGE RESERVE value. Resubmit the job.
Reason:
The parameter statement just processed did not contain any errors.
Action:
None.
Reason:
The parameter statement just processed contained one or more errors.
Action:
None.
Reason:
An unrecoverable error condition has been detected.
Action:
Contact Computer Associates Product Support.
Reason:
File SYSIPT was empty.
Action:
Place parameter statements in file SYSIPT. Resubmit the job.
Reason:
The named IIX index set resides within a COPY area for only one of the subschemas.
Action:
Give a COPY parameter statement to resolve the error condition. Resubmit the job.
Reason:
The named record had its location mode changed. The named areas must be copy areas.
Action:
Give two COPY parameter statements to resolve the error condition. Resubmit the job.
Reason:
The named record had its location mode changed. The named area must be a copy area.
Action:
Give a COPY parameter statement to resolve the error condition. Resubmit the job.
Reason:
The record indicated had its format and/or length changed from the old subschema to new subschema. Additionally, for a variable length record, the control length may have changed. This type of change is a restructure and is not supported.
Action:
Correct this condition and resubmit the job.
Reason:
The subschema specified in the PROCESS statement has a format or content error.
Action:
Correct the subschema or verify its name in the PROCESS statement and resubmit the job.
Reason:
The current release of CA IDMS/DB Reorg does not support the processing of native VSAM files.
Action:
Create a subschema (NEW or OLD) which does not include native VSAM files and resubmit the job using the changed subschema.
Reason:
A requested reorganization cannot be executed because a privacy lock is active for the named area, set, or record.
Action:
Create a subschema without a privacy lock and make it available to CA IDMS/DB Reorg. Resubmit the job.
Reason:
The indicated record is a member or an owner of sets that are not defined in the new subschema.
Action:
Define a subschema that includes all sets in which the records participate. After making the necessary changes, resubmit the job.
Reason:
Both DSPLYINT=NO and the INFOROUTE or REPLYROUTE parameter were specified.
Action:
Specify another option for DSPLYINT or delete the INFOROUTE and/or REPLYROUTE.
Reason:
A class 11 route code was specified. Class 11 is not acceptable because it only allows display of information and does not allow the operator to reply.
Action:
Specify a route code that allows the operator to reply.
Reason:
The indicated record is defined with a MINIMUM FRAGMENT clause, but does not have an OCCURS DEPENDING ON clause.
Action:
Remove the FRAGMENT clause from the new subschema or add an OCCURS DEPENDING ON clause.
Reason:
The old and new subschemas do not correspond.
Action:
Define the index set in either the old or the new subschema as required.
Reason:
The member record is inconsistent between the old and new subschema.
Action:
Change the member record in either the old or the new subschema to match the other.
Reason:
Index set names are inconsistent between the old and new subschema.
Action:
Change the index set name in either the old or the new subschema to match the other.
Reason:
The indicated area was designated NOSWEEP and it contains records that are linked (as members) to an SR8 set in a copy area.
Action:
Remove the NOSWEEP statement for the indicated area. Resubmit the job.
Reason:
The OR52 subschema control block, for the indicated index set, points to an AM57 subschema control block whose page ranges do not correspond to any AC56 page ranges in the subschema.
Action:
Contact Computer Associates Product Support. To verify the page ranges, you can browse the subschema load module to find the OR52 control block for the indicated set. The last fullword in the OR52 indicates the offset to the AM57. The HI-LO page ranges are in the fifth and sixth fullwords of the AM57. Compare these page ranges to the page ranges in the AC56 control blocks.
Reason:
The integrated index set owner was found in a copy area in one subschema, but not in the other subschema.
Action:
Add another COPY statement that includes the area containing the integrated index in the other subschema.
Reason:
Unsupported function.
Action:
The DSPLYINT parameter is not functional in a VM/ESA environment.
Reason:
The SET(S) this record participates in is not defined in the noted subschema.
Action:
Add the SETS(S) to the appropriate subschema.
Reason:
Invalid user work area size passed in call to GSDBLDP.
Action:
Size must be from 64 to 256 inclusive
Reason:
An area was specified in the subschema which was not found in the DMCL.
Action:
Use a DMCL that contains all areas in the subschema.
Reason:
CA IDMS/DB Reorg does not currently support SQL databases.
Action:
Do not run an CA IDMS/DB Reorg against an SQL database.
Reason:
The BLOCKNUM parameter which specifies the blocking factor for the CNTRL1, CNTRL2, and PAGUTIL work files must be in the range from 1 to 32.
Action:
Correct the BLOCKNUM value and re-run the job.
Reason:
The BLOCKNUM parameter specified in a RESTART run must match that from the previous run.
Action:
Correct the BLOCKNUM value and re-run the job.
Reason:
The FSBUFFER parameter was included on the PROCESS statement. This is no longer valid. It has been replace by the SYSIDMS prefetch capability.
Action:
None- the parameter is ignored.
Reason:
An unrecoverable error condition has been detected.
Action:
Contact Computer Associates Product Support.
Reason:
The number of PRIOPTA records that have been read.
Action:
None.
Reason:
The number of PRIREAL records written.
Action:
None.
Reason:
The number of UNALLOC records written.
Action:
None.
Reason:
The number of PAGUTIL records written.
Action:
None.
Reason:
The number of PAGUTIL records updated.
Action:
None.
Reason:
The PRIOPTA file was not created by CA IDMS/DB Reorg or it is a legitimate file that has been corrupted.
Action:
Verify that the PRIOPTA file is from the present run. Resubmit the job.
Reason:
The record-ID does not exist in the subschema designated.
Action:
Correct the subschema or verify its name in the PROCESS statement and resubmit the job.
Reason:
PRIOPTA contains the record defined as CALC but the program is unable to locate its CALC set.
Action:
Correct the subschema or verify its name in the PROCESS statement and resubmit the job.
Reason:
The location mode of the record is being changed from VIA to CALC with a DUPLICATES NOT ALLOWED option, but duplicate symbolic keys exist in the old database.
Action:
Eliminate duplicates for the record or redefine the record with DUPLICATES ALLOWED option in the new subschema and resubmit the job. CA IDMS/DB Reorg cannot delete records from the database.
Reason:
An SR7 was obtained whose set name (or CALC key) does not match any set name in the OR52 subschema control blocks in the subschema.
Action:
Contact Computer Associates Product Support.
Reason:
The OR52 subschema control block, for the indicated index set, points to an AM57 subschema control block whose page ranges do not correspond to any AC56 page ranges in the subschema.
Action:
Contact Computer Associates Product Support. To verify the page ranges, you can browse the subschema load module to find the OR52 control block for the indicated set. The last fullword in the OR52 indicates the offset to the AM57. The HI-LO page ranges are in the fifth and sixth fullwords of the AM57. Compare these page ranges to the page ranges in the AC56 control blocks.
Reason:
An unrecoverable error condition has been detected.
Action:
Contact Computer Associates Product Support.
Reason:
CA IDMS/DB Reorg subschema and step status information for the RESTART parameter.
Action:
None.
Reason:
GSSCALL experienced a problem invoking GSSPRINT.
Action:
Ensure all necessary programs are available in your steplib or LIBDEF.
Reason:
The CA IDMS/DB Reorg step where you should continue processing after interrupting CA IDMS/DB Reorg.
Action:
None.
Reason:
CA IDMS/DB Reorg file status information for RESTART parameter.
Action:
None.
Reason:
An unrecoverable error condition has been detected.
Action:
Contact Computer Associates Product Support.
Reason:
There is insufficient storage for CA IDMS/DB Reorg to execute. The amountof storage requested was n bytes.
Action:
Under VSE/ESA, use a larger partition or smaller SIZE= parameter. Under z/OS or OS/390, use a larger REGION. Resubmit the job.
Reason:
The integrity of CNTRL1/CNTRL2 files has been compromised.
Action:
Contact Computer Associates Product Support.
Reason:
The integrity of CNTRL1/CNTRL2 files has been compromised.
Action:
Contact Computer Associates Product Support.
Reason:
Control file-1 could not be read successfully, so backup control file-2 will be tried.
Action:
None.
Reason:
Control file designated could not be read successfully.
Action:
None.
Reason:
Control file designated was successfully processed by USRRCTL.
Action:
None.
Reason:
An unrecoverable error condition has been detected.
Action:
Contact Computer Associates Product Support.
Reason:
USREORG is unable to call this module due to internal error.
Action:
Contact Computer Associates Product Support.
Reason:
Module cannot be located in the available load or core image libraries.
Action:
Locate the load or core image library that contains the module and make it available to the job. Resubmit the job.
Reason:
The module cannot be loaded due to insufficient GETVIS area (VSE/ESA only).
Action:
Resubmit the job with a smaller SIZE= parameter. A larger partition may also be required.
Reason:
An unrecoverable error condition has been detected.
Action:
Contact Computer Associates Product Support.
Reason:
An unrecoverable error condition has been detected.
Action:
Contact Computer Associates Product Support.
Reason:
The module cannot be located in the available load or core image libraries.
Action:
Locate the load or core image library that contains the module and make it available to the job. Resubmit the job.
Reason:
Module cannot be loaded due to insufficient GETVIS area (VSE/ESA only).
Action:
Resubmit the job with a smaller SIZE= parameter. A larger partition may also be required.
Reason:
The call to the installation-provided sort program failed with anon-zero return code.
Action:
See your installation's sort program documentation for an explanation of the return code and any other sort program messages. Correct and resubmit the job.
Reason:
GSSFILE failed while processing the input file. This error could also be caused by incorrect JCL.
Action:
Verify that the JCL is appropriate and resubmit the job. If no JCL or other user errors can be found, report the error to Computer Associates Product Support.
Reason:
Module detected an error. The error was reported in the preceding message.
Action:
Verify that the JCL is appropriate and resubmit the job. If no JCL or other user errors can be found, report the error to Computer Associates Product Support.
Reason:
The current step was bypassed because it was not needed.
Action:
None.
Reason:
The database reorganization process is complete.
Action:
None.
Reason:
An unrecoverable error condition has been detected.
Action:
Contact Computer Associates Product Support.
Reason:
An unrecoverable error condition has been detected.
Action:
Contact Computer Associates Product Support.
Reason:
The sum of the SECOPTA and UNALLOC records read.
Action:
None.
Reason:
The number of SECREAL records written.
Action:
None.
Reason:
The number of PAGUTIL records read.
Action:
None.
Reason:
The number of PAGUTIL records written.
Action:
None.
Reason:
The number of PAGUTIL records updated.
Action:
None.
Reason:
Secondary allocation file was not created by CA IDMS/DB Reorg, or it is alegitimate file that has been corrupted.
Action:
Verify that the secondary allocation file is valid. The secondary allocation file consists of the SECOPTA and UNALLOC files. Resubmit the job.
Reason:
The record-ID is not defined in the subschema designated. Probable cause is a CNTRL1/CNTRL2 file that has been corrupted.
Action:
Correct this condition and resubmit the job.
Reason:
The area is full.
Action:
Correct this condition by creating adequate space in the new subschema for the area indicated, by decreasing the page reserve parameter value, by redistributing records to other areas, or by using a combination of these techniques. Resubmit the job.
Reason:
The area is full. The number of bytes targeted to the area is greater than the allocated space.
Action:
Correct this condition by creating adequate space in the new subschema for the area indicated by allocating more space to the area, by redistributing records to other areas, or by using a combination of these methods. The situation arises when attempting to allocate space for the named record above. This record cannot be fragmented.
Reason:
This area is full.
Action:
Correct this condition by creating adequate space in the new subschema for the area indicated, by decreasing the page reserve parameter value, by redistributing records to other areas, or by using a combination of these techniques. Resubmit the job.
Reason:
No set record was found with the an ID that matches the ID found in the system-owned integrated index set.
Action:
Save the SNAP/dump and contact Computer Associates Product Support.
Reason:
CA IDMS/DB Reorg could not find an area containing the indicated index set.
Action:
Save the SNAP/dump and contact Computer Associates Product Support.
Reason:
The program encountered a serious logic flaw and could not continue.
Action:
Save the SNAP/dump and contact Computer Associates Product Support.
Reason:
An unrecoverable error condition has been detected.
Action:
Contact Computer Associates Product Support.
Reason:
The number of ALLOCX records read.
Action:
None.
Reason:
The number of DBREC records written.
Action:
None.
Reason:
The number of database records modified.
Action:
None.
Reason:
Records have been modified in the area indicated. The area was not specified in a copy statement.
Action:
None.
Reason:
An unrecoverable error condition has been detected.
Action:
Contact Computer Associates Product Support.
Reason:
CA IDMS statistics are reported following this message.
Action:
None.
Reason:
Statistics for the step are reported following the message.
Action:
None.
Reason:
An unrecoverable error condition has been detected.
Action:
Contact Computer Associates Product Support.
Reason:
The number of DBREC records read.
Action:
None.
Reason:
The number of database records stored.
Action:
None.
Reason:
The release numbers of CA IDMS/DB Reorg's main program (USREORG) and module-name do not match. This error occurs if a new release of CA IDMS/DB Reorg is partially installed over a prior release, or if two releases of CA IDMS/DB Reorg are present and the available load or core-image libraries cause mixed releases of the program modules to be used.
Action:
Verify that CA IDMS/DB Reorg is correctly installed and that the proper load or core-image libraries are used. Resubmit the job.
Reason:
The file designated was not created by CA IDMS/DB Reorg or it is a legitimate file that has been corrupted.
Action:
Verify that the file is valid. Resubmit the job.
Reason:
The file designated was created by CA IDMS/DB Reorg but is not to be used with this run of CA IDMS/DB Reorg.
Action:
Verify that the file is valid. Resubmit the job.
Reason:
The file indicated was created by CA IDMS/DB Reorg but appears to be corrupted with extraneous records.
Action:
Verify that the file is valid. Resubmit the job.
Reason:
The file is corrupt because of missing or extraneous records.
Action:
Verify that the file is valid and resubmit the job.
Reason:
Module indicated has received an invalid parameter list.
Action:
Contact Computer Associates Product Support.
Reason:
Module ended with the indicated return code.
Action:
Contact Computer Associates Product Support.
Reason:
See the message following this one on the Audit Report.
Action:
See the message following this one on the Audit Report.
Reason:
An unusual processing situation has occurred and the utility cannot continue.
Action:
Contact Computer Associates Product Support.
Reason:
The Console Communication Facility has been activated. CA IDMS/DB Reorgis ready to accept console requests.
Action:
Enter a console communication command if desired.
Reason:
A reply to WTOR000I was given but it did not contain a command.
Action:
Enter a console communication command.
Reason:
The value in the SET INTERVAL request is too large.
Action:
Enter a SET INTERVAL request in the range 0-120.
Reason:
The value in the SET INTERVAL request is too small.
Action:
Enter a SET INTERVAL request in the range 0-120.
Reason:
A reply to WTOR000I was given but it did not contain a valid command/operand.
Action:
Enter a console communication command with a valid command/operand.
Reason:
A SET INTERVAL REQUEST command was successfully processed.
Action:
None.
Reason:
The display interval could not be established by USRINTV. An ABEND or internal error may be the cause. In VSE/ESA, lack of timer support in the partition used by CA IDMS/DB Reorg could also cause the error.
Action:
If no user error can be found, contact Computer Associates Product Support.
Reason:
A SET INTERVAL command was successfully processed.
Action:
None.
Reason:
A SET INTERVAL STEP command was successfully processed.
Action:
None.
Reason:
A SET INTERVAL STEP command was issued and the interval timer was turned off by a previous SET INTERVAL console command or it was established through the DISPLAY parameter or a SET INTERVAL command.
Action:
Establish a timer display interval with the SET INTERVAL console command. (VSE/ESA installations only: If this message appears in the Audit Report at the end of the job, the interval timer ended before the interval established in the SET INTERVAL command. Contact Computer Associates Product Support.)
Reason:
The subtask designated has ended unexpectedly and the timer display cannot be reestablished once it has abended.
Action:
Contact Computer Associates Product Support.
Reason:
This message is displayed in response to a SET INTERVAL operator command.
Action:
None.
|
Copyright © 2014 CA.
All rights reserved.
|
|