Using Reports › Understanding the ACFRPTXR Report › What Does this Report Look Like? › Cross-Reference Report › Sample Cross-Reference Report

Sample Cross-Reference Report

ACF2 UTILITY LIBRARY ‑ ACFRPTXR ‑ CROSS REFERENCE REPORT ‑ PAGE    1
DATE 06/25/05 (05.176) TIME 17.49 NAME(****PAY‑) CLASS(D) TYPE(PLN) RSRC ACF
********************************************************************************
ACF64001 USER REQUESTING REPORT ‑ TLCRPT ‑ RICHARD C. TALBOTT
OUTPUT LIMITED TO ACF2 RECORDS WITHIN YOUR AUTHORITY AND SCOPE.
AUTHORITY: ACCOUNT SECURITY USER
SCOPE: UID(‑)  LID(‑)  SCPLIST(‑)
********************************************************************************
‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
RESOURCE CLASS: D RESOURCE TYPE: PLN RESOURCE NAME: ALL RESOURCE NAMES FOR TYPE
RULE KEY: DPLN    PAYPGM
STORED: 05/21/05‑10:37 BY: TLCRPT
CONTROLS: %CHANGE DATA EXISTS  %RCHANGE DATA EXISTS
LOGONIDS THAT HAVE ACCESS WITHOUT RULES
TLCDCF(NC,SE) TLCDEM(NC)  TLCFAS(SE)  TLCSEC(SE)  TLCSTC(NC)  TLCRTY (SE)
TLCVAX(NC,SE) TLCZRM(SE)
UID(SH) SHIFT(NORMAL) SERVICE(BIND,EXECUTE) ALLOW
TLCABC(O,U)   TLCACT(O,U)  TLCBAD       TLCKLB(O,U,NC,SE)
TLCYBB(O,U,NC)             TLCZZT(U,SE)
UID(SH) SERVICE(BIND,EXECUTE) LOG
TLCBDF(O,U)   TLCACT(O,U)  TLCBSW       TLCBZM         TLCDRD(O,U)
TLCKLB(O,U,NC,SE)          TLCYBB(O,U,NC)
UID(*) SERVICE(EXECUTE) ALLOW
ALL LOGONIDS MATCH SPECIFIED UID STRING
RULE KEY: DPLNDSN PAYPLAN
STORED: 05/21/05‑10:37 BY: TLCRPT
CONTROLS: %CHANGE DATA EXISTS
LOGONIDS THAT HAVE ACCESS WITHOUT RULES
TLCDCF(NC,SE) TLCDEM(NC)  TLCFAS(SE)  TLCSEC(SE)  TLCSTC(NC)  TLCRTY (SE)
TLCVAX(NC,SE) TLCZRM(SE)
UID(SH) SERVICE(BIND,EXECUTE) ALLOW
TLCABC(O,U)   TLCACT(O,U)  TLCBAD       TLCKLB(O,U,NC,SE)
TLCYBB(O,U,NC)             TLCZZT(U,SE)
UID(SH) SERVICE(EXECUTE) LOG
TLCBDF(O,U)   TLCADM(O,U)  TLCBSW       TLCBZM         TLCDRD(O,U)
TLCKLS(O,U,NC,SE)          TLCYUM(O,U,NC)

In this example, Richard C. Talbott wants to see who can access the plans that begin with PAY. The rule keys that CA ACF2 Option for DB2 finds are PAYPGM and PAYPLAN. CA ACF2 Option for DB2 prints information about when they were stored and by whom. CA ACF2 indicates whether %CHANGE or %RCHANGE data exists. You can then run the Rule Record Summary to review this type of information. CA ACF2 also lists the logonids that can access each plan without a rule entry. These users have SECURITY or NON‑CNCL specified in their logonids. The rule entries for each rule set follow these logonids. Under each rule entry, the logonids that match the rule entry or are owners of the plan are shown. For example, the first rule entry shows that TLCABC can perform a BIND and EXECUTE on the PAYPGM plan because he is an owner (O) of the plan. TLCBAD is not an owner, his UID simply matches the UID parameter for this rule entry. Access is determined by whether he satisfies other parameters of the rule entry, such as SHIFT, SERVICE, and so on.