Why is IDDAT being called for a SC00NATD transaction?

Document ID : KB000072154
Last Modified Date : 26/02/2018
Show Technical Document Details
Question:
IDDAT  is being called twice for each Internet pricing call. The ids used by the Internet applications are static service accounts and have no SIGNON member. Can we make IDDAT  a cached copy or eliminate the two calls? The goal is to reduce I/O to the IDDAT file. 
Environment:
CICS Transaction Server 
CA IDEAL
Answer:
Even when so SIGNON member is used for the ASYNC RUNs, IDEAL still has to do the I/O to IDDAT to find out. And the minimum is 2 I/Os for the 2 level index to read IDDAT. SIGNON member is currently not cached . You can start an IDEA if you want a SIGNON member to be cached for SC00NATD.