Version 4.3.2
 —  Messages and Codes  —

Review 20xxx Messages

Overview of Messages

REV20001 | REV20002 | REV20003 | REV20004 | REV20005 | REV20011 | REV20012 | REV20013 | REV20014 | REV20015 | REV20016 | REV20017 | REV20018 | REV20019 | REV20020 | REV20021 | REV20022 | REV20023 | REV20024 | REV20025 | REV20026 | REV20027 | REV20028 | REV20029 | REV20030 | REV20031 | REV20032 | REV20033 | REV20034 | REV20035 | REV20036 | REV20037 | REV20038 | REV20039 | REV20040 | REV20041 | REV20042 | REV20043 | REV20044 | REV20045 | REV20046 | REV20047 | REV20048 | REV20049 | REV20050 | REV20051 | REV20052 | REV20053 | REV20054 | REV20055 | REV20056 | REV20061 | REV20062 | REV20063 | REV20101 | REV20102 | REV20103 | REV20104 | REV20105 | REV20106 | REV20107 | REV20108 | REV20120 | REV20121 | REV20124 | REV20125 | REV20126 | REV20128 | REV20129 | REV20130 | REV20141 | REV20142 | REV20146 | REV20147 | REV20148 | REV20149 | REV20150 | REV20151 | REV20152 | REV20153 | REV20154 | REV20155 | REV20156 | REV20157 | REV20158 | REV20159 | REV20160 | REV20161 | REV20162 | REV20163 | REV20164 | REV20165 | REV20166 | REV20185 | REV20186 | REV20187 | REV20190 | REV20191 | REV20192 | REV20232 | REV20233

REV20001 ERROR IN PARAMETERS AS FOLLOWS
Explanation:

An error was detected during the parameter processing phase of Review. All parameters are processed for further error diagnosis. However, no data is handled by the Review processor. This message is followed by one of the PRMnnn error messages shown below.

Message ID Message Text Explanation
PRM001 INVALID STATEMENT NAME FORMAT The format of the statement name (the first item of the parameter statement) is not correct.
PRM002 STATEMENT NAME MUST BE FOLLOWED BY A BLANK The basic syntax of the parameter statement requires a blank. The parameter processor cannot correctly identify the statement.
PRM003 UNIDENTIFIED STATEMENT NAME The parameter processor has located a statement name that is not valid.
PRM004 INVALID SEPARATOR A character other than a comma or an equal sign was used as a delimiter.
PRM007 INSUFFICIENT POSITIONAL PARAMETERS DEFINED More positional parameters were entered than were allowed.
PRM008 NULL VALUE INVALID FOR REQUIRED PARAMETER Values must be provided for all required parameters.
PRM009 UNIDENTIFIED KEYWORD An invalid keyword has been identified.
PRM010 LIST-FORMAT VALUE NOT ALLOWED Only a single value may be specified for the parameter.
PRM011 INVALID HEX DIGIT Hexadecimal digits must be 0-9 or A-F.
PRM012 LENGTH EXCEEDED The parameter supplied is longer than allowed.
PRM013 UNEXPECTED END-OF-FILE The parameter statements terminated prematurely. The parameter processor was expecting more input.
PRM014 PREMATURE END OF HEX VALUE A trailing quote was not supplied to terminate a hexadecimal value.
PRM015 INVALID CONTINUATION STATEMENT A statement has not been continued properly.
PRM016 PREMATURE END OF STATEMENT The current statement ended abnormally; a comma, parenthesis, or quote may be missing.
PRM017 INVALID CHARACTER IN NUMERIC PARAMETER VALUE Only the characters 0-9 are allowed in numeric fields.
PRM018 EXCESSIVE NUMERIC VALUE LENGTH The numeric value is too large for the parameter.
PRM019 INVALID PARAMETER VALUE The value specified is not allowed for this parameter.
PRM020 NUMERIC VALUE TOO LARGE FOR PROCESSING The numeric value is too large for the parameter to be processed.
PRM021 PARAMETER VALUE TRUNCATED Some parameter values were lost due to truncation.
PRM022 LIST SIZE EXCEEDED Too many entries have been specified in a list of values.
PRM023 REQUIRED PARAMETER MISSING A required parameter is missing; it must be provided before execution can proceed.
Action:

