Starting CA Vantage task, it can happen to get the error: VAN1531E Open VSAM failed. Mode=RLS RC=16 Reason=182 DSN=%%DSNPFX%%.HWMLOG and the initialization is not completed correctly.

Document ID:  TEC1743246
Last Modified Date:  08/02/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA Vantage Storage Resource Manager

Releases

  • CA Vantage Storage Resource Manager:Release:14.0

Components

  • CA Vantage Storage Resource Manager:VANT
Issue:

The Hardware Monitor can listen for both temporary and permanent I/O errors, for both disk and tape devices, as they are being written to SYS1.LOGREC. The most recent errors are kept and summarized in a memory table, and a subset is written to this product hardware error log. To avoid logging many duplicates, only one permanent error record per device is kept within a wall-clock minute. Only one temporary error record per device is kept in a 10-minute interval. The hardware error log data set is allocated as part of INSTALL job J01GMI and may already be done.

The following system parameter identifies the error log data set. Ensure that this data set exists.

HWMLOG (%%DSNPFX%%.HWMLOG)

 

By default, this component is active.To prevent the hardware monitor from starting, use the Config Client to set system parameter

 SUHWM (N).

 To deactivate (stop) the hardware monitor temporarily, issue the following command:

 F SAMS,STOP,HWM

 To activate the hardware monitor after it has been deactivated (stopped), issue the command:

 F SAMS,START,HWM

 

 Starting CA Vantage task, it can happen to get the error:

 

VAN1531E Open VSAM failed. Mode=RLS RC=16 Reason=182 DSN=%%DSNPFX%%.HWMLOG 

 

and the initialization is not completed correctly.

 

How to bypass this error? 

Environment:
CA Vantage 14.0
Cause:

Per our CA Vantage 14.0 Message Guide:

 

VAN1531E

%5S VSAM failed. Mode=%6S RC=%2S Reason=%4S DSN=%44S

Reason:

 

Either an Open, Get, Put, Point, Erase, or Close function failed for a VSAM data set.

Mode= is either RLS or NonRLS, indicating whether this Data Set is processed in an RLS or NonRLS mode.

RC= and Reason= displays the VSAM Return and Reason Codes. These codes are documented in the IBM manual DFSMS Macro Instructions for Data Sets.

 

Action:

 

Check the RC and Reason codes in the IBM manual DFSMS Macro Instructions for Data Sets and fix the problem. Then restart the function. If the function is Open, you could attempt the following:

 

Use the ALTER command to change SHAREOPTIONS, LOG, and STORCLAS parameters for the data set depending on whether it is to be used as an RLS or non-RLS data set.

 

The following describes how to define an RLS or non-RLS data set or alter the settings for existing data sets for usage:

 

To define a data set for RLS usage, use:

 

SHAREOPTIONS(3 3) LOG(NONE) and STORCLAS(smsrls).

 

To alter a data set for RLS usage, use:

 

ALTER CA.VANT.DATASET LOG(NONE) STORCLAS(smsrls)

ALTER CA.VANT.DATASET.DATA SHAREOPTIONS(3 3)

ALTER CA.VANT.DATASET.INDEX SHAREOPTIONS(3 3)

 

where smsrls is an SMS storage class name that supports RLS.

 

To define a data set for non-RLS usage, use SHAREOPTIONS (2 3) and no LOG parameter specified.

 

To alter a data set for non-RLS usage, use:

 

ALTER CA.VANT.DATASET.DATA SHAREOPTIONS(2 3)

ALTER CA.VANT.DATASET.INDEX SHAREOPTIONS(2 3)

 

Notice that the LOG cannot be NONE for a non-RLS data set used by CA Vantage SRM, and you cannot alter the LOG to "null", so if the original LOG value is NONE, you could alter the LOG value to (UNDO) as follows:

 

ALTER CA.VANT.DATASET LOG(UNDO)

ALTER CA.VANT.DATASET.DATA SHAREOPTIONS(2 3)

ALTER CA.VANT.DATASET.INDEX SHAREOPTIONS(2 3)

 

To find the log value, use TSO command:

 

listc entry('CA.VANT.DATASET') all

Resolution:

To bypass the error:

 

VAN1531E Open VSAM failed. Mode=RLS RC=16 Reason=182 DSN=%%DSNPFX%%.HWMLOG 

 

where Mode=RLS is reported but the dataset should be defined for a non-RLS environment, it is necessary to allocate/alter it with options:

 

SHAREOPTIONS(2 3) -     
LOG(UNDO) -             

 

 

If, after the suggested activity, the task still fails with the same error, please open a Case with CA Support.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >