Skip to main content

Technotes(Troubleshooting)

warning: Creating default object from empty value in /homepages/10/d92055197/htdocs/cicsworld2/modules/taxonomy/taxonomy.pages.inc on line 33.
Technotes(Troubleshooting)

TSS9410E Unknown classname (CCICSCMD) for SVC (RACHECK) during CICS TS startup

You upgrade CICS Transaction Server for z/OS (CICS TS) to a new release. Afterwards, CICS initialization fails with CA Top Secret message TSS9410E indicating that the CCICSCMD classname is unknown. In addition to CCICSCMD, the failure can be seen for other CICS RACF resource class such as FCICSFCT and TCICSTRN .

EYUNL0150W Get Topology for resource PROGRAM failed RESP=27 RESP2=1

During a CICS WARM start, you receive message EYUNL0150W Get Topology for resource PROGRAM failed with RESP=27 and RESP2=1 for COMMAND NEXT. This occurs when the CICSPlex SM (CPSM) MAS agent code begins and Topology collection browses through all programs defined in the region. A COLD or INITIAL startup is successful.

DFHDS0001 0C4 AKEX at offset FFFF in DFHDSDS3 when using IAM files

You receive an abend 0C4 or AKEX (abend0C4 abendAKEX) in CICS Dispatcher module DFHDSDS3. You are using vendor product IAM from Innovation Data Processing for some of your CICS Transaction Server for z/OS (CICS TS) files.

CA-7.SVCA-04 and CA-7.U7SVC-99 RC=00000004 when using CICS TS 5.1 with CA Common Services

Jobs triggered by the CA-7 SVC in CICS fail after upgrading to CICS Transaction Server for z/OS (CICS TS) V5.1. You receive error CA-7.SVCA-04 security extract failed and CA-7.U7SVC-99 error return from SASSSVCA with RC 00000004. You are using CA Common Services interfacing with CA-7. You might see different failures when using other CA products like ACF2 that interface with CA Common Services.

Slowdown in CICS TS every 15 minutes with resource manager waits and DB2 hanging

You are experiencing slowdowns in your CICS Transaction Server for z/OS (CICS TS) regions running on the same LPAR every 15 minutes for 90 seconds in duration. Over a few months time, the duration of the slowdown increased from 15 to 90 seconds. You have analyzed performance reports and noticed that most of the transaction time is spent on resource manager waits. The DB2 group checked DB2 behavior and noticed that the whole DB2 subsystem is getting locked at those periods.

Syndicate content