Document revision date: 28 June 1999

## DECdfs for OpenVMS Management Guide

Previous | Contents | Index

## Chapter 4
DFS$CONTROL Commands

This chapter contains a list of the DFS$CONTROL commands and their definitions. Many of the DFS$CONTROL commands are the same as or similar to DCL commands. All DFS$CONTROL commands comply with DCL command syntax conventions. The basic command syntax is as follows:
COMMAND/QUALIFIER=(option,option) parameter

You can abbreviate DFS$CONTROL commands, qualifiers, and keywords. You can enter them in uppercase, lowercase, or any combination of uppercase and lowercase. If you specify only one option with a qualifier, you need not use the parentheses.

For more information on command syntax, see the OpenVMS User's Manual.

You can use DFS$CONTROL commands either interactively or in DECdfs command files. To invoke the DFS$CONTROL program interactively, enter the following command:

    $ RUN SYS$SYSTEM:DFS$CONTROL

DECdfs installation does not modify the system DCLTABLES to add a DFS$CONTROL command, but a foreign command can be used as follows:

    DFSCP == "$DFS$CONTROL"

With this symbol definition, all of the commands documented in this chapter can be entered interactively at the DCL prompt by preceding them with DFSCP, for example:

    $ DFSCP SHOW COMMUNICATION
    $ DFSCP MOUNT .DATA_DISK LCLNAME

Also, the control program can be run for repeated DFS commands by entering:

    $ DFSCP
    DFS>

To get help on DFS$CONTROL commands, enter the HELP command from the DFS> prompt as follows:

    DFS> HELP

You can use standard command-line editing features from the DFS> prompt.

The SYS$STARTUP:DFS$CONFIG.COM file is an example of how to use DFS$CONTROL commands in a command file.

Note The examples in this chapter illustrate the interactive use of commands, even for those that you typically enter from a command file.

You can use the Help Message utility to access explanations of messages returned in response to DFS$CONTROL commands. For information on using the Help Message utility, see the OpenVMS System Messages: Companion Guide for Help Message Users or enter HELP HELP/MESSAGE at the DCL prompt ($). Appendix A in this manual also provides descriptions of DECdfs messages.

## ADD ACCESS_POINT

> Registers an access point name in the DECdfs server database and the Digital Distributed Name Service (DECdns).

### Format

> #### ADD ACCESS_POINT ap-name directory-name

### Parameters

> #### ap-name

> The access point name stored by the DECdfs server and DECdns.

> #### directory-name

> The device and directory to which the access point refers. The device name is required and must be followed by a colon (:). The directory name is optional; the default directory is the device's master file directory (MFD). For example, if you specify DUA3:, the access point refers to DUA3:[000000]. You can substitute a system-rooted logical for a device name.

### Description

> This command makes an access point available to DECdfs clients by adding its name to DECdns and to the local server database. Insert the command into the DFS$SYSTARTUP command file to register each access point at startup time. Each command line takes one access point name.

> Entering this command interactively registers the access point with DECdns but keeps the server database entry alive only until the server stops. Once the server stops, the display for the SHOW ACCESS POINT command lists the access point but notes that it is unavailable. Editing the DFS$SYSTARTUP file each time you add an access point interactively will ensure that DECdns and your server database contain the same information.

> You must have the SYSNAM and OPER privileges to use this command.

### Qualifier

> #### /CLUSTER_ALIAS

> Gives the cluster alias, rather than the individual node's DECnet address information, to DECdns when registering the access point. To use this qualifier, you must use the identical command on each cluster member that has the incoming alias enabled.

> #### /LOCAL

> Registers the access point with the local DECdfs server database but not the DECdns server namespace. This is what happens by default when you add an access point on a system on which DECdns is not available. The /LOCAL qualifier makes this an option on systems where DECdns is available.

> The access point name for an access point added with the /LOCAL qualifier must include the namespace name unless you have defined the logical name DFS$DEFAULT_NAMESPACE in the DFS$CONFIG.COM file.

> Access points added with the /LOCAL qualifier must be mounted with the /NODE qualifier.

###

#### Examples

#1
    DFS> ADD ACCESS_POINT DEPARTMENT_FINANCE USER$34:
    DFS>

> This command adds the access point name DEPARTMENT_FINANCE. The access point refers to the directory USER$34:[000000].

#2
    DFS> ADD ACCESS_POINT BAKER_STREET.221B DISK$CASES:[MORIARTY]
    DFS>

> This command registers the access point BAKER_STREET.221B. The access point refers to the directory DISK$CASES:[MORIARTY].

#3
    DFS> ADD ACCESS_POINT BAKER_STREET.WATSON -
    _DFS> DISK$CASES:[WATSON]/CLUSTER_ALIAS
    DFS>

> This command registers the access point BAKER_STREET.WATSON, whose registered location will be the cluster name.

#4
    DFS> ADD ACCESS_POINT DEC:.LKG.S.DEPARTMENT_FINANCE -
    _DFS> USER$34:[000000] /LOCAL
    DFS>

> This command adds the access point to the local DECdfs server database. Note that the access point name includes the namespace name (DEC:). The access point refers to the directory USER$34:[000000].

## DISMOUNT

> Renders a DECdfs client device unavailable to users.

### Format

> #### DISMOUNT local-device-name

### Parameter

> #### local-device-name

> The name of the device to dismount. The value for local-device-name can be a logical name or the device name and unit number (DFSCn:).

### Description

> This command renders a DECdfs client device unavailable to users. If the device was mounted with the /GROUP or /SYSTEM qualifier, you must have the user privilege GRPNAM or SYSNAM, respectively, to dismount it.

> Before dismounting a client device, you can display a list of the client devices on your node (but not their logical names) by entering the DCL command SHOW DEVICE DFSC. Alternatively, you can use the DCL DISMOUNT command to dismount the device.

### Qualifier

> #### /ABORT

> Cancels any outstanding I/O requests and terminates mount verification. This qualifier allows you to dismount a device regardless of who actually mounted it.

> This qualifier is the same as the /ABORT qualifier to the DCL DISMOUNT command.

### Example

    DFS> DISMOUNT FINANCE
      %DFS-S-DISMNT_SUCCESS, Dismount was successfully performed.

> This command dismounts the local device whose logical name is FINANCE.

## EXIT

> Terminates the current DFS$CONTROL session and returns the DCL prompt.

### Format

> #### EXIT

### Parameters

> ####

> None.

### Description

> Use the Exit command when you want to end the current DFS$CONTROL session and return to the DCL prompt.

### Qualifiers

> ####

> None.

### Example

    DFS> EXIT
    $

> This command terminates the DFS$CONTROL session.

## HELP

> Displays help information on DFS$CONTROL commands.

### Format

> #### HELP [command-name]

### Parameters

> #### command-name

> The command on which you want information.

### Description

