SMS Add Vol to LWM failure and message VAN1593E

Products

• Vantage Storage Resource Manager

Issue/Introduction

The user triggered the Vantage action 'SMS Add Vol to LWM' from the Windows Client.  The userid did not have update access to the master catalog, and thus message VAN1593E was issued. Vantage continued to add volumes past the LWM until "F SAMS,SHUTDOWN" was issued.

Several questions arise:

Is it possible to stop SAMS adding volumes once it has started?

How does VAN1593E affect the number of volumes to be added and at what time does it decide the number of volumes to add, and can that processing be changed during a run?

Is it possible to remove VVDS creation from the script?

Is it possible to use the SAMS userid for this function?

Can buffered commands be flushed?

If using SAMS to automatically add volumes, does this trigger on the HWM, or above it. If above, by how much?

Environment

Vantage

Resolution

1) Is it possible to stop SAMS adding volumes once it has started?

Answer: It should be possible to stop the adding process by canceling the script.

2) How does VAN1593E affect the number of volumes to be added and at what time does it decide the number of volumes to add.  And can that be changed during a run?

Answer: According to our design, if IDCAMS fails for some reason, we continue adding volumes. In this exact scenario, it would make sense to stop since all volumes will be depleted, but there are plenty of other scenarios where you want to continue adding (such as VVDS might already exist or can already be cataloged). It is documented several places that the user should have update rights to the master catalog. I would recommend implementing message automation for message VAN1593E if it is desired to cover this failure somehow.

3) Is it possible to remove VVDS creation from the script?

Answer: In R14.1, it is possible to bypass the VVDS creation by setting the VVDS value to 0 in the VPVVDSSX member or in the  SSGACONF member. It is not possible to do this in R14.0.

4) Is it possible to use the SAMS userid for this function?

Answer: If this processing is performed via a GOA script, then having the SECURSCR VKGPARMS parameter set to 'N' will allow the Vantage STC userid to authorize this processing (via READ access to the STGADMIN resource, as defined by the STGADMIN VKGPARMS parameter).   If this processing is triggered by an 'ad hoc' action by the user via an object, then this user will need to have READ access to the STGADMIN resource.    

5) Can buffered commands be flushed?

Answer: If a script is running which triggers this processing, then the script can be stopped.  

6) If using SAMS to automatically add volumes, does this trigger on the HWM, or above it. If above, by how much?

Answer: For the ACTION driven from the Windows Client, the HWM is not used at all. It triggers automatically if the value is above the LWM value (thus Vantage strives to reach the LWM value).

7) Our testing shows that the script (NOT the SMS Add Vol to LWM function in the Windows Client) to automatically add volumes to depleted storage groups is triggered by the HWM value being surpassed.  If this is the case, when would the script be triggered?  When the DiffWM value is at 0, or -1?

Answer:  When a GOA script is defined to undertake this processing, the user can create a FILTER which defines how the DiffWM or the HighWM values can be used.  For example, the following filters could be defined by the user which determine when the volume addition processing is triggered: 

"% Allo" > "HighWM"

or

"DiffWm" < 0
 

Since we are dealing with percentages with these different values, when a value is +/- 1% or more above/below the test value, then the processing should be triggered.