Review 20xxx Messages

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.

Correct the error and resubmit the job.

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

Correct the error and resubmit the job.

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

Correct the error and resubmit the job.

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

Define a valid REPORT statement and resubmit the job.

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

Define a valid LINE SIZE statement and resubmit the job.

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

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

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

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

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

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

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

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

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

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

The field name specified is not a numeric field.

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

The field name specified is not a numeric field.

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

The field name specified is not a numeric field.

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

The field name specified is not a numeric field.

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

The field name specified is not a numeric field.

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

The field name specified is not a numeric field.

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

The statement specified can only be used for summary reports.

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

The statement specified can only be used for summary reports.

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

The statement specified can only be used for summary reports.

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

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

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

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

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

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

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

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

This message is for information only.

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.

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

An invalid COPY statement file-type parameter was detected.

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

Termination task attached successfully.

This message is for information only.

Termination task not found in the program library.

Contact your Software AG technical support representative.

I/O error occurred while loading termination task.

Contact your Software AG technical support representative.

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.

Correct the error and resubmit the job.

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

Correct the error and resubmit the job.

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

This message is for information only.

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

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

Termination task initiated.

This message is for information only.

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

Correct the error and resubmit the job.

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

Correct the error and resubmit the job.

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

Correct the error and resubmit the job.

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

Correct the error and resubmit the job.

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

Correct the error and resubmit the job.

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

This message is for information only.

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

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

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

This message is for information only.

The Review Interval Statistics task has been started.

This message is for information only.

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

Contact your Review administrator.

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

This message is for information only.

The Review task nnnnnnnn was attached successfully.

This message is for information only.

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

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.

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

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

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

Contact your Software AG technical support representative.

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.

Contact your Software AG technical support representative.

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

Contact your Software AG technical support representative.

The Review task has detected that

• the module U2DENQ was not linked in; or

• the incorrect version of U2DENQ was linked in.

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

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

Do not attempt to start the master interval task.

The termination task has ended.

This message is for information only.

An error has occurred while executing the specified program:

Record message and contact your Software AG technical support representative.

The Review history file task has been started.

This message is for information only.

The Review history file task has completed execution.

This message is for information only.

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

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

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.

This message is for information only.

The Review history file task is waiting for work.

This message is for information only.

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

Contact your Software AG technical support representative.

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

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

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.

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

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.

This message is for information only.

Adabas Review attempted to attach an operating system subtask but received a nonzero return code from this 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.

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.

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

Adabas Review successfully attached an operating system subtask.

This message is for information only.

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

This message is for information only.

Adabas Review attempted to attach an operating system subtask but received a nonzero return code from this 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.

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

This message is for information only.

Adabas Review successfully attached an operating system subtask.

This message is for information only.

This message indicates a specific phase of Review execution.

This message is for information only.

This message indicates a specific phase of Review execution.

This message is for information only.

This message indicates a specific phase of Review execution.

This message is for information only.

This message indicates a specific phase of Review execution.

This message is for information only.

This message indicates a specific phase of Review execution.

This message is for information only.

This message indicates a specific phase of Review execution.

This message is for information only.

This is an internal error that rarely occurs.

Contact your Software AG technical support representative.

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

This message is for information only.

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

This message is for information only.

The RAOSAUTO subtask has been detached successfully.

This message is for information only.

The RAOSAUTO automatic regeneration subtask started successfully.

This message is for information only.

The RAOSAUTO automatic regeneration subtask has completed successfully.

This message is for information only.

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

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

A request for a GETMAIN failed in RAOSSYDR.

Increase the region size for the Adabas task.

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

This message is for information only.

A request for a FREEMAIN to RAOSSYDR failed.

Contact your Software AG technical support representative.

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

Check additional warning messages issued by subtask.

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

This message is for information only.

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

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

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

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

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

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

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.

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

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.

Contact your Software AG technical support representative.

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

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

Internal error occurred.

Contact your Software AG technical support representative.

Internal error occurred.

Contact your Software AG technical support representative.

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

Correct the syntax error and restart Adabas Review.

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

Check which Review version runs with your Adabas version.

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

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

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.

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.

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

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