> The HELP command displays information on DFS$CONTROL. If you include the command-name parameter, the HELP command displays information about that command. If you omit the command-name parameter, the HELP command displays a list of the topics for which information is available.

### Qualifiers

> ####

> None.

### Example

    DFS> HELP SHOW VERSIONS

    This command displays version numbers for DECdfs software
    components.
    When tracking down problems in communication between a DECdfs
    server and client, enter this command and compare the versions
    on the two nodes. Different versions of the DECdfs software might
    cause a number of errors. You also use this command to get version
    information required for reporting problems to Compaq.
    Some version numbers are given as ranges, while others are single
    numbers. The range for the client protocol on the client node must
    overlap the server protocol on the server node. The communication
    protocol version must be the same on client and server.

> This command displays information on the SHOW VERSIONS command.

## MOUNT

> Makes available a specified access point as a local DECdfs client device.

### Format

> #### MOUNT ap-name [local-logical-name]

### Parameters

> #### ap-name

> Specifies an access point name on a DECdfs server. The name must already exist. That is, the server manager must have already registered it with the ADD ACCESS_POINT command.

> #### local-logical-name

> Designates a local logical name for the mounted device. The logical name is a string of 1 to 255 characters.

### Description

> This command allows your client system to use an access point located on a DECdfs server. When you mount an access point, DECdfs creates a pseudodevice of type DECdfs client (DFSC) on your system. The master file directory (MFD) for the mounted client device is the directory to which the access point refers. The device is mounted for sharing, as if you had used the DCL command MOUNT/SHARE.

> The device name is DFSCn:. If you do not use the /DEVICE qualifier, DECdfs assigns sequential unit numbers beginning with DFSC1001. DFS displays this name in the command response and instructs the communication entity to create a connection to the server. The connection is now ready to process user requests.

> You can supply a local logical name for the access point. This lets subsequent DFS$CONTROL and user commands see the device by that name. The local-logical-name parameter creates the logical name in the job logical name table. However, if you specify the /SYSTEM or /GROUP qualifier, the logical name is created in the system or group logical name table, respectively. Dismounting the device removes the logical name.

> Attempts to mount an access point that is already mounted produce different results depending on whether the later mount command specifies /SYSTEM or /GROUP. If these qualifiers are specified, such an attempt fails with the message:

>     %MOUNT-VOLALRMNT, another volume of same label already mounted

> If the mount attempt does not specify /SYSTEM or /GROUP, and no /DEVICE qualifier is specified, then a new DFSC device is created and the mount attempt proceeds. Thus, different users who mount the same access point will use different DFSC devices, but file access interlocking is not compromised because it always takes place at the server.

> Most command qualifiers are the same as those for the DCL MOUNT command. Note that the command qualifiers apply to the client device on your system, not to the actual physical device at the server.

### Qualifiers

> #### /[NO]DATA_CHECK [=option]

> Requests that the server perform a data check following all read requests, all write requests, or both read and write requests for the client device. The option value can be READ or WRITE or both.

> The default qualifier is /NODATA_CHECK. If you specify /DATA_CHECK without an option, the default option is WRITE.

> #### /DEVICE=DFSCn:

> Specifies the DFSC unit on which the access point is to be mounted. If this qualifier is not supplied, the OpenVMS operating system automatically supplies the unit number starting at 1001. It is recommended that units numbered 1 to 1000 be reserved for system-mounted access points.

> #### /GROUP

> Makes the mounted client device and its logical name available to other users whose UIC group code matches yours. To use this qualifier, you must have the GRPNAM privilege. You cannot use the /GROUP and /SYSTEM qualifiers together.

> #### /[NO]MESSAGE

> Displays or suppresses the message that confirms a successful mount operation. The default qualifier is /MESSAGE.

> #### /NODE=node_name

> In systems without DECdns, specifies the node that serves an access point. In such systems, a MOUNT command entered without the /NODE qualifier cannot determine where the specified access point is located because the DECdns namespace is not available.

> The MOUNT command does not prompt for the node name specification but if it is not supplied, the command will fail with the following error message:

>     %DFS-E-NODEMSNG, Server node not specified

> Access point names are normally unique within the namespace. However, if DECdns is not used, there is no enforcement of uniqueness and the same access point name may be used on multiple nodes. This is recommended only for cluster nodes where the access point name refers to the same physical disk on all nodes. The MOUNT command expects access point names to be unique and does not implicitly qualify them with the node name. Therefore, an attempt to mount the same access point name on two different nodes is seen as an attempt to mount the same access point twice and is treated as described above.

> #### /SYSTEM

> Makes the mounted client device and its logical name available to every user on the system. To use this qualifier, you must have the SYSNAM privilege. You cannot use the /SYSTEM and /GROUP qualifiers together.

> #### /VOLUME_NAME=string

> Specifies a volume name of up to 12 characters for the client device. The volume name provides a way of identifying the device when you view the response to the DCL command SHOW DEVICE.

> If you omit a volume name, the access point name is the default volume name if it has 12 or fewer characters. If the access point name has more than 12 characters, the default volume name consists of the first 5 characters of the access point name, 2 periods (..), and the last 5 characters of the access point name.

> #### /WINDOWS=n

> Specifies the number of mapping pointers to allocate for file windows. Extra window pointers are allocated automatically as required. For information on the range or default for the n value, see the OpenVMS System Management Utilities Reference Manual.

> The DECdfs client device makes files appear to be contiguous even though they may not be contiguous at the server. Increasing this value, therefore, will not be useful for accessing fragmented files, as it would be with local file access. It might be useful, however, if you need to access very large files.

### Example

    DFS> MOUNT DEPARTMENT_FINANCE FINANCE
    %MOUNT-I-MOUNTED, .DEPARTMENT_FINANCE mounted on _$DFSC1004:

> This command mounts the access point DEPARTMENT_FINANCE, giving it the logical name FINANCE. The response indicates that DEPARTMENT_FINANCE was mounted on the local node as DECdfs client device DFSC1004:. The access point name conforms to conventions for a single-directory DECdns namespace.

## REMOVE ACCESS_POINT

> Removes a specified access point name from the DECdfs server database and from the Digital Distributed Name Service (DECdns) namespace.

### Format

> #### REMOVE ACCESS_POINT ap-name

### Parameters

> #### ap-name

> Specifies the name of the access point to remove from the server database and from the DECdns namespace. If the server node does not have access to the DECdns namespace, or the server is not synchronized with the namespace, the access point must be fully qualified (namespace name and access point name).

### Description

> This command removes an access point name from both the server database and from the DECdns namespace. Entering this command does not affect operations on currently open files but does prevent new attempts to use the access point.

> You must have the SYSNAM and OPER privileges to use this command.

### Qualifiers

> #### /LOCAL

> Removes the access point from the local DECdfs server database. The access point name must include the namespace name unless you have defined the logical name DFS$DEFAULT_NAMESPACE in the DFS$CONFIG.COM file.

