HP ARPA File Transfer Protocol User’s Guide HP 3000 MPE/iX Computer Systems Edition 6 Manufacturing Part Number: 36957-90159 E0300 U.S.A.
Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
Contents 1. Overview The ARPA Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MPE/iX File Transfer Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FTP User (Client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Transferring Files from Other Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 Transferring Multiple Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 Prompting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 Using Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 6. MPE/iX File System and Data Transfers How FTP Transfers Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ASCII Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Binary (IMAGE) Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bytestream (Byte—Local-byte 8) Transfers . . . . . . . . . . . . . .
Contents Glossary 6
Tables Figure 1-1.. FTP Client-Server Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 1-2.. MPE/iX FTP User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 1-3.. MPE/iX FTP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 6-1.. ASCII Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 6-2..
Tables 8
Preface The HP ARPA File Transfer Protocol product provides the ARPA file transfer protocol (FTP) service to MPE/iX users. Related Documentation The following manuals contain information related to the product described in this manual.
1 Overview This chapter briefly describes ARPA services and what is provided on MPE/iX. In addition, who should use this manual is included.
Overview The ARPA Services The ARPA Services The ARPA services are a subset of the networking services originally developed by the University of California at Berkeley for the Advanced Research Projects Agency (ARPA). ARPA services have become a de facto standard for multivendor network communication. FTP FTP is an ARPA Service that allows users to transfer files among other networked systems. FTP is the file transfer program that uses the ARPA standard File Transfer Protocol (FTP).
Overview MPE/iX File Transfer Protocol MPE/iX File Transfer Protocol The MPE/iX FTP is an implementation of both the client and server programs which conform to RFC959 and RFC1123. The MPE/iX FTP can transfer files with FTP implementations on many other system types, including MS-DOS, OS2, HP-UX, (AT&T, IBM & SUN) variations of UNIX, POSIX, VAX/VMS, IBM/MVS, HP-RTE and other MPE systems. FTP/iX is supported over Internet Protocol (IP) based network and operates over many different hardware links.
Overview Who Should Use This Manual Who Should Use This Manual This manual is intended for MPE/iX users who want to transfer files between MPE/iX and other HP and non-HP systems that support the FTP service. FTP User An MPE/iX user can access a remote systems FTP server by running the MPE/iX FTP client program. The MPE/iX user enters commands to the FTP client program, which sends them to the remote systems FTP server. The remote systems FTP server responds with messages and data, as shown in Figure 1-2..
Overview Who Should Use This Manual Figure 1-3. MPE/iX FTP Server Before Using the FTP Client In order to use the FTP client, your network administrator must have a network up and running. The remote host you wish to access must be reachable from your network. You should have some understanding of the remote file system you want to access.
Overview Who Should Use This Manual 16 Chapter 1
2 FTP User Commands: Quick Reference This chapter provides a quick reference of the syntax and usage of the FTP user commands. The commands are listed in alphabetic order. FTP user commands can be entered in uppercase or lowercase letters. To stop a file transfer or directory listing in progress, you can use [CTRL]-Y. You are prompted to exit FTP, cancel the transfer, or continue. From the FTP prompt you can exit by entering QUIT or pressing the [Break] key.
FTP User Commands: Quick Reference Sets the file transfer type to bytestream. CASE When using the MPUT command, turns on or off the feature to force resulting filenames to lowercase. When case is off, resulting file names are all uppercase. The default is off. CD remotedirectory Changes the working directory on the remote host to the directory specified. CLOSE ClosesU the remote connection but remains in the FTP program.
FTP User Commands: Quick Reference The move option requests that the specified source file be physically moved from the source location to the specified target location. This is available for MGET, PUT and MPUT as well. NOTE The removal of the original source file may be guarded by file system security. HASH Toggles the state of the hash function within the ftp client.
FTP User Commands: Quick Reference Transfer multiple files using wildcard characters in the localfiles parameter. Optionally, build parameters can be specified if the remote system is an MPE/iX system. The build parameters affect each file in the transfer. Non-MPE/iX FTP servers will not interpret the build parameters as intended. The resulting file names are in uppercase letters unless you use the CASE command to force the resulting file names to all lowercase letters.
FTP User Commands: Quick Reference on sets the internal replace flag and the value of the FTPREPLACE CI environment variable to TRUE (this is the default state). In this case, all file transfers will unconditionally replace the target file. off sets the internal replace flag and the value of the environment variable to FALSE. In this state, all file transfers will be conditional predicated on user response to replace the target file if it previously existed. RESET Clear reply queue.
FTP User Commands: Quick Reference The connection timeout value indicates how long to wait for a message from the remote FTP server before giving up. The allowable range is 0 to 3000. A value from 1 to 3000 indicates a timeout value in seconds. A value of 0 means no timeout (that is, wait forever). If num-secs is not specified, the current timeout value will be displayed. Otherwise, this command sets the connection timeout to num-secs seconds.
3 Getting Started: A Simple FTP Session This chapter provides you with a simple FTP file transfer session. The example shows the output from an MPE/iX user’s terminal accessing an HP 9000. The FTP responses shown are with verbose mode on.
Getting Started: A Simple FTP Session FTP Session Example FTP Session Example To follow the same steps as the example, make sure you have the following: • Remote logon name and passwords • Remote system internet protocol (IP) address • Create or have available a simple text file of type ASCII to transfer to the remote system. Step 1: Run FTP After you have entered your MPE/iX user account, enter: :FTP.ARPA.
Getting Started: A Simple FTP Session FTP Session Example Step 4: Transfer a File from MPE/iX to the Remote Host Select a simple ASCII text file, for example, README from your list of files. Transfer your local file to the remote host file named readme1 using the PUT command as follows: ftp> PUT README readme1 200 PORT command okay. 150 Opening data connection for readme1 (123.50.42.32,50894) 226 Transfer complete nnn bytes sent in n.nn seconds: (nn.
Getting Started: A Simple FTP Session FTP Session Example NSCREEN2 NSPROGX PROG README README2 80B 1934W 80B 80B FA VB FA FA 500 4551 500 500 14000 9480 14000 14000 Step 7: Exiting the FTP User Program When you are finished transferring files or performing directory operations, enter QUIT. ftp> QUIT 221 Goodbye. END OF PROGRAM : When you issue a QUIT command, you are logged off the remote host, and the remote connection is closed. You are returned to your MPE/iX session prompt.
4 Using FTP This chapter provides you with the information you can use to accomplish the following tasks with FTP: • Running the FTP User Program • Connecting and Logging on to a Remote Host • Performing Directory Operations • Setting or Changing Transfer Types • Transferring Files • Renaming Remote Files • Deleting Remote Files • Viewing Local Settings • Issuing MPE/iX Commands from Within FTP • Temporarily Exiting FTP • Obtaining Help • Using FTP Commands in UDCs and Programs • Obtaining Status Informatio
Using FTP Running the FTP User (Client) Program Running the FTP User (Client) Program To run the FTP client program from the CI prompt: :RUN FTP.ARPA.SYS [; INFO= “remotehostname”] or :FTP.ARPA.SYS [remotehostname] or on 5.0 and greater, if the HPPATH CI variable has ARPA.
Using FTP Connecting and Logging On to a Remote Host ftp> OPEN 123.1.20.125 Node Names Besides using IP addresses with the FTP OPEN command, you can use either an ARPA domain name or an NS node name in the OPEN command. NS names are recognized if the remote host supports the Probe protocol or if the remote host name is configured in your local node network directory. ARPA domain names are configured in two ASCII files, RSLVCNF.NET.SYS and HOSTS.NET.SYS.
Using FTP Performing Directory Operations Performing Directory Operations With FTP, you can view the remote working directory, change remote directories, and view or save a listing of the contents of remote directories. Viewing the Remote Working Directory The PWD command is used to list the name of the remote working directory. The content of the information displayed by PWD is dependent on the remote system.
Using FTP Performing Directory Operations testt 226 transfer complete Listing Directory Information to a Local File You can transfer remote directory information to a local file with the LS or DIR commands using the following form (assuming a remote host UNIX file system): ftp> DIR [remotedirectory/]filename localfile or, ftp> LS [remotedirectory/]filename localfile The format of remotedirectory/filename is dependent on the remote system implementation.
Using FTP Setting or Changing Transfer Types Setting or Changing Transfer Types FTP supports three transfer types, binary, ASCII, and BYTESTREAM. When you first enter FTP, the transfer type defaults to ASCII. For example, text files are type ASCII and are transferred as ASCII files. To find out what the transfer type is for your current session, enter the TYPE command without parameters.
Using FTP Transferring Files Transferring Files Once you have logged on to the remote host, you can transfer files from your system to the remote host, or from the remote host to your local system. Transferring Limitations The following types of MPE/iX files can be transferred to a remote host using FTP :. Standard MPE files, with fixed, variable, or bytestream format, and either binary or ASCII data types.
Using FTP Transferring MPE/iX Files to the Remote Host CAUTION If the remote file name you specify already exists on the remote host, the remote system may overwrite the existing remote file without warning. File Naming Note that other systems may support uppercase and lowercase file names. For example, if you entered the following commands and file names when connected to a UNIX system, the result would be two new remote files named RFILE and rfile.
Using FTP Transferring MPE/iX Files to the Remote Host CAT2 80B FA 800 10000 CAT3 80B FA 900 10000 CAT4 80B FA 700 10000 Transfer this group of ASCII files to the remote system: ftp> ASCII 200 Type set to A. ftp> MPUT C@ mput CAT1? Y 200 PORT command okay. 150 Opening data connection for CAT1 (15.13.132.120,63014). 226 Transfer complete. nnn bytes sent in n.nn seconds: (n.
Using FTP Transferring Remote Host files to MPE/iX NOTE The sequence of commands is repeated for each file transferred. Check that the files transferred correctly: ftp> LS C@ 200 PORT command okay. 150 Opening data connection for /bin/ls -1 (123.50.42.32,50895) (0 bytes). total nn Cat1 Cat2 Cat3 Cat4 226 Transfer complete nnn bytes sent in n.nn seconds (n.nn Kbytes/sec) Transferring Remote Host files to MPE/iX Use the GET command to copy a file from the remote host to your local MPE/iX system.
Using FTP Transferring Remote Host files to MPE/iX ASCII 80 Bytes Fixed = Default record length for a terminal screen padded with blanks. Binary 256 Bytes Fixed = Default record length for a MPE executable program file.
Using FTP Renaming Remote Files Transferring Multiple Files To transfer a group of files from the remote system to your MPE/iX system, use the MGET command. For example, transfer a group of binary files beginning with the letter “B” to your MPE/iX system. First verify the files to be transferred: ftp> DIR 200 PORT command okay. 150 Opening data connection for /bin/ls -l (123.50.42.32,50895) (0 bytes).
Using FTP Deleting Remote Files as follows: ftp> RENAME remotefile directoryname/newfile CAUTION If the new file name you specify already exists on the remote system, the remote system may overwrite the existing file without warning.
Using FTP Issuing MPE/iX Commands from Within FTP STRUCT FILE If you issue one of these commands without the option, the supported option is displayed. For example if you enter MODE, the following is displayed: ftp> MODE We only support STREAM mode, sorry. (FTPWARN 18) Issuing MPE/iX Commands from Within FTP You can enter MPE/iX commands by preceding the command name with a colon (:). The command will execute, and return you to the ftp> prompt on completion.
Using FTP Obtaining Help : append ascii binary bye bytestream case cd close debug delete dir disconnect exit exitonerror form get help lcd ls mdelete mget mkdir mode modtime mput open prompt put pwd quit quote recv remotehelp rename reset rmdir runique send site size status struct sunique system timeout trace type verbose user ? Additional help available on buildparms, ftperr#, ftpwarn#, ftpinfo# Enter the HELP command with a valid FTP user command to obtain information about individual commands supp
Using FTP Using FTP Commands in UDCs and Programs Listing the Remote FTP Server Commands The REMOTEHELP command displays the remote host supported server commands. A display similar to the following appears, (depending on the supported server commands).
Using FTP Using FTP Commands in UDCs and Programs 226 Transfer complete. 322 bytes received in 0.65 seconds: (4.25 Kbytes/second) ftp> GET filez 200 PORT command okay. 550 filez: No such file or directory. Data Transfer Request Failed. (FTPERR 13) END OF PROGRAM : :SHOWVAR ftp@ FTPLASTERR = -13 FTPXFERFILES = 0 FTPREQFILES = 0 FTPREPLACE = true FTPLASTREPLY = 550 filez: No such file or directory FTPLASTMSG = Data Transfer Request Failed.
Using FTP Using FTP Commands in UDCs and Programs Transferring Multiple Files You can create a command file to automatically copy a group of files from the remote system into your account as in the following example. 1.
Using FTP Using FTP Commands in UDCs and Programs !EOJ Programmatic Example You can use FTP commands in programs using the HPCICOMMAND intrinsic, as in the following example. The input file containing the FTP commands, FTPIN, is listed following the program.
Using FTP Using FTP Commands in UDCs and Programs In the following example, both the client (abc.cup.hp.com) and server (katsu.cup.hp.com) are MPE/iX machines. ftp>status Connected to katsu.cup.hp.com (22.11.138.29). (FTPINFO 40) Using ASCII mode to transfer files. (FTPINFO 25) Verbose mode on. (FTPINFO 22) Debugging off (debug=0). (FTPINFO 23) ExitOnError mode off. (FTPINFO 34) Interactive mode on. (FTPINFO 41) Lower case off. (FTPINFO 44) Store unique mode off. (FTPINFO 51) Receive unique mode off.
5 Using the FTP Server This chapter provides information for remote users accessing the MPE/iX FTP server and is organized as follows: • A list of user commands and the corresponding FTP server commands supported. • Sample session for a remote user accessing the FTP MPE/iX server. • More information about FTP and MPE/iX for the remote user. User command (SERVER command) DESCRIPTION ASCII (TYPE A) Sets the FTP file transfer type to ASCII. This is the default when you first enter FTP.
Using the FTP Server Transfers the remote file specified to a local file. If a local file name is not specified, the file is saved with the same name as the remote file name (assuming a legal file name). LS [remotedirectory][localfile] (NLST) Displays the contents of a remote directory, one file per line. If a localfile name is specified, the listing will be saved to the file specified. If remotedirectory is not included, the current remote working directory contents are listed.
Using the FTP Server server command is specified with the REMOTEHELP command, a brief description of the command is displayed. RENAME remotefile newname (RNFR,RNTO) Renames a remote file. RMDIR remotedirectory (RMD|XRMD) Deletes a directory from the remote machine. SITE HELP | MPE/iX | BUILDPARMS file-name | USER_LABELS filename [number] | STREAM file-name | TIMEOUT num-secs (SITE) Remote system HELP Returns a help line.
Using the FTP Server Sample FTP Session: Accessing MPE/iX [Return] key. If you enter passwords as part of the logon string, they are displayed in the message text of the password prompt. Sample FTP Session: Accessing MPE/iX The purpose of this sample session is to provide help for a remote user accessing the MPE/iX FTP server. More detailed information about FTP behavior follows the sample.
Using the FTP Server Sample FTP Session: Accessing MPE/iX 331 Guest login ok, send ident as password. Password: 230 User logged on Remote system type is MPE/IX Check the Session and Group Check the session and group you are accessing. This example shows the user logged on with the working group, MYGROUP. ftp> pwd 257 “/MYACCT/MYGROUP” is the current directory. 257 “SESS1,USER.MYACCT,MYGROUP” is the current session.
Using the FTP Server Sample FTP Session: Accessing MPE/iX 150 File LISTF opened; data connection will be opened AFILE.GROUP1 TSCREEN.GROUP1 TSCREEN2.GROUP1 NSPROG1.GROUP1 NSPROG2.GROUP1 NSPROG3.GROUP1 NPROGRAM.GROUP1 226 Transfer complete nnn bytes received in n.nn seconds (n.nn Kbytes/sec) ftp> Note that this display is different than using the LS command with no group name which displays only file names.
Using the FTP Server More Information About FTP and MPE/iX Transfer Multiple Files to MPE/iX Transfer multiple ASCII files to MPE/iX using the MPUT command: ftp> ASCII 200 Type set to A. ftp> MPUT A* If your system supports prompting, you are prompted whether or not (yes or no) to transfer each file in the selected group of files. Check that the files transferred: ftp> :DIR A@ 200 PORT command ok.
Using the FTP Server More Information About FTP and MPE/iX ftp> USER session1,username/userpass.acctname/acctpass,groupname/grouppass Press the return key when prompted for passwords. The following example shows: no session, and a password for the account only: ftp> USER myname.myacct/acctpass 331 Password required for MYNAME.MYACCT/ACCTPASS [userpass][,acctpass][,grouppass] Password: (press return) 230 USER LOGGED ON ftp> pwd 257 “/MYACCT/PUB” is the current directory.
Using the FTP Server More Information About FTP and MPE/iX Notice that only the current directory changed and not the current session. File Naming on MPE/iX The MPE/iX file system is not case sensitive: file1 is the same file as FILE1. A fully-qualified MPE/iX filename is in the form: filename.groupname.account Each part, (filename, groupname, and account) is 1–8 alphanumeric characters, beginning with an alphabetic character.
Using the FTP Server More Information About FTP and MPE/iX In the following example, using only CODE=PROG defaults to a file of fixed binary, with records of 128 words (which are the BUILD command REC= defaults).
6 MPE/iX File System and Data Transfers This chapter describes MPE/iX file system characteristics that affect how files are transferred and saved using FTP. This chapter can be useful to both MPE/iX FTP users and remote users accessing the MPE/iX FTP server and is organized as follows: • How FTP Transfers Files.
MPE/iX File System and Data Transfers How FTP Transfers Files How FTP Transfers Files Files can be transferred with FTP in ASCII mode, binary (IMAGE) mode, and BYTESTREAM mode. ASCII Transfers FTP ASCII file transfers are used primarily for the transfer of ASCII text files. The actual data transfer occurs in 8-bit NVT-ASCII representation. The receiver converts the data from the standardized transfer form to the desired target form according to the target system’s internal representation requirements.
MPE/iX File System and Data Transfers Using BUILD Parameters with FTP Using BUILD Parameters with FTP MPE/iX BUILD command parameters can be used to modify the default file building parameters for files transferred to an MPE/iX system.
MPE/iX File System and Data Transfers Using BUILD Parameters with FTP A negative value indicates record size in bytes. A positive integer value indicates record size in words (two bytes per word). If DEV= is not specified, the default record size is 128 words. blkfactor The default blkfactor size is one. When creating variable length files, include the 1 in the parameter string to maintain the record size specified in the parameter REC=.
MPE/iX File System and Data Transfers MPE/iX File System All files in the set beginning with letter “P” are created with the following attributes: file code label PROG, fixed binary, 128 word records, and a maximum number of records equal to 1,023. The blank space preceding the semicolon is required.
MPE/iX File System and Data Transfers File Transfer Examples ftp> get zfile mpefile Some records were truncated during transfer. (FTPWARN 15) The default ASCII file building parameters are fixed, 80 byte records. Since the original record size is 132 bytes, only the first 80 bytes of each record are transferred, and the remaining bytes in each record are discarded.
MPE/iX File System and Data Transfers File Transfer Examples Figure 6-1. ASCII Transfer Mixed Mode Transfer If you transfer an ASCII type file in binary mode, you may not be able to retrieve the file in its original form as pictured in Figure 6-2., “Mixed Mode Transfer,”. An MPE/iX ASCII file, AFILE, transferred to the UNIX system using FTP binary transfer mode results in a file of contiguous data on the UNIX system. Note that record structure is not maintained in binary transfers.
MPE/iX File System and Data Transfers File Transfer Examples Figure 6-2. Mixed Mode Transfer Fixed Record Files Transferring files that contain imbedded carriage return-line feed characters ( ) can be a problem if you try to transfer these files in ASCII mode. In FTP ASCII transfer mode, the remote system interprets a carriage return-line feed pair ( ) as a new record.
MPE/iX File System and Data Transfers File Transfer Examples Figure 6-3.
MPE/iX File System and Data Transfers File Transfer Examples 66 Chapter 6
7 Troubleshooting This chapter describes possible problems you may encounter and the methods you can use to troubleshoot them.
Troubleshooting Cannot Run FTP Cannot Run FTP • Did you specify the correct filename.group.account to run the FTP user program: FTP.ARPA.SYS • Check with your network administrator: The network and links must be active. Cannot Connect to the Remote Host • Did you enter the correct ARPA domain name, IP address, or NS node name? See your network administrator.
Troubleshooting File Transfer Problems At the password prompt: userpass,acctpass,grouppass or, as part of the logon string: ftp> USER sess,user/userpass.acct/acctpass,gourp/grouppass NOTE Passwords can only be entered once. For example, if the user enters the account password in the USER command string, do not re-enter it at the password prompt. File Transfer Problems For file transfer problems, first turn verbose and debug on. • Use the LS or DIR command to verify the file name spelling.
Troubleshooting Command Not Supported on Remote System 70 Chapter 7
A MPE/iX and POSIX Differences FTP/iX has the ability to access files in both the MPE/iX and POSIX (IEEE Portable Operating System Interface for Computing Environments) name space. The POSIX standards define a common portable interface to files. The following information defines access and command usage while operating in the POSIX name space environment.
MPE/iX and POSIX Differences Filename Size Restrictions Filename Size Restrictions The file reference can be either in MPE/iX or POSIX namespace. The MPE file domain consists of MPE accounts, MPE groups and files which reside in these groups.accounts. The MPE file domain is a 3 level Hierarchical File System (HFS). The POSIX file domain is considered a superset of the MPE file domain. The POSIX file domain consists of a root (/) and POSIX directories, which can contain additional directories or files.
MPE/iX and POSIX Differences Filename Size Restrictions have a maximum of 255 characters. For more information, refer to the New Features of MPE/iX: Using The Hierarchical File System Reference Manual for accepted syntax of file names and directories. Sample File Name MPE File Name Space POSIX File Name Space FILENAME FILENAME FILENAME filename FILENAME filename longfilename Invalid MPE file name longfilename Read_Me Invalid MPE file name Read_Me NOTE The file identifiers “.
MPE/iX and POSIX Differences Working With Directories Working With Directories When a user logs on as USER.ACCT,GROUP, the current working directory is initialized to /ACCT/GROUP. If a user creates a hierarchical directory through the FTP/iX MKDIR DIR1 command and then changes to that directory with the FTP/iX CD command, the new working directory will be /ACCT/GROUP/DIR1. The current working directory can be identified with the FTP/iX command PWD.
MPE/iX and POSIX Differences Working With Directories the FTP command prompt. Syntax CHGROUP [ [GROUP=]groupname] [/grouppass] Parameters groupname The name of the group to which you will be switched. If you omit this parameter, you will be switched to the home group. grouppass The password of the group you are switching to, if it is assigned a password. In a session, if the target group has a password and you fail to supply one on the command line, MPE/iX will prompt you to enter one.
MPE/iX and POSIX Differences Working With Directories :chdir /SYS/WORK CWD is “/SYS/WORK”. :SHOWME USER: #S36,MANAGER.SYS,WORK (NOT IN BREAK) :showvar hpcwd HPCWD = /SYS/WORK FTP Usage Examples Example 1: This is a sample of the operation of the POSIX current working directory “cwd” and the resulting file domain on the local system. In this example, the user on the local system, logged on as “MANAGER.SYS,PUB”, enters FTP and then executes a “:CHDIR /SYS/WORK” command.
MPE/iX and POSIX Differences Listing MPE/iX or POSIX Files Listing MPE/iX or POSIX Files Earlier versions of the MPE/iX LISTF command may not report files in the POSIX name space; the LISTFILE command must be used instead. The FTP/iX client’s LS and DIR commands provide a means to list the files on the remote host (refer to earlier sections of this manual for syntax and usage of these commands). If no file set is specified, the default is (./@).
MPE/iX and POSIX Differences Bytestream Files Bytestream Files Bytestream record formats can exist in both the MPE/iX and POSIX namespace. The purpose of this new record format is to provide an emulated file format which exists on character-oriented file systems, where the user application is responsible for defining where logical records begin and end. To create such a file, use the build parameters: ftp> put ;rec=,,b The (b) references the bytestream record type.
MPE/iX and POSIX Differences Building and Transferring a Bytestream File BYTESTRM NOTE 1B BA 1119420 2000000 1 4608 18 * The BYTESRM file contains 80 (record size) x 13820 (number of records) plus 13820 (the number of line feed (hexadecimal $0A) record terminator characters). Building and Transferring a Bytestream File These examples create a bytestream file in the POSIX shell and MPE namespace with the vi editor and then transfers that file to a remote system with FTP.
MPE/iX and POSIX Differences Building and Transferring a Bytestream File 200 PORT command ok. 150 File: LISTFILE .bytestrm,2 opened; data connection will be opened PATH= /SYS/PUB/ CODE --------LOGICAL RECORD-------SIZE 80B TYP FA EOF 38 LIMIT 2147483647 R/B 1 ----SPACE---SECTORS 16 #X 1 MX 32 FILENAME bytestrm 226 Transfer complete. 230 bytes received in 0.01 seconds (24.96 Kbytes/sec) Example 2: File transfer HPUX (unix) system to HP3000 MPE/iX system.
MPE/iX and POSIX Differences FTP Default Name Space ftp> dir ./bytestrm 200 PORT command successful. 150 Opening ASCII mode data connection for /bin/ls. -rw-r--r-- 1 jph network 35 Jun 20 16:19 ./bytestrm 226 Transfer complete. 66 bytes received in 0.18 seconds (0.37 Kbytes/sec) FTP Default Name Space FTP default name space is “almost always” MPE name space when specifying files to be transferred with FTP commands (PUT or GET as examples).
MPE/iX and POSIX Differences Transferring Files only the filename (not the full path) needs to be specified. Example 1: This example demonstrates a FTP data transfer from a file in a MPE group to a POSIX directory. :listf testdata,2 ACCOUNT = SYS FILENAME CODE TESTDATA SIZE 80B GROUP= WORK --------LOGICAL RECORD-------TYP FA EOF 13820 LIMIT 13820 ----SPACE---- R/B 16 SECTORS 4304 #X 1 MX * ftp> pwd 257-“/SYS/WORK” is the current directory. 257 “,MANAGER.SYS,WORK” is the current session.
MPE/iX and POSIX Differences Transferring Files ftp> :showvar HPCWD HPCWD = /SYS/WORK/temp2 ftp> :SHOWME USER: #S6,MANAGER.SYS,PUB (IN PROGRAM) ftp> PWD 257-”/SYS/WORK/temp” is the current directory. 257 “,MANAGER.SYS,WORK” is the current session. ftp> DIR 200 PORT command ok. 150 File: LISTFILE .
MPE/iX and POSIX Differences Transferring Files else FTP will attempt to fit the file in the MPE file space and fail, as in the following examples: Example 4: ftp> put TESTDATA long_file_name2 200 PORT command ok. 550 An invalid character was found in an MPE syntax name. (FILE SYSTEM ERROR -102) Data Transfer Request Failed. (FTPERR 13) Example 5: ftp> put TESTDATA longfilename12 200 PORT command ok. 500 The file name specified exceeds the maximum legal length.
B Error Messages This appendix contains messages and errors that may be received if you are using FTP to access another host or an FTP server.
Error Messages FTP User Messages and Errors FTP User Messages and Errors These error and warning messages may be returned to FTP users on MPE/iX while using the FTP user program. In the following list of messages and errors, the exclamation point (!) represents a variable value. (FTPERR 3) MESSAGE: Error in loading keywords from FTP catalog. CAUSE: The User-FTP program encountered an error while trying to load the FTP command keywords onto its program stack from the FTP catalog.
Error Messages FTP User Messages and Errors CAUSE: An error was detected during a data transfer. This error is accompanied by another error which indicates the problem. ACTION: Use the accompanying error to resolve the problem. (FTPERR 14) MESSAGE: Target File Could Not Be Opened. CAUSE: The MPE/iX target file could not be opened. This error is typically accompanied by a file system error. ACTION: Use the accompanying file system error to resolve the problem.
Error Messages FTP User Messages and Errors CAUSE: The FTP VERBOSE command was entered when verbose was disabled. ACTION: None. (FTPINFO 23) MESSAGE: Debugging off (debug=0). CAUSE: The FTP DEBUG command was entered when debug was enabled. ACTION: None. (FTPINFO 24) MESSAGE: Debugging off (debug=1). CAUSE: The FTP DEBUG command was entered when debug was disabled. ACTION: None. (FTPINFO 25) MESSAGE: Using ascii mode to transfer files.
Error Messages FTP User Messages and Errors (FTPERR 32) MESSAGE: Remote server received timeout. Closing connection. CAUSE: The FTP user did not receive a required reply from an FTP server in the allocated time window. ACTION: Close the connection and quit before trying again. Try to ping the remote system using PING.NET.SYS. If this does not succeed, no FTP connection can be established.
Error Messages FTP User Messages and Errors CAUSE: A connection request to a remote FTP server was accepted. ACTION: None. (FTPINFO 41) MESSAGE: Interactive mode on. CAUSE: The PROMPT command was issued while prompting was disabled. ACTION: None. (FTPINFO 42) MESSAGE: Interactive mode off. CAUSE: The PROMPT command was issued while prompting was enabled. ACTION: None. (FTPINFO 43) MESSAGE: Lower case on. CAUSE: The CASE command was issued while “Forcing Lower Case” was disabled. ACTION: None.
Error Messages FTP User Messages and Errors (FTPINFO 50) MESSAGE: Store unique mode on. CAUSE: The FTP sunique command was entered when store-unique was disabled. ACTION: Subsequent put commands will guarantee that the file will be created with a unique name on the remote machine. (FTPINFO 51) MESSAGE: Store unique mode off. CAUSE: The FTP sunique command was entered when store-unique was enabled. ACTION: None. (FTPINFO 52) MESSAGE: Receive unique mode on.
Error Messages FTP User Messages and Errors (FTPINFO 60) MESSAGE: Using byte-stream mode to transfer files. CAUSE: The FTP type command was entered without any parameters while in byte-stream mode. ACTION: None. (FTPINFO 61) MESSAGE: Unique file name cannot be created. CAUSE: Either the file name was so long that appending (.1) surpassed the maximum legal file name length, or every appendage from (.1 up to .99) was tried and no unique name could be found.
Error Messages FTP Server Messages and Errors FTP Server Messages and Errors FTP users accessing an MPE/iX-based FTP server may receive the messages and/or errors listed below which are based on the Military Standard, FTP, MIL-STD-1780.
Error Messages FTP Server Messages and Errors 202 MESSAGE: Command not implemented at this site. CAUSE: The MPE/iX FTP server received a command that is not implemented. ACTION: This command cannot be used. 213 MESSAGE: “!”: !. CAUSE: A file status (SIZE | MDTM) command was received and accepted. This first parameter is the filename. The second contains detailed information that differs depending on the command. ACTION: None. 215 MESSAGE: MPE/iX system type. CAUSE: The server received a SYST command.
Error Messages FTP Server Messages and Errors CAUSE: A PWD command was received and accepted. ACTION: None. 257 MESSAGE: ! successful, “!” created CAUSE: A directory creation (MKD/XMKD) has completed. ACTION: None. 331 MESSAGE: Password required for !. [userpass][,acctpass][,grouppass] CAUSE: A USER command has been received, the server is waiting for the password. ACTION: Enter the passwords required. 350 MESSAGE: File exists, ready for destination name.
Error Messages FTP Server Messages and Errors ACTION: Specify a parameter which is supported. 530 MESSAGE: User log on unsuccessful CAUSE: The server received a user account and/or password which were not valid. ACTION: Specify the correct user account and password. If the user is sure that they are correct, notify the network manager and have him/her refer to the Installing and Managing HP ARPA File Transfer Protocol Network Manager’s Guide. 530 MESSAGE: Please login with USER and PASS.
Glossary A address A numerical identifier defined and used by a particular protocol and associated software to distinguish one node from another. address resolution In NS networks, the mapping of node names to IP addresses and the mapping of IP addresses to subnet addresses. See Also: probe protocol, ARP. ARP Address Resolution Protocol. ARP provides IP to LAN station address resolution for Ethernet nodes on a LAN. ARPA Advanced Research Projects Agency.
connection. E environment A session that is established on a remote node. Ethernet Local Area Network system that uses baseband transmission at 10 Mbps over coaxial cable. Ethernet is a trademark of Xerox Corporation. F file equation Assignment statement used to associate a file with a specific device or type of device during execution of a program. file system The part of the operating system that handles access to input/output devices, data blocking, buffering, data transfers, and deblocking.
identifies a node within the network. L loopback The routing of messages from a node back to itself. M MPE/iX The operating system for the HP 3000 Series 900 computers. N network address This can be either 1) the network portion of an IP address as opposed to the node portion, or 2) when referring to X.25 networks, it is a node’s X.25 address. network directory A file containing information required for one node to communicate with other nodes in 1) an internetwork, 2) an X.
privileged mode A capability assigned to accounts, groups, or users allowing unrestricted memory access, access to privileged CPU instructions, and the ability to call privileged procedures. probe protocol An HP protocol used by NS 3000/iX IEEE 802.3 networks to obtain information about other nodes on the network. It provides name to IP address resolution, and IP to IEEE 802.3 address resolution. protocol A set of rules that enables two or more data processing entities to exchange information.
Index Symbols ? user command, 17 A APPEND user command, 17 ARPA services, 12 ASCII user command, 17 ASCII command, 32 ASCII transfers, 58 attributes default file, 36 B BINARY user command, 17 BINARY command, 32 binary transfers, 58 BUILD command, 37, 59 BUILD parameters, 59 BYE user command, 17 BYTE user command, 18 BYTE command, 32 BYTESTREAM user command, 18 BYTESTREAM command, 32 bytestream transfers, 58 C CASE user command, 18 CASE command, 20, 35 CD server command, 47 user command, 18 CD command, 34 c
Index MGET, 19 MKDIR, 19 MODE, 19 MODTIME, 19 mpecommand, 17 MPUT, 20 NONPRINT, 18 num-secs, 22 OPEN, 20 PROMPT, 20 PUT, 20 PWD, 20 QUIT, 20 QUOTE, 20 RECV, 20 REMOTEHELP, 20 RENAME, 20 RESET, 21 RMDIR, 21 RUNIQUE, 21 SEND, 21 SITE, 21 SIZE, 21 STATUS, 21 STREAM, 19 STRUCT, 21 subject, 17 SUNIQUE, 21 SYSTEM, 21 TIMEOUT, 22 TRACE, 22 TYPE, 22 USER, 22 VERBOSE, 22 G GET user command, 18 GET command, 20, 25, 36, 52 H hardware links, 13 HELP server command, 49 user command, 19 HELP command, 17, 19, 40 I IMAGE
Index server command, 48 STREAM user command, 19 STRU server command, 49 STRUCT user command, 21 SUNIQUE user command, 21 SYSTEM user command, 21, 49 T TIMEOUT user command, 22 TRACE user command, 22 transfer files, 33, 37 transfer multiple files, 38 transferring files, 34 trnasfer types ASCII, 32 binary, 32 BYTESTREAM, 32 TYPE server command, 47, 49 user command, 22 TYPE command, 32 U UDC, 42 USER server command, 49 user command, 22 user account, 54 USER command, 29 User Defined Commands (UDC), 42 V VERBO
