search cancel

Mismatches Between A User's LAST MOD Statistics In The CA Top Secret Security File And Their REFDATEs In The Cleanup Tracking Database.

book

Article ID: 53611

calendar_today

Updated On:

Products

Cleanup Datacom DATACOM - AD CIS COMMON SERVICES FOR Z/OS 90S SERVICES DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS COMMON PRODUCT SERVICES COMPONENT Common Services CA ECOMETER SERVER COMPONENT FOC EASYTRIEVE REPORT GENERATOR FOR COMMON SERVICES INFOCAI MAINTENANCE IPC UNICENTER JCLCHECK COMMON COMPONENT Mainframe VM Product Manager CHORUS SOFTWARE MANAGER CA ON DEMAND PORTAL CA Service Desk Manager - Unified Self Service PAM CLIENT FOR LINUX ON MAINFRAME MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME GRAPHICAL MANAGEMENT INTERFACE WEB ADMINISTRATOR FOR TOP SECRET Xpertware Top Secret Top Secret - LDAP Top Secret - VSE

Issue/Introduction

Description:

Why do the User's LAST MOD statistics in the CA Top Security File (SECFILE) not always correspond with the REFDATEs in the CA Cleanup Tracking Database?

Solution:

CA Cleanup's REFDATE is updated for all system entry validations, whether successful or not, and may include the following signons that would not update the LAST MOD date.

For example:

  • ATS signons - unless the TSS OPTIONS(30) parm is set.

  • CICS ISC signons in the AOR

  • A RACROUTE VERIFY request, specifying STAT=NO

CA Cleanup's REFDATE is not updated for TSS administrative commands against the CA Top Secret user.

For example, if a CA Top Secret administrator reset the password of a returning long term absent user, the user's LAST MOD would be updated, but not CA Cleanup's REFDATE.

Environment

Release:
Component: ETCLNT