###

#### Examples

#1
    DFS> REMOVE ACCESS_POINT DEPARTMENT_FINANCE
    DFS>

> This command removes the access point DEPARTMENT_FINANCE from the DECdfs server and the DECdns namespace. In this example, the access point name is from a single-directory DECdns namespace.

#2
    DFS> REMOVE ACCESS_POINT BAKER_STREET.221B
    DFS>

> This command removes the DECdfs access point name 221B from the DECdns directory BAKER_STREET and the server database. In this example, the access point name is from a hierarchical DECdns directory.

#3
    DFS> REMOVE ACCESS_POINT DEC:.LKG.S.DEPARTMENT_FINANCE /LOCAL
    DFS>

> This command removes the access point from the local DECdfs server database. Note that the access point name includes the namespace name (DEC:).

## SET COMMUNICATION

> Sets parameters for the DECdfs Communication Entity.

### Format

> #### SET COMMUNICATION

### Parameters

> ####

> None.

### Description

> This command sets Communication Entity parameters that affect file buffering, limits on use, lifetimes of DECnet logical links, message reporting, and data integrity checks.

> These communication parameters can be dynamic or static. Dynamic parameters take effect when you enter the command; static parameters take effect the next time you start the communication entity. The description of each qualifier notes whether it takes effect on a dynamic or static basis.

> You must have the OPER privilege to use this command.

### Qualifiers

> #### /BUFFER_SIZE=n

> Sets the size (in bytes) of the DECdfs communication buffers for incoming and outgoing data. You need not set the same buffer size on client and server nodes; if the buffer sizes do not match, the DECnet software resolves the difference. The default buffer size is 2560 bytes; the range is from 560 to 9,216 bytes. If your system has enough memory, increasing the buffer size to 9,216 may improve DECdfs performance. This is a static parameter.

> #### /[NO]CHECKSUM

> Enables or disables DECdfs checksumming for all subsequent connections. You can enable and disable checksumming only from a client node; at a server-only node, this qualifier is ignored. If checksumming is enabled and DECdfs detects a checksum error at either the client node or the server node, it disconnects the DECnet link. Checksumming checks the data integrity above the DECnet level. The default qualifier is /NOCHECKSUM.

> This qualifier takes effect only when a new DECnet logical link is created. DECdfs then starts checksumming for that and all subsequently created links. If a SHOW COMMUNICATION/CURRENT_CONNECTIONS command shows that at least one connection has a link status of Inactive, the next user request on that connection will create a new link and checksumming will start. If all connections have a link status of Active, checksumming will not start until all user file operations on one connection stop, two successive scan times expire, and a new user request creates a new link. If you must start checksumming immediately, you can use NCP or NCL commands to disconnect a link, as follows:

> For DECnet Phase IV:

>     NCP> DISCONNECT LINK link-component

> Replace link-component with the number of the link or, if you wish to disconnect all links, with the parameter KNOWN LINKS.

> For DECnet Phase V:

>     NCL> DELETE SESSION CONTROL PORT session-control-port-name

> A session control port represents one end of a transport connection (logical link). To determine which port to delete, use the command SHOW SESSION CONTROL PORT * ALL. The output from this command is as follows:

>     Node 0 Session Control Port SCL$PORT$12010015
>     at 1994-05-07-15:30:30.525-04:00I0.613

>     Identifiers

>         Name                              = SCL$PORT$12010015

>     Status

>         Client                            = <Default value>
>         Local End User Address            = UIC = [0,0]<dfs$comacp>
>         Transport Port                    = NSP Port NSP$PORT_00002016
>         Direction                         = Outgoing
>         Remote End User Address           = name = DFS$COM_ACP
>         Node Name Sent                    = DEC:.ZKP.LAURAC
>         Version Sent                      = V3

>     Counters

>         Creation Time                     = 1994-05-07-15:29:18.476-04:00I0.568

>     Node 0 Session Control Port SCL$PORT$12010016
>     at 1994-05-07-15:30:30.525-04:00I0.613

>     Identifiers

>         Name                              = SCL$PORT$12010016

>     Status

>         Client                            = <Default value>
>         Local End User Address            = name = DFS$COM_ACP
>         Transport Port                    = NSP Port NSP$PORT_00002017
>         Direction                         = Incoming
>         Remote End User Address           = UIC = [0,0]<dfs$comacp>
>         Node Name Sent                    = DEC:.ZKP.LAURAC
>         Version Sent                      = V3

>     Counters

>         Creation Time                     = 1994-05-07-15:29:18.626-04:00I0.568

> The name of the session control port in this example is SCL$PORT$12010003. Note that the display identifies the session control port further by providing the name of the NSP port.

> #### /READS_MAXIMUM=n

> Sets the maximum number of concurrent read operations the Communication Entity can post to DECnet. Each read request requires one I/O request packet (called IRP in DECnet Phase IV and VCRP in DECnet Phase V) and one DECdfs communication buffer from nonpaged pool. The default value is 3; the range is from 1 to 20. This is a static parameter.

> #### /[NO]REPORTING [=option]

> Enables or disables reporting of communication messages. DECdfs sends the reports that you enable to OPCOM as network class messages. Enable only the reports that you need, because the reports produce heavy output and can slow response time. This is a dynamic parameter. See Appendix B for more information on the /REPORTING qualifier, including a figure.

> The option value can be one or more of the following:

> ALL | Enables or disables all reports.
> NONE | Disables all reports.
> [NO]ERRORS | Enables or disables reporting of DECdfs Communication Entity errors.
> [NO]NETWORK_EVENTS | Enables or disables reporting of DECnet events about the DECdfs Communication Entity.

> The default reporting option is ALL. Do not use a double negative, such as /NOREPORTING=NONE.

> #### /REQUESTS_OUTSTANDING_MAXIMUM=n

> Specifies how many outstanding file I/O requests from clients a DECdfs server can have. The Communication Entity stops reading I/O from the network when outstanding requests exceed the specified maximum number. The default value is 20; the range is from 1 to 65,535. This is a dynamic parameter.

> #### /SCAN_TIME=time

> Specifies the time interval between scans for inactive DECnet links. If the Communication Entity finds an inactive link on two successive scans, it disconnects the link. The link is reestablished the next time a user on the client requests a file operation on the server. The default scan time is 4 minutes (00:04:00.00); the maximum is just under 24 hours (23:59:59.99). This is a dynamic parameter. The qualifier is valid only on the client.

### Example

    DFS> SET COMMUNICATION/NOREPORTING=NETWORK_EVENTS
    DFS>

> This command disables reporting of DECnet events about the DECdfs Communication Entity.

## SET SERVER

> Sets parameters for the DECdfs server.

### Format

> #### SET SERVER

### Parameters

> ####

> None.

### Description

> This command sets server parameters that affect the creation of access points, the caching of file blocks, the caching of user access rights information, and the type of message reporting to use.

