[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DCLREVIEW |
|
| Moderator: | HYLNDR::SYSTEM |
|
| Created: | Sun Apr 19 1987 |
| Last Modified: | Fri May 23 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 773 |
| Total number of notes: | 5391 |
766.0. "OpenVMS Disk Services for Windows NT" by MOVIES::PARSONS () Thu Mar 27 1997 06:49
Product OpenVMS Disk Services for Windows NT Version 1.0
contact name Judy Parsons
email address MOVIES::PARSONS
DTN 7-824-3318
role OpenVMS technical writer
Command Summary
Seven new commands:
NTDS CREATE CONTAINER Creates a container file that can be used
to provide a disk service to a Windows NT
computer
NTDS SHOW SERVER Shows whether the NTDS server software is
started on the local node and summary
information about the local node
NTDS SHOW SERVICE Shows information about disk services that
are currently available on the local node
NTDS START SERVER Starts the NTDS server software
NTDS START SERVICE Starts a disk service on the local node,
allowing the local node to provide that
service to a Windows NT computer
NTDS STOP SERVER Stops all the disk services on the local
node, then stops the server software on
the local node
NTDS STOP SERVICE Stops a disk service on the local node
Product Summary
OpenVMS Disk Services for Windows NT is a layered product that
currently plans to ship in July 1997. It lets you use OpenVMS
disks to store data for Windows NT users, by creating virtual
disks on Windows NT computers that look like real disks that are
attached to the Windows NT computers. You format them with native
Windows NT file systems, such as NTFS, and they behave just like
locally attached disks, although their data is actually stored on
an OpenVMS Cluster.
Version 1.0 of the product runs on OpenVMS Alpha Version 7.1 and
Windows NT Version 4.0.
Syntax Description
_________________________________________________________________
NTDS CREATE CONTAINER
Creates a container file that can be used to provide a disk
service to a Windows NT computer.
Requires SYSPRV privilege, and read and write access to the
directory in which you are creating the container file.
Format
NTDS CREATE CONTAINER filespec
Parameter
filespec
The file specification of the new container file that you want
to create.
Description
The NTDS CREATE CONTAINER command creates a brand new empty
container file that can be used to provide a disk service to a
Windows NT computer.
The container file is created with its protection mask set to
(S:RW, O:, G:, W:) and its ownership set to the system UIC.
Qualifiers
/SIZE=n
This qualifier specifies the size of the container file in
blocks. The default size is 2048 blocks, which is the minimum
size you can specify.
Example
NTDS> CREATE CONTAINER DISK$PAY:[NTDS$CONTAINERS]ADMIN.NTDS -
_NTDS> /SIZE=100000
This command creates a 100000 block container file called
ADMIN.NTDS in DISK$PAY:[NTDS$CONTAINERS].
_________________________________________________________________
NTDS SHOW SERVER
Shows whether the server software is started on the local node
and, if so, summary information about the local node.
Requires SYSPRV privilege.
Format
NTDS SHOW SERVER
Description
The NTDS SHOW SERVER command shows whether the OpenVMS Disk
Services for Windows NT server software is started on the local
node. If the server software is started, it also shows the
following information:
o The process identification (PID) of the server process,
NTDS_SERVER
o The cluster name that was specified on the NTDS START SERVER
command
o The number of active disk services and the number of standby
disk services currently available on the local node; for more
information on these services, use the NTDS SHOW SERVICE
command
o The number of Windows NT computers currently connected to
disk services on the local node; to find out which services the
computers are connected to, use the NTDS SHOW SERVICE command.
Examples
1. NTDS> SHOW SERVER
OpenVMS Disk Services for Windows NT
Server software not started
In this example, an NTDS START SERVER command has not yet been
issued on the local node.
2. NTDS> SHOW SERVER
OpenVMS Disk Services for Windows NT
Server software started
Cluster name: MONEY
PID of server process: 222000D2
Active disk services: 2
NT computers connected: 1
Standby disk services: 1
In this example, an NTDS START SERVER command that specified a
cluster name of MONEY has been issued on the local node. Two
active services and one standby service are currently
available on the local node, and a Windows NT computer is
currently connected to one of the active services.
_________________________________________________________________
NTDS SHOW SERVICE
Shows information about disk services that are currently
available on the local node.
Requires SYSPRV privilege.
Format
NTDS SHOW SERVICE [servicename]
Parameter
servicename
The name of the service that you want to show information
about. If you omit this parameter, the command shows
information about all the disk services currently available on
the local node.
This parameter can include wildcard characters.
Lower case characters are automatically converted to upper case
unless you enclose the string in quote marks. The search is
case sensitive, so for example, if a service called
Sales_Payroll is available on the local node, the following
command does not show information about it:
$ NTDS SHOW SERVICE Sales_Payroll
%NTDS-F-NOSUCHSERVICE, the specified service does not exist on
this node
Description
The NTDS SHOW SERVICE command shows information about disk
services that are currently available on the local node.
The services are listed in the order in which they were started
up on the local node. For each service, the command shows the
following information:
o The name of the service
o The status of the service on the local node (either active
or standby)
o If the status is active and a Windows NT computer is
currently connected to it, the name of the computer
o The full file specification of the container file associated
with the service
o If you use the /FULL qualifier, the total number of read and
write operations issued to the container file and the total
number of blocks that were read and written
Qualifiers
/FULL
Use this qualifier to show the following additional information
about each of the specified disk services:
o The total number of read operations issued to the container
file and the total number of blocks that were read
o The total number of write operations issued to the container
file and the total number of blocks that were written
Examples
1. NTDS> SHOW SERVICE
OpenVMS Disk Services for Windows NT
Disk services available on this node:
Service name: R&D
Status: Active
NT computer connected: (none)
Container file: DISK$PAY:[NTDS$CONTAINERS]R&D.NTDS
Service name: ADMIN
Status: Standby
NT computer connected: (n/a)
Container file: DISK$PAY:[NTDS$CONTAINERS]ADMIN.NTDS
Service name: SALES
Status: Active
NT computer connected: Sales-server
Container file: DISK$PAY:[NTDS$CONTAINERS]SALES.NTDS
This command shows information about all the disk services
currently available on the local node.
2. NTDS> SHOW SERVICE SALES /FULL
OpenVMS Disk Services for Windows NT
Disk services available on this node:
Service name: SALES
Status: Active
NT computer connected: Sales-server
Container file: DISK$PAY:[NTDS$CONTAINERS]SALES.NTDS
Read operations: 3678
Blocks read: 256789764
Write operations: 7899
Blocks written: 365829876
This command shows full information about the disk service
called Sales_Payroll.
_________________________________________________________________
NTDS START SERVER
Starts the server software on the local node.
Requires SYSNAM and SYSPRV privileges.
Format
NTDS START SERVER
Description
The NTDS START SERVER command starts the OpenVMS Disk Services
for Windows NT server software on the local node. It creates
the server process, NTDS_SERVER, on the local node.
Qualifiers
/CLUSTERNAME=clustername
This qualifier is needed in V1 but will be ignored in V2, when
NTDS will provide a clusterwide database that stores this
information.
This qualifier defines the name that Windows NT computers use
to identify your OpenVMS Cluster when they connect to the disk
services that it provides.
The cluster name can be up to 24 characters long and can
include any printable ASCII character except for the backslash
character (\). Lower case characters are automatically
converted to upper case unless you enclose the string in quote
marks.
Example
1. NTDS> START SERVER /CLUSTERNAME=MONEY
This command starts the OpenVMS Disk Services for Windows NT
server software and defines the cluster name to be MONEY.
_________________________________________________________________
NTDS START SERVICE
Starts a disk service on the local node.
Requires SYSNAM and SYSPRV privileges.
Format
NTDS START SERVICE servicename
Parameter
servicename
The name of the service that you want to start.
This parameter can be up to 24 characters long and can include
any printable ASCII character except for the the backslash
character (\). Lower case characters are automatically
converted to upper case unless you enclose the string in quote
marks.
Description
The NTDS START SERVICE command starts a disk service on the
local node. You must have previously used the NTDS CREATE
CONTAINER command to create the container file for the
service. You must also have issued an NTDS START SERVER
command on the local node to start up the OpenVMS Disk
Services for Windows NT server software.
The parameter of the NTDS START SERVICE command specifies the
name you want to give to the service.
In Version 1 you must use the /CONTAINER qualifier to specify
which container file you want to associate with that service
name. In Version 2, this qualifier will be ignored; NTDS will
provide a clusterwide database that stores the mapping between
the service names and container file specifications.
The NTDS START SERVICE command starts an active disk service
on the local node if this is the first node in the OpenVMS
Cluster to start a service with the specified name. When a
Windows NT computer subsequently tries to connect to the
service, the local node will accept the connection and provide
the service to that Windows NT computer.
If another node in the OpenVMS Cluster has already started a
service with the specified name, the command starts a standby
disk service on the local node. The local node will
automatically take over the job of providing the service if:
o The node that has the active disk service either fails or
is shut down, or
o You stop the service on that node, using either the NTDS
STOP SERVICE or NTDS STOP SERVER command.
Qualifiers
/CONTAINER=filespec
See above discussion. This specifies the container file that
you want to associate with the service.
The volume that contains the container file must be mounted
systemwide on the local node.
Example
1. NTDS> START SERVICE ADMIN -
_NTDS> /CONTAINER=DISK$PAY:[NTDS$CONTAINERS]ADMIN.NTDS
This command starts a disk service called ADMIN that is
associated with the container file ADMIN.NTDS in
DISK$PAY:[NTDS$CONTAINERS]. When a Windows NT computer
connects to the ADMIN service, this container file will look
like a disk that is locally attached to the Windows NT
computer.
_________________________________________________________________
NTDS STOP SERVER
Stops all disk services on the local node, then stops the server
software on the local node.
Requires SYSNAM and SYSPRV privileges.
Format
NTDS STOP SERVER
Description
The NTDS STOP SERVER command stops all the disk services on
the local node, then it stops the server software on the local
node. It deletes the server process, NTDS_SERVER, and frees up
the memory resources used by the server software.
If an active service on the local node has a standby service
on another node in the OpenVMS Cluster, the service
automatically fails over to the other node; the standby
service on the other node automatically becomes the active
service. If there are several standby services, the service
fails over to the one that was started first.
If a Windows NT computer is currently connected to the
service, the failover is transparent. The Windows NT users
carry on using the service, unaware that it is being provided
by a different node in the OpenVMS Cluster.
By default, the NTDS STOP SERVER command fails if the local
node has an active disk service to which a Windows NT computer
is currently connected. You can use the /OVERRIDE qualifier to
override this behavior.
Qualifiers
/OVERRIDE
You can use this qualifier to force the command to stop all
disk services and the server software, even though a Windows
NT computer is currently connected to an active disk service
on the local node.
The Windows NT computer looses its connection. If there is a
standby service on another node in the OpenVMS Cluster, the
computer will automatically reconnect to the service as soon
as the standby service becomes the active service. In this
case, the connection effectively fails over to another node in
the cluster. The failover is automatic and transparent to
Windows NT users; they carry on using the service, unaware
that it is being provided by a different node in the cluster.
If there are no standby services in the cluster, the Windows
NT computer keeps on trying to reconnect to the service, if
necessary, forever. In this case, use the NTDS START SERVICE
command on any node in your cluster to restart the service, so
that the computer can reconnect to it.
Until the Windows NT computer manages to reconnect to the
service, it stalls all read and write I/O requests to the
disk. If the computer fails or is shut down before it manages
to reconnect:
o You loose the data in its cache that has not yet been
written to disk.
o The next time it restarts, it automatically tries to
reconnect to the service, but this time it only retries for
about 20 seconds. If it fails to reconnect within the 20
seconds, the computer will not automatically try to reconnect
the next time it restarts.
Example
1. NTDS> STOP SERVER
This command stops all disk services on the local node, then
it stops the OpenVMS Disk Services for Windows NT server
software on the local node.
_________________________________________________________________
NTDS STOP SERVICE
Stops a disk service on the local node.
Requires SYSNAM and SYSPRV privileges.
Format
NTDS STOP SERVICE servicename
Parameter
servicename
The name of the service that you want to stop.
Lower case characters are automatically converted to upper
case unless you enclose the string in quote marks.
Description
The NTDS STOP SERVICE command stops a disk service that was
started with the NTDS START SERVICE command. It stops the
service on the local node only.
If the service is an active service that has a standby service
on another node in the OpenVMS Cluster, the service
automatically fails over to the other node; the standby
service on the other node automatically becomes the active
service. If there are several standby services, the service
fails over to the one that was started first.
If a Windows NT computer is currently connected to the
service, the failover is transparent. The Windows NT users
carry on using the service, unaware that it is being provided
by a different node in the OpenVMS Cluster.
By default, the NTDS STOP SERVICE command fails if the service
is active on the local node and a computer is currently
connected to it. You can use the /OVERRIDE qualifier to
override this behavior.
Qualifiers
/OVERRIDE
You can use this qualifier to force the command to stop the
service even though a Windows NT computer is currently
connected to it.
The Windows NT computer looses its connection. If there is a
standby service on another node in the OpenVMS Cluster, the
computer will automatically reconnect to the service as soon
as the standby service becomes the active service. In this
case, the connection effectively fails over to another node in
the cluster. The failover is automatic and transparent to
Windows NT users; they carry on using the service, unaware
that it is being provided by a different node in the cluster.
If there are no standby services in the cluster, the Windows
NT computer keeps on trying to reconnect to the service, if
necessary, forever. In this case, use the NTDS START SERVICE
command on any node in your cluster to restart the service, so
that the Windows NT computer can reconnect to it.
Until the Windows NT computer manages to reconnect to the
service, it stalls all read and write I/O requests to the
disk. If the computer fails or is shut down before it manages
to reconnect:
o You loose the data in its cache that has not yet been
written to disk.
o The next time it restarts, it automatically tries to
reconnect to the service, but this time it only retries for
about 20 seconds. If it fails to reconnect within the 20
seconds, the computer will not automatically try to reconnect
the next time it restarts.
Examples
1. NTDS> STOP SERVICE ADMIN
This command stops the disk service ADMIN on the local node,
provided that a Windows NT computer is not currently connected
to it.
2. NTDS> STOP SERVICE ADMIN /OVERRIDE
This command stops the disk service ADMIN on the local node,
even if a Windows NT computer is currently connected to it.
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 766.1 | | TLE::REAGAN | All of this chaos makes perfect sense | Thu Mar 27 1997 09:53 | 11 |
| All the subcommands look OK to me. However, as one could guess
NTDS isn't the greatest top-level DCL command. Traditionally, the
review board doesn't approve of acronymns (yeah, I know about
commands like CMS, DTM, LSE, etc., don't cloud the argument with
fact... :-) )
Is NTDS a real DCL command or is it a foreign command? Looking
at similar system-management tools, they have recently all be run
using foreign commands or MCR.
-John
|
| 766.2 | | AMCFAC::RABAHY | dtn 471-5160, outside 1-810-347-5160 | Thu Mar 27 1997 10:42 | 1 |
| Um, wait, isn't this what Pathworks does???
|
| 766.3 | OpenVMS Disk Services for Windows NT | MOVIES::PARSONS | | Thu Mar 27 1997 11:56 | 15 |
| Thanks for your reply. That was quick!
NTDS is a real DCL command, not a foreign command. You can enter
NTDS commands at the $ prompt, for example:
$ NTDS STOP SERVICE ADMIN
or at the NTDS> prompt, for example:
$ NTDS
NTDS> STOP SERVICE ADMIN
NTDS> EXIT
$
BTW, NTDS is the facility code for the product
|
| 766.4 | | TLE::REAGAN | All of this chaos makes perfect sense | Fri Mar 28 1997 09:22 | 6 |
| Well, the review board has looked the other way for foreign commands
since NTDS would only be a "suggested" way of activating the image.
For real DCL commands, the guidelines are more clear that NTDS is
not acceptable.
-John
|
| 766.5 | OpenVMS Disk Services for Windows NT | MOVIES::PARSONS | | Mon Mar 31 1997 11:21 | 18 |
| RE: NOTE 766.2
>> Um, wait, isn't this what Pathworks does???
Yes, kindof, but NTDS is about storage solutions and PATHWORKS is
about sharing files and printers. Here's what it says in the book:
PATHWORKS servers provide file services and print services. The
file services allow Windows NT and OpenVMS applications to share
files that are stored on disks in an OpenVMS Cluster.
NTDS provides disk services. It serves raw disk blocks, not
files, to the Windows NT computer that is connected to the
service. OpenVMS applications cannot access the data stored on
those disk blocks, just as they cannot access the data stored on a
real disk that is locally attached to the Windows NT computer.
Judy
|
| 766.6 | OpenVMS Disk Services for Windows NT | MOVIES::PARSONS | | Tue Apr 01 1997 07:27 | 8 |
| RE: NOTE 766.1 and .4
Agreed! The acronym NTDS isn't ideal, but we've not been able to think of anything
better, given the name of the product (OpenVMS Disk Services for Windows NT) and
given that the product doesn't have any latent support in the operating system so
it can't go in on existing DCL verbs like CREATE etc.
Judy
|