CA IDMS Log Analyzer Error Messages are prefixed by an Ennn number. The following list provides an explanation of each message that includes a possible cause for the message and the suggested action to be taken by the user to correct the problem.
Reason:
Probable JCL error or Z/VSE I/O module has not been generated correctly. Processing terminates with an abend.
Action:
Correct and resubmit the job. See Table 6-1 for explanation and appropriate action for the return codes indicated.
Reason:
A temporary file has been deleted prematurely. Processing terminates with an abend.
Action:
Correct and resubmit the job. See Table 6-1 for explanation and appropriate action for the return codes indicated.
Reason:
Probable JCL error or Z/VSE I/O module has not been generated correctly. Processing terminates with an abend.
Action:
Correct and resubmit the job. See Table 6-1 for explanation and appropriate action for the return codes indicated.
Reason:
Probable JCL error or Z/VSE I/O module has not been generated correctly. Processing terminates with an abend.
Action:
Correct and resubmit the job. See Table 6-1 for explanation and appropriate action for the return codes indicated.
Reason:
A minor keyword was misplaced or misspelled. The specific input that was not recognized is printed.CA IDMS Log Analyzer ignores the invalid text and skips to the next valid Keyword. Processing continues unless CONT=NO was specified.
Action:
Correct the parameter and resubmit.
Reason:
A major keyword was misplaced or misspelled. The specific input that was not recognized is printed.CA IDMS Log Analyzer ignores the invalid text and skips to the next valid keyword. Processing continues unless CONT=NO was specified.
Action:
Correct the parameter and resubmit.
Reason:
A parameter statement with a trailing comma was followed by a parameter with a new major keyword or the parameter was the final statement in the input. Parameter is accepted as entered unless CONT=NO was specified.
Action:
Correct the parameter and resubmit.
Reason:
CA IDMS Log Analyzer load module is incomplete. Processing terminates with an abend.
Action:
Confirm that CA IDMS Log Analyzer was properly installed and reinstall as necessary.
Reason:
The value entered for a keyword was unacceptable to CA IDMS Log Analyzer. The specific problem is noted in the text. CA IDMS Log Analyzer ignores invalid keyword and skips to the next valid keyword. Processing continues unless CONT=NO was specified.
Action:
Correct the parameter and resubmit.
Reason:
More than twenty (20) valid report parameters have been encountered. The first twenty (20) parameters are processed unless CONT=NO was specified.
Action:
Eliminate the excess parameter statements.
Reason:
All report requests entered were invalid. Processing terminates with an abend.
Action:
Correct the requests and resubmit.
Reason:
First record on the log archive file was not of a known log type. Processing terminates with an abend.
Action:
Supply a correct file and resubmit.
Reason:
An internally requested sort has ended improperly. Processing terminates with an abend. Message text lists the return code received from the sort, the name of the CA IDMS Log Analyzer module that requested the sort and the number of the sort within that module (if the module does more than one sort).
Action:
Based on sort message content, correct the problem and resubmit.
Reason:
A report request was submitted for an unrecognized report. Message text lists the unrecognized report.CA IDMS Log Analyzer ignores an invalid request and skips to the next valid request. Processing continues unless CONT=NO was specified.
Action:
Correct the request and resubmit.
Reason:
The Log file was created without specifying STATISTICS TASK WRITE in the central version (CV) sysgen.
START, STOP, NAME, etc. parameters found no matching Archive Log Records.
The database log was used as input.
Processing terminates by forcing an abend.
Action:
Check the I006 messages for record types 6-02 and 6-03. If none of these record types are present, ensure that the CV was generated with STATISTIC TASK WRITE. Additionally, if CA IDMS Task Analyzer is installed, ensure that DC STATISTICS Y is specified on USFAOPT.
Change the selection parameter or supply a different Archive Log File.
Change the JCL to specify a proper log file for input. See Note 4 in the chapter “Operations”.
Reason:
CA IDMS Log Analyzer must have input parameters. The input parameter file is empty. Processing terminates by forcing an abend.
Action:
Supply an input parameter file that contains valid CA IDMS Log Analyzer parameter statements.
Reason:
CA IDMS Log Analyzer must have a PROCESS parameter. The input parameter file did not contain one. Processing terminates by forcing an abend.
Action:
Supply an input parameter file that contains a valid CA IDMS Log Analyzer PROCESS parameter statement.
Reason:
A required delimiter has not been found following a keyword. The PROCESS keyword must not be followed by an equal (=) sign. All other keyword phrases are composed of a major keyword, an equal (=) sign, and a minor keyword or variable data. CA IDMS Log Analyzer ignores invalid keyword and skips to the next valid keyword. Processing continues unless CONT=NO was specified. Text contains the specific input that caused the problem.
Action:
Correct the problem and resubmit.
Reason:
Mutually exclusive keywords or keyword values have been entered.CA IDMS Log Analyzer ignores the conflicting keyword or value and skips to the next valid keyword. Processing continues unless CONT=NO was specified.
Action:
Correct the problem and resubmit.
Reason:
GSSCVDT was called to convert a date from/to a Gregorian format. The non-zero return code is shown. Possible functions are:
Possible return codes are:
Processing terminates by forcing an abend.
Action:
An internal error has occurred. Contact CA Product Support.
Reason:
GSSCALL was called to invoke program-name. The non-zero return code is shown. Possible return codes are:
Processing terminates by forcing an abend.
Action:
For return code 8 or 12, make the appropriate change to the JCL and rerun. For return code 4 or 16, contact Technical Support.
|
Copyright © 2014 CA.
All rights reserved.
|
|