PDS Compare Job Using High CPU In Top Secret

Products

• Top Secret

Issue/Introduction

A batch job doing a compare of PDS is hanging and using excessive CPU (15-25% continually) until the job is FORCE ended. Below is a sample event from the TSSUTIL report. The event is repeated for over 200 PDSMEM1 resource names.

DATE         TIME    SYSI  ACCESSOR   JOBNAME   FACILITY MODE PROGRAM  R-ACCESS  A-ACCESS SRC/DRC SEC JOBID TERMINAL

12/08/21  15:38:14  ssss   acid                   job                fac         FAIL      ISPTASK      READ            ALL             OK+A   OPN    jjjjjjjj     tttttttt
                    RESOURCE  TYPE & NAME :   PDSMEM1  memname

Environment

Release : 16.0

Component : Top Secret for z/OS

Resolution

The excessive CPU usage was from Top Secret Audit I/O activity. The ACID running the job had a permit to bypass the PDSMEM1 resource checking that had ACTION(AUDIT) on it. To reduce this activity, revoke the permit with ACTION(AUDIT) and re-permit it without ACTION(AUDIT):

TSS REVOKE(acid) PDSMEM1(<BYPASS>) ACCESS(ALL) PRIVPGM(ISRSUPC) ACTION(AUDIT)
TSS PERMIT(acid) PDSMEM1(<BYPASS>) ACCESS(ALL) PRIVPGM(pgm)