DC4

Explanation
An error occurred in processing for either IARCP64
or IARST64.
Here are the values and their meanings for IARCP64:Code
Explanation
xx0410xx (IARCP64AbendRsnCellAddrLow)
The cell address passed to the IARCP64 FREE service is within
a meg used for storage pools, but the address is less than the address
of the first usable storage address.Action: Correct the
address passed to IARCP64 FREE, making sure that it is the same address
that was returned from IARCP64 GET.

xx0412xx (IARCP64AbendRsnBuildMotherFromCmro)
The OWNINGTASK was specified as the mother task, but the caller
is running on the CMRO task.  This is not supported.Action: Correct
the specification of OWNINGTASK.  If you need the storage to survive
job step termination, then specify RCT as the owner. If you are unauthorized,
use OWNINGTASK that is set to either CMRO or JOBSTEP.

xx0413xx (IARCP64AbendRsnCellNotInExtent )
The request was to the IARCP64 or IARST64 FREE service, and the
address of the storage passed in, is not within the bounds of a cell
pool.Action: Correct the address passed to IARCP64 FREE
or IARST64 FREE, making sure that it is the same address that was
returned from IARCP64 GET or IARST64 GET.

xx0414xx (IARCP64AbendRsnBuildNotRctOrCmro )
 The parameter list passed to the IARCP64 BUILD service from an
SRB or cross memory environment did not specify RCT or CMRO as the
owning task.Action: Fix the OWNINGTASK parameter to specify
RCT or CMRO. Alternatively, build the pool from a different environment.

xx0415xx (IARCP64AbendRsnBuildCellSizeZero )
The parameter list passed to the IARCP64 BUILD service specified
the CELLSIZE as zero.Action: Change the cell size to be
in the range of 1 to 520 192.

xx0416xx (IARCP64AbendRsnBuildNotAuth)
The parameter list passed to the IARCP64 BUILD service from an
unauthorized caller requested an authorized option: system key, common
storage, RCT ownership, MEMLIMIT=NO, MOTKN, TYPE=FIXED or DREF.Action: Either
correct the environment such that the caller is authorized, or change
the options on IARCP64 BUILD such that it does not request options
that require authorization.

xx0417xx (IARCP64AbendRsnBuildCellSizeTooBig )
The parameter list passed to the IARCP64 BUILD service specified
a cell size larger than the maximum size supported.Action: Specify
a size between 1 and 520 192. If a larger storage area is needed,
consider using IARV64 REQUEST=GETSTOR or GETCOMMON.

xx0418xx (IARCP64AbendRsnBuildKeyNot9)
The parameter list passed to the IARCP64 BUILD service from an
unauthorized caller, specified a storage key other than 9.Action: Either
remove the key specification for an unauthorized caller, specify key
9, or change the program to run in an authorized environment.

xx0419xx (ARCP64AbendRsnCellOverRun)
The request was to the IARCP64 or IARST64 FREE service, and the
trailer data at the end of the cell was detected as being overrun.
 If the overrun is sufficiently large, it causes damage to the following
cell.  The caller is abended, so they can fix the code to not use
more storage than is requested.Action: Determine whether
the storage has been overrun or whether the trailer data was overlaid
by some other code.   Fix the code so that it only uses the amount
of storage requested. Possibly increase the cell size to meet the
program's needs.

xx041Axx (IARCP64AbendRsnCellNotInUse)
The request was to the IARCP64 or IARST64 FREE service, and the
address of the storage passed in, is already in the freed state. 
This happens when an application frees the storage twice.Action: Determine
whether the current application is freeing the storage twice or whether
it is using a cell that some other program is freeing twice.

xx041Bxx (IARCP64AbendRsnNotOnCellBoundary)
The request was to the IARCP64 or IARST64 FREE service, and the
address of the storage passed in is not on a cell boundary in the
cell pool from which the GET request was satisfied.Action: Correct
the address passed to IARCP64 FREE, making sure that it is the same
address that was returned from IARCP64 GET.

xx041Cxx (IARCP64AbendRsnIARV64Error)
During processing of IARCP64 BUILD or GET, a call to the IARV64
service for GETSTOR, GETCOMMON, PAGEFIX, or PROTECT failed. The failing
return code from IARV64 was placed in register 2 before the abend.
The failing reason code from IARV64 was placed in register 3 prior
to the abend.Action: Examine the return and reason code
as documented under IARV64 to determine if you can resolve the problem.

xx041Dxx (IARCP64AbendRsnCellPoolHeaderKeyNot0)
The cell pool header points to a key 0 control block used to protect
cell pool information.  The pointer did not point to key 0 storage.
This would happen if a caller tried to trick the service into getting
storage that the user was not normally allowed to get.Action: Correct
the cell pool address passed to IARCP64 GET, making sure that it is
the same address that was returned from IARCP64 BUILD. Do not modify
the cell pool header, other than through IARCP64 services.

xx041Exx (IARCP64AbendRsnHeaderFailedValidityCheck)
The cell pool header points to a key 0 control block used to protect
cell pool information.  The pointer did not point to a valid structure
used by IARCP64. This would happen if a caller tried to trick the
service into getting storage that the user was not normally allowed
to get.Action: Correct the cell pool address passed to IARCP64
GET, making sure that it is the same address that was returned from
IARCP64 BUILD.

xx041Fxx (IARCP64AbendRsnHeaderDamaged)
The cell pool header authorized area was damaged.  This could
be caused by a storage overlay or by a user deleting a cell pool while
other work units are trying to obtain a cell from the pool.Action: Make
sure that the application does not request cells during or after the
cell pool is deleted.

xx0420xx (IARCP64AbendRsnCphaNotQueued)
The cell pool header authorized area was not queued to the owning
task as expected.  This could happen due to storage overlays, or possibly
the user doing IARCP64 DELETE while the pool was still in use.Action: Make
sure that the application does not request cells during or after the
cell pool is deleted.  If the problem persists, search problem reporting
databases for a fix for the problem. If no fix exists, collect a dump
and contact the IBM® Support
Center.

xx0421xx (IARCP64AbendRsnBuildVersionHigh)
The parameter list passed to the IARCP64 BUILD service has a version
level higher than the current implementation can support. Action: Correct
the call of IARCP64 such that you don't specify a level or use parameters
that are not supported on the release of the operating system on which
it is intended to run.

xx0422xx (IARCP64AbendRsnBuildBadParmlist)
The parameter list passed to IARCP64 BUILD is not addressable
in the caller's key or is not valid storage.Action: Correct
the calling program to place the parameter list in storage addressable
in the primary address space.

xx0423xx (IARCP64AbendRsnBuildNoOwner)
The parameter list passed to the IARCP64 BUILD service for a common
cell pool does not have an owner option specified.Action: Add
the OWNER keyword to the call of IARCP64 BUILD when building a cell
pool in common.

xx0424xx (IARCP64AbendRsnDeleteNotChained)
A request was made to the IARCP64 DELETE service for a user key
cell pool. The control information for this cell pool was missing
from the system queue used to maintain it.  This can only happen if
the caller has two tasks racing to delete the same cell pool.Action: Fix
the application cleanup logic so that the cell pool is only deleted
once.

xx0425xx (IARCP64AbendRsnPoolNotInCallerKey)
The request to IARCP64 GET or DELETE was against a pool that was
not in the key of the caller.Action: You must be in a key
that has the ability to modify the pool storage for the request to
be processed.

xx0426xx (IARCP64AbendRsnPrimaryExtentOverlaid)
The request to IARST64 or IARCP64 GET was against a storage pool
where the primary extent control information had been overlaid.Action: Search
problem reporting databases for a fix for the problem. If no fix exists,
collect a dump and report the problem to the IBM Support Center.

xx0427xx (IARCP64AbendRsnSecondaryExtentOverlaid)
The request to IARST64 or IARCP64 GET was against a storage pool
where the secondary extent control information had been overlaid.Action: Search
problem reporting databases for a fix for the problem. If no fix exists,
collect a dump and report the problem to the IBM Support Center.

xx0428xx (IARCP64AbendRsnUnexpectedError)
During processing of IARCP64 BUILD, DELETE or the cell pool expansion
on a GET, an unexpected abend occurred.  An SDUMP should have been
generated.Action: Search problem reporting databases for
a fix for the problem. If no fix exists, collect the dump and report
the problem to the IBM Support
Center.

xx052Axx (IARCP64AbendRsnValidationError)
The call to the IARCP64 GET service detected a validation error
when locating the storage pool to be used. The possible cause is the
storage overlay of the storage pool control block in the caller's
key.Action: Search problem reporting databases for a fix
for the problem. If no fix exists, collect a dump and report the problem
to the IBM Support Center.

