Maintaining Access Rules with the Full-Screen Feature › Testing a VM Access Rule

Testing a VM Access Rule

This screen lets you test rules and assists you in verifying that the rules you have created do what you want them to do. To use this screen, enter the information you want to test.

 M9PA‑2510    Test a VM Data Access Rule (2.5.1)      CA ACF2 for VM 
 COMMAND ===> ________________________________________________________
                                                          TIME 17:12
 What is being accessed:
 Rulekey           ==> ________
 Minidisk Address  ==> _____   Filepool  ==> ________
 Filename/”VOLUME” ==> ________ Filetype ==> ________
 SFS Directory     ==> ______________________________________________
                       ______________________________________________
                       ______________________________________________
          
 Who is attempting the access:
 Logonid      ==> ________ or UID  ==> _______________________
 Program      ==> ________
 
 When and where is this access occurring:
 Date ==> ________ Time ==> _____ Source ==> ________
 
Test results:   WRITE access   : Allow
                READ access    : Prevent  By Rule Entry : ____
                EXECUTE access : Allow

 



PF1=Help       2=Print       3=Quit       4=Return      5=          6=MVS<‑>VM
PF7=Backward   8=Forward     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.

Minidisk address

Specifies the address of the minidisk that the rule applies to (for example, V0191) where:

R

Specifies real DASD

V

Specifies virtual address. This is the default.

Filepool

Specifies the Shared File System (SFS) filepool identifier this rule applies to.

Filename/”VOLUME”

Specifies the filename of the file this rule applies to. If the rule applies to a minidisk, VOLUME is the filename.

Filetype

Specifies the filetype of the file this rule applies to.

SFS Directory

Specifies the Shared File System (SFS) directory identifier this rule applies to.

Who Is Attempting the Access:

Logonid

Specifies the logonid of the user.

or

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.

Note: Pick only one of these fields. If you fill in both the logonid field and the UID field, CA ACF2 for VM logonid uses the logonid field.

Program

If applicable, enter the program name attempting the simulated 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 simulated access is 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 that the access is allowed.

Log

Specifies that the access is allowed but logged.

Prevent

Specifies that the access is denied.

By rule entry:

Specifies that the rule entry line number for the simulated access.