Resources › OTRAN Resource Class—Secure Ownable Transactions

OTRAN Resource Class—Secure Ownable Transactions

Valid on z/OS and z/VSE.

Use OTRAN to secure ownable transactions for CICS, IMS, and CA‑IDMS that are protected by OTRAN. OTRAN is fully supported as a NONMASK resource (set by default). OTRAN in the IMS environment does not support the MASK RDT attribute.

When used with TSS ADDTO/REMOVE, this resource class has the following format:

TSS ADDTO(acid) OTRAN(transaction-id)

Prefix length

One to eight characters

Capacity of list

One to five transaction per TSS command

When used with TSS PERMIT/REVOKE, this resource class has the following format:

TSS PERMIT(acid) OTRAN(transaction-id)

Prefix length

One to eight characters

Capacity of list

One to five transactions per TSS command

This keyword is used with:

• The commands CREATE, ADDTO, REMOVE, PERMIT, REVOKE, ADMIN, DEADMIN, WHOOWNS, and WHOHAS
• OTRAN ACID types User, Profile, Department, Division, Zone, DCA, VCA, ZCA, LSCA, SCA, and MSCA when used with TSS ADD/REMOVE
• OTRAN ACID types User, Profile, DCA, VCA, ZCA, LSCA, SCA, and MSCA when used with TSS PERMIT/REVOKE
• OTRAN(OWN) authority to ADD or REMOVE OTRAN from ACIDs
• OTRAN(XAUTH) authority to permit or revoke access to transactions

The administrator can:

• Specify the access levels: INQUIRE, SET, EXECUTE, ALL, UPDATE, INSTALL, and COLLECT. If ACCESS is not specified, CA Top Secret defaults to EXECUTE access.
• Use any of the following methods to control access to the OTRAN resource: Expiration, Facility, Time/Day, and Actions.

Examples: OTRAN resource class

This example protects the CICS transaction, PAYR, by assigning ownership to the Payroll Department (PAYDEPT):

TSS ADDTO(PAYDEPT) OTRAN(PAYR)

This example removes ownership:

TSS REMOVE(PAYDEPT) OTRAN(PAYR)

This example permits an ACID, PAYPROG, to access the transaction PA01 through CICS only:

TSS PERMIT(PAYPROG) OTRAN(PA01)
                    FACILITY(CICS)

This example grants USER01 execute, collect, and set access to the TRANS1 ownable transaction:

TSS PERMIT(USER01) OTRAN(TRANS1) ACCESS(EXECUTE,COLLECT,SET)

This example revokes access:

TSS REVOKE(PAYPROG) OTRAN(PA01)

Transactions that require additional security is defined to require the signon password entered with each use. This is an attempt to prevent certain sensitive transactions from being entered by an unauthorized individual at an unlocked terminal. Once the resource is owned, password re‑verification is indicated on the PERMIT by the ACTION (REVERIFY) parameter as shown next:

TSS PERMIT(SUPR01) OTRAN(PROD)
                   ACTION(REVERIFY)