View considerations if not using XFACILIT resource class
To do the most effective setup of views for an installation which is not using the XFACILIT resource class to control history file fault entry access, an understanding of all of the different sets of users of Fault Analyzer is required. The main aspects of each user group that need to be determined are:
- Their data set security profiles for data sets with write access.
- The need to review or work on faults from jobs submitted by other user groups.
- The need for read access only, or no access at all, to fault entries between groups.
These requirements are already understood to some degree by the installation security administrators, as they are the ones primarily dealing with data set security requirements. The extra element is any requirement for fault visibility between the groups.
Without using the XFACILIT resource class to control history file fault entry access, the security of history files is the data set security in your system. For users' jobs to record faults in the fault history file, they need write (update) access to the history file that the job uses. All users in the same group thus have read and delete access to the faults in a history file set up for the group.
It is generally better to maintain separate fault history files for different user groups, providing the write (update) access only to the history file their jobs use. However, this approach makes it harder for a user to look at the faults across the environment if they are in many different history files. To solve this problem, create a "view" to let a use see a composite view of many history files in the one Fault Analyzer ISPF display.