Problem data from the linkage stack

The linkage stack is used to identify a program that requested a system service, if the service was entered by a branch instruction.

For example, to see the linkage stack entry that is associated with address space identifier (ASID) X'1A', use the IPCS subcommand:
   SUMMARY FORMAT ASID(X'1a')
The resulting dump for the linkage stack associated with the address space (see Figure 1) shows one entry, as follows:
BAKR STATE ENTRY
A Branch and Stack (BAKR) instruction caused this entry.
SASN..1A and PASN..1A
At the time of the BAKR, the program was not in cross memory mode. When the branching program is not in cross memory mode, secondary address space number (SASN) and primary address space (PASN) are identical. If the program had been in cross memory mode, SASN and PASN would not have been identical.
PSW..070C0000 80FD7618
The return address of the branch caused by the BAKR is FD7618. This address is in the right half of the program status word (PSW).

Many system services are called through branches. For branch entry services, use register 14 to identify the calling program. Look for the problem in the calling program. See z/OS MVS Programming: Extended Addressability Guide for more information about the linkage stack.