RVCALL* - Adabas Review RVCALL API Messages

The RVCALL function completed successfully.

No action is required for this informational message.

An attempt was made to start a report with the EZSTART function. But the report definition, that was supposed to be started, was not found.

Either specify a different, existing report or define the specified report and try again.

An invalid value was specified for the RVCALL parameter RVC-FUNCTION. Valid values are START, DELETE, CLOSE, SUSPEND, REACT, LIST, GETHUBID, GETDBID, EZSTART, VIEWON, or VIEWOFF.

Specify a valid value and try again.

The message text for this message varies. The following message texts may appear:

Correct the value of the RVC-DBID or RVC-REVIEW-TARGET parameter and try again.

A value for the RVC-REPORT-NAME parameter is required, but no value was specified.

Specify an valid value for RVC-REPORT-NAME and try again.

A value for the RVC-ACCOUNT-FIELDS parameter is required, but no value was specified.

Specify the order in which fields should appear for summary reports in the RVC-ACCOUNT-FIELDS parameter. Then try again.

RVC-WRAP is specified, but the SEQUENCE field is not specified in the RVC-ACCOUNT-FIELDS parameter.

Examine the problem. Correct either the RVC-WRAP parameter setting or add SEQUENCE to the RVC-ACCOUNT-FIELDS parameter setting. Then try again.

History data was requested, but no value was specified for the RVC-HISTORY-DBID parameter.

In the RVC-HISTORY-DBID parameter, specify the valid database ID (DBID) of the Adabas Review repository used to store history data. Then try again.

History data was requested, but no value was specified for the RVC-HISTORY-FNR parameter.

In the RVC-HISTORY-FNR parameter, specify the valid file number of the Adabas Review repository used to store history data. Then try again.

History data was requested, but no value was specified for the RVC-HISTORY-SVC parameter.

In the RVC-HISTORY-SVC parameter, specify the valid Adabas SVC number used to communicate with the Adabas Review repository to which history data should be written. Then try again.

The report specified in the RVC-REPORT-NAME parameter using the EZSTART function is already active.

Specify a different report in the RVC-REPORT-NAME parameter and try again. Alternatively, you could stop the running report and start it again using RVCALL, but if the report was started online using SYSREVDB, it will need to be stopped online (not using RVCALL).

The storage available for Adabas Review reports is inadequate. This was determined during an attempt to run the EZSTART function.

Increase the storage available for Adabas Review reports and try again. If the problem persists, contact your Software AG technical support representative.

There is not enough storage to start a report using the EZSTART function.

Increase the storage available for Adabas Review reports and try again. If the problem persists, contact your Software AG technical support representative.

An invalid field definition was found in an Adabas Review report while running the RVCALL EZSTART function.

Using SYSREVDB, correct the field definition online. Then try the RVCALL EZSTART function again.

An invalid summary field was specified for an Adabas Review report while running the RVCALL EZSTART function.

Using SYSREVDB, correct the summary field value online. Then try the RVCALL EZSTART function again.

An invalid field length was specified for an Adabas Review report while running the RVCALL EZSTART function.

Using SYSREVDB, correct the field length value online. Then try the RVCALL EZSTART function again.

An invalid field format was specified for an Adabas Review report while running the RVCALL EZSTART function.

Using SYSREVDB, correct the field format value online. Then try the RVCALL EZSTART function again.

An unknown error occurred in the RVCALL EZSTART processing of an online report. The response code is given in the message (rsp).

Review the response code and use SYSREVDB to examine the report definition online. Make appropriate corrections and retry. If the problem persists, contact your Software AG technical support representative.

The report name specified in the RVC-REPORT-NAME parameter is not active, but must be active for the RVCALL function identified in the RVC-FUNCTION parameter.

Either specify an active report name in the RVC-REPORT-NAME parameter or change the RVCALL function specified in the RVC-FUNCTION parameter.

An internal error occurred in the RVCALL EZSTART processing of an online report.

Contact your Software AG technical support representative.

During RVCALL LIST/LISTSCH function processing (RVC-FUNCTION='LIST'/’LISTSCH’), RVCALL found no active/waiting reports to list.

Determine whether this is really a problem. No action is required if there are no active/waiting reports. However, if there are active/waiting reports, verify that the other LIST/LISTSCH function input parameters are specified correctly. Then try again.

An error occurred while processing an RVCALL GETDBID function.

Contact your Software AG technical support representative for assistance.

No hub IDs were found during RVCALL GETHUBID function processing for the SVC specified in the RVC-SVC parameter.

Verify that the SVC specified in the RVC-SVC parameter is valid and try again. If the problem persists, contact your Software AG technical support representative.

The SVC specified in the RVC-SVC parameter for RVCALL GETHUBID function processing was invalid.

Specify a valid SVC in the RVC-SVC parameter for the run and try again.

There are about 20 possible messages from the ADATMZ call.

Examine the message and take appropriate action. If the problem persists, contact your Software AG technical support representative for assistance.

During RVCALL EZSTART processing, you specified "BUFFER POOL DISPLAY" for the report name and set the RVC-ALL parameter to "ALL". This is not allowed. You cannot produce the buffer pool display for all DBIDs.

Specify a single database ID in the RVC-DBID parameter for the RVCALL EZSTART run and remove the RVC-ALL='ALL' specification. Then try again.

With the EZSTART function a DBID to be monitored (parameter RVC-DBID) was specified, which is not in the possible range.

Specify a valid value and try again.

An internal Adabas call was made, which returned H’4040’ in the first two bytes of the record buffer.

Note the function which caused the error. Use SYSREVDB and try to execute the same function. If is works with SYSREVDB, examine the input parameters of the function for an error. If the problem persists, contact your Software AG technical support representative.

An error occurred while the RVCALL API was calling Adabas. The response code from the call is given in the message (rsp).

Review the response code explanation in the Adabas Response Code documentation and try to resolve the problem. If the problem persists, contact your Software AG technical support representative.

An error occurred while the RVCALL API was calling Adabas. The response code from the call is given in the message (rsp).

Review the response code explanation in the Adabas Response Code documentation and try to resolve the problem. If the problem persists, contact your Software AG technical support representative.

The report requested during an RVCALL EZSTART run required a command log file that was not available.

Make the command log file available and try again.

The report requested during an RVCALL EZSTART run required a command log data set that was not available.

Make the command log data set available and try again.

The report requested during an RVCALL EZSTART run required a printer, but no printer was available.

Make the printer available and try again.