Maintaining Access Rules with the Full-Screen Feature › Testing an OS/390 or VSE Data Access Rule

Testing an OS/390 or VSE Data Access Rule

This screen is for testing rules and to assist you in verifying that the rules do what you want them to do. Enter the information you want to test on this screen.

M9PA‑2520  Test a MVS/VSE Data Access Rule (2.5.2)   CA ACF2 for VM 
COMMAND ===> ______________________________________________________
                                                         TIME 17:12
What is being accessed:
 Rulekey       ==> ________
 Volume        ==> ________
 Data set Name ==> ____________________________________________
 
Who is attempting the access:
 Logonid    ==> ________ or UID  ==> _______________________
 DDNAME     ==> ________ Program ==> ________
 Library    ==> ____________________________________________
 
When and where is this access occurring:
 Date ==> ________ Time ==> _____ Source ==> _______
 
Test results:
 READ access     : _________  By Rule Entry : ____
 WRITE access    : _________
 EXECUTE access  : _________
 ALLOCATE access : _________
 




PF1=Help       2=Print       3=Quit       4=Return      5=          6=MVS<‑>VM
PF7=           8=            9=Director   10=           11=         12=Retrieve

What Is Being Accessed

Rulekey

Specifies the key value of the rule set. The rulekey you specify can be up to eight characters long. You cannot mask this field.

Volume

Specifies the volume of the data set.

Data set name

Specifies the name of the data set.

Who Is Attempting the Access

Logonid

Specifies the logonid of the user.

UID

Specifies a pseudofield concatenation of selected information from the logonid record that can include information from user‑defined fields, such as company code, department, job function, and the logonid field.

DDNAME

Specifies the ddname to be accessed.

Program

If applicable, enter the program name attempting the simulated access.

Library

Specifies the library name for the attempted access.

When and Where Is this Access Occurring

Date

Specifies the date (in the format mm/dd/yy, dd/mm/yy, or yy/dd/mm, depending upon the DATE field in the OPTS VMO record) that the access was attempted.

Time

Specifies the time of the simulated access.

Source

Specifies an input source or source group name where this rule should apply. For example, you can specify the ID of a terminal. The access is allowed only if the user logs onto the specific terminal. If you do not specify a source, any input source is valid. Ask your security administrator for a list of valid source group names (optional).

Test Results

The access permission is displayed following the access type.

Allow

Specifies the access is allowed.

Log

Specifies the access is allowed but logged.

Prevent

Specifies the access is denied.

By rule entry

Specifies the rule entry line number that applied to the simulated access.