2.2.1 FTAM Responder Log File
OpenVMS On OpenVMS, when the FTAM responder is activated, a log file is created in the home directory of the user specified by the FTAM operation. The name of the log file is OSIF$RESPONDER.LOG.
The OSIF$RESPONDER.LOG log file contains any errors that may be generated by the FTAM responder. It also contains a list of all files that are accessed by an F-OPEN-REQUEST, including the processing mode of the access.
You can use the OSIF$RESPONDER.LOG file to check the status of an FTAM operation. For example, issue the following FTAM command on an OpenVMS system to another OpenVMS system, amiguita:
$ copy/app=ftam test.dat amiguita"fencer thrust"::test.dat
On system amiguita, in the home directory of userfencer, there is an OSIF$RESPONDER.LOG file corresponding to the operation that you can use to check on the status of thecopy command. ♦
2.2.2 Copying Files
The copying facility allows you to copy a single input file to a single output file, within or between FTAM systems.
The FTAM copying facility operates on any combination of local-to-remote files, remote-to-local files, and remote-to-remote files. However, local-to-local file copies are only supported by the OpenVMScopycommand.
OpenVMS On OpenVMS, thecopy command has the following format:
copy/app=ftam [/qualifier(s)] input-file-spec [,...] output-file-spec
The following example copies the single local file test.datto \dir\fileon
amiguita:
$ copy/app=ftam test.dat amiguita::"\dir\file" Return
Note that without the double quotation marks (" ") enclosing \dir\file, RMS would generate the following error:
%COPY-F-OPENIN, error opening AMIGUITA::\DIR\FILE as input -RMS-F-SYN, file specification syntax error
For a complete description of the copy command and its qualifiers, see Appendix A.♦
UNIX On Digital UNIX, theocpcommand has the following format:
ocp [options...] [application-address::]file1 [application-
address::]file2
The following example copies the local Digital UNIX file test.datto an OpenVMS file called test.dat;25onlesamies.
% ocp test.dat lesamies::’test.dat;25’ Return
Note that because the output-file designation is enclosed in single quotation marks (’), the characters entered in the command are retained in the output-file designation sent to the remote FTAM system.
For a complete description of theocp command and its options, see Appendix B. ♦
2.2 FTAM Commands
2.2.2.1 Copying FTAM-2 Document Types
OpenVMS FTAM maps an RMS file to a single FTAM document type, based on the record format and record attributes of the RMS file. In previous versions of FTAM, if the responding FTAM implementation did not support the abstract syntax required for our FTAM document type, the file could not be transferred. This situation was seen most commonly when the copycommand attempted to transfer an RMS file with a variable record format (which FTAM maps to the FTAM-2 (sequential text file) document type) to an implementation that cannot support the FTAM-2 document type.
If this situation occurs with FTAM, the FTAM initiator automatically attempts to transfer the local FTAM-2 file to the responder as an FTAM-1 (unstructured text file) document type and FTAM sends you an informational message that the file was transferred as an FTAM-1 file.
For more information on FTAM document types, see Section 7.2.2.6. For specific information on the relationship of RMS files to FTAM document types, see Appendix E.♦
2.2.2.2 Copying Files With Records Larger Than 7168 Bytes
Due to the size restrictions specified in NIST Phase 2 and Phase 3 agreements and ISO/IEC ISP 10607-3, you cannot send files using FTAM with fixed-length records longer than 7168 bytes, because fixed-length records cannot be segmented. Before you can send such a file using FTAM—for example, an OpenVMS save set that has a block size greater than 7168 bytes—you must first unwind the file and rewind it with a block size of less than 7168 bytes.
2.2.2.3 Copying FTAM Files
UNIX On Digital UNIX, other options of the ocp command let you specify certain properties specific to FTAM files. For example, to copy an FTAM file with the properties of a particular document type, you can use a command that resembles the following:
% ocp -D FTAM-1 -C General -M 512 petrie::ftam.tst ftam.txt Return
This command specifies that the source file is to be opened as an FTAM-1 file with a universal class number ofGeneralString and a maximum string length of 512. The characteristics you specify must match those of the source file. This command also specifies that the destination file is created with the same attributes as the source file.
Note
The FTAM responder on Digital UNIX does not properly handle any attempt to transfer a non-fixed record length file as a fixed length. ♦
2.2.2.4 Copying Files with Confirmation
OpenVMS If you want the system to query you about copying files when using the copy command, use the /confirmoption with your command, as in the following example:
$ copy/confirm/app=ftam test.dat amiguita::"\dir\file" Return
COPY TEST.DAT to AMIQUITA::"\DIR\FILE"?
If you typeyand press Return, the output file is copied. Otherwise, the file is not ♦
2.2 FTAM Commands
UNIX On Digital UNIX, if you want the system to query you about overwriting existing files when using the ocpcommand, use the-ioption with your command, as in the following example:
% ocp -i petrie::’user2:[ami]ftam.tst’ ftam.txt Return
ocp: overwrite ftam.txt?
If you type yand press Return, the output file is overwritten. Otherwise, the file is not copied. ♦
2.2.2.5 Copying Files With No Output File-Designation
OpenVMS On OpenVMS, you may copy a local file to a remote FTAM system without specifying the file-designation on the output-file-spec. This use of the copy
command has one of the following formats:
copy/app=ftam [/qualifier(s)] input-file-spec[,...] appl-address::
copy/app=ftam [/qualifier(s)] input-file-spec[,...] appl-address"initiator-id password account":: For example:
$ copy/app=ftam ftam.txt amiguita::
The name of the file that is created on the remote FTAM system is the same as the name of the local file to be copied (FTAM.TXT in this example). Note that if the remote FTAM system is case-sensitive (for example, a Digital UNIX system), the remote file name is in uppercase even if you typed it in lowercase because OpenVMS file names are always uppercase. ♦
2.2.3 Appending Files
The FTAM append facility can append multiple input files together to form a new output file through concatenation. Concatenation takes each input file in its input order and appends its contents to the end of the output file. The output file is a new file.
The append facility also allows you to append an input file to a single output file, and concatenate two or more input files to a single output file. (When using FTAM on a Digital UNIX system, the output file must be local.)
OpenVMS On an OpenVMS system, if the output-file designation identifies an existing local file, the new output file receives the next highest version by default. ♦
UNIX On a Digital UNIX system, the new output file overwrites the existing file. When concatenating to a remote output file, the effect of specifying an existing remote file name depends on the file management procedures of the remote operating system. ♦
Concatenation primarily affects three RMS file attributes: file organization, record format, and record attributes. Use the directorycommand to display these attributes for any local or remote file (see Section 2.2.5). Taken together, these RMS file attributes equate to an FTAM file attribute called contents type. During concatenation, the appending facility monitors the contents type of the first input file to determine the contents type of the output file. If the input- file list begins with a wildcard file designation, the output contents type is determined by the file whose file specification is first alphabetically. Note that using wildcards for the local input file succeeds only if the local file designation is compatible with the file-designation format of the remote system. (For an explanation of wildcards, see Section 2.1.1.5.)
2.2 FTAM Commands
OpenVMS On OpenVMS, theappendcommand has the following format:
append/app=ftam [/qualifier(s)] input-file-spec [,...] output-file-spec
The following example appends the input file,^vol>main>file.ext, fromfreunde, and the local input file,test.dat(assuming the files have a single contents type), into the local output file, largetest.dat:
$ append/app=ftam/new_ver freunde::"^vol>main>file.ext",- Return
_$ test.dat largetest.dat Return
Note that without the double quotation marks (" ") enclosing the file designation
^vol>main>file.ext, DCL interprets the symbol ^ as a parameter delimiter and generates the following error:
%DCL-W-PARMDEL, invalid parameter delimiter - check ... \^VOL\
For a complete description of the appendcommand and its qualifiers, see Appendix A. ♦
UNIX On Digital UNIX, theocatcommand has the following format:
ocat [options...] application-address::file [application-
address::file...]
The following example displays and appends the contents of the remote file,
/usr/user1/file1, on freunden, to the local filefile2 on the local standard output:
% ocat freunden/fencer/thrust::/usr/user1/file1 > file2 Return
Note the use of user name fencer, and passwordthrustin the application address of the remote Digital UNIX responder.
The contents of remote files can only be appended by redirecting the output to a local file. You must specify whatever type of information the remote FTAM system requires for specifying files. (Refer to the user documentation for the remote FTAM system.)
For a complete description of the ocat command and its options, see Appendix B.♦
2.2.3.1 Concatenating with the copy Command
OpenVMS The copying facility can also concatenate input files that have an identical contents type to an output file with the same contents type. This is similar to the append facility described in Section 2.2.3. For input files with non-identical contents types, the concatenated output file has the contents type of the first input file. With non-identical contents types, a warning message occurs that informs you of the incompatible attributes.
To concatenate files with the copy command, you must use the /concatenate
qualifier, as in the following example:
$ copy/concatenate/app=ftam *.dat freunde::newfile.dat Return ♦
2.2.3.2 Appending Files with the ocp Command
UNIX On Digital UNIX, theocp command has a -Aoption that allows you to append files within or between FTAM systems. For example, you might use the following command to append the remote file ftam.tstto the local fileftam.txt: