Maintaining Access Rules with the ACF Command › Using ACF TEST to Test an Access Rule › TEST Subcommand Keywords

TEST Subcommand Keywords

A period indicates you have activated the TEST subcommand. You can enter any of the following keywords with appropriate values to specify a test access environment. Separate each keyword with blank characters. You can specify one or more input lines.

DATE(date)

Specifies when access to a rule is tested. (This date can be in the format mm/dd/yy, dd/mm/yy, or yy/mm/dd.) The appropriate format is defined in the DATE field of the OPTS VMO record. The TEST subcommand uses the current date as the default.

DIR(sfsdirectory)

Specifies an actual SFS directory name and indicates the rule you are testing is for an SFS file. If you specify the DIR keyword, you must also specify a value for FILEPOOL. A null value indicates that this SFS file was defined without any directory levels.

DSN(dsn)

Specifies the actual filename for testing access. Refer to the FNFT keyword for information about SFS file filenames and filetypes.

FILEPOOL(filepool)|FPOOL(filepool)

Specifies an actual VM Shared File System (SFS) filepool and indicates the rule you are testing is for a SFS file or SFS directory. A null value, FILEPOOL(), turns off SFS testing and returns to CMS or OS/390 file testing.

FNFT(filename.filetype)

This keyword is a synonym of the DSN keyword. We include it to ease entering a SFS file's filename and filetype. If you specified FILEPOOL(filepool) to do SFS testing, then you can enter the filename and filetype of a SFS file. If you specify a null value, FNFT(), you test a SFS directory access. If you specify any value, you must separate the SFS filename and filetype with a dot. Additional levels are invalid. For example:

FNFT(PROFILE.EXEC)

Tests access to PROFILE EXEC

FNFT()

Tests access to a SFS directory

FNFT(PROFILE)

Invalid for SFS testing

FNFT(PROFILE.EXEC.A)

Invalid for SFS testing

LIBRARY(libmask)

Specifies a library you want to test access from. CA ACF2 for VM validation skips rule entries with LIBRARY specified. You can use this keyword to test OS/390 access rule entries.

LID(lid)

Specifies the logonid to obtain the UID. You must have access authority to the specified logonid record.

PGM(pgmmask)

This is an OS/390 keyword. If you specify this keyword in a rule entry,
CA ACF2 for VM rule validation skips it. You can use this keyword to test OS/390 access rule entries.

SOURCE(sourceid)

Specifies the logical name of the input source or source group.

TIME(hhmm)

Specifies the time, in hours (hh) and minutes(mm), CA ACF2 for VM uses to test the access.

UID(uid)

Specifies the actual UID. This keyword does not require access to the logonid record.

VOLUME(vol)

Specifies the pattern volume set or set of volumes where the data must reside to be valid. VM validation uses the VOL keyword for attach rules only.
CA ACF2 for VM validation skips rule entries with the VOL keyword specified in all other rules. You can use this keyword to test OS/390 access rule entries.