Warning messages are suffixed by a nnnW message number and report on the following:
CA IDMS/DB Audit error messages are suffixed by an nnnE number and include possible causes for the message and action to be taken to correct the problem.
Reason:
The amount of available storage in the region or partition was not large enough for CA IDMS/DB Audit's pseudo subschema table or other work areas. The required number of contiguous bytes of storage is displayed.
Action:
See the "Operations" chapter for more details about CA IDMS/DB Audit storage requirements. Increase the GETMAIN/GETVIS area by changing the REGION/SIZE parameter on the EXEC statement or lower the SETLIMIT value so that less storage is required.
Reason:
Module USAT0010 was not link edited with CA IDMS/DB Audit. CA IDMS/DB Audit terminates processing.
Action:
Contact Computer Associates Product Support for assistance.
Reason:
An unrecognizable parameter value was returned by the keyword processor. CA IDMS/DB Audit terminates abnormally.
Action:
Contact Computer Associates Product Support for assistance.
Reason:
An input parameter statement containing a comma followed the last keyword phrase when end-of-file was reached on SYSIPT.
Action:
If continuation is desired, add an additional parameter statement to the parameter file.
If continuation is not desired, delete the comma after last keyword phrase. Resubmit the job.
Reason:
The first word in the parameter statement was not a major keyword.
Action:
Check parameter statement for misspelled keywords. Correct the keywords and resubmit the job.
Reason:
An unrecognizable major or minor keyword was detected.
Action:
Check parameter statement for misspelled or invalid keywords. Correct the keywords and resubmit the job.
Reason:
The designated keyword was incorrectly specified. Absence of a keyword will not invoke this message.
Action:
Check the parameter statement for correct parameter syntax. Correct the keyword and resubmit the job.
Reason:
Value for the designated keyword was smaller or larger than the value allowed.
Action:
Correct the keyword value and resubmit the job.
Reason:
PROCESS parameter not detected as first non-comment parameter statement. PROCESS keyword misspelled.
Action:
Check the parameter file and make sure the PROCESS statement is the first non-comment parameter statement. Correct spelling of the keyword and resubmit the job.
Reason:
More than one PROCESS, AUDIT, FIX or REPORTS parameter statement encountered. Multiple AREA parameters specifying identical area name encountered. Multiple RECORD parameters specifying identical record name encountered. Multiple SET parameters specifying identical set name encountered.
Action:
Delete all but one occurrence of multiple parameters and resubmit job. Delete extra parameter statements or change area, set, or record name on duplicate parameter statements. Resubmit the job.
Reason:
A required value was not entered for the designated keyword.
Action:
Specify a value for the keyword and resubmit the job.
Reason:
An invalid value was specified for the designated keyword.
Action:
Correct the keyword value and resubmit the job.
Reason:
A non-numeric value was specified for the designated keyword.
Action:
Correct the keyword value and resubmit the job.
Reason:
Auditing of the CALC set cannot be performed because a RECORD or SET statement, or both, contained NOACCESS.
Action:
Delete NOACCESS from RECORD and SET statements and resubmit the job.
Reason:
Auditing of CALC set cannot be performed because a RECORD statement contained NOSWEEP.
Action:
Delete NOSWEEP from the RECORD statement and resubmit the job.
Reason:
An AREA, RECORD, or SET statement was entered without also entering an AUDIT statement.
Action:
Enter an AUDIT statement and resubmit the job. If only fixing or reporting is to be performed, delete the AREA, RECORD, or SET statement.
Reason:
Incorrect subschema specified. Area name, record name, or set name was misspelled.
Action:
Check that the correct subschema was specified and that subschema name is spelled correctly. Resubmit job. Correct area name, record name, or set name and resubmit the job.
Reason:
The specified BEGIN or END page number in an AREA statement is outside the area page range or a null value was entered. An incorrect area name was entered in an AREA statement.
Action:
Correct the page number value and resubmit the job. Correct the area name and resubmit the job.
Reason:
The specified BEGIN page number is greater than the specified END page number in an AREA statement.
Action:
Correct the BEGIN and END page numbers and resubmit the job.
Reason:
A fix option was specified for a portion of the database for which there was no corresponding audit specified.
Action:
Correct the fix request and resubmit the job.
Reason:
Auditing cannot be performed because all areas in the subschema were designated NOACCESS in AREA parameter statements.
Action:
Delete NOACCESS from at least one AREA statement and resubmit the job.
Reason:
Auditing cannot be performed because all sets in the subschema were designated NOACCESS in either AREA, RECORD, or SET parameter statements.
Action:
Delete NOACCESS from the appropriate AREA, RECORD, or SET parameter statements and resubmit the job.
Reason:
The designated area cannot be audited because the area has a privacy lock of NO for Ready Exclusive Update or Ready Shared Retrieval.
Action:
Specify another subschema that allows the area to be readied in the appropriate mode and resubmit the job. Designate the area as NOACCESS using an AREA parameter statement and resubmit the job.
Reason:
The designated record cannot be audited because it has a privacy lock of NO for the DML command FIND or GET in the subschema being used.
Action:
Specify another subschema that allows FIND and GET for all records to be audited. Designate the record as NOACCESS, by using a RECORD parameter statement. Resubmit the job.
Reason:
The designated record cannot be fixed because it has a privacy lock of NO for the DML command MODIFY in the subschema being used.
Action:
Specify another subschema that allows MODIFY for all records to be audited. Designate the record as NOACCESS, by using a RECORD parameter statement during the audit phase. Rerun the audit and fix phases.
Reason:
When LDEL record fixing was requested, the designated record could not be fixed because it had a privacy lock of NO for the DML command ERASE in the subschema being used.
Action:
Specify another subschema that allows ERASE for all records to be audited. Designate the record as NOACCESS, BY using a RECORD parameter statement during the audit phase. Rerun the audit and fix phases.
Reason:
The indicated member record was not copied into subschema being used for the indicated set.
Action:
Specify another subschema that has copied the member record and resubmit the job. Designate the set as NOACCESS by using a SET statement and resubmit the job.
Reason:
The DISCONNECT option was specified for a record that was designated as NOACCESS in either an AREA or RECORD parameter statement.
Action:
Delete the DISCONNECT option and resubmit the job. Delete the NOACCESS option and resubmit the job.
Reason:
The DISCONNECT option was specified for a member record of a set designated as NOACCESS in either an AREA, RECORD, or SET statement.
Action:
Delete the DISCONNECT option and resubmit the job. Delete the NOACCESS option and resubmit the job.
Reason:
The DISCONNECT option was specified for a set designated as NOACCESS in either an AREA, RECORD, or SET statement.
Action:
Delete DISCONNECT option and resubmit the job. Delete the NOACCESS option and resubmit the job.
Reason:
The DISCONNECT option was specified in a RECORD statement for a record that is not a member of a set.
Action:
Delete the DISCONNECT option from the RECORD statement and resubmit the job.
Reason:
No options were specified in the AUDIT statement to indicate the type of auditing to be performed.
Action:
Add the desired options to the AUDIT statement and resubmit the job.
Reason:
DBKEYTBL and/or WALKNEXT was requested in an AUDIT statement without CALCSETS or USERSETS.
Action:
Add CALCSETS and/or USERSETS to the AUDIT statement and resubmit the job. Delete DBKEYTBL and WALKNEXT from the AUDIT statement and resubmit the job.
Reason:
No type of fixing was specified in the FIX statement.
Action:
Add the desired fix options to the FIX statement and resubmit the job.
Reason:
Fixing was requested using an extract file created by a previous audit job. The subschema name used by the audit phase, however, does not match the subschema name specified in the PROCESS statement of the fix phase.
Action:
Correct the subschema name in the PROCESS statement to match the subschema name in the extract file of the audit phase. Resubmit the job.
Reason:
Fix processing cannot be performed because of an irrecoverable error during the audit phase.
Action:
Review messages displayed during the audit phase and correct any errors. Rerun both the audit and fix phases.
Reason:
Fix processing cannot be performed because the STOPAFTER limit was exceeded during the audit phase.
Action:
Increase the value of STOPAFTER. Rerun both the audit and fix phases.
Reason:
Fix processing cannot be performed because the SETLIMIT value was exceeded during the audit phase.
Action:
If the DBKEYTBL option was not requested, a set loop condition may exist. Resubmit both the audit and fix phases requesting the DBKEYTBL option. If DBKEYTBL was requested, increase the value of SETLIMIT. Rerun both the audit and fix phases.
Reason:
CA IDMS/DB Audit could not successfully open the designated file. Processing is terminated.
Action:
Check that all file names are correctly spelled. Add the appropriate file name to the JCL. Resubmit the job.
Reason:
The audit phase that created the extract file was canceled before the header or trailer record was written. CA IDMS/DB Audit terminates processing. The file being read by the report or fix phase is not a CA IDMS/DB Audit extract file.
Action:
Rerun the audit and fix phases. Resubmit the job using the correct extract file.
Reason:
Extract files from multiple CA IDMS/DB Audit jobs were concatenated. CA IDMS/DB Audit terminates processing.
Action:
Resubmit the job using only one extract file.
Reason:
A non-zero error status was returned when a BIND RUN-UNIT command was issued. CA IDMS/DB Audit terminates processing.
Action:
See message 050I.
Reason:
A non-zero error status was returned when a BIND command for the designated record or page was issued. CA IDMS/DB Audit terminates processing.
Action:
See message 050I.
Reason:
A non-zero error status was returned when the indicated ready mode was invoked for the designated area. CA IDMS/DB Audit terminates processing.
Action:
See message 050I.
Reason:
A non-zero error status was returned after a FINISH command. CA IDMS/DB Audit terminates processing.
Action:
See message 050I.
Reason:
A non-zero error status was returned after an OBTAIN command for a first record, a next record, or a page within the area displayed with the preceding message I018. The db-key is displayed for the last record retrieved in the area, or the page number is displayed for the last page retrieved in the area sweep. If the record db-key or the page number equals HIGH-VALUES, an OBTAIN FIRST command was issued; otherwise, an OBTAIN NEXT command was issued. Message 050I follows this message.
Action:
See message 050I.
Reason:
A non-zero error status was returned after an OBTAIN command for a record or page. In the audit phase, CA IDMS/DB Audit terminates processing of the area or set occurrence. In the fix phase, CA IDMS/DB Audit terminates all processing. This situation may result when a valid dbkey is passed to IDMS but no data record is found at the location specified by the dbkey.
Action:
Audit phase--see message 050I. Fix phase--contact Computer Associates Product Support.
Reason:
A non-zero error status was returned when issuing a MODIFY command was issued during the fix phase. CA IDMS/DB Audit terminates.
Action:
Audit phase--see message 050I for the error status. Contact Computer Associates Product Support.
Reason:
A non-zero error status was returned when an ERASE command was issued during the fix phase. CA IDMS/DB Audit terminates.
Action:
Contact Computer Associates Product Support.
Note: If errors 050E, 051E, or 052E occur during fix phase, thedatabase must be restored to its state prior to running CA IDMS/DB Audit . A SNAP of appropriate CA IDMS/DB Audit work areas will automatically be produced. Contact Computer Associates Product Support for assistance.
Reason:
The STOPAFTER value was exceeded by one physical integrity error. CA IDMS/DB Audit terminates the audit phase.
Action:
Increase the STOPAFTER value and resubmit the job.
Reason:
The SETLIMIT value was exceeded for the designated set. CA IDMS/DB Audit terminates processing of the set occurrence.
Action:
If DBKEYTBL was not requested, a set loop may exist in the set occurrence. Resubmit the job requesting DBKEYTBL. If DBKEYTBL was requested, increase the SETLIMIT value. Resubmit the job.
Reason:
The SORT program returned a non-zero return code to the designated CA IDMS/DB Audit phase. An error was detected that makes execution of the phase impossible.
Action:
Review the SORT messages and correct the problem. Resubmit the job. Review the associated error message and correct the problem. Resubmit the job.
Reason:
CA IDMS/DB Audit has performed a partial area audit and one of the following conditions exists:
Action:
If Error 057E occurred during the fix phase, specify a BEGIN/END page range for the area that includes the owner of the indicated set, and rerun both the audit and fix phases. If the error occurred during the report phase, processing continues. The Before Images Report does not, however, accurately display the sets involved.
Reason:
One of the following conditions exists.
Action:
Reason:
The db-key of displayed record occurrence does not fall within the from/thru page range specified for record type.
Action:
None. CA IDMS/DB Audit cannot fix this type of error.
Note: This type of error does not affect the walking of a setoccurrence. It can, however, cause CALC records not to be found.
Reason:
During USERSETS auditing, the displayed record occurrence contained a next, prior, or owner db-key that is null.
Action:
Review associated messages and determine if fixing should be performed. Use the CA IDMS utility IDMSBCF, FIX PAGE function to display the page where the record resides and patch the bad page.
Reason:
During USERSETS/CALCSETS auditing, the displayed record occurrence contained either a next, prior, or owner db-key that did not point into any of the areas copied into the subschema.
Action:
Review associated messages to determine if fixing should be performed. Use the CA IDMS utility IDMSBCF, FIX PAGE function to display the page where the record resides and patch the bad page.
Reason:
During USERSETS/CALCSETS auditing, the displayed record occurrence contained either a next, prior, or owner db-key that pointed into an non-readied area of the subschema.
Action:
Review associated messages to determine if fixing should be performed. Use the CA IDMS utility IDMSBCF, FIX PAGE function to display the page where the record resides and patch the bad page.
Reason:
During CALCSETS auditing, the displayed record occurrence contained a next, prior, or owner db-key that is null. This error can occur if all CALC records have not been copied into the subschema being used. During USERSETS/CALCSETS auditing, the displayed record occurrence contained either a next, prior, or owner db-key that pointed to a non-existent record.
Action:
Be certain that all CALC records have been copied into the subschema being used. Review associated messages to determine if fixing should be performed. Use the CA IDMS utility IDMSBCF, FIX PAGE function to display the page where the record resides and patch the bad page.
Reason:
During USERSETS/CALCSETS auditing, the displayed record occurrence contained either a next, prior, or owner db-key that pointed to an invalid record type for the set.
Action:
Review associated messages to determine if fixing should be performed. Use the CA IDMS utility IDMSBCF, FIX PAGE function to display the page where the record resides and patch the bad page.
Reason:
When sorted in ascending order, the displayed record's sort key was less than the sort key of the prior record (of the same record type) in the set. When sorted in descending order, the displayed record's sort key was greater than the sort key of the prior record in the set.
Action:
Review the associated messages and determine if fixing should be performed.
Reason:
The displayed record's sort key was equal to the sort key of the prior record in a set where duplicates were not allowed.
Action:
None. CA IDMS/DB Audit cannot fix this type of error.
Reason:
Owner db-key of displayed record is invalid. Displayed record is member of another set occurrence pointed into by the current set occurrence.
Action:
Review associated messages and determine if fixing should be performed.
Reason:
When walking next in the set occurrence, the prior db-key of the displayed record did not match the db-key of the prior record in the set occurrence.
Action:
Review associated messages and determine if fixing should be performed.
Reason:
When walking prior in the set occurrence, the next db-key of the displayed record did not match the db-key of the next record in the set occurrence.
Action:
Review associated messages and determine if fixing should be performed.
Reason:
When walking either next or prior, a second owner record occurrence was detected in the set occurrence. This message can indicate a set occurrence that points into another set occurrence.
Action:
Review associated messages and determine if fixing should be performed.
Reason:
When walking either next or prior in a set occurrence, the designated db-key of the displayed record pointed to a member record previously retrieved, indicating a set loop condition.
Action:
Review associated messages and determine if fixing should be performed.
Reason:
All fragments of the record could not be successfully retrieved because of a bad SR4 chain pointer. The record is either variable length or compressed. (A compressed fixed length record is stored on the database as a variable length record. See message 080E.) The Record Descriptor Word (RDW) length could also erroneously indicate that there should be more fragments for the record while the last SR4 chain pointer points back to the root of the fragmented record indicating that there are no more fragments. Only the control portion of the record data is displayed.
Action:
Use the CA IDMS utility IDMSBCF, FIX PAGE to display the page where the designated record resides and patch the bad page.
Reason:
Processing was terminated because of a previous error.
Action:
Review all displayed error messages.
Reason:
The extract file used by the current fix/report phase was created by another CA IDMS/DB Audit job. The current subschema being used is not the same subschema as that used by the audit phase even though the subschema names match.
Action:
Check that the correct load/core image library is being used. Resubmit the job. If the problem recurs, save all output listings and contact Computer Associates Product Support for assistance.
Reason:
An irrecoverable internal error was detected by CA IDMS/DB Audit.
Action:
If CURRENCY/AREA-SWEEP is indicated, a page header may be invalid. Rerun, specifying AUDIT=PAGES. Otherwise, save all output listings and contact Computer Associates Product Support for assistance.
Reason:
The displayed record is a compressed record that could not be successfully decompressed because of errors detected within the compressed portion of the record. Improper decompression can cause a fragmented record to be improperly assembled. See message 072E.
Action:
Use the CA IDMS utility IDMSBCF, FIX PAGE to display the page where the designated record resides and patch the bad page.
Reason:
The amount of available storage in the region or partition was not large enough for CA IDMS/DB Audit to load the subschema or the DMCL named in the subschema, or both, into virtual storage.
Action:
See the "Operations" chapter for details about CA IDMS/DB Audit storage requirements. Increase the GETMAIN/GETVIS area by changing the REGION/SIZE parameter on the EXEC statement. Resubmit the job.
Reason:
The subschema and/or the DMCL named in the subschema resides in the load/core image libraries allocated to the job. CA IDMS/DB Audit has determined, however, that the subschema is not a valid subschema and/or the DMCL named in the subschema is not a valid DMCL.
Action:
Check the spelling of the subschema named in the PROCESS statement. Check that the correct load/core image libraries were allocated. Resubmit the job.
Reason:
DISCONNECT=EXPLICIT was specified on the AUDIT statement indicating that CA IDMS/DB Audit should audit for set disconnections of mandatory automatic or DISCONNECT member records. There are no records, however, that are to be audited that are mandatory automatic or specified as DISCONNECT.
Action:
Delete DISCONNECT=EXPLICIT from the AUDIT statement, or specify specific records or sets as DISCONNECT, and resubmit the job.
Reason:
DISCONNECT=NONE was specified in the AUDIT statement, indicating that CA IDMS/DB Audit should not audit for set disconnections. However, at least one RECORD or SET statement specified DISCONNECT, and CA IDMS/DB Audit terminated processing.
Action:
Specify DISCONNECT=EXPLICIT in the AUDIT statement. Delete DISCONNECT from all RECORD and SET statements. Resubmit the job.
Reason:
Retrieval mode and updating the database are mutually exclusive.
Action:
If you want to run in retrieval mode, change to FIX=SIMULATE. If you want to actually update the database, change to READYMODE=UPDATE. Resubmit the job.
Reason:
Date and time that SR8 auditing was terminated because of a processing error.
Action:
Review associated messages to determine the reason for termination.
Reason:
The record indicated by a db-key contained in an SR8 entry could not be found.
Action:
Use the CA IDMS utility IDMSBCF, FIX PAGE function to fix the SR8 record.
Reason:
The record indicated by a db-key contained in an SR8 entry was found, but it is not the correct record type for this integrated index set.
Action:
Use the CA IDMS utility IDMSBCF, FIX PAGE function to display the page where the record resides and patch the bad page.
Reason:
The record indicated by a db-key in an SR8 entry was found, but its page range is not within the page range indicated for that record type.
Action:
Use the CA IDMS utility IDMSBCF, FIX PAGE function to display the page where the record resides and patch the bad page.
Reason:
The record indicated by a db-key in an SR8 entry resides in an area that was not readied.
Action:
Remove the NOACCESS parameter for the area where the record resides. Resubmit the job.
Reason:
The orphan count in the SR8 record was not fixed because an invalid next pointer was detected when trying to decrease orphan counts. CA IDMS/DB Audit should have detected and already fixed this pointer.
Action:
Make sure the correct audit extract file is being used. Use the CA IDMS utility IDMSBCF, FIX PAGE function to correct the invalid next pointer in the SR8 record and fix the orphan counts.
Reason:
An error occurred during the execution of the indicated program.
Action:
Contact Computer Associates Product Support.
Reason:
The subschema specified in the PROCESS statement does not match the database. The database contains an SR7 record for a system owned integrated index set, but the subschema does not contain a definition for that set, nor does the subschema indicate that it is a partial description of the database. The subschema for CA IDMS/DB Audit must be created from a schema that has a complete description of the database.
Action:
Correct the subschema and resubmit the job.
Reason:
The sort program was unable to complete a sort.
Action:
Examine the related messages from your sort utility. See the list of return codes associated with the sort utility for appropriate action.
Reason:
CA IDMS/DB Audit was unable to read the indicated file.
Action:
See message 050I.
Reason:
CA IDMS/DB Audit was unable to write to the indicated file.
Action:
See message 050I.
Reason:
CA IDMS/DB Audit was unable to close the indicated file.
Action:
See message 050I.
Reason:
DISP=MOD on the index db-key work file (instead of DISP=OLD, DISP=SHR, or DISP=NEW) causes the output to be added to the existing file. This problem can occur if CA IDMS/DB Audit is run with two different subschemas.
Action:
Run CA IDMS/DB Audit with DISP=OLD, DISP=SHR, or DISP=NEW.
Reason:
The integrated index set cannot be audited because the set or a record of the set was specified NOACCESS in a RECORD or SET statement.
Action:
Delete INDEXES from the AUDIT parameter statement or delete the RECORD or SET statement that specifies NOACCESS. Resubmit the job.
Reason:
The integrated index set cannot be audited because the SR7 record is designated NOSWEEP in a RECORD parameter statement.
Action:
Delete INDEXES from the AUDIT parameter statement or delete the RECORD statement that specifies NOSWEEP for the SR7 record. Resubmit the job.
Reason:
In a top level SR8 record, the upper level pointer is not null (High-Values).
Action:
Use the CA IDMS utility IDMSBCF, FIX PAGE function to patch the upper level pointer.
Reason:
A module call processor error occurred.
Possible return codes are:
Action:
Contact Computer Associates Product Support.
Reason:
INDEXORPHANS was specified in the FIX statement. Because an invalid record type was encountered, the integrated index orphan count was not decreased.
Action:
Correct the invalid record. You can use the CA IDMS utility IDMSBCF, FIX PAGE function to decrease the orphan count.
Reason:
INDEXORPHANS was specified in the FIX statement. Because of an invalid pointer pointing out of the index set, orphan counts could not be completely decreased.
Action:
Fix the erroneous pointer by using the CA IDMS utility IDMSBCF, FIX PAGE function. You can use IDMSBCF, FIX PAGE to decrease the orphan count.
Reason:
Both DISK and CORE were entered in the AUDIT parameter statement.
Action:
Remove either DISK or CORE from the AUDIT statement and resubmit the job. If DISK is specified, be sure that two VSAM files are allocated.
Reason:
An SR8 record has been encountered where the decompressed record size exceeds Max-SR8-size as calculated from the subschema. This calculation is based upon the INDEX BLOCK CONTAINS n KEYS in the schema description of the integrated index set.
Action:
Rerun using a subschema created from a schema having a larger value for INDEX BLOCK CONTAINS n KEYS.
Reason:
Setlimit is an important factor in determining the size of the db-key table. In this case, setlimit is so large that the db-key table cannot reside in core.
Action:
Specify DISK on the AUDIT statement and resubmit the job. If DISK is specified, be sure that two VSAM files are allocated.
Reason:
Only one of these keywords is allowed per AREA statement.
Action:
Determine which keyword is desired and resubmit job.
Reason:
A record set to SWEEP resides in an area that is set to NOACCESS.
Action:
Resolve the conflict by either deleting the RECORD statement or change the AREA statement to allow access, then resubmit the job.
Reason:
A set that is to be audited resides in an area that is set to NOACCESS.
Action:
Resolve the conflict by either deleting the SET statement or change the AREA statement to allow access, then resubmit the job.
Reason:
One of these subparameters must be specified on with the AREA statement.
Action:
Specify subparameter for area and resubmit the job.
Reason:
A record set to SWEEP resides in an area that is set to NOACCESS.
Action:
Resolve the conflict by either deleting the RECORD statement or change the AREA statement to allow access, then resubmit the job.
Reason:
A record set to SWEEP resides in an area that is set to NOACCESS.
Action:
Resolve the conflict by either deleting the RECORD statement or change the AREA statement to allow access, then resubmit the job.
Reason:
A set that is to be audited reside in an area that is set to NOACCESS.
Action:
Resolve the conflict by either deleting the SET statement or change the AREA statement to allow access, then resubmit the job.
Reason:
A set that is to be audited reside in an area that is set to NOACCESS.
Action:
Resolve the conflict by either deleting the SET statement or change the AREA statement to allow access, then resubmit the job.
Reason:
A set that is to be audited reside in an area that is set to NOACCESS.
Action:
Resolve the conflict by either deleting the SET statement or change the AREA statement to allow access, then resubmit the job.
Reason:
A record set to SWEEP resides in an area that is set to NOACCESS.
Action:
Resolve the conflict by either deleting the RECORD statement or change the AREA statement to allow access, then resubmit the job.
Reason:
A set that is to be audited resides in an area that is set to NOACCESS.
Action:
Resolve the conflict by either deleting the SET statement or change the AREA statement to allow access, then resubmit the job.
Reason:
A set that is to be audited resides in an area that is set to NOACCESS.
Action:
Resolve the conflict by either deleting the SET statement or changing the AREA statement to allow access, then resubmit the job.
Reason:
A record set to SWEEP resides in an area that is set to NOACCESS.
Action:
Resolve the conflict by either deleting the RECORD statement or changing the AREA statement to allow access, then resubmit the job.
Reason:
Index orphan fixing was specified on the FIX statement in a QuickCheck type audit run.
Action:
Remove INDEX ORPHAN FIX parameter or change audit type to Standard and resubmit the job.
Reason:
Only one of these keywords is allowed per RECORD statement.
Action:
Determine which keyword is desired and resubmit job.
Reason:
A record set to NOACCESS is a member of a set that is to be audited.
Action:
Resolve the conflict by either deleting the SET statement or changing the RECORD statement to allow access, then resubmit the job.
Reason:
A record set to NOACCESS is a member of a set that is to be audited.
Action:
Resolve the conflict by either deleting the SET statement or changing the RECORD statement to allow access, then resubmit the job.
Reason:
A record set to NOACCESS is a member of a set that is to be audited.
Action:
Resolve the conflict by either deleting the SET statement or changing the RECORD statement to allow access, then resubmit the job.
Reason:
A record set to NOACCESS is a member of a set that is to be audited.
Action:
Resolve the conflict by either deleting the SET statement or changing the RECORD statement to allow access, then resubmit the job.
Reason:
One of these subparameters must be specified on the RECORD statement
Action:
Specify subparameter for record and resubmit the job.
Reason:
A record set to SWEEP resides in an area that is set to NOACCESS.
Action:
Resolve the conflict by either deleting the RECORD statement or changing the AREA statement to allow access, then resubmit the job.
Reason:
A record set to SWEEP resides in an area that is set to NOACCESS.
Action:
Resolve the conflict by either deleting the RECORD statement or changing the AREA statement to allow access, then resubmit the job.
Reason:
A record set to SWEEP resides in an area that is set to NOACCESS.
Action:
Resolve the conflict by either deleting the RECORD statement or changing the AREA statement to allow access, then resubmit the job.
Reason:
A record set to SWEEP resides in an area that is set to NOACCESS.
Action:
Resolve the conflict by either deleting the RECORD statement or changing the AREA statement to allow access, then resubmit the job.
Reason:
A record set to SWEEP resides in an area that is set to NOACCESS.
Action:
Resolve the conflict by either deleting the RECORD statement or changing the AREA statement to allow access, then resubmit the job.
Reason:
A set that is to be audited resides in an area that is set to NOACCESS.
Action:
Resolve the conflict by either deleting the SET statement or changing the AREA statement to allow access, then resubmit the job.
Reason:
A set that is to be audited resides in an area that is set to NOACCESS.
Action:
Resolve the conflict by either deleting the SET statement or changing the AREA statement to allow access, then resubmit the job.
Reason:
A record set to NOACCESS is a member of a set that is to be audited.
Action:
Resolve the conflict by either deleting the SET statement or changing the RECORD statement to allow access, then resubmit the job.
Reason:
A record set to NOACCESS is a member of a set that is to be audited.
Action:
Resolve the conflict by either deleting the SET statement or changing the RECORD statement to allow access, then resubmit the job.
Reason:
A record set to NOACCESS is a member of a set that is to be audited.
Action:
Resolve the conflict by either deleting the SET statement or changing the RECORD statement to allow access, then resubmit the job.
Reason:
A set that is to be audited resides in an area that is set to NOACCESS.
Action:
Resolve the conflict by either deleting the SET statement or changing the AREA statement to allow access, then resubmit the job.
Reason:
A set that is to be audited resides in an area that is set to NOACCESS.
Action:
Resolve the conflict by either deleting the SET statement or changing the AREA statement to allow access, then resubmit the job.
Reason:
A record set to NOACCESS is a member of a set that is to be audited.
Action:
Resolve the conflict by either deleting the SET statement or changing the RECORD statement to allow access, then resubmit the job.
Reason:
One of these subparameters must be specified on each SET statement.
Action:
Specify subparameter for set and resubmit the job.
Reason:
SR7 or SR8 record was found to have inconsistent next, prior, or owner pointers. This error is reported during AUDIT INDEX processing when AUDIT USERSETS was not also specific.
Action:
Use the CA IDMS utility IDMSBCF, FIX PAGE function to display the page where the SR8 resides to determine problem with the index set pointers, and to patch the bad page.
Reason:
Audit subparameter is specified with QuickCheck audit.
Action:
Index integrity checking is not available with QuickCheck type audit.
Reason:
WALKNEXT subparameter is specified with QuickCheck type audit.
Action:
USERSET orphan detection is incorporated with QuickCheck type audit.
Reason:
QuickCheck type audit created the extract file but Standard type audit was specified in subsequent fix run.
Action:
Change audit type in fix run to Standard or rerun audit type Standard to create new extract file.
Reason:
Standard type audit created the extract file, but QuickCheck type audit was specified in subsequent fix run.
Action:
Change audit type in fix run to QuickCheck or rerun with audit type QuickCheck to create new extract file.
Reason:
BEGIN/END subparameter specified with AREA statement and QuickCheck audit requires a sweep of all records in the area.
Action:
If partial area audit is preferable, then change audit type to Standard or audit all records in the area as required with QuickCheck type audit.
Reason:
If any index set is to be audited, all index sets in that page range must be audited.
Action:
Change parameters so that all index sets that follow are audited to ensure correct index processing.
Reason:
Native VSAM files are not allowed by CA IDMS/DB Audit.
Action:
VSAM file must be removed from subschema in order for CA IDMS/DB Audit to be run.
Reason:
SWEEP record type SR7 specified on RECORD statement.
Action:
SWEEP SR7 cannot be used to initiate audit of index set.
Reason:
Index orphan has an invalid upper level index record pointer.
Action:
Index orphan is connected to correct upper level index record but, the invalid pointer value caused the counter not to be decremented.
Reason:
Error found during QuickCheck sort and match, but no evidence of error could be found when SETWALK process was invoked to determine the cause of the error.
Action:
Rerun audit with process READYMODE set to UPDATE to assure no database update will occur during the audit run. If problem still exists, notify Computer Associates Product Support.
Reason:
Pointer error(s) were found while QuickCheck was processing an integrated index set.
Action:
QuickCheck is not able to determine correct index set sequence. Run Standard audit with AUDIT INDEX option set on.
Reason:
An internal error has occurred.
Action:
Contact Computer Associates Product Support.
Reason:
The user work area size must be a value 64 to 256 inclusive.
Action:
Correct the user work area size and resubmit the job.
Reason:
All the areas in the subschema are not included in the DMCL.
Action:
Use a DMCL that contains all the areas in the subschema.
Reason:
Subschema contains areas with mixed page groups or mixed radix - not supported.
Action:
CA IDMS/DB Audit cannot be run against a subschema that contains mixed page groups or mixed radix.
Reason:
The indicated file function could not be performed with the specified file.
Action:
See Figure 6.2 for an explanation and appropriate action for the return codes indicated.
Informative messages are suffixed by an nnnI message number and include possible causes for the message and any actions to be taken by the user.
Reason:
A CA IDMS/DB Audit input parameter statement has been read. The entire 80 byte image is displayed.
Action:
None.
Reason:
The parameter statement listed in message 001I contains a comma after the last keyword phrase. No processing is performed until a complete parameter statement is read.
Action:
None.
Reason:
The parameter statement listed in message 001I contains an asterisk (*) or a dollar sign ($) in position 1. The statement is not processed by CA IDMS/DB Audit.
Action:
None.
Reason:
A complete parameter statement was processed and no errors were detected.
Action:
None.
Reason:
The parameter statement listed in message 001I was not processed because of parameter errors.
Action:
Review the associated error messages. Correct the errors and resubmit job.
Reason:
A previous error has made execution of CA IDMS/DB Audit impossible; all remaining parameter statements are displayed but not processed.
Action:
Review the associated error messages. Correct any errors and resubmit the job.
Reason:
The end of the input parameter file was reached. All parameter statements were read.
Action:
None.
Reason:
The number of error or warning messages is shown. If any processing errors were detected, CA IDMS/DB Audit terminates processing.
Action:
Correct any errors and resubmit the job. Review all warning messages to determine if the requested processing options were in effect. If required, correct the parameter causing the warning message and resubmit the job.
Reason:
All parameter statements were processed and no errors were detected.
Action:
None.
Reason:
CA IDMS/DB Audit has successfully completed its parameter processing phase. CA IDMS/DB Audit prepares to obtain the amount of storage required for processing and initiate CA IDMS housekeeping functions at the designated date and time.
Action:
None.
Reason:
CA IDMS/DB Audit displays the total amount of main storage obtained for its work areas (record/page bind areas, symbolic sort key areas, DBKEYTBL, and db-key save table). See the "Operations" chapter for more details about CA IDMS/DB Audit storage requirements.
Action:
None.
Reason:
CA IDMS/DB Audit prepares to bind all records and pages that are to be audited, fixed, or reported. The amount of storage allocated from the storage pool for the BIND areas and symbolic sort key work areas is displayed.
Action:
None.
Reason:
CA IDMS/DB Audit prepares to ready all areas to be audited, fixed, or reported for EXCLUSIVE UPDATE or SHARED RETRIEVAL according to the READYMODE parameter of the PROCESS statement. The names of areas successfully readied follow this message.
Action:
None.
Reason:
CA IDMS/DB Audit initializes the DBKEYTBL that is used for determining whether or not a set occurrence contains a loop. The amount of storage allocated from the core storage pool is displayed. If DISK is specified in the AUDIT statement, the number of bytes is 0 (zero). See the "Parameters" chapter for more information about the DBKEYTBL.
Action:
None.
Reason:
CA IDMS/DB Audit initializes the db-key save table that is used for auditing a set containing prior pointers. The amount of storage allocated from the storage pool is displayed. If DISK is specified in the AUDIT statement, the number of bytes is 0 (zero). See Set Walk Processing in the "Concepts" chapter for more information about the db-key save table. This table is also used when processing integrated index sets.
Action:
None.
Reason:
Displays the date and time the designated phase began processing.
Action:
None.
Reason:
Displays the date and time the designated phase ended processing, and its return code.
Action:
None.
Reason:
Displays the date and time CA IDMS/DB Audit began sweeping the designated area during the audit phase.
Action:
None.
Reason:
Displays the date and time CA IDMS/DB Audit ended the sweep of the area designated in message 018I.
Action:
None.
Reason:
Associated audit and fix phase statistics follow this message.
Action:
See the "System Output" chapter for a description of the statistics.
Reason:
Associated CA IDMS and Computer Associates statistics follow this message. This message follows informative message 017I.
Action:
None.
Reason:
A FIX parameter statement was entered without an AUDIT parameter statement. CA IDMS/DB Audit uses as input an extract file created on the designated date and time by a previous CA IDMS/DB Audit job.
Action:
None.
Reason:
A request to physically delete LDEL records was made, but no LDEL records were detected in the audit phase. A request to fix CALCSETS, USERSETS, and/or PAGES was made, but no physical integrity errors were detected during the audit phase.
Action:
Review the FIX parameter statement to verify if the correct FIX request was made.
Reason:
No integrity errors were detected during the audit phase. No Integrity Analysis Report will be produced, even though a REPORTS statement is present.
Action:
None.
Reason:
Following this message, CA IDMS/DB Audit displays all processing options in effect for the current job.
Action:
None.
Reason:
CA IDMS/DB Audit successfully completed the requested processing phases (audit, fix, or reports) at the indicated date and time.
Action:
None.
Reason:
During the audit phase, physical integrity errors were detected in the designated area when auditing the PAGE header/footer.
Action:
Review the associated error messages and determine if fixing should be performed.
Reason:
Fixing was requested. CA IDMS/DB Audit has fixed the pages in the designated area as shown.
Action:
Refer to FIX Report banner to determine if real or simulated fixing was done. If simulated fixing was done, review the fixes to determine if real fixes should be applied.
Reason:
The db-keys of the displayed records do not fall within the from/thru page ranges specified. The records do not participate in a set occurrence found to contain other integrity errors.
Action:
None. CA IDMS/DB Audit cannot fix this type of error.
Note: This type of error does not affect the walking of a setoccurrence. It can, however, cause CALC records not to be found.
Reason:
The audit phase has determined that the designated record occurrences are fully disconnected from a set occurrence. Either DISCONNECT=ALL or DISCONNECT=EXPLICIT was specified.
Action:
If the record(s) should be connected to a set, use the CA IDMS utility IDMSBCF, FIX PAGE function to display the page where the designated record resides and patch the bad page.
Reason:
The records displayed do not participate in a set occurrence found to contain other integrity errors. A partial area audit was performed and the record occurrence is a member of a set occurrence whose owner record was never retrieved through the area sweep. A full area audit was performed and the record occurrence is an orphan of a set occurrence and WALKNEXT was not requested.
Action:
Execute an audit with a full area sweep where the owner record of the indicated set resides. Execute an audit requesting WALKNEXT processing. In order for processing to proceed quickly, all areas, records, and sets that do not participate in the error set can be designated as NOACCESS in the appropriate AREA, RECORD, or SET parameter statements.
Reason:
The audit phase has determined that the designated set contains the following integrity errors. Information about the owner record of the set follows this message.
Action:
Review the associated messages and determine if fixing should be performed.
Reason:
When fixing was requested, CA IDMS/DB Audit fixed the designated set as shown. Information about the owner record of the set follows this message.
Action:
Refer to the FIX Report banner to check if real or simulated fixing was performed. If simulated fixing was performed, review the fixes to determine if real fixes should be applied.
Reason:
Information about every record occurrence detected while walking next from the owner record of the set follows this message.
Action:
Review the associated messages.
Reason:
Information about every record occurrence detected while walking prior from the owner record of the set follows this message.
Action:
Review the associated messages and determine if fixing should be performed.
Reason:
This message appears only for a set containing both next and prior pointers. While walking next, the designated record's prior db-key did not point back to the prior record in the set. While walking prior, the designated record's next db-key did not point back to the next record in the set. Once the chain containing the record with the mismatched next/prior db-key is walked, CA IDMS/DB Audit begins walking the chain from the record in the opposite direction. See Set Walk Processing in the "Concepts" chapter for more information.
Action:
Review the associated messages and determine if fixing should be performed.
Reason:
While walking a set occurrence containing an integrity error, CA IDMS/DB Audit detected that the record's designated db-key pointed to a member record that was already audited.
Action:
Review the associated messages and determine if fixing should be performed.
Reason:
Information about a record occurrence is displayed. The record is logically deleted, however, and does not have any record data associated with it.
Action:
None.
Reason:
The record occurrences displayed after this message were detected as orphan records via walknext processing.
Action:
Review the associated messages and determine if fixing should be performed. If fixing is performed, the displayed orphan records will be added back into the set.
Reason:
CA IDMS/DB Audit has determined that the designated set contains no physical integrity errors. During walknext processing, however, orphan records were found to be associated with the set occurrence.
Action:
Review the associated messages and determine if fixing should be performed. If fixing is performed, the orphan records will be added back into the set.
Reason:
The records following this message could not be associated with any owner record occurrences for the indicated set type.
Action:
None. CA IDMS/DB Audit cannot fix this type of error.
Reason:
When fixing was requested, CA IDMS/DB Audit successfully deleted the logically deleted records from the indicated set occurrence. The deleted records are listed following this message.
Action:
Refer to the FIX Report banner to check if real or simulated fixing was performed. If simulated fixing was performed, review the fixes to determine if real fixes should be applied.
Reason:
When fixing was requested, CA IDMS/DB Audit has determined that the displayed LDEL record was physically deleted from all sets where it was a member. CA IDMS/DB Audit erases the LDEL record occurrence.
Action:
Refer to the FIX Report banner to check if real or simulated fixing was performed. If simulated fixing was performed, review the fixes to determine if real fixes should be applied.
Reason:
This message is displayed only for records that do not participate in a set occurrence found to contain other integrity errors. Two conditions can cause this message:
Only the control portion of the record data is displayed.
Action:
Use the CA IDMS utility IDMSBCF, FIX PAGE function to display the page or pages where the designated records reside and to patch the bad page or pages.
Reason:
CA IDMS/DB Audit prepared for correction of either SETS (CALCSETS and/or USERSETS), LDELS, or PAGES at the designated date and time.
Action:
None.
Reason:
The displayed non-zero error status was returned after executing a CA IDMS DML command. This message follows the error message that describes the type of CA IDMS function requested.
Action:
Review the error status and take appropriate action. See Figure 6.1 at the end of this chapter for a description of error status codes not described in the CA IDMS CODES and MESSAGES manual.
Reason:
This message follows any error messages that caused CA IDMS/DB Audit to terminate processing on a specific set occurrence. The name of the last record retrieved through the area sweep is displayed.
Action:
None.
Reason:
The displayed db-key is associated with the previously displayed error message. Both hexadecimal and decimal forms are displayed.
Action:
None.
Reason:
CA IDMS/DB Audit displays the record name of the owner of the set occurrence where CA IDMS/DB Audit terminated processing.
Action:
Review the associated informative and error messages.
Reason:
This message appears only if the records do not participate in a set occurrence found to contain other integrity errors. The records displayed following this message are compressed records that could not be successfully decompressed because of errors within the compressed portion of the records. A record that could not be properly decompressed can cause CA IDMS/DB Audit to report that fragments could not be properly assembled. See message 048I.
Action:
Use the CA IDMS utility IDMSBCF, FIX PAGE function to display the page or pages where the designated records reside and to patch the bad page or pages.
Reason:
CA IDMS/DB Audit has successfully completed fixing of SETS, LDELS, or PAGES displayed in message 049I. A COMMIT DML has been successfully issued and the database buffers have been cleared.
Action:
None.
Reason:
SETMBRS=ERRSONLY was specified in the REPORTS statement. Therefore, the display shows only records containing errors or records immediately preceding or following them. The message indicates the number of records that are not displayed for this set.
Action:
None.
Reason:
Displays the date and time CA IDMS/DB Audit began integrated index processing.
Action:
None.
Reason:
Displays the date and time CA IDMS/DB Audit ended integrated index processing.
Action:
None.
Reason:
The records displayed after this message are orphan records of the indicated integrated index set. The upper level pointer does not point to the correct SR8 record in the level above.
Action:
Review the associated messages and determine if fixing should be performed. If fixing is performed, for each orphan record listed, the upper db-key is modified to point to the appropriate record in the next higher level. Also, the orphan counts are decreased.
Reason:
The records displayed after this message are disconnected from the indicated integrated index set. Db-keys obtained during sweep processing and index processing are not paired.
Action:
Use the CA IDMS utility IDMSBCF, FIX PAGE function to correct the situation.
Reason:
When CA IDMS/DB Audit looked for a record indicated by the db-key pointers in an integrated index set, it either did not find the record or it found errors within the record.
Action:
Examine the associated messages to determine the specific nature of the error.
Reason:
In a set sorted by symbolic key, an SR8 record points to a member record, but the symbolic key listed in the SR8 record does not match the symbolic key of the member record.
Action:
Use the CA IDMS utility IDMSBCF, FIX PAGE function to display the page where the designated record resides and patch the bad page.
Reason:
In an upper level SR8 entry, the sort key is in error. In a set sorted by db-key, the upper level SR8 db-key does not match the last db-key in the record below. In a set sorted by symbolic key, an upper level symbolic key does not match the last symbolic key in the record below. In a lower level SR8, the sequence of the table within the SR8 record is in error.
Action:
Use the CA IDMS utility IDMSBCF, FIX PAGE function to display the page where the designated record resides and patch the bad page.
Reason:
The sequence order of a sorted set.
Action:
None.
Reason:
Date and time integrated index disconnect processing began.
Action:
None.
Reason:
Date and time integrated index disconnect processing ended.
Action:
None.
Reason:
The upper level db-keys of the listed records were corrected.
Action:
The report banner indicates whether real or simulated fixing was performed. If simulated fixing was performed, review the changes to determine if real fixing should be performed.
Reason:
The level number in an SR8 record does not match the number of the level where the record resides.
Action:
Use the CA IDMS utility IDMSBCF, FIX PAGE function to display the page where the designated record resides and patch the record.
Reason:
In an integrated index record, the symbolic flag is on even though the sorted set flag is off.
Action:
Use the CA IDMS utility IDMSBCF, FIX PAGE function to display the page where the designated record resides and patch the record.
Reason:
The displayed owner db-key is associated with previously displayed error message.
Action:
None.
Reason:
The displayed index set name is associated with previously displayed error message.
Action:
None.
Reason:
Indicates whether sort record was created from an actual database record (type=sweep) or a generated match record (type=dummy), shows the name of the set (for IIX sets the name cannot be determined), and shows what pointers the set has (NEXT, NEXT/PRIOR, NEXT/OWNER, NEXT/PRIOR/OWNER).
Action:
When SET=UNKNOWN-IIX-SET, run AUDITTYPE=STANDARD.
Reason:
Displays the db-keys in the actual sort record.
Action:
None.
Reason:
Indicates errors were found while QuickCheck was processing an integrated index set.
Action:
Refer to Audit Report for details of error. Run AUDITTYPE=STANDARD to correct the error.
Reason:
An earlier step encountered a DML error.
Action:
Refer to Audit Report for details of error.
Reason:
A record having a location node of CALC was not a member of the CALC set. It's CALC key indicates the CALC set owner to which it should be connected.
Action:
Review the associated messages and determine if fixing should be performed. If fixing is performed, the orphan records will be added back into the set.
|
Copyright © 2013 CA.
All rights reserved.
|
|