Known Issues › z/OS

z/OS

The following known issues were identified in z/OS in this release:

• CICS Cooperative Server-to-Server abend

  CICS Server-to-Server transactions generated and installed using Gen 8.5 abend with S0C4 in TIRMOVP.

  CICS Server-to-Server transactions generated and installed using Gen 8.0 or earlier releases do not encounter the abend.

• CommID mismatch

  When executing cooperative clients with z/OS IMS servers and certain error states are encountered, the following incorrect error message is displayed:

  TIRM626E: Error client/server send/recv protocol not in sync.

  In addition, the CMIDEBUG log indicates that there is a CommID mismatch.

• Codepage

  When the server runtime TIRCRUNI or TIRCRUNC does not have the correct code page translations that are linked into them, the server abends with either a U3500 or IEFT. This must be changed so that the client receives an error instead of the abend. A possible workaround is to verify that the correct translation modules are linked in.

• IMS Cooperative Server-to-Server abend

  IMS Server-to-Server transactions abend with S0C4 in TIRMOVP.

• IMS transaction using zLib abends S0C4 in DSNHLI

  IMS Block Mode transaction that executes zLib Action Block abends S0C4 in DSNHLI.

• Host Encyclopedia

  Occasional panel error: ISPD113 Invalid panel. As a workaround, press the Enter key.

• Build zLib application using z/OS Implementation Toolset

  When processing a remote file created by CA Gen Toolset or CSE to build a z/Lib application using z/OS IT, the techsys name for the CASCADE Action Block is blank and the split step fails with message:

  ERROR – BUILD PROC – COMMON MEMBER’S BUSINESS SYSTEM NOT FOUND. Workaround build using Host Construction or manually add Business System Name to .rmt file.

  When processing a remote file to build a z/Lib application using the z/OS IT, the execute step of the IP gets error message: Link-edit Failed, RC=8 and an UNRESOLVED reference.