Question & Answer
Question
This documents describes the file layout for for the QSYS2.AUTHORITY_COLLECTION Authority Collection file.
Answer
The following is the layout of the QSYS2.AUTHORITY_COLLECTION Authority Collection file:
Note 2 : Refer to document Authority Collection - Sample SQL Queries for sample queries for the Authority Collection Process
Note 3: Refer to document Authority Collection - Getting Started for information on how to get started with the Authority Collection Process
Schema Field Name
|
Type
|
Length
|
OS Field Name
|
AUTHORIZATION_NAME | VARCHAR |
10
|
USER_NAME |
CHECK_TIMESTAMP | TIMESTAMP |
26
|
CHKTIME |
SYSTEM_OBJECT_NAME | CHARACT |
10
|
SYS_ONAME |
SYSTEM_OBJECT_SCHEMA | CHARACT |
10
|
SYS_DNAME |
SYSTEM_OBJECT_TYPE | CHARACT |
8
|
SYS_OTYPE |
ASP_NAME | CHARACT |
10
|
ASP_NAME |
ASP_NUMB | DECIMAL |
5
|
ASP_NUMBER |
OBJECT_NAME | VARCHAR |
128
|
ONAME |
OBJECT_SCHEMA | VARCHAR |
128
|
OSCHEMA |
OBJECT_TYPE | VARCHAR |
9
|
OTYPE |
AUTHORIZATION_LIST | CHARACT |
10
|
AUTL |
AUTHORITY_CHECK_SUCCESSFUL | CHARACT |
1
|
CHKSUCCESS |
CHECK_ANY_AUTHORITY | CHARACT |
1
|
CHKANYAUTH |
CACHED_AUTHORITY | CHARACT |
1
|
CACHEAUTH |
REQUIRED_AUTHORITY | VARCH |
7
|
REQAUTH |
DETAILED_REQUIRED_AUTHORITY | VARCH |
90
|
DTLREQAUTH |
CURRENT_AUTHORITY | VARCH |
8
|
CURAUTH |
DETAILED_CURRENT_AUTHORITY | VARCH |
99
|
DTLCURAUTH |
AUTHORITY_SOURCE | VARCH |
50
|
AUTHSRC |
GROUP_NAME | CHARACT |
10
|
GROUP_NAME |
MULTIPLE_GROUPS_USED | CHARACT |
1
|
MLTGRPUSED |
ADOPT_AUTHORITY_USED | CHARACT |
1
|
ADOPTUSED |
MLTADOPTPG | CHARACT |
1
|
MLTADOPTPG |
ADOPTING_PROGRAM_NAME | CHARACT |
10
|
ADOPTPGM |
ADOPTING_PROGRAM_SCHEMA | CHARACT |
10
|
ADOPTLIB |
ADOPTING_PROCEDURE_NAME | VARCH |
256
|
ADOPTPRC |
ADOPTING_PROGRAM_TYPE | CHARACT |
8
|
ADOPTPGMT |
ADOPTING_PROGRAM_ASP_NAME | CHARACT |
10
|
ADOPTPGMA |
ADOPTING_PROGRAM_ASP_NUMB | DECIMAL |
5
|
ADOPTPGMAN |
ADOPTPGMSN | DECIMAL |
10
|
ADOPTPGMSN |
ADOPTING_PROGRAM_OWN | CHARACT |
10
|
ADOPTPGMOW |
CURRENT_ADOPTED_AUTHORITY | VARCH |
8
|
CURADPT |
DTLCURADPT | VARCH |
99
|
DTLCURADPT |
ADOPTED_AUTHORITY_SOURCE | VARCH |
50
|
ADOPTAUTSR |
MOST_RECENT_PROGRAM_INVOKED | CHARACT |
10
|
PGMINV |
MOST_RECENT_PROGRAM_SCHEMA | CHARACT |
10
|
PGMLIBINV |
MOST_RECENT_MODULE | VARCH |
30
|
MODINV |
MOST_RECENT_PROGRAM_PROCEDURE | VARCH |
256
|
PGMPRC |
MOST_RECENT_PROGRAM_TYPE | CHARACT |
8
|
PGMTYP |
MOST_RECENT_PROGRAM_TYPE | CHARACT |
10
|
PGMASP |
MOST_RECENT_PROGRAM_ASP_NUMBER | DECIMAL |
5
|
PGMASPN |
PGMSTMN | DECIMAL |
10
|
PGMSTMN |
USTPGM | CHARACT |
10
|
USTPGM |
USTLIB | CHARACT |
10
|
USTLIB |
MOST_RECENT_USER_STATE_MODULE | VARCH |
30
|
USTMOD |
USTPGMPRC | VARCH |
256
|
USTPGMPRC |
USTPGMTYP | CHARACT |
8
|
USTPGMTYP |
USTPGMASP | CHARACT |
10
|
USTPGMASP |
USTPGMASPN | DECIMAL |
5
|
USTPGMASPN |
USTPGMSN | DECIMAL |
10
|
USTPGMSN |
JOB_NAME | CHARACT |
10
|
JOB_NAME |
JOB_US | CHARACT |
10
|
JOB_USER |
JOB_NUMB | CHARACT |
6
|
JOB_USER |
THREAD_ID | BIGINT |
18
|
THREAD_ID |
CURRENT_USER | CHARACT |
10
|
CURUSR |
OBJECT_FILE_ID | BINARY |
16
|
OFILEID |
OBJECT_ASP_NAME | VARCH |
10
|
OASP |
OBJECT_ASP_NUMB | DECIMAL |
5
|
OASPN |
PATH_NAME | DBCLOB |
16777216
|
PATH_NAME |
PATH_REGION | CHARACT |
2
|
PATHREGION |
PATH_LANGUAGE | CHARACT |
3
|
PATHLANG |
ABSOLUTE_PATH_INDICATOR | CHARACT |
1
|
ABSPATHIND |
RELATIVE_DIRECTORY_FILE_ID | BINARY |
16
|
RELDIRID |
Note 1: Both the Schema Field Name and OS Field Name can be used when creating a report using the STRSQL product, when using WRKQRY, you need to use the OS Field Name
Note 2 : Refer to document Authority Collection - Sample SQL Queries for sample queries for the Authority Collection Process
Note 3: Refer to document Authority Collection - Getting Started for information on how to get started with the Authority Collection Process
[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.1.0"}]
Was this topic helpful?
Document Information
Modified date:
16 September 2020
UID
nas8N1021147