Adabas Review 20xxx Messages

#### Search Results

Search

# Adabas Review 20xxx Messages

### Overview of Messages

`REV20001 | REV20002 | REV20003 | REV20004 | REV20005 | REV20007 | REV20008 | REV20010 | 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 | REV20109 | REV20110 | REV20111 | REV20112 | REV20113 | REV20114 | REV20115 | REV20118 | REV20119 | REV20120 | REV20121 | REV20122 | REV20123 | REV20124 | REV20125 | REV20126 | REV20127 | REV20128 | REV20129 | REV20130 | REV20141 | REV20142 | REV20143 | REV20144 | REV20145 | REV20146 | REV20147 | REV20148 | REV20149 | REV20150 | REV20151 | REV20152 | REV20153 | REV20154 | REV20155 | REV20156 | REV20157 | REV20158 | REV20159 | REV20160 | REV20161 | REV20162 | REV20163 | REV20164 | REV20165 | REV20166 | REV20167 | REV20180 | REV20184 | REV20185 | REV20186 | REV20187 | REV20189 | REV20190 | REV20191 | REV20192 | REV20199 | REV20229 | REV20230 | REV20231 | REV20232 | REV20233 | REV20234 | REV20235 | REV20236 | REV20237 | REV20238 | REV20239 | REV20241 | REV20253 | REV20255 | REV20257 | REV20258 | REV20259 | REV20260 | REV20261 | REV20262 | REV20263 | REV20300 | REV20301 | REV20302 | REV20303 | REV20304 | REV20309 | REV20310 | REV20311 | REV20312 | REV20313 | REV20314`

REV20001 | Error in parameters as follows
Explanation | An error was detected during the parameter processing phase of Adabas Review. All parameters are processed for further error diagnosis. However, no data is handled by the Adabas 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.
PRM024 | Parameter mutually exclusive to one of the other parameters | A specified parameter is mutually exclusive with one of the other specified parameters; only one of the mutually-exclusive parameters may be specified.
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 255 positions. Processing is continued with the default size of 133.
Action | To avoid the usage of the default and this message, define a valid LINE SIZE statement and resubmit the job.

REV20007 | Detail report exceeds line size
Explanation | The number of printable characters for the report exceeds the report line size.
Action | Increase the report line size if possible, or reduce the report data to be displayed.

REV20008 | INVALID FIELD NAME IN DISPLAY STATEMENT fieldname
Explanation | The field fieldname is not allowed in a DISPLAY statement.
Action | The report will be started without this field. The field name is either spelled incorrectly, or the field is not allowed for this TYPE of CLASS of report.

REV20010 | Invalid field name in 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.

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 | Sever 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 Adabas Review attempted to close the specified file.
Action | This message is for information only.

REV20045 | YYYY-MM-DD hh:mm:ss ADABAS RESPONSE CODE rrr/sssss
Explanation | A non-zero Adabas response code with subcode sssss has occurred during writing of the Adabas Review history file. In Review batch this was the result of the interaction with Adabas because of the COPY statement with FILETYPE=ADABAS.
Action | In the case of response 148, the history records will be stored on RVUALT file if this is specified in the Hub JCL. In the case of response 9, the Review Hub will do an OP command and re-execute the command. In the case of any other response code, the data will not be written to the Review history file, but the processing of the report will continue. As long as the reason for the error is not repaired, the following write to the Review history file might end in the same error.

REV20046 | Interval statistics task terminating
Explanation | Adabas Review detected that an EOJ command was issued to the Com-plete nucleus. Adabas Review terminates the interval task and starts the termination task.
Action | This message is for information only.

REV20047 | Interval statistics task started
Explanation | The Adabas Review Interval Statistics task has been started.
Action | This message is for information only.

REV20048 | No interval statistics record found
Explanation | Adabas Review unsuccessfully attempted to load the interval statistics record from its system file.
Action | Contact your Adabas Review administrator.

REV20049 | xxxxxxxxxxxx will be saved every nnn mins
Explanation | The Adabas 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 Adabas Review task nnnnnnnn was attached successfully.
Action | This message is for information only.

REV20051 | No dummy TID available for use by nnnnnnnn task
Explanation | Adabas 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 | Adabas Review was unable to attach the nnnnnnnn task because the program to be attached was not found in the Com-plete program library data set.
Action | Request that the system programmer responsible for Com-plete catalog the program.

REV20053 | CLASS=CLIENT only in hub mode allowed
Explanation | The CLASS parameter was invalidly set to "CLIENT" in Adabas Review local mode for automatically started reports. You can only set the CLASS parameter to "CLIENT" in hub mode. Adabas Review processing continues, but the report is treated as a non-client report.
Action | Remove the CLASS=CLIENT specification from the parameters in Adabas Review local mode.

REV20054 | TARGET=0 not allowed
Explanation | This message is produced in the RVUPRT00 member as an error message when the target database ID is zero, blank, or unassigned in the REVUAUT1 or RVUAUT2 file. Blank or unassigned targets default to a value of zero. Targets of zero are not allowed in autostarted reports.
Action | Update the TARGET parameter setting with a valid database ID.

REV20055 | Unknown return code from attach
Explanation | The Adabas 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 Adabas 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 Adabas 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 Adabas Review history file task has been started.
Action | This message is for information only.

REV20102 | History file population completed
Explanation | The Adabas Review history file task has completed execution.
Action | This message is for information only.

REV20103 | Adabas RSP = rrr SUB sssss received
Explanation | The Adabas Review history file task received a non-zero Adabas response code rrr with subcode sssss.
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 Adabas 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 Adabas Review history file.
Action | This message is for information only.

REV20105 | History task waiting for work
Explanation | The Adabas Review history file task is waiting for work.
Action | This message is for information only.

REV20106 | History task error during FREEMAIN
Explanation | The Adabas 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 | dbid Review suspended, buffer unavailable
Explanation | REVIEW local mode is experiencing a temporary buffer shortage. CLOG records cannot be sent to the sub task REVIEWB. They are skipped until message REV20109 indicates that buffers are again available.
Action | Try to find the reason of buffer shortage.

REV20109 | dbid Review resumed, nn CLOG records skipped
Explanation | Buffers have become available after the shortage noted by message REV20108. The number of CLOG records skipped during the shortage is given in the message (nn).
Action | Try to find the reason of buffer shortage.

REV20110 | Corrupted length arrived from Natural. Length truncated to 65535
Explanation | A corrupted length value arrived in the format buffer of a search buffer from Natural. The corrupted length value is truncated to 65535.
Action | Contact your Software AG technical support representative for assistance in resolving the problem.

REV20111 | SVC number nnn is invalid
Explanation | An invalid SVC number was used (for example, in the history file definition). The Adabas call will not be executed.
Action | Specify a valid SVC number for the Adabas call.

REV20112 | RAOSSORT internal error
Explanation | An internal error occurred in the Adabas Review sort routine RAOSSORT. The sum of offset and length for sorted data is too big. The sort request is not performed.
Action | Contact your Software AG technical support representative to obtain a fix for this error.

REV20113 | Sort option SUMFIELD not permitted.
Explanation | The sort option, SUMFIELD, was specified for a report, but there are no summary fields in the report.
Action | Remove the SUMFIELD sort option from the report or specify summary fields for the report. Then try again.

REV20114 | Sort option SUMFIELD not permitted Report name: rptname
Explanation | The sort option, SUMFIELD, was specified for a report, but there are no summary fields in the report.
Action | Remove the SUMFIELD sort option from the report or specify summary fields for the report. Then try again.

REV20115 | Field fn does not fit into report rrrr
Explanation | The field listed in the message (fn) is a valid field name, but it does not fit into the printed report or history file, because the record length is not big enough. As a result, the field is empty in the report or history file. rrrr is the report name truncated to 29 characters.
Action | Omit this field or increase the record size.

REV20118 | RVUAUT1 selected. RVUAUT2 selected.
Explanation | The user has to specify two data definition job control statements
    //RVUAUT1 DD ...
or
    //RVUAUT2 DD ...
This message tells the user which statement is selected by Adabas Review.
Action | This message is for your information only.

REV20119 | Catastrophic error, no registers available, check dump.
Explanation | An abend occurred, the REVIEW Estae got control, but the data were corrupted so completely that the ESTAE cannot continue its work.
Action | This message is for your information only. Check the dump to find the error. Contact your Software AG technical support representative.

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 Adabas 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.

REV20122 | REV20122 - Adabas Review ESTAE exit driven. REV20122 - ADABAS REVIEW now disabled. REV20122 - ABEND 000xx000 PSW xxxxxxxx xxxxxxxx REV20122 - R0 xxxxxxxx - R1 xxxxxxxx - R2 xxxxxxxx - R3 xxxxxxxx REV20122 - R4 xxxxxxxx - R5 xxxxxxxx - R6 xxxxxxxx - R7 xxxxxxxx REV20122 - R4 xxxxxxxx - R9 xxxxxxxx - R10 xxxxxxxx - R11 xxxxxxxx REV20122 - R12 xxxxxxxx - R13 xxxxxxxx - R14 xxxxxxxx - R15 xxxxxxxx REV20122 - Dump has been taken.
Explanation | The main task of Adabas Review had an abend. The REVIEW ESTAE got control and issued these messages and was forced to write a dump. The Adabas nucleus will continue working, but Review will be disabled.
Action | This message is for your information only. Check the dump to find the error. Contact your Software AG technical support representative.

REV20123 | ESTAE driven recursively.
Explanation | The REVIEW ESTAE is called a second time, although REVIEW should run disabled.
Action | This message is for your information only. Check the dump to find the error. Contact your Software AG technical support representative.

REV20124 | Allocation for Review buffer pool failed
Explanation | Adabas Review unsuccessfully acquired storage for the Adabas Review buffer. The size of the buffer is determined by the BUFFMB parameter on the Adabas Review INPUT statement.
Action | Increase the size of the address space, region, partition, or virtual machine that Adabas Review is executing or decrease the size of the Adabas 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.

REV20127 | REV20127 - ADABAS REVIEW forced abnormal termination. REV20127 - R0 - nnnnnnnn R1 - nnnnnnnn R2 - nnnnnnnn R3 - nnnnnnnn REV20127 - R4 - nnnnnnnn R5 - nnnnnnnn R6 - nnnnnnnn R7 - nnnnnnnn REV20127 - R8 - nnnnnnnn R9 - nnnnnnnn RA - nnnnnnnn RB - nnnnnnnn REV20127 - RC - nnnnnnnn RD - nnnnnnnn RE - nnnnnnnn RF - nnnnnnnn
Explanation | The Review subtask REVIEWB or the Review batch module REVIEWB found an internal serious error. REVIEWB is disabled.
Action | This message is for your information only. Check the dump to find the error. Contact your Software AG technical support representative.

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 Adabas Review execution.
Action | This message is for information only.

REV20142 | RCSBINIT - Review initialization started
Explanation | This message indicates a specific phase of Adabas Review execution.
Action | This message is for information only.

REV20143 | Storage available: nnnn Storage allocated: nnnn Storage free: nnnn
Explanation | Depending on the message text given, the following applies:
Message | Explanation | Action
--- | --- | ---
Storage available: nnnn | The value nnnn is 90% of the value displayed in the z/OS control block field LDAELIM. This value is calculated by the trans-port routines. If the value is zero, for instance in non-transport case, all REV20143 are not issued. | These values are generated by Review internal processes, and are informational only.
Storage allocated: nnnn | The value nnnn is the value found in the z/OS control block field LDAELOAL. | If the value is too big, try to find out, who allocated that storage.
Storage free: nnnn | The value nnnn is the difference of the above two values. This value shows the additional buffer space for trans-port. | If the value is too low, try to find out why it is too low. When this value approaches to zero, CLOG records sent to the REVIEW hub are skipped.

REV20144 | Trans-Port activity Records queued qnn Records skipped snn
Explanation | This message displays the number of records from clients that have been queued (qnn) and skipped (snn) via Trans-Port to the Adabas Review hub. Records are skipped when no storage is available to send them to the hub
Action | To resolve the storage problem, you might choose to increase the number of attached buffers (NAB ADARUN parameter) used during the Adabas Review session.

REV20145 | Free main error, length is zero
Explanation | An internal error occurred freeing storage; a length of zero is requested.
Action | Contact your Software AG technical support representative for assistance.

REV20146 | RCSBSUM - summary processing
Explanation | This message indicates a specific phase of Adabas Review execution.
Action | This message is for information only.

REV20147 | RCSBFINI - called for termination
Explanation | This message indicates a specific phase of Adabas Review execution.
Action | This message is for information only.

REV20148 | RCSBREIN - reinitialization
Explanation | This message indicates a specific phase of Adabas Review execution.
Action | This message is for information only.

REV20149 | Review is operative
Explanation | This message indicates a specific phase of Adabas 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 data set can now be copied. The TO data set will receive command log output.
Action | This message is for information only.

REV20152 | Now it's too late to copy output-data set
Explanation | The specified output data set is open for output. The data in this data set can no longer be copied.
Action | No action is required for this informational message. It can be switched on or off by applying the optional zap RY4rs003, where r is the release number and s is the system maintenance level of your Adabas Review installation.

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 Adabas Review points to the correct DBID and FNR for the Adabas Review data file.

REV20157 | GETMAIN failed
Explanation | A request for a GETMAIN failed in RAOSSYDR. The Adabas task (in hub mode) or the Adabas Review task (in local mode) will be shut down immediately.
Action | Increase the region size for the Adabas task.

REV20158 | Doing open call because of Resp 9
Explanation | The Adabas Review history task had to perform an OP (open) call during history data population because an Adabas response code 9 (ADARSP009) 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 Adabas 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 Adabas 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 Adabas 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 Adabas 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 fieldname 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 (fieldname) is bigger than the maximum field length allowed in the history file. Storing such a data can result in later Adabas response code 55 (ADARSP055). 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.

REV20167 | Big amount of storage requested.
Explanation | More than 2 GB of storage was erroneously requested.
Action | Determine why such a large amount of storage was erroneously requested. If the problem persists, contact your Software AG technical support representative for assistance.

REV20180 | Requested buffer too big.
Explanation | An amount of requested storage is too large.
Action | Determine why such a large amount of storage was erroneously requested and who requested it. If the problem persists, contact your Software AG technical support representative for assistance.

REV20184 | Command log records selected: nnnnnnnnnnn
Explanation | This message is issued at shut down of REVIEW. It displays the number of command log records arriving the sub task REVIEWB.
Action | No action is required for this informational message.

REV20185 | Unable to load user exit module-name - RC xx (xx)
Explanation | The Adabas Review command log processor was unable to load the specified user exit module to copy Adabas Review command logs.
Action | Ensure that the module exists in one of the libraries accessible by Adabas 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.

REV20189 | nnnnnnnnnn Command log record(s) skipped.
Explanation | The number of records which were not sent to subtask REVIEWB because they were sent from the history feature is given in the message (nnnnnnnnnn).
Action | If this database contains a history file, no action is required for this informational message. If this database does not contain a history file, determine why history records are being sent to this database.

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 | In local mode when Adabas Review is called by Adabas, the Adabas Review nucleus verifies that the Adabas version is for a compatible version. If it is incompatible, this message appears. This message identifies the incompatible version of Adabas (vrs). The connection between the two products will not work, and Adabas Review will not collect any data.
Action | Call compatible versions of Adabas Review from the Adabas nucleus. For information about version compatibility, read Adabas and Adabas Review Version Compatibility, in the Adabas Review Release Notes.

REV20192 | Only CLOGLAYOUT=8 supported
Explanation | Adabas Review received erroneous CLOG records with CLOGLAYOUT not set to "8". Only CLOGLAYOUT=8 is supported.
Action | In this version of Adabas, only CLOGLAYOUT 8 should be produced. Check the version of Adabas that is being used.

