The storage addressed by the CICS registers and PSW

Any storage addressed by the CICS® registers and PSW is included in the error data for the failing task.

Figure 1, Figure 2, and Figure 3 show parts of an example storage report for a task that failed when a program check was detected.

Only the values of the registers and PSW, not the storage they address, are guaranteed to be as they were at the time of the error. The storage that is shown is a snapshot taken at the time the internal system dump request was issued. Data might change because, for example, a program check was caused by an incorrect address in a register, or short lifetime storage is addressed by a register.

Also, in general, where error data is given for a series of errors, the older the error, the less likely it is that the storage is as it was at the time of the failure. The most recent error has the highest error number; it might not be the first error shown in the output.

The Breaking Event Address is the address of the last successful branch before the program check. If it is available, you can use it to help determine the location of a wild branch instruction.

Figure 1. Storage report for a task that has experienced a program check - part 2
 CICS Registers and PSW

   PSW:  079D1001 80000000 00000000 2A1E7742   Instruction Length:  4  Interrupt Code:  04
   Exception Address:  00000000_00000000

   Execution key at Program Check/Abend: 9     Addressing Mode:  64

   Space at Program Check/Abend: Subspace

   Breaking Event Address: 00000000_2A1E768A - offset 0000026A in module DFHGA680

   64-BIT REGISTERS 0-15

   GPR 0-3   00000000_C6F4E2C1  00000000_2AA00740  00000000_0008196E  00000000_29992B78
   GPR 4-7   00000000_2A8411D0  00000000_00000002  00000000_29390988  00000000_2A1E7564
   GPR 8-B   00000000_2AA00690  00000000_000C0000  00000000_2AA00048  00000000_2AA00100
   GPR C-F   00000000_2A1E77A8  00000000_2AA00690  00000000_2A1E75A2  00000000_00000000

   ACCESS REGISTERS 0-15

   AR  0-3   009FF890  00010004  00000000  00000000
   AR  4-7   00000000  00000000  00000000  00000000
   AR  8-B   00000000  00000000  00000000  00000000
   AR  C-F   00000000  00000000  00000000  00000000

   FLOATING POINT REGISTERS 0-15

   FPR 0-3   00000000_00000000  00000000_00000000  00000000_00000000  00000000_00000000
   FPR 4-7   00000000_00000000  00000000_00000000  00000000_00000000  00000000_00000000
   FPR 8-B   00000000_00000000  00000000_00000000  00000000_00000000  00000000_00000000
   FPR C-F   00000000_00000000  00000000_00000000  00000000_00000000  00000000_00000000
   FPCR      00000000

The format of the PSW is described in z/Architecture Principles of Operation. The information in the PSW can help you to find the details needed by the IBM® Support Center. You can find the address of the failing instruction, and thus its offset within the module, and also the abend type. You find the identity of the failing module itself by examining the kernel linkage stack, as described in Using the linkage stack to identify the failing module.

Figure 2. Storage report for a task that has experienced a program check - part 3
   Data at PSW: 00000000_2A1E7742    Module: DFHGA680   Offset: 00000322

 PSWDATA 2A1E7420

    0000  C4C6C8C7 C1F6F8F0 E3F0021C 001758F0  F0D058F0 F01458F0 F00C58FF 004407FF  *DFHGA680T0.....00}.00..00.......*    2A1E7420
    0020  5CC6C9D3 D3C9D55C A7F40089 23C1D4F6  F4F2F0F1 404DC95D 40F1F061 F0F361F1  **FILLIN*x4.i.AM64201 (I) 10/03/1*    2A1E7440
    0040  F240F1F0 4BF5F040 A9D6E2F6 F8F04040  40C3C9C3 E240F5F6 F5F560E8 F0F4404D  *2 10.50 zOS680   CICS 5655-Y04 (*    2A1E7460
    0060  C35D40C3 D6D7E8D9 C9C7C8E3 40C9C2D4  40C3D6D9 D7D6D9C1 E3C9D6D5 6B406B40  *C) COPYRIGHT IBM CORPORATION, , *    2A1E7480
    0080  C1D3D340 D9C9C7C8 E3E240D9 C5E2C5D9  E5C5C44B 40E44BE2 4B40C7D6 E5C5D9D5  *ALL RIGHTS RESERVED. U.S. GOVERN*    2A1E74A0
    00A0  D4C5D5E3 40E4E2C5 D9E240D9 C5E2E3D9  C9C3E3C5 C440D9C9 C7C8E3E2 406040E4  *MENT USERS RESTRICTED RIGHTS - U*    2A1E74C0
    00C0  E2C56B40 C4E4D7D3 C9C3C1E3 C9D6D540  D6D940C4 C9E2C3D3 D6E2E4D9 C540D9C5  *SE, DUPLICATION OR DISCLOSURE RE*    2A1E74E0
    00E0  E2E3D9C9 C3E3C5C4 40C2E840 C7E2C140  C1C4D740 E2C3C8C5 C4E4D3C5 40C3D6D5  *STRICTED BY GSA ADP SCHEDULE CON*    2A1E7500
    0100  E3D9C1C3 E340E6C9 E3C840C9 C2D440C3  D6D9D74B 40D3C9C3 C5D5E2C5 C440D4C1  *TRACT WITH IBM CORP. LICENSED MA*    2A1E7520
    0120  E3C5D9C9 C1D3E240 6040D7D9 D6D7C5D9  E3E840D6 C640C9C2 D400EBEC D0080024  *TERIALS - PROPERTY OF IBM...}...*    2A1E7540
    0140  A7150007 00000202 2A1E78C8 0000E3F0  10040017 0DEFC0C0 00000119 B90400D1  *x..........H..T0......{{.......J*    2A1E7560
.
.
.
    03E0  00000816 00000817 00000818 00000819  0000081A 0000081B 0000081C 0000081D  *................................*    2A1E7800
    0400  0000081E 0000081F C1D4F3F1 E7F2F0F1  E7D7C3E3 C1404040 C1D4F6F4 F2F0F140  *........AM31X201XPCTA   AM64201 *    2A1E7820
    0420  4410                                                                      *..                              *    2A1E7840

   Data at BEAR: 2A1E768A    Module: DFHGA680   Offset: 0000026A

 BEARDATA 2A1E7420

    0000  C4C6C8C7 C1F6F8F0 E3F0021C 001758F0  F0D058F0 F01458F0 F00C58FF 004407FF  *DFHGA680T0.....00}.00..00.......*    2A1E7420
    0020  5CC6C9D3 D3C9D55C A7F40089 23C1D4F6  F4F2F0F1 404DC95D 40F1F061 F0F361F1  **FILLIN*x4.i.AM64201 (I) 10/03/1*    2A1E7440
    0040  F240F1F0 4BF5F040 A9D6E2F6 F8F04040  40C3C9C3 E240F5F6 F5F560E8 F0F4404D  *2 10.50 zOS680   CICS 5655-Y04 (*    2A1E7460
    0060  C35D40C3 D6D7E8D9 C9C7C8E3 40C9C2D4  40C3D6D9 D7D6D9C1 E3C9D6D5 6B406B40  *C) COPYRIGHT IBM CORPORATION, , *    2A1E7480
    0080  C1D3D340 D9C9C7C8 E3E240D9 C5E2C5D9  E5C5C44B 40E44BE2 4B40C7D6 E5C5D9D5  *ALL RIGHTS RESERVED. U.S. GOVERN*    2A1E74A0
    00A0  D4C5D5E3 40E4E2C5 D9E240D9 C5E2E3D9  C9C3E3C5 C440D9C9 C7C8E3E2 406040E4  *MENT USERS RESTRICTED RIGHTS - U*    2A1E74C0
    00C0  E2C56B40 C4E4D7D3 C9C3C1E3 C9D6D540  D6D940C4 C9E2C3D3 D6E2E4D9 C540D9C5  *SE, DUPLICATION OR DISCLOSURE RE*    2A1E74E0
    00E0  E2E3D9C9 C3E3C5C4 40C2E840 C7E2C140  C1C4D740 E2C3C8C5 C4E4D3C5 40C3D6D5  *STRICTED BY GSA ADP SCHEDULE CON*    2A1E7500
    0100  E3D9C1C3 E340E6C9 E3C840C9 C2D440C3  D6D9D74B 40D3C9C3 C5D5E2C5 C440D4C1  *TRACT WITH IBM CORP. LICENSED MA*    2A1E7520
    0120  E3C5D9C9 C1D3E240 6040D7D9 D6D7C5D9  E3E840D6 C640C9C2 D400EBEC D0080024  *TERIALS - PROPERTY OF IBM...}...*    2A1E7540
    0140  A7150007 00000202 2A1E78C8 0000E3F0  10040017 0DEFC0C0 00000119 B90400D1  *x..........H..T0......{{.......J*    2A1E7560
.
.
.
    0320  20000700 A7150017 002A0000 C1D4F3F1  F2F0F140 D6A58599 A69989A3 85409686  *....x.......AM31201 Overwrite of*    2A1E7740
    0340  40D9C4E2 C1409596 A3408485 A38583A3  85840A23 00004110 D0B041E0 C11650E0  * RDSA not detected......}..\A.&\*    2A1E7760
    0360  10009680 1000E3F0                                                         *..o...T0                        *    2A1E7780

The registers might point to data in the CICS region. If the values they hold can represent 24-bit addresses, you see the data around those addresses. If their values can represent 31-bit addresses, you see the data around those addresses. If their values can represent 64-bit addresses, you see the data around those addresses.

The contents of a register might represent a 24-bit address, a 31-bit address, and a 64-bit address. In that case, you get three sets of addressed data. A lower half of the register might contain a 24-bit address with a higher order bit set, making it appear like a 31-bit address; or it could contain a genuine 31-bit address. The 64-bit register could also contain a genuine 64-bit address.

Figure 3. Storage report for a task that has experienced a program check - part 4
   Data at Registers

   REG 0   00000000_C6F4E2C1

 64-bit data cannot be accessed **

 31-bit data cannot be accessed **

 24-bit data follows:

 REGDATA 00F4E2C1

   -0080  00000004 08001000 00000000 03000028  B6A356E0 000000C9 D5E3C5D9 D5C1D300  *.................t.\...INTERNAL.*    00F4E241
   -0060  00000000 00000000 00000000 F4E24000  00000000 00000000 00000000 000000C1  *............4S ................A*    00F4E261
   -0040  E2C3C200 FB028000 FDB30000 00000000  00000000 00000000 00000000 00000000  *SCB.............................*    00F4E281
   -0020  00000000 02000000 0100FF00 0000007F  F18E10C0 80000028 E66A0000 00000000  *..............."1..{....W.......*    00F4E2A1

    0000  00000000 4D1138CA 30B230C6 0AB4A400  00000080 9FDA18CA 30B20E00 00000000  *....(......F..u.................*    00F4E2C1
    0020  9FD0C0FF FF010000 00000000 9FDB6000  2600C600 00000000 00000000 9FE04000  *.}{...........-...F..........\ .*    00F4E2E1
    0040  00000000 00000000 00000040 00000002  78760002 78472800 00038000 00000000  *........... ....................*    00F4E301
    0060  00000000 00000000 00000000 00000000  F9DB4000 00000000 00000000 00000000  *................9. .............*    00F4E321
    0080  00000700 00000000 00000000 098DA600  00000000 00000000 00000000 00000000  *..............w.................*    00F4E341
    00A0  9FEAF8FF FFFFFF00 00000000 00000000  00000000 00000002 8040807F FCC0007F  *..8...................... .".{."*    00F4E361
    00C0  FD7B6000 02000100 07000200 9FEB0800  00000000 00000000 00000000 9FF890C0  *.#-..........................8.{*    00F4E381
    00E0  00000002 C2D00000 00000000 000000CA  30B23049 6D1DA300 00000000 00000000  *....B}.............._.t.........*    00F4E3A1

   REG 1   00000000_2AA00740

 64-bit data follows:

 REGDATA 00000000_2AA00740

   -0080  00000000 29992B78 00000000 2A8411D0  00000000 00000002 00000000 29390988  *.....r.......d.}...............h*    2AA006C0
   -0060  00000000 2A1E7564 00000000 2AA00690  00000000 00089FC4 00000000 2AA00048  *.......................D........*    2AA006E0
   -0040  00000000 2AA00100 00000000 2A1E77A8  00000000 2AA00048 00000000 00000000  *...............y................*    2AA00700
   -0020  00000000 2AA00100 00000000 00000000  00000000 2AA00690 00000000 00000000  *................................*    2AA00720

    0000  2A1E787C AAA00840 00000000 00000000  00000000 00000000 00000000 00000000  *...@... ........................*    2AA00740
    0020  00000000 00000000 00000000 00000000  00000000 00000000 00000000 00000000  *................................*    2AA00760
    0040 -    00FF LINES SAME AS ABOVE                                                                                    2AA00780

 24-bit data cannot be accessed
If, for any reason, the register does not address any data, one of the following messages is issued:
24-bit data cannot be accessed
31-bit data cannot be accessed
64-bit data cannot be accessed
This means that the addresses cannot be found in the system dump of the CICS region. MVS™ keeps a record of how CICS uses storage, and any areas not used by CICS are considered to lie outside the CICS address space. Such areas are not dumped in an MVS SDUMP of the region.

It is also possible that the addresses were in the CICS region, but were not included in the SDUMP. This is because MVS enables you to take SDUMPs selectively, for example "without LPA". If a selective SDUMP occurred without your knowledge, you might think you had an addressing error when the address was actually valid.



dfhs1c0044.html | Timestamp icon Last updated: Monday, 5 June 2017