> These server parameters can be dynamic or static. Dynamic parameters take effect when you enter the command; static parameters take effect the next time you start the server unless described otherwise below. The description of each qualifier notes whether the parameter is dynamic or static.

> You must have the OPER privilege to use this command.

### Qualifiers

> #### /ACCESS_POINTS_MAXIMUM=n

> Sets the maximum number of access points in the server's database. The default value is 128; the range is from 64 to 65,535. This is a static parameter that takes effect when you enter the next START SERVER command.

> #### /DATA_CACHE=option

> Sets values for the server's data cache. This is a static parameter. It takes effect the next time you reboot and restart DFS.

> The option value can be one or both of the following:

> COUNT_OF_BUFFERS= n | Allocates n buffers from nonpaged pool for use in DECdfs file data caching. Each buffer takes a total of 8242 bytes. The default n value is 16; the range is from 16 to 2048.
> FILE_BUFFER_QUOTA= n | Specifies how many cache buffers a single file usually uses. The default quota is 4; the range is from 2 to 512.

> For normal use, insert the COUNT_OF_BUFFERS and FILE_BUFFER_QUOTA values into the DFS$CONFIG.COM command procedure.

> #### /INVALIDATE_PERSONA_CACHE

> Immediately flushes the persona cache and closes and reopens the NETPROXY.DAT file.

> #### /PERSONA_CACHE=UPDATE_INTERVAL=time

> Sets the lifetime of individual persona blocks for the server's persona cache. If a user whose persona block is outdated attempts a file access, the DECdfs server reads the NETPROXY.DAT, SYSUAF.DAT, and RIGHTSLIST.DAT files and updates the persona cache with that information. The default interval is 10 minutes (00:10:00.00); the maximum is just under 24 hours (23:59:59.99). This is a dynamic parameter.

> #### /[NO]REPORTING [=option]

> Enables or disables reporting of server messages. Output goes to the log files specified with the START SERVER command's /ERROR and /OUTPUT qualifiers. This is a dynamic parameter.

> The option value can be one or both of the following:

> [NO]ERRORS | Enables or disables reporting of DECdfs server general errors.
> [NO]OPCOM | Enables or disables reporting of any events as network class messages to OPCOM. The default is OPCOM.

###

#### Examples

#1
    DFS> SET SERVER/ACCESS_POINTS_MAXIMUM=30
    DFS>

> This command sets the access point limit for a DECdfs server to 30.

#2
    DFS> SET SERVER/DATA_CACHE=(COUNT_OF_BUFFERS=17,-
    _DFS> FILE_BUFFER_QUOTA=5)
    DFS>

> This command sets two values for the server's data cache: the number of buffers in the cache, and the per-file buffer quota. The command concatenates the two /DATA_CACHE qualifier options by surrounding them in parentheses and separating them with a comma.

## SHOW ACCESS_POINT

> Displays access points stored by the Digital Distributed Name Service (DECdns) and by individual DECdfs server databases.

### Format

> #### SHOW ACCESS_POINT ap-name

### Parameter

> #### ap-name

> Specifies the access point name to display.

> If the DECdns namespace is a single-directory namespace, an asterisk (*) wildcard character operates as it does in DCL file specifications: it expands to the names of all access points. A question mark (?) in DECdfs operates as a percent sign (%) operates in DCL. The question mark expands to the names of access points that match in all characters except the one represented by the wildcard.

> With a hierarchical DECdns namespace, an asterisk (*) wildcard character in the last segment of the name displays all access point names in the DECdns directory named by the previous segment. If the first segment is a logical name (defined in DNS$SYSTEM_TABLE), DECdns translates it and then adds the information that follows to the end of the equivalence string. If you want to prevent this translation, put a period (.) before the first segment.

### Description

> This command displays a list of access points and their node locations as registered with DECdns.

> The default qualifiers are /BRIEF and /REMOTE.

### Qualifiers

> #### /BRIEF

> Shortens and quickens the command response by including just the DECdns information (access point name and node name) and omitting the server information (device and directory) and namespace name. The default qualifier is /BRIEF.

> #### /FULL

> Displays the following information for each access point:
> - The full name, starting with the namespace name
> - The node on which the server is located
> - The device and directory to which the access point refers
> - Status information on the availability of the server or the access point (when necessary)

> The /FULL qualifier causes DECdfs to verify the DECdns information by querying each server for current information about the access points. The server information includes the device and directory to which the access point refers or gives current status information. For example, the command response might tell you that the server is currently unavailable or that the access point is not being served. The /FULL qualifier also adds the namespace name to each displayed access point name. Querying each remote server causes a slower command response with the /FULL qualifier.

> Querying a remote server for information on access points and displaying that information at your node creates a DECdfs connection between your node and that server node. You sometimes see those connections in the response to a SHOW COMMUNICATION command.

> #### /LOCAL

> Lists the access points in the local server database. /LOCAL is the default on systems without DECdns. You can use wildcard characters for any part of the access point name or for the entire name. You cannot use the /LOCAL qualifier with other qualifiers except /FULL.

> #### /NODE=node-name

> Lists the access points located on just the specified node. The /NODE qualifier is valid only on systems that are running DECdns.

> #### /REMOTE

> Lists the access points on remote nodes only. The /REMOTE qualifier is the default on systems running DECdns.

###

#### Examples

#1
    DFS> SHOW ACCESS_POINT/LOCAL
      DEC:.LKG.S.DEPARTMENT_FINANCE on SCOTER::USER$34:[000000]

> This command displays information about the access point DEPARTMENT_FINANCE, including the full namespace name. The command output shows that the access point refers to the master file directory of device USER$34.

#2
    DFS> SHOW ACCESS_POINT FIN.ADMIN.DIV.MYSTRY*
      FIN.ADMIN.DIV.MYSTRY on SCOTER::
      FIN.ADMIN.DIV.MYSTRY$VMS_SOURCE on SCOTER::
      FIN.ADMIN.DIV.MYSTRY_DUA0 on SCOTER::
      FIN.ADMIN.DIV.MYSTRY_USER on SCOTER::
      FIN.ADMIN.DIV.MYSTRY_VMS_SOURCE on SCOTER::

> This command illustrates the default brief display of access point names. It also illustrates how you can use a wildcard in the command with a hierarchical namespace. The display includes just the names of the access points and their server nodes.

#3
    DFS> SHOW ACCESS_POINT FIN.MYSTRY*/FULL
      CRANE_NS:.FIN.MYSTRY on SCOTER:: Access point is not
      presently being served
      CRANE_NS:.FIN.MYSTRY_DUA0 on JAY:: Server is presently
      unavailable
      CRANE_NS:.FIN.MYSTRY_USER on SCOTER::USER$1:[000000]
      CRANE_NS:.FIN.MYSTRY_VMS_SOURCE on WARBLR::DUA0:[VMS_SOURCE]

