ARVU* - Adabas Review Interface Messages

Overview of Messages

ARVU01 | ARVU02 | ARVU03 | ARVU04 | ARVU05 | ARVU06 | ARVU07 | ARVU08 | ARVU09 | ARVU10 | ARVU11 | ARVU12 | ARVU13 | ARVU14 | ARVU16 | ARVU17 | ARVU18 | ARVU19 | ARVU20 | ARVU21 | ARVU22 | ARVU23 | ARVU24 | ARVU25 | ARVU26 | ARVU27 | ARVU28 | ARVU29 | ARVU30 | ARVU31 | ARVU32 | ARVU33 | ARVU34 | ARVU35 | ARVU36 | ARVU38 | ARVU40 | ARVU41 | ARVU42 | ARVU43 | ARVU45

ARVU01

dbid GETMAIN FAILURE, SIZE= requested-getmain-size

Explanation

ADARVU was unable to obtain the necessary GETMAIN space to operate. ADARVU terminates processing. It is probable that the specified region size is too small, or the default region size is too small. SIZE is the requested GETMAIN size that could not be obtained. The Adabas nucleus completes its initialization but no calls are made to the Adabas Review hub.

Action

Increase the region size for Adabas and restart the nucleus.

Under BS2000 increase/add the ADARUN parameter SUBMPSZ=140000000.

ARVU02

dbid REVIEW HUB ID= target-id LOG RETD RSP rsp
dbid REVIEW HUB ID= target-id CLS RETD RSP rsp
dbid REVIEW HUB ID= target-id OPN RETD RSP rsp

Explanation

A non-zero Adabas response was received from the Adabas Review hub with the specified target ID when ADARVU sent one of the following requests:

LOG	request to process a command log record.
CLS	close call to terminate monitoring services with the hub.
OPN	open call to establish monitoring services with the hub.

Action

Identify the problem from the Adabas response code. If the problem is parameter settings in the hub, i.e., attached buffer size or command queue size, then the Adabas Review hub must be cycled to reset the parameters. If the Adabas response code 148 (ADARSP148) was received, the Adabas Review hub may have been terminated.

ARVU03	dbid REVIEW REVIEW HUB ID target-id IS NOT A HUB SERVER
Explanation	The target ID specified on the REVIEW parameter is not an Adabas Review hub. The target may be another Adabas nucleus. The Adabas nucleus completes its initialization but no calls are made to the Adabas Review hub.
Action	Ensure that the REVIEW parameter specifies the correct target ID of an Adabas Review hub and restart the nucleus.
Action	The operator command REVIEWHUBID=`hub-id` may be used to change the value to a another target ID.

ARVU04	dbid REVIEW REVIEW HUB ID target-id IS NOT ACTIVE
Explanation	ADARVU received response code 148 (ADARSP148) on a request call to the Adabas Review hub. This message is displayed in conjunction with the AREV02 message.
Action	Start the appropriate Adabas Review hub.

ARVU05

dbid UEX5: REQUESTED WAIT FOR nnnnn SECONDS
dbid UEX5: INVALID REQ ( xx ), IGNORE ASSUMED

Explanation

On any error condition, ADARVU calls user exit 5 if present. User exit 5 may return one of three possible service requests:

Wait for nnnnn seconds, after which ADARVU will resend the request to the Adabas Review hub.
Ignore the non-zero response received from the Adabas Review hub and to continue processing.
Immediately resend the request to the Adabas Review hub.

The message displays the service request received from the user exit 5. If an unknown request is received from the user exit, the request is ignored and processing continues.

Action

None required, unless the fourth message is displayed. The INVALID REQ message indicates a problem with the user exit 5. Correct the problem and restart the Adabas nucleus, when possible.

ARVU06	dbid CHECK ADABAS MESSAGES AND CODES MANUAL
Explanation	This message is displayed in conjunction with the AREV02 message in the event that the non-zero response received by ADARVU is not a RSP 148.
Action	None required. This message is for your information only.

ARVU07	dbid SESSION OPEN FAILURE, MODULE module COULD NOT BE LOADED
Explanation	The specified module was not found in the load library and could not be loaded. The Adabas nucleus completes its initialization but no calls are made to the Adabas Review hub.
Action	Ensure that the correct load libraries are specified for the Adabas job and restart the Adabas nucleus.

ARVU08	**dbid NUMBER OF NON-ZERO RESPONSES FROM HUB IS count**
Explanation	Whenever an unexpected response is received by ADARVU, the count of the number of non-zero responses is incremented and this message is displayed.
Action	None required. This message is for your information only.

ARVU09	dbid USER EXIT 5 {AVAILABLE \| UNAVAILABLE}
Explanation	During session initialization, ADARVU checks if a user exit 5 has been loaded. This message displays whether the user exit 5 was located or not.
Action	None required. This message is for your information only.

ARVU10	dbid REVIEW HUB hub-id VERSION Vnn LOCATED
Explanation	During session initialization, ADARVU issues a call to the specified Adabas Review hub. When a successful connection is established, this message is displayed.
Action	None required. This message is for your information only.

ARVU11	**dbid CHANGE ORDERS FROM REVIEW HUB hub-id**
Explanation	The Adabas Review hub notified the client nucleus that it changed the monitoring or reporting status of the client nucleus. ADARVU then displays this message accompanied by the ARVU13 message set.
Action	None required. This message is for your information only.

ARVU12	**dbid REVIEW HUB ID CHANGED FROM hub-id TO hub-id**
Explanation	ADARVU detected that the hub-id specified in the REVIEW parameter was changed dynamically by an operator command.
Action	None required. This message is for your information only.

ARVU13

dbid text

Explanation

Possible message texts:

Message Text (`text`)	Description
{NO \| `count` } REVIEW REPORT(S) STARTED	In conjunction with the ARVU11 message, this message indicates the status of information transmitted from the client nucleus to the hub. If no Adabas Review report(s) are started, ADARVU does not send data to the hub. If there is at least one report started, then ADARVU transmits the command log data to the hub. Action: No action required. This message is for your information only.
{NO \| `count` } REPORT`s` REQUIRE`s` BUFFERS	If at least one report requires buffers, ADARVU transmits the requested Adabas control buffer data in addition to the command log data. The `count` indicates the number of started reports and/or the number of reports requiring buffers. Action: No action required. This message is for your information only.
REVIEW HUB TRANSPORT INITIALIZED, MEMORY `mmmmmmmm`	BS2000: The hub started Adabas Review Trans-port with the memory `mmmmmmmm`. Action: No action Required. This message is for your information only.
RTPINIT, CANNOT GET HEADER, SIZE `ssssssss`, MEMORY `mmmmmmmm`	BS2000: The hub cannot acquire an Adabas Review Trans-port header of size ssssssss using memory mmmmmmmm. Action: Check memory allocation parameters in use in the Adabas Review Hub. Otherwise contact SAG Support.
RTPINIT, COULD NOT ESTABLISH EXIT FOR RTPTERM - RC `rrrrrrrr`	BS2000: The RTPTERM exit module could not be established in the Hub's task. Action: Send Hub output protocol to SAG Support.
RTPINIT, REVIEW HUB COULD NOT BE FOUND IN IDT	BS2000: The hub has not successfully registered with the ID Table. The IDT is a table of databases or nodes still active in the system. Action: Check in the output protocol for other error messages from the Adabas MPM. Otherwise contact SAG support.
RTPSSPC, HEADER HAS `xxxxxxxx` AND DBID `dddddddd`	BS2000: The stored Adabas Review Trans-port header has an ID that is different from the one in the request. This header exists in a common memory pool and should have an eyecatcher of ADAPCTRA and the Hub's dbid. This doesn't check. Action: Contact Software AG Support with dump and protocol information.
RTPSSPC, REVIEW HUB COULD NOT BE FOUND IN IDT	BS2000: The nucleus tried to access a hub with a DBID that is unknown to the system. The IDT is a table of databases or nodes still active in the system. Action: Use the Utility IDTLOOK to check for active IDs in the table. Check also on the use of the GROUPS=NO/YES parameter. Otherwise, contact SAG support.
RTPSSPC, REVIEW HUB `hubid` HAS BEEN REMOVED FROM THE IDT	BS2000: The hub ID requested is no longer active. Action: Use the Utility IDTLOOK to check for active IDs in the table. Check also on the use of the GROUPS=NO/YES parameter. Otherwise contact SAG support.
THE FOLLOWING BUFFER TYPES ARE REQUIRED: `buffer-type-codes`	If buffers are required, the required buffer types are listed in the message. The possible buffer type codes can be F (format buffer), R (record buffer), S (search buffer), V (value buffer), M (multifetch buffer), or I (ISN buffer). Action: Verify that the correct buffers are specified. Otherwise, no action is required for this informational message.
TRANSPORT INITIALIZED, MEMORY `mmmmmmmm`	BS2000: The nucleus accessed the hub through the Adabas Review Trans-port and uses the common memory defined by mmmmmmmm. Action: No action required. This message is for your information only.

ARVU14	dbid UNEXPECTED CHANGE ORDER FROM HUB hub-id IS IGNORED.
Explanation	ADARVU received a change order from an Adabas Review hub that is not the hub to which ADARVU is currently sending data. The may happen if another hub is initialized that has started reports for the client nucleus. ADARVU ignores the change order.
Action	Find out what has issued the strange change order.

ARVU16	dbid REVIEW IS ACCEPTING BUFFERED CLOG RECORDS
Explanation	The Adabas Review hub accepts buffered CLOG records from the client nucleus as a way of reducing the number of cross-memory calls from the client nucleus to the hub.
Action	None required. This message is for your information only.

ARVU17	dbid REVIEW IS NOT ACCEPTING BUFFERED CLOG RECORDS
Explanation	The Adabas Review hub is not accepting buffered CLOG records from the client nucleus.
Action	Check the job log of the Adabas nucleus and the Adabas Review hub, why the Adabas Review hub refuses to accept buffered CLOG records.

ARVU18	**dbid REVIEW TRANS-PORT IS INSTALLED USING PC pc-number**
Explanation	z/OS only. The Adabas nucleus runs with the Adabas Review Trans-port feature when sending CLOG records to the Adabas Review hub.
Action	None required. This message is for your information only.

ARVU19	dbid REVIEW TRANS-PORT IS NOT INSTALLED
Explanation	BS2000 and z/OS only. The Adabas Review Trans-port feature is not installed.
Action	If this Adabas nucleus should run with the Adabas Review trans-port feature, check the job log of the Adabas nucleus and the job log of the Adabas Review hub why trans-port is not installed.

ARVU20	dbid REVIEW MODULES NOT FOUND, LOGCLEX PARAMETER IS SET TO NO
Explanation	ADARUN LOGCLEX=YES has been specified, but no Adabas Review modules are available. The Adabas nucleus changed the LOGCLEX parameter to ADARUN LOGCLEX=NO. The extended information is made available for the purpose of running Adabas Review in batch mode.
Action	Please make the Adabas Review modules available in the STEPLIB.

ARVU21	dbid ADAIOR REQUEST FAILED: FUNC ff RSP rr
Explanation	A request to the Adabas ADAIOR interface by the Pulse failed.
Action	Retain all dumps, messages, and other related information; contact your Software AG technical support representative.

ARVU22	dbid GETMAIN FAILED: INSUFFICIENT STORAGE
Explanation	A request for storage by the Pulse failed. The report is not started.
Action	Increase the region size for Adabas and restart the nucleus.

ARVU23

dbid INTERNAL ERROR IN module, subcode n

Explanation

An internal error has occurred in the given Pulse module. The report is not started.

In the Pulse modules ADAPMT, ADAPSM, and ADAPST a sub code is issued:

Module	Subcode	Explanation
ADAPMT	1	Operating system erroneously VM/ESA.
ADAPMT	2	Operating system erroneously BS2000.
ADAPSM	1	ADAPLRPL work area is missing.
ADAPSM	2	The Pulse extension in CLEX is missing.
ADAPST	1	SVC number is zero. Action: Check SVC numbers in Reports.
ADAPST	2	A'ADAPCS is missing. Action: Check whether module ADAPCS is available.
ADAPST	3	A'ADAPCS is missing. Action: Check whether module ADAPCS is available.
ADAPST	4	The eye catcher in the buffer is neither 'TIMC' nor 'TERM' nor 'RSTR'.
ADAPST	5	A'ADAPCS is missing. Action: Check whether module ADAPCS is available.
ADAPST	6	A'ADAPCS is missing. Action: Check whether module ADAPCS is available.

In ADAPCS no sub code is issued.

Action

Retain all dumps, messages, and other related information; contact your Software AG technical support representative.

ARVU24	dbid CLUSTER SERVICES NOT ACTIVE
Explanation	The Pulse has determined that Cluster Services statistics reporting is not possible. The report is not started.
Action	Ensure that Cluster Services is active.

ARVU25	dbid ADABAS rspcode rrrrr subcode sssss returned from DBID dbid NUCID nucid
Explanation	The Pulse has encountered the given Adabas non-zero response code and subcode. The report is deactivated.
Action	Identify the problem from the Adabas response code and subcode.

ARVU26	dbid PULSE ESTAE DRIVEN, RETRY IN PROGRESS
Explanation	The Pulse subtask has encountered an error and will attempt to recover.
Action	None.

ARVU27	dbid PULSE RECOVERY ATTEMPT FAILED
Explanation	The Pulse subtask attempt at error recovery failed. The report is deactivated.
Action	Retain all dumps, messages, and other related information; contact your Software AG technical support representative.

ARVU28	dbid Pulse task failed to attach
Explanation	The Pulse subtask could not be attached. The report is deactivated.
Action	Retain all dumps, messages, and other related information; contact your Software AG technical support representative.

ARVU29	dbid Pulse task now {active\|inactive}
Explanation	The Pulse has stopped or started.
Action	None.

ARVU30	dbid Invalid Pulse interval, default used
Explanation	The Pulse detected an invalid timer interval. The acceptable range is from 1 to 1440 minutes. The default interval of 15 minutes is used.
Action	Restart the report with a valid timer value.

ARVU31	dbid Pulse ended due to non-zero RSP codes
Explanation	The Pulse detected three non-zero Adabas response codes. The report is deactivated.
Action	Correct the cause of the non-zero response codes and restart the report.

ARVU32	dbid CLOG too big, No CLEX attached
Explanation	The length of CLOG and CLOG extension exceeds 65K. The CLOG extension is not attached. This message is only issued one time.
Action	An internal error occurred. Contact Software AG support.

ARVU33	dbid REVIEW hub CPU id different.
Explanation	This message is issued when the CPU ID of the Adabas nucleus and the CPU ID of the Adabas Review hub are different. When this happens, CLOG records to the Adabas Review hub cannot be sent via the Trans-port PC call, but must be sent via the Adabas router. The performance of the Adabas router sending mechanism is slower than the performance of Trans-port.
Action	No action is required for this informational message.

ARVU34	dbid REVIEW = ADABAS DBID not allowed. REVIEW = NO set.
Explanation	The ADARUN parameters DBID and REVIEW specify equivalent DBID values. The REVIEW parameter is set to NO.
Action	Specify the correct REVIEW parameter. This can be done online.

ARVU35	dbid ONLY CLOGLAYOUT=5/8 permitted
Explanation	There are no valid Adabas modules available which can convert CLOGLAYOUT=8 records for Adabas Review.
Action	Specify an Adabas load library from version 8.1 SP3 or later in your Adabas nucleus job.

ARVU36	dbid Review local mode initialization failed, REVIEW set to NO.
Explanation	Review Local mode has been disabled due to an error when initializing Review. A preceding message will identify the specific error.
Action	Correct the error and restart the nucleus. In some cases it may be possible to use operator commands to assign the nucleus to a Review Hub.

ARVU38	dbid REVIEW record filtering started. dbid REVIEW record filtering stopped. dbid Records processed: nnnnnnnnnn dbid Records filtered: nnnnnnnnnn
Explanation	The status of record filtering has changed. When filtering is stopped, the number of command log records processed thus far by the filter is printed, as well as the number of records filtered from Review processing.
Action	None required. This message is informational only.

ARVU40

dbid xx BUFFER TRUNCATED

Explanation

Every field which could be processed by REVIEW has an indication (or attribute) whether a particular Adabas buffer (FB, RB, SB, VB, IB, MB, PB) is necessary for REVIEW to process this field. These indications (or attributes) are gathered for each report running and the indications (or attributes) for all running reports are gathered and Adabas is informed which Adabas buffers are requested by REVIEW.

When Adabas sets up a command log record for REVIEW, it checks these indications in order to build the command log record with or without a particular Adabas buffer. During this process Adabas (ADARVU) checks whether the length of the actual Adabas buffer confirms the ADARUN parameter REVLOGBMAX. If the value is violated the first time, the ARVU40 message is issued.

Action

The relevant buffer is truncated. If necessary increase the value of REVLOGBMAX or deselect fields which require Adabas buffers.

ARVU41

dbid BUFFER IGNORED

Explanation

When Adabas sets up a command log record for REVIEW, it checks these indications in order to build the command log record with or without a particular Adabas buffer. During this process Adabas (ADARVU) checks whether the length of the actual Adabas buffer confirms the ADARUN parameter REVLOGMAX. If the value is violated the first time, the ARVU41 message is issued.

Action

Buffers are ignored. If necessary increase the value of REVLOGBMAX or deselect fields which require Adabas buffers.

ARVU42	*dbid REVIEW HUB hub-id* VERSION Vnn NOT SUPPORTED**
Explanation	During session initialization, ADARVU issues a call to the specified Adabas Review hub, running with version V`nn`. This version is not supported; the version number is either too low or too high. The handshake command to the hub did not work, so Adabas Review will not collect any data.
Action	Start the Adabas Review hub with the appropriate version. For information about version compatibility, read Adabas and Adabas Review Version Compatibility.

ARVU43	dbid Storage keys of nucleus and hub are different.
Explanation	The storage keys of the Adabas nucleus and of the Adabas Review hub are different. Both address spaces must run under storage keys 0 or storage keys 8.
Action	Start Adabas nucleus and Adabas Review hub under the same key, i.e. storage key 0 or storage key 8.

ARVU45

dbid ADABAS REVIEW Main Task Statistics
dbid Hub mode log records n,nnn,nnn,nnn
dbid Local mode log records n,nnn,nnn,nnn
dbid Log record filtering
dbid Records processed n,nnn,nnn,nnn
dbid Records filtered n,nnn,nnn,nnn
dbid Largest log record nn,nnn
dbid Successful Hub calls n,nnn,nnn,nnn
dbid Unsuccessful Hub calls n,nnn,nnn,nnn
dbid Storage keys of nucleus and hub are different.

Explanation

This message displays shutdown statistics for the Adabas Review components in the Adabas nucleus. ADARVU reports:

The number of log records processed while in Hub mode
The number of log records processed while in Local mode
The number of log records processed while record filtering was active
The number of log records filtered from Review processing
The size (in bytes) of largest log record
The number of successful calls and Trans-Port sends to the Review Hub
The number of unsuccessful calls and Trans-Port sends to the Review Hub

Action

None required. This message is informational only.