Note: Although the action taken on some of the following messages indicates NONE, if any of these messages is generated, you can contact Technical Support for assistance in determining a remedy for the problem.
Reason:
An out-of-sequence file was detected during ABORT COINCIDENCE report processing.
Action:
Rerun the job. If this situation reoccurs, contact Technical Support.
Reason:
A non-zero sort return code was encountered during ABORT COINCIDENCE report processing.
Action:
Look at JASRTMSG for messages from SORT.
Reason:
An ENDJ or ABRT was missing for a transaction (COMT extract) during ACTIVITY report processing.
Action:
None.
Reason:
A BGIN extract was missing for an ENDJ/ABRT/COMT extract of the same transaction during ACTIVITY report processing.
Action:
None.
Reason:
An out-of-sequence condition was detected during ACTIVITY report processing.
Action:
Rerun the job. If this situation reoccurs, contact Technical Support.
Reason:
An ENDJ or ABRT was missing for a transaction (BGIN extract) during ACTIVITY report processing.
Action:
None.
Reason:
Multiple ENDJ/ABRT extracts were encountered for the same transaction during ACTIVITY report processing.
Action:
None.
Reason:
A non-zero sort return code was encountered during ACTIVITY report processing.
Action:
Look at JASRTMSG for messages from SORT.
Reason:
The program being reported had readied more than eight areas. This is a limitation for the current release of Journal Analyzer.
Action:
None.
Reason:
The program is not registered to any subschema.
Action:
Use IDD or IDMSDDDL to register the program to an appropriate subschema. You can find more information in Appendix D.
Reason:
No program name was indicated in the BYPASS statement.
Action:
Specify a program name to be bypassed during Data Extraction and Reporting phases.
Reason:
Only 10 BYPASS Program Names can be specified.
Action:
Remove the extra BYPASS statements.
Reason:
A non-zero return code resulted from an attempt to CALL the named program.
Action:
Ensure the named program exists in the STEPLIB or LIBDEF. SEARCH library. Ensure there is adequate memory in the region or partition.
Reason:
The prefix length was changed for a particular database record occurrence.
Action:
Investigate the possibility of a change in the schema/subschema.
Reason:
For a particular database record occurrence, either successive BFOR or AFTR images were encountered.
Action:
Produce a DATABASE KEY Display for the record in question to check for possible integrity error.
Reason:
A non-zero CA IDMS error status was returned. Possible function codes are:
This message is followed by normal IDMS-STATUS information. Processing terminates with an abend.
Action:
Based upon the particular ERROR-STATUS, resolve the problem according to normal CA IDMS error resolution techniques.
Reason:
A non zero return code resulted from an attempt to delete the named program from storage.
Action:
This should not occur. If it does, notify Technical Support.
Reason:
CA IDMS Presspack support is provided only where CA IDMS Presspack is used for both compression and decompression as indicated by a value of 'BT' in the CALL-TIME-040 field of the associated SRCALL-040 record.
Action:
None.
Reason:
CA IDMS Presspack support is provided only for records using the generic or BUILTIN Data Characteristic Table (DCT).
Action:
None.
Reason:
Either a CUSTOM DCT name or else BUILTIN Presspack compression must be used.
Action:
None.
Reason:
The display file created during the Extract Phase did not contain any records. Display processing terminates.
Action:
Ensure that your DISPLAY requests will find qualifying BFOR/AFTR records on the archive file.
Reason:
All of the records on the display file were ABRT records. These records are dropped during the first DISPLAY sort.
Action:
Ensure that your DISPLAY requests will find qualifying BFOR/AFTR records on the archive file.
Reason:
A non-zero sort return code was encountered during the initial display sort. DISPLAY processing terminates.
Action:
Look at JASRTMSG for messages from SORT.
Reason:
The display file created during the EXTRACT phase contained only ABRT records. Display processing is terminated.
Action:
Ensure that your DISPLAY requests will find qualifying BFOR/AFTR records on the archive file.
Reason:
A non-zero sort return code was encountered during the main display sort. DISPLAY processing terminates.
Action:
Look at JASRTMSG for messages from SORT.
Reason:
CA IDMS Journal Analyzer could not determine an area name from the DMCL associated with the given dbkey and page group values.
Action:
Review the DMCL to ensure it includes the appropriate area.
Reason:
Routine GSICVTDB has returned a non-zero status code to routine USJDSPO. Possible status codes are:
Action:
Ensure that the CA IDMS dictionary is for the same release as the archive file.
Reason:
Routine GSSMOVE has returned a non-zero status code to routine USJDSP0. Possible status codes are:
Action:
Status 01--Contact Technical Support.
Status 02--This can occur when a compressed, fragmented record is written to the journal without its fragments (as when only a pointer was changed) or when CA IDMS Journal Analyzer's recomposition of spanned or fragmented records was unsuccessful for any reason.
Reason:
A bad return code was received from the IDMSUNPS CA IDMS Presspack decompression routine.
Action:
Review the return code value received and contact Technical Support.
Reason:
Routine USJDSP1 has returned a non-zero status code to routine USJDSP0. Possible status codes are:
Action:
Ensure that the CA IDMS dictionary is for the same release as the archive file.
Reason:
Routine USJSEQF has returned a non-zero status code to routine USJDSP0.
Possible function codes are:
Possible status code is:
Action:
Run the job in a larger region/partition. If your environment is z/VSE, make more GETVIS available to the partition.
Reason:
An out-of-sequence condition was detected during CHRONOLOGICAL EVENT report processing.
Action:
Rerun the job. If this situation reoccurs, contact Technical Support.
Reason:
A non-zero sort return code was encountered during the extract file sort. EXTRACT process terminates with an abend.
Action:
Look at JASRTMSG for messages from SORT.
Reason:
The archive file must be in sequence. A record has been read in which the sequence number is less than the number in the previous archive record. The current and previous sequence numbers, as well as a count of records already processed, are shown.
Action:
Extract processing terminates. If multiple archive files have been defined for processing, ensure that they are defined in the sequence in which they were created.
Reason:
This informative message indicates the release of CA IDMS as entered on the PROCESS statement, or taken as a default. The archive file records were processed according to the format for that release.
Reason:
Function codes are:
Status codes are:
Action:
Provide additional MAIN/GETVIS storage and rerun the job.
Status code 24, ensure that GSSMOVE resides in your STEPLIB, and ensure that your region or partition size is sufficient. Correct, then resubmit the job.
Reason:
CA IDMS Journal Analyzer is designed to expect these record types on the archive file:
ABRT, AFTR, AREA, BFOR, BGIN, COMT, ENDJ, JSEG, TIME, CKPT, JHDA, JHDR, JHDS, USER, Dxxx Distributed Data Records
Action:
Record types other than those listed are counted (see message E022 and) and ignored.
Reason:
Routine USJSEQF has returned a non-zero status code to routine USJEXT0.
Possible function codes are:
Possible status code is:
Possible file names are EXTRACT and DISPLAY
Action:
Run the job in a larger region/partition. If your environment is z/VSE, make more GETVIS available to the partition.
Reason:
The Management Ranking file is out of sequence.
Action:
Rerun the job. If this situation reoccurs, contact Technical Support.
Reason:
The Management Ranking file is out of sequence.
Action:
Rerun the job. If this situation reoccurs, contact Technical Support.
Reason:
During Display processing for subschema view, either invalid or incomplete field descriptions have been encountered for a subscripted group in a program's subschema.
Action:
Review the corresponding schema and subschema; revise as needed, then resubmit the job.
Reason:
During Display processing for subschema view, an inconsistent processing condition has been detected.
Action:
Contact Technical Support.
Reason:
In the z/VSE environment, an optional technical Bulletin has been applied to cause CA IDMS Journal Analyzer to run with overlay phases. An attempt to load the indicated phase has failed. Possible codes are:
Action:
Ensure all steps required to run as an overlay have been successfully executed.
Reason:
An ENDJ or ABRT extract was missing for a transaction (COMT extract) during MANAGEMENT report processing.
Action:
None.
Reason:
A BGIN extract was missing for an ENDJ/ABRT/COMT extract of the same transaction during MANAGEMENT report processing.
Action:
None.
Reason:
An out-of-sequence condition was encountered during MANAGEMENT report processing.
Action:
Rerun the job. If this situation reoccurs, contact Technical Support.
Reason:
An ENDJ or ABRT extract was missing for a transaction (BGIN extract) during MANAGEMENT report processing.
Action:
None.
Reason:
Multiple ENDJ/ABRT extracts were encountered for the transaction during MANAGEMENT report processing.
Action:
None.
Reason:
A non-zero sort return code was encountered during MANAGEMENT Highlight Summary report processing.
Action:
Look at JASRTMSG for messages from SORT.
Reason:
A non-zero sort return code was encountered during MANAGEMENT Rank report processing.
Action:
Look at JASRTMSG for messages from SORT.
Reason:
A non-zero sort return code was encountered during MANAGEMENT Rank report processing.
Action:
Look at JASRTMSG for messages from SORT.
Reason:
A non-zero sort return code was encountered during MANAGEMENT Rank report processing.
Action:
Look at JASRTMSG for messages from SORT.
Reason:
An invalid MANAGEMENT Table entry was encountered.
Action:
None.
Reason:
This message appears in a record name field on a Journal Display.
Action:
See the NONUNIQ parameter.
Reason:
During DISPLAY processing for subschema view, a field with an OCCURS greater than 3 has been encountered. This is a violation of ANS COBOL specifications.
Action:
Review the corresponding schema and subschema for the selected program.
Note: The following PARM errors will cause processing to terminate if CONT=N was specified on the PROCESS card; otherwise, the erroneous parameter is ignored.
Reason:
The time interval present in one report request overlapped the time interval for another request of the same journal report type. All Management reports must be the same time period.
Entry 1 and entry 2 show the report type as well as the time intervals for the overlapping report requests.
Action:
None. (See note above.)
Reason:
The RECORD table, used to convert record IDs into record names, overflowed during extended parameter validation.
Action:
None. (See note above.)
Reason:
The RECORD table, used to convert record names into record IDs, overflowed during extended parameter validation.
Action:
None. (See note above.)
Reason:
The prefix length field of a journal archive record contains a value that is not evenly divisible by 4. This can occur if processing an archive of native VSAM records.
Action:
The prefix is processed as 4 byte db-keys. The odd portion of the prefix is ignored.
Reason:
CA IDMS Journal Analyzer has an internal limit of only being able to DISPLAY 64 record prefix dbkeys in subschema view.
Action:
None.
Reason:
An ENDJ or ABRT extract was missing for a transaction (COMT/AREA extract) during PROGRAM report processing.
Action:
None.
Reason:
A BGIN extract was missing for an ENDJ/ABRT/COMT/AREA extract of the same transaction during PROGRAM report processing.
Action:
None.
Reason:
An out-of-sequence condition was detected during PROGRAM report processing.
Action:
Rerun the job. If this situation reoccurs, contact Technical Support.
Reason:
An ENDJ or ABRT extract was missing for a transaction (BGIN extract) during PROGRAM report processing.
Action:
None.
Reason:
A probable out-of-sequence condition was detected during PROGRAM report processing.
Action:
None.
Reason:
Multiple ENDJ/ABRT extracts were encountered for the same transaction during PROGRAM report processing.
Action:
None.
Reason:
A probable out-of-sequence condition was detected during PROGRAM report processing (Program Summary).
Action:
None.
Reason:
A probable out-of-sequence condition was detected during PROGRAM report processing (Program Highlights).
Action:
None.
Reason:
A non-zero sort return code was encountered during PROGRAM report processing.
Action:
Look at JASRTMSG for messages from SORT.
Reason:
An inconsistent condition has been detected during the building or searching of the Record Attribute Table.
Action:
None.
Reason:
A subscripted structure is greater than can be accommodated by an internal table.
Action:
None.
Reason:
An inconsistent condition has been detected during the building of the Field Attribute Table. One cause is that the record was not found in the subschema.
Action:
A full view of the AFTR image is displayed.
Reason:
A program was not registered to a subschema.
Action:
You can find more information in Appendix D.
Reason:
The data in a BFOR image does not match data in the preceding AFTR image, although both images are for the same database key.
Action:
Reason:
A BFOR image was not followed by a AFTR image for an non-ERASE verb.
Action:
Produce a DATABASE KEY Display for the record occurrence in question.
Reason:
The file handler program GSSFILE encountered an error when attempting an I/O operation on the associated file. The 'function' indicates the specific type of operation either OPEN, CLOSE, READ, or WRITE. The return codes n1, n2, n3, and n4 denotes the specific file return codes.
Action:
Review the file return codes table to determine the reason that the error occurred.
Return Codes:
This message contains the following return codes:
Reason: End-of-File
Action: Contact Technical Support.
Reason: Open error or file is not open
Action: Look for JCL errors or for the use of improper files.
Reason: An I/O error has occurred
Action: Find cause for I/O error.
Reason: Request not recognized
Action: Contact Technical Support.
Reason: File was already opened
Action: Contact Technical Support.
Reason: Parameter list error
Action: Contact Technical Support.
Reason: VSAM error:
n1=R15 return code from VSAM
n2=low order byte from R0
GENCB/MODCB type of error
n3=VSAM feedback byte error in I/O request
Action: Use n1, n2, and n3 to check for possible user errors. If there are no user errors, contact Technical Support.
Reason: Insufficient storage
Action: Increase storage for job step.
Reason: SYNAD error occurred:
n1=byte 1 of DECB
n2=byte 2 of DECB
n3=byte 3 of DECB
Action: Examine your BDAM files.
Reason: BPAM FIND ERROR
n1=R15
n2=R0
Action: Use n1 and n2 (as described in Data Management Macro Instructions) to check for errors.
Reason: BPAM STOW error:
n1=R15
n2=0
Action: Use n1 and n2 (as described in Data Management Macro Instructions) to check for error.
Reason:
n4=8, use of unopened file
n4=24, parameter list error
Action: Contact Technical Support.
Reason: JCL/label overrode parm list
Action: Remove DCB information from JCL and ensure that the correct files are referenced.
Reason: Parm list overrode JCL/label
Action: Remove DCB information from JCL and ensure that the correct files are referenced.
Reason: Unrecognized request
Action: Contact Technical Support.
Reason: OS x13 ABEND trapped at open
Action: Fix cause for x13 ABEND.
Reason: Tried to update seq. file
Action: Contact Technical Support.
Reason: VSAM write at other than load
Action: Contact Technical Support.
Reason: SOS table could not expand
Action: Contact Technical Support.
Reason: OS DCB open failed
Action: Contact Technical Support.
Reason: SOS table buffer pointer lost
Action: Contact Technical Support.
Reason: SOS table file CB not built
Action: Contact Technical Support.
Reason: OS DD statement Missing
Action: Supply missing DD Action: statement.
Reason: VSAM ACB open failed
Action: Contact Technical Support.
Reason: Record format invalid
Action: Contact Technical Support.
Reason: Macro format invalid
Action: Contact Technical Support.
Reason: Record length not numeric
Action: Contact Technical Support.
Reason: Record length too large
Action: Contact Technical Support.
Reason: Block size not numeric
Action: Contact Technical Support.
Reason: Block size too large
Action: Contact Technical Support.
Reason: Invalid DOS sysname table
Action: Assemble a valid sysname table.
Reason: DOS sysname table entry missing
Action: Assemble a sysname table with an entry for the missing one.
Reason: DOS LU number too large
Action: Use an LU number within range.
Reason: DOS sysname is not numeric or is misspelled
Action: Correct to a valid sysname.
Reason: DOS sysname blank
Action: Do not use blank sysname.
Reason: DOS LU not assigned
Action: Contact Technical Support.
Reason: DOS DTF prototype missing
Action: Contact Technical Support.
Reason: DOS logic module missing
Action: Generate missing logic module.
Reason: DOS CCW mismatch
Action: Contact Technical Support
Reason: File is not a PDS
Action: Allocate file to a PDS.
|
Copyright © 2014 CA.
All rights reserved.
|
|