Messages › Message Listing

Message Listing

ARPT001I AREA REPORTS COMPLETED SUCCESSFULLY

Reason: All area reports have been successfully written.

Action: None.

ARPT002W UNABLE TO WRITE AREA REPORT - NO AREA-TYPE RECORDS FOUND IN STATISTICS FILE (1/2)

Reason: The statistics file specified contains no records of the type required to produce the report requested.

Action: Verify that the file name specified is correct.

CALL901E PARAMETER LIST ERROR - PGM = module-name

Reason: The module could not be called because of an internal problem.

Action: Contact CA, Inc. Product Support.

CALL902E NOT FOUND IN LIBRARY - PGM = module-name

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.

CALL903E NOT ENOUGH STORAGE - PGM = module-name

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.

CALL904E ANCHOR TABLE LOAD FAILURE - PGM = GSSANKR

Reason: An internal error has been detected.

Action: Contact CA, Inc. Product Support.

CALL905E UNANTICIPATED RETURN CODE = n PGM = module-name

Reason: An internal error has been detected.

Action: Contact CA, Inc. Product Support.

DRVR001E ERROR CALLING module-name, CALL PARAMETER ERROR

Reason: The specified module cannot be called because of an internal error.

DRVR002E ERROR CALLING module-name, PROGRAM NOT FOUND

Reason: The specified program cannot be located in the available library.

Action: Locate the library that contains the module and make it available to the job. Resubmit the job.

DRVR003E ERROR CALLING module-name, NOT ENOUGH STORAGE TO LOAD PROGRAM

Reason: The specified program cannot be loaded because of insufficient region size.

Action: Increase the region size and resubmit the job.

DRVR004E UNANTICIPATED RETURN CODE r PGM = module name

Reason: An internal error has been detected.

Action: Contact CA, Inc. Product Support.

FILM001E GSSFILE RETURNED AN ERROR DURING file-function WITH FILE file-name, RETURN CODES ARE n1,n2,n3,n4

Reason: The file handler is unable to perform the file function with the specified file.

Action: Refer to the following table for an explanation of specific return codes and action.

Two types of errors can be reported by the return codes of n1, n2, n3, and n4—non-VSAM file errors and VSAM file errors. The error is described by n2 and n4. For VSAM file errors, n4 is always equal to 28. The error is described by n1, n2, and n3. A general return code is given by n4 for both non-VSAM and VSAM errors. All return codes are decimal values.

GSFL999I file-id IS NOT VSAM—WILL TRY QSAM

Reason: The indicated file is not a VSAM file (VSE/ESA only).

Action: CA IDMS/DB Analyzer attempted to open the indicated file for VSAM processing. No action is required.

IERR000E INTERNAL ERROR, module-name - description

Reason: An unrecoverable error condition was detected by the module. The description explains the error.

Action: Contact CA, Inc. Product Support.

IRPT001I SR8 INDEX REPORTS COMPLETED SUCCESSFULLY

Reason: All SR8 index reports were successfully written.

Action: None

IRPT002W UNABLE TO WRITE SR8 INDEX REPORT—NO SR8 INDEX-TYPE RECORD FOUND IN STATISTICS FILE (1/2)

Reason: The statistics file specified contains no records of the type required to produce the report requested.

Action: Verify that the file name specified is correct.

LMSG901E MESSAGE NOT IN TABLE.........message-id module-name

Reason: The indicated module does not contain the indicated message.

Action: Contact CA, Inc. Product Support.

LMSG902E MESSAGE TABLE NOT FOUND......module-name

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.

LMSG903E NOT ENOUGH STORAGE FOR TABLE.module-name

Reason: The indicated 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.

LMSG904E BAD MESSAGE PARM OR TABLE....module-name

Reason: An internal processing error has been detected.

Action: Contact CA, Inc. Product Support.

LMSG905E UNANTICIPATED RETURN CODE....n

Reason: An internal processing error has been detected.

Action: Contact CA, Inc. Product Support.

NKWP001E UNRECOGNIZABLE MAJOR KEYWORD

Reason: The major keyword underscored by asterisks (*******) in the Audit Report is misspelled or is in error and cannot be processed.

Action: Correct the spelling of the keyword and resubmit the job.

NKWP002E DUPLICATE MINOR KEYWORD ENTERED

Reason: The minor keyword underscored by asterisks (*******) in the Audit Report has already been entered on the parameter statement underscored.

