Reporting on the CSDATA Segment

We use the CSDATA segment heavily on User IDs, so that data about the user is stored on the User ID. We don't have to look up information in some other zOS dataset or some off host repository. But we need to be able to effectively report on that data.

Here is a list of examples where CSDATA reporting should be improved:

1. Provide a list of userids by selecting fields on the base and csdata segment, and reporting on the fields in both segments.

2. Create a report of the UserIDs that have access to a profile (resolve the groups to users) but report on the CSDATA segment for the UserID. Example: Lets say we wanted a list of all users that had access to CICS transaction ABCD, but I want to see each users EMPNUM and DEPTNUM that is stored in the CSDATA.

3. Similar to the example above, but be able to select based on the CSDATA. Who has access to CICS Transaction ABCD that are in DEPTNUM 9938.

4. Create a report of who has access to dataset profiles, but have the ability to display the CSDATA segment for the groups in the ACL, and display the CSDATA from the dataset profile.

5. Can the CSDATA segment be available to display or select on the RA.3 menu items. Like RA.3.1, RA.3.4, RA.3.G

6. We realize that for Access Monitor CSDATA is not used for authentication/authorization so the CSDATA would not be in AM itself, but make the ability to display the CSDATA segment fields (lookup) in the reports. If you are reporting on a dataset profile then be able to report on the CSDATA from the dataset profile, or the CSDATA for the User ID that accessed the dataset profile.

We realize that the engine may already support some of these functions, but the UI does not. But there is nothing out there today that we are aware of that tells you how to do this reporting. We need documentation / education materials, and updates to the UI.