CIU2201S LOAD CIUPFXTB or YYYY with RESP 27 and IUZA in CIUA110C during CICS IA collector startup

Question & Answer

Question

Why would my application owning region (AOR) startup fail with message CIU2201S after I upgrade from CICS Interdependency Analyzer for z/OS (CICS IA) V5.2 to V5.3? These are the messages I have received:

CIU2201S CICS LOAD CIUPFXTB failed RESP=27 RESP2=3 RCODE=01000000 CINT has abended IUZA in program CIUA110C

CIU2201S CICS LOAD YYYY failed RESP=27 RESP2=24 RCODE=01000000 CINT has abended IUZA in program CIUA110C

My Global and General options are as follows

 CINT Collector runtime options for CICUTA01:
   GLOBAL OPTIONS:
     VSAM_FILE_SHARE=Y TERMINATE_ON_ABEND=  HL_TRACE=N RESTORE= N
     LANGUAGE=E
     DATE_FORMAT='YYYY/MM/DD' TIME_FORMAT='HH:MM:SS 12 hrs'
   GENERAL OPTIONS:
     DATA_TO_COLLECT=A PERIODIC_SAVES=Y CINB_TRIGGER=5
     RESTORE_DATA=N MAINTAIN_USAGE_COUNTS=Y DS_SIZE=16
     PROGRAM_EXCLUDE_LIST='CIUXPROG' TRANSID_PREFIX=''
     COMMAND_EXCLUDE_LIST='CIUXCOMM' RESOURCE_PREFIX_LIST=&'CIUPFXTB'
     TRANSACTION_EXCLUDE_LIST='CIUXTRAN' DUMP_HLQ='CICS    '
     DYNAMIC_CALL=Y TRIGGER_FOR_TASK_COLLECTION=1
     COLLECT_LONG_RUNNING_TASKS=Y
     Collect Application Data = 'N'; Application data is not collected

Answer

The CIU2201S messages with the RESP=27 on the EXEC CICS LOAD indicate a PGMIDERR and the RESP2 of 3 and 24, indicate the program could not be found or autoinstalled. (The ' YYYY' is picking up the wrong offset in the CIUCNTL record as it is the CICS IA V5.2 format instead of V5.3).

The resource prefix list CIUPFXTB from CICS IA V5.2 was replaced by the resource compression list module CIUXRCOM in CICS IA V5.3.

You will need to run the CIUJCLCC job (which runs program CIUCFUPD) to create a new CIUCNTL data set for CICS IA V5.3. This program should initialize the DEFAULTS record in the CIUCNTL data set with the new values.

You can upgrade the control file from V3.2 or V5.1. However, in the CICS IA V5.3 documentation topic Configuring an existing collection environment there is a note indicating when upgrading from V5.2 to V5.3 that you need to create a new control file:

 Note
 CICS IA V5.3 does not support upgrading an existing CICS IA Control file.

Here is the topic Creating a new collection environment on creating the V5.3 control file in step 1 in the CICS IA documentation.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSPPUS","label":"CICS Interdependency Analyzer for z\/OS"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"startup","Version":"5.3","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Product Synonym

CICSIA CICS IA;CICS/TS CICSTS CICS TS CICS Transaction Server

Was this topic helpful?

Document Information

Modified date:
24 May 2017

UID

dwa1373031

Tips