HP FTAM/9000 User’s Guide Edition 4 B1033-90024 HP 9000 Networking E0597 Printed in: U.S.A. © Copyright 1997, Hewlett-Packard Company.
Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty.
©copyright 1980, 1984, 1986 Novell, Inc. ©copyright 1986-1992 Sun Microsystems, Inc. ©copyright 1985-86, 1988 Massachusetts Institute of Technology. ©copyright 1989-93 The Open Software Foundation, Inc. ©copyright 1986 Digital Equipment Corporation. ©copyright 1990 Motorola, Inc.
Printing History The manual printing date and part number indicate its current edition. The printing date will change when a new edition is printed. Minor changes may be made at reprint without changing the printing date. The manual part number will change when extensive changes are made. Manual updates may be issued between editions to correct errors or document product changes. To ensure that you receive the updated or new editions, you should subscribe to the appropriate product support service.
Preface Purpose This guide provides the information you need to use HP FTAM/9000 interactively. This guide does not supply information for installing or configuring HP FTAM/9000 on your local system. For that information, refer to the Installing and Administering HP FTAM/9000 manual. NOTE This guide assumes that HP FTAM/9000 is correctly installed and configured for use. This includes locally configuring the address and alias of each remote host you need to work with.
Terms The following terms are used in this guide: 8 Initiator The person, process, or system that requests an FTAM transaction is called the initiator. Responder The process or system to which an FTAM request is directed is called the responder. Shadow file Every HP FTAM/9000 file has an associated shadow file, which contains attribute information not stored by the HP- UX file system. Local host The system you are logged into is the local host.
Conventions The table below explains the typographic conventions used in this manual. Notation Description computertext or computertext Computer font is used for on-screen prompts and messages, for responses to user commands, and what you type in. Boldface Boldface type is used when a term is defined. italics Italic type is used for emphasis and titles of manuals and publications, and to represent a variable in a syntax statement, such as target_file.
Contents 1. A Foundation for Using FTAM HP FTAM/9000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 Interactive FTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 Command-Line FTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 Programmatic FTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 2. Using Interactive FTAM Chapter Overview . . . . . . . . . . . . .
Contents Streamlining ftam with a Startup File . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Quick ftam Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 3. Using Command-Line FTAM Chapter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Specifying File and Directory Names . . . . . . . . . . . . . . . . . . . . .
Contents Changing File Attributes with fcattr . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 About fcattr. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 Using fcattr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 Examples: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 4. Special FTAM Files Chapter Overview . . . . . . . . . . . . . . . . . . . . . . . .
Contents Using FTAM File Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 6. Resolving FTAM Problems Chapter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 User Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Resolving File Protection Errors . . . . . . . . . . .
1 A Foundation for Using FTAM Computer networks rank among the most complex systems ever invented. These networks are especially complex when they involve systems from many different computer manufacturers.
A Foundation for Using FTAM Reference Model has been adopted by many computer manufacturers. The OSI Reference Model identifies many different aspects of intercomputer communication. The FTAM (pronounced eff'•tam) service was defined by the International Organization for Standards (ISO ). FTAM conforms to the OSI reference model. The FTAM acronym stands for File Transfer, Access, and Management. You will usually use FTAM as a file transfer service.
A Foundation for Using FTAM HP FTAM/9000 HP FTAM/9000 The HP-UX FTAM product has three complimentary interfaces: • Interactive. This is described in Chapter 2, “Using Interactive FTAM.” • Command-line. This is described in Chapter 3, “Using Command-Line FTAM.” • Programmatic. This is described in the HP FTAM/9000 Programmer's Guide.
A Foundation for Using FTAM HP FTAM/9000 The command-line interface to HP-UX FTAM is patterned after a similar ARPA networking service called rcp. Command-line FTAM is covered in Chapter 3, “Using Command-Line FTAM.” For simple file transfers, command-line FTAM is frequently the best approach. Programmatic FTAM This interface is for programmers only. It is used to develop applications that use FTAM services during their execution.
2 Using Interactive FTAM 19
Using Interactive FTAM This chapter describes how to use the ftam program to transfer, access, and manage files. This program transfers files between hosts (both UNIX 1–based and other systems alike) that support FTAM services. It can also be used to perform remote file management operations. The ftam program is patterned after ftp, an Internet service that allows you to copy files between hosts on a network.
Using Interactive FTAM Chapter Overview Chapter Overview This chapter describes how you can use the ftam program to do the following: • Establish, end, and manage ftam sessions. • Get help with ftam. • List, create, and remove remote directories. • Perform file transfers over the network. • Delete FTAM files.
Using Interactive FTAM Basic Steps for Using ftam Basic Steps for Using ftam A typical ftam session consists of the following steps: 1. Invoke ftam. 2. Get connected to the remote host. 3. Use ftam commands. 4. End the ftam session. This section describes steps 1, 2, and 4. Step 3 is covered in later sections of this chapter, titled “Managing an ftam Session,” “Performing Remote Directory Operations,” “Performing Local Operations,” and “Performing File Transfers.
Using Interactive FTAM Basic Steps for Using ftam Provide Login Information to the Remote Host For security reasons, you must provide valid login information for the remote host you specified in step 2. At the prompts that ftam provides, you must supply the remote host with a login name and password it recognizes. The following example illustrates these steps.
Using Interactive FTAM Basic Steps for Using ftam To make login even easier, you can create a special FTAM–related file called.ftamrc in your home directory. This file is used to automate the login procedure. See “Streamlining ftam with a Startup File” later in this chapter. Set a Default Working Directory (Optional) The default working directory for the remote host is assigned by the remote FTAM implementation.
Using Interactive FTAM Basic Steps for Using ftam Step 4: Ending an ftam Session To close the current ftam connection, but remain in ftam, enter close at the ftam prompt. If you want, you can then use the open command to open a connection to a different remote host. ftam> close Released connection to denver. ftam> open madrid To end an ftam session altogether and return to your system prompt, enter quit at the ftam prompt. ftam> quit Released connection to denver.
Using Interactive FTAM Basic Steps for Using ftam • The initial remote working directory for file transactions is determined by the FTAM implementation on the remote host. HP FTAM/9000 responders set the initial working directory to be the home directory for the user noted in the “Connected to ...” message during ftam startup (See “Step 2” in the previous discussion). Other (non-HP-UX) FTAM implementations are apt to use different conventions.
Using Interactive FTAM Managing an ftam Session Managing an ftam Session This section discusses how to use ftam commands to control various aspects of your ftam session. Table 2-1 explains the session-control commands you can use at the ftam> prompt : Table 2-1 Commands for Controlling Your ftam Session Command Function bell When bell is on, a bell (or beep) sounds after each file transfer. Enter bell at the ftam prompt to toggle the bell setting. bye or quit Terminates your ftam session.
Using Interactive FTAM Managing an ftam Session Example: You can display the status of your local ftam settings by entering status at the ftam prompt. The display will show you the activated commands as well as the remote host. This example shows a simple ftam session during which Sue modifies some local settings using the bell and prompt commands before transferring files. $ ftam denver Username (denver:sue): sue Password (denver:sue): Connected to denver as user sue.
Using Interactive FTAM Performing Remote Directory Operations Performing Remote Directory Operations The ftam program allows you to manipulate the remote host's file system. You can change your current working directory at the remote host; delete, rename, and change the attributes of remote files; and create, rename, and delete directories on the remote host (however, see the following section on directory support). Table 2-3 lists commands that allow you to work with remote files.
Using Interactive FTAM Performing Remote Directory Operations Command Function dir [name] [file] If the name argument is a directory, dir shows a “summary” listing of the files the directory contains; the default is the remote working directory. If the name argument is a file, dir displays a summary listing of the file if it exists. If the file argument is given, the output from the command is placed in a file by the specified name.
Using Interactive FTAM Performing Remote Directory Operations ftam> ls fn_1gfs fn_1gnl fn_1gns fn_2m fn_2s fn_3m fn_3s ftamdir ftam> ls -a fn_1gns Filename: Permissions: File type: Storage account: File creation: Last file modification: Last read: Last attribute modification: Identity of creator: Identity of modifier: Identity of reader: Identity of attribute modifier: File availability: Filesize: Access Control: Legal qualification: /users/donald/reports/fn_1gns R-PXEACD--text (FTAM-1) no value available
Using Interactive FTAM Performing Remote Directory Operations The cattr command can perform the actions in Table 2-4. Use the associated cattr command option to request an action. Syntax of the cattr Command The syntax for the cattr command is as follows: cattr -dinflsv new_attribute [-dinflsv new_attribute] ... file The cattr command always works on files in the remote filestore you are connected to. You can use one or more options in a command (one at a time, each followed by its argument).
Using Interactive FTAM Performing Remote Directory Operations Examples:. This example illustrates how to rename a remote file using cattr. The file called oldfile is renamed to newfile. ftam> cattr oldfile -n newfile This example adds access control for the file's owner, allowing all actions.
Using Interactive FTAM Performing Remote Directory Operations Directory Support in FTAM Implementations The behavior of some directory commands depends on the remote system. 1 Some remote FTAM implementations might not support the concept of directories, but others, like HP FTAM/9000, do. Table 2-5 explains the effect of different levels of support for directories: Table 2-5 Command Effect of Directory Support on ftam Commands If remote system supports the concept of directories, ...
Using Interactive FTAM Performing Local Operations Performing Local Operations The ftam command allows you to change the local working directory . You can also execute HP-UX commands, or start an interactive shell using customary HP-UX syntax. Table 2-6 illustrates the ftam commands to do this: Table 2-6 Performing Local Operations Command Description lcd directory Changes the local working directory. Note that the directory parameter is literal; environment variables (like $HOME) are not recognized.
Using Interactive FTAM Performing File Transfers Performing File Transfers The ftam commands in Table 2-7 let you copy files to and from the remote host: NOTE See “Notes About Remote File and Directory Names” earlier in this chapter for guidelines on specifying remote names. Table 2-7 ftam Commands for Transferring Files Command Description append local_file [remote_file] Transmit the local_file to the remote host, and append it to remote_file.
Using Interactive FTAM Performing File Transfers Example In this example, Sue uses the get command to copy the report.dat file from the remote host denver to her working directory on the local host. Note how ftam reports the successful transfer: $ ftam denver Username (denver:Sue): Sue Password (denver:Sue): Connected to denver as user Sue. ftam> get report.dat Received file /users/marketing/sales/sue/report.
Using Interactive FTAM Streamlining ftam with a Startup File Streamlining ftam with a Startup File You can have ftam skip the password request and automatically set up a connection to a remote host. To automate your ftam connections, you create an FTAM “startup” file (called .ftamrc ) in your home directory. This file contains login information for specific remote hosts. Once login information is available in .ftamrc, ftam does not prompt you for passwords during connection establishment.
Using Interactive FTAM Streamlining ftam with a Startup File Example Sue has the following entries in her .ftamrc file: machine denver login don password shadowy machine denver login sue password mystery machine atlanta login kelly In this example, Sue connects to each host with ftam to show the effect of these entries.
Using Interactive FTAM Quick ftam Command Reference Quick ftam Command Reference Table 2-8 ftam Command Summary Command Abbreviation Function ! N/A Execute a local command or new shell. ? N/A Request help. append a Append to a remote file. bell be Toggle file transfer bell. bye by End an FTAM session. cattr ca Change FTAM file attributes. cd cd Change the current remote working directory. close cl End the current connection. connect co Establish a connection.
Using Interactive FTAM Quick ftam Command Reference Command Abbreviation Function pwd pw Get current remote working directory. quit q End an FTAM session. recv rec Copy remote file to local file. release rel End the current connection. rename ren Change the name of a file. rmdir rm Delete a remote directory. send sen Copy local file to remote file. set set Set FTAM parameters. status st Request a status report. unset un Unset file options.
Using Interactive FTAM Quick ftam Command Reference 42 Chapter 2
3 Using Command-Line FTAM This chapter describes how to use the FTAM service directly from the HP- UX system prompt, rather than through the ftam program described in Chapter 2, “Using Interactive FTAM.
Using Command-Line FTAM Table 3-1 FTAM Commands Command Function fcp source target Copies an FTAM file between systems. The contents of source are unaffected; its attributes might be updated. fmv source target Moves an FTAM file between systems. The source is deleted in the process. fls [name] Lists an FTAM directory (or file), named name. fdel file Deletes an FTAM file. fcattr file Changes the FTAM attributes of a file.
Using Command-Line FTAM Chapter Overview Chapter Overview • Each of the above commands has, as a parameter, a file or directory name. The next section shows how to specify file and directory names. • The remainder of this chapter describes how to use each of the commands listed above, along with its options and parameters. • Some of the above commands can take command options. These options are discussed separately for each command.
Using Command-Line FTAM Specifying File and Directory Names Specifying File and Directory Names This section covers the way you specify both local and remote file and directory names. Specifying Local Names Specify local file and directory names with the usual HP-UX syntax and conventions. Specifying Remote Names Remote file and directory names have three elements, as described in Table 3-2. Table 3-2 Name Elements Element Description user The login name that will be used to access the remote host.
Using Command-Line FTAM Specifying File and Directory Names The local host uses the login name betty to access the remote HP-UX host named denver. You are prompted to supply betty's password. The file name (memos/mymemo) accesses a file called mymemo in the memos subdirectory of betty's home (default) directory. Notice that this example file name uses normal HP-UX syntax; other vendors' responders require the native syntax and conventions of the host.
Using Command-Line FTAM Specifying File and Directory Names Shortcut Remote Names You can omit the user@ portion of a remote name if your ftam startup file contains an appropriate entry (see Chapter 4, “Special FTAM Files,” for information about the ftam startup file).
Using Command-Line FTAM Copying Files with fcp Copying Files with fcp The fcp command can transfer a remote file to the local host, or a local file to a remote host. From your local host, you can also use fcp to copy files between two remote hosts, or make a local copy. About fcp The fcp command is patterned after rcp, a Berkeley service that copies files between UNIX hosts on a network. With fcp, you can create a copy (either local or remote) of an existing file (either local or remote).
Using Command-Line FTAM Copying Files with fcp Example: In this example, a user known as betty uses fcp to create a copy of the local file localplan in her home directory on a remote HP-UX host called chicago: $ fcp localplan chicago:localplan Password (chicago:betty): $ Note that you are prompted for betty's password at chicago. Creating a .ftamrc file may allow you to bypass this prompt. In fcp file transfers, you must explicitly specify both the source and destination file names.
Using Command-Line FTAM Moving Files with fmv Moving Files with fmv The fmv command can move a remote file to the local host, or a local file to a remote host. From your local host, you can also use fmv to move files between two remote hosts, or move files locally. The fmv command can also be used to rename a file, leaving it in its original place. About fmv With fmv, you can move an existing file (either local or remote) to a new location (either local or remote).
Using Command-Line FTAM Moving Files with fmv Example: In this example, a user known as betty uses fmv to move the local file localplan to her home directory on a remote HP-UX host called chicago: $ fmv localplan chicago:localplan Password (chicago:betty): $ Note that you are prompted for betty's password at chicago. Creating a .ftamrc file may allow you to bypass this prompt. In fmv file transfers, you must explicitly specify both the source and destination file names .
Using Command-Line FTAM Deleting Files with fdel Deleting Files with fdel The fdel command can delete remote or local FTAM files. About fdel With fdel, you can delete existing FTAM files (either local or remote). When you use this command, the original file or files no longer exist. When fdel completes, your local host redisplays its prompt . When you work with remote files, the working directory for fdel on the remote host is a default directory that depends on the remote FTAM implementation.
Using Command-Line FTAM Deleting Files with fdel Example: In this example, a user known as betty uses fdel to delete a local file–localplan. She also deletes a remote file–regionplan–in her home directory on the host called chicago: $ fdel -i localplan chicago:regionplan Password (chicago:betty): Remove “localplan” (y/n): y Remove “chicago:regionplan?“? (y/n): y $ Note that you are prompted for betty's password at chicago. Because of the -i option, you are also requested to confirm the deletion request.
Using Command-Line FTAM Listing Directories with fls Listing Directories with fls The fls command lists directories or files. About fls With fls, you can list existing either local or remote directories or files. NOTE If the remote FTAM implementation does not support the concept of directories (i.e., NBS–9 type documents), fls does not work; you will receive an error message. When fls is finished, your local host redisplays its prompt.
Using Command-Line FTAM Listing Directories with fls Command Options for fls The following table summarizes the two unique command options (excluding –z) for the fls command: Table 3-3 Command Options for fls Option Description –a Requests a complete listing, including information about every FTAM file attribute for each file listed. –l Requests a “summary” listing of the directory.
Using Command-Line FTAM Listing Directories with fls Example: The following example illustrates the different kinds of file listings that are available. The example continues on the next page.
Using Command-Line FTAM Changing File Attributes with fcattr Changing File Attributes with fcattr The fcattr command is similar to the HP-UX chmod command. About fcattr The FTAM specification defines many attributes that describe an FTAM file. The fcattr command gives you the ability to modify many of these attributes for a file. To change the attributes of a file, you must have at least FTAM change_attribute permission for the file. The fcattr command can perform the actions in Table 3-4.
Using Command-Line FTAM Changing File Attributes with fcattr Action Command Option Option Argument Change the file's legal qualification.* -l New legal qualification (Character string) Change the file's storage account.* -s New account (Character string) Change the file availability.* -v -v I or -v i :Immediate -v d or -v D :Deferred *HP FTAM/9000 does not keep track of these attributes for local files. The option is for use with other FTAM responders.
Using Command-Line FTAM Changing File Attributes with fcattr 60 Chapter 3
4 Special FTAM Files This chapter discusses certain files that FTAM uses for special purposes.
Special FTAM Files Chapter Overview Chapter Overview FTAM uses three types of special files for distinct purposes: • Maintaining FTAM file attributes and access control information that HP-UX does not inherently support. • Simplifying routine FTAM operations, like establishing connections. • Maintaining the configuration information necessary to permit connections between hosts. FTAM users do not generally need to read or change the local configuration.
Special FTAM Files FTAM Shadow Files FTAM Shadow Files The FTAM Virtual File Store (VFS) is defined by the FTAM ISO standard, and provides a common file system abstraction for all FTAM implementations to use. Each vendor independently maps the FTAM VFS to their real file system. The FTAM VFS defines several file attributes—including access control mechanisms—that are not native to HP-UX. (See Chapter 5, “FTAM File Protection.
Special FTAM Files FTAM Shadow Files Precautionary Notes about Shadow Files An HP-UX file together with its FTAM shadow file forms a logical unit, which should be maintained. This logical unit can be thought of as “an FTAM file,” and is distinct from an ordinary HP-UX file. The two HP-UX files are paired, based on their related names. However, the underlying HP-UX system does not enforce this logical matching.
Special FTAM Files The FTAM Startup File The FTAM Startup File If you want to simplify your day–to–day use of FTAM, you can create a “startup” file called .ftamrc, usually in your home directory. The .ftamrc file contains two types of information: • The logins and passwords for connecting to remote hosts. • Special default settings for FTAM operation. CAUTION A startup file that contains password information is a potential security hazard . This may be an unacceptable risk in some situations.
Special FTAM Files The FTAM Startup File Having this line in .ftamrc can simplify using FTAM with the host named chicago. FTAM uses the login name betty, and the password sesame to gain access to chicago. The default directory on the remote host (chicago) depends on the FTAM implementation there. Each item on the line is separated from its neighbors with “white space” (tabs or spaces).
5 FTAM File Protection The FTAM Virtual File Store (VFS) is defined by the FTAM ISO standard, and provides a common file system abstraction for all FTAM implementations to use. Each vendor independently maps the FTAM VFS to their real file system.
FTAM File Protection The FTAM VFS defines several file protection mechanisms that are not native to HP-UX. This chapter discusses these attributes and mechanisms and how to work with them. NOTE Many people only need to know about the –X option (for exclusive access). This option is covered later in this chapter.
FTAM File Protection Chapter Overview Chapter Overview This chapter has these main sections: • Introduction to FTAM File Protection. • Concepts of FTAM File Protection. • Action/Concurrency Strings. • Using FTAM File Protection.
FTAM File Protection Introduction to FTAM File Protection Introduction to FTAM File Protection One of the key FTAM features is its sophisticated file protection scheme. FTAM provides two related mechanisms to protect files from undesirable or unauthorized use: • The first—called access control —controls the actions that users can perform on the file. A file has a list of permissions (permitted actions), which specify the actions that are allowed to be performed on the file (see Table 5-1).
FTAM File Protection Introduction to FTAM File Protection NOTE Vendors implement an FTAM access control scheme appropriate to the host system. Because of this, using access control is apt to cause complications. For example, HP-UX FTAM can apply access control to a file according to the three HP-UX ownership classes: user, group, and other. Other FTAM implementations may apply access control to individual users, different classes of users, or elect to not implement file protection at all.
FTAM File Protection Introduction to FTAM File Protection If a file has FTAM access control applied to it, the only users who can perform a given action on a file are those users who have been explicitly granted permission to perform that action with the file. • Locking a file during access, to ensure the integrity of the data. Many common activities can corrupt data if multiple users are permitted simultaneous access. Therefore, HP-UX FTAM provides ways to “shut-out” other users during critical operations.
FTAM File Protection Introduction to FTAM File Protection Permissions The following table lists the name of each possible permission (or “file–action”), an associated code letter, and an explanation of its meaning. The code letters appear in action/concurrency strings 1, and in extended and summary listings from fls and ftam: Table 5-1 Action Name Possible File Actions Code Letter Explanation: Read R ... read the file. Insert I ... insert new data anywhere in the file. rePlace P ...
FTAM File Protection Introduction to FTAM File Protection Concurrency Control The following table lists each valid concurrency control value (or “lock”) which can be applied to a file action, and its associated code for use in action/concurrency strings: Table 5-2 Lock Name Concurrency Control Locks Code Letter Explanation You perform the action Others perform the action Shared S Use shared–access when you need to perform the action, and would not experience conflict if other users simultaneously
FTAM File Protection Concepts of FTAM File Protection Concepts of FTAM File Protection As noted before, there are two related concepts in FTAM file protection: access control, and concurrency control. Access control governs the actions that are permitted on a file, granting different users different subsets of the available actions. Concurrency control governs whether and how multiple users can access the file. Concurrency control is applied independently to each action, as will be described later.
FTAM File Protection Concepts of FTAM File Protection Now examine the italicized entry labelled Access Control. Each user in this category is granted different permissions: • The owner of the file, user, has full permission (excluding Insert, as just noted). • Co-workers in the owner's group can Read, eXtend, and read the Attributes of the file; they are excluded from any other activity that involves this file.
FTAM File Protection Concepts of FTAM File Protection (Read and read Attributes) could be given “shared” access , which allows multiple users to perform these actions simultaneously. Possible concurrency controls are listed in Table 5-2. Note, however, that HP-UX FTAM does not keep track of concurrency control applied to file–actions. There is no effect if you attempt to set (or satisfy) file–action concurrency control on files stored by an HP-UX FTAM host, either local or remote.
FTAM File Protection Action/Concurrency Strings Action/Concurrency Strings As noted throughout this guide, action/concurrency strings are used as arguments to options for two commands within ftam, and as arguments to options for several command–line FTAM commands. The exact usage of an action/concurrency string in each of these commands is covered in the section “Using FTAM File Protection” later is this chapter.
FTAM File Protection Action/Concurrency Strings Element password Description A password associated with the file action; there may be no password. HP-UX FTAM does not store passwords for file actions; this field is only provided for users whose remote responders do support action passwords. The previous example is reproduced below. Each element is labelled to indicate its function in the command. Figure 5-1 $fmv myplan -z D=X.PassMeBy denver:FY91plan -z P=X.
FTAM File Protection Using FTAM File Protection Using FTAM File Protection The tables in this section describe the syntax and use of HP-UX FTAM's action/concurrency strings. Action/concurrency strings are always and only used as arguments to certain command options, as noted in the following tables. The syntax for action/concurrency strings is abbreviated to “a/c” in these tables. The previous section contains details about action/concurrency strings.
FTAM File Protection Using FTAM File Protection Note that unless a file has passwords or concurrency control associated with actions, you do not need to use the –z option to satisfy access control. You either have permission to perform the desired action, or you do not. To obtain exclusive access to a file, use the –X option, which does not require an action/concurrency string argument.
FTAM File Protection Using FTAM File Protection To restrict access for others to read and read_attributes on the file JuneData, enter the following command: $ fcattr JuneData -i user,RPXEACD -i group,RPXEACD -i other,RA The following examples illustrate correct use of the -z and –i option for several different situations. This allows the user and group members full access to the file, while other users have only read and read attribute access.
FTAM File Protection Using FTAM File Protection In the next example, the file owner sets special permissions which permit multiple users to simultaneously read or read the attributes of the directory (providing they know the password). However, a user will require knowledge of a different passwords to delete, or change the attributes of, the directory.
FTAM File Protection Using FTAM File Protection 84 Chapter 5
6 Resolving FTAM Problems This chapter is intended to help you resolve any difficulty you encounter while using HP FTAM/9000.
Resolving FTAM Problems Chapter Overview Chapter Overview There are essentially two kinds of problems you can encounter when using FTAM: • User errors • Network/Resource errors This chapter has two main sections to cover these two types of errors.
Resolving FTAM Problems User Errors User Errors A user error occurs when you make an invalid request that FTAM can not fulfill. Errors in this category include typing errors, non-existent source files, file protection errors, and so on. The message you receive when FTAM detects a user error should be straightforward, and the remedy should normally be self-evident. The cause of file protection errors may be less obvious; see the next section for details.
Resolving FTAM Problems User Errors Steps to Resolving File Protection Errors Figure 6-1 Do you own the file? YES NO Use fls -a to check for access control elements (aces): Does fls -a fail? YES Use fls -a to check for access control elements (aces): Does fls -a fail? NO NO If fls -a indicates aces, do you, as the owner, have the required permissions? NO You do not have access to attributes. Use fchdoc to rebuild the shadow file.
Resolving FTAM Problems Network and Resource Errors Network and Resource Errors Network and resource errors occur when some aspect of the network which supports FTAM fails to operate correctly. Errors in this category include hardware failures and resource exhaustion. For example, if the network cable is damaged or disconnected, all network operations (including FTAM) will fail. Likewise, if the lower layers of the network are not running, FTAM failures will occur.
Resolving FTAM Problems Network and Resource Errors 2. Turn on verbose mode (ftam> setv), reproduce the error, and write down the “log instance” number that appears in the error message. This number will be important as you begin further troubleshooting. See the section following for a general overview of troubleshooting. 3. Turn to the OSI Troubleshooting Guide. That document contains detailed information about troubleshooting the network. Troubleshooting is easiest when performed by an experienced person.
Resolving FTAM Problems Network and Resource Errors • Setting the API to 2 causes input parameters, as well as procedure entry and exit, to be traced.
Resolving FTAM Problems Network and Resource Errors 92 Chapter 6
7 FTAM File Details This chapter discusses FTAM document types, the default attributes applied to FTAM files, and manual control of FTAM file attributes.
FTAM File Details Document Types Document Types The FTAM Virtual File Store (VFS) defines several document types. Document types generally correspond to file types on actual computer systems. Files are classified into various document types based on their structure and the interpretation of their contents. HP FTAM/9000 currently supports five FTAM document types: Table 7-1 FTAM Document Type Definitions FTAM-1 FTAM-1 documents are unstructured text files.
FTAM File Details Default FTAM File Attributes Default FTAM File Attributes When HP-UX FTAM creates a shadow file, it applies the default FTAM attributes noted in the following table: Table 7-2 Default FTAM File Attributes Attribute Default Value Document type FTAM-1 Access control None Permissions Read, eXtend, rePlace, Erase, read_Attributes, Change_attributes, Delete. (That is, all actions are permitted.
FTAM File Details Manual File-Attribute Control Manual File-Attribute Control HP-UX FTAM provides a special tool for direct control of a file’s FTAM attributes. This tool , the fchdoc command, can be used to modify or reconstruct a shadow file for an FTAM file. It is only in unusual circumstances that you may need to use the fchdoc command to deliberately override the default or defined attributes for a file. Refer to the online man pages for information on the fchdoc command.
Index FTAMRC environment variable, 65 Security hazard, 38, 65 A Abbreviation, of ftam commands, 24 Access Shared and Exclusive, 76 Access control, 8, 70 with fcp, 51, 53 Access control list Manipulating, 32 Action/Concurrency string Example, 79 Action/concurrency string Elements of, 78 Alias, 46, 66 append command, 36 Attributes Changing with cattr, 30, 31 Changing with fcattr, 58 Default, 95 fchdoc command, 96 Manual control of, 96 B bell command, 27 bye command, 27 C cattr command, 30 Example, 33 Syntax
Index FTAM Acronym, 16 Startup file, 48 Three interfaces to, 17 ftam Abbreviating commands, 24 Basic steps for using, 22 close, 25 Ending a session, 25 open command, 22 open command, bypassing, 23 Passwords, 23 Stopping, 25 ftam commands append, 36 bell, 27 bye, 27 cattr, 30 cattr, Syntax and use, 32 cd, 30, 34 close, 27 connect, 27 delete, 30 dir, 30 get, 36 help, 27 ls, 30 mdelete, 30 mget, 36 mkdir, 30 mput, 36 open, 27 put, 36 pwd, 30 recv, 36 release, 27 rename, 30 rmdir, 30 send, 36 set, 27 status, 2
Index put command, 36 pwd command, 29, 34 Q Quick reference, ftam, 40 R rcp, compared to fcp, 49 recv command, 36 release command, 27 Remote directories and ftam, 29 Remote file names Names, 47 Remote host, 8 Remote names, file and directory, 46 Remove File or directory, ftam, 30 rename command, 30 Rename file with cattr, 32 with fcattr, 58 with rename, 30 Responder, 8 rmdir command, 30, 34 S Security, 23, 38, 65 Access control, 67 Concurrency control, 67 send command, 36 set command, 27 Shadow files, 8, 6
