067

Explanation
An access register translation exception occurred.
A hexadecimal reason code in register 15 explains the error; x in
the reason code contains diagnostic data: Code
Explanation
00000004
A program encountered a page fault, segment fault, or address
space secondary entry table (ASTE) validity fault on a data space
that was deleted.
00000008
The target address space was created after the access list entry
(ALE) was created.
0000000C
The interrupted program's extended authority index (EAX) does
not have Set Secondary ASN (SSAR) authority
to the target address space specified by a private ALE.
00000010
The EAX in the ALE does not have SSAR authority to the target
address space.
00000014
An ASTE sequence exception occurred while attempting to reference
an incorrect or deleted data space.
00000018
An unexpected error occurred in the access register translation
second level interrupt handler (SLIH).
00000020
An ASTE validity exception occurred when a program tried to access
a subspace that had been deleted.
00000024
An ASTE sequence exception occurred when a program tried to access
a subspace that had been deleted.
00000064
A system error occurred during the fetch of a PR, PTI, or SSAIR
instruction.
00000068
The target PASN or SASN is no longer valid.
00000072
A system error occurred.
00000076
The desired target PASN or SASN has a non-matching instance number.
xxxx0Axx
A program attempted to reference a data space that has been deleted.
xxxx0Bxx
An unexpected error occurred when the system tried to bring a
data space page into real storage.

System action
The system abends the task and writes an ABEND
dump for the failing job step.

System programmer response
Do the following: Obtain the ABEND dump for the failing job step. If the JCL for
the step did not contain a DD statement for an ABEND dump, add a SYSMDUMP
DD statement.
Find the reason code in register 15.
Use the PSW address at the time of the error to obtain the name
of the load module.
If the module is installation-provided, correct it and run the
job step again.
If the module is an IBM® module,
or if the problem persists, search problem reporting data bases for
a fix. If no fix exists, contact the IBM Support
Center.

Source
Program Call/authorization (PC/AUTH)