Managing EXTENDED ADMINISTRATION AUTHORITIES
Article ID: 258995
Updated On:
Products
Issue/Introduction
The list of a User shows the following:
TSS LIST(USER0001) DATA(ADMIN)
----------- ADMINISTRATION AUTHORITIES
OTRAN = XAUTH
ACCESS = EXECUTE
..
..
----------- EXTENDED ADMINISTRATION AUTHORITIES
OTRAN = X(G) OWNER(TEST0001 )
ACCESS = EXECUTE
This article explains how Extended Administration Authorities are added to a user and how to add to an Admin Acid the possibility to let acids in its scope permission to other CICS OTRAN.
Environment
Release : 16.0
Resolution
Taking the example of the extended admin authorities for USER0001:
----------- EXTENDED ADMINISTRATION AUTHORITIES
OTRAN = X(G) OWNER(TEST0001)
ACCESS = EXECUTE
What this means is that someone at some time must have issued the following command:
TSS PER(USER0001) OTRAN(X(G)) ACCESS(EXECUTE) ACTION(ADMIN)
The ACTION(ADMIN) allows USER0001 to give exec access to any OTRAN starting with X to any acid within his scope.
In order to allow other LSCAs to ADD permissions to users that are under his scope the permit should have ACTION(ADMIN).
For Example
TSS PER(lsca_user) OTRAN(transaction) access(access_level) ACTION(ADMIN)
After this command, the Lsca_user will be able to permit the transaction to other users under his scope.
Additional Information
Feedback
