Wiki Category: VNC04nn: VNAC agent command processors

taskname: Reloading REXX environment.

A MODIFY vnac,RELOAD,REXX command was received. The dispatcher is reinitializing the REXX environment of the named task.

Action: None. This is an informational message.

REXX storage: Used RM31=decimal-K-bytesK, RM24=decimal-K-bytesK; Requests=request-count, Failed=request-count

Informational message issued by VNCINI00, the program that runs the OBEYFILE exec during agent initialization, and VNCCPR01, the program that runs all REXX execs after the agent has finished intializing.

This message is displayed after an exec has completed execution, following message VNC0411I, to show the maximum amount of rmode 31 and rmode 24 memory used by the exec.

The request-count is the total number of requests from REXX to obtain and free blocks of memory. Normally, this should be an even number. It may be an odd number if a request fails and REXX issues a request for a smaller amount of memory that is accepted.

Normally, the failed request-count will be zero. If it is not, message VNC0961E will have been previously issued to show which rmode memory limit was exceeded.

When UseREXXLoader is set to Yes, RM24 is typically OK. However, even when the VNAC REXX loader is used, you may see some exec tasks running and below-the-line storage being used. Typically, these will be the initial obeyfile task and any exec that runs automatically at startup.

Until the initial obeyfile has been processed, the agent will default to running without the use of the VNAC REXX loader. Thus, these early tasks will load their own exec locally and cause REXX to obtain below-the-line storage for the I/O buffer. When these execs have ended, the REXX environment will be deleted and the associated below-the-line storage will be released. As a result, these execs do not impact the address space below-the-line storage usage in any significant manner; any such usage is temporary.

Action: Assuming the exec does not have an error, the corrective action is to increase the memory limit for the corresponding rmode using the RexxEnvLimit global configuration statement.

allocating|opening|closing dataset dataset-name; DD=ddname

VNAC generates this diagnostic message when it handles a browse request to retrieve a dataset. The message shows the command identifier, function request, dataset name, and DDName.

The view feature is not configured on this agent.

The VNAC agent is configured to send zero (0) lines of a dataset to the server and client.

Action: In the agent configuration member, re-set the ViewLimit parameter.

VNAC cannot process the input dataset. An abend occurred during read processing

VNAC detected an abend while reading a dataset for the View feature. VNAC recovers and issues this message to the log and to the user at the browser.

Action: This message can be issued if an invalid dataset was requested. Ensure the dataset is a DSORG=PS dataset with RECFM=F or V, or a PDS member. If the problem persists, contact SDS Technical Support.

VNAC cannot process the input dataset because its DSORG is not PS

A dataset was passed to the View datasets feature that had a dataset organization (DSORG) that was not PS. VNAC only supports DSORG=PS datasets, or PDS members.

Action: Specify a valid dataset name or PDS member name.

Dataset dataset-name allocation failed; retc=return-code, rsnc=reason-code

The dataset View feature was used to request a dataset and the dataset could not be allocated. This message is sent to the VNAC client user.

Action: Look up the return and reason codes to determine the cause of the error. (Dynamic allocation return codes are documented in the IBM manual MVS Authorized Assembler Services Guide.) Correct any errors and retry the request.

Dataset dataset-name could not be found

The dataset View feature was used to request a dataset and the dataset could not be located. This message is sent to the VNAC client user.

Action: The VNAC agent cannot process uncataloged datasets. Check the dataset name and ensure it is cataloged. Retry the request.

Dataset open failed, retc=return-code

The dataset View feature was used to request a dataset and the dataset could not be opened. This message is sent to the VNAC client user.

Action: Check the dataset name and retry the request. If this condition persists, contact SDS Technical Support.

VNAC cannot process the input dataset. An abend abend-code occurred during OPEN processing.

The dataset View feature was used to request a dataset that is invalid or that cannot be processed by the VNAC agent. This message is sent to the VNAC client user. This message can be issued with code S013 if a fully-qualified PDS dataset name with a non-existent member is requested. It can be issued with code S913 if the user is not authorized the view the dataset.

Action: Check the dataset name. Make sure the dataset is of a format that can be processed by the VNAC agent.