Here are the values and their meanings for IARST64: Code
Explanation
xx0410xx (IARST64AbendRsnCellAddrLow
The storage address passed to the IARST64 FREE service is within
a meg used for storage pools, but the address is less than the address
of the first usable storage address.Action: Correct the
address passed to IARST64 FREE, making sure that it is the same address
that was returned from IARST64 GET.

xx0413xx (IARST64AbendRsnCellNotInExtent)
The request was to the IARCP64 or IARST64 FREE service, and the
address of the storage passed in is not within the bounds of a cell
pool.Action: The address passed to IARST64 REQUEST=FREE
must be the same as the address obtained from IARST64 REQUEST=GET.

xx0419xx (IARST64AbendRsnCellOverRun)
The request was to the IARCP64 or IARST64 FREE service, and the
trailer data at the end of the cell was detected as being overrun.
 If the overrun is sufficiently large, it causes damage to the following
cell. The caller is abended so that they can fix the code to not use
more storage than is requested.Action: Determine whether
the storage has been overrun or whether the trailer data was overlaid
by some other code. Fix the code so that it only uses the amount of
storage requested.

xx041Axx (IARST64AbendRsnCellNotInUse)
The request was to the IARCP64 or IARST64 FREE service, and the
address of the storage passed in is already in the freed state. This
happens when an application frees the storage twice.Action: Determine
whether the current application is freeing the storage twice or whether
it is using a cell that some other storage is freeing twice.

xx041Bxx (IARST64AbendRsnNotOnCellBoundary)
The request was to the IARCP64 or IARST64 FREE service, and the
address of the storage passed in is not on a cell boundary in the
cell pool from which the GET request was satisfied.Action: When
freeing storage with IARST64 REQUEST=FREE, make sure to specify the
address that was returned by IARST64 REQUEST=GET.

xx041Cxx (IARST64AbendRsnIARV64Error)
During processing of IARST64 GET, a call to the IARV64 service
for GETSTOR, GETCOMMON, PAGEFIX, or PROTECT failed. The failing return
code from IARV64 was placed in register 2 before the abend. The failing
reason code from IARV64 was placed in register 3 before the abend.Action: Examine
the return and reason code as documented under IARV64 to determine
if you can resolve the problem.

xx0420xx (IARST64AbendRsnCphaNotQueue)
The cell pool header authorized area was not queued to the owning
task as expected. This could happen due to storage overlays or the
caller bypassing the IARST64 macro and PCing directly to the service
with incorrect input paramters.Action: Make sure that the
application is using the IARST64 macro to request storage. If the
problem persists, search problem reporting databases for a fix for
the problem. If no fix exists, collect a dump and contact the IBM Support Center.

xx0425xx (IARST64AbendRsnPoolNotInCallerKey)
The request to IARST64 GET was against a storage pool that was
not in the key of the caller. Normally, this abends with an 0C4, but
if the pool is out of cells and is in storage that is not fetch protected,
the pool expand routine verifies that the caller is allowed to modify
this storage pool.Action: You must be in a key that has
the ability to modify the pool storage for the request to be processed.

xx0426xx (IARST64AbendRsnPrimaryExtentOverlaid)
The request to IARST64 or IARCP64 GET was against a storage pool
where the primary extent control information had been overlaid.Action: Search
problem reporting databases for a fix for the problem. If no fix exists,
collect a dump and report the problem to the IBM Support Center.

xx0427xx (IARST64AbendRsnSecondaryExtentOverlaid)
The request to IARST64 or IARCP64 GET was against a storage pool
where the secondary extent control information had been overlaid.Action: Search
problem reporting databases for a fix for the problem. If no fix exists,
collect a dump and report the problem to the IBM Support Center.

xx0428xx (IARST64AbendRsnUnexpectedError)
During processing of IARST64 GET, an unexpected abend occurred.
An SDUMP should have been generated.Action: Search problem
reporting databases for a fix for the problem. If no fix exists, collect
the dump and report the problem to the IBM Support
Center.

xx0511xx (IARST64AbendRsnKeyGT7Common)
The request to IARST64 GET was for common storage, but the requested
or caller key was greater than key 7.  You cannot allocate common
storage in key 8 or above.Action: Correct the key passed
to IARST64 GET or change your request to get private storage.

xx0512xx (IARST64AbendRsnGetMotherFromCmro)
The request was to the IARST64 GET service and specified OWNINGTASK(MOTHER),
but the caller is running on the CMRO task.  You cannot request that
the mother task be the storage owner from the CMRO task.Action: Either
specify CMRO as the owner or specify RCT if you want the storage to
persist across termination of the CMRO.

xx0514xx (IARST64AbendRsnGetNotRctOrCmro)
The request was to the IARST64 GET service for private storage,
and the caller was running in cross memory mode or SRB mode.  In these
environments, the OWNINGTASK parameter must be set to RCT or CMRO.
 Neither of these was specified, so the request failed.Action: Specify
the OWNINGTASK parameter as RCT or CMRO.

xx0515xx (IARST64AbendRsnGetCellSizeZero)
The request was to the IARST64 GET service and specified a length
of zero.Action: Specify a length between 1 and 128 KB.

xx0516xx (IARST64AbendRsnGetNotAuth)
The request was to the IARST64 GET service and specified a parameter
that requires the caller to be running in key 0-7.  The caller is
not authorized to use authorized options of COMMON, DREF, FIXED, OWNINGTASK(RCT),
CALLERKEY(NO), and Key00ToF0 set to a system key.Action: Either
run the code in key 0-7 or do not use authorized options.

xx0517xx (IARST64AbendRsnGetCellSizeTooBig)
The request was to the IARST64 GET service and specified a length
greater than 128 KB.Action: Specify a size between 1 and
128 KB.  If larger storage is needed, consider using IARCP64 or IARV64
GETSTOR or GETCOMMON.

xx0518xx (IARST64AbendRsnGetKeyNot9)
The request was to the IARST64 GET service and specified a CALLERKEY(NO)
and a value for Key00ToF0 that was not key 9, and the caller is not
authorized.Action: The only key that an unauthorized user
can specify is key 9.  Either request key 9 or change the specification
to CALLERKEY(YES).

xx0529xx (IARST64AbendRsnGetSizeTooBig)
The call to the IARST64 GET service specified a cell size larger
than the maximum size supported.Action: Specify a size between
1 and 128 KB. If a larger storage area is needed, consider using IARCP64
or IARV64 REQUEST=GETSTOR or GETCOMMON.

xx052Axx (IARST64AbendRsnValidationError)
The call to the IARST64 GET service detected a validation error
when locating the storage pool to be used. The possible cause is the
storage overlay of the storage pool control block in the caller's
key.Action: Search problem reporting databases for a fix
for the problem. If no fix exists, collect a dump and report the problem
to the IBM Support Center.

xx052Bxx (IARST64AbendRsnMemLimitNoUnauth )
The call to the IARST64 GET service requested MEMLIMIT=NO, but
is running unauthorized (key 8-15 and problem program state).Action: Either
specify MEMLIMIT=YES or call from an authorized environment.

xx052Cxx (IARST64AbendRsnCellLT4Gig)
The call to the IARCP64 or IARST64 FREE service is passed to a
cell address less than 4GB, so it cannot be a valid cell address in
a 64-bit cell pool.Action: Pass a storage address that is
obtained with IARCP64 or IARST64 GET.

xx052Dxx (IARST64AbendRsnLocalSysAreaYesUnauth)
The call to the IARST64 GET service requested LOCALSYSAREA=YES,
but is running unauthorized (key 8-15 and problem program state).Action: Either
specify LOCALSYSAREA=NO or CALL from an authorized environment.

System action
The abend is delivered to the applications recovery
routine (if any). The application can retry or percolate.

Operator response
None.

System programmer response
None.

Programmer response
The programmer needs to determine whether
the problem was caused by bad input, improper use of authorized option,
a structure damaged by the application, or a defect in the service.
For user-triggered problems, correct the error. For suspected damaged
control blocks, search problem reporting databases for a fix for the
problem. If no fix exists, collect a dump and contact the IBM Support Center.

Problem determination
If the caller is authorized, some of the
abends trigger a system SVC DUMP. For unauthorized callers, no dump
will be taken. You can either allocate a SYSMDUMP DD to gather a SYSMDUMP
or use a SLIP on DC4 abends to collect a dump.

Module
IAXCV, IAXCY, or IAXSV