search cancel

Why do I get a IDADERRP71E - INTERR: CA-DATADICTIONARY error, RC=GKU when trying to sign-in to Ideal?

book

Article ID: 54197

calendar_today

Updated On:

Products

Datacom DATACOM - AD Ideal CIS COMMON SERVICES FOR Z/OS 90S SERVICES DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS COMMON PRODUCT SERVICES COMPONENT Common Services CA ECOMETER SERVER COMPONENT FOC Easytrieve Report Generator for Common Services INFOCAI MAINTENANCE IPC UNICENTER JCLCHECK COMMON COMPONENT Mainframe VM Product Manager CHORUS SOFTWARE MANAGER CA ON DEMAND PORTAL CA Service Desk Manager - Unified Self Service PAM CLIENT FOR LINUX ON MAINFRAME MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME GRAPHICAL MANAGEMENT INTERFACE WEB ADMINISTRATOR FOR TOP SECRET Xpertware

Issue/Introduction

Description:

When starting a Ideal session, each terminal gets a block of storage allocated for it's Group Key Table. Because IPC allocates storage based on terminal-id, it doesn't matter what user-id is signing on. This block of storage will hold fifteen group keys. This allows for a user to sign onto IDEAL and initiate asynchronous tasks (Like split screen sessions or IDEAL compiles). The PRDINITI DSF command ties up one of the slots in the table and the slot is not released until a PRDTERMI command is issued. When all the slots for a terminal-id are in use, the next PRDINITI command, issued for that terminal, receives a GKU DSF return code.

Solution:

GKU mostly happens because the customer is using SET $ACCOUNT-ID with the wrong transaction ID, i.e. one that points to SC00INIT. This causes SCF to make a DSF initialization call at the start of the "new" session without ever releasing the DSF resources for the "old" session. In this case, the SET $ACCOUNT-ID must be corrected.

The same problem can also occur if CICS terminal autoinstall program is re-using terminal-ids and a previous Ideal session, using the same termid, has abnormally terminated (abend, timeout or unresponsive session closed by user), so no PRDTERMI has been issued. In this case, implementing VPUR can avoid the GKU to occur. See Ideal Administration Guide manual for VPUR implementation. A quick solution for this case is CICS recycling.

Environment

Release: ESBIDL99000-2.2-Extended Support Basic-for CA Ideal
Component: