Bull DPX/20 Unified File Transfer (UFT) Reference Manual AIX ORDER REFERENCE 86 A2 10CB 03
Bull DPX/20 Unified File Transfer (UFT) Reference Manual AIX Software March 1996 Bull Electronics Angers S.A.
The following copyright notice protects this book under the Copyright laws of the United States and other countries which prohibit such actions as, but not limited to, copying, distributing, modifying, and making derivative works. Copyright Bull S.A. 1992, 1996 Printed in France Suggestions and criticisms concerning the form, content, and presentation of this book are invited. A form is provided at the end of this book for this purpose.
About This Book This manual describes how to install UFT (Unified File Transfer) on DPX/20 systems. It describes in detail the inter-operation of the DPX/20 with other similar systems and with non-DPX systems. The non-DPX systems covered in this manual are the Bull DPS 6, DPS 7, DPS 8, and IBM systems. Audience This manual is intended for UFT users in a networking environment comprising DPX/20 systems. Operating System Level This document is at Revision 2 level, which applies to AIX Version 4.1.
Reading this Appendix is an absolute prerequisite before transferring NFS files. Appendix F UFT API Programming Example Appendix G Remote Hosts Table Glossary Index Conventions Used in This Document The following typographic conventions are used in this document: Bold Bold characters are used to highlight key words, commands and subroutines. Italic Italic characters represent file names and user supplied values.
Table of Contents Chapter 1. UFT Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Structure of UFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UFT Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi UFTinit() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UFTconnect() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UFTdisconnect() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UFTsend() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 1. UFT Introduction Overview UFT (Unified File Transfer) is an application for transferring files between a DPX/20 and: • either another DPX/20 or a DPX/2, • or a non DPX system such as a DPS 6, DPS 7, DPS 8 or IBM system. The two systems can be connected through: • either an X25 Wide-Area Network (public or private WAN) • or an Ethernet (normal or integrated LAN), an FDDI or a Token Ring Local Area Network.
Structure of UFT The UFT product includes a configurator, several commands and subcommands, requestor and server programs, and APIs. The UFT commands are initiated by: • either a user, • or an application. and are executed: • either interactively, • or from an input command file. The UFT service itself is composed of two processes: • a requestor (client) process: The requestor process executes UFT commands locally initiated. For file transfer commands, this process sends and/or receives files.
Running Environment of UFT The environment in which UFT can run must provide: • the OSI communications stack, • and one of the supported communications adaptors. See OSI Services Reference Manual. The UFT environment is shown in the following Figure. User application UFT API UFT server UFT client User Environment Application Kernel Environment COSP = SESSION NetShare COTP = TRANSPORT CLNP/ES–IS Operating System LLC–1 TCP IP OSI Driver Operating System Lan Drivers Operating System Wan Drivers X.
Files Processed by UFT Types of Files Processed by UFT Files locally processed by UFT are of two types, namely: • byte stream files such as binary files which consist of a stream of unstructured bytes, • sequential files such as text files which are organized as variable length records where each line corresponds to a file record.
File Name Structure The structure of file names specified by UFT must be the same as the file name structure prevailing on each system. For non DPX systems such as the DPS 7 and DPS 8, see Appendix B File Identifiers on Non DPX Systems. For DPX systems, the UFT service imposes the following structure: [label(dirname(]filename where: label the label of the disk or partition (virtual disk) on which the file resides but which has not been mounted.
1-6 UFT Reference Manual
Chapter 2. UFT User Subcommands Overview This section lists and describes the user subcommands that can be executed under UFT. • Subcommands are first described briefly in alphabetical order, in “List of UFT Subcommands”, on page 2-2, • Subcommands are then covered in detail in the uft command, on page 2-3, • Commands are briefly described in “User Tasks”, on page 2-15, in particular how to connect to a remote host, transfer a file, request information on the connection, exit UFT, etc.
List of UFT User Subcommands The following commands available under UFT are given in alphabetical order. cd Changes the current directory of the local system under UFT. cfile Executes a sequence of UFT commands. cmp [on | off] Compresses data prior to transfer. cmp Displays the current status of the compress mode. connect Sets up a UFT service connection (alias open). create Creates the remote_file on the remote host. CTRL C Aborts the current file transfer.
uft uft Command Purpose Transfers files between a local and a remote host. Syntax uft –t trace_level –n output_file Description The uft command is need to transfer files between a DPX/20 and: • either another DPX/20 or a DPX/2, • or a non–DPX system such as a DPS 6, DPS 7, DPS 8 or IBM system.
uft The command uft –n
uft On starting UFT, the user is in the current directory. When connecting to a remote host, the user is in the directory of the local login chosen during connection. The local_directory can be changed using the command cd at any time. If local_directory is omitted, the user is: • either in the directory of the local login used to set up the current UFT connection, • or in the directory of the user login if there is no current UFT connection.
uft connect remote_host Opens a UFT service connection with the remote_host. The remote_host must have been declared in the table /etc/isohosts. See “Remote Host Access Table” on page 4-5.
uft by using the modify command, in which case the last parameter setting prevails. UFT only manages one connection at a time. To converse with another system, first disconnect from the current system before entering another connection request. See “Disconnecting from Remote Host” on page 2-15. Once the connection request is accepted, the user’s access rights are those of the selected local login.
uft Return Values If an error occurs, the reason for failure to delete is displayed. See “Error Messages” on page A-1. disc Disconnects from the remote host. Return Values If an error occurs, a message is displayed. See “Error Messages” on page A-1. exit Quits UFT and closes the connection to the remote host. ga remote_file Gets information about the remote_file on the remote host. Same as the readatt subcommand. get remote_file ap local_file Transfers a file from the remote host to the local system.
uft rcdir local_directory [from remote_directory] Receives the contents of all files from the remote_directory that already exist in the local_directory. Note: This command refers to a file system specific to DPX systems and can be used only where both systems belong to this family. A recursive search is performed for the file names in the local directory. The list of files to be received is therefore based on this search in the local directory.
uft Return Values If an error occurs, a message is displayed. See “Error Messages” on page A-1. receive remote_file [ap local_file|as local_file] Transfers a file from the remote host to the local system. receive remote_file ap local_file transfers a file from the remote host to the local system. The file received is concatenated to the local file. receive remote_file as local_file transfers a file from the remote host to the local system. By default, the name of the local file is remote_file.
uft When this command is invoked without any arguments, a summary of all user interrupted transfers is displayed. This information is given in the following format: line 1: transfer_id transfer_mode record_size remote_site_and_user line 2: original_transfer_command line 3: number_of_blocks/records_transferred A transfer can be restarted only if the user is connected as the remote user at the time of transfer interruption. A restarted transfer can be further interrupted and resumed.
uft The different error messages returned on a failed restart are described in “Error Messages” on page A-1. sd local_directory [in remote_directory] Transfers all the files from the local_directory to the remote_directory. Same as the sndir subcommand. send local_file [ap remote_file|as remote_file] Transfers a file from the local system to the remote host. send local_file ap remote_file transfers a file from the local system to the remote host. The file sent is concatenated to the remote file.
uft SHELL=/bin/ksh export SHELL UFT then uses korn–shell each time shell is invoked. sndir local_directory [in remote_directory] Transfers all the files from the local_directory to the remote_directory. Note: This command refers to a file system specific to DPX systems and can be used only where both systems belong to this family. It sends the contents of all files in the local_directory to the remote_directory. A recursive search is performed for file names in the local directory.
uft Sending /tmp/file1 as /tmp/file_on_dorade Transfer Identification : 171783280 Transferred Size : 280 Kbytes The value of the Transferred Size field changes dynamically as the transfer progresses. who Displays the characteristics of the current connection from the local point of view.
User Tasks This section contains a brief description of each command that can be executed under UFT. Connecting to a Remote Host connect remote_host (alias open) This command opens a UFT service connection with the remote_host. Compressing Data for Transfer cmp [on | off] This command compresses data prior to transfer. Modifying Characteristics of Current Connection modify This command modifies certain connection characteristics set at the time of the last connect or modify.
Sending a Directory to a Remote Host sndir local_directory [in remote_directory] (alias sd) This command refers to a file system specific to DPX systems and can be used only where both systems belong to this family. Receiving a Directory from a Remote Host rcdir local_directory [from remote_directory] (alias rd) This command refers to a file system specific to DPX systems and can be used only where both systems belong to this family.
Automation of UFT Connection and Transfers This section describes the three methods for running automatic file transfers under UFT, either by using the cfile command, or by a direct call to the transdiff command, or by starting uft with the option –n. Only the first two commands enable deferred execution. cfile Command cfile file [at] The cfile command runs, from file, a sequence of UFT commands concerning transfers, creation, file deletion and attribute acquisition, once connection is established.
RLIMIT_STACK=65536 RLIMIT_CORE=2048 RLIMIT_RSS=65536 UMASK=22 USRENVIRON:_=/usr/bin/at LANG=Fr_ FRNLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls /msg/prime/%N PATH=/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin /X11:/sbin LOGNAME=root MAIL=/usr/spool/mail/root LOCPATH=/usr/lib/nls/loc USER=root DISPLAY=dpx2153:1 SHELL=/bin/ksh ODMDIR=/etc/objrepos HOME=/TERM=xterm MAILMSG=[YOU HAVE NEW MAIL] PWD=/TZ=NFT–1A_z=! LOGNAMESYSENVIRON:NAME=root TTY=/dev/pts/0 LOGNAME=root LOGIN=rootumask 022 cd/ /usr/bin/transdiff /usr/sp
4. local user password 5. user name for remote machine accepting connection 6. remote user password 7. account number: DPS information 8. project name: DPS information 9. record size 10.transfer mode (1: block mode; 2: line mode; default: 1) 11. remote machine type: (1:DPX; 2:DPS 8; 3:DPS 7; 4:DPS 6; 5:OTHER) 12.
cd / readatt /tmp/test Name of file: Current size: Record size: File organization: Record format: Max file size: Creation date time: Last retrieval date time: Last modification date time: /tmp/test 35713K bytes 2560 bytes sequential variable 35713K bytes 1992 10 06 at 10:59 GMT 1992 10 06 at 10:44 GMT 1992 10 06 at 10:59 GMT send /etc/isohosts as /tmp/test Transfer identification: Transfer duration: Transfer traffic: 1419408883 2 seconds 0.
Execution of the above command produces the following result file: result_file= /tmp/resul: uft>co auber Local login: Local password: Remote login: Remote Password: Remote Billing: Remote Project: Max record size (0:your choice; 1:512; 2:950; 3:2000; default: 512): Enter max record size (between 1 and 16384): Transfer mode (1:block mode; 2:line mode; default:1) Remote machine type (1:DPX: 2:DPS8;3:DPS7; 4:DPS6: 5:OTHER; default:1): Create command: available Delete command: available Readatt command: availab
uft>who You are connected to site: Local login: Remote login: Max record size: Transfer in mode: Remote machine: Verbose mode: Compression mode: No abort mode: Trace: Trace level: Trace file: The current directory is: / uft>clos uft>ex 2-22 UFT Reference Manual auber root telecom 1024 block DPX off off off off 0 –
Chapter 3. Access to Non DPX Systems Overview UFT offers the capability of connecting DPX systems to non–DPX systems such as the DPS 6, DPS 7 and the DPS 8 via an X25 network (public or private), an Ethernet local area network (RLE3), an FDDI network or a Token Ring.
Connection to Non DPX Systems To establish the connection with a non DPX system, use the command connect followed by the name of the remote host. The name of the remote host must be declared in the table /etc/isohosts. See “Installation and Configuration”, “Prerequisites” on page 4-3. The login, password, billing and project codes of the remote host must be declared with the necessary access rights in the DPS 6, DPS 7 and DPS 8 system catalogs.
Link With the DPS 7 Once connected to the remote DPS 7, any sequence of UFT commands can be submitted. Types of DPS 7 Files Recommended for Transfers On DPX systems, UFT only processes files in byte stream or sequential organization. See “Types of Files Processed by UFT” on page 1-4. To ensure compatibility, files recommended on the DPS 7 are: • SL source library or BIN binary library • UFAS sequential files on disk with variable format records.
Binary File Transfers with the DPS 7 Binary file transfers on the DPS 7 use: • either a BIN library: • or a UFAS sequential disk file with variable format records. When connecting to the remote host: • select block mode: – to transfer data in binary code, – and to enable the data to be grouped into blocks when received on DPX systems, and vice versa.
Link With the DPS 8 During UFT connection, the DPS 8 does not check the password given. When the DPS 8 is the requestor, the user name must not contain lower case letters and the user must not have a password because GCOS 8 cannot send lower case letters or passwords. Therefore, the DPS 8 cannot be the requestor when UFT is running on a C2 secure AIX which requires lower case user names and passwords. This section only deals with create, delete and file transfer commands.
Deleting Files on the DPS 8 with UFT The command delete erases a file on a remote DPS 8. Example: delete 74502/TRANS/FIC$PASS Text File Transfers with the DPS 8 When connecting to the remote host: • select line transfer mode to ensure that the file is transmitted in lines due to incompatibility of file structures, • select the maximum size of transfer records taking into account that max_record_size must be less than or equal to the maximum size (1272 bytes) of a GFRC sequential disk file record.
Link With IBM Systems Once connected to the remote IBM system, a sequence of commands authorized within the connection can be submitted. The remote IBM system must be running the UFTF (Unified File Transfer on a Foreign Host) application. For the IBM system, type in the value OTHER at remote machine type prompt of the connect and modify commands. The IBM system does not check the password given during the UFT connection.
Link With the DPS 6 Once connected to the remote DPS 6 system, a sequence of UFT commands can be submitted. If the DPS6 software release is not HVS2.20 or later, the DPS 6 string relative file is left in the DAMAGE state if the length of the last file record is null. Types of DPS 6 Files Recommended for Transfers On DPX systems, UFT only processes files in byte stream or sequential organization. See “Types of Files Processed by UFT” on page 1-4.
• select the maximum size of transfer record taking into account that: – max_record_size must be less than or equal to the record size of the file on the DPS 6 – DPX adjusts the record size to the characteristics of the file on the DPS 6. The receiving file must exist on the DPS 6 before the transfer. Binary File Transfers with the DPS 6 Binary file transfers on the DPS 6 use UFAS sequential files with datacode UNKNOWN.
3-10 UFT Reference Manual
Chapter 4. Installation and Configuration Overview This section describes how to prepare the files and tables specific to UFT and how to startup UFT. For installing UFT and the OSI communications stack refer to How to Install the OSI Stack, in OSI Services Reference Manual. UFT installation is detailed in the following sections: • Package Contents, on page 4-1. • License Control, on page 4-1. • Installing UFT, on page 4-3. • Configuring UFT, on page 4-4. • Managing Remote Sites, on page 4-5.
UFT License Control Implementation UFT Requester The local Nodelock key is tested when the uft process is started and at each connection command. Once an outgoing connection has been accepted it cannot be ended by uft if the license becomes unavailable. If the UFT Nodelocke license is not available, an error message similar to the following is displayed: License Request Nodelocked: License not found in database In the event of a NetLS error, the uft process stops running.
Installing UFT Prerequisites Software The following OPPs (Optional Program Products) must be installed prior to installing UFT: • bos.rte, version 4, revision greater than 0 • osi_high.rte and its prerequisites. Disk To install the LPP (Licensed Program Product), the disk space required is 2 Mbytes. Procedure General All LPPs are installed using SMIT (System Management Interface Tool).
Configuring UFT UFT configuration is performed in three steps: • Configuring the Communications Stack (mandatory), • Configuring NetShare (for NetShare sites only), • Managing remote sites. Configuring the Communications Stack To use the SMIT configurator, refer to “OSI Stack Configuration”, in OSI Services Reference Manual. The number of simultaneous incoming and outgoing connections is not limited by UFT.
Managing Remote Sites Enter the SMIT Configuration Tool Note: Some menus contain multiple choice parameters (a + character is displayed at the right side of the parameter). Use Esc+4 to display the list. Enter the following command: smit if you are using an X terminal, smit –C if you are using an ASCII terminal. The first menu which appears using the smit –C command is: System Management Move cursor to desired item and press Enter.
Select the ’Unified File Transfer (UFT)’ item and Press Enter. Fastpath = smit [–C] uft Unified File Transfer (UFT) Move cursor to desired item and press Enter. Installation Start UFT Stop UFT Restart Information Log Utilities F1=Help Esc+9=Shell F2=Refresh Esc+0=Exit F3=Cancel Enter=Do Esc+8=Image Select the ’Installation’ item and Press Enter. Installation Move cursor to desired item and press Enter.
Adding an Ethernet Remote Site After selecting the ’Add ETHERNET site entry in /etc/isohosts’ item in the ’Add site entries in /etc/isohosts’menu, the following menu appears. Add an ETHERNET site entry in /etc/isohosts Type or select values in entry fields. Press Enter AFTER making all desired changes.
Adding an X25 Remote Site After selecting the ’Add X25 site entry in /etc/isohosts’ item in the ’Add site entries in /etc/isohosts’menu, the following menu appears. Add an X25 site entry in /etc/isohosts Type or select values in entry fields. Press Enter AFTER making all desired changes.
Adding a FULL–IP or NULL–IP Remote Site After selecting the ’Add FULL–IP or NULL–IP site entry in /etc/isohosts’ item in the ’Add site entries in /etc/isohosts’menu, the following menu appears. Add FULL–IP or NULL_IP site entry in /etc/isohosts Type or select values in entry fields. Press Enter AFTER making all desired changes.
Adding a NETSHARE Remote Site After selecting the ’Add a NetShare site entry in /etc/isohosts’ item in the ’Add site entries in /etc/isohosts’menu, the following menu appears. Add a NETSHARE site entry in /etc/isohosts Type or select values in entry fields. Press Enter AFTER making all desired changes.
Activating UFT UFT can be started in one of the following ways: • using SMIT • manually by entering /etc/rc.uft. • automatically Starting UFT Using SMIT Enter the SMIT Configuration Tool Fastpath = smit [–C] uft, select ’Start UFT’. 1. Select the Communications Applications and Services item and Press Enter, 2. Select the Unified File Transfer (UFT) item and Press Enter. Select ’Start UFT’ item and Press Enter.
The trace level specified can be –l0 or –l1 or –l2 or –l3; level 0 is the default. The meaning of these trace levels is as follows: l0 no trace. l1 only error messages and internal exchanges are traced. l2 error messages and calls to the communication stack are traced. l3 full trace level, includes dump of data exchanges, functional calls, etc. The trace filename, if specified by the user stores trace log information.
Deactivating UFT UFT can be stopped in one of the following ways: • using SMIT • manually on entering /etc/rc.uft stop. Stopping UFT Using SMIT Enter the SMIT Configuration Tool Fastpath = smit [–C] uft 1. Select the Communications Applications and Services item and Press Enter, 2. Select the Unified File Transfer (UFT) item and Press Enter. Select ’Stop UFT’ item and Press Enter. After selecting the ’Stop UFT’ item in the ’Unified File Transfer (UFT)’menu, the following menu appears.
Managing Interrupted Transfer Using SMIT The SMIT menu “Restart Information Log” enables the user to handle interrupted transfer data for both the requester and the server side. It comes under the main “Unified File Transfer” menu. The cascading submenus are the same for the requester and the server. Therefore, only the Server Restart Information Log is shown in detail below. Enter the SMIT Configuration Tool Fastpath = smit [–C] uft 1.
#transfer id: 20143896420000000000 #local login: root #remote node: @JUC4 #local file name: /tmp/_U09210.Z ################################################## #transfer id: 19167822920000000000 #local login: marcel #remote node: @JUC1 #local file name: /users/marcel/guionnea/new_LIB.a ################################################## #transfer id: 14360444250000000000 #local login: uftex3 #remote node: @BS3D #local file name: /tmp/_U09910.
On entering the restart identifier, the complete description of the associated entry is displayed in the following form: transfer id : 14360444250000000000 local file name local login remote node record size datacode data comp file organ file type rec format access type initial size restart rank file seq num : : : : ; : : : : : : : : /tmp/U09210.
Chapter 5. UFT Application Program Interface Overview The purpose of this chapter is to describe the Application Program Interface (API) of UFT V3.1 (Unified File Transfer). The UFT API V3.1 is delivered with the standard UFT V3 MI. General Features The UFT API supplies all the functions of the requester (uft client) process of UFT. These functions enable a user to create an application that executes file transfer, file creation, file deletion... with a remote host supporting the UFT protocol.
• UFTdisconnect() to disconnect from the remote host. The states of UFT API are: 0 Reset 1 Initialized 2 connected 1 1 2 UFTconnect() NA 2 NA UFTdisconnect() NA NA 1 UFTsend() NA NA 2 UFTrec() NA NA 2 UFTdelete() NA NA 2 UFTcreate() NA NA 2 UFTgetattribut() NA NA 2 UFTnoabort() NA NA 2 UFTtrace() NA 1 2 UFTcmp() 0 1 2 UFTmodify() NA NA 2 UFTrestart() NA NA 2 UFTwho() NA NA 2 States Functions UFTinit() Table 1.
UFTinit() Purpose Initialization of the UFT API. Syntax int UFTinit(return_code) unsigned int * return_code Description This function initializes the UFT API and checks that a local UFT server is currently working. Parameters return_code Specifies the result of the call execution, which is returned to the local program. return_code can have one of the values explained below. Return Code Values UFT_OK: no error.
UFTconnect() Purpose Connection to a remote host.
struct tadrres { unsigned short ladrres; unsigned char typadr[8]; }; struct qostype { unsigned short lfac; unsigned char typfac[109]; }; Fixed part TABSIT lsaping sttsaping Variable part lsaped sttsaped ldtx25 dtx25 lnsaping nsapind lnsaped nsaped Fixed part stcl class of transport: 0, 2, 3,4 staltcl alternate class: 0, 2, 3, 4, 0xFF stexp use of express stream 1, 0 (need to be set to 1 for UFT) stctrl stream check: 0, 1 stcrdt transport credit: from 1 to 15 stltpdu size of tpdu in bytes, fr
stwo network transmit window from 1 to 127 stypres network type: 1: X25, WAN with SNPA address 2: Ethernet with SNPA address 3: FULL–IP with NSAP address 4: NULL–IP with SNPA address 5: SPEE/Netshare 6: X25,with PVC stcnx connection type (0 with connection, 1 without connection) stfrna local address (SNPA) sttona remote address (SNPA) stqos facility linked to network (e.g., TRANSPAC facilities) variable part Lengths are coded with one byte.
max_record_size Maximum record size negotiated during the connection phase. (see ”Connecting to a remote Host”, on page 2-15 for the limits and the used of this parameter). transfer_mode The transfer mode can be UFT_MODE_LINE for line mode, or UFT_MODE_BLOC for block mode (see ”File Transfer Modes”, on page 1-4).
UFTdisconnect() Purpose Disconnection from a remote host. Syntax int UFTdisconnect(return_code) unsigned int * return_code Description This function closes a connection with the remote host. Parameters return_code Specifies the result of the call execution, which is returned to the local program. return_code can have one of the values explained below. Return Code Values UFT_OK: The function UFTdisconnect is successful.
UFTsend() Purpose Send a file to the remote host already connected. Syntax int UFTsend (local_file_name, send _mode, remote_filename, return_code, transfer_id) char * local_file_name int send_mode char *remote _file_name unsigned * return_code char ** transfer_id Description The file (local_file_name) is sent to the remote host. Parameters local_file_name It is the full name of the file to send (e.g.: /users/cop/bin/file.uft).
UFT_NO_CONNECT: There is no connection. A UFTconnect() must be issued first. State Changes If no error occurs, the connection state remains connected. If UFT_COM_ERR occurred the connection state may change to disconnected. Application Usage The connection state must be connected. Related Information See also the send subcommand, and the ”Error Messages”, on page A-1.
UFTrec() Purpose Receive a file from a remote host already connected. Syntax int UFTrec (remote_file_name, rec_mode, local_file_name, return_code, transfer_id) char * remote_file_name int rec_mode char * remote_file_name unsigned int * return_code char ** transfer_id Description The file (remote_file_name) is received from the remote host. Parameters remote_file_name It is the full name of the file to be received.
UFT_NO_CONNECT: There is no connection. A UFTconnect() must be issued first. State Changes If no error occurs, the connection is still initialized to the remote hosts. The connection state remains connected. If UFT_COM_ERR occured the connection state can be disconnected. Application Usage The connection state must be connected. Related Information See also the receive subcommand, and the ”Error Messages”, on page A-1.
UFTdelete() Purpose Delete a file of a remote host already connected. Syntax int UFTdelete(remote_file_name, return_code) char *remote_file_name unsigned int return_code Description The file (remote_file_name) is removed from the remote host. Parameters remote_file_name The name of the file to be removed. See ”File Identifiers on Non DPX Systems”, on page B-1 for the syntax of other files for non UNIX machines.
UFTcreate() Purpose Create a remote file. Syntax int UFTcreate (remote_file_name, file_size, return_code) char *remote_file_name int file_size unsigned int * return_code Description The file (remote_file_name) is created to the remote host. Parameters remote_file_name This is the name of the file to be created. See ”File Identifiers on Non-DPX Systems”, on page B-1 for the syntax of other files of non-unix machines. file_size The initial size of the file to be created.
UFTgetattribut() Purpose Get attributes of a remote file. Syntax int UFTgetattribut (remote_file_name, attributs, return_code) char * remote_file UFTattrib * attributs unsigned int * return_code Parameters remote_file_name The name of the remote file from which to get the attributs. attributs [A structure UFTattrib containing all the attributs of the file.
file_type UFT_UNDEF_FILE (for all files exept GCOS 8 files) UFT_GFRC_FILE (for GCOS 8 file) UFT_UFAS_FILE (for GCOS 8 file) record_format UFT_FIXED UFT_VARIABLE inc_alloc_size incremental size max_alloc_size maximum file size cur_alloc_size current file size alloc_size_unit define the unit for the size fields: 0: KBytes 1: number of records creat_date creation date last_ret_date last access date last_mod_date last modification date return_code Specifies the result of the call execution, which is returne
UFTnoabort() Purpose Set/unset the noabort mode. Syntax UFTnoabort (flag, return_code) int * flag unsigned int * return_code Parameters flag The possible values for this flag are: UFT_SET: To set the noabort mode. UFT_UNSET: to disable the no abort mode. The flag is returned to the user with the value UFT_SET or UFT_UNSET: UFT_SET: The noabort mode is accepted. UFT_UNSET: The noabort mode is refused because the remote host does not accept the UFTrestart() function.
UFTtrace() Purpose Set the trace level and the trace file. Syntax int UFTtrace (trace_level, trace_file, return_code) unsigned int trace_level char * trace_file unsigned int * return_code Parameters trace_level This parameter gives the level of trace and can take the following values: 0: no trace 1: trace level 1 2: trace level 2 3: trace level 3 trace_file The file in which the traces are recorded. return_code Specifies the result of the call execution, which is returned to the local program.
UFTcmp() Purpose Set/unset the compress mode. Syntax int UFTcmp (flag, return_code) int * flag unsigned int * return_code Parameters flag The possible values for this flag are: UFT_SET: To set the compress mode. UFT_UNSET: To disable the compress mode. return_code Specifies the result of the call execution, which is returned to the local program. return_code can have one of the values explained below. Return Code Values UFT_OK: The function UFTcmp() is successful.
UFTmodify() Purpose Modify the parameter of the connection. Syntax int UFTmodify (max_record_size, transfer_mode, remote_machine_type, GCOS8_file_type, return_code) unsigned int * max_record_size unsigned int transfer_mode unsigned int remote_machine_type char GCOS8_file_type unsigned int * return_code Parameters max_record_size Maximum record size negotiated during the connection phase. (see ”Connecting to a remote Host”, on page 2-15, for the limits and the used of this parameter).
State Changes No state change, only connection parameters are changed. Application Usage The state must be connected before issuing this function. Related Information See also the modify subcommand, and the ”Error Messages”, on page A-1.
UFTrestart() Purpose Restart an interrupted transfer. Syntax int UFTrestart (transfer_id, return_code) char * transfer_id unsigned int * return_code Parameters transfer_id It is the identifier of the interrupted transfer. return_code Specifies the result of the call execution, which is returned to the local program. return_code can have one of the values explained below. Return Code Values UFT_OK: The function UFTrestart() is successful. UFT_ERR: An error occurs from the UFT protocol.
UFTinterrupt() Purpose This function can be called by a user signal handler to interrupt a transfer (UFTsend(), UFTrec() or UFTrestart()). Syntax void UFTinterrupt() Description During a file transfer, a signal handler can call this function to interrupt the file transfer. The information about the file transfer is logged and the file transfer can be restarted using UFTrestart(). If the interruption failed, the return_code of UFTsend() or UFTrec() contains the reason for the failure.
UFTwho() Purpose get the characteristics of the current connection from the local point of view. Syntax int UFTwho (uftwho, return_code) UFT_who *uftwho unsigned int return_code Parameters uftwho A structure UFT_who containing all the characteristics of the connection: connexion_en_cours 1:connected curdir current directory of the local system site remote host to which the user is connected locallogin the local login remotelogin the remote login remote remote type machine (DPX,....
Appendix A. Error Messages Overview This appendix deals with the error messages displayed during the Connection Phase and the Running Phase of UFT. For more information about diagnostics, see ”UFT Diagnostic Guide”. Error Messages during Connection Phase Error messages concerning faulty installation or operation may be displayed during the connection phase: • Remote UFT server: inactive or saturated The remote server is inactive or saturated.
This error occurred during the execution of the connect subcommand, see page 2-6. Return codes can appear in the second and third lines. A return code consists of 4 bytes structured as follows: • origin 1 byte, where: – the leftmost bit signifies: 0: error on local system 1: error on remote host – the 7 rightmost bits identify the OSI layer that set the return code.
Return Codes Severity Code 0 Return Code Mnemonic Description 06000000: normal: no error 06000001: errtronq: truncated data 06000002: errcrefich: remote host refused to create file 06000003: errattfich: remote host refused file attributes request 06000004: errassfich: remote host refused to assign file 06000005: errouvfich: remote host refused to open file 06000006: errdeassfich: remote host refused to deassign file 06000007: errfermfich: remote host refused to close file 06000008
Check Pointing Return Code Mnemonic Description 0601002e: 0601002f: errnockm: errckmnum: checkpoint option not negotiated incorrect ckm number Parameter Errors Return Code Mnemonic Description 06010030: 06010031: 06010032: 06010033: 06010034: 06010035: 06010036: 06010037: 06010038: 06010039: errparam: errdonnees: errlgdata: errlgemiss: errlgrecept: errfileid: errlgfileid: errlgtr: errtrid: errlgrest: 0601003a: 0601003b: errrest: erretfcb: incorrect parameter in FCB no data during send (length=0
FCB Return Codes Return Code Mnemonic Description 00000000: 06010001: 06010002: 06010003: 06010004: erfcbnormal: erfcbmispar1: erfcbinvpar1: erfcbincpar1: erfcbduppar1: 06010005: 06010006: 06010007: 06010008: 06010009: 0601000a: 0601000b: 0601000c: 0601000d: 0601000e: 0601000f: 06010010: 06010011: 06010012: 06010013: 06010014: 06010015: 06010016: 06010017: 06010018: 06010019: 0601001a: 0601001b: 0601001c: 0601001d: 0601001e: 0601001f: 06010020: 06010021: 06010022: 06010050: 06010051: 06010052: 06010053
Common Errors set by the Session Layer: A-6 Return Code Mnemonic Description 05600001: indtronc: truncated data 0500003a: errclo: closure in progress 05010013: errrefclo: remote host refused disconnection 05010018: errproftrp: incorrect transport profile 05010033: erretat: status incompatibility 0501003b: errab: abort in progress 0501003c: errsync: resynchronization in progress 0501003d: errdem: identical request in progress 0501003e: errto: timeout error 05010043: errrefus:
Common Errors set by the Transport Layer Return Code Description 04010002: session local entity not connected 84010002: session remote entity not connected 04010003: unknown local network address 84010003: unknown remote network address 04010080: disconnection requested by local session 84010080: disconnection requested by remote session 04010085: local protocol error 84010085: remote protocol error Error Messages A-7
UFT API Protocol Errors A-8 Return Code Mnemonic Description 10010001: erfcbmispar1: missing parameter or incorrect value 10010002: erfcbinvpar1: invalid parameter 10010003: erfcbincpar1: unknown parameter 10010004: erfcbduppar1: illegal duplication of parameter (only last value retained) 10010005: erfcbunkpar1: unknown parameter (ignored) 10010006: erfcbseqpar1: parameter out of sequence 10010007: erfcbsuppar1: unsupported parameter value 10010008: erfcbaccperm: unsufficient acc
Return Code Mnemonic Description 10010056: erfcbtimeout: inactivity timeout expired 10010077: erfcbintegrestart: cannot assume data integrity in restart 10010078: erfcbuserrestart: bad remote site or bad connection on restart 10010080: err_notfound: host name not found in /etc/isohosts 10010081: err_format: format error in /etc/isohosts 10010082: err_param: parameter entry error in /etc/isohosts 10010083: err_tronq: incomplete entry in /etc/isohosts Error Messages A-9
A-10 UFT Reference Manual
Appendix B. File Identifiers on Non DPX Systems Overview The following sections give the syntax of file identifiers: • Syntax of File Identifiers on the DPS 7, on page B-1. • Syntax of File Identifiers on the DPS 8, on page B-3. • Syntax of File Identifiers on the DPS 6, on page B-3. • Syntax of File Identifiers on IBM Systems, on page B-4. Syntax of File Identifiers on the DPS 7 Members of Source or Binary Libraries Uncataloged Library Syntax: library_name..
Example: D7LIB..
Syntax of File Identifiers on the DPS 8 For a disk file: Syntax: UMC_name/UFT_catalog_name/file_name where: UMC_name designates the name of the UMC associated with the login on the DPS 8 UFT_cat_name designates the name of the catalog including the UFT access rights to files file_name designates the name of the file in the UFT catalog. This file inherits the rights of the UFT catalog, and can therefore be handled by UFT.
Syntax of File Identifiers on IBM Systems For IBM systems, the dataset name must be specified. The dataset name is up to 44 alphanumeric characters, which completely qualify the cataloged dataset or cluster. Example: GROUP1.
Appendix C. File Management on the DPS 7 Overview The following sections describe how to: • Create Libraries and Files, on page C-1. • Display Libraries and Files, on page C-3. Creating Libraries and Files The file creation facility of UFT is not supported by release GCOS7 V5 or earlier releases on the DPS 7. One solution is to use a terminal connected to IOF to create the files on DPS 7 before sending them by UFT. Some products such as PAD, TWS2107, OTM provide a remote terminal function.
Characteristics of the library created: name D7LIBSL status uncataloged (UNCAT) initial_size 2 x D500 disk cylinders max_number_of_members10 type source library (SL) medium cartridge disk (MS/D500) medium_name L738 BUILD_FILE Command Syntax BF FILE=file_name:media:device FILESTAT=UNCAT UFAS=SEQ UNIT=CI SIZE=number_of_CI CISIZE=size_of_CI RECSIZE=record_size RECFORM=V Description Creates a UFAS Sequential Variable File Flags file_name identifies the file media identifies the medium on which
Characteristics of the File created: name D7FICSEQ status uncataloged (UNCAT) initial_size 20 CIs (CI is 2048 bytes in this case) record_size 1024 bytes (maximum) record_format V (variable) medium fixed disk (MS/D500) medium_name L686 Displaying Libraries and Files LIST_FILE Command Syntax LSF {library|file_name} ALL; Description Displays library and file Characteristics: Flags library or file_name identifies the library or file Example LSF STOCK:L738:MS/D500 ALL; For printing, displays th
Flags library_type identifies the type of the library, source (SL) or binary (BIN) library_name identifies the library Example MNLIB SL D7LIBSL:L738:MS/D500 This starts the library management processor with the uncataloged D7LIBSL:L738:MS/D500 as the name of the current library. MNLIB command changes the library and allows its members to be displayed. Subcommands The following printing commands can be used with the MAINTAIN_LIBRARY command.
Appendix D. Creating Files on the DPS 8 Recommendations for Creating Files with UFT The size of files created on the DPS 8 is expressed in little links (1 LL = 1280 characters). The UFT application for the DPS 8 converts the size chosen by a remote UFT user from Kbytes to LL. The GFRC sequential organization stores control records and data records: • when the file is created • when the file is filled. Since the unit of the DPS 8 file is the 4–byte word, all records are multiples of 4 bytes.
D-2 UFT Reference Manual
Appendix E. System Limitations Transferring NFS Files with UFT To send or receive an NFS file, the lock manager daemons /usr/bin/rpc/lockd and /usr/bin/rpc/statd must both be running. The daemons lock the file during its transfer, thereby enabling UFT to preserve the integrity of the file contents. See DPX/20 Commands Reference Manual (6 Volumes) for details on the lock manager. The uft or uftser process may block if the user attempts to transfer an NFS file when the above daemons are not running.
E-2 UFT Reference Manual
Appendix F. API Programming Example The sources of this program are found in /usr/lpp/uft/samples. Compilation command: cc –lUFTapi –lPW program.c –o program /* * @BULL_COPYRIGHT@ */ /* * HISTORY * $Log: caller.c,v $ * Revision 1.2 1996/01/24 * * $EndLog$ */ #include #include #include #include ”UFTapi.
”interrupt” ,DOUFTinterrupt, ”tracoff” ,DOUFTh, ”traceon” ,DOUFTh1, ”print” ,DOUFTprint, ”psrint” ,DOUFTsprint, ”who” ,DOUFTwho, ”” ,(void (*)())0 } static char tbfin[] = ”fin”; int level_trace = 0 ; #define PRINTF(A)\ {\ if ( level_trace == 0 )\ {\ printf(A);\ }\ } void perreur( char * s , unsigned int crd) { printf(”\n”); if ( crd > 256 ) { printf(”erreur dans %s %x \n”, s , crd); return; } if ( (crd & UFT_ALREADY_CON) == UFT_ALREADY_CON) { printf(”erreur dans %s UFT_ALREADY_CON \n”,s); } if ( (crd & U
struct int scall *sc; index ; printf(”For inputs, printf(” printf(” printf(” (s) (d) (x) (o) means means means means string,\n”); decimal,\n”); hexadecimal,\n”); octal\n”); for ( printf(”\nsyscall ? ”); scanf(”%s”, syscall) != EOF ; printf(”\nsyscall ? ”) ) { for (sc = syscalls; sc–>funct && strcmp(sc–>name, syscall); sc++); if (sc–>funct) (*sc–>funct)(); else { if ( strcmp(syscall,tbfin) == 0 ) break ; printf(”syscall:\n”); for (sc = syscalls,index=0; sc–>funct; sc++,index++) { printf(”%s ”, sc–>name
unsigned int return_code = 9999 ; int crd = 9999 ; crd = UFTinit (&return_code) ; if ( return_code != 0 ) { perreur (”UFTinit\treturn_code =”,return_code); } if ( crd != 0 ) { perreur (”UFTinit\tcrd =”, crd ); } } void { DOUFTcmp() unsigned return_code = 9999 ; int crd = 9999 ; int recall ; int flag_comp ; PRINTF(”Compress mode 1(set) 2(unset)?”); recall = scanf(”%d”,&flag_comp); crd = UFTcmp(&flag_comp, &return_code) ; if ( return_code != 0 ) { perreur (”UFTcmp\treturn_code =”,return_code); } if ( crd !=
perreur (”UFTsend\tcrd =”,crd); } if ( return_code != 0 ) { perreur (”UFTsend\treturn_code =”,return_code); } if ( (crd&UFT_TRANS_REST) == UFT_TRANS_REST ) { printf(”Transfert Id = %s \n”,transfer_id); } } void { DOUFTrec() unsigned return_code = 9999 ; int crd = 9999 ; int recall ; char nom_local[256]; char nom_distant[256]; char *transfer_id ; int type_trans ; PRINTF(”nom distant file :? ”); recall = scanf(”%s”,nom_distant); PRINTF(”nom local file :? ”); recall = scanf(”%s”,nom_local); PRINTF(”Type tran
perreur (”UFTgetattribut\tcrd =”,crd); } if ( return_code != 0 ) { perreur (”UFTgetattribut\treturn_code =”,return_code); } } void { DOUFTdelete() unsigned return_code = 9999 ; int crd = 9999 ; int recall ; char nom_file[256] = ”” ; PRINTF(”nom fichier a deleter:?”); recall = scanf(”%s”,nom_file); crd = UFTdelete( nom_file , &return_code); if ( crd != 0 ) { perreur (”UFTdelete\tcrd=”,crd); } if ( return_code != 0 ) { perreur (”UFTdelete\treturn_code =”,return_code); } } void { DOUFTcreate() unsigned retu
unsigned int transfer_mode ; PRINTF(”nom Site :?”); recall = scanf(”%s”,&nom_site ); PRINTF(”login distant :?”); recall = scanf(”%s”,&remote_log); PRINTF(”passwd distant :?”); recall = scanf(”%s”, &remote_pass); PRINTF(”Max record size ( 1–>512 2–>950 3–>2000 ):”); recall = scanf(”%d”,&max_record_size); if ( max_record_size == 1 ) { max_record_size = 512 ; } if ( max_record_size == 2 ) { max_record_size = 950 ; } if ( max_record_size == 3 ) { max_record_size = 2000 ; } PRINTF(”Mode transfert:? 1(Mode block)
} if ( crd != 0 ) { perreur (”UFTdisconnect\tcrd =”,crd); } } void { DOUFTnoabort() unsigned int return_code ; unsigned int crd ; int recall ; int flag = 1; PRINTF(”noabort SET(1) UNSET(2):?”); recall = scanf(”%d”,&flag); crd = UFTnoabort(&flag, &return_code) ; if ( return_code != 0 ) { perreur (”UFTnobaort\treturn_code =”,return_code); } if ( crd != 0 ) { perreur (”UFTnobaort\tcrd =”,crd); } } void DOUFTmodify() { unsigned int return_code ; unsigned int crd ; int recall ; unsigned int max_record_size = 1
recall = scanf(”%d”,&remote_type_machine); PRINTF(” type de fichiers GCOS8 (1 GFRC) ( 2 UFF REL) (3 UFF SEQ) :?”); recall = scanf(”%d”,&GCOS8_file_type); crd = UFTmodify( &max_record_size,transfer_mode,remote_type_machine,GCOS8_file_typ e,&return_code); if ( return_code != 0 ) { perreur (”UFTmodify\treturn_code =”,return_code); } if ( crd != 0 ) { perreur (”UFTmodify\tcrd =”,crd); } } void DOUFTrestart() { unsigned return_code = 9999 ; int crd = 9999 ; int recall ; char transfer_id[256] = ”” ; PRINTF(”Trans
} } /* extern int *,char *, UFTconnect(struct TABSIT *,unsigned int,char char *,char *,char *,unsigned int *,unsigned int, unsigned int,char ,unsigned int *); */ void { DOUFTinitcon() unsigned return_code = 9999 ; int crd = 9999 ; int recall ; char nom_site[256] = ”” ; char remote_log[256] = ”root”; char remote_pass[256] = ”twitwi”; char remote_bil[256] = ””; char remote_proj[256] = ””; unsigned max_record_size =512 ; unsigned remote_type_machine = 1 ; char GCOS8_file_type ; unsigned int transfer_mode ;
s[0]=’.’; }else{ s[0]=buffer[i]; } continue; } if(i%4==0) { printf(” ”); } if (i%24==0) { printf(” %s\n”,s); } printf(”%02x”,buffer[i]); if(isprint(buffer[i])==0) { s[i%24]=’.
uftwho.maxlgrecs); if(uftwho.transfermode == UFT_MODE_BLOC) { printf(”Transfer mode \t\t\t: block \n”); } if(uftwho.transfermode == UFT_MODE_LINE) { printf(”Transfer mode \t\t\t: line\n”) ; } printf (”Compression mode\t\t: %s\n”,(uftwho.uftcompac == UFT_SET)?”on”:”off”) ; printf (”No abort mode\t\t\t: %s\n”,(uftwho.uftnoabort == UFT_SET)?”on”:”off”); printf (”Trace level\t\t\t: %d\n”,uftwho.trace_level); printf (”Trace file\t\t\t: %s\n”,uftwho.
Appendix G. Remote Hosts Table To connect with a remote host, specify the remote host. For example, SYSTEM001 in connect. UFT checks if this host name exists in the file /etc/isohosts and recovers the information necessary to connect to it. The command /usr/lpp/uft/samples/uftact is used to create and to subsequently update the remote hosts access file /etc/isohosts. A conventional text editor can also be used to modify the /etc/isohosts file.
Examples of possible values: 12 (decimal value 12) 0xfc (hexadecimal value fc) 12,13,0xa2,0x2,3 (decimal and hexadecimal values) • the lines between two site description tables are ignored by connect • the description of the site table must not contain blank lines and must be in the order specified above • no line must be left out except that concerning TSAPs if the length of these is null.
flow control Sets the flow control on the transport where: - 0 no flow control on the transport - 1 flow control on the transport. flow control on transport is recommended. credit Credit on the transport protocol must be set as a function of tpdu size. A credit of 3 for a tpdu of 1024 bytes is recommended. class 4 checksum control Sets an additional check for class 4 transport to allow detecting errors during the message transportation: - 0 no additional check - 1 additional check.
type of connection: Type of connection in the case of an X25 public or private network: - 0 switched virtual circuit (SVC) - 1 permanent virtual circuit (PVC). local address Network address of local system. The format of the address must be compatible with the type of network: - X25 address format - Ethernet, Token Ring, FDDI address format - local NSAP for FULL–IP, SPEE or NetShare. remote address Network address of remote host.
The local address and remote address fields for the local and remote network addresses must comply with the format for the type of network (X25 or Ethernet): • for X25, depending on the connection: – SVC connection, The local and remote network addresses are expressed as a string of 1 to 15 decimal digits. For example: 138061000 (TRANSPAC address) – PVC connection, The remote network addresses are expressed as a string of 8 characters.
Access to a Remote Host via ETHERNET The following description enables connection to a remote host SITEA via Ethernet: SITEA ufts: 0x10 uftp: 0x10 class of transport (0, 2, 4): 4 alternate class (0, 2, 4): 2 expedited data (0, 1): 1 flow control (0, 1): 1 credit (1 to 15): 3 checksum control for class 4 (0, 1): 0 tpdu size: 1024 nsdu size: 1024 npdu size: 1024 input network window (1 to 127): 3 output network window (1 to 127): 3 type of network (1–X25 2–ETH 3–INTER 4–NULLINTER): 2 type of connection (0 SVC
Glossary This glossary contains the abbreviations, keywords and phrases that can be found in this document. API Application Program Interface: Functional interface allowing a high level language application program to use specific data or functions of the operating system. ASCII American Standard Code for Information Interchange. COSP Connection Oriented Session Protocol. COTP Connection Oriented Transport Protocol. DPX Distributed Processor for UNIX. DSA Distributed Systems Architecture.
RIB Routing Information Base, Network database which contains all the required routing information to remote NSAPs. It gives the remote SNPA and local subnetwork to use for NSAPs or groups of NSAPs. The SNPA is found by using the Subnet table. SMIT System Management Interface Tool (IBM): Menu–driven, resident command–building system management facility. SNPA Sub Network Point of Attachment: Information for accessing the system within the domain (Transpac or Ethernet address).
Index Symbols ! command, 2-12 ? command, 2-4 A Access via Ethernet, G-5 via FULL–IP, G-6 via TRANSPAC, G-5 Address Ethernet, G-5 FULL–IP, G-5 NULL–IP, G-5 X25 PVC connection, G-5 X25 SVC connection, G-4 API functions UFTcmp(), 5-19 UFTconnect(), 5-4 UFTcreate(), 5-14 UFTdelete(), 5-13 UFTdisconnect(), 5-8 UFTgetattribut(), 5-15 UFTinit(), 5-3 UFTinterrupt(), 5-23 UFTmodify(), 5-20 UFTnoabort(), 5-17 UFTrec(), 5-11 UFTrestart(), 5-22 UFTsend(), 5-9 UFTtrace(), 5-18 UFTwho(), 5-24 B Binary file, 1-4 Block t
Ethernet, access via, G-5 Ethernet address, G-5 exit command, 2-8, 2-16 F FCB return codes, A-5 session, A-6 transport, A-7 File binary, 1-4 byte stream file, 1-4 DPS 6 file types, 3-8 DPS 7/7000 file types, 3-3 DPS 8 file types, 3-5 IBM systems file types, 3-7 sequential, 1-4 text, 1-4 File structure, DPX/20, 1-5 Files, Creating DPS 8 files, D-1 FULL–IP, access via, G-6 FULL–IP address, G-5 NSAP address, 4-9 NULL–IP, 4-9 OSI/DSA TSAP address, 4-8 TSAP, 4-7, 4-8, 4-9, 4-10 remote site NETSHARE address, 4-
UFT Functions, 1-2 UFT process client, 1-2 requestor, 1-2 server, 1-2 UFT running environment, 1-3 UFTcmp(), 5-19 UFTconnect(), 5-4 UFTcreate(), 5-14 UFTdelete(), 5-13 UFTdisconnect(), 5-8 UFTgetattribut(), 5-15 UFTinit(), 5-3 UFTinterrupt(), 5-23 UFTmodify(), 5-20 UFTnoabort(), 5-17 UFTrec(), 5-11 UFTrestart(), 5-22 UFTsend(), 5-9 UFTtrace(), 5-18 UFTwho(), 5-24 W who command, 2-14 X X25 PVC connection address, G-5 X25 SVC connection address, G-4 Index X-3
X-4 UFT Reference Manual
Vos remarques sur ce document / Technical publication remark form Titre / Title : Bull DPX/20 Unified File Transfer (UFT) Reference Manual Nº Reférence / Reference Nº : 86 A2 10CB 03 Daté / Dated : March 1996 ERREURS DETECTEES / ERRORS IN PUBLICATION AMELIORATIONS SUGGEREES / SUGGESTIONS FOR IMPROVEMENT TO PUBLICATION Vos remarques et suggestions seront examinées attentivement Si vous désirez une réponse écrite, veuillez indiquer ci-après votre adresse postale complète.
ORDER REFERENCE 86 A2 10CB 03 PLACE BAR CODE IN LOWER LEFT CORNER Bull Electronics Angers S.A.
Utiliser les marques de découpe pour obtenir les étiquettes. Use the cut marks to get the labels.
