RVCL* - Adabas Review Batch Client Reporting (REVCLRP) Messages

#### Search Results

Search

# RVCL* - Adabas Review Batch Client Reporting (REVCLRP) Messages

### Overview of Messages

`RVCL001 | RVCL002 | RVCL003 | RVCL004 | RVCL005 | RVCL006 | RVCL007 | RVCL008 | RVCL009 | RVCL010 | RVCL011`

RVCL001 | Review Client Reporting has been {started | stopped}
Explanation | Adabas Review client reporting has been started or stopped. (REVEXIT2 has successfully been changed to the requested state: ON or OFF.)
Action | No action is required for this informational message.

RVCL002 | Review Client Reporting is currently {on | off | unavailable}
Explanation | The current status of Adabas Review client reporting is listed in the message.
Action | No action is required for this informational message.

RVCL003 | Unexpected error while resetting state
Explanation | While performing the STATUS function, an error occurred resetting the original state after processing. This is due to a very small window of opportunity where an externally controlled process was altered. An example would be if the Adabas Review hub was terminated during the time when the STATUS call has started but not completed.
Action | Retry the operation.

RVCL004 | Invalid function code
Explanation | An invalid function code was specified in RVCLFUNC. Valid function codes are "ON", "OFF" or "STATUS".
Action | Specify a valid function code in RVCLFUNC and try again.

RVCL005 | Non-zero response from link routine
Explanation | An error condition exists. Output fields RVCLRSP and RVCLRESN will contain the response and reason codes returned by the Adabas link routine, ADALNK. Note: These fields were set by ADALNK, not REVCLRP.
Action | Examine the response code and reason codes to understand the problem and fix it. If you need assistance, contact your Software AG technical support representative.

RVCL006 | Review Client Reporting was already {on | off}
Explanation | A request was made to change the state of client reporting, but client reporting was already in that state.
Action | Determine whether the request to change the state was requested correctly. If not, correct the request and try again.

RVCL007 | REVEXIT2 is not installed
Explanation | An attempt to call REVCLRP was made from an application, but the REVEXIT2 link routine is not currently installed. REVEXIT2 is required for client reporting.
Action | Contact your Software AG technical support representative for assistance.

RVCL008 | Insufficient storage for REVEXIT2
Explanation | There is not enough memory available for REVEXIT2 to operate.
Action | Provide more storage and try to run the job that calls REVCLRP again.

RVCL009 | The hand shake with the Review hub failed
Explanation | The Trans-Port service was not able to communicate properly with the Adabas Review hub because the PC number was zero.
Action | Contact your Software AG technical support representative; be prepared to provide a dump and protocol information.

RVCL010 | The internal Trans-Port mechanism failed
Explanation | Attempts to communicate with the Adabas Review hub failed. Output fields REVCLRSP and RVCLRESN will be set with the response and reason codes from REVCLRP. If the response and reason codes are 148/50, then the hub was terminated after client reporting (REVEXIT2) was activated.
Action | If the response and reason codes are 148 and 50 (respectively), restart the hub and try again. If the response and reason codes are not 148 and 50, contact your Software AG technical support representative for assistance.

RVCL011 | Adabas response 148 was received contacting the hub
Explanation | The Adabas Review hub is not available.
Action | Start the Adabas Review hub and try again.