Chapter 3 TotalNET User Commands

This chapter lists TAS user commands, which reside in the TNHOME/usr/bin directory. The permissions of users, except for the superuser, determine the scope of modifications the users can make with these commands.

This chapter contains the following sections:

• "General Utilities" -- Commands for generating information about system components.

• "Realm-Specific Utilities" -- Commands specific to the LM-NT-OS/2, NetWare, and AppleTalk realms.

• "Shadow File Utilities" -- Commands for administering shadow files for name mapping.

• "Remote Utilities" -- Commands for administering remote system objects.

General Utilities

• "tncct"

• "tncmnames"

• "tngettext"

• "tninfo"

• "tnld"

• "tnmsgfmt"

• "tnpasswd"

• "tnstat"

• "tnwho"

tncct

This command allows you to manage client contexts for file services. It lists different types of client context files for given realms and services and returns the UNIX path names of given client contexts for specified users, services, and realms.

For each file service in a realm, each user may have files whose contents have meaning only for clients within the realm. These files must have appropriate names and contain information clients can accept. A user can access any number of client contexts for each service in each realm.

Location

TNHOME/usr/bin

Usage

tncct -r realm -s service [-c client-context -u user]

Options

Examples

1. Use the following command to list the type of client context files in the NetWare realm for the file service myhost:

   tncct -r NW -s myhost:file

2. Use the following command to list the UNIX path name of the client context file corduroy for the user schwip and the file service myhost in the AppleTalk realm:

   tncct -r AT -s myhost:file -c corduroy -u schwip

tncmnames

This command displays a list of TotalNET character set map names.

Location

TNHOME/usr/bin

Usage

tncmnames

Example

Use the following command to display the list of TotalNET character set map names below:

tncmnames

Character Set Map Names

builtin-mac-roman
 builtin-codepage-437
 builtin-unicode
 builtin-iso-latin-1
 iso-greek
 codepage-850
 shift-jis
 euc-jp

tngettext

This command retrieves a translated text string corresponding to msgid from a message file generated using the tnmsgfmt command. The message file name comes from the domain argument, if present, or from the TEXTDOMAIN environment variable. The domain text names a domain, like the message file name without the .mo suffix. If you specify no domain or if no corresponding string exists, tngettext prints msgid.

This command looks for its message object in the directory TNHOME/usr/lib/locale/msgs/lang, where TNHOME represents the TotalNET home directory /var/opt/totalnet. The lang variable represents the locale name. The value of lang comes from the value of either the LC_MESSAGES or LANG environment variables, checked in that order; if neither of these variables exists, tngettext prints msgid. If one or both exist, tngettext appends the value of the LC_CHARSET environment variable to the path name. For example, message files for the shift-jis character set reside in TNHOME/usr/lib/locale/msgs/lang/shift-jis.

The tngettext command reads C escape sequences. Use \t for a tab and \\ for a backslash. To set a message on a line of its own, either add \n at the end of msgid or use tngettext in conjunction with the UNIX printf command. For more information, refer to the UNIX printf(1) man page.

Location

TNHOME/usr/bin

Usage

tngettext [domain] "msgid"

Options

tninfo

This command displays information about one or more TotalNET client connections, such as the connecting users, the times at which they initiate connections, and the network addresses from which they connect. By default, the report gives the following information about each client's connection: the user's UNIX name, the file service realm, the date and time of the connection, the number of transaction requests serviced, and the server's network name.

Location

TNHOME/usr/bin

Usage

tninfo [-r realm] [-t type] [-s service] [-f]
 	[-u user|-c client]

Options

If you do not select a service, if no services match the conditions, or if the conditions contradict, such as in -t file -s sparky:term, an error message appears.

Examples

1. Use the following command to get basic information about all connected TAS clients:

   tninfo

   Sample Output:

   User	Realm	Startup	Request	Server Name
   spartacus	NB	Jan 19	10:390	lmspiffy:file
   otto	NB	Jan 19	11:462	lmspock:file

2. Use the following command to get full information about user sallie:

   tninfo -f -u sallie

   Sample Output:

   User	Realm	Startup	Request	Servername
   larry	NB	Jan 19	10:390	lmspiffy:file

   Client name
   X(00000101:00aa006834ba:4003)

   Network address
   X(00000101:00aa006834ba:4003)

3. Use the following command to get information about the user kathy:

   tninfo -u kathy

   Sample Output:

   User	Realm	Startup	Request	Server Name
   kathy	NB	Jan 19	10:390	lmnew:file

tnld

This command displays the contents of the TAS file service lock file {TNHOME}/tndb/=flock.file in a readable format. Lock entries appear in any of three forms: "brief", "long", and "wide". If entries appear, a single header line appears first, unless you use the -h option. In all of the forms, blank spaces separate the fields in the output lines. If you specify no options, tnld uses the "brief" form to display lock entries. The "brief" output format contains one line per lock entry. Each line contains the following fields:

The following table shows an example of brief output format:

Location

TNHOME/usr/bin

Usage

tnld [-h][-l] [-s] [-w] [-c client] [-f file]
 	[-i inode-number] [-u username]

Options

Examples

1. Use the following command to display the inode number, device number, lock state, and number of clients:

   tnld

   Sample Output:

   Inum	device	state	clients
   229114	32,1	DN	1

2. Use one of the following commands to display the inode number, device number, lock state, number of clients, and file names:

   tnld -f /home2/tmp/sh.date tnld -s

   Sample Output:

   Inum	device	state	clients
   229144	102,7	DN	1

   filename
   /home2/tmp/sh.date

3. Use the following command to display contents of the file service lock file in long output format with lock-entry lines and without a file name:

   tnld -l

   Sample Output:

   Inum	device	state	Pid	user
   229144	102,7	DN	9365	totalnet

   realm	service
   NB	spiffy:file

4. Use the following command to display the file service lock file in long output format with lock-entry lines, and for a file name readodd.notes in the directory /home2/tmp/:

   tnld -l -f /home2/tmp/readodd.notes

   Sample Output:

   Inum	device	state	filename
   298503	32.1	DN	/home2/tmp/readodd.notes

   Pid	user	realm	service
   9365	totalnet	NB	spiffy:file

5. Use the following command to display the file service lock file in long output format with client-info lines for the file service client marcie:

   tnld -l -c `N(marcie<00>/1/0)1901' marcie

   Sample Output:

   Inum	device	state	Pid	user
   229144	32,1	DN	9467	totalnet

   realm	service
   NB	plural:file

6. Use the following command to display the file service lock file in wide output format with client-info lines:

   tnld -w

   Sample Output:

   Inum	device	state	Pid	user	realm
   229144	32,1	DN	9467	totalnet	NB

   service	client
   plural:file	N(marcie<00>/1/0)1901

tnmsgfmt

This command creates message object files from portable object files--those with the .xmsg extension--without changing the portable object files. The .xmsg file contains messages displayed to users by system commands or application programs. You can edit these files and translate the messages to any language supported by the system.

All .xmsg files have the same format. Each file contains one or more lines, and each line contains either a comment or a statement. A comment begins with a hash mark (#) and ends with a new-line character. The tnmsgfmt command ignores all comments. Statements follow this format:

directive value

Each directive starts at the beginning of the line, and white space--either spaces or tab characters--separate it from value. The value variable consists of one or more quoted strings separated by white space. Use any of the following types of directives:

domain domainname
msgid message_identifier
msgstr message_string

The value of domainname should correspond to the message file name; if you edit messages for the tnnlc_lowutils domain, the directive should read domain tnnlc_lowutils, and the output goes into the message file tnnlc_lowutils.mo.

The msgid directive specifies the value of a message identifier associated with the directive that follows it. The message_identifier variable represents the target string to use at retrieval time. Follow each msgid directive statement with a msgstr directive statement. Do not change the msgid lines, since the code uses them as keys to locate the translated strings defined by the msgstr lines that immediately follow msgid lines. Message strings may contain the following escape sequences:

Location

TNHOME/usr/bin

Usage

tnmsgfmt [-v] filename.xmsg

Option

Notes

1. Install message object files in the directory TNHOME/usr/lib/locale/msgs/lang[/charset/], where TNHOME represents the TotalNET home directory /var/opt/totalnet. The lang variable represents the message language defined in LC_MESSAGES or in LANG, and charset represents the message character set defined in LC_CHARSET.

2. Messages can have any length; however, each line in the .xmsg file can have only MAX_INPUT (512) bytes. Installing message catalogs under the C locale serves no purpose, since the command ignores them for the sake of efficiency.

tnpasswd

This command creates, modifies, and deletes TAS users' passwords.

Location

TNHOME/usr/bin

Usage

tnpasswd [-u username] [-r realm...] [-s script...]
tnpasswd -d username [-r realm...]

Usage for TAS-DCE

You must have the TAS-DCE package installed on your system to use this command:

tnpasswd [-u username] [-r realm...] [-s script...]
 	[-g DCE-adm-name] [-h DCE-adm-passwd]

Options

Notes

1. Any TAS user can create a password, but only the superuser root can delete passwords. When the superuser deletes a user's password for a realm, the user does not have access to that realm. Only the superuser can reinstate a deleted password for a realm.

2. Users can create or modify their own passwords. If a user has different passwords for different realms, an error message appears when the user tries to change the password across all realms simultaneously.

3. When a user changes a password, the system prompts for the old password, the new password, and re-entry of the new password. The system does not prompt for the existing password when the superuser modifies or deletes the password of a TAS user.

4. You can configure a null password by entering a carriage return at the password prompt.

5. When you set the client-encryption attribute to on, only users who have entries in the TAS password file can access TAS realms. When you set client-encryption to off, only users who have entries in the UNIX password file can access TAS realms.

6. When you delete a TAS password, you do NOT delete the corresponding DCE and UNIX passwords.

7. In Distributed Computing Environment (DCE), TAS regards DCE as a TotalNET realm, along with NB, NW, AT, and UNIX. This provides a way of synchronizing the passwords of all realms, including DCE if it exists on the server. When changing a DCE user's password, you should use one password for all supported realms--NB, NW, AT, UNIX, and DCE. To change a DCE password entry, you must use tnpasswd to define -r DCE. Defining -r DCE only changes the DCE password. If you do not define the DCE realm, the TAS system changes the password for all realms except DCE. You cannot create or delete DCE user names and passwords with this command. Use the DCE administration interface to administer DCE passwords externally.

Examples

1. Use the following command to allow the superuser to create or modify the password of user harold for all supported realms:

   tnpasswd -u harold

   The following prompts appear:

   New password: Re-enter new password:

2. Use the following command to create or modify the password of user harold for the LM-NT-OS/2 realm:

   tnpasswd -u harold -r NB

   The following prompts appear:

   Changing password for harold New password: Re-enter new password:

3. Use the following command to delete the password of user harold and deny harold access from all three realms:

   tnpasswd -d harold

4. Use the following command to delete the password of user harold from the NetWare realm:

   tnpasswd -d harold -r NW

5. User harold can use the command below to change his password. He can use either the -u option or no options.

   tnpasswd [-u harold]

   The following prompts appear:

   Changing password for harold Old password: New password: Re-enter new password:

6. Use the following command to specify the logon script win95.bat for the user harold in the LM-NT-OS/2 realm:

   tnpasswd -u harold -r NB -s win95.bat

7. Use the following command to change the password of DCE user spiffy:

   tnpasswd -u spiffy -r DCE

   The following prompts appear:

   DCE privilege user account:
   DCE privilege user password:

   Log in as the DCE administrator. The following prompts appear:

   Changing password for spiffy Old password: New password: Re-enter new password:

tnstat

This command displays operational status information about all realms. The output includes status of the TAS system and services.

Location

TNHOME/usr/bin

Usage

tnstat [-r realm] [-t type] [-s service]

Options

Examples

1. Use the following command to show basic TAS status information:

   tnstat

   Sample Output:

   TotalNET system is enabled. Transports: tcpip tnipx tnatk NBservices are up.
   	Transports used: tcpip
   	sparky:file is accepting new connects.
   	0 client(s) connected.
   NWservices are up.
   	Transports used: tnipx
   	nwsparky:file is accepting new connects.
   	2 client(s) connected.
   ATservices are up.
   	Transports used: tnatk
   	atsparky:file is accepting new connects.
   	0 client(s) connected.

2. Use the following command to view the status of the NetWare realm:

   tnstat -r NW

   Sample Output:

   TotalNET system is enabled. Transports: tcpip tnipx tnatk NWservices are up.
   	Transports used: tnipx
   	nwmartin:file is accepting new connects.
   	2 client(s) connected.
   	nwmartin:term is accepting new connects.
   	0 client(s) connected.

3. Use the following command to view the status of file services:

   tnstat -t file

   Sample Output:

   TotalNET system is enabled. Transports: tcpip tnipx tnatk NBservices are up.
   	Transports used: tcpip
   	spatacux:file is accepting new connects.
   	0 client(s) connected.
   NWservices are up.
   	Transports used: tnipx
   	nwspatacux:file is accepting new connects.
   	1 client(s) connected.
   ATservices are up.
   	Transports used: tnatk
   	atspatacux:file is accepting new connects.
   	0 client(s) connected.

4. Use the following command to view the status of the file service ran in the LM-NT-OS/2 realm:

   tnstat -r NB -s ran:file

   Sample Output:

   TotalNET system is enabled. Transports: tcpip NBservices are up.
   	Transports used: tcpip
   	ran:file is accepting new connects.
   	0 client(s) connected.

tnwho

This command lists the users that have current connections to the LM-NT-OS/2, NetWare, or AppleTalk file or print services. The report resembles that of the UNIX who command and includes the following information:

• each user's UNIX name

• the file service realm

• the machine name of the client

• the date and time of connection started

The report normally shows only one connection per Ethernet address. A duplicate may appear if TAS does not recognize a connection as terminated. An "ungraceful" disconnection by the client, such as when the user turns off the PC or reboots without logging out, usually causes this.

Location

TNHOME/usr/bin

Usage

tnwho [-r realm][-t type][-s service]

Options

Examples

1. Use the following command to list users currently connected to TAS file services:

   tnwho

   Sample Output:

   simon	NB	SIMONPC	Jan 14 09:55
   peter	NB	PETERPC	Jan 15 10:23

2. Use the following command to list users currently connected to file services for the LM-NT-OS/2 realm:

   tnwho -r NB

3. Use the following command to list users currently connected to the file service spock in the LM-NT-OS/2 realm:

   tnwho -r NB -s spock:file

Realm-Specific Utilities

With the TAS 5.0 release, shadow file utilities took over functions of several realm-specific commands. If you cannot complete an activity as expected with a realm-specific command, check "Shadow File Utilities".

AppleTalk Realm:

• "acprint"

• "acslist"

• "aczonelist"

• "atattr"

• "atconvert"

• "ddpinfo"

• "desk"

• "m2u"

• "maccp"

• "macfsck"

• "macmd"

• "macmv"

• "macrd"

• "macrm"

• "pfinfo"

• "u2m"

LM-NT-OS/2 Realm:

• "nbmessage"

• "nbq"

NetWare Realm:

• "nwmessage"

• "nwq"

acprint

This command sends a print job to a remote AppleTalk realm printer, provided the system contains an active AppleTalk transport, the AppleTalk ream has started, and the remote printer supports the file's format. For example, you must print PostScript files to PostScript printers.

Location

TNHOME/usr/bin

Usage

To print a file to an AppleTalk realm printer with the given name:

acprint [-b] [-d] [-o] [-t] printername [file...]

To display the printer's PAP status string:

acprint -s printername

Options

Examples

1. Use the following command to send the file rain.doc to the remote AppleTalk realm printer atlwpr:LaserWriter@CINNEBAR and turn off the default printer output translation:

   acprint -t atlwpr:LaserWriter@CINNEBAR rain.doc

2. Use the following command to send the file seattle.doc to the printer atlwpr:LaserWriter@CINNEBAR and delete the file after it prints:

   acprint -d atlwpr:LaserWriter@CINNEBAR seattle.doc

3. Use the following command to send the file northwest.doc to the printer atlwpr:LaserWriter@CINNEBAR and write the output data from the printer to the standard output:

   acprint -o atlwpr:LaserWriter@CINNEBAR northwest.doc

acslist

This command lists active services in the AppleTalk realm.

Location

TNHOME/usr/bin

Usage

acslist [-m] [-s] [-q queries] [-w wait-secs] [pattern]

Options

Example

1. Use the following command to list active services in the AppleTalk realm:

   acslist

   Sample Output:

   A(61443.86.150)	newatkemppc:AFPServer@Cinnebar
   A(61443.86.149)	atkemppcd:AFPServer@Cinnebar
   A(61443.86.148)	atkemppc:AFPServer@Cinnebar
   A(4100.246.128)	SPIRO:AFPServer@*
   A(11268.159.128)	atNTPC:AFPServer@*
   A(18948.244.128)	atscorpio:AFPServer@*
   A(64771.133.128)	atjanepc:AFPServer@Cinnebar
   A(12548.26.128)	atmikhailpc:AFPServer@CINNEBAR
   A(772.64.130)	atspirogira:AFPServer@CINNEBAR

2. Use the command below to list active services in the AppleTalk zone Cinnebar. AppleTalk uses "=" as a wild card.

   acslist '=:AFPServer@CINNEBAR'

   Sample Output:

   A(61443.86.150)	newatkemppc:AFPServer@Cinnebar
   A(61443.86.149)	atkemppcd:AFPServer@Cinnebar
   A(61443.86.148)	atkemppc:AFPServer@Cinnebar
   A(4100.246.128)	SPIRO:AFPServer@*
   A(11268.159.128)	atNTPC:AFPServer@*
   A(18948.244.128)	atscorpio:AFPServer@*
   A(64771.133.128)	atjanepc:AFPServer@Cinnebar
   A(12548.26.128)	atmikhailpc:AFPServer@CINNEBAR
   A(772.64.130)	atspirogira:AFPServer@CINNEBAR

3. Use the following command with the wild card "=" to list all AppleTalk services available in your local AppleTalk zone:

   acslist =:=

   Sample Output:

   A(77767.2.997)	wallawalla:AFPServer@CINNEBAR
   A(23238.1.132)	simile:AFPServer@CINNEBAR
   A(99977.1.131)	datjunk:AFPServer@CINNEBAR
   A(99977.1.130)	datjunkr:LaserWriter@CINNEBAR
   A(99977.1.129)	junk:AFPServer@CINNEBAR
   A(99977.1.128)	bomb:AFPServer@CINNEBAR
   A(99977.45.128)	atsolx86:AFPServer@SYNTAX
   A(2323.55.8)	lc580:SNMP Agent@*
   A(2323.55.4)	lc580:Workstation@*
   A(9876.55.252)	powermac:Power Macintosh@*
   A(9876.55.4)	powermac:Workstation@*
   A(6666.567.2)	quadra:ARA - Client-Only@*
   A(6666.567.252)	quadra:Macintosh@*
   A(6666.567.4)	quadra:Workstation@*
   A(12345.1.251)	macbook:AFPServer@*
   A(12345.1.252)	macbook:PPCToolBox@*
   A(12345.1.253)	macbook:PowerBook 150@*
   A(12345.6.4)	macbook:Workstation@*
   A(12345.6.8)	NW410:SNMP Agent@*

aczonelist

This command displays a list of all zones in the AppleTalk network.

Location

TNHOME/usr/bin

Usage

aczonelist [-l]

Option

Examples

1. Use the following command to display a list of all zones in the AppleTalk network:

   aczonelist

   Sample Output:

   CINNEBAR LTA 00000000 LTB 00000000 P2Ether1 A5178101

2. Use the following command to display the local zone:

   aczonelist -l

   Sample Output:

   Cinnebar

atattr

This command sets or modifies Macintosh file attributes.

Location

TNHOME/usr/bin

Usage

atattr [-C] [-V] [-v] [-u] [{+|-}bcdimrsw] filename...

Options

Example

Use the following command to add the Invisible and Write Inhibit attributes to the files private and notes in the current directory, display the program version number, and execute in written form:

atattr -Vv +iw private notes

atconvert

This command converts the finder information .finderinfo and resource fork .resource formats of pre-TAS 5.0 versions of the AppleTalk realm file format, CAP 6.0, or Helios EtherShare into the TAS 5.2 shadow file structure. The default, if you select no option, converts Macintosh files in pre-TAS 5.0 format to TAS 5.2 format. The atconvert command converts Macintosh files recursively, descending through directory arguments.

CAP 6.0 stores the finder information and resource fork in the .finderinfo and .resource directories, respectively. The atconvert command converts the information from the .finderinfo and .resource directories into the new structure and stores it in new shadow files. The command then deletes the .finderinfo and .resource directories.

Helios EtherShare stores the finder information and resource fork in a single file directory under .rsrc. The atconvert command converts this information from .rsrc into the new structure and stores it in new shadow files.

The atconvert command uses character set mapping when converting files between Macintosh and TAS. With TAS installed, the server reads the host character set value from the TAS configuration file. The client character set defaults to builtin-mac-roman. The host character set defaults to builtin-iso-latin-1.

Location

TNHOME/usr/bin

Usage

atconvert [-b] [-c] [-C charset] [-d] [-H] [-k]
 	directory...

Options

Notes

1. This command does not preserve the comment field in the finder information when converting from Helios format to TAS format.

2. This command uses the UNIX creation/modification date of the files in all conversions except when converting CAP format to TAS format with CAP binary compiled with USE_MAC_DATES.

3. The user who runs this command must have permission to read, write, and create all of the files under the directory.

4. This command preserves the original permission and ownership of the file. The shadow files and directories it creates have the same ownership and permission as the parent directory. Back up the directory if you want to preserve the original content.

5. Do not run the command from the root directory "/".

Examples

1. Use the following command to convert the directory /home/totalnet and every subdirectory and file under it from pre-TAS 5.0 Macintosh file structure to TAS 5.2 structure and delete the original pre-TAS 5.0 finder information and resource fork:

   atconvert /home/totalnet

2. Use the following command to convert CAP directory /home/macdir to a TAS directory, with USE_MAC_DATES defined when building CAP:

   atconvert -c -d /home/macdir

3. Use the following command to convert Helios directory /home/heliodir to a TAS directory:

   atconvert -H /home/heliodir

ddpinfo

This command gives information about AppleTalk input and output packets and packet errors.

Location

TNHOME/usr/bin

Usage

ddpinfo [-i[x]] [-u[x]] [-r]

Options

Examples

1. Use one of the following commands to acquire information about an AppleTalk interface:

   ddpinfo ddpinfo -i

   Sample Output:

   Port 0:
   	name: 11c2:66
   	hw addr: 0800 6902 7a4e
   	appletalk addr: 1079/154 (0x437/0x9a)
   	ipkts/opkts 26579/2220, ierrs/oerrs 5/0

2. Use the following command to receive a detailed breakdown of errors:

   ddpinfo -x

   Sample Output:

   Port 0:
   	name: 11c2:66
   	hw addr: 0800 6902 7a4e
   	appletalk addr: 1079/154 (0x437/0x9a)
   	ipkts/opkts 26579/2220, ierrs/oerrs 5/0
   Error breakdown:
   	fragment: 0
   	short packet: 0
   	too many hops: 0
   	indirect broadcast: 0
   	unreachable network: 1
   	inactive protocol type: 4
   	user queue closed: 0
   	no memory on input: 0
   	badly formatted aarp packet: 0
   	badly formatted ddp packet: 0
   	dropped due to full queue: 0
   	dropped due to full interface: 0
   	output data link: 0
   	interface unlinked: 0
   	no memory on output: 0
   	no output ddp stream: 0
   	no output aarp stream: 0

3. Use the following command to acquire user information:

   ddpinfo -u

   Sample Output:

   Upper stream minor device 0:
   	Protocol type 6
   	ipkts/opkts 72/3, ierrs/oerrs 0/0
   Upper stream minor device 1:
   	Protocol type 3
   	ipkts/opkts 0/0, ierrs/oerrs 0/0
   Upper stream minor device 2:
   	Protocol type 1
   	ipkts/opkts 23817/0, ierrs/oerrs 0/0
   Upper stream minor device 3:
   	Protocol type 2
   	ipkts/opkts 2769/2203, ierrs/oerrs 0/0
   Upper stream minor device 4:
   	Protocol type 4
   	ipkts/opkts 0/0, ierrs/oerrs 0/0
   Upper stream minor device 5:
   	Protocol type 0
   	ipkts/opkts 0/0, ierrs/oerrs 0/0

4. Use the following command to acquire the network number and port number, or the route and router address:

   ddpinfo -r

Sample Output:

desk

This command lists the information in a volume's desktop database.

Location

TNHOME/usr/bin

Usage

desk [-C][-u][-V][-{a|h|i}] volume

Options

Example

Use the following command to print the .Adesktop and .Idesktop files for the volume with root /usr/macvol:

desk -ai /usr/macvol

m2u

This command converts all Macintosh carriage returns to UNIX linefeeds.

Location

TNHOME/usr/bin

Usage

m2u [-C][-u][-V][-v] filename...

Options

Examples

1. Use the following command to convert the files Fonts and Worklog in the current directory:

   m2u Fonts Worklog

2. Use the following command to convert all files ending in .doc in the directory /usr/macvol/docs, display the program version number, and execute in verbose mode:

   m2u -Vv /usr/macvol/docs/*.doc

maccp

This command has the same behavior as the tncp command. It exists for backward compatibility only and may not appear in the next release of TAS. To copy files and directories, use the tncp command.

Location

TNHOME/usr/bin

Usage

maccp [-C] [-i] [-p] [-V] [-u] sourcefile targetfile
maccp [-C] [-i] [-p] [-V] [-u] sourcedir targetdir
maccp [-C] [-i] [-p] [-V] [-u] sourcefile targetdir

Options

Note

The information from source files and directories overwrites the target files and directories.

Examples

1. Use the following command to copy the file textfile to datafile in the current directory:

   maccp textfile datafile

2. Use the following command to copy the directory textfiles in the home directory to datafiles in the /home/macapps directory:

   maccp ~/textfiles /home/macapps/datafiles

3. Use the following command to copy the file textfile in the current directory and the contents of the directory datafiles in your home directory to the /usr/mac directory, and to prompt for confirmation of overwrites and preserve file modification time stamps and permission modes:

   maccp -ip textfile ~/datafiles /usr/mac

macfsck

This command performs a consistency check on a Macintosh volume, verifying that all files and directories in the volume have the appropriate shadow file entries.

Location

TNHOME/usr/bin

Usage

macfsck [-C] [-f] [-r] [-s] [-u] [-V] [-v] [-y] dirname...

Options

Note

The macfsck command's behavior resembles that of the tnvolck command with the -p option. Running the macfsck command always preserves the file name. This command exists for backward compatibility only and may not appear in future releases of TAS. To perform the same function, use the tnvolck command.

Example

Use the following command to perform a consistency check on the subdirectory mac under the current directory with messages displayed as appropriate:

macfsck mac

macmd

This command behaves like the UNIX mkdir command. It exists for backward compatibility only and may not appear in future releases of TAS.

Location

TNHOME/usr/bin

Usage

macmd [-C] [-u] [-V] dir...

Options

Example

Use the following command to create the directory macutils in your home directory, and the directory /usr/macapps/word:

macmd ~/macutils /usr/macapps/word

macmv

This command, similar to the tnmv command, moves Macintosh files and directories and their shadow file information. This command exists for backward compatibility only. It may not appear in future releases of TAS. Use the tnmv command instead of this command for forward compatibility.

Location

TNHOME/usr/bin

Usage

macmv [-C] [-f] [-i] [-u] [-V] file1 file2
macmv [-C] [-f] [-i] [-u] [-V] dir1 dir2
macmv [-C] [-f] [-i] [-u] [-V] file1 dir2

Options

Examples

1. Use the following command to rename the file textfile, in the local directory, to datafile:

   macmv textfile datafile

2. Use the following command to rename the directory textfiles in your home directory to datafiles and move it to the /home/macapps directory:

   macmv ~/textfiles /home/macapps/datafiles

3. Use the following command to move the file textfile in the current directory and the contents of the directory datafiles in your home directory to the directory /usr/mac and prompt for confirmation:

   macmv -i textfile ~/datafiles /usr/mac

macrd

This command, similar to the tnrm command, removes a Macintosh directory and its shadow file subdirectories. You can remove multiple directories with one command line; separate them with spaces

This command exists for backward compatibility only; future releases of TAS may not support it. Use the tnrm command instead of this command for forward compatibility.

Location

TNHOME/usr/bin

Usage

macrd [-C] [-u] [-V] dir...

Options

Example

Use the following command to remove the directory /usr/macapps/word and the directory macutils from your home directory:

macrd ~/macutils /usr/macapps/word

macrm

This command, similar to the tnrm command, removes Macintosh files and directories and their corresponding shadow file entries.

This command exists for backward compatibility only and may not appear in future releases of TAS. Use the tnrm command instead for forward compatibility.

Location

TNHOME/usr/bin

Usage

macrm [-C] [-f] [-i] [-r] [-V] [-u] {file|dir}...

Options

Examples

1. Use the following command to remove the file letter from the home directory:

   macrm ~/letter

2. Use the following command to remove all files ending in .tmp from the current directory and prompt for confirmation:

   macrm -i *.tmp

3. Use the following command to recursively remove all subdirectories and files of /tmp/temp:

   macrm -r /tmp/temp

pfinfo

This command acquires the finder information for a file.

Location

TNHOME/usr/bin

Usage

pfinfo [-C] [-V] [-u] [-m atmap] file...

Options

Examples

1. Use the following command to acquire the finder information for the file Unknown in the current directory:

   pfinfo Unknown

2. Use the following command to acquire the finder information for the file Unknown in the current directory, using the AppleTalk map defatmap:

   pfinfo -m defatmap Unknown

u2m

This command converts UNIX linefeeds to Macintosh carriage returns. You can name multiple files in one command, separate them with spaces.

Location

TNHOME/usr/bin

Usage

u2m [-C] [-u] [-V] [-v] filename...

Options

Examples

1. Use the following command to convert the files Fonts and Worklog in the current directory:

   u2m Fonts Worklog

2. Use the following command to convert all files ending in .doc in the directory /usr/macvol/docs, display the program version number, and execute in verbose mode:

   u2m -Vv /usr/macvol/docs/*.doc

nbmessage

This command sends messages to NetBIOS file service clients. You may specify any number of service names, user names, or clients, up to the maximum length of the command line, preceding each with the corresponding option. This specification defaults to all connected NetBIOS file service clients.

You can use any text for a message, but if it includes any of the following characters, enclose it in quotes to keep the UNIX shell from evaluating the message and protect embedded quotes:

#  $  &  *  {  `  "  `  ?  |  ^  !

If the message text includes dollar signs ($) or back quotes (`), enclose them in apostrophes (').

Location

TNHOME/usr/bin

Usage

nbmessage [-u username] [-c clientname] [-s service] [-n NetBIOS_client...] message

Options

Examples

1. Use the following command to send the message "Roger will back up the server tonight" to all connected clients:

   nbmessage "Roger will back up the server tonight"

2. Use the following command to send the message "You look smashing" to user smitten:

   nbmessage -u smitten "You look smashing"

3. Use the following command to send the message "Who are you?" to the client" N(ickky<00>/2/0)3":

   nbmessage -c "N(ickky<00>/2/0)3" "Who are you?"

4. Use the following command to send the message "The server will shut down in 5 minutes!" to all clients connected to the file service nbmauve:

   nbmessage -s nbmauve:file "The server will shut down in 5 minutes!"

5. Use the following command to send the message "Who are you?" to NetBIOS client NTPC:

   nbmessage -n NTPC "Who are you?"

nbq

This command displays the network print jobs handled by the TAS NBprint process for NetBIOS clients. When you enter this command, the following information displays for each print job:

• the UNIX name of the client user

• the NetBIOS name of the client

• the size, in bytes, of the print job

• the date and time of the print job

• the full path name of the temporary spool file

You cannot use this command to pause, resume, or delete print jobs. You can delete a print job by deleting its temporary spool file or by using the UNIX cancel or lprm command (see the UNIX man pages for those commands).

Location

TNHOME/usr/bin

Usage

nbq [queuename...]

Option

Examples

1. Use the following command to display all NetBIOS print queues:

   nbq

2. Use the following command to display the printers laser and dotty:

   nbq laser dotty

nwmessage

This command sends brief messages to NetWare file service clients.

Location

TNHOME/usr/bin

Usage

nwmessage [-u user] [-c client] [-s service] message

Options

Examples

1. Use the following command to send the message "I will back up the server tonight." to all connected clients:

   nwmessage "I will back up the server tonight."

2. Use the following command to send the message "Hello." to the user spartacus:

   nwmessage -u spartacus Hello.

3. Use the following command to send the message "Who are you?" to the client X(00000100:00aa001a940b):

   nwmessage -c "x(00000100:00aa001a940b)" "Who are you?"

   Use the following command to send the message "I will shut down the server in 5 minutes!" to all clients connected to the file service nwpinial:

   nwmessage -s nwpinial:file "I will shut down the server in 5 minutes!"

nwq

This command displays the print jobs handled by the NWprint process for NetWare clients.

Location

TNHOME/usr/bin

Usage

nwq [queue...]

Notes

1. When you enter an nwq command, the following information appears for each print job:

   • the UNIX name of the client user

   • the size, in bytes, of the print job

   • the date and time of the print job

   • the name of the temporary spool file

2. You cannot use nwq to pause, resume, or delete print jobs. You can delete a print job by deleting its temporary spool file or by using the UNIX cancel or lprm commands (see the UNIX man pages for those commands).

Examples

1. Use the following command to display all NetWare print queues:

   nwq

2. Use the following command to view the print queues of the printer names laser and dotty:

   nwq laser dotty

Shadow File Utilities

Shadow file utilities mimic the functionality of standard UNIX commands while maintaining the integrity of the TAS shadow file system.

• "tnchgrp"

• "tnchmod"

• "tnchown"

• "tncp"

• "tndirck"

• "tnmv"

• "tnrm"

• "tnvolck"

tnchgrp

This command sets the group ID of a file or a directory to a specified group and changes the TAS shadow file group ID information to reflect the new ID. For more information, refer to the UNIX chgrp man page. Only the owner and the superuser may change the group of a file or a directory, and the owner can only change the group to a group in which owner belongs.

Location

TNHOME/usr/bin

Usage

tnchgrp [-f] [-i] [-R] group {file...|dir...}

Options

Examples

1. Use the following command to change the group of the file word.doc to the group tech:

   tnchgrp tech word.doc

2. Use the following command to change the group of the files template.doc and diction.doc, and the directory publish, to the group ID 269:

   tnchgrp 269 template.doc diction.doc publish

3. Use the following command to change the group of the file sample.ppt to the group marketing without receiving any error messages even if the command fails:

   tnchgrp -f marketing sample.ppt

4. Use the following command to change the group of the file logo.gif to the group marketing and prompt for confirmation:

   tnchgrp -i marketing logo.gif

5. Use the following command to change the group of the directory FrameMaker and all files and directories under it to the group document:

   tnchgrp -R document FrameMaker

tnchmod

This command allows you to change or assign the mode of a file or a directory in a manner similar to that of the UNIX chmod command, as well as change the mode of the corresponding TAS shadow file for the specified file or directory. For more information, refer to the chmod man page.

Location

TNHOME/usr/bin

Usage

tnchmod [-f] [-i] [-R] absolute-mode {file...|dir...}
tnchmod [-f] [-i] [-R] symbolic-mode-list {file...|dir...}

Options

Examples

1. Use the following command to change the mode of the file userlist.doc to "read" and "write" permissions for the owner and "read-only" permissions for others:

   tnchmod 644 userlist.doc

2. Use the following command to add "write" permissions for everyone to the files present.doc and schedule.doc and the directory mgmt:

   tnchmod a+w present.doc schedule.doc mgmt

3. Use the following command to change the permission of the file log.nw to 777 without receiving any error messages:

   tnchmod -f 777 log.nw

4. Use the following command to change the permission of the file testplan.doc to 777 and prompt for confirmation before the mode changes:

   tnchmod -i 777 testplan.doc

5. Use the following command to change the mode of the directory marketing, and all files and directories under it, to "read" and "write" permissions for everyone:

   tnchmod -R a+r+w marketing

tnchown

This command sets the user ID of a file or a directory to a specified owner and changes TAS shadow file user ID information of that file or directory to reflect the new ID. Only the owner of the file or directory and the superuser root may change the owner of a file or directory. You can specify the owner as either the user name or the user ID.

Location

TNHOME/usr/bin

Usage

tnchown [-f] [-i] [-R] owner {file...|dir...}

Options

Examples

1. Use the following command to change the owner of the file tnarch.doc to the user jeremy:

   tnchown jeremy tnarch.doc

2. Use the following command to change the owner of the files status.doc and schedule.doc and the directory engineer to user ID 269:

   tnchown 269 status.doc schedule.doc engineer

3. Use the following command to change the owner of tadmin.jpeg to user matt without getting an error message even if the command fails:

   tnchown -f matt tadmin.jpeg

4. Use the following command to change the owner of schedule.ppt to user jacque and prompt for confirmation:

   tnchown -i jacque schedule.ppt

5. Use the following command to change the owner of the directory marketing and all files and directories under it to user diane:

   tnchown -R diane marketing

tncp

This command copies a source file or directory and its corresponding shadow file information to a destination file or directory. This command overwrites destination files that have the same name as the source file, unless you specify the -i option. The source and destination directories must have unique names. For more information, refer to the UNIX cp man page.

Location

TNHOME/usr/bin

Usage

tncp [-f] [-i] [-p] file1 file2
tncp [-f] [-i] [-p] file... dir
tncp [-f] [-i] [-p] [-R] dir1 dir2

Options

Examples

1. Use the following command to copy the file report.doc and rename it schedule.doc:

   tncp report.doc schedule.doc

2. Use the following command to copy the files chapter1.doc and chapter2.doc to the directory manuals:

   tncp chapter1.doc chapter2.doc manuals

3. Use the following command to copy the directory bookfiles, along with all files and directories under it, to the directory manuals:

   tncp -R bookfiles manuals

4. Use the following command to copy intro.doc to preface.doc but attempt to unlink preface.doc first, if it exists and has the "write" permission off:

   tncp -f intro.doc preface.doc

5. Use the following command to copy the file agenda.ppt to the existing file report.ppt and prompt for confirmation before overwriting report.ppt:

   tncp -i agenda.ppt report.ppt

6. Use the following command to copy the file logo.gif to the file graphic.gif, along with attributes of logo.gif:

   tncp -p logo.gif graphic.gif

7. Use the following command to copy all files under the directory system, and their associated shadow files, to the directory etc:

   tncp -R system etc

tndirck

Do not use tndirck for synchronizing TAS shadows files; use "tnvolck". The tndirck command exists for backward compatibility only and will not appear in TAS 5.3.

This command finds the TAS volumes in which the given directories reside. Each directory must reside in one TAS volume. This command passes the volumes as variables and invokes the tnvolck command. The tnvolck command then performs the actual checking and synchronization of TAS shadow files.

Location

TNHOME/usr/bin

Usage

tndirck [-f] [-i] [-p] [-R] dir...

Options

Examples

1. Use the following command to check and clean up shadow files in the directory /usr/backup96:

   tndirck /usr/backup96

2. Use the following command to check and clean up the directory /home/simon/testing without prompting for user confirmation:

   tndirck -f /home/simon/testing

3. Use the following command to check and clean up the directory /usr/bin/andromedia and suppress the file name conversion:

   tndirck -p /usr/bin/andromedia

tnmv

This command moves a source file or a directory and its corresponding TAS shadow file information to a destination file or directory. For more information, refer to the UNIX mv man page.

Location

TNHOME/usr/bin

Usage

tnmv [-f] [-i] file1 file2
tnmv [-f] [-i] file... dir2
tnmv [-f] [-i] dir1 dir2

Options

Note

This command does not support files moving across the mount point. In that case, use tncp and tnrm instead.

Examples

1. Use the following command to move the file phone.doc to the file call.doc without prompting for confirmation even if call.doc already exists:

   tnmv -f phone.doc call.doc

2. Use the following command to move the file intro.ppt to the file preface.ppt and prompt for confirmation before overwriting:

   tnmv -i intro.ppt preface.ppt

3. Use the following command to move the file sample.html to the file main.html:

   tnmv sample.html main.html

4. Use the following command to move the files project1.ps and project2.ps to the directory projects97:

   tnmv project1.ps project2.ps projects97

5. Use the following command to move the directory documents to the directory worddocs:

   tnmv documents worddocs

tnrm

This command removes files or directories and their corresponding TAS shadow file entries. To use this command, you must have privileges to remove files and directories.

Location

TNHOME/usr/bin

Usage

To remove a file:

tnrm [-f] [-i] file

To remove a directory and everything under it:

tnrm [-f] [-i] -R dir

Options

Examples

1. Use the following command to remove the file system.ini:

   tnrm system.ini

2. Use the following command to remove the directory sales, including all files and directories under sales:

   tnrm -R sales

3. Use the following command to remove the files term.doc and pccode.doc without prompting for a confirmation message:

   tnrm -f term.doc pccode.doc

4. Use the following command to remove the directory saleorders, including all files and directories under saleorders, and prompt for confirmation before deleting each file or directory:

   tnrm -i -R saleorders

tnvolck

This command checks and synchronizes files and directories under TAS volumes for the integrity of their corresponding TAS shadow files. The filename-case attribute of the volume specifies the volume's naming convention. The command only needs to synchronize file names for volumes with the filename-case attribute set to lower. By default, if tnvolck needs to synchronize a file name, it prompts for user confirmation before converting the file name.

This command checks for TAS shadow files that no longer have their corresponding UNIX base files. This condition may occur if a user has removed or moved the UNIX files using UNIX commands such as mv or rm, instead of TAS commands tnmv or tnrm. This command removes these shadow files.

This command checks for TAS shadow files that have different owner, group and mode information from their corresponding UNIX base files. This condition may occur if a user has changed the ownership and mode of the UNIX files using UNIX commands such as chown, chgrp or chmod, instead of TAS commands tnchown, tnchgrp or tnchmod. The tnvolck command changes the information on the shadow files to match the information of their corresponding UNIX files.

The tnvolck command checks to see if the files' UNIX names follow their TAS volumes' naming conventions. If a file's name does not follow its volume's specified convention, tnvolck attempts to synchronize it.

Location

TNHOME/usr/bin

Usage

tnvolck [-a] [-[y|n]] [-p] [volume[:file]]

Options

Examples

1. Use the following command to check and clean up shadow files in the volume myvol:

   tnvolck myvol

2. Use the following command to check and clean up shadow files in the volume mybin, which has a substitutable path, and replace it with the path contained in the file /tmp/mydoc.txt:

   tnvolck mybin:/tmp/mydoc.txt

   The /tmp/mydoc.txt path, an ASCII file, contains a list of directory names. Each line should contain a directory path name. For example, the file might contain the following entries:

   /home/simon /home/steven /home/emily

3. Use the following command to check and clean up all TAS volumes, as found in the TAS configuration file:

   tnvolck -a

4. Use the following command to check and clean up the volume saleorders and assume a yes answer to all questions:

   tnvolck -y saleorders

5. Use the following command to check the volume singular without performing directory synchronization or clean-up:

   tnvolck -n singular

6. Use the following command to check and clean up the volume spartacus without converting file names:

   tnvolck -p spartacus

Remote Utilities

Remote utilities allow the UNIX host to obtain printing, file manipulation, messaging, and system time services from remote LM-NT-OS/2 and NetWare servers. Remote utilities for LM-NT-OS/2 servers begin with ru; remote utilities for NetWare servers begin with nc.

Use of Wildcards

Several of remote utilities allow you to use wildcard designators for files, following normal UNIX conventions for wildcard interpretations. The command descriptions and examples in this chapter conform to Bourne shell conventions. When you use wildcards with other shells, you may need to make some changes to the example commands. For example, the C shell expands any wildcards on the command line before passing parameters to the program. This causes unexpected results with the remote utilities commands unless you "escape" the string containing the wildcard, so the shell does not expand it. Do this by using single quotation marks ('), double quotation marks ("), or backslash characters (\). For example, in the Bourne shell, you can use the following command:

rudir -P //server1/root/*.*

To achieve the same result in the C shell, use one of the following commands:

rudir -P '//server1/root/*.*'
rudir -P "//server1/root/*.*"
rudir -P //server1/root/\*.\*

Remote LM-NT-OS/2 utilities

• "ruattr"

• "rucopy"

• "rudel"

• "rudir"

• "rumd"

• "rumessage"

• "ruprint"

• "rurd"

• "ruren"

• "rush"

• "ruslist"

• "rutime"

Remote NetWare utilities

• "ncget"

• "ncprint"

• "ncput"

• "ncslist"

• "nctime"

ruattr

This command, for use with LM-NT-OS/2 servers, allows you to view the current DOS attributes of a file. You can set or clear DOS attributes.

Location

TNHOME/usr/bin

Usage

ruattr [-u username] [{-p password|-P}] [-C charset]
 	[+{a|s|h|r}] [-{a|s|h|r}] //servername/object/path

Options

Notes

1. To use this command, you must first start the LM-NT-OS/2 realm.

2. If you include neither an option to set attributes nor an option to clear attributes, UNIX returns the current attributes of the file.

3. File attributes always appear after modification.

Examples

1. Use the following command to show the attributes of net.exe in the directory split of the shared object client on the server country and prompt for a password, as user maple:

   ruattr -u maple -P //country/client/split/net.exe

2. Use the following command to modify the attributes of the file private.txt in the virtual root of the shared object shared on the server demopc, change it to a Read-Only, Hidden file, and clear the Archive bit, with password mypword:

   ruattr -p mypword -a +rh //demopc/shared/private.txt

3. Use the following command to clear the hidden attributes of all files in the shared object public on the server demopc, prompt for a password, and use the character set "shift-jis", as user Ajax:

   ruattr -u Ajax -P -C shift-jis -h //demopc/public/*.*

rucopy

This command copies files between TAS and an LM-NT-OS/2 server. The file name convention used when copying a file depends upon the protocol negotiated. If UNIX and the server negotiate LANMAN 2.0 or higher as the protocol, this command uses the long file name convention; otherwise, it uses the DOS 8.3 file name convention. Only the path specification permits wildcards. The system checks any file copied to a DOS server for compatibility with DOS file naming conventions. If the target file already exists, the system prompts the user to choose one from the options detailed under the Note below. This remote utility is for use only with LM-NT-OS/2-compatible servers.

Location

TNHOME/usr/bin

Usage

To copy local files to a remote server:

rucopy [-u username] [{-p password|-P}] [-v] [-c]
 	[-C charset] [-f] localfile
 	//servername/object/path

To copy remote files to a local computer:

rucopy [-u username] [{-p password|-P}] [-v] [-c]
 	[-s] [-C charset] [-a{s|h}]
 	//servername/object/path/localpath

Options

If a target file already exists, the system prompts the user to choose one of the following options:

Examples

1. Use the following command to copy all files with extension .c to the sub-directory apps of the object root on the server aspen, display names of files as they copy, and prompt for a password, as user Andrew:

   rucopy -u Andrew -P -v *.c //aspen/root/apps

2. Use the following command to copy files whose names end in .txt in the top directory of the object word on the server demopc to the local directory /tmp, convert the files from DOS to UNIX text format, and supply the password mypass, as user Andrew:

   rucopy -u Andrew -p mypass -c //demopc/word/*.txt /tmp

3. Use the command below to copy the file autoexec.bat in the top directory of the shared object root on the server vampire to the local file autoexec.dos in the current directory. The object root has share-mode access and no password.

   rucopy //vampire/root/autoexec.bat autoexec.dos

4. Use the following command to display the contents of the file notes.txt in the top directory of the shared object root on the server demopc, pipe the output to the program more, and prompt for a password, as user Templeton:

   rucopy -u Templeton -P -s //demopc/root/notes.txt | more

5. Use the command below to copy all files with extension .h in the current local directory to the subdirectory headers of the shared object apps on the server demopc, convert the files from UNIX to DOS text format, and display names of files as they copy. The object apps has share-mode access and no password.

   rucopy -c -v *.h //demopc/apps/headers

6. Use the command below to copy all files from the directory /tmp to the shared object paint on the server demopc, which expects the character set "shift-jis", as user joe, with password joepass2:

   rucopy -u joe -p joepass2 -C shift-jis /tmp/*.* //demopc/paint

rudel

This command, used with LM-NT-OS/2 servers, deletes remote files. You may delete system or hidden files.

Location

TNHOME/usr/bin

Usage

rudel [-u username] [{-p password|-P}] [-C charset]
 	[-a {s|h}] //servername/object/path

Options

Note

If you include no -a options, this command finds only the files marked Read-Only, Directory, and Archive.

Examples

1. Use the following command to delete all files in the subdirectory tmp of the shared object root on the server pipe and prompt for a password:

   rudel -P //pipe/root/tmp/*.*

2. Use the command below to delete the files with the extension .obj in the subdirectory comp of the shared object dev on the server projectpc. The shared object dev has no password.

   rudel //projectpc/dev/comp/*.obj

3. Use the following command to delete all files with the extension .tmp, including hidden files, using the object data in the directory tmp on the server Troy, and prompt for a password, as user galaxy:

   rudel -u galaxy -P -ah //Troy/data/tmp/*.tmp

rudir

This command, for use with LM-NT-OS/2 servers, displays the directory listing of remote files. The listing displays the volume name, file names, file sizes, file modification time stamps, number of bytes used, and number of bytes free on the disk. The format of the listing depends on the negotiated protocol. If UNIX and the server negotiated LANMAN 2.0 or higher as the protocol, this command uses the long file name convention; otherwise, it uses the DOS 8.3 file name convention.

Location

TNHOME/usr/bin

Usage

rudir [-u username] [{-p password|-P}] [-C charset]
 	[-a{s|h}] //servername/object/path

Options

Note

If you include no -a option, this command finds only the files marked Read-Only, Directory, and Archive.

Examples

1. Use the following command to list the files in the subdirectory word/doc of the shared object root on the server demopc, prompt for a password, and use the "euc-jp" character set:

   rudir -P -C euc-jp //demopc/root/word/doc/*.*

2. Use the following command to list all files in the top level of the shared object root with password mypasswd on the server demopc, including system and hidden files:

   rudir -p mypasswd -ash //demopc/root/*.*

3. Use the command below to list all files with the .exe extension on the server columbia and prompt for a password, as user salmon. The object, dev, has the path fry.

   rudir -u salmon -P //columbia/dev/fry/*.exe

rumd

This command, for use with LM-NT-OS/2 servers, creates a directory on a remote server.

Location

TNHOME/usr/bin

Usage

rumd [-u username] [{-p password|-P}] [-C charset] //servername/object/path

Options

Examples

1. Use the following command to create the subdirectory tmp in the top directory of the shared object root on the server aztecserver and prompt for the object's password:

   rumd -P //aztecserver/root/tmp

2. Use the following command to create the subdirectory perm on the object mta on the server boston for the user charlie with password broke:

   rumd -u charlie -p broke //boston/mta/perm

rumessage

This command sends a message to a remote client on LM-NT-OS/2 servers such as Windows for Workgroups, Windows 95, or Windows NT.

Location

TNHOME/usr/bin

Usage

rumessage [-C charset] //servername text

Options

Examples

1. Use the following command to send a message to the server myserver:

   rumessage //myserver Please share a printer.

2. Use the following command to send a message to the server myserver using the "shift-jis" character set:

   rumessage -C shift-jis //myserver Please share a printer.

ruprint

This command prints files on a remote SMB server.

Location

TNHOME/usr/bin

Usage

ruprint [-u username] [{-p password|-P}] [-N copies] [-v]
 	[-c] [filespec] //servername/object

Options

Examples

1. Use the following command to print the file /usr/notes/info.txt on the printer shared as kathpr on the server jessicaserver, and prompt for a password:

   ruprint -P /usr/notes/info.txt /jessicaserver/kathpr

2. Use following command, as user sphinx, to print the file /usr/notes/info.txt on the printer shared as kathpr on the server heatherserver with a prompt for the password:

   ruprint -u sphinx -P /usr/notes/info.txt //heatherserver/kathpr

3. Use the following command, as user joe, to display the queue information for the printer shared as maxar on the server sytos with a prompt for the password:

   ruprint -u joe -P //sytos/maxar

Using ruprint as a Printer

The following instructions describe configuring ruprint as a regular UNIX printer. For example, with ruprint configured as a UNIX printer, you can redirect print jobs to a printer on a remote server that does not run LMserver.

The following examples involve a remote PostScript printer shared as prn on the server dosserver running TAS. It has the UNIX print queue dosq. Refer to your UNIX documentation for complete information on configuring a printer.

For BSD UNIX:

1. Add the following entry for ruprint printcap to the /etc/printcap file:

   dosq|lp:\
   	:lp=/dev/null:\
   	:lf=/usr/adm/lpd-errs:\
   	:sd=/usr/spool/dosqd:\
   	:mx#0:\
   	:rw:\
   	:sh:\
   	:sf:\
   	:if=/usr/bin/dosq.rup:

2. Create the spool directory, indicated by :sd in the printcap entry, as follows:

   cd /usr/spool

   mkdir dosqd

   chown root dosqd

   chgrp bin dosqd

   chmod 775 dosqd

   chmod gas dosqd

3. Create an input filter, indicated by :if in the printcap entry, as follows:

   #!/bin/sh

   # lp filter for ruprint

   PATH=/bin:/usr/bin:/usr/local/bin:TNHOME/usr/bin

   export PATH

   TF=/tmp/dosq.$$

   cat - $TF

   If you need to make the file a PostScript file, run it through the psf filter using the script below. Some operating systems, like Solaris, do this automatically.

   grep '%!PS-Adobe' $TF /tmp/grep.out 2&1

   if [$? -ne 0]; then

   psf $TF ${TF}.1 2>&1

   rm $TF

   TF=${TF}.1

   fi

   ruprint $TF //dosserver/prn 2>&1

   rm -f $TF

   exit 0

For System V:

1. To create the same dosq.rup input filter as for BSD UNIX, make sure the line beginning with cat reads:

   cat $6 $TF

   This script does not work if the file name does not come sixth ($6) on the command line. You can diagnose this by inserting the following line in the script just before the cat line to determine exactly which command line argument contains the file name:

   echo $1 $2 $3 $4 $5 $6 $7

2. After attempting to print to this printer, examine /tmp/args.test to determine the sequence of arguments.

3. Create the printer definition by entering the following command:

   Rapidan -p dosq -i /usr/bin/dosq.rup -v /dev/null

4. Enable printing and allow jobs to queue by entering the following commands:

   enable dosq accept dosq

5. To create a printer queue and device, add the following to the end of /etc/qconfig:

   /etc/qconfig:
   dosq:
   	device = dosqdev
   	up =TRUE
   dosqdev:
   	file = FALSE
   	access = write
   	backend = /usr/bin/dosq.rup

rurd

This command deletes a directory on a remote server.

Location

TNHOME/usr/bin

Usage

rurd [-u username] [{-p password|-P}] [-C charset]
 	//servername/object/path

Options

Example

Use the following command to access the remote server, remove the subdirectory tmp from the top directory of the shared object root on the server kathserver, prompt for a password, and use the character set "builtin-unicode", as user Heather:

rurd -u Heather -P -C builtin-unicode //kathserver/root/tmp

ruren

This command renames files on a remote server.

Location

TNHOME/usr/bin

Usage

ruren [-u username] [{-p password|-P}] [-C charset]
 	[-a{s|h}] //servername/object/path1 path2

Options

Notes

If you include no -a options, this command finds only the files marked Read-Only, Directory, and Archive.

Examples

1. Use the following command to rename the file autoexec.bat in the top directory of the shared object root on the server kathserver to autoexec.old, prompt for a password, and use the character set "builtin-unicode":

   ruren -P -C builtin-unicode //kathserver/root/autoexec.bat autoexec.old

2. Use the following command to access the remote server and rename the file prog.c in the subdirectory apps of the shared object root on the server monaserver into the subdirectory sources if the object has no password:

   ruren //monaserver/root/apps/prog.c /sources/prog.c

rush

This command establishes a remote utility shell session to provide an environment for performing several remote commands without having to reconnect with each command.

Location

TNHOME/usr/bin

Usage

rush [-u username] [{-p password|-P}] [-C charset]
 	[+{a|s|h|r}] [-{a|s|h|r}] //servername/object/path

Options

Notes

1. Once you establish the connection, the name of the remote server displays in the prompt. The remote utilities shell enables the commands shown in the following table:

   ! unix_command	Executes a local UNIX command.
   ? [command] or  help [command]	Acquires information on a remote utilities command.
   attr [+{a|s|h|r}]   [-{a|s|h|r}]	Shows, sets, or clears remote file attributes.
   cd path	Changes current remote directory.
   del path	Deletes remote files.
   dir [-p] [+{a|s|h|r}]  [-{a|s|h|r}]	Lists remote files.
   exit  or  quit	Exits the remote utilities shell.
   get [-v] [-c] [-s] path1 [path2]	Copies files from the remote server.
   lcd path	Changes current local directory.
   lpwd	Shows current local directory.
   md path	Creates a remote directory.
   msg text	Sends a message to the remote server.
   pwd	Shows current remote directory.
   ren path1 path2	Rename remote file(s).
   rd path	Removes a remote directory.
   set [value [options]]	Sets a global value.
   time [-s]	Displays remote system time.
   type path	Displays a remote text file on the local monitor.

2. All commands entered in the remote utilities shell use the password, server name, and object specified in the rush command. To change one of these parameters, you must terminate the shell and issue a new rush command.

Examples

1. Use the following command, as user joe, to connect to the object outnet on the server netserver with path yellowbrick and password joepass using the client character set "iso-greek" for all SMB requests:

   rush -u joe -p joepass -C iso-greek //netserver/outnet/yellowbrick

2. Use the following command to execute the UNIX command ls by temporarily escaping to a UNIX shell:

   ! ls

3. Use one of the commands below to display information about the remote utilities shell pwd, as listed in the table. If you do not specify a command, the screen displays the list of commands available.

   ? pwd

   help pwd

4. Use the following command to display, set, or clear file attributes for dorothy.txt on server far:

   attr //far/dorothy.txt

5. Use the following command to change the current remote directory to skip/hop/jump:

   cd skip/hop/jump

6. Use the command below to delete the remote files ink.doc and inker.doc. This command works like the remote utilities rudel command. It permits wildcards.

   del ink.doc inker.doc

7. Use the command below to list the contents of the remote directory at jump/hop/skip, display the output one screen at a time, and include system and hidden files. Press e to display the next page.

   dir -p -ash jump/hop/skip

8. Use one of the following commands to terminate the current remote utilities shell session and return to the UNIX prompt:

   exit quit

9. Use the command below to copy the remote files turtle.txt and schmurtle.gif to the file bagpipe on the local computer, display the file names as they copy, convert text files from DOS to UNIX format, and display the contents of the files. This works like the remote utilities rucopy command. If a target file already exists, the system prompts you for action as with the remote utilities rucopy command, in which o = "overwrite", a = "overwrite all without further prompting", c = "continue without copying", and n = "use new file name".

   get -v -c -s turtle.txt schmurtle.gif bagpipe

10. Use the command below to temporarily change the local current directory to rainy/rainier/rainiest. This change lasts only as long as the remote utilities shell remains active:

    lcd rainy/rainier/rainiest

11. Use the following command to display the name of the current local directory:

    lpwd

12. Use the command below to create a remote directory using the path seed/sapling/tree. This works like the remote utilities rumd command.

    md seed/sapling/tree

13. Use the command below to send the message "The end draweth nigh" to the remote server. This works like the remote utilities rumessage command. The message appears at the server only if the server can receive messages. Desk To Desk and some other DOS and OS/2 servers can receive and display messages, whereas UNIX-based LM-NT-OS/2 servers cannot.

    msg The end draweth nigh

14. Use the command below to copy the file fingers from the local computer to toes on the remote computer. This works like the remote utilities rucopy command and has the same options as the get command.

    put fingers toes

15. Use the following command to show the current remote directory:

    pwd

16. Use the command below to rename the file good to better. This works like the remote utilities ruren command.

    ren good better

17. Use the command below to remove the directory urg from the remote server. This works like the remote utilities rurd command.

    rd urg

18. Use the sequence of commands below to avoid having to include the -ah option in the dir command. The current attribute setting appears when the command completes. This command defaults to d, the directory attribute.

    set attribute +h

    dir

    The listing includes files with hidden attributes, the same as if you entered:

    dir -ah

19. Use the command below to avoid having to include the -v option on commands to display the names of files as they copy. To turn off the verbose attribute, enter the above command again.

    set verbose

20. Use the command below to reset the prompt so that only the remote server name appears. Enter the same command again to resume the default behavior.

    set prompt

21. Use the command below to generate a trace file called rutrace.txt for Syntax Technical Support that includes incoming and outgoing SMB packets, program procedures, and program errors at a moderate level of tracing detail. To turn tracing off, use set tracing off.

    set tracing -zin=5 -zout=5 -zproc-5 -ztracefile=rutrace.txt

    Use the command below to display and synchronize local time with the remote server's system time. Only the superuser can use the -s option. This option only works if the remote server supports the request.

    time [-s]

22. Use the command below to display the contents of the remote file roland.txt, at the server gunslingers, on the local monitor screen. This command has the same effect as get -s when you do not specify a destination path.

    type //gunslingers/roland.txt

ruslist

This command displays the browse list of all LM-NT-OS/2 servers on the network. Use it only with LM-NT-OS/2 servers.

Location

TNHOME/usr/bin

Usage

To obtain the list of all LM-NT/OS/2 servers known to the local system and display a combined list:

ruslist [-v] [-w workgroup]

To obtain the list as known to a server for a particular workgroup or domain by a domain master browser running on the local system:

ruslist [-v] -w workgroup -n transport -i interface [
 	-p ipaddr] [-l] //servername

Options

Examples

1. Use the following command to obtain the list of servers with all transports and interfaces known to the local system and display a combined list:

   ruslist

2. Use the following command to obtain the list of servers with all transports and interfaces for the workgroup tasserver:

   ruslist -w tasserver

3. Use the following command if a user on a system with TCP/IP interface name 204.242.8.10 wants to obtain a verbose list of all servers in the tasserver workgroup with master browser huey and transport tcpip:

   ruslist -v -w tasserver -n tcpip -i 204.242.8.100 //huey

rutime

This command allows the current system to display the remote server's system time. Any user can display the remote server's time. When you use the -s option, you--the superuser--can synchronize the local system time to that of the remote server.

Location

TNHOME/usr/bin

Usage

rutime [-u username] [{-p password|-P}] [-s] //servername/object

Options

Notes

1. Only the superuser can change the local system time. Any user can run this command to display the remote server's time.

2. The remote server must run TAS. When used with any other server, an error message may result.

Examples

1. Use the following command to display the time at the remote TAS server syntax as user orange and prompt for a password:

   rutime -u orange -P //syntax

2. Use the following command to access the remote server, make the server prompt you for a password, and synchronize the local time to the time on the server syntax and the object time, as the user Tommy.

   rutime -u Tommy -P -s //syntax/time

ncget

This command copies a file from a remote NetWare server the local disk. This utility does not support wildcards.

Location

TNHOME/usr/bin

Usage

ncget -s servername -u username {-p password|-P}
 	[-C charset] [-v] volume:[/]path [localfile]

Options

Examples

1. Use one of the following commands to copy the file pure.doc from the directory subdir on the volume public of the server library to the local file impure.doc, as the remote user tanya:

   ncget -s library -u tanya -P -v public:subdir/pure.doc impure.doc ncget -s library -u tanya -P -v public:/subdir/pure.doc impure.doc

2. Use the following command to copy the file village/well.doc from the server valhalla to the NetWare volume sys, as user eric with password viking:

   ncget -s valhalla -u eric -p viking -v sys:village/well.doc

ncprint

This command prints local files to a remote printer.

Location

TNHOME/usr/bin

Usage

ncprint [-c] [-nf] -s servername -q queuename [-N copies]
 	-u username [{-p password|-P}] filename

Options

Examples

1. Use the command below to print four copies of the local file /tmp/that.doc to the print queue starblazer on the server flip, as user john with password abcdefgh. This command also prevents banner printing and post-printing form feeds.

   ncprint -nf -s flip -q starblazer -N 4 -u john -p abcdefgh /tmp/that.doc

2. Use the command below to print the local file this.doc from the current local directory and send the print job to the print queue nov4dot on the server nov4 as user root. This command does not display the password.

   ncprint -s nov4 -q nov4dot -u root -P this.doc

3. Use the command below to print 10 copies of the file rampage.doc in the directory tmp to the print queue village on server hi, as user mildred with password market:

   ncprint -s hi -q village -N 10 -u mildred -p market /tmp/rampage.doc

ncput

This command copies local files to remote NetWare servers.

Location

TNHOME/usr/bin

Usage

ncput -s servername -u username {-p password|-P}
 	[-C charset] localfile [-v] volume:[/]path

Options