REV20199 | Old CLEX from prior ADA V vr arrived and will be converted
Explanation | Adabas Review received a call from an Adabas version v.r (or earlier) database. The internal structure of the CLEX is converted to the new format of the CLEX.
Action | No action is required for this informational message.

REV20229 | Corrupted record skipped
Explanation | When analyzing command log records with batch program REVIEWB, corrupted command log records may occur. Instead of abending the batch job, the record is skipped and the message REV20229 is issued. The number of these messages is limited to 20 messages.
Action | Find out why there are corrupted command log records. This may involve editing the CLOG and manually looking for inconsistencies. For REVIEW this message is for information only.

REV20230 | Number of corrupted record skipped: nnnnnn
Explanation | This message is issued after the sequence of skipped records with message REV20229 is finished.
Action | This message is for information only. See also action for REV20229.

REV20231 | Report interval reached report-name
Explanation | The report named in the message (report-name) was suspended because the time interval specified in the Review Option screen or in the RVUAUT1/2 data set was reached.
Action | No action is required for this informational message. It can be switched on or off by applying the optional zap RY4rs003, where r is the release number and s is the system maintenance level of Adabas Review you have installed.

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 Adabas Review was processing the RVUEXI parameter file specified in the Adabas startup procedure.
Action | Refer to the RVUEXP output file to determine the parameters that were in error and correct the specified parameters.

REV20234 | Report suspended reportname
Explanation | The report named in the message (reportname) was suspended for one of the following reasons: The CL, PS, SU, or RF command was issued from within SYSREVDB. The time specified in the INTERVAL option for the report was exceeded.
Action | No action is required for this informational message. It can be switched on or off by applying the optional zap RY4rs003, where r is the release number and s is the system maintenance level of Adabas Review you have installed.

REV20235 | Report restarted reportname
Explanation | The report named in the message (reportname) was restarted automatically after a suspension because the report RESTART option is set to "Y". If a report is suspended with the SU command within SYSREVDB, it is restarted no matter how the RESTART option is set.
Action | No action is required for this informational message. It can be switched on or off by applying the optional zap RY4rs003, where r is the release number and s is the system maintenance level of Adabas Review you have installed.

REV20236 | Report reportname started by userid
Explanation | The report named in the message (reportname) was started as an autostarted report during Adabas Review startup, manually, or after the RF command was issued within SYSREVDB. The user ID (Natural *INIT-USER value, if this is zero the value UNKNOWN will be displayed) shown in the message is either "AUTOSTRT" if the report is autostarted or the name of the user who started or refreshed the report.
Action | No action is required for this informational message. It can be switched on or off by applying the optional zap RY4rs003, where r is the release number and s is the system maintenance level of Adabas Review you have installed.

REV20237 | Report resuspended reportname
Explanation | The report named in the message (reportname) was suspended for one of the following reasons: The CL, PS, SU, or RF command was issued from within SYSREVDB; The time specified in the INTERVAL option for the report or the MAXK limit was exceeded; or There are internal storage limitations or errors.
Action | No action is required for this informational message. It can be switched on or off by applying the optional zap RY4rs003, where r is the release number and s is the system maintenance level of Adabas Review you have installed.

REV20238 | Report MAXK suspended reportname
Explanation | The report named in the message (reportname) was suspended because the storage maximum specified in the MAXK report option was exceeded. If the report RESTART option is set to "N", message REV20232 is also printed.
Action | No action is required for this informational message. It can be switched on or off by applying the optional zap RY4rs003, where r is the release number and s is the system maintenance level of Adabas Review you have installed.

REV20239 | Field fldname is not a client report field
Explanation | The field name given in the message (fldname) was requested for a client report, but is not valid for client reports. Adabas Review processing continues normally, but the values for the field are empty.
Action | Remove the field from the client report.

REV20241 | A buffer will not fit into LORECR
Explanation | During conversion of log records to the Adabas Review internal command log record (LORECR) format, a buffer would not fit into LORECR due to LORECR size limitations. The information of this buffer is cut and you may not be able to find the desired buffer information in the report output.
Action | If the data in the affected buffer is not used in a report definition, this error can be ignored as it causes no consequences. However, if this error causes data to be missing, contact your Software AG technical support representative for assistance.