Action: Delete the duplicate minor keyword phrase and resubmit the job.

NKWP003E AN EQUAL SIGN (=) AND VALUE MUST FOLLOW THE KEYWORD

Reason: The required equal sign and value after the keyword are missing.

Action: At the location underscored by an asterisk (*) in the Audit Report, enter an equal sign followed by an appropriate value for the parameter. Resubmit the job.

NKWP005E MISSING RIGHT PARENTHESIS; PHRASE TERMINATED

Reason: A set of open and closed parentheses is required.

Action: Enter a right parenthesis to enclose the phrase or list, then resubmit the job.

NKWP006E REPEATED LIST IMPROPERLY CONTINUED

Reason: The last phrase on this statement is a list enclosed in parentheses that ends with a comma. However, the next statement entered does not continue the list.

Action: Supply a continuation card and resubmit the job.

NKWP007E MISSING CONTINUATION CARD

Reason: The previous statement ended with a comma, but this statement begins with a major keyword.

Action: Supply a continuation card and resubmit the job.

NKWP008E PRIORITY MUST CONTAIN NO MORE THAN 500 VALUES

Reason: You supplied more than 500 record types and/or record names in the priority list.

Action: Correct and resubmit the job.

NKWP009E VALUE MUST BE xxxxxxxxxxxxxxxxxxxxx

Reason: The value underscored by an asterisk (*) in the Audit Report is incorrect for the keyword.

Action: Supply the appropriate value specified in the message and resubmit the job.

NKWP010E KEYWORD PHRASES NOT SEPARATED BY COMMA

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.

NKWP011E UNRECOGNIZABLE MINOR KEYWORD

Reason: The minor keyword underscored by asterisks (*******) in the Audit Report is misspelled or is in error and was not processed.

Action: Correct the spelling of the minor keyword and resubmit the job.

NKWP012E MINOR KEYWORD OMITTED

Reason: A minor keyword was omitted at the location underscored by an asterisk (*) in the Audit Report.

Action: Enter the missing minor keyword and resubmit the job.

NKWP015E THESE KEYWORD(S) MUST BE SPECIFIED:xxxxxxxxxxxxxxxxxxxx

Reason: The minor keyword(s) listed in the message was omitted. CA IDMS/DB Analyzer cannot continue processing unless the keyword(s) shown is entered.

Action: Supply the missing keyword(s) and resubmit the job.

NKWP018E MISSING VALUE NEEDED xxxxxxxxxxxxx

Reason: A keyword was entered without a value. The acceptable values are listed in the variable portion of the error message.

Action: Enter the correct value at the location underscored by an asterisk (*) in the Audit Report and resubmit the job.

NKWP019E VALUE ENTERED PREVIOUSLY

Reason: The value underscored by asterisks (****) on the Audit Report was already entered in the list. CA IDMS/DB Analyzer cannot process this parameter unless you supply two different values.

Action: Correct the value and resubmit the job.

NKWP020E VALUE MUST BE ASCENDING

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.

NKWP021E VALUE MUST BE DESCENDING

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.

NKWP024E SECOND-LEVEL PRIORITY MUST CONTAIN AT LEAST ONE VALUE.

Reason: A list or sublist cannot be empty. It must contain at least one valid record type for the record name.

Action: At the location underscored by an asterisk (*) in the Audit Report, insert one or more record types or record names in the priority statement.

NKWP027E SECOND-LEVEL-PRIORITY MUST CONTAIN NO MORE THAN 10 VALUES

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.

NKWP050E GSSNKWP INTERNAL ERROR. NOTIFY Computer Associates PRODUCT SUPPORT

Reason: An unrecoverable error has been detected.

Action: Contact CA, Inc. Product Support.

NKWP051E ERROR OCCURRED DURING CALL OF xxxxxxxx - GSSCALL RETURN CODE IS nn

Reason: A module call processor error occurred.

Action: Contact CA, Inc. Product Support.

NKWP052E ERROR OCCURRED DURING LOAD OF xxxxxxxx - GSSLOAD RETURN CODE IS nn

Reason: A module load processor error occurred.

Action: Contact CA, Inc. Product Support.

NKWP053E ERROR OCCURRED DURING WRITE OF xxxxxxxx - GSSPRINT RETURN CODE IS nn

Reason: An error occurred during a call of the printer module.

Action: Contact CA, Inc. Product Support.

