IDFHXS1203 IDs revoked in CICS logs, but not in Top Secret
search cancel

IDFHXS1203 IDs revoked in CICS logs, but not in Top Secret

book

Article ID: 269832

calendar_today

Updated On:

Products

Top Secret

Issue/Introduction

The CICS system was updated to V5.4 over the previous weekend. Following this upgrade, it was reported that two user IDs were causing application failures. Our CICS logs revealed that these IDs were linked to XS1203 error messages:

DFHXS1203 06/06/2023 07:11:09 A01CICSP The userid supplied in the verification for userid hank09 is revoked. This occurred in transaction DV00 when userid XXXXXX was signed on at netname ??? 

When we check the IDs in Top Secret, they do not show as revoked. 

The TSSUTIL report shows the messages that occur every time the IDs attempts to connect.   

Example:
   DATE     TIME   SYSI ACCESSOR JOBNAME  FFM VC PROGRAM  R-ACCESS A-ACCESS SRC/DRC SEC RESOURCE (TYPE & NAME)       JOBID   TERMINAL
 -------- -------- ---- -------- -------- --- -- -------- -------- -------- ------- --- ---------------------------- ------- --------
+
+
007/06/23 08:03:01 BBB hank09  CICSPROD A F 01                            *08*-96  D8 , BBB                     J009011 INTRDR
 07/06/23 08:03:01 BBB hank09  CICSPROD A F 02 DFHKETCB                   *08*-96 INI , BBB                      J000001
 07/06/23 08:03:01 BBB hank09  CICSPROD A F 01                            *08*-96  D8 , BBB                  J009011 INTRDR
 07/06/23 08:03:01 BBB izze09  CICSPROD A F 02 DFHKETCB                   *08*-96 INI , BBB                       J000001
 

*hank09 & izze09 are example acids*

 

 

 

Environment

Release : 16.0

Resolution

CICS 5.4 has a new check for CPU(BETA) which was defined but no permits were given.
Once permitted to the two acids it worked without a problem. 
Most sites do not own CPU resources and therefore do not need a permit.