Correct the error and resubmit the job.


REV20002 INVALID FILE-TYPE
Explanation:

An invalid INPUT statement file-type parameter has been detected. Processing is discontinued.

Action:

Correct the error and resubmit the job.


REV20003 INVALID FILE-TYPE
Explanation:

An invalid INPUT statement file-type parameter has been detected. Processing is discontinued.

Action:

Correct the error and resubmit the job.


REV20004 PRIOR REPORT STATEMENT MISSING
Explanation:

A valid REPORT statement must precede all other parameter statements except the INPUT statement. Processing is discontinued.

Action:

Define a valid REPORT statement and resubmit the job.


REV20005 INVALID PRINTER LINE SIZE
Explanation:

The printer line size must be at least 72 positions and cannot exceed 4080 positions. Processing is continued.

Action:

Define a valid LINE SIZE statement and resubmit the job.


REV20011 INVALID FIELD NAME IN MINIMUM STATEMENT
Explanation:

The name must match one of the field names or alias names defined for the Adabas command log record.

Action:

The invalid field name is ignored. Processing is continued for the valid field names specified as positional parameters in this statement.


REV20012 INVALID FIELD NAME IN MAXIMUM STATEMENT
Explanation:

The name must match one of the field names or alias names defined for the Adabas command log record.

Action:

The invalid field name is ignored. Processing is continued for the valid field names specified as positional parameters in this statement.


REV20013 INVALID FIELD NAME IN AVERAGE STATEMENT
Explanation:

The name must match one of the field names or alias names defined for the Adabas command log record.

Action:

The invalid field name is ignored. Processing is continued for the valid field names specified as positional parameters in this statement.


REV20014 INVALID FIELD NAME IN PERCENT STATEMENT
Explanation:

The name must match one of the field names or alias names defined for the Adabas command log record.

Action:

The invalid field name is ignored. Processing is continued for the valid field names specified as positional parameters in this statement.


REV20015 INVALID FIELD NAME IN COST STATEMENT
Explanation:

The name must match one of the field names or alias names defined for the Adabas command log record.

Action:

The invalid field name is ignored. Processing is continued for the valid field names specified as positional parameters in this statement.


REV20016 INVALID FIELD USAGE FOR MINIMUM STATEMENT
Explanation:

The field name specified is not a numeric field.

Action:

The invalid field name is ignored. Processing is continued for the valid field names specified as positional parameters in this statement.


REV20017 INVALID FIELD USAGE FOR MAXIMUM STATEMENT
Explanation:

The field name specified is not a numeric field.

Action:

The invalid field name is ignored. Processing is continued for the valid field names specified as positional parameters in this statement.


REV20018 INVALID FIELD USAGE FOR SUM STATEMENT
Explanation:

The field name specified is not a numeric field.

Action:

The invalid field name is ignored. Processing is continued for the valid field names specified as positional parameters in this statement.


REV20019 INVALID FIELD USAGE FOR AVERAGE STATEMENT
Explanation:

The field name specified is not a numeric field.

Action:

The invalid field name is ignored. Processing is continued for the valid field names specified as positional parameters in this statement.


REV20020 INVALID FIELD USAGE FOR COST STATEMENT
Explanation:

The field name specified is not a numeric field.

Action:

The invalid field name is ignored. Processing is continued for the valid field names specified as positional parameters in this statement.


REV20021 INVALID FIELD USAGE FOR PERCENT STATEMENT
Explanation:

The field name specified is not a numeric field.

Action:

The invalid field name is ignored. Processing is continued for the valid field names specified as positional parameters in this statement.


REV20022 ACCOUNT STATEMENT INVALID FOR A DETAIL REPORT
Explanation:

The statement specified can only be used for summary reports.

Action:

The statement is ignored and processing continues. Specify this statement following a valid REPORT statement with TYPE=SUMMARY.


REV20023 SUM STATEMENT INVALID FOR A DETAIL REPORT
Explanation:

The statement specified can only be used for summary reports.

Action:

The statement is ignored and processing continues. Specify this statement following a valid REPORT statement with TYPE=SUMMARY.


REV20024 MINIMUM STATEMENT INVALID FOR A DETAIL REPORT
Explanation:

The statement specified can only be used for summary reports.

Action:

The statement is ignored and processing continues. Specify this statement following a valid REPORT statement with TYPE=SUMMARY.


REV20025 MAXIMUM STATEMENT INVALID FOR A DETAIL REPORT
Explanation:

The statement specified can only be used for summary reports. The statement is ignored and processing continues.

Action:

Specify this statement following a valid REPORT statement with TYPE=SUMMARY.


REV20026 AVERAGE STATEMENT INVALID FOR A DETAIL REPORT
Explanation:

The statement specified can only be used for summary reports. The statement is ignored and processing continues.

Action:

Specify this statement following a valid REPORT statement with TYPE=SUMMARY.


REV20027 PERCENT STATEMENT INVALID FOR A DETAIL REPORT
Explanation:

The statement specified can only be used for summary reports. The statement is ignored and processing continues.

Action:

Specify this statement following a valid REPORT statement with TYPE=SUMMARY.


REV20028 APPLYMOD nn HAS BEEN TURNED {ON | OFF} BY user-id
Explanation:

The applymod nn has been turned ON/OFF by the user user-id.

Action:

This message is for information only.


REV20029 INVALID COST VALUE
Explanation:

COST may be specified as field/operator/value, where valid operators are * (TIMES), + (PLUS), and - (MINUS). Fixed costs may be specified using the reserved word FIXED with an operator of @ (AT). Positive and negative values are allowed with or without a single imbedded decimal point.

Action:

A value of 0 is assumed. Correct the value and resubmit the job.


REV20030 INVALID COPY FILE-TYPE
Explanation:

An invalid COPY statement file-type parameter was detected.

Action:

The COPY statement is ignored and processing is continued. Correct the statement and resubmit the job if necessary.


REV20031 TERMINATION TASK ATTACHED SUCCESSFULLY
Explanation:

Termination task attached successfully.

Action:

This message is for information only.


REV20032 TERMINATION TASK NOT FOUND IN THE PROGRAM LIBRARY
Explanation:

Termination task not found in the program library.

Action:

Contact your Software AG technical support representative.


REV20033 I/O ERROR OCCURRED WHILE LOADING TERMINATION TASK
Explanation:

I/O error occurred while loading termination task.

Action:

Contact your Software AG technical support representative.


REV20034 SEVERE PARAMETER ERROR(S)
Explanation:

A parameter error of some significance was reported. All parameters are processed for further error diagnosis. However, the run is discontinued before any input data is processed.

Action:

Correct the error and resubmit the job.


REV20035 SEVERE PARAMETER ERROR(S)
Explanation:

A parameter error of some great significance has occurred. Parameter validation is terminated.

Action:

Correct the error and resubmit the job.


REV20036 REPORT DISCONTINUED DUE TO LIMIT PARAMETER
Explanation:

The report has been discontinued due to the LIMIT parameter. The LIMIT parameter on the report statement has been exceeded.

Action:

This message is for information only.


REV20037 SUMMARY REPORT EXCEEDS LINE SIZE
Explanation:

The number of printable characters for the report exceed the report line size.

Action:

Increase the report line size if possible or reduce the report data to be displayed.


REV20038 TERMINATION TASK INITIATED
Explanation:

Termination task initiated.

Action:

This message is for information only.


REV20039 OPEN OPERATION FAILURE ON PRINTER
Explanation:

An error occurred attempting to open the above file. When this occurs, processing is discontinued.

Action:

Correct the error and resubmit the job.


REV20040 OPEN OPERATION FAILURE ON COPY
Explanation:

An error occurred attempting to open the copy file. When this occurs, processing is discontinued.

Action:

Correct the error and resubmit the job.


REV20041 OPEN OPERATION FAILURE ON LOG INPUT
Explanation:

An error occurred attempting to open the log input file. When this occurs, processing is discontinued.

Action:

Correct the error and resubmit the job.


REV20042 OUTPUT ERROR ON PRINTER
Explanation:

An error occurred attempting to output to the printer file. When this occurs, processing is discontinued.

Action:

Correct the error and resubmit the job.


REV20043 OUTPUT ERROR ON COPY
Explanation:

An error occurred attempting to output to the copy file. When this occurs, processing is discontinued.

Action:

Correct the error and resubmit the job.


REV20044 CLOSE OPERATION FAILURE ON file-name
Explanation:

An error occurred while Review attempted to close the specified file.

Action:

This message is for information only.


REV20045 ADABAS RESPONSE CODE
Explanation:

A potentially severe Adabas error has occurred. The Adabas interaction was a result of the COPY statement with FILETYPE=ADABAS.

Action:

Processing is discontinued. Evaluate the significance of the Adabas error and perform the required action.


REV20046 INTERVAL STATISTICS TASK TERMINATING
Explanation:

Review detected that an EOJ command was issued to the Com-plete nucleus. Review terminates the interval task and starts the termination task.

Action:

This message is for information only.


REV20047 INTERVAL STATISTICS TASK STARTED
Explanation:

The Review Interval Statistics task has been started.

Action:

This message is for information only.


REV20048 NO INTERVAL STATISTICS RECORD FOUND
Explanation:

Review unsuccessfully attempted to load the interval statistics record from its system file.

Action:

Contact your Review administrator.


REV20049 xxxxxxxxxxxx WILL BE SAVED EVERY nnn MINS
Explanation:

The Review interval statistics task will save the data from the function or subsystem xxxxxxxxxxxx every nnn minutes.

Action:

This message is for information only.


REV20050 nnnnnnnn TASK ATTACHED SUCCESSFULLY
Explanation:

The Review task nnnnnnnn was attached successfully.

Action:

This message is for information only.


REV20051 NO DUMMY TID AVAILABLE FOR USE BY nnnnnnnn TASK
Explanation:

Review was unable to attach the nnnnnnnn task because no dummy TID was available for use by the attached program.

Action:

If this problem happens frequently, the system programmer responsible for Com-plete maintenance should be requested to increase the value of the NOTIBS keyword argument in the TIBTAB definition.


REV20052 nnnnnnnn TASK NOT FOUND IN THE PROGRAM LIBRARY
Explanation:

Review was unable to attach the nnnnnnnn task because the program to be attached was not found in the Com-plete program library dataset.

Action:

Request that the system programmer responsible for Com-plete catalog the program.


REV20053 I/O ERROR OCCURRED WHILE LOADING INTERVAL TASK
Explanation:

Review was unable to attach the interval task because an unrecoverable I/O error occurred while reading the Com-plete program library.

Action:

Contact your Software AG technical support representative.


REV20054 THE NAME OF THE PROGRAM TO BE ATTACHED IS NOT VALID
Explanation:

The Review master interval statistics task was unable to attach the interval task because the name of the program to be attached is not valid.

Action:

Contact your Software AG technical support representative.


REV20055 UNKNOWN RETURN CODE FROM ATTACH
Explanation:

The Review master interval statistics task was unable to attach the interval task because it received an unknown return code.

Action:

Contact your Software AG technical support representative.


REV20056 xxxxxxxxxxxxxxx TASK INCORRECTLY LINKED
Explanation:

The Review task has detected that

  • the module U2DENQ was not linked in; or

  • the incorrect version of U2DENQ was linked in.

Action:

Rerun the link job provided in the Review source library, ensuring that the JCL is correct.


REV20061 MASTER INTERVAL TASK ALREADY ACTIVE
Explanation:

An attempt was made to start the master interval statistics task but the task was already active.

Action:

Do not attempt to start the master interval task.


REV20062 TERMINATION TASK TERMINATED
Explanation:

The termination task has ended.

Action:

This message is for information only.


REV20063 error-type ERROR error-number OCCURRED ON LINE line-number OF PROGRAM program-name
Explanation:

An error has occurred while executing the specified program:

error-type = Command Processing
Logon Processing
Object Time
Non-correctable Syntax
Action:

Record message and contact your Software AG technical support representative.


REV20101 HISTORY FILE POPULATION STARTED
Explanation:

The Review history file task has been started.

Action:

This message is for information only.


REV20102 HISTORY FILE POPULATION COMPLETED
Explanation:

The Review history file task has completed execution.

Action:

This message is for information only.


REV20103 ADABAS RSP = rsp RECEIVED
Explanation:

The Review history file task received a non-zero Adabas response code.

Action:

Evaluate the severity of the response code and perform the required steps to resolve the problem.


REV20104 HISTORY TASK POSTED FOR WORK
Explanation:

The Review history file task has posted for work. This means that a detailed report with a COPY statement with FILETYPE=ADABAS is active and has selected data to write out to the Review history file.

Action:

This message is for information only.


REV20105 HISTORY TASK WAITING FOR WORK
Explanation:

The Review history file task is waiting for work.

Action:

This message is for information only.


REV20106 HISTORY TASK ERROR DURING FREEMAIN
Explanation:

The Review history file task received a nonzero return code attempting to free storage.

Action:

Contact your Software AG technical support representative.


REV20107 HISTORY TASK UNABLE TO OPEN RVUALT
Explanation:

An error has occurred while attempting to open the RVUALT file.

Action:

Verify that the JCL is correct and that the RVUALT file is available.


REV20108 CLOG TOO BIG, NO CLEX ATTACHED
Explanation:

The maximum length of a command log record is 32767 bytes, regardless of whether a CLEX is attached or not. In some cases ADALOG may issue command log records with almost the maximum possible size. In such cases, no CLEX can be attached for Adabas Review purposes, so Adabas Review does not display all fields.

This message is issued only one time.

Action:

Decrease the size of the command log records, for example, LOGRB=NO.


REV20120 REVIEW v.r.s RUNNING WITH ADABAS n.n
Explanation:

Adabas Review has been given control for the first time where v.r.s is the Review version and n.n is the Adabas version.

Action:

This message is for information only.


REV20121 ATTACH FOR REVIEW SUBTASK FAILED
Explanation:

Adabas Review attempted to attach an operating system subtask but received a nonzero return code from this action.

Action:

Examine the messages displayed by the operating system and correct the problem. The possibility exists that the address space, region, or partition was not large enough to attach the task, or the attached module RAOSREVW was not in the library concatenations so it could not be found to be loaded.


REV20124 ALLOCATION FOR REVIEW BUFFER POOL FAILED
Explanation:

Adabas Review unsuccessfully acquired storage for the Review buffer. The size of the buffer is determined by the BUFFER-SEGMENTS parameter on the Review INPUT statement.

Action:

Increase the size of the address space, region, partition, or virtual machine that Review is executing or decrease the size of the Review buffer.


REV20125 REVIEW SUBTASK SUCCESSFULLY ATTACHED
Explanation:

Adabas Review successfully attached an operating system subtask.

Action:

This message is for information only.


REV20126 REVIEW SUBTASK DETACHED
Explanation:

Adabas Review successfully detached an operating system subtask during its termination logic.

Action:

This message is for information only.


REV20128 ATTACH FOR HISTORY SUBTASK FAILED
Explanation:

Adabas Review attempted to attach an operating system subtask but received a nonzero return code from this action.

Action:

Examine the messages also displayed by the operating system and correct the problem. The possibility exists that the address space, region, or partition was not large enough to attach the task, or the attached module was not in the library concatenations so it could not be found to be loaded.


REV20129 HISTORY SUBTASK DETACHED
Explanation:

Adabas Review successfully detached an operating system subtask during its termination logic.

Action:

This message is for information only.


REV20130 HISTORY SUBTASK SUCCESSFULLY ATTACHED
Explanation:

Adabas Review successfully attached an operating system subtask.

Action:

This message is for information only.


REV20141 GETMAIN FOR SPARE AREA FAILED
Explanation:

This message indicates a specific phase of Review execution.

Action:

This message is for information only.


REV20142 RCSBINIT - REVIEW INITIALIZATION STARTED
Explanation:

This message indicates a specific phase of Review execution.

Action:

This message is for information only.


REV20146 RCSBSUM - SUMMARY PROCESSING
Explanation:

This message indicates a specific phase of Review execution.

Action:

This message is for information only.


REV20147 RCSBFINI - CALLED FOR TERMINATION
Explanation:

This message indicates a specific phase of Review execution.

Action:

This message is for information only.


REV20148 RCSBREIN - REINITIALIZATION
Explanation:

This message indicates a specific phase of Review execution.

Action:

This message is for information only.


REV20149 REVIEW IS OPERATIVE
Explanation:

This message indicates a specific phase of Review execution.

Action:

This message is for information only.


REV20150 FILE RVUALT CAN NOT BE OPENED
Explanation:

This is an internal error that rarely occurs.

Action:

Contact your Software AG technical support representative.


REV20151 NOW SWITCHING LOGS FROM clog-dataset1 TO clog-dataset2
Explanation:

A LOG switch is in progress. The FROM dataset can now be copied. The TO dataset will receive command log output.

Action:

This message is for information only.


REV20152 NOW IT'S TOO LATE TO COPY clog-dataset
Explanation:

The specified command log dataset is open for output. The command log can no longer be copied.

Action:

This message is for information only.


REV20153 RAOSAUTO SUBTASK DETACHED
Explanation:

The RAOSAUTO subtask has been detached successfully.

Action:

This message is for information only.


REV20154 AUTO REGENERATE STARTED
Explanation:

The RAOSAUTO automatic regeneration subtask started successfully.

Action:

This message is for information only.


REV20155 AUTO REGENERATE COMPLETED
Explanation:

The RAOSAUTO automatic regeneration subtask has completed successfully.

Action:

This message is for information only.


REV20156 RESPONSE CODE rsp FOR cmd COMMAND TO DBID= dbid ,FNR= fnr
Explanation:

The RAOSAUTO automatic regeneration subtask issued an Adabas call and received the response indicated in the message.

Action:

Verify that the LFILE/NTFILE statement for Review points to the correct DBID and FNR for the Review data file.


REV20157 GETMAIN FAILED
Explanation:

A request for a GETMAIN failed in RAOSSYDR.

Action:

Increase the region size for the Adabas task.


REV20158 DOING OPEN CALL BECAUSE OF RESP 9
Explanation:

The Review history task had to perform an OP (open) call during history data population because an Adabas response code 9 was encountered.

Action:

This message is for information only.


REV20159 FREEMAIN FAILED
Explanation:

A request for a FREEMAIN to RAOSSYDR failed.

Action:

Contact your Software AG technical support representative.


REV20160 HISTORY FILE POPULATION FAILED
Explanation:

An error was encountered during Review history file population and the history subtask was unable to continue.

Action:

Check additional warning messages issued by subtask.


REV20161 nnnnn ET COMMANDS WERE ISSUED
Explanation:

The number of ET commands issued by the Review history task was nnnnn. The ET commands were issued to synchronize history file population.

Action:

This message is for information only.


REV20162 LOAD FAILED FOR module-name
Explanation:

A request for a LOAD to RAOSSYDR failed. The requested module was not found in the STEPLIB.

Action:

Check the STEPLIB to be sure that the module is present.


REV20163 IMMEDIATE RECOVERY FOR RVUALT REQUIRED
Explanation:

The Review history task encountered an error during history file population and could not continue processing.

Action:

Copy the RVUALT data file to another sequential data file and reinitialize Review.


REV20164 OPEN FAILED FOR xxxxxxxx
Explanation:

A request for an OPEN for DD or file name xxxxxxxx to RAOSSYDR failed.

Action:

Check that the required DD card or filedef is present in the task job stream.


REV20165 THE VALUE OF FIELD field IS value
IT IS TOO BIG, trunc-value STORED INSTEAD.
Explanation:

When storing data into the history file it was detected that the value (value) of the field listed in the message (field) is bigger than the maximum field length allowed in the history file. Storing such a data can result in later Adabas response code 55. The value is therefore truncated (trunc-value) and stored instead.

Action:

Contact your Software AG support representative about this message to avoid this in the future.


REV20166 RECORD TO xxxxxxxx skipped, because > 32K
Explanation:

While writing a CLOG record, Adabas Review determined that the record was larger than 32767 bytes. Records larger than 32767 bytes are not written to the data set. The DD name or link name of the data set is given in the message (xxxxxxxx). This message is issued only one time.

Action:

Contact your Software AG technical support representative.


REV20185 UNABLE TO LOAD USER EXIT module-name - RC xx (xx)
Explanation:

The Review command log processor was unable to load the specified user exit module to copy Review command logs.

Action:

Ensure that the module exists in one of the libraries accessible by Review.


REV20186 ADAIOR function REQUEST FAILED
Explanation:

Internal error occurred.

Action:

Contact your Software AG technical support representative.


REV20187 FUNCTION function NO LONGER SUPPORTED BY INTERFACE
Explanation:

Internal error occurred.

Action:

Contact your Software AG technical support representative.


REV20190 USER PARM ERROR - text
Explanation:

A syntax error was recognized when file RVUFLD was read (custom reporting fields). Possible texts include the following:

CANNOT LOCATE USERFLD
        INVALID NAME PARAMETER
        INVALID INTYPE PARAMETER
        INVALID OUTTYPE PARAMETER
        INVALID HEADER PARAMETER
        INVALID ADANAME PARAMETER
        INVALID CALC PARAMETER
        PREVIOUS PARM LEN TOO LONG
        PREVIOUS PARM NOT NUMERIC
        DELIMITER <=>NOT FOUND
        KEYWORD MISSING OR NOT RECOGNIZED
Action:

Correct the syntax error and restart Adabas Review.


REV20191 ADABAS vrs not supported
Explanation:

The current Review version does not run with the Adabas version.

Action:

Check which Review version runs with your Adabas version.


REV20192 Only CLOGLAYOUT=5 supported
Explanation:

Review received erroneous CLOG records with CLOGLAYOUT not set to "5". Only CLOGLAYOUT=5 is supported.

Action:

Verify that the setting of the Adabas nucleus ADARUN CLOGLAYOUT parameter is 5.


REV20232 REPORT report-name status-message
Explanation:

One of the following status messages applied to the specified report:

DEACTIVATED DUE TO MAXSTORE LIMIT EXCEEDED

The specified active report stopped collecting data because all storage space allocated by the MAXSTORE parameter has been used.

DEACTIVATED DUE TO STORAGE ALLOCATION FAILURE
      

The specified active report stopped collecting data because no more storage is available in the address space/partition.

ENCOUNTERED STORAGE ALLOCATION FAILURE,
 REINITIALIZATION SCHEDULED

The specified active report stopped collecting data because no more storage is available in the address space/partition. All reports will be reinitialized.

DEACTIVATED DUE TO HASH TABLE MANAGER
INITIALIZATION ERROR

The specified active report could not collect data because of an error in the hash table manager.

DEACTIVATED DUE TO HASH TABLE MANAGER FIND ERROR

The specified active report could not collect data because of an error in the hash table manager.

DEACTIVATED DUE TO TERMINATION PROCESSING
STORAGE ALLOCATION FAILURE

The specified active report could not perform termination processing because no more storage is available in the address space/partition.

HISTORICAL DATA COLLECTION DEACTIVATED DUE TO
STORAGE ALLOCATION FAILURE

The specified report could not perform historical data collection because no more storage is available in the address space/partition.

Action:

Investigate the cause of the specific error. In the event of a failure in the hash table manager, contact your Software AG technical support representative.


REV20233 PARAMETER ERROR(S) ENCOUNTERED PROCESSING RVUEXI PARAMETER FILE
Explanation:

Parameter error(s) were encountered when Review was processing the RVUEXI parameter file specified in the Adabas start-up procedure.

Action:

Refer to the RVUEXP output file to determine the parameters that were in error and correct the specified parameters.


Top of page