Error messages during Vantage started task initialization: VAN0590E: GETMAIN FAILED, LEN= 67,108,944 SP=000 ID=MUEWAREA FOR_MEMORY_MAP VAN0590D 201,326,592=REGION LIMIT FOR MEMORY ABOVE THE LINE

Products

• Vantage Storage Resource Manager

Issue/Introduction

During the initialization of Vantage the below error messages are received: 

VAN0590E: GETMAIN FAILED, LEN= 67,108,944 SP=000 ID=MUEWAREA FOR_MEMORY_MAP 
VAN0590D 201,326,592=REGION LIMIT FOR MEMORY ABOVE THE LINE 
VAN0590D 16,449,536=MAX LENGTH CURRENTLY AVAILABLE ABOVE THE LINE  
VAN0590D 9,412,608=REGION LIMIT FOR MEMORY BELOW THE LINE 
VAN0590D 5,406,720=MAX LENGTH CURRENTLY AVAILABLE BELOW THE LINE
GENMEMUS WORK AREA DOES NOT EXIST 

 ...and the task abends.   How to resolve this problem?

 

 

 

Environment

Vantage

Cause

This is the general description of the messages from the Vantage Message Reference Guide:

 VAN0590E

GETMAIN failed, LEN=%4F SP=%4F ID=%8S INFO=%16S

DTOC COMPONENT POSTED FOR SHUTDOWN DUE TO GETMAIN FAILURE

FREEMAIN failed, Len=4%F At=%4X SP=%4F ID=%8S TCBPGM=%8S

GET M64: TCB=%8S A(TCB)=%4X PGM=%8S MB=%8X ID=%8S UTOKEN=%8X

GOT ERR: TCB=%8S A(TCB)=%4X PGM=%8S A=%8X ID=%8S RC=8 REASON=xxRRRRyy

FREE M64: TCB=%8S A(TCB)=%4X PGM=%8S MB=%8X ID=%8S UTOKEN=%8X

FREE ERR: TCB=%8S A(TCB)=%4X PGM=%8S A=%8X ID=%8S RC=8 REASON=xxRRRRyy

 Reason:

 There are 9 diagnostic forms of this message which present information about the available memory, and 7 forms for error messages. The 7 error forms are divided into 3 for failures involving memory below the bar, and another 4 involving memory above the bar. Both the diagnostic and error forms of the messages are discussed in more detail below.

 The first diagnostic message displays the REGION=nnn specified for the job (address space) when it was started.

The second diagnostic message displays the REGION LIMIT for space that can be GETMAINed below the 16 MB line.

The third diagnostic message displays the REGION LIMIT for space that can be GETMAINed above the 16 MB line, but below the 2 GB bar.

The fourth diagnostic message displays the MEMORY LIMIT for space that can be GETMAINed above the 2 GB bar.

The fifth diagnostic message is a WARNING that the REGION parameter has been changed from the distributed default value of 0M.

The sixth diagnostic message is a WARNING that the MEMLIMIT parameter has been changed to a value less than the distributed default value of 51,200 MB (50 GB).

The seventh diagnostic message is a WARNING that GETMAIN errors might occur because the value of the REGION parameter or the MEMLIMIT parameter has been changed, which results in less memory being available.

The eighth and ninth diagnostic messages display the maximum memory available below and above the line at a given point in time. They are issued immediately after a GETMAIN failure for below the bar memory.

 z/OS sets the limit values based on the REGION= value specified for the job, but several installation exits can be used to override the limits, such as IEFUJV, IEFUSI, IEALIMIT, JES2 Exit 6, or JES3 Exit IATUX03. When a GETMAIN request is made for below the bar memory, it must be satisfied within the displayed limits. That is, contiguous free space within the limits must be available or the request will fail.

 There are 3 forms of error messages involving memory below the bar. The first of these is the GETMAIN error message. The request for the indicated length and subpool failed for the buffer identified by the ID and Info fields. The program making the request, and the offset within that program, are also identified. The GETMAIN error message is normally followed by the diagnostic messages stating the region limits and the maximum memory currently available. The limit values are too low and are the cause of the failure.

 If a GETMAIN failure occurs for memory below the bar under the DTOC component, the component is immediately posted for shutdown. An additional message informs you of this. Other components remain active. To allow the DTOC component to execute, you must increase the value of the Region parameter by an appropriate amount, and then restart CA Vantage SRM.

 For the FREEMAIN error message, the identified area below the bar was thought to be allocated, but either it could not be found or the area attributes did not match. If there has been an abend, this can occur during the cleanup and recovery process.

 There are 4 forms of error messages involving memory above the bar. These 4 always display the name of the TCB, the TCB address and the name of the program that made the request. The first of these is the GET M64 error message. MB= shows the number of megabytes requested, ID= shows the name of the area, UTOKEN= is the token for the area. The next form is the GOT ERR error message.

RC=nnn and Reason=xxRRRRyy show the IBM Return Code and Reason code for the failure. The RRRR portion of the Reason code identifies the specific cause of the failure. RC=8 with Reason=xx0016yy means that the MEMLIMIT value has already been allocated and additional memory above the bar cannot be obtained.

The third form is the FREE M64 error message, which shows the parameters for the FREEMAIN request. The fourth form is the FREE ERR error message, which shows the RC and Reason codes for the failure. The identified area above the bar was thought to be allocated, but it could not be found.

 Action:

 For GETMAIN failures involving below the bar memory, increase the limit values by increasing the Region parameter in the JCL by at least the LEN= value in the error message. Restart the system and verify that the new REGION LIMIT values in the diagnostic messages have increased by the appropriate amounts. If they have not, an installation exit is overriding your specified region request, and you must contact your system programming staff regarding the exits used, the limits being set, and the appropriate action to take

 For GET M64 failures involving above the bar memory, increase the value of the MEMLIMIT parameter in the JCL by at least the MB= value in the error message. (If you are running z/OS 1.7 or an earlier release, also ensure that the fix for IBM APAR OA14391 is applied.) Restart the system and verify that the new MEMORY LIMIT value has increased by the appropriate amount. If it has not, installation exit IEFUSI is overriding your specified MEMLIMIT request, and you must contact your system programming staff regarding this exit, the MEMLIMIT being set, and the appropriate action to take.

 If you are unable to correct the GETMAIN or GET M64 errors by adjusting the REGION or MEMLIMIT parameters in the JCL, or if you get a FREEMAIN or FREE M64 error, then save the JESLOG and MSGE output files and contact CA Support for assistance.

 

Resolution

These error messages mean that the memory size allocated to the Vantage task (below or above the line) is not enough to allow the correct activation of all the required subtasks and functions defined.

 After having checked that all the available GA maintenance is applied to the product and all the task parameters related to Region/Storage dimension are correctly set up (REGION=0M, and MEMLIMIT=0M by default), it is necessary to check also the possible limitation caused by the Z/OS SMF Exits like IEFUSI, and also the value of the ACCT parameter associated with this task using the ACCOUNT command, or the Security Product userid definition command.

 In Z/OS there are several methods to limit by default the size of each user's address space or region, so that they cannot run commands or programs that use large amounts of virtual storage. It can then be possible to override this default limit for individual users to allow only some of them to run programs or commands that require additional storage. 

You can override the region size for individual users/jobs/tasks by using either the Z/OS IEALIMIT exit for storage below 16 MB in virtual storage, or the MVS IEFUSI exit for storage above 16 MB in virtual storage. 

It is also possible to limit the region size for users/jobs/tasks by specifying the maximum region size on either the ACCOUNT command or the Security Product userid definition command.     

The specific error:

 VAN0590E: GETMAIN FAILED, LEN= 67,108,944 SP=000 ID=MUEWAREA FOR_MEMORY_MAP 

... can be bypassed by checking for any limitation in both the IEFUSI SMF Exit and the ACCT parm value set (if any) for the Vantage started task userid. They should have at least the same value and it should be large enough to bypass this error, allowing Vantage to be started correctly.

 In any other situation, collect the complete Vantage task STC joblog, and also the active VKGPARMS and the System Dump, and provide this doc to Broadcom Support via a case to investigate the issue.