search cancel

How To Correctly Define $CHGMAN Class In The TSS RDT For The CHANGEMAN Product?

book

Article ID: 19851

calendar_today

Updated On:

Products

Cleanup Datacom DATACOM - AD CIS COMMON SERVICES FOR Z/OS 90S SERVICES DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS COMMON PRODUCT SERVICES COMPONENT Common Services CA ECOMETER SERVER COMPONENT FOC EASYTRIEVE REPORT GENERATOR FOR COMMON SERVICES INFOCAI MAINTENANCE IPC UNICENTER JCLCHECK COMMON COMPONENT Mainframe VM Product Manager CHORUS SOFTWARE MANAGER CA ON DEMAND PORTAL CA Service Desk Manager - Unified Self Service PAM CLIENT FOR LINUX ON MAINFRAME MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME GRAPHICAL MANAGEMENT INTERFACE WEB ADMINISTRATOR FOR TOP SECRET Xpertware Top Secret Top Secret - LDAP Top Secret - VSE

Issue/Introduction

Description:

The $CHGMAN class is defined in the TSS RDT as it follows:

 RESOURCE CLASS = $CHGMAN
  RESOURCE CODE = X'13F'
      ATTRIBUTE = MASKABLE,MAXOWN(26),MAXPERMIT(044),ACCESS,PRIVPGM
         ACCESS = READ(4000),NONE(0000),UPDATE(8000),WRITE(2000),ALL(FFFF)
         DEFACC = READ

 

Please, note the hexadecimal value of accesses READ and UPDATE, respectively 4000 and 8000.

In that case the issue is that having UPDATE access doesn't imply READ access causing CHANGEMAN to not functioning correctly.

Solution:

Change access level UPDATE=8000 to UPDATE=6000 in class $CHGMAN.

Then having UPDATE access also allows READ access and CHANGEMAN works correctly.

Environment

Release: TOPSEC00200-15-Top Secret-Security
Component: