User Detail and Key Reports (DREPORTs 004 and 074)

Standard Dictionary Reports—DREPORTS › Basic Entity Reports › User Reports (DREPORTs 004, 054, 074) › User Detail and Key Reports (DREPORTs 004 and 074)

User Detail and Key Reports (DREPORTs 004 and 074)

Contents

The user detail report provides detailed information about all user occurrences; the user key report provides similar information for selected user occurrences. The fields and format of these two reports are the same.

The following report shows sample output for DREPORT 074. The DREPORT and KEY parameters used to create this sample report are:

DREPORT=074
 KEY USER-NAME-047 'LHN'

Sample DREPORT 074:

REPORT NO. 74 DATA DICTIONARY REPORTER REL nn.n mm/dd/yy PAGE 1 DREPORT 074 USER REPORT ********************************************************************************************************************************* ---- D A T E ---- USER NAME UPDATED CREATED ********************************************************************************************************************************* LHN mm/dd/yy mm/dd/yy PREPARED BY LHN REVISED BY LHN DESCRIPTION SYSTEM ADMINISTRATOR FULL NAME LAURIE NELSON AUTHORITIES : PASSWORD NO AUTHORITY IDD DC CULPRIT NO AUTHORITY ELEMENT NO AUTHORITY DESTINATION NO AUTHORITY OLQ NO AUTHORITY FILE NO AUTHORITY LINE NO AUTHORITY ADS NO AUTHORITY MODULE NO AUTHORITY LTERM NO AUTHORITY LOAD MODULE NO AUTHORITY PROCESS NO AUTHORITY MAP NO AUTHORITY IDMS QFILE NO AUTHORITY MESSAGE NO AUTHORITY SCHEMA NO AUTHORITY TABLE NO AUTHORITY PANEL NO AUTHORITY SUBSCHEMA NO AUTHORITY PROGRAM NO AUTHORITY PTERM NO AUTHORITY DMCL NO AUTHORITY ENTRY POINT NO AUTHORITY QUEUE NO AUTHORITY CLASS & ATTRIBUTE RECORD NO AUTHORITY TASK NO AUTHORITY CLASS NO AUTHORITY REPORT NO AUTHORITY ATTRIBUTE NO AUTHORITY TRANSACTION NO AUTHORITY SYSTEM NO AUTHORITY USER NO AUTHORITY DEFAULT OPTIONS NO OLQ HEADER INTERRUPT WHOLE FULL NO FILLER ECHO HEADER ALL COMMENTS NO PATH STATUS NO CODE TABLE NO EXTERNAL PIC TERSE &&1. QFILE ALLOWED SORT ALLOWED OVERRIDES ALLOWED MRR ALLOWED IDD SIGNON ALLOWED SUPERVISOR JFD DIVISION DOCUMENT DATE-OF-HIRE mm-dd-yy PRODUCT ASF SYSTEM LHNSYSTEM VER 1 AUTHORIZED TO ALL AUTHORITY

Sample DREPORT 074 - continued:

REPORT NO. 74 DATA DICTIONARY REPORTER REL nn.n mm/dd/yy PAGE 2 DREPORT 074 USER REPORT ********************************************************************************************************************************* ---- D A T E ---- USER NAME UPDATED CREATED ********************************************************************************************************************************* SYSTEM LHNTEST VER 1 AUTHORIZED TO ALL AUTHORITY PROGRAM EMPSS01 VER 1 AUTHORIZED TO UPDATE ACCESS TO SYSTEM LHNSYSTEM VER 1 ACCESS TO SUBSCHEMAEMPSS01 OF SCHEMA EMPSCHM VER 1 RECORD EMPOSITION VER 1 RESPONSIBLE FOR CREATION AND UPDATE AND DELETION RECORD EMPOSITION VER 1 AUTHORIZED TO UPDATE ELEMENT LHN-ELEM VER 1 RESPONSIBLE FOR CREATION AND UPDATE AND DELETION AUTHORIZED TO ALL AUTHORITY ELEMENT DEPT-NAME VER 1 RESPONSIBLE FOR CREATION AND UPDATE AND DELETION AUTHORIZED TO UPDATE DESTINATION TESTDEST VER 1 RESPONSIBLE FOR CREATION AND UPDATE AND DELETION AUTHORIZED TO ALL AUTHORITY LINE VTAM234 VER 1 RESPONSIBLE FOR CREATION AND UPDATE AND DELETION COMMENT 00000100 USER WAS CREATED FOR TEST PURPOSES DEFINITION 00000100 DELETION DATE

Field Descriptions

The format of DREPORTs 004 and 074 depends on the order in which information was defined to the dictionary. A description of the fields in the sample user report follows:

USER NAME: Identifies the name of the user occurrence.
DATE UPDATED/CREATED: Identifies the date the user occurrence was last updated and the date the user occurrence was defined to the dictionary.
PREPARED BY/REVISED BY: Identifies the user who defined the user occurrence to the dictionary and the user who last updated it.
DESCRIPTION: Identifies text associated with the user occurrence.
FULL NAME: Identifies a name associated with the user occurrence (typically the user's full name).
PASSWORD ASSIGNED: Indicates that a password is assigned to the user.
AUTHORITIES: Identifies the user's authority to access secured entities, perform secured operations, or assign or revoke equal authority for another user.
DEFAULT OPTIONS: Identifies values that CA OLQ uses as default options when the user signs on.
CA OLQ options: Identifies additional CA OLQ authorizations.
OVERRIDES ALLOWED: Indicates whether the user can define and update CA Culprit for CA IDMS record layouts and files definitions.
IDD SIGNON ALLOWED: Indicates whether the user can access the DDDL compiler.
IDB ALLOWED: Indicates that the user can access IDB.
ASF ALLOWED: Indicates that the user can access ASF.
WITHIN USER: Identifies a relationship between this user occurrence and another user occurrence.
SAME AS: Identifies the user occurrence from which this user occurrence was copied (if copied).
User-defined nests: Identify user-defined nests that relate one user occurrence to another. In this sample report, the user-defined nest SUPERVISOR relates user LHN to user JFD.
Class/attribute associations: Identifies class/attribute associations that have been defined for the user occurrence. In this sample report, the attribute ASF within class PRODUCT and the attribute mm/dd/yy within class DATE-OF-HIRE are associated with user LHN.
Associated entity occurrences: Identifies associated entity occurrences for the user occurrence. Responsibility codes and text associated with each relationship are also listed.
ACCESS TO: Indicates that the user is authorized to access a CA Culprit for CA IDMS file, a qfile, a signon qfile, a subschema, or a system.
COMMENT: Identifies comments associated with the user occurrence through the COMMENTS clause of the DDDL USER statement.
User-defined comments: Identifies user-defined comments that were defined through the DEFINITION/comment-key clause of the DDDL USER statement are listed in this field. In this sample report, DELETION DATE is a comment key.