NKWP061E DD STATEMENT MISSING FOR DDNAME: xxxxxxxx

Reason: A JCL DD card was not supplied.

Action: Correct the JCL and resubmit the job.

NKWP062E LOGICAL UNIT NOT ASSIGNED: xxxxxxxx

Reason: An ASSGN card was not supplied.

Action: Correct the JCL and resubmit the job.

NKWP063E SYSIPT LRECL MUST BE 80.

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.

NKWP064E ERROR OCCURRED DURING OPEN OF xxxxxxxx FILE - GSSFILE RETURN CODE IS n1,n2,n3,n4

Reason: The file handler is unable to open the file.

Action: See the table above for an explanation and appropriate action for the indicated return codes.

NKWP065E ERROR OCCURRED DURING READ OF xxxxxxxx FILE - GSSFILE RETURN CODE IS n1,n2,n3,n4

Reason: The file handler is unable to read the file.

Action: See the table above for an explanation and appropriate action for the indicated return codes.

NKWP066E ERROR OCCURRED DURING CLOSE OF xxxxxxxx FILE - GSSFILE RETURN CODE IS n1,n2,n3,nnn

Reason: The file handler is unable to close the file.

Action: See the table above for an explanation and appropriate action for the indicated return codes.

NKWP080W SKIPPING UNTIL NEXT RECOGNIZABLE STATEMENT

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.

NKWP081W SKIPPING UNTIL NEXT RECOGNIZABLE MINOR KEYWORD

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.

NKWP091I INPUT PARAMETER STATEMENT

Reason: A CA IDMS/DB Analyzer input parameter statement has been read. The entire 80-byte image is displayed. Columns 1-72 will be processed.

Action: None.

NKWP092I CONTINUATION STATEMENT

Reason: The parameter statement continues a previous statement entered.

Action: None.

NKWP093I COMMENT STATEMENT

Reason: The parameter statement contains an asterisk (*) as the first non-blank character. This indicates that this is a comment statement, and it will not be processed.

Action: None.

NKWP094I END OF PARAMETER INPUT

Reason: All parameters that were entered have been read and processed by CA IDMS/DB Analyzer.

Action: None.

NKWP095I BLANK PARAMETER STATEMENT

Reason: The parameter statement contains only blanks in columns 1-72 and will not be processed.

Action: Correct and resubmit the job.

NKWP096E UNMATCHED APOSTROPHE. NEED xxxxxxxxxxxx

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 acceptable values are listed in the variable portion of the error message.

Action: Correct the value underscored by asterisks (****) and resubmit the job.

NKWP097E BAD LITERAL FORMAT. NEED xxxxxxxxxxxx

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 acceptable values are listed in the variable portion of the error message.

Action: Correct the value underscored by asterisks (****) and resubmit the job.

NLYZ001E STATISTICS FILE file-name IS EMPTY, REPORTING CANNOT BE DONE

Reason: The first read of the specified file returned an END-OF-FILE condition. This error can be caused by improper JCL or by a corrupted statistics file.

Action: Verify that the file is a valid statistics file and that there are no JCL errors. Resubmit the job.

NLYZ002E FILE file-name IS NOT A VALID STATISTICS FILE, REPORTING CANNOT BE DONE

Reason: The specified file was not created by CA IDMS/DB Analyzer or is a legitimate statistics file that has been corrupted. This error could also be caused by improper JCL.

Action: Verify that the file is a valid statistics file and that there are no JCL errors. Resubmit the job.

NLYZ003E ERROR LINKING TO module-name, LINK PARAMETER ERROR

Reason: USNLYZR is unable to call the module due to an internal problem.

Action: Call CA, Inc. Product Support.

NLYZ004E ERROR LINKING TO module-name, PROGRAM NOT FOUND

Reason: The specified 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.

NLYZ005E ERROR LINKING TO module-name, NOT ENOUGH STORAGE TO LOAD PROGRAM

Reason: The specified 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.

NLYZ006I CA-IDMS/DB ANALYZER ENDED, CC=number

Reason: CA IDMS/DB Analyzer has completed execution with the designated condition code.

Action: None.

NRPT001I INDEX REPORTS COMPLETED SUCCESSFULLY

Reason: All index reports have been successfully written.

Action: None.

NRPT002W UNABLE TO WRITE INDEX REPORT - NO INDEX-TYPE RECORDS FOUND IN STATISTICS FILE (1/2)

Reason: The statistics file specified contains no records of the type required to produce the report requested.

Action: Verify that the file name specified is correct.

PARM001I INPUT PARAMETER STATEMENT VALIDATION IS COMPLETE

Reason: All input parameter statements were read and validated. Any parameter errors have been reported.

Action: None.

PARM003E MEMBER LOADED FOR subschema-name SUBSCHEMA IS NOT A SUBSCHEMA

Reason: The specified subschema is not a subschema. If the subschema name is correct then the subschema has been corrupted in the load or core-image library.

Action: Verify that the subschema name is correct. If the subschema is corrupted then recreate it. Resubmit the job.

PARM005E MEMBER LOADED FOR DMCL OF subschema-name SUBSCHEMA IS NOT A DMCL

Reason: The subschema's DMCL is invalid. If the DMCL name is correct then the DMCL has been corrupted in the load or core-image library.

Action: Verify that the DMCL name in the indicated subschema is correct. If DMCL is corrupted then recreate it. Resubmit the job.

PARM006E NOT ENOUGH STORAGE TO BUILD INTERNAL PROCESSING TABLE

Reason: There is insufficient storage for CA IDMS/DB Analyzer to execute.

Action: Under VSE/ESA, use a larger partition or a smaller SIZE= parameter. Under z/OS and OS/390, use a larger REGION. Resubmit the job.

PARM007E END-OF-FILE ON FIRST READ OF INPUT PARAMETER FILE, OR ONLY COMMENT OR BLANK RECORDS WERE READ

Reason: File SYSIPT was empty or no parameter statements were present in the input given.

Action: Place parameter statements in file SYSIPT. Resubmit the job.

PARM008E PROCESS PARAMETER STATEMENT WAS EXPECTED

Reason: CA IDMS/DB Analyzer expected a PROCESS statement, but instead received some other parameter statement type.

Action: A PROCESS statement is required and must be the first parameter statement in file SYSIPT. Correct and resubmit the job.

PARM009E PROCESS STATEMENT WAS NOT FIRST

Reason: CA IDMS/DB Analyzer found a PROCESS statement, but it was not the first parameter statement encountered.

Action: The PROCESS statement must be the first parameter statement in file SYSIPT. Correct and resubmit the job.

PARM010E PROCESS STATEMENT WAS NOT FOUND

Reason: CA IDMS/DB Analyzer did not find a PROCESS parameter statement in file SYSIPT.

Action: A PROCESS statement is required and must be the first parameter statement in file SYSIPT. Correct and resubmit the job.

PARM011E WHEN GIVEN, THE TENTH AREADIST VALUE MUST EQUAL THE AREA SWEEP STOP PAGE

Reason: Ten AREADIST values were given and the tenth one was not equal to the area sweep stop page.

Action: Change the tenth AREADIST value to equal the area sweep stop page or do not specify the tenth value. When only nine values are given, the tenth one will default to the area sweep stop page. Resubmit the job.

PARM012E DUPLICATE PROCESS STATEMENT DETECTED

Reason: More than one PROCESS statement was found in file SYSIPT. Only one PROCESS statement is allowed.

Action: Correct and resubmit the job.

PARM013E AREA area-name NOT IN SUBSCHEMA

Reason: The indicated area is not in the subschema specified on the PROCESS statement.

Action: Correct and resubmit the job.

PARM014E DUPLICATE AREA STATEMENT ENTERED FOR AREA area-name

Reason: More than one AREA statement was found for the indicated area in file SYSIPT. Only one AREA statement is allowed for each area.

Action: Correct and resubmit the job.

PARM015E NOSWEEP IS MUTUALLY EXCLUSIVE WITH THE AREA PROCESSING PARAMETERS OF START, STOP, AND AREADIST

Reason: An AREA statement with the NOSWEEP keyword also indicated a parameter of START, STOP, or AREADIST. START, STOP, and AREADIST are processing parameters that may not be included in the same statement with NOSWEEP.

Action: Correct and resubmit the job.

PARM016E START/STOP PAGE SPECIFIED ON PARAMETER STATEMENT IS GREATER/LESS THAN AREA HIGH-PAGE/LOW-PAGE

Reason: An AREA statement has one of the following conditions: Either the START page given is greater than the area's HIGH-PAGE, or the STOP page given is less than the area's LOW-PAGE.

Action: Correct and resubmit the job.

PARM017E STOP PAGE SPECIFIED ON PARAMETER STATEMENT IS LESS THAN SPECIFIED AREA SWEEP START PAGE

Reason: An AREA statement has a STOP page that is less than the indicated area sweep START page. The area STOP page must be greater than or equal to the area START page.

Action: Correct and resubmit the job.

PARM018E AN hpage SPECIFIED ON PARAMETER STATEMENT IS GREATER/LESS THAN AREA SWEEP STOP/START PAGE

Reason: An AREA statement has one of the following conditions: Either an hpage given is greater than the area's sweep STOP page, or an hpage given is less than the area's sweep START page.

Action: Correct and resubmit the job.

PARM019E DUPLICATE SET STATEMENT ENTERED FOR SET set-name

Reason: More than one SET statement was found for the indicated set in file SYSIPT. Only one SET statement is allowed for each set.

Action: Correct and resubmit the job.

PARM020E A PARAMETER STATEMENT FOR SET set-name WAS ENTERED THAT TRIED TO ACCESS AN AREA MARKED AS NOOWNERSET OR NOMEMBERSET

Reason: A SET statement for the indicated set attempted to turn on WALK within an area that has been set NOOWNERSET or NOMEMBERSET by a previous AREA statement.

Action: Change either the SET statement or the AREA statement to resolve the conflict. Resubmit the job.

PARM021E SET set-name NOT IN SUBSCHEMA

Reason: The indicated set is not in the subschema specified on the PROCESS statement.

Action: Correct and resubmit the job.

PARM022E NOWALK IS MUTUALLY EXCLUSIVE WITH THE SET PROCESSING PARAMETER OF LNTHDIST

Reason: A SET statement specifying NOWALK also specified LNTHDIST. LNTHDIST may not be specified in the same statement with NOWALK.

Action: Correct and resubmit the job.

PARM026E NOOWNERSET/NOMEMBERSET NOT ALLOWED, AREA area-name CONTAINS SET(S) NAMED FOR ACCESS BY PREVIOUS SET OR INDEX STATEMENTS

Reason: An AREA statement for the specified area attempts to turn off WALK within an area that contains sets named for WALK by previous SET statements.

Action: Change either the SET statement or the AREA statement to resolve the conflict. Resubmit the job.

PARM027E PROCESS SELECTION=EXPLICIT REQUIRES THAT AT LEAST ONE AREA OR SET STATEMENT BE ENTERED

Reason: The PROCESS statement specifies EXPLICIT processing but no AREA or SET statements were found in file SYSIPT. EXPLICIT processing requires that at least one AREA or SET statement be given.

Action: Correct and resubmit the job.

PARM029E FSTRIGGER MUST BE LESS THAN FSBUFFERS

Reason: The FSTRIGGER value is greater than or equal to the FSBUFFERS value.

Action: Reduce the FSTRIGGER value or increase the FSBUFFERS value as appropriate. Resubmit the job.

PARM030E AN AREA STATEMENT WITH NO PARAMETERS IS NOT ALLOWED DURING AUTOMATIC PROCESSING.

Reason: An AREA statement without any processing parameters was specified with AUTOMATIC Mode. AREA statements without processing parameters are normally only specified with the EXPLICIT Mode. Either AREA statement processing parameters were forgotten for AUTOMATIC processing or EXPLICIT processing was desired.

Action: Correct and resubmit the job.

PARM031E ERROR LINKING TO module-name, LINK PARAMETER ERROR

Reason: USNDRVR is unable to call the module due to an internal problem.

Action: Call CA, Inc. Product Support.

PARM032E ERROR LINKING TO module-name, PROGRAM NOT FOUND

Reason: The specified 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.

PARM033E ERROR LINKING TO module-name, NOT ENOUGH STORAGE TO LOAD PROGRAM

Reason: The specified 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.

PARM034E MEMBER LOADED FOR xxx SUBSCHEMA CONTAINS INTEGRITY ERRORS

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.

PARM035I SUBSCHEMA subschema-name DOES NOT INCLUDE RECORD-ID record-id, STATISTICS MAY NOT REFLECT THE ENTIRE DATABASE

Reason: The indicated record ID is present in the database but is not part of the specified subschema. Statistics related to the indicated record ID will not be collected.

Action: None.

PARM036E MEMBER LOADED FOR xxx SUBSCHEMA CONTAINS nnn NATIVE VSAM FILES

Reason: The current release does not support the processing of Native VSAM Files.

Action: Create a subschema which does not include Native VSAM Files and resubmit the job using the changed subschema.

PARM037E NOSWEEP IS MUTUALLY EXCLUSIVE WITH THE SELECTION MODE OF EXPLICIT

Reason: An AREA statement including NOSWEEP was specified after a PROCESS statement designated SELECTION=EXPLICIT. NOSWEEP may not be specified when EXPLICIT is the selection mode.

Action: Correct the AREA statement and resubmit the job.

PARM038E NOWALK IS MUTUALLY EXCLUSIVE WITH THE SELECTION MODE OF EXPLICIT

Reason: NOWALK was specified in a SET statement after a PROCESS statement designated SELECTION=EXPLICIT. NOWALK may not be specified when EXPLICIT is the SELECTION mode.

Action: Correct the SET statement and resubmit the job.

PARM039E IIX SET setname NOT FOUND WITHIN YOUR SUBSCHEMA'S AREAS

Reason: The area associated with the SR7 of a system owned integrated index set is not within the subschema.

Action: Use a subschema that does not contain a partial view of the set.

PARM043E INVALID USER WORK AREA SIZE PASSED

Reason: The user work area size must be a value from 64 to 256 inclusive.

Action: Correct the user work area size and resubmit the job.

PARM044E SUBSCHEMA AREA NOT FOUND IN THE DMCL

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.

PARM045E SUBSCHEMA subschema-name DEFINES AN SQL DATABASE - NOT SUPPORTED

Reason: CA IDMS/DB Analyzer does not currently support SQL databases.

Action: Do not run CA IDMS/DB Analyzer specifying a subschema that defines an SQL database.

PRNT910E A SEVERE ERROR OCCURRED DURING OUTPUT TO THE SYSLST FILE

Reason: GSSCALL experienced a problem invoking GSSPRNT.

Action: Ensure all necessary programs are available in your steplib or LIBDEF.

RRPT001I RECORD REPORTS COMPLETED SUCCESSFULLY

Reason: All record reports have been successfully written.

Action: None.

RRPT002W UNABLE TO WRITE RECORD REPORT - NO RECORD-TYPE RECORDS FOUND IN STATISTICS FILE (1/2)

Reason: The statistics file specified contains no records of the type required to produce the report requested.

Action: Verify that the file name specified is correct.

SORT001I SORT OF ACCUMULATED STATISTICS IS COMPLETE

Reason: The sorting of the gathered statistics has run to completion.

Action: None.

SORT002E SORT OF ACCUMULATED STATISTICS TERMINATED WITH RETURN CODE n

Reason: The call to the installation-provided sort program has resulted in a non-zero return code of n.

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.

SORT003E ERROR LINKING TO module-name, LINK PARAMETER ERROR

Reason: USNSORT is unable to call the specified module due to an internal problem.

Action: Call CA, Inc. Product Support.

SORT004E ERROR LINKING TO module-name, PROGRAM NOT FOUND

Reason: The specified module cannot be located in the available load or core-image libraries.

Action: Locate the load or core-image library that contains module-name and make it available to the job. Resubmit the job.

SORT005E ERROR LINKING TO module-name, NOT ENOUGH STORAGE TO LOAD PROGRAM

Reason: The specified 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.

SRPT001I SET REPORTS COMPLETED SUCCESSFULLY

Reason: All set reports have been successfully written.

Action: None.

SRPT002W UNABLE TO WRITE SET REPORT - NO SET-TYPE RECORDS FOUND IN STATISTICS FILE (1/2)

Reason: The statistics file specified contains no records of the type required to produce the report requested.

Action: Verify that the file name specified is correct.

 DBIO MAJOR ERROR STATUS CODES

 FS = FAST-SCAN
 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 run unit
 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 db-key
 C2 = Invalid Store
 C3 = Skipped index
 C4 = Broken chain
 C5 = IXDET member of multiple sets
 C6 = Ignored page reserve
 C7 = Invalid Length - discrepancy in RDW lengths encountered during
      attempted MODIFY RECORD
 C8 = DMCL/SCHEMA IDMS release mismatch
 C9 = Decompress error
 D1 = Invalid record length
 D2 = FSBUFFER less than minimum value
 D3 = FSTRIGGER not less than FSBUFFER or FSTRIGGER equal to 0
 D4 = Invalid page displacement
 D5 = Invalid request
 D6 = FSBUFFER exceeds maximum value
 D7 = GSDTPARM cannot be loaded
 D8 = Record not found in PSUB
 D9 = segment named in 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 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