REV20253 | This version of ADATMZ does not support all features ADATMZ version is v.r.s
Explanation | The module ADATMZ was loaded from either the WAL or the ADA library. The ADATMZ version loaded does not support all of the features needed for the current Adabas Review version. The current version of ADATMZ is given in the message (v.r.s).
Action | Check the Adabas Review version to find out more about the new features and, if necessary, specify a newer WAL or ADA library to obtain the newer version of the ADATMZ module.

REV20255 | parameter set too low or missing
Explanation | The parameter of the INPUT statement named in the message (parameter) is set too low or is not coded. A possible parameter that may appear in this message is the BUFFMB parameter. The following table describes this parameter further:
Parameter | Description | Minimum Value
--- | --- | ---
BUFFMB | The size of the Adabas Review buffer pool in MB. The default value is 10. | 1
Adabas Review runs with the minimum value setting of this parameter. If this setting is too small for a hub environment running Trans-port, command log records might be lost. For more information about the INPUT statement, read INPUT Statement, in the Adabas Review User Guide.
Action | Increase the value setting of the buffer parameter, as described above.

REV20257 | Rpt 'rptname' was stopped by userid
Explanation | The report named in the message (rptname) was stopped using the PS command on the Started Reports screen by the user with the user ID (Natural *INIT-USER value, if this is zero the value UNKNOWN will be displayed) listed in the message (userid).
Action | No action is required for this informational message.

REV20258 | For dsname no valid data set found.
Explanation | For the logging file with dataset name dsname there is no internal AMT found. Either the dsname is incorrect or this dataset is not defined for the Adabas Review system.
Action | Check either the Adabas nucleus JCL (in local mode) or the Adabas Review HUB JCL (in Hub mode) against the report definitions and correct one of them.

REV20259 | REVIEW field fieldname cannot be stored into history file.
Explanation | While building the record buffer for writing the report data to the history file, Adabas Review detected an invalid length definition for the field fieldname in its internal tables.
Action | Contact your Software AG technical support representative.

REV20260 | CLEX conversion caused buffer truncation
Explanation | While converting the CLEX from version 82 to 83 format, the command log record had to be cut to 32764 bytes. The message is issued only once upon the first occurrence of this event. It is for informational purpose only.
Action | No action is required for this informational message.

REV20261 | Rpt rptname put on queue for sec=nnnn
Explanation | The report named in the message (rptname) was placed into the queue queue for nnnn seconds. The queue could be either ACTI or SCHD.
Action | No action is required for this informational message. It can be switched on or off by applying the optional zap RY4rs003, where r is the release number and s is the system maintenance level of Adabas Review you have installed.

REV20262 | Rpt rptname variable message text.
Explanation | The auto started scheduled report named in the message (rptname) has invalid schedule data as indicated in the variable message text. The auto started scheduled report is not scheduled. The variable message text content can be one of the following: schedule start not before schedule end The point in time specified by SCHED-STRTDATE and SCHED-STRTTIME is not before the point in time specified by SCHED-ENDDATE and SCHED-ENDTIME. schedule duration larger than interval SCHED-DURATION and SCHED-INTERVAL have been specified and SCHED-DURATION is larger than SCHED-INTERVAL. If specified, SCHED-INTERVAL has to be larger than SCHED-DURATION. invalid schedule start/end date/time One of the parameters SCHED-STRTDATE, SCHED-STRTTIME, SCHED-ENDDATE, SCHED-ENDTIME contains an invalid date or time value. schedule end in the past The point in time specified by SCHED-ENDDATE and SCHED-ENDTIME is before the actual time.
Action | Correct the scheduling data of your report definition accordingly.

REV20263 | Set timer failed rpt rptname RC=nnn secs=nnnnnnnnnnn
Explanation | While processing the scheduled report rptname Adabas Review failed to set a timer for either the active or waiting processing phase of the report with the specified return code (RC=nnn) for the specified amount of seconds (secs=nnnnnnnnnnn).
Action | Contact your Software AG technical support representative.

REV20300 | zIIP-related statistics for XXXX enclave
Explanation | The message is the header of the following zIIP statistics for the REVIEW enclave. XXXX will be replaced by the actual enclave name. Possible enclave names are REVHUB REVHIST REVAUTO REVIEWB
Action | No action is required for this informational message.

REV20301 | ADAZIP function XXXX got rc yy.
Explanation | REVIEW encountered during a call to ADAZIP a none zero return code. XXXX will indicate the ADAZIP function invoked and yy will be the return code. The following function abbreviations are used. Init Initialize ADAZIP session. Term Terminate ADAZIP session 2SRB Switch into SRB mode 2TCB Switch into TCB mode CSRB Cancel SRB (unused) Stat get zIIP statistics from ADAZIP QPrq queue a parallel request
Action | Contact your Software AG technical support representative.

REV20302 | REVIEWB buffer processing stats maximum records in 1 period : n REVIEWB processing periods : n maximum 4K buffers queued : n maximum 32K buffers queued : n
Explanation | The message is the header of the following REVIEWB buffer processing statistics. maximum records in 1 period specifies the maximum of records REVIEWB has processed during one processing period, i.e. between 2 wait situations. REVIEWB processing periods specifies the number of processing periods executed during the life of the REVIEWB subtask. maximum 4K buffers queued specifies the maximum of 4k buffers queued for the REVIEWB subtask at any time in the life of the subtask. maximum 32K buffers queued specifies the maximum of 32k buffers queued for the REVIEWB subtask at any time in the life of the subtask.
Action | No action is required for this informational message.

REV20303 | REVIEWB switch to supervisor state failed REVIEWB continues without ADAZIP
Explanation | The message is issued if the switch to supervisor state failed. Supervisor state is necessary to operate in SRB mode. In order to do so REVIEW has to be loaded from an APF authorized library. maximum 32K buffers queued specifies the maximum of 32k buffers queued for the REVIEWB subtask at any time in the life of the subtask.
Action | Start REVIEW from an APF-authorized load library.

REV20304 | Log record from database XXXXX-YYYYY received, but database not in client database table found.
Explanation | The message is issued if a log record from a database is received which is not registered in REVIEW. The log record is ignored. REVIEW continues processing.
Action | Contact your Software AG technical support representative.

REV20309 | REVIEW starting with ZIIP=XXX
Explanation | The message indicates with which ZIIP parameter value Adabas Review is starting. XXX could be either YES or NO. If you have specified ZIIP=YES in RVUAUT1/2 data set and ZIIP=NO is printed in the REV20309 message, you probably have a license key problem. Check the DDPRINT data set for license key messages. The AZPAD license is necessary to start with ZIIP=YES.
Action | Supply the correct AZPAD license either as load module or in a DDLAZPAD DD statement.

REV20310 | REVIEW started with ZIIP=NO Switch to ZIIP=YES not allowed
Explanation | Adabas Review was started with ZIIP=NO and an operator command ZIIP=YES was issued. This is not allowed.
Action | Start Adabas Review with ZIIP=YES in the INPUT statement in order to switch zIIP mode during an Adabas Review session.

REV20311 | REVIEW is already executing in SRB mode
Explanation | An operator command ZIIP=YES was issued while Adabas Review already executes in SRB mode. Nothing was changed.
Action | No action is required for this informational message.

REV20312 | REVIEW is already executing in TCB mode
Explanation | An operator command ZIIP=NO was issued while Adabas Review already executes in TCB mode. Nothing was changed.
Action | No action is required for this informational message.

REV20313 | REVIEW is now executing in SRB mode
Explanation | An operator command ZIIP=YES was issued while Adabas Review was executing in TCB mode. Adabas Review switches into SRB mode.
Action | No action is required for this informational message.

REV20314 | REVIEW is now executing in TCB mode
Explanation | An operator command ZIIP=NO was issued while Adabas Review was executing in SRB mode. Adabas Review switches into TCB mode.
Action | No action is required for this informational message.