HP Archive Backup System for OpenVMS Guide to Operations

Remote Devices
8.6 RDserver Inactivity Timer
8.5.3 Deny Specific RDF Clients Access to All Remote Devices
You can deny access from specific RDF client nodes to all remote devices. For example, if the
server node is MIAMI and you want to deny access to all remote devices from RDF client nodes
OMAHA and DENVER, do the following:
1. Edit TTI_RDEV:CONFIG_MIAMI.DAT
2. Before the first device designation line, insert the /DENY qualifier:
$ Edit TTI_RDEV:CONFIG_MIAMI.DAT
CLIENT/DENY=(OMAHA,DENVER)
DEVICE $1$MUA0: MUA0, TK50
DEVICE MSA0: TU80, 16700bpi
OMAHA and DENVER are the specific RDF client nodes denied access to all the remote
devices (MUA0, TU80) on the server node MIAMI.
8.5.4 Deny Specific RDF Clients Access to a Specific Remote Device
You can deny specific client nodes access to a specific remote device.
Example:
If the server node is MIAMI and you want to deny access to MUA0 from RDF client nodes
OMAHA and DENVER, do the following:
1. Edit TTI_RDEV:CONFIG_MIAMI.DAT
2. Find the device designation line (for example, DEVICE $1$MUA0:)
3. At the end of the device designation line, add the /DENY qualifier:
$ Edit TTI_RDEV:CONFIG_MIAMI.DAT
DEVICE $1$MUA0: MUA0, TK50/DENY=(OMAHA,DENVER)
DEVICE MSA0: TU80, 16700bpi
OMAHA and DENVER RDF client nodes are denied access to device MUA0 on the server node
MIAMI.
8.6 RDserver Inactivity Timer
One of the features of RDF is the RDserver Inactivity Timer. This feature gives system managers
more control over rdallocated devices.
The purpose of the RDserver Inactivity Timer is to rddeallocate any rdallocated device if NO I/O
activity to the rdallocated device has occurred within a predetermined length of time. When the
RDserver Inactivity Timer expires, the server process drops the link to the client node and deallocates
the physical device on the server node. On the client side, the client process deallocates
the RDEVn0 device.
The default value for the RDserver Inactivity Timer is 3 hours.
The RDserver Inactivity Timer default value can be manually set by defining a system wide logical
on the RDserver node prior to rdallocating on the rdclient node. The logical name is
RDEV_SERVER_INACTIVITY_TIMEOUT.
To manually set the timeout value:
$ DEFINE/SYSTEM RDEV_SERVER_INACTIVITY_TIMEOUT seconds
For example, to set the RDserver Inactivity Timer to 10 hours, you would execute the following
command on the RDserver node:
$ DEFINE/SYSTEM RDEV_SERVER_INACTIVITY_TIMEOUT 36000
8-10 Remote Devices