How To Implement ODM With Top Secret

Products

• Top Secret
• Top Secret - LDAP

Issue/Introduction

This document intends to supply you with the Top Secret commands to implement IBM ODM product.

Some resource classes might not be defined to the Top Secret RDT record. You have to define these resource classes before performing any TSS commands.

The Top Secret commands should be tailored to fit your site standard requirements.

Environment

Release:
Component: TSSMVS

Resolution

1) You have to define the following Resource Classes to the Top Secret RDT (Resource Descriptor Table): 

TSS ADD(RDT) RESCLASS(HBRCMD) POSIT(128) MAXLEN(64) - 

ACLST(ALL,UPDATE,READ,NONE) DEFACC(READ) 

TSS ADD(RDT) RESCLASS(HBRCONN) POSIT(128) MAXLEN(64) - 

ACLST(ALL,UPDATE,READ,NONE) DEFACC(READ) 

TSS ADD(RDT) RESCLASS(HBRADMIN) POSIT(128) MAXLEN(64) - 

ACLST(ALL,UPDATE,READ,NONE) DEFACC(READ) 

2) Tailor the attached file which contains the Top Secret commands to implement ODM. You will find all RACF commands followed by the TSS equivalents. 

3) Perform the tailored Top Secret commands.

Additional Information

There might be an issue with adding resources to Top Secret when using wildcard.

About the wildcard '*', here they are the possible combination: 

Below they are correct: 

TSS ADD(dept#) HBRCMD(**) 
TSS ADD(dept#) HBRCMD(*.xxxx.*) 

but notice that: 

tss add(dept#) hbrcmd(a*.bbbb.) 
tss add(dept#) hbrcmd(aaaa.bbbb.*) 
tss add(dept#) hbrcmd(aaa*.bbbb.*) 
tss add(dept#) hbrcmd(aaa*.bbbb.) 

are all invalid. This is because with Top Secret, you can add a resource with a masking character only if the resource name starts with a masking character.