> This command illustrates a full display of access point names in the directory FIN.MYSTRY, which is part of the hierarchical namespace CRANE_NS. For each access point, the display includes the namespace name, the name, the server node name, and, when available, the device and directory.

> Full information is not available for all of the access points in this display. One access point "is not presently being served." This indicates that the DECdns namespace contains an entry for the access point but the DECdfs server does not. For another access point, the "Server is presently unavailable." This indicates that the server on that node has stopped, and it is therefore not processing requests for information.

## SHOW CLIENT

> Displays information about a DECdfs client device.

### Format

> #### SHOW CLIENT local-device-name

### Parameter

> #### local-device-name

> Specifies a local DECdfs client device. The value for local-device-name can be either a logical name that you assigned or the pseudodevice name that OpenVMS assigned (DFSCn:).

### Description

> For the device name that you specify, this command displays the name of its associated access point and access point's server node. You can also display the client counters.

> If the device that you specify is unavailable (not mounted), the command returns an error message.

### Qualifiers

> #### /ACCESS_POINT

> Displays the name of the access point associated with the specified device.

> #### /ALL

> Displays all client parameters and counters.

> #### /[NO]COUNTERS

> Displays or suppresses information about the following DECdfs client counters: file operations performed, bytes read from the device, bytes written to the device, files opened by the device, and mount verifications tried.

> The client counters reflect use from the time that you mounted the client device. They wrap when they exceed the maximum value of 64 bits (32 bits for the number of file operations). The display includes two sets of values: the current values, and the difference between the current values and those recorded by the last SNAPSHOT CLIENT command.

> #### /FREE_BLOCKS

> Displays the number of free blocks currently available on the client device.

> #### /NODE

> Displays the name of the DECdfs server node to which the client device gives access.

> #### /SNAPSHOT_FILE=file-spec

> Specifies the file to which you previously sent a client snapshot (using the SNAPSHOT CLIENT/SNAPSHOT_FILE=file-spec command). The output for this command compares the current counters with the counters recorded in that file. You can use this qualifier with the /COUNTERS qualifier.

### Examples

#1
    DFS> SHOW CLIENT DFSC1001
      Client Device DFSC1001 (Translates to _DFSC1001:)
          Status       = Available
          Access Point = DEC:.LKG.S.TANTS.RANGER_SATURN
          Node         = RAINBO
          Free blocks  = 61518

> This command displays all information on the client device represented by the name dfsc1001. The command output shows that the mounted device is available and is associated with the access point DEC:.LKG.S.TANTS.RANGER_SATURN on node RAINBO.

#2
    DFS> SHOW CLIENT DFS$DISK/COUNTERS
          Client Device DFS$DISK (Translates to _DFSC1:)
           DECdfsClient Counters  (Snapshot from Startup)
                                 |                 |  Change Since   |
     Counter                     | Current Value   |    Snapshot     |
    -----------------------------+-----------------+-----------------+
    | Operations Performed       | 8090            | 8090            |
    | Bytes Read                 | 4203520         | 4203520         |
    + Bytes Written              + 189440          + 189440          +
    | Files Opened               | 796             | 796             |
    | Mount Verifications Tried  | 0               | 0               |
    -----------------------------+-----------------+-----------------+

> This is an example of the client counters display. Note that the display includes the actual device name for the logical device specified in the command. This command response shows that DECdfs compared the current counters with the initial zero values, since the current values and the "Change Since Snapshot" values are the same.

## SHOW COMMUNICATION

> Displays information on the DECdfs Communication Entity.

### Format

> #### SHOW COMMUNICATION

### Parameters

> ####

> None.

### Description

> This command displays a variety of Communication Entity values and, optionally, counters.

> Note that a previous SET COMMUNICATION command might have set some (static) communication values that will not take effect until you next restart DECdfs. In this instance, this command displays both the current (most recently set) value and the static value now in use.

> Each qualifier is described in more detail in the SET COMMUNICATION command description.

### Qualifiers

> #### /ALL

> Displays all communication qualifier values and counters.

> #### /BUFFER_SIZE

> Displays the message buffer size of the DECdfs Communication Entity.

> #### /CHECKSUM

> On a client node, displays whether DECdfs is performing checksumming.

> #### /[NO]COUNTERS

> Displays or suppresses information about the following DECdfs communication counters: bytes sent and received, bytes lost because of checksum errors, number of checksum errors, and communication errors. Communication errors are those that the DECnet network passes up to the Communication Entity, such as "Network partner task aborted the logical link," "Path to the network partner task node was lost," and so forth.

> The display includes two sets of values: the current values, and the difference between the current values and those recorded by the last SNAPSHOT COMMUNICATION command. To use a particular snapshot file for the comparison, use this qualifier with the /SNAPSHOT_FILE qualifier.

> #### /CURRENT_CONNECTIONS

> Lists the current connections maintained by the Communication Entity. The command output displays the following information about each connection:
> - The name of the remote server node (for any outbound connections) or the remote client node (for any inbound connections). If the node name is a cluster alias, the cluster member name appears in parentheses.
> - The type of connection (inbound or outbound).
> - The state of the connection's DECnet logical link (active if DECdfs is currently using the link, inactive if DECdfs disconnected the link after the expiration of two successive scans).
> - The state of checksumming (enabled or disabled).
> - The number of active sessions (the number of open files).

> In examining the command response, note that some inbound connections might occur because remote DECdfs users are displaying access point information, and not necessarily because remote users are performing file operations.

> #### /READS_MAXIMUM

> Displays the current number of concurrent read operations the Communication Entity can post to DECnet.

> #### /REQUESTS_OUTSTANDING_MAXIMUM

> Displays the number of outstanding I/O requests a node can have.

> #### /REPORTING

> Displays the status of communication reporting to OPCOM.

> #### /SCAN_TIME

> Displays the interval between scans for inactive DECnet links.

> #### /SNAPSHOT_FILE=file-spec

> Specifies the file to which you previously sent a communication snapshot (using the SNAPSHOT COMMUNICATION/SNAPSHOT_FILE=file-spec command). The output for this command compares the current counters with the counters recorded in that file. Use this qualifier with the /COUNTERS qualifier.

> #### /STATUS

> Displays the status of the DECdfs Communication Entity, as follows:

> Running | Ready to process or is currently processing requests.
> Shutdown | Responding to a SHUTDOWN COMMUNICATION command; that is, allowing existing file operations to complete but denying new requests.
> Stopped | Stopped because of completion of shutdown status, response to a STOP COMMUNICATION command, or an unexpected error.

### Examples

#1
    DFS> SHOW COMMUNICATION/ALL/NOCOUNTERS

                         |  Current  |  Minimum  |  Maximum  |   Static  |
    Parameter            |   Value   |  Allowed  |  Allowed  |   Value   |
    ---------------------+-----------+-----------+-----------+-----------+
    Communication Status | Running   |           |           |           |
    Buffer Size          |       2560|        560|      65516|       2560|
    Req. Outstanding Max.|         20|          1|      65535|           |
    Reads Maximum        |          3|          1|         10|          3|
    Scan Time            |00:04:00.00|00:00:00.00|23:59:59.99|           |
    Report Errors        | Disabled  |           |           |           |
    Report Network Events| Disabled  |           |           |           |
    Checksum             | Disabled  |           |           |           |
    ---------------------+-----------+-----------+-----------+-----------+

> This command displays the Communication Entity parameters. Note that, when appropriate, the display includes the range of values for the parameter.

#2
    DFS>SHOW COMMUNICATION/COUNTERS/SNAPSHOT_FILE=COMM_SNAP.DAT
    Communication Counters  (Snapshot from 8-JAN-1999 08:31:18.22)
    Snapshot interval is    0 00:01:59.43
    Snapshot file = COMM_SNAP.DAT
                                       |               | Change Since |
      Counter                          | Current Value | Snapshot     |
    -----------------------------------+---------------+--------------+
    | Bytes Sent                       | 2248815       | 54689        |
    | Bytes Received                   | 7220040       | 299510       |
    | Bytes Lost from Checksum Errors  | 0             | 0            |
    + Number of Checksum Errors        + 0             + 0            +
    | Communication Errors             | 0             | 0            |
    -----------------------------------+---------------+--------------+

> This command displays the current communication counters and compares them with the counters in the file COMM_SNAP.DAT.

#3
    DFS> SHOW COMMUNICATION/CURRENT_CONNECTIONS
    DFS/COM Connections at 08-JAN-1999 08:33:36.69

> This command displays information about the Communication Entity's current connections. In this example, the node has both a DECdfs server and a DECdfs client. For the server on this node, the Communication Entity handled one or more requests from a client on node VIREO. The node name LINNET is a cluster alias. The following line ( (CHICKN) ) indicates that the cluster member CHICKN is the node handling the connection.

## SHOW SERVER

> Displays information on the DECdfs server.

### Format

> #### SHOW SERVER

### Parameters

> ####

> None.

### Description

> This command displays a variety of server parameters and, optionally, counters.

> Note that a previous SET SERVER command might have set some (static) server parameters that will not take effect until the next START SERVER command. For such parameters, this command displays two values: the current (most recently set) value and the static value now in use.

> For more information on each server parameter, see the SET SERVER command description.

> The default qualifiers are /ALL and /NOCOUNTERS.

### Qualifiers

> #### /ACCESS_POINTS_MAXIMUM

> Displays the maximum number of access points that can be stored in the DECdfs server database.

> #### /ACTIVE_FILES

> For each file currently open for a DECdfs end user, displays the file specification and the name of the user.

> #### /ALL

> Displays all server parameters and counters. For each parameter, the display includes the current value, the minimum and maximum allowed values, and the static value. The current and static values might be different for static parameters.

> To display all server parameters without the counters, use the /ALL and /NOCOUNTERS qualifiers.

> #### /[NO]COUNTERS

> Displays all DECdfs server counters. The display includes two sets of values: the current values, and the difference between the current values and those recorded by your last SNAPSHOT SERVER command. To use a particular snapshot file for the comparison, use the /SNAPSHOT_FILE=file-spec qualifier. The counters wrap when they reach their maximum value (64 bits). For a description of the persona cache counters, see Section 2.6.3. For a description of the data cache counters, see Section 2.7.3

> #### /DATA_CACHE [=option]

> Displays information about the data cache. The option value can be one or both of the following:

> FILE_BUFFER_QUOTA | Displays the per-file quota for data cache buffers.
> COUNT_OF_BUFFERS | Displays how many cache buffers a single file usually uses.

> #### /PERSONA_CACHE=UPDATE_INTERVAL

> Displays the lifetime of individual blocks in the persona cache.

> #### /REPORTING

> Displays the status of server message reporting.

> #### /SNAPSHOT_FILE=file-spec

> Specifies the file to which you previously sent a server snapshot (using the SNAPSHOT SERVER/SNAPSHOT_FILE=file-spec command). The output for this command compares the current counters with the counters recorded in that file. Use this qualifier with the /COUNTERS qualifier.

> #### /STATUS

> Displays the status of the DECdfs server, as follows:

> Running | Ready to process or currently processing requests.
> Stopped | Stopped in response to a STOP SERVER command.
> Aborted | Stopped because of an unexpected error.

> #### /USERS

> Displays information on client users that have recently accessed the server. The display contains information from the persona cache and includes the user name, node name, and proxy account name.

> The display also shows the number of open files and the status of the persona block. Expired persona blocks are marked QUOTE(Inval). (See the SET SERVER /PERSONA_CACHE=UPDATE_INTERVAL command.) These blocks appear in the display if any currently open files are using them or if recently closed files were using them. When a client user of an invalid persona block has new activity, the server builds a new persona block.

### Examples

#1
    DFS> SHOW SERVER/ALL/NOCOUNTERS
                          |Most Recent|  Minimum  |  Maximum  | Static |
    Parameter             |  Setting  |  Allowed  |  Allowed  | Value  |
    ----------------------+-----------+-----------+-----------+--------+
    Server Status         | Running   |           |           |        |
    Access Points Maximum |        128|         64|      65535|     128|
    Report Errors         | Disabled  |           |           |        |
    Report OPCOM Events   | Disabled  |           |           |        |
    D. Cache Buffer Count |         16|         16|        512|      16|
    D. Cache Quota        |          4|          1|         64|        |
    P. Cache Update Intrvl|00:10:00.00|00:00:00.00|23:59:59.99|        |
    ----------------------+-----------+-----------+-----------+--------+

> This command displays all the DECdfs server parameters. Note that the display includes the minimum and maximum allowed values for each.

#2
    DFS> SHOW SERVER/COUNTERS
              DECdfs Server Counters  (Snapshot from 10:38:16.01)
                    Snapshot interval is    0 00:00:44.76
                                     |                | Change Since |
      Counter                        | Current Value  |   Snapshot   |
    ---------------------------------+----------------+--------------+
    | P. Cache Blocks Active         | 4              | 0            |
    | Maximum P. Cache Blocks Active | 7              |              |
    + P. Cache Blocks Allocated      + 30             + 0            +
    | Max. P. Cache Blocks Allocated | 30             |              |
    | P. Cache Hits                  | 796483         | 91           |
    + P. Cache Misses                + 1366           + 0            +
    | D. Cache Full                  | 0              | 0            |
    | D. Cache Hits                  | 55656          | 8            |
    + D. Cache Misses                + 441831         + 47           +
    | D. Cache Quota Exceeded        | 113            | 0            |
    | RMS Directory Opens            | 0              | 0            |
    + Physical Reads                 + 191477         + 17           +
    | Physical Writes                | 3770013        | 469          |
    ---------------------------------+----------------+--------------+

> This command displays current server counters and compares them with counters recorded at the time of the last snapshot. The example shows a high ratio of persona cache hits to misses, indicating that the persona cache update interval is set high enough.

#3
    DFS> SHOW SERVER/USERS
    4 DECdfs Users at 08-JAN-1999 08:35:20.50
                                      |              | Files  | Persona |
                Remote User           |  Local User  | Open   |  Block  |
    ----------------------------------+--------------+--------+---------+
     JULIE::CORENZWIT                 | DFS_JAC      |     0  |  Inval  |
     LAURAP::CORENZWIT                | CORENZWIT    |     0  |  Valid  |
     QUANTZ::CORENZWIT                | DFS_JAC      |     1  |  Valid  |
     LAURAP::CORENZWIT                | CORENZWIT    |     1  |  Inval  |
    ----------------------------------+--------------+--------+---------+

> This command displays the users that have current or recent activity on the server. Note that the command display shows only two users with open files: QUANTZ::CORENZWIT and LAURAP::CORENZWIT. LAURAP::CORENZWIT has an open file that is using a persona block that expired after the file was opened. After the persona block expired, LAURAP::CORENZWIT opened and closed another file, causing the building of another persona block. If you see apparent duplicate entries in this display, you should expect to see only one valid entry for any one client user.

> JULIE::CORENZWIT also has an invalid entry in the display but has no files open. This can happen when a user keeps a file open for a longer period of time than the persona cache update interval and the display appears shortly after that user closes the file. User entries can appear in the display for about five to ten minutes after their last activity.

#4
    DFS> SHOW SERVER/ACTIVE_FILES
    3 DECdfs Server Open Files at 08-JAN-1999 08:34:35.94
          Remote User     |  File
    ----------------------+------------------------------------------
     FALCON::PFC          | DISK$VAXVMSRL4:[USER.CODWELL]LOGIN.COM;4
     FALCON::PFC          | DISK$VAXVMSRL4:[USER.CODWELL]ERRNO.MSG;1
     RAVEN::WICKLES       | DISK$VAXVMSRL4:[CDC_SOURCE]RDERR.LOG;1
    ----------------------+------------------------------------------

> This command shows that user PFC on node FALCON is currently accessing two files: LOGIN.COM and ERRNO.MSG. User WICKLES on node RAVEN is currently accessing the file RDERR.LOG.

## SHOW VERSIONS

> Displays version information for DECdfs components.

### Format

> #### SHOW VERSIONS

### Parameters

> ####

> None.

### Description

> This command displays version numbers for DECdfs software components. Use this command to get version information required for reporting problems to Compaq.

> When you view the response to this command, note that the range for the client protocol on the client node must overlap with the range for the server protocol on the server node. Otherwise, the client and server cannot interoperate. The communication protocol is not a range; it must be the same on both the client and server.

### Qualifiers

> ####

> None.

### Example

    DFS> SHOW VERSIONS
    Component              |  Version   |      Time  Started
    -----------------------+------------+---------------------+
    Communication Entity   |  V2.3-0    | 23-OCT-1998 13:56:26.61
    Communication Protocol |   1.0-0    |
    Server Entity          |  V2.3-0    | 23-OCT-1998 13:56:28.96
    Server Protocol        |  1.0 - 1.5 |
    Client Entity          |  V2.3-0    |
    Client Protocol        |  1.0 - 1.5 |
    DFS Control Program    |  V2.3-0    |
    -----------------------+------------+---------------------+

> This command displays the version numbers of DECdfs components.

## SHUTDOWN COMMUNICATION

> Stops DECdfs communication after existing file operations are complete.

### Format

> #### SHUTDOWN COMMUNICATION

### Parameters

> ####

> None.

### Description

> This command initiates a controlled shutdown of communication. It denies requests for new connections and waits for open files to be closed before stopping the Communication Entity. Entering the SHOW COMMUNICATION command displays the state of the Communication Entity, which is first "Shutdown" and then "Stopped." When the Communication Entity stops, it disconnects all DECnet links. To restart the entity, you should execute the SYS$STARTUP:DFS$STARTUP.COM file. In contrast, the STOP COMMUNICATION command aborts existing connections. Use SHUTDOWN COMMUNICATION whenever possible.

> On a server, executing the SHUTDOWN COMMUNICATION command also stops the server when the Communication Entity stops.

> You must have the CMKRNL and WORLD or GROUP privileges to use this command.

### Qualifiers

> ####

> None.

### Example

    DFS> SHUTDOWN COMMUNICATION
    DFS>

> This command causes the Communication Entity to refuse new requests and then to stop communication when all open files are closed.

## SNAPSHOT CLIENT

> Records the current DECdfs client counters for the specified client device.

### Format

> #### SNAPSHOT CLIENT local-device-name

### Parameter

> #### local-device-name

> Specifies the client device to record in the snapshot.

### Description

> This command records the current client counters for later use in client tuning or troubleshooting. After entering the SNAPSHOT command, you can enter the SHOW CLIENT/COUNTERS command. The display will compare the current counters with the counters preserved by the SNAPSHOT command.

> The information that you record with the SNAPSHOT command is usually stored in DFS$CONTROL memory. For a more permanent record, use the /SNAPSHOT_FILE qualifier.

### Qualifier

> #### /SNAPSHOT_FILE=file-spec

> Writes the current counter values to the specified file instead of to DFS$CONTROL memory. You cannot display this file using DCL commands such as TYPE; display the information in it by entering the SHOW CLIENT/SNAPSHOT_FILE=file-spec command.

### Example

    DFS> SNAPSHOT CLIENT DFSDISK/SNAPSHOT_FILE=DFSDISK:[LFS]SNAP_CLI.DAT
    DFS> SHOW CLIENT DFSDISK/COUNTERS/SNAPSHOT_FILE=DFSDISK:-
    _DFS> [LFS]SNAP_CLI.DAT
               Client Device DFSDISK (Translates to _DFSC1:)
           DECdfs Client Counters  (Snapshot from 11:18:56.78)
                    Snapshot interval is    0 00:00:27.12
                                  !    Current     |  Change Since  |
      Counter                     !     Value      |    Snapshot    |
    ------------------------------+----------------+----------------+
    | Operations Performed        | 72956          | 6              |
    | Bytes Read                  | 24786944       | 0              |
    + Bytes Written               + 1931776        + 1024           +
    | Files Opened                | 7366           | 1              |
    | Mount Verifications Tried   | 0              | 0              |
    ------------------------------+----------------+----------------+

> This example shows a sequence of commands. The first command records the client counters and writes them to the file SNAP_CLI.DAT. The SHOW CLIENT command then displays the current counters and compares them with the counters in the snapshot file.

## SNAPSHOT COMMUNICATION

> Records the current DECdfs communication counters.

### Format

> #### SNAPSHOT COMMUNICATION

### Parameters

> ####

> None.

### Description

> This command records the current communication counters for later use in tuning or troubleshooting. After entering this SNAPSHOT command, you can enter the SHOW COMMUNICATION/COUNTERS command. The display will compare the current counters with the counters preserved by the SNAPSHOT command.

> The information that you record with the SNAPSHOT command is usually stored in DFS$CONTROL memory. For a more permanent record, use the /SNAPSHOT_FILE qualifier.

### Qualifier

> #### /SNAPSHOT_FILE=file-spec

> Directs DFS$CONTROL to save the current counter values in the specified file instead of in DFS$CONTROL memory. You cannot display this file using DCL commands such as TYPE; display the information in it by entering the SHOW COMMUNICATION/SNAPSHOT_FILE=file-spec command.

### Example

    DFS> SNAPSHOT COMMUNICATION/SNAPSHOT_FILE=COMM_SNAP.DAT
    DFS>

> This command records the current communication counters, writing them to the file COMM_SNAP.DAT. The SHOW COMMUNICATION/SNAPSHOT=file-spec command then displays the current counters and compares them with the counters in the snapshot file.

## SNAPSHOT SERVER

> Records the current DECdfs server counters.

### Format

> #### SNAPSHOT SERVER

### Parameters

> ####

> None.

### Description

> This command records the current server counters for later use in tuning or troubleshooting. After entering the SNAPSHOT command, you can enter the SHOW SERVER/COUNTERS command. The resulting display compares the current counters with the counters preserved by the SNAPSHOT command.

> The information that you record with the SNAPSHOT command is usually stored in DFS$CONTROL memory. For a more permanent record, use the /SNAPSHOT_FILE qualifier.

### Qualifier

> #### /SNAPSHOT_FILE=file-spec

> Writes the current counter values to the specified file instead of DFS$CONTROL memory. You cannot display this file using DCL commands like TYPE; display the information in it by entering the SHOW SERVER/SNAPSHOT_FILE=file-spec command.

### Example

    DFS> SNAPSHOT SERVER/SNAPSHOT_FILE=SERVER_SNAPSHOT.DAT
    DFS>

> This command records the current server counters in the file SERVER_SNAPSHOT.DAT. You can then use the SHOW SERVER/SNAPSHOT=file-spec command to display the current counters and compare them with the counters in the snapshot file.

## START COMMUNICATION

> Starts the DECdfs Communication Entity.

### Format

> #### START COMMUNICATION [comm-file-spec]

### Parameter

> #### comm-file-spec

> Specifies a DECdfs communication ancillary control process (ACP) that differs from the default file specification, which is SYS$SYSTEM:DFS$COM_ACP.EXE.

### Description

> This command starts executing the Communication Entity ACP, making it available for use by clients, or servers or both, and setting its counters to zero.

> You usually enter this command from the DFS$STARTUP file. However, you can also enter it interactively to restart the Communication Entity after a STOP COMMUNICATION command or an unexpected abort.

> You must have CMKRNL and PSWAPM privileges to use this command.

### Qualifiers

> #### /ERROR=file-spec

> Specifies the output destination to use for DECdfs communication ACP errors. The default destination is the log file.

> #### /OUTPUT=file-spec

> Specifies the destination for communication ACP output. The default destination is SYS$MANAGER:DFS$ERROR.LOG

Note Only certain errors that can occur during communication startup go to the destinations that the /ERROR and /OUTPUT qualifiers specify. All other communication errors go to OPCOM.

### Example

    DFS> START COMMUNICATION
    DFS>

> This command starts the DECdfs Communication Entity.

## START SERVER

> Starts the DECdfs server.

### Format

> #### START SERVER [server-file-spec]

### Parameter

> #### server-file-spec

> Specifies a DECdfs server ancillary control process (ACP) that differs from the default file specification, which is SYS$SYSTEM:DFS$SERVER_ACP.EXE.

### Description

> This command starts executing the server ACP, making the server available for incoming client requests, and setting its counters to zero.

> You usually enter this command from the DFS$STARTUP file. However, you can also enter it interactively to restart the server after a STOP SERVER command or an unexpected abort.

> You must have CMKRNL, PSWAPM, OPER, and PHY_IO privileges to use this command.

### Qualifiers

> #### /ERROR=file-spec

> Specifies an output destination for the error messages from the DECdfs server ACP that differs from the default file specification, which is SYS$MANAGER:DFS$ERROR.LOG.

> #### /OUTPUT=file-spec

> Specifies an output destination for the OPCOM messages from the DECdfs server ACP that differs from the default file specification, which is SYS$MANAGER:DFS$ERROR.LOG.

### Example

    DFS> START SERVER/ERROR=SYS$MANAGER:DFS$MESSAGE.LOG
    DFS>

> This command starts the server and specifies that DECdfs writes error messages to the file SYS$MANAGER:DFS$MESSAGE.LOG.

## STOP COMMUNICATION

> Stops the DECdfs Communication Entity immediately, aborting existing connections.

### Format

> #### STOP COMMUNICATION

### Parameters

> ####

> None.

### Description

> This command immediately stops the Communication Entity ancillary control process (ACP) from executing. This disconnects DECnet links and aborts all incoming and outgoing communication. To restart the entity, you should execute the SYS$STARTUP:DFS$STARTUP.COM file.

> On a server, executing this command also stops the server, as if you had entered the STOP SERVER command.

> On a client, end users currently using DECdfs to access files get the SS$_ABORT error. The client then gives the Communication Entity several chances to restart. It tries to reestablish its relationship with the Communication Entity for a short time, while reporting a "Mount verification in progress" message to OPCOM. Unless you start the Communication Entity again during this period, the mount verification times out. End users who attempt a new file operation then get a "Device not ready, not mounted, or unavailable" message.

> In contrast, the SHUTDOWN COMMUNICATION command initiates a controlled shutting down of services and does not abort user operations. Use the SHUTDOWN COMMUNICATION command whenever possible.

> You must have the CMKRNL and WORLD or GROUP privileges to use this command.

### Qualifiers

> ####

> None.

### Example

    DFS> STOP COMMUNICATION
    DFS>

> This command immediately stops the DECdfs Communication Entity.

## STOP SERVER

> Stops the DECdfs server immediately.

### Format

> #### STOP SERVER

### Parameters

> ####

> None.

### Description

> This command stops the local DECdfs server process, making local access points unavailable to client users and closing open files on the server. The end user might not know immediately that the file is closed on the server, depending on the application being used. However, the user's next I/O request to the client device will return a "Device offline" error message.

> You must have the CMKRNL, PHY_IO, and OPER privileges to use this command.

### Qualifiers

> ####

> None.

### Example

    DFS> STOP SERVER
    DFS>

> This command stops the DECdfs server process and closes open files.

Previous | Next | Contents | Index

| privacy and legal statement |
6548_CPRO_004.HTML