Version 4.6.2
 —  Messages and Codes  —

RVCALL* - Adabas Review RVCALL API Messages

Overview of Messages

RVCALL00 | RVCALL04 | RVCALL05 | RVCALL06 | RVCALL07 | RVCALL08 | RVCALL09 | RVCALL10 | RVCALL11 | RVCALL12 | RVCALL13 | RVCALL14 | RVCALL15 | RVCALL16 | RVCALL17 | RVCALL18 | RVCALL19 | RVCALL20 | RVCALL22 | RVCALL23 | RVCALL24 | RVCALL25 | RVCALL27 | RVCALL35 | RVCALL98 | RVCALL99 | RVCALL420 | RVCALL421 | RVCALL499

RVCALL00 Function completed successfully
Explanation

The RVCALL function completed successfully.

Action

No action is required for this informational message.


RVCALL04 Invalid RVC-FUNCTION specified
Explanation

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.

Action

Specify a valid value and try again.


RVCALL05 <msg-text>
Explanation

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

Message Text Explanation
RVC-DBID must be specified A value for the RVC-DBID parameter is required, but no value was specified.
RVC-DBID must not be greater than 65535 An invalid value was specified for RVC-DBID.
RVC-REVIEW-TARGET must be specified A value for RVC-REVIEW-TARGET is required, but no value was specified.
RVC-REVIEW-TARGET must not be greater than 65535 An invalid value was specified for RVC-REVIEW-TARGET.
Action

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


RVCALL06 RVC-REPORT-NAME must be specified
Explanation

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

Action

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


RVCALL07 RVC-ACCOUNT-FIELDS required for summary reports
Explanation

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

Action

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


RVCALL08 RVC-WRAP = "Y" valid for sequence reports only
Explanation

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

Action

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


RVCALL09 RVC-HISTORY-DBID must be specified for history reports
Explanation

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

Action

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.


RVCALL10 RVC-HISTORY-FNR must be specified for history reports
Explanation

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

Action

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


RVCALL11 RVC-HISTORY-SVC must be specified for history reports
Explanation

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

Action

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.


RVCALL12 RVC-REPORT-NAME already active
Explanation

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

Action

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


RVCALL13 UCMD area storage allocation failed
Explanation

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

Action

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


RVCALL14 Not enough storage to start report
Explanation

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

Action

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


RVCALL15 Invalid field definition in report
Explanation

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

Action

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


RVCALL16 Invalid summary field specified in report
Explanation

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

Action

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


RVCALL17 Field length error in report
Explanation

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

Action

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


RVCALL18 Field format error in report
Explanation

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

Action

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


RVCALL19 Error in report processing, resp = rsp
Explanation

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

Action

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.


RVCALL20 RVC-REPORT-NAME is not active
Explanation

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.

Action

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


RVCALL22 No active reports to be listed
Explanation

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

Action

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


RVCALL23 Error accessing DBID for L-FILE
Explanation

An error occurred while processing an RVCALL GETDBID function.

Action

Contact your Software AG technical support representative for assistance.


RVCALL24 Found zero HUBIDs on selected SVC
Explanation

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

Action

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.


RVCALL25 RVC-SVC is invalid
Explanation

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

Action

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


RVCALL27 <msg-text>
Explanation

One of the following errors occurred using ADATMZ during RVCALL processing.

Message Text Explanation
ADATMZ: No Adabas SVCs found No Adabas SVCs were found by ADATMZ.
ADATMZ: No Active targets for an SVC No active targets were found for the SVC by ADATMZ.
Action

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


RVCALL35 BUFFER POOL reports cannot have DBID=ALL
Explanation

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.

Action

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.


RVCALL98 Adabas error, resp = rsp
Explanation

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

Action

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.


RVCALL99 Adabas error, resp = rsp
Explanation

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

Action

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.


RVCALL420 Unable to open command log file for output
Explanation

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

Action

Make the command log file available and try again.


RVCALL421 Command log dataset already in use
Explanation

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

Action

Make the command log data set available and try again.


RVCALL499 Detail printer not available
Explanation

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

Action

Make the printer available and try again.


Top of page