B78

Explanation

The error occurred when the system tried to run one of the following:
  • An RC, RU, VRC, or VRU GETMAIN macro
  • An RC or RU FREEMAIN macro
  • A STORAGE macro.
A reason code in the SDWACRC field of the system diagnostic work area (SDWA) explains the error. The reason code appears in the form xxxxxxyy, where xxxxxx is the internal reason for the error, and yy is described in the following table:
Code
Explanation
04
The macro tried to obtain or free storage in an undefined subpool.
08
The program issuing the macro is not authorized to obtain or free storage in system subpools. The program must be supervisor state, key 0, or authorized program facility (APF) authorized.
0C
A global branch entry caller of the GETMAIN or FREEMAIN macro tried to obtain or free a nonglobal subpool.
10
The LOC parameter is not valid. Virtual storage manager (VSM) received a request for either a fetch-protected local system queue area (LSQA) or a disabled reference subpool that resides below 16 megabytes. Fetch-protected LSQA and disabled reference subpools are supported only above 16 megabytes.
14
A local branch entry caller of the GETMAIN or FREEMAIN macro did not hold the local lock for the address space that is currently addressable.
18
An incorrect task control block (TCB) address was specified on a branch entry or STORAGE request. Register 4 at the time of the abend contains the TCB address.
1C
The address space control block (ASCB) address specified on a branch entry request was not the current ASCB.
24
The user of the STORAGE macro is disabled.
28
A caller that is not in supervisor state, or keys 0 through 7, specified the ALET parameter or the TCBADDR parameter on the STORAGE macro.
2C
The caller violated the STORAGE service's locking restrictions by holding a suspend lock that is not the local lock of the target address space.
30
The specified ALET does not translate to a valid STOKEN.
34
The STOKEN does not translate to a valid ASCB; the address space from which the storage is to be obtained or released is not valid for cross memory access.
38
The target address space is the master scheduler's address space, which is not the home address space.
3C
The target address space is either in the process of ending, or has ended.
40
A user violated serialization requirements by calling global branch entry GETMAIN or FREEMAIN while enabled.
44
A program issued a SETLOCK OBTAIN,TYPE=VSMFIX macro before issuing a VSMLIST or VSMLOC request. The program or an associated FRR issued a GETMAIN, FREEMAIN, or STORAGE request before issuing SETLOCK RELEASE,TYPE=VSMFIX.
48
A program issued a SETLOCK OBTAIN,TYPE=VSMPAG macro before issuing a VSMLOC request. The program or an associated FRR issued a GETMAIN, FREEMAIN, or STORAGE request before issuing SETLOCK RELEASE,TYPE=VSMPAG.
4C
An incorrect subpool was specified on a GETMAIN or STORAGE OBTAIN request with the LOC=EXPLICIT keyword specified. Valid subpools for unauthorized programs are:
  • 0-127
  • 131-132
Valid subpools for authorized programs are:
  • 0-127
  • 129-132
  • 240
  • 250-252
50
A GETMAIN or STORAGE OBTAIN request failed because the address specified on the INADDR keyword was greater than 16 megabytes and the central storage backing specified on the LOC keyword was BELOW. The virtual storage address specified on INADDR and the central storage backing specified on the LOC=EXPLICIT must be a valid combination. For example, if the address specified on INADDR is for virtual storage above 16 megabytes, specify LOC=EXPLICIT or LOC=(EXPLICIT,ANY). The following combinations are valid:
  • virtual above, central any
  • virtual any, central any
  • virtual below, central below
  • virtual below, central any
54
A GETMAIN or STORAGE OBTAIN request failed because the address specified on the INADDR keyword was not on an doubleword boundary.
58
Branch entry caller for local storage request is running in AR mode.
5C
A program attempted to obtain or release user-key (8 - 15) storage from a CSA subpool but the ALLOWUSERKEYCSA(NO) parameter is specified in a DIAGxx member of PARMLIB and either of the following conditions is true:
  • An appropriate restricted use common service area (RUCSA/extended RUCSA) is not defined.
  • The address space in which the caller is running lacks SAF authority to reference user-key CSA storage.

For more information, see Restricted use common service area (RUCSA/extended RUCSA) in z/OS MVS Initialization and Tuning Guide.

60
The boundary indicated by the CONTBDY parameter on a GETMAIN or STORAGE OBTAIN request was less than the requested storage area length.
64
CONTBDY or STARTBDY was specified on a variable-length GETMAIN or STORAGE OBTAIN request.
68
CONTBDY or STARTBDY was specified with LOC=EXPLICIT on a GETMAIN or STORAGE OBTAIN request.
6C
CONTBDY or STARTBDY was specified with BNDRY=PAGE on a GETMAIN or STORAGE OBTAIN request.
70
Storage overlay detected while freeing storage. VSM processing has recovered this error.
74
PAGEFRAMESIZE1MB was specified with LOC= on a STORAGE OBTAIN request for a subpool that does not support PAGEFRAMESIZE1MB. The supported subpools are 0-127, 129-132, 240, 244 and 250-252. If an unsupported subpool is required, do not specify LOC=PAGEFRAMESIZE1M.
78
An unsupported subpool was specified on the storage obtain request with the EXECUTABLE=NO keyword specified. See the "Storage subpools and their attributes" table in The subpool table in z/OS® MVS™ Programming: Authorized Assembler Services Guide to determine which subpools can be specified as non-executable.
7C
STORAGE RELEASE with ALET for a task related subpool is specified where the target address space of the Job Step Program task has terminated.

System action

The system issues message IEA705I. The system abnormally ends the current task.

Programmer response

Depending on the reason code, do one of the following:
Code
Response
04
Ensure that the specified subpool is not incorrectly specified or modified.
08
If the program requires system subpools, ensure that the program resides in an authorized program library. Users of the STORAGE macro must also switch to supervisor state, or key 0.
0C
Note that a global branch entry request can only request global subpools, that is, system queue area (SQA) subpools or common service area (CSA) subpools.
10
An incorrect bit combination for the LOC operand was put into an input register.
14
Ensure that a local branch entry caller holds the local lock for the currently addressable address space.
44
Issue the SETLOCK RELEASE,TYPE=VSMFIX macro before you issue a GETMAIN, FREEMAIN, or STORAGE macro.
48
Issue the SETLOCK RELEASE,TYPE=VSMPAG macro before you issue a GETMAIN, FREEMAIN, or STORAGE macro.
A4
If the program requires the LOC=PAGEFRAMESIZE1M specification, ensure that a supported subpool is also specified (0-132,240,244). If an unsupported subpool is required, then do not specify LOC=PAGEFRAMESIZE1M.
ALL
Check for program errors that modify the parameter list.

Source

Virtual storage manager (VSM)