STAT002E IDMS ERROR RETURNED FROM program-name

Reason: A DBIO error has occurred. The program indicated was executing at the time the error occurred.

Action: The action required depends on interpretation of the DBIO return code given in Message: STAT003E.

STAT003E ERROR STATUS WAS error-code

Reason: A DBIO error has occurred.

Action: To find the meaning of the first two digits of the error code refer to the list of CA IDMS/DB Analyzer major error codes found in the CA IDMS Messages and Codes Guide or the list of DBIO error codes displayed above. If the third and fourth digits of the error code fall within the ranges 00-99, refer to the list of CA IDMS/DB Analyzer minor error codes found in the CA IDMS Messages and Codes Guide. Otherwise, refer to the list of CA DBIO Error Codes listed above.

STAT004E CURRENT RECORD WAS record-name

Reason: A DBIO error has occurred. The record indicated was the last one processed successfully before the error occurred.

Action: The required action depends on interpretation of the DBIO return code given in Message: STAT003E.

STAT005E CURRENT AREA WAS area-name

Reason: A DBIO error has occurred. The area indicated was the last one processed successfully before the error occurred.

Action: The required action depends on interpretation of the DBIO return code given in Message: STAT003E.

STAT006E ERROR SET WAS set- name

Reason: A DBIO error has occurred. The set indicated was the one being processed when the error occurred.

Action: The required action depends on interpretation of the DBIO return code given in Message: STAT003E.

STAT007E ERROR RECORD WAS record-name

Reason: A DBIO error has occurred. The record indicated was the one being processed when the error occurred.

Action: The required action depends on interpretation of the DBIO return code given in Message: STAT003E.

STAT008E ERROR AREA WAS area-name

Reason: A DBIO error has occurred. The area indicated was the one being processed when the error occurred.

Action: The required action depends on interpretation of the DBIO return code given in Message: STAT003E.

STAT009I STATISTICS ACCUMULATION COMPLETED SUCCESSFULLY

Reason: The accumulation of statistics has been successfully completed.

Action: None.

STAT010I DECOMPRESS ERROR FOUND ON RECORD WITH DBKEY=db-key

Reason: USNSTAT is unable to decompress a record that is defined in the subschema as compressed.

Action: Ignore statistics in these report fields: Savings Due to Compression, Occurrence Length (Decompressed), and Compression Bytes Saved. The data in these fields is inaccurate.

STAT011I DECOMPRESS STATISTICS ARE INVALID DUE TO A DECOMPRESS ERROR COUNT OF error-count

Reason: USNSTAT is unable to collect valid decompress statistics because it cannot decompress the problem records.

Action: Ignore statistics in these report fields: Savings Due to Compression, Occurrence Length (Decompressed), and Compression Bytes Saved. The data in these fields is inaccurate.

STAT012E CURRENT DBKEY......dbkey

Reason: A DBIO error has occurred. The value of the current db-key when the error occurred is indicated.

Action: The required action depends on interpretation of the DBIO return code given in Message: STAT003E.

STAT013E DIRECT DBKEY......dbkey

Reason: A DBIO error has occurred. The value of the direct db-key when the error occurred is indicated.

Action: The required action depends on interpretation of the DBIO return code given in Message: STAT003E.

STAT014E SUBSCHEMA CONTAINS AREAS WITH MIXED PAGE GROUPS OR MIXED RADIUS— NOT SUPPORTED

Reason: An attempt was made to ready an area with a different page group from those already readied.

Action: The database analyzer cannot be run against a subschema that contains mixed page groups or mixed radius.

SYNC001E MODULE VERSIONS DO NOT MATCH, CA IDMS/DB Analyzer release-number 1 module-name release-number 2

Reason: The release numbers of CA IDMS/DB Analyzer's main program (USNLYZR) and module name do not match. Release-number 1 and release-number 2 indicate the respective release numbers. This error usually occurs only if a new release of CA IDMS/DB Analyzer is partially installed over a prior release, or if two releases of CA IDMS/DB Analyzer 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 Analyzer is correctly installed and that the proper load or core-image libraries are used. Resubmit the job.