The ACCESS DATADVH File

The ACCESS DATADVH file is a required file intended for local tailoring, but will default to the DIRMAINT 11F disk. This allows you to modify how commands and data files are routed.

The DIRMAINT EXEC obtains access to the interface files by using the nodeid entries found in the SYSTEM NETID and ACCESS DATADVH files. The production level of these two files generally resides on the 19E disk of the MAINT machine, although the test level of these files generally resides on the 29E disk of the 7VMDIR20 machine.

A common error that occurs is having multiple copies of the ACCESS DATADVH file in the search order, with the wrong one accessed ahead of the other. This can be detected by use of the DIRM CHECK command. For more information on the DIRM CHECK command, see z/VM: Directory Maintenance Facility Commands Reference.

When accessing the ACCESS DATADVH file, you should choose one of these formats. Enter:

ON= nodeid  USE= server:owner.subdirectory
ON= nodeid  USE= owner vaddr <rpass>

Or you can choose to use the IBM-supplied default format. Enter:

ON= *  USE= 7VMDIR20 11F ALL

Where:

ON=

Specifies nodeid, this keyword must be followed by at least one blank column.

nodeid

Identifies the node of the user entering the allocation request.

*

Specifies a default entry for use if no other entry matches the user's nodeid.

USE=

Specifies the interface or the qualified path name of a shared file directory; this keyword must be followed by at least one blank column.

server:owner.subdirectory

Identifies the userid that owns the interface or the qualified path name of a shared file directory.

or

owner vaddr

Specifies the virtual machine userid and the minidisk address containing the user interface files or blanks if you are using a shared file directory.

Note: The DVHPROFX EXEC file must be updated if a disk address other than 11F or an SFS directory is used.

rpass

Specifies the read-share password needed to obtain a link for the interface disk, or blanks if you are using a shared file directory.

Note:

1. If you are using the password of ALL, then ALL should be specified in the ACCESS DATADVH entry.
2. If an ESM is installed, the password may or may not be required, or may be required but ignored.
3. If you are using RACF as your ESM with DISKP=ALLOW on the SYSSEC macro, a password is not required in the ACCESS DATADVH entry and is ignored if specified. If you are using RACF with DISKP=DEFER, then the ACCESS DATADVH entry must supply the correct link password.

For more information, see your ESM documentation. If you are using IBM RACF, refer to z/VM: RACF Security Server Macros and Interfaces.