Previous Topic: ProcessingNext Topic: Informative Messages

Messages › Error Messages

Error Messages

E001

MINOR KEYWORD ERROR

Reason:

  1. Invalid minor keyword (or synonym) was submitted.
  2. Minor keyword was misspelled.

Action:

Correct keyword and resubmit job.

E002

MAJOR KEYWORD ERROR

Reason:

  1. Invalid major keyword (or synonym) was submitted.
  2. Major keyword was misspelled.

Action:

Correct keyword and resubmit job.

E003

KEYWORD TABLE MISSING

Reason:

Internal keyword table not found in program.

Action:

Contact Technical Support.

E004

LAST REQUEST CONTINUED...IGNORED

Reason:

Last parameter request card in job indicates continuation.

Action:

  1. Include additional parameter phrases after last card.
  2. Review last request card and remove continuation delimiter.

E005

PROCESS CARD MISSING OR INVALID

Reason:

  1. PROCESS card was not the first card in parameter file.
  2. No PROCESS card was included in job.
  3. PROCESS card contained syntactical errors.

Action:

  1. Check parameter file and make sure PROCESS card is first available card.
  2. Add a PROCESS card to Parameter file.
  3. Correct the PROCESS card syntax.

Note: Errors E006 through E019 cause processing to terminate if CONT=N in the PROCESS statement. If processing is terminated at the end of the parameter phase, message E020 is also generated.

If CONT=Y in the PROCESS statement, the error message is generated and processing continues, but the parameter in error is ignored.

E006

INVALID PARAMETER REQUEST

Reason:

An invalid parameter (or synonym) was requested.

Action:

Correct parameter (or synonym) and resubmit job.

E007

INVALID REPORT TYPE FOR SUPPRESS

Reason:

An invalid report type (or list number) was requested for suppression.

Action:

Correct report type (or list number) and resubmit job.

E008

EXCESSIVE REPORT REQUEST

Reason:

More than 20 report requests have been validated and accepted.

Action:

Delete excessive report requests and resubmit job.

E009

INVALID REPORT TYPE

Reason:

An invalid report type was requested.

Action:

Correct the report type and resubmit job.

E010

INVALID REPORT OPERAND

Reason:

  1. An invalid report operand was specified.
  2. A required report minor keyword is missing.

Action:

Correct report operand and resubmit job.

E011

INVALID REPORT DATE/TIME LIMITS

Reason:

  1. One of the limit fields is non-numeric.
  2. Start value is greater than the stop value.

Action:

Correct limit fields and resubmit job.

E012

PREVIOUS REPORT - ALL IN EFFECT

Reason:

A report request for all records has preceded this request for selected records.

Action:

The report request is ignored.

E013

NO VALID REPORT REQUESTS

Reason:

No valid report requests were accepted at the beginning of the Report phase.

Action:

Report processing is terminated immediately. Review PROCESS options and Report requests.

E014

EXCESSIVE DISPLAY REQUEST

Reason:

More than 20 display requests have been validated and accepted.

Action:

Delete excessive display requests and resubmit job.

E015

INVALID DISPLAY TYPE

Reason:

An invalid display type was requested.

Action:

Correct the display type and resubmit the job.

E016

INVALID DISPLAY OPERAND

Reason:

  1. An invalid display operand was specified.
  2. A required minor keyword is missing.

Action:

Correct display operand and resubmit job.

E017

INVALID DISPLAY DATE/TIME LIMITS

Reason:

  1. Start time, stop time, or interval is non-numeric.
  2. Start value is greater than the stop value.
  3. Month, day, hour, or minute is out of range.

Action:

Correct limit fields and resubmit job.

E018

INVALID DISPLAY - ALL IN EFFECT

Reason:

A display request for all records preceded this request for selected records.

Action:

The Display request is ignored.

E019

ALL OUTPUTS ARE SUPPRESSED

Reason:

At the end of the Parameter phase, a condition was detected where all extract records were suppressed and no valid display requests were accepted.

Action:

Processing is terminated immediately. Review SUPPRESS and Display requests.

E020

PROCESSING DISCONTINUED

Reason:

A parameter error was detected, and CONT=N was specified on the PROCESS card.

Action:

Examine other error messages generated prior to this message; correct problem and resubmit job.

E021

END-OF-FILE BEFORE FIRST BGIN

Reason:

An end-of-file condition was detected before the first BGIN record in the Archive Journal file.

Action:

None. The Archive Journal file is effectively null.

E022

UNKNOWN ARCHIVE RECORD TYPE

Reason:

At least one unknown Archive Journal record type was detected during the Extract phase. An incorrect tape may have been used for processing user journal records.

Action:

Select new tape and resubmit job; or contact Technical Support to report the existence of this situation.

E023

RUN UNIT TABLE ENTRY NOT FOUND

Reason:

Transaction information was not available during Extract phase, as expected. Processing is aborted immediately. This is usually an internal processing error.

Action:

For assistance, contact Technical Support at http://ca.com/support

E024

BGIN MATCHES RUN UNIT ENTRY

Reason:

During the Extract phase, the transaction number in a BGIN record matches that of a concurrently executing run-unit (that is, a second BGIN record was read for a transaction). This is usually due to reading an Archive Journal file that is out of sequence or that contains duplicates. Processing is aborted immediately.

Action:

Select a new tape and resubmit job; or contact Technical Support to report the existence of this problem.

E025

RUN UNIT TABLE OVERFLOW

Reason:

More than 100 concurrent transactions were encountered in the internal transaction table. Processing is aborted immediately. This is an internal limitation of CA IDMS Journal Analyzer.

Action:

Select a new tape and resubmit job; or contact Technical Support to report the existence of this problem.

E026

EXTRACT TABLE ENTRY ERROR

Reason:

An extract was created with an invalid extract type. Processing is aborted immediately. Usually this is due to reading an Extract file that was not created by CA IDMS Journal Analyzer.

Action:

For assistance, contact Technical Support at http://ca.com/support

E027

RELIDMS MUST BE ENTERED AS nn.nn

Reason:

Non-numeric data was entered for the RELIDMS parameter.

Action:

Enter a valid numeric value.

E028

PREVIOUS STEP WAS UNSUCCESSFUL

Reason:

ACA IDMS Journal Analyzer step was unsuccessful, but rather than abending, only a return code of 16 was provided because ABEND=N was specified.

Action:

Resolve error and rerun CA IDMS Journal Analyzer. If the error is not obvious, you may need to rerun CA IDMS Journal Analyzer with ABEND=Y to obtain a dump before calling the Technical Support.