Accommodate increase in ESQA

Description

With the introduction of the z/OS V1R13 RSM Enablement Offering Web deliverable, there is an increased allocation of 24K (6 pages) in ESQA per CPU per LPAR. This increased allocation in ESQA per CPU includes general purpose CPs, zIIPs, and zAAPs regardless of the status (online, offline, configured, stand-by, and so forth) of the hardware. Because of this increase in ESQA, if you change the ESQA size, the available private storage may affect application execution on your system.

Table 1 provides more details about this migration action. Use this information to plan your changes to the system.

Table 1. Information about this migration action
Element or feature: BCP
When change was introduced: z/OS® V1R13 RSM Enablement Offering Web deliverable.
Applies to migration from: z/OS V1R13 without the z/OS V1R13 RSM Enablement Offering Web deliverable.
Timing: Before the first IPL of z/OS V2R2.
Is the migration action required? Yes, if the increase in ESQA usage might cause you to run out of ESQA storage.
Target system hardware requirements: The migration action is relevant on all servers.
Target system software requirements: None.
Other system (coexistence or fallback) requirements: None.
Restrictions: None.
System impacts: Failure to have sufficient private storage available might result in errors that affect the running of your applications. The following messages might be issued:
IRA103I SQA/ESQA HAS EXPANDED 
INTO CSA/ECSA BY xxxx PAGES

IRA104I SQA/ESQA EXPANSION INTO 
CSA/ECSA HAS BEEN RELIEVED
Related IBM® Health Checker for z/OS check: VSM_CSA_CHANGE. You can use this health check to identify changes in the size of CSA or private (including the extended areas) since the last IPL.

Steps to take

Review your ESQA specification in IEASYSxx, to ensure that an ESQA increased allocation of 24K per CPU used on the LPAR will not adversely affect your system. If you need to increase your ESQA specification, you should also review the effects on your current available private storage usage above the 16 MB line using reports from RMF or an equivalent product. Adjust values accordingly.

Note: On a z13 server, z/OS can use symmetric multi-threading (SMT) if parmlib member LOADxx specifies PROCVIEW CORE. Here, the system defines 2 threads for every core (including CPs and zIIPs). For example, with 1 general purpose CP core and 1 zIIP core, z/OS allocates 2 CP threads and 2 zIIP threads, which results in 24K times 4 CPUs, for a total increased allocation of 96K.

Reference information

For more information, see the following references:
Parent topic: BCP actions to perform before the first IPL of z/OS V2R2