VAN1558E Object=LSPACEPO was not created because the auxiliary page space limit of 62% was hit
search cancel

VAN1558E Object=LSPACEPO was not created because the auxiliary page space limit of 62% was hit

book

Article ID: 279494

calendar_today

Updated On:

Products

Vantage Storage Resource Manager

Issue/Introduction

After a Vantage restart, the task started getting the below recursive messages:

...

 14.29.23 S0099385  VAN1558E Object=LSPACEPO was not created because the auxiliary page space limit of 62% was  hit
 14.29.23 S0099385  VAN1558E Object=LSPACEPO was not created because the auxiliary page space limit of 62% was  hit
 14.29.23 S0099385  VAN1558E Object=LSPACEPO was not created because the auxiliary page space limit of 62% was  hit
 14.29.23 S0099385  VAN1558E Object=LSPACEPO was not created because the auxiliary page space limit of 62% was  hit
 14.29.23 S0099385  VAN1558E Object=LSPACEPO was not created because the auxiliary page space limit of 62% was  hit
 14.29.23 S0099385  VAN1558E Object=LSPACEPO was not created because the auxiliary page space limit of 62% was  hit
 14.29.23 S0099385  VAN1558E Object=LSPACEPO was not created because the auxiliary page space limit of 62% was  hit
 14.29.23 S0099385  VAN1558E Object=LSPACEPO was not created because the auxiliary page space limit of 62% was  hit
 14.29.23 S0099385  VAN1558E Object=LSPACEPO was not created because the auxiliary page space limit of 62% was  hit

...

How to bypass this error. 

Resolution

Vantage cannot allocate memory above the bar because of the Vantage mechanism to keep page data sets "healthy". So it's important to either find out what other process is occupying the page data sets or better just increase the size of it. 

Possibly, some other processes in this situation were running and using a large amount of paging space before Vantage started processing.  Vantage then started up, and because a large amount of paging space was already being used, Vantage reached the limit for MEMLIMPA (62%) quickly, and thus started producing the VAN1558E messages within 8 seconds of Vantage having been started.

Solution to these messages is either increase the paging data sets on the system, or increasing the MEMLIMPA system parameter. First one is preferred, second one can cause issues for other applications on the system, because Vantage could be taking too much after increasing it.

The help on the message itself (the action section) seems to be self-explanatory, but there is nothing to do from the Vantage point of view.

VAN1558E

Object=object_name was not created because the auxiliary page space limit of %3S was hit
Reason
While processing the named object, it was detected that its getmain request for above the bar memory could cause the used auxiliary page space to exceed the MEMLIMPA limit of the allocated auxiliary page space. This guards against a system degradation or possible system outage due to a lack of sufficient page space.
Action
Contact your system programmer and request an increase in the total system page space such that this and other needed objects can be created. If you need the size (in MB) of the request causing this specific failure, see the VKGOBJAM VANLIMIT diagnostic message for the named object in the MSGE sysout.