Home

Digital SNA Data Transfer Facility for OpenVMS Use

1. CANCEL REQUEST YES NO Take one of the following actions e Type YES and press Enter to cancel the request and free the terminal e Type NO and press Enter to continue processing Using the DTF for IBM Command Processor 9 31 If you respond with YES the DTF processor halts the transfer at the current position You must then clean up the partial files You cannot issuea RESUME subcommand to restart a canceled request On VM systems you can cancel a transfer that is in progress at any time by typing the command CANCEL and pressing Enter You can request a status report for a transfer in progress by typing the command QUERY and pressing Enter The following sections describe the required and optional keywords associated with the RESUME subcommand RETNUM retry number The number returned in message DTF0062I when the original request was submitted retry number The number returned by the DTF processor in the DTF 00621 message Length 5 digits Range 1 to 32767 CLIENTUSER decnet user id Specifies the user ID for the DECnet file specification involved in the original TRANSFER request decnet user id The user ID for the DECnet file specification involved in the original TRANSFER request Length 1 to 40 characters Usage Notes e The CLIENTUSER keyword should not be used in the following situations Ifthe original file transfer involved two
2. DTF for VM DTF utilities MS DOS DECnet SNA PATHWORKS for DOS DECnet Gateway n node VMS DTF IBM O22 ey server client node PATHWORKS for OS 2 ULTRIX DECnet ULTRIX OpenVMS DTF server RSX 11M M PLUS DECnet RSX LKG 4629 93R 1 3 1 Multiple User Interfaces All Clients The DTF product provides both Digital and IBM users with a familiar user interface This interface allows both Digital and IBM users to transfer data using an interface to which they are already accustomed 1 4 Introducing the Data Transfer Facility DTF Product 1 3 1 1 DECnet User Interfaces Most of the network file transfer commands work in much the same way with DTF as they do when they are used to access a file on a DECnet network The only difference is that one of the file specification parameters is replaced with an IBM file specification This makes accessing a file on an IBM client as easy as accessing a file on a DECnet network Refer to Chapter 2 for more information on the IBM file specification parameters and IBM file specification qualifiers Refer to Chapter 5 and Chapter 6 for information on using the OpenVMS client interfaces Refer to Chapter 10 for information on using the ULTRIX and Digital UNIX client interfaces Refer to Chapter 11 for information on using the RSX 11M M PLUS client interface Refer to C
3. VM Output File Options Panel 000 Network File Options Panel 000 0c eee Data Translation Options Panel Post Processing Options Panel 00 eee eens Batch Options Panel VM Systems 050 Batch Options Panel MVS Systems 04 File Structure of VSAM Sequential or Relative Files 9 42 9 42 9 43 1 4 2 23 2 24 4 6 4 8 7 3 7 5 7 10 7 15 7 18 7 19 7 22 7 24 7 27 7 30 7 34 7 38 7 39 7 41 7 42 7 43 D 2 xi D 2 File Structure for VSAM Indexed Files 0 D 3 D 3 File Structure for VSAM Indexed File with Multiple Keys D 5 E 1 File Transfers Using FTAM Software and a DAP FTAM Galeway soiice ewes cnet ary foe he Rte ee ae ae E 4 Tables 2 1 IBM File Specification Qualifiers and Their Usage for Remote VM Fil S ccc eee eens 2 10 2 2 IBM File Specification Qualifiers and Their Usage for Remote MVS Files 0 ccc ee ees 2 13 2 3 MVS File Attributes and Their Usage in the BASE and ALTERNATE _INDEX Sections 005 2 40 2 4 VM File Attributes and Their Usage in the BASE and ALTERNATE _INDEX Sections 0005 2 41 4 1 User ID and Password Syntax Rules 4 4 2 4 2 Access to Remote Systems Without Proxy 4 3 5 1 DTF Level of Support for APPEND Command Qualifiers 5 3 5 2 DTF Level of Support for BAC
4. Refer to the sample directory shown at the end of this command description for information about directory contents Note The DIRECTORY command is not supported for IBM tape volumes Table 5 9 shows the level of support DTF provides for the DCL DIRECTORY command qualifiers For more detailed information about the DIRECTORY command refer to the DCL Dictionary Table 5 9 DTF Level of Support for DIRECTORY Command Qualifiers For IBM File Qualifier Specifications Commenis ACL supported 7 BACKUP not supported IBM files do not have a BACKUP date BEFORE time supported BRIEF supported 2See Section 5 10 1 for restrictions 31f specified for an IBM input file specification no file will be selected continued on next page 5 20 OpenVMS File Transfer Operations Table 5 9 Cont DTF Level of Support for DIRECTORY Command Qualifiers Qualifier For IBM File Specifications Comments BY_OWNER uic COLUMNS CREATED DATE option EXCLU DE file spec EXPIRED FILE_ID FULL GRAND_TOTAL INOJHEADING MODIFIED INOJOUTPUT filespec OWNER PRINTER INO JPROTECTION SECURITY SELECT3keywordf SINCE time NO SIZE option TOTAL INOJTRAILING NERSION n WIDTH Xkeyword supported supported supported supported ignored supported supported supported supported supported supported supported supported supported supported supported supp
5. The following DTF subcommands change the completion code e DEFINE sets only a return code of 1 or O e TRANSFER sets all return codes except 1 e RESUME sets all return codes except 1 Note If an internal error occurs during the processing of any subcommand a return code of 12 is generated Return codes from the TRANSFER subcommand are grouped into the following ranges 0 3 The transfer was partially successful 4 7 The transfer could not begin Cleanup of partial files is not necessary 8 12 The outcome of the transfer request is in doubt Some investigation must be done to determine the state of the transfer Cleanup of partial files is necessary A complete explanation of all return codes and suggested user action is contained in an appendix of the Digital SNA Data Transfer Facility for OpenVMS Problem Solving and Messages manual 9 8 Initiating DTF Command Processor Operations from Command Procedures The DTF command processor can be invoked from a TSO CLIST or a CMS REXX exec The DTF subcommands should be entered immediately following the DTF command All records following the DTF command will be treated as input records to DTF until an END subcommand is found Using the DTF for IBM Command Processor 9 45 When the DTF command processor encounters an END subcommand it returns control to the command procedure with the condition code set A list of return codes is included in Section 9 7 9 8 1 Va
6. Queue def outuser jones outpass secret Queue transfer Queue end r dtf Using the DTF for IBM Command Processor 9 39 return r e Submit the job to a CMS batch machine through the panel interfaces The batch machine must have the authority required to link and access the minidisks needed during the transfer For more information about minidisk passwords see the MDxPASSWORD qualifier in Section 2 3 3 9 6 Executing the DTF Command Processor in Batch Mode MVS Systems To execute the DTF command processor in batch mode invoke the TSO Terminal Monitor Program through J CL and DTF command processor subcommands which are supplied in a sequential file Batch mode operations are useful for the following types of situations e For transferring large files that lock the TSO terminal for a long period of time e In production environments where the same files are regularly moved and can be controlled by a scheduling system through the use of J CL procedures e For transfers that require a log a J ES job log can retain transfer information The IBM MVS manuals SPL TSO User s Guide or SPL TSO E User s Guide describe how to invoke the TSO Terminal Monitor Program and explain any TSO enforced restrictions 9 6 1 The SYSTSIN DD Card The SYSTSIN DD card points to a sequential file that supplies the DTF subcommands The sequential file must adhere to the following guidelines e Any record in the file
7. gt SNADTF E RCOPYCOM error communicating with TRANSFER DTF process gt SYSTEM F THIRDPARTY network logical link disconnected by a third party DTFO048I ENTER CLEAR DEFINE END LIST RECALL RESUME SET SHOW OR TRANS RESUME RETNUM 00051 CLIENT NODE1 CLIENTUSER JONES CLIENTPAS BOBJONES SERVER NODE1 NETMGR DTF2 8 DTF0030I REQUEST SUBMITTED TO DTF2 DTF0037I THIS REQUEST ASSIGNED REQUEST NUMBER 00016 DTF0066I THE RECOVERABLE COPY REQUEST IS ABOUT TO BEGIN DTF0062I THIS REQUEST ASSIGNED RETRY NUMBER 00054 DTF0067I SERVER NODE HANDLING THE TRANSFER IS NODE1 VERSION 3 1 0 DTF0068I CLIENT NODE INVOLVED IN TRANSFER IS NODE1 VERSION 3 1 0 DTFOO55I SUBSYSTEM DTF2 REPORTS COMPLETION OF REQUEST 9 gt SNADTF S COPIED NODE1 lt JONES DTF TEST gt TEST123 RES 17 copied to gt NODE1 SNADTF JONES DTFTEST MEMBER USER JONES CORR 00047 PASS password gt CHEC 1000 4583 records DTFO048I ENTER CLEAR DEFINE END LIST RECALL RESUME SET SHOW OR TRANS This DEFINE statement specifies the input file This DEFINE statement specifies the output file This DEFINE statement specifies the transfer parameters This message reports that the transfer was assigned retry number 00051 This message reports that the server node handling the transfer is NODE 1 Aun FF WN PR This message reports that the client node involved in the transfer is NODE1 7 This message rep
8. 0 ce eee Specifying Remote RSX 11M M PLUS Files Specifying Remote MS DOS or OS 2 Files Specifying Remote ULTRIX and Digital UNIX Files IBM File Specification Qualifiers 00 eee Qualifier Defaults 0 0 cc ee eee Qualifier Restrictions When Accessing Remote VM and MVS Clients syn ate Ua Ee ie acelin Ma eb Se ae Qualifier Descriptions 0 0 0 cee ee Setting Up DTF File Definition Files 0 0008 Adding an Entry to the File Definition Database Modifying an Entry in the File Definition Database Displaying File Definitions from the File Definition Database a ndau a 5 AM act die u atenn A whieh Ok aden aa E482 File Format and Syntax 0 0 00 cece BASE and ALTERNATE INDEX Sections INDEX DATA and PATH Subsections 0055 FIle Atir IDUS osc ead Pee aes ba hele a ale aE Fes 3 DTF Supported File Types 3 1 3 1 1 3 1 2 3 1 3 3 1 4 3 2 3 2 1 3 2 2 3 2 3 3 2 4 3 3 3 3 1 Supported Input File Types 0 0 00 ccc eee ees Supported File Organizations 00 ccc ewes Supported Record FormatS 0 cece eee eee ees Supported Record Lengths 0 00 cece eee ees Supported Record Attributes aaae Supported Output File Types 0 0 00 ees Supported File Organizations 0 0c eee eee ees Supported Record FormatS 000 e eee ee eens Supported Record Length
9. e DECne amp RSX Guide to Use Utilities DOS client users may also find the following PATHWORKS for DOS manual to be helpful e PATHWORKS for DOS DECne User s Guide OS 2 dient users may also find the following PATHWORKS for OS 2 manual to be helpful e PATHWORKS for OS 2 Utilities Guide IBM client users may also find the following IBM manuals to be helpful e J CL Reference e CMS Prime e IBM Access Method Services The following IBM manuals provide additional reference information that could be helpful in problem determination e DFP Access Method Services Reference e IBM VTAM Customization e MVS J CL Reference Manual e MVS SeviceAids Manual e MVS System Commands e MVS System Messages e VTAM Operator Commands e VM Planning and Reference e VM SP6 Connectivity Planning and Administration e VM SP5 TSAF Acronyms The following acronyms are used throughout this manual ASCII American Standard Code for Information Interchange DCL Digital Command Language DMCS Digital Multinational Character Set DTF Digital SNA Data Transfer Facility software EBCDIC Extended Binary Coded Decimal Interchange Code ESDS Entry Sequenced Data Set GDG Generation Data Group HSM IBM s Hierarchical Storage Manager IBM MVS IBM s Multiple Virtual Storage system IBM SNA IBM s Systems Network Architecture IBM VM IBM s Virtual Machine system ISPF Interactive System Productivity Facility KSDS Key Sequenced Data Set MS DOS Microsoft Corporation
10. 0 000000 cee eee Displaying OpenVMS DTF Error Messages 4 7 Using the DTF for IBM Panel Interface The DTF Panel Interface 0 ee The Operation Selection Panel 0 00 e ee eee eens The Send to Remote Panel 00000 cece eee The Receive from Remote Panel 000 cece eee The Resume Previously Failed Transfer Panel The Transfer Execution Panel 0000 cece The Remote Node Options Panel 0 00 eee eens The MVS Input File Options Pana 005 The VM Input File Options Panel 0000005 The MVS Output File Options Panel The VM Output File Options Panel 005 The Network File Options Panel 0 00005 The Data Translation Options Panel The Post Processing Options Panel 005 The Batch Options Panel 0 00 cece es 7 15 8 Using the DTF for IBM File Transfer Commands vi 8 1 8 2 8 3 DTFSEND DTFRECV DTFRESUM 7 1 7 3 7 5 7 10 7 15 7 18 7 22 7 24 7 27 7 30 7 34 7 38 7 39 7 41 7 42 9 Using the DTF for IBM Command Processor 9 1 Invoking the DTF Command Processor 004 9 1 9 2 The DTF Command dauena cd Sade wake Bae aside Beare E K 9 2 9 3 DTF Subcommands 0 00 cece eee eee eens 9 2 9 3 1 CLEAR Subcommand 00c eee eee eee eens 9 4 9 3 2 DEFINE Subc
11. Gives an overview of the file definition commands of the OpenVMS SNADTFCFG utility Describes VSAM file structures and provides additional information about VSAM files Discusses IBM and Digital data types and the way DTF translates data between Digital and IBM systems Discusses the FTAM file types supported by DTF FTAM Discusses the correspondence between OpenVMS DTF qualifiers and DTF for IBM command processor keywords and ISPF panel entry fields The postage prepaid Reader s Comments form on the last page of this manual is for your critical evaluation to assist us in preparing future documentation Associated Documents The Digital SNA Data Transfer Facility software documentation consists of the following manuals Digital SNA Data Transfer Facility for OpenVMS Installation Digital SNA Data Transfer Facility for OpenVMS Management Digital SNA Data Transfer Facility for OpenVMS Problem Solving and Messages Digital SNA Data Transfer Facility for OpenVMS Use You should have the following Digital documents available for reference when you use the Digital SNA Data Transfer Facility software Common Data Dictionary Summary Description Common Data Dictionary User s Guide Common Data Dictionary Utilities Reference Common Data Dictionary Data Definition Language Reference Digital SNA Domain Gateway Installation Digital SNA Domain Gateway Management Digital SNA Domain Gateway Guide to IBM Resource Definition DECn a
12. IB DD DISP SHR DSN DTFTLOAD R DD DISP SHR DSN DTFIBM DTFUSER PARMS RT DD SYSOUT DD DSN SYS1 BRODCAST DISP SHR P DD DSN IPO1 HELP DISP SHR DD t the recoverable transfer DTF SERVER BOSTON OV Y ILE PAYROLL DATA TFILE BOSTON SMITH SECRET A A R POST POST COM 9 42 Using the DTF for IBM Command Processor This is a sample batch job that demonstrates how the post processing feature may be used In this case the local file PAYROLL DATA is being transferred to the remote OpenVMS node named BOSTON When the transfer completes successfully the DCL command procedure named POST COM will be submitted on the remote node Example 9 3 Sample REXX EXEC to Automatically Recover a Transfer VM DTF Batch Job Queue def netmgr dtf4 server vmsland Queue def infile profile EXEC a Queue def outfile vmsland a a Queue def outuser lindsey outpass secret Queue def recovery y Queue transfer Queue end rc dtf batc If we had a recoverable error try to resume the transfer if rc 2 then do Retrieve values saved by DIF globalv select dtfresum get Sretnum Sclient Sclientuser Sclientpass Try again in 10 minutes CP SLEEP 10 MIN Resume the transfer Queue set netmgr dtf4 server vmsland Queue resume retnum Sretnum client client clientuser clientuser clientpass Sclientpass Que
13. MDxPASSWORD Qualifier Part 2 Is minidisk password for No password required requested operation password ignored and mode access if supplied set to ALL Specify a single password using the rules below and DTF will provide the Was DTF correct password or passwords needed on IBM system for the access configured to do mini j SI disk password Specify the read write or multiwrite validation password for read access Specify the write or multiwrite password for write and delete access Specify one or more passwords using the rules below Specify read for read operation Specify multiwrite for write operations Specify multiwrite and read for delete operations Specify multiwrite for all mode 0 accesses LKG 4416B 93R 2 24 DTF File Specifications MRS record length Specifies the maximum record size MRS for a VB file to be created on the IBM MVS system where the record lengths exceed 255 bytes and the MRS is set to 0 for the file definition Usage Notes This qualifier is valid only for creating a file The default is to supply no maximum records size MVS This qualifier is for MVS files only This qualifier is not recommended unless you specifically need it This value is useful for transfers in which a VB file is to be created on the IBM MVS system and record lengths exceed 255 bytes with the MRS defaults or is set to 0 The maximum record size defaults
14. MODIFIED supported 11f specified for an IBM file specification the qualifier is ignored 31f specified for an IBM input file specification no file will be selected 4See Section 5 10 1 for restrictions continued on next page OpenVMS File Transfer Operations 5 29 Table 5 13 Cont DTF Level of Support for SEARCH Command Qualifiers For IBM File Qualifier Specifications Comments INOJNUMBERS supported INOJOUTPUT file supported spec INOJREMAINING supported SINCE time supported INOJSTATISTICS supported INOJWINDOW AXn1 n2 supported 4See Section 5 10 1 for restrictions Examples MVS SEARCH LKG DTF200 GARY DTF TEXT DTF This command searches the PDS member TEXT of the GARY DTF data set located on the IBM DTF client for the string DTF It lists all the lines containing this string The OpenVMS DTF server node is LKG and the server account is DTF200 Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers VM SEARCH PARIS VMDTF DTF DTF MDADDR 181 DEFINE This command searches the file DTF DTF located on the IBM DTF dient for the string DEFINE It lists all the lines containing this string The IBM system uses the first DTF DTF file it finds regardless of mode value The OpenVMS DTF server node is PARIS and the server account is VM
15. NICK DTF USER NICK This command deletes all the data sets beginning with NICK DTF Caution is recommended when using wild cards The OpenVMS DTF server node is MYFAIR and the server account is DTFV200 Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers VM DELETE LOG PARIS DTFVM ASHFLD 1 USER ROBERT SDELETE I FILDEL PARIS DTFVM ASHFLD C 1 deleted 10 blocks SDELETE I FILDEL PARIS DTFVM ASHFLD M 1 deleted 10 blocks SDELETE I FILDEL PARIS DTFVM ASHFLD Z 1 deleted 10 blocks This command deletes all files named ASHFLD with mode 1 The server account is DTFVM the OpenVMS DTF server node is PARIS and the user account on the VM system is ROBERT Account verification on the VM system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers OpenVMS File Transfer Operations 5 17 5 9 DIFFERENCES Command To compare the contents of two disk files and create a listing of the records that do not match use the DCL DIFFERENCES commana DIFFERENCES maste filespec revision file spec Notes Unlike local OpenVMS files if the master file specification is an BM specification you must supply a revision file specification The revision file does not default to the next lower version of the master file The DIFFERENCES command assumes
16. Recoverable File Transfer OpenVMS TRANSFER DTF and IBM Clients Only 0 0 cc eee ees RMS Programming Interface OpenVMS Clients Only DCL Record Level Access and DATATRIEVE Access OpenVMS Clients Only 0 0 00 What Does the DTF Product Allow Me to Do OpenVMS DCL Commands 00 0c eee eee OpenVMS TRANSFER DTF Commands IBM DTF Panel Interface Operations IBM DTF File Transfer Commands 0065 IBM DTF Command Processor Commands DECnet ULTRIX and DECnet OSI Network File Transfer Commands trasat Geek Sale ek cakes a aries A ee enka nay hate RSX 11M M PLUS DCL Commands DECnet RSX NFT Switches 0 0 0 0 cee eee eee DECnet RSX FTS Switches 0 0 00 c cece eee XV a Coe ae ae er ee ae Cee Cee ee NODODODOOTAAHARWN 1 10 1 10 1 4 10 1 4 11 1 4 12 PATHWORKS for DOS NFT Commands PATHWORKS for OS 2 NFT Commands OpenVMS RMS Programming Access 00005 2 DTF File Specifications 2 1 2 2 2 2 1 2 2 2 2 2 3 2 2 4 2 3 2 3 1 2 3 2 2 3 3 2 4 2 4 1 2 4 2 2 4 3 2 4 4 2 4 5 2 4 6 2 4 7 Specifying Remote IBM Files for DTF FileAccess Specifying Remote DECnet Files for BM Initiated DTF File ACESS herpes tk PRE Pere hose Bde bae et eae hapa here Beale oh nee wet ea aye Specifying Remote OpenVMS Files
17. This example creates a file definition record NON_VSAM 1 in the file definition database on the default node the node defined by the last USE NODE command The values for the various file creation parameters are specified on the command line Files created using the NON_VSAM 1 file definition will not be superseded and will be placed on the minidisk with an address of 193 C 2 Displaying File Definition Attributes To display the attributes of a single file definition or a group of file definitions in the file definition database on a specified node use the SHOW FILE _ DEFINITION command SHOW FILE_DEFINITION qualifiers nodd access control filedefinition name Command Parameters node access contro The node parameter specifies the OpenVMS DTF server node where the file definition database resides If you omit the node parameter from the SHOW FILE_DEFINITION command the server node defined by the last USE NODE command is selected by default If you have not issued a USE NODE command then your current node is selected The access control parameter specifies the account name and password of an account on the server node with read and write access to all the databases The account name is usually SNADTF MGR Note Do not use an account in the OpenVMS DTF server account database for the access control parameter file definition name Specifies the user assigned name of the file definition in the definition
18. Using the DTF for IBM Command Processor 9 37 9 3 10 SET CONVERSE LONG SHORT SET Subcommand Examples The following examples show common uses of the SET subcommand Example 1 display the short form of the DTF prompt SET CONVERSE SHORT DTF0047I DTF Example 2 display the long form of the DTF prompt SET CONVERSE LONG DTF0048I ENTER CLEAR DEFINE END LIST RECALL RESUME SET SHOW OR TRANS SHOW Subcommand The SHOW subcommand is used to show the defaults used by the command processor and any values which may have been changed through use of the SET subcommand No options are available on the SHOW subcommand This is the syntax of the SH OW subcommand SHOW SHOW Subcommand Example DTF0048I ENTER CLEAR DEFINE END LIST RECALL RESUME SET SHOW OR TRANS SHOW SET NETMGR DTF4 DEBUG OFF RECOVERY N CONVERSE L NULL REJECT SET VERSION 3 1 0 DTF0048I ENTER CLEAR DEFINE END LIST RECALL RESUME SET SHOW OR TRANS 9 4 DTF Command Processor Usage Considerations As you use the DTF command processor you should be aware of certain considerations which involve using tapes and overriding the server node and server account The following sections address these considerations 9 38 Using the DTF for IBM Command Processor 9 4 1 Using Tapes MVS Systems The DTF Network Manager subsystem may not allow unmounted tapes This is an installation dependent option A tape can be mounted using the follow
19. continued on next page DTF File Specifications 2 11 Table 2 1 Cont IBM File Specification Qualifiers and Their Usage for Remote VM Files Tape Resident Qualifier CMS Files Files VSAM Files USERID 2 3 45 supported supported supported NOLUME 23 ignored supported ignored NSAM 2 3 45 ignored ignored supported This qualifier is used when reading IBM input files for copy search compare and display operations 2This qualifier is used when writing over existing IBM output files 3This qualifier is used when creating a new IBM file 4This qualifier is used when deleting an IBM file 5This qualifier is used when listing an IBM directory 6This qualifier is used only for IBM tape resident files 2 12 DTF File Specifications Table 2 2 IBM File Specification Qualifiers and Their Usage for Remote MVS Files Non VSAM Disk Resident Tape Resident Qualifier Files Files VSAM Files ALIGNMENT supported ignored ignored ALLOCATION supported ignored supported BATCHID ignored ignored ignored BLOCK_SIZE supported supported ignored CASE supported supported rejected CATALOG supported supported ignored CLASS ignored ignored ignored DEFAULT 2 3 45 supported supported supported DENSITY 236 ignored supported ignored DIRECTORY_BLOCKS supported ignored ignored FILE_DEFINITION 2345 supported supported supported HSMRECALL 49 supported supported supported IGNORE 123 supported supported supported IKEY ignored igno
20. DTF does not support append operations to files with RECFM FBS The request will be rejected e Copy a file toan IBM DTF dient and submit that file to the batch system on that IBM system Note Files submitted to IBM batch subsystems must not contain any records that exceed 80 bytes If a remote file has additional attributes besides ASCII or binary the file will lose those attributes when transferred to an ULTRIX or UNIX system ULTRIX and UNIX File Transfer Operations 10 3 Table 10 2 shows the level of support DTF provides for the DECnet ULTRIX or DECNet OSI for Digital UNIX dcp command options For more detailed information about the dcp command refer to the DE Cn amp ULTRIX Use manual or the DE Cne amp OSI for Digital UNIX Introductory User s Guide Table 10 2 DTF Level of Support for dcp Command Options For IBM File Option Specifications Comments i supported a supported A supported S supported File should not contain any records that exceed 80 bytes The file will be deleted after the submitted job completes V supported Examples MVS dcp veena dtfmvs gary dtf file transfer usr users gary dtf file This command transfers the file gary dtf file transfer located on the IBM DTF client to the output file usr users gary dtf file located on the local DECnet ULTRIX or DECnet OSI for Digital UNIX node The OpenVMS DTF server name is veena and the server account is
21. PASS SECRET SERVER TIAMAT NETMGR DTFGCS This example shows how to copy a file called MONDAY DAT from a DECnet node named WMASS to the file MONDAY DATA on the local VM system The file on the DECnet node is accessed through the SIMPSON account using the password SECRET The operation is to be done using the server TIAMAT and the Network Manager subsystem DTFGCS VM DTFRECV PROGRAM1 BIN FROM JONES AT SMAUG AS PROGRAM EXEC PASS SECRET RECOVERY Y TRANSLATE N This example shows how to copy a binary file called PROGRAM1 BIN froma DECnet node named SMAUG to the file PROGRAM1 EXEC on the local VM system The file on the DECnet node is accessed through the J ONES account using the password SECRET The file operation is done using the recovery feature Note that all binary files must be transferred with TRANSLATE set to N 8 12 Using the DTF for IBM File Transfer Commands 8 3 DTFRESUM You use this command to resume a failed recoverable transfer During the transfer you can obtain status information by typing the QUERY command DTFRESUM RETNUM resumenumber options resume number Specifies a number up to five digits long that appears in messages beginning with DTF0062I when you submit the request Options NODE Specifies the name of the dient system which is cooperating in the recoverable transfer PASS The user s password on the client node USER This is the user ID of the user on the client node NETMGR
22. Similar to the Send to Remote panel there are four categories of information that you enter on this panel The following pages describe the fields on this panel You can press PF3 to return to the Operation Selection panel without initiating the receive operation 7 10 Using the DTF for IBM Panel Interface RECEIVE this remote file FILENAME This field contains the name of the file you are copying from the remote system You must enter a file name in this field See Chapter 2 for more information on entering file names when using DTF Note If the remote client node is running Digital UNIX or ULTRIX you must enter the file name with the proper case OPTIONS There may be additional information about the remote input file that you can enter To see the panel for entering this information type the letter Y in the OPTIONS field and press the ENTER key These panels are described in Section 7 8 and Section 7 9 FROM this USER at this remote NODE NODENAME Specify the name of the node you are copying the file from in this field You can specify either a DECnet node name or an abbreviation that names an IBM system See your system programmer for a list of the DTF system abbreviations used at your site If you leave this field blank DTF displays the Remote Node Options panel see Section 7 7 The Remote Node Options panel always precedes all other panels because it determines the operating system
23. resident file DTF MAN BACKUP The OpenVMS DTF server node is DTFSVR and the server account is VAXBACKUPS The MVS user ID is DTFMAN Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers Note that the NOTRANS qualifier is required for the BACKUP command OpenVMS File Transfer Operations 5 7 VM BACKUP EXCLUDE LOGIN COM BIGGUY VMACCESS BACKUP SAVE NOTRANS SAVE _ MYSDISK BURR This command restores all the files in the save set BACKUP SAVE stored on the VM system with the exception of the file LOGIN COM The OpenVMS DTF server node is BIGGUY and the server account is VMACCESS Account verification on the VM system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers 5 4 CLOSE Command To close a file that was opened with the DCL OPEN command use the DCL CLOSE command CLOSE logical namd Table 5 3 shows the level of support DTF provides for the DCL CLOSE command qualifiers For more detailed information about the CLOSE command refer to the DCL Dictionary Table 5 3 DTF Level of Support for CLOSE Command Qualifiers For IBM File Qualifier Specifications ERRORSabd supported INO JLOG supported Example CLOSE FILE1 This command closes a file that was opened previously with the OPEN command and deassigns the logical name sp
24. s DOS operating system NFT Network File Transfer utility xxi Graphic Conventions xxii PDS REXX RRDS SMS SNADTFCFG TRANSFER DTF TSO ULTRIX OpenVMS DTF OpenVMS VSAM VTAM Partitioned Data Set Restructured Extended Executor Relative Record Data Set IBM s Storage Management Subsystem SNA DTF Configuration utility SNA DTF Transfer utility IBM s Time Sharing Option Digital s UNI X based operating system Digital resident Data Transfer Facility software The OpenVMS operating system IBM s Virtual Storage Access Method IBM s Virtual Telecommunications Access Method The following conventions are used throughout this manual Special type UPPERCASE lowercase bold lowercase italics CTRLX Return This special type in examples indicates system output or user input Uppercase letters in command lines indicate keywords that must be entered You can enter keywords in either uppercase or lowercase You can abbreviate command keywords to the first three characters or their minimum unique abbreviation Lowercase bolding is used for ULTRIX and Digital UNIX commands command options and arguments Lowercase bolded words must be entered in lowercase Lowercase italics in command syntax or examples indicate variables for which either the user or the system supplies a value Hold down the CTRL key and press the key specified by x Square brackets in command syntax statem
25. By default a standard DMCS to EBCDIC translation table is used for data translation If you specify the TRANSLATE qualifier however you can use a user defined translation table Translation using the standard translation table or a user defined translation table can occur on the OpenVMS DTF server node or on the IBM system The location of the translation is defined by the OpenVMS DTF server manager See Section F 3 for for information on translation tables If you use the NOTRANSLATE qualifier the data is transferred without being translated You might want to use this mode of translation for transferring binary or image data DTF Data Translation F 1 The RECORD_DEFINITION qualifier allows you to specify a CDD record definition to control field level translation If you use the RECORD_ DEFINITION qualifier with the TRANSLATE qualifier you can use a loadable translation table to define the way character data is translated at the field level Translation using a CDD record definition always occurs on the OpenVMS DTF server node See Section F 4 for for information on field level data translation F 2 Controlling Data Translation on IBM Initiated File Transfers Translation of data types is controlled by following e For the command processor the TRANS and RECDEF keywords e For the panel interface the TRANSLATE field of the Send and Receive panels and the RECORD DEFINITION field of the Translate Options panel e For the singl
26. CLIENTPASS Contains a value that can later be used with the RESUME subcommand and the CLIENTPASS keyword to restart the transfer from the last successful checkpoint before the transfer failed Cleared for BM to IBM transfers Using the DTF for IBM Command Processor 9 47 10 ULTRIX and UNIX File Transfer Operations This chapter describes how to use the DECnet ULTRIX and DECnet OSI for Digital UNIX file transfer commands with DTF software to transfer files between ULTRIX or Digital UNIX DTF clients and IBM DTF dients You can use the DECnet ULTRIX and DECnet OSI for Digital UNIX commands supported by DTF at any ULTRIX or Digital UNIX node in a DECnet network so long as that node can access the OpenVMS DTF server node You simply include the OpenVMS DTF server node as part of the file specification No DTF software is required at the ULTRIX or Digital UNIX client node 10 1 Transferring Files Between ULTRIX UNIX and IBM DTF Clients You can use the following DTF supported DECnet ULTRIX or UNIX commands with an IBM file specification e dcat to display the contents of IBM data sets e dcp to copy append or submit files e dls to display the contents of an IBM directory e drm to remove an IBM data set 10 2 dcat Command To display the contents of one or more files on an IBM DTF client use the DECnet ULTRIX or DECnet OSI for Digital UNIX dcat command dcat option file spec 1 file spec 2 file spec n Table 10 1 shows t
27. DMCS toEBCDIC F 3 TYPE command OpenVMS DCL 5 33 PATHWORKS for DOS NFT 12 10 PATHWORKS for OS 2 NFT 12 10 RSX 11M M PLUS DCL 11 16 F 2 1 F 2 U ULTRIX file specification format 2 8 UNIT entry field 7 25 UNIT unit spec 2 31 2 32 UPDATE RMS service call B 20 USERID entry field 7 11 7 16 USERID userid 2 32 Using DATATRIEVE A 1 Utilities software 1 2 V Version number displaying 6 20 VM Input File Options Panel entry fields MIXED CASE NAME 7 28 VM Output File Options Pane entry fields MIXED CASE NAME 7 36 PRIMARY ALLOCATION 7 36 SECONDARY ALLOCATION 7 36 VOLUME entry field 7 25 VOLUME lt vol namd 2 32 VSAM 2 33 VSAM files cluster attribute defaults D 8 copying using the CONVERT command 5 9 Index 11 VSAM files cont d specifying component allocation 2 42 creating file definitions 2 33 specifying component names 2 43 DTF naming conventions D 6 specifying file sharing 2 44 indexed file structure D 2 structures D 1 IKEY qualifier 2 20 supported as input files 3 1 naming ALTERNATE_INDEXes D 7 supported as output files 3 4 naming conventions D 5 VSAM naming conventions D 6 record level access to B 2 NSAM qualifier 2 33 relative file structure D 1 restrictions 3 8 Ww RFA qualifier 2 28 RMS programming considerations B 4 WRITE command OpenVMS DCL 5 35 B 5 Writing individual file records sample file definition 2 38 from OpenVMS DCL 5
28. DTF Product 1 9 1 4 6 DECnet ULTRIX and DECnet OSI Network File Transfer Commands e dcat display a file e dcp copy append or submit a file e dis display a file listing e drm delete an existing file 1 4 7 RSX 11M M PLUS DCL Commands e APPEND append one file to another e COPY copy a file to another file e CREATE create a new file e DELETE delete an existing file e DIRECTORY show a listing of files e SUBMIT submit a file to a batch subsystem e TYPE display a file on the terminal 1 4 8 DECnet RSX NFT Switches e no switch copy a file to another file e AP append one file to another e DE delete an existing file e LI FU AT or BR show a listing of files e SB submit a file to a batch subsystem 1 4 9 DECnet RSX FTS Switches e no switch copy a file to another file e AP append one file to another e DE delete an existing file e SB submit a file to a batch subsystem 1 10 Introducing the Data Transfer Facility DTF Product 1 4 10 1 4 11 1 4 12 PATHWORKS for DOS NFT Commands e APPEND append a file to another file e COPY copy a file to another file e DELETE delete an existing file e DIRECTORY display a file listing e SUBMIT submit a file to a batch subsystem e TYPE display a file on the terminal PATHWORKS for OS 2 NFT Commands e APPEND append a file to another file e COPY copy a file to another file e DELETE delete an existing
29. ID and password access will be denied If a site does not want to issue user IDs and passwords access through a proxy is the recommended alternative 4 4 What Is Proxy Proxy in general terms means that one person has authorization to act for another In the context of system security proxy means that one user has authorization to access another user s data without specifying a password User IDs and passwords are used when proxy accounts are not defined In addition if default proxy user IDs are implemented you do not need to specify the remote user IDs Refer to Chapter 2 for more information on the use of the USERID and PASSWORD qualifiers For information on recommended use see your system administrator or the person in charge of the proxy database 4 4 1 Benefits of Using Proxy Access Proxy allows a user on a DECnet TCP IP host or IBM system to send a file transfer request to a remote system without using a password DECnet and IBM users can specify files just by specifying accounts The benefits of using proxy access are e No need for users to remember multiple passwords e Reduction in user input on the command line e More security since passwords are not displayed on the terminal in a command procedure or on the network e Elimination of the administrative task of distributing passwords and Control of passwords by users File access through the network but with no logon capabilities 4 4 Data Se
30. OF THE KEY ER YOU DO RANSF L TO SEE MO PREVIO THAT PROC ING PROC ESSOR E MVS AN ESSOR U SF T LOW LE FIL ry E R RANS G FOR E FO CO FER THE R TH TRO ES FIN gow Oa HE ER SUBCO OR MOR PERTAI IATE T BOUT T LIST C ORDS YO OT NEED MAND RAR U E T TY Li RE INFORMAT NABLES YOU TO TRANSFER FILES BETWEEN D NODES ON THE DECNET NETWORK SES SUBCOMMANDS TO INITIATE NEW USLY FAILED TRANSFERS AND CONTROL HOW THE PERATES USE THE DEFINE SUBCOMMAND TO TRANSFER E TRANSFER L HOW AND WHERE THE TRANSFER WILL BE KEY mI E TO DESCRIBE EACH INPUT ORDS EE MORE INFORMATION ABOUT TO SE ay UBCOMMANDS T RANSFER US R TYPE H ING INVOLV TER ALL O E TRANSFER RANSFER TO SEE A TRANSFER F THE Fil i EL ESS ED A TER USE THESE SUBCOM PE HELP FOLLOWED ION ABOUT THESE SU D R ED DS TO KEEP SUBCOMMAN BEFORE YO LIST CLEA ANDS ECALL SUBCO ITH THE DE a D U USE R OR Using the DTF for IBM Command Processor 9 27 RESTARTING A PREVIOUSLY FAILED TRANSFER F A PREVIOUSLY INITIATED TRANSFER FAILED WITH A RECOVERABLE RROR YOU CAN USE THE RESUME SUBCOMMAND TO RESTART THAT TRANSFER R i AES ROM THE CHECKPOINT WHERE THE FAILURE OCCURRED THE RESUME UBCOMMAND USES A SET OF KEYWORDS TO IDENTIFY WHICH TRANSFER AILED AND WHERE
31. PROJECTS NETWORK gt DOC_PLAN FINAL 22 refers to the file DOC_PLAN of type FINAL and version 22 that is stored in the subdirectory NETWORK in the subdirectory PROJ ECTS in directory ROBERTSON on device USER 656 2 2 2 Specifying Remote RSX 11M M PLUS Files Enter the remote RSX 11M M PLUS file specification as shown The node and access control portion of the file specification were previously described in Section 2 2 node access control device lt ufd gt filenametypeversion where node access control device 2 6 DTF File Specifications is the 1 to 6 character name of the DECnet client node is optional information that can include a user ID and password is a device on the RSX 11M M PLUS system such as DL1 or DM A device name can be up to 4 characters The first two characters which must be alphabetic specify the device type the second two characters which must form an octal number specify the device unit The login procedure on the dient node can include a default for the device specification The device name must be terminated with a colon directory filename type version For example is a directory name on the RSX 11M M PLUS system A directory name can be up to 9 characters acceptable characters are A Z and 0 9 You can also use UI C based directory names which use the syntax lt g m gt The value g is the group and the value m is the group member Both values must be between 0 and 377
32. SEARCH command OpenVMS DCL 5 29 SEARCH RMS service call B 20 Searching for strings in files See Files searching for strings in SECONDARY ALLOCATION entry field 7 32 7 36 SECONDARY_ALLOCATION number of 512 byteblocks 2 28 SECURITY_DATA data 2 29 SEQUENCE NUMBER n 2 29 Server account specifying server account name 2 1 9 11 9 17 9 20 9 37 SERVER keyword 9 20 9 37 Server node specifying node name 2 1 8 5 8 10 9 11 9 17 9 20 9 34 9 37 Server software 1 2 SET QUEUE TRANSFER DTF command 6 14 SET subcommand 9 36 SHARE_OPTIONS file definition attribute 2 44 SHOW ERROR TRANSFER DTF command 6 21 SHOW FILE_DEFINITION SNADTFCFG command C 3 SHOW J OBS TRANSFER DTF command 6 17 SHOW QUEUE TRANSFER DTF command 6 19 SHOW subcommand 9 38 examples 9 38 SHOW VERSION TRANSFER DTF command 6 20 SINGLE 2 29 SMSDCLASS data dass 2 30 Index 10 SMSMCLASS data class 2 30 SMSSCLASS data class 2 30 SNADTFCFG commands ADD FILE_DEFINITION C 1 REMOVE FILE_DEFINITION C 8 SHOW FILE_DEFINITION C 3 SNADTFCFG utility 1 2 SPANNED 2 30 Strings searching for from OpenVMS DCL 5 29 SUBMIT command OpenVMS DCL 5 31 PATHWORKS for DOS NFT 12 9 PATHWORKS for OS 2 NFT 12 9 RSX 11M M PLUS DCL 11 14 SUPERSEDE 2 31 SYSTSIN DD card 9 40 T Tab characters in files 3 10 TAPE LABEL entry field 7 25 7 28 7 32 7 36 Taperesident files restrictions 3 9 9 39 specifying density 2
33. TO SMITH AT BOSTON AS TEST DAT NETMGR DTFGCS VSAMDISK 193 This example shows how to copy a VSAM file called TEST DSDS located on minidisk 193 from the local VM system to a user named SMITH at node BOSTON on a DECnet network The new filename on the DE Cnet node is TEST DAT This example requests that the subsystem DTFGCS handle the transfer and specifies that the input file is a VSAM file VM DTFSEND DMSSP MACLIB A LINERO TO GIBSON AT BOSTON AS TEST DAT This example shows how to copy the maclib member called LINERO in the maclib DMSSP on the local VM system to a user named GIBSON at node BOSTON on a DECnet network The new filename on the DE Cnet node is TEST DAT Using the DTF for IBM File Transfer Commands 8 7 8 2 DTFRECV You use this command to transfer a file from a remote system to the local MVS or VM system you are on DTFRECV input file FROM user name AT nodename AS output file options input file This parameter identifies the input file on the remote system You must know how to specify the name of the file on this system correctly see Chapter 2 This is a required parameter user name This parameter identifies the user ID name on the remote system node name This parameter identifies the node name of the remote system output file This parameter identifies the name of the output file on the local system You must specify the correct file syntax for the type of system you are on VM system
34. You can specify either an absolute time or a combination of absolute and delta times Refer to the DCL Concepts Manual for more complete information about specifying time values CHARACTERISTICS characteristic Specifies one or more queue characteristics for transferring files If you specify only one characteristic you can omit the parentheses Codes for characteristics consist either of names or of values from 0 to 127 and are installation defined Use the DCL SHOW QUEUE CHARACTERISTICS command to display the characteristics defined for your system Use the TRANSFER DTF SHOW QUEUE FULL command to display the characteristics defined for a particular queue A copy operation can execute only if each characteristic specified with the COPY command is also specified on the DTF queue If you specify a characteristic not defined for the DTF queue the job remains in a pending state In order to start your job the system manager must specify new values with the DCL SET QUEUE command using the CHARACTERISTICS qualifier A COPY command that does not list all the characteristics defined for a DTF queue executes without pending CHECKPOINT_INTERVAL interval Specifies a number in the range 1 to 65 376 that controls the number of records transferred between checkpoints during a recoverable file transfer the default interval is 1 000 records This qualifier is not supported for VSAM file transfers 6 6 OpenVMS TRANSFER DTF File Transfer
35. attribute for the INDEX subsection of the ALTERNATE_INDEX section is used here If this value is not specified then the default value is used by VSAM VSAM File Support D 3 A KRF1 PATH A DATA A INDEX D 4 VSAM File Support is the path component name for A KRF1 The value of the NAME attribute for the PATH section of the ALTERNATE_INDEX section is used here If this value is not specified then the default value is generated by DTF for IBM is the name of the base cluster and is specified on the command line is the data component name for A The value of the NAME attribute for the DATA subsection of the BASE section is used here If this value is not specified then the default value is used by VSAM is the index component name for A The value of the NAME attribute for the INDEX subsection of the BASE section is used here If this value is not specified then the default value is used by VSAM Figure D 3 File Structure for VSAM Indexed File with Multiple Keys A KRF1 PATH A KRF1 INDEX A KRF1 DATA A INDEX LKG 4263 93R D 2 DTF for IBM and VSAM Naming Conventions Names are assigned to all of the following VSAM entities File Data component Index component Alternate index VSAM File Support D 5 e Path To create any type of VSAM file you need only to specify the name of the cluster on the command line You can use a file definition to specify any of the names associated with VSAM files If
36. e If you do not database will specifies a number or character that should be stored in place of the null record The value must be specified as one of the following Cchar specifies that the indicated character should be stored in place of the null record Dnumber specifies that the indicated decimal number should be stored in place of the null record The number must be between 128 and 127 inclusive Xnumber specifies that the indicated hexadecimal number should be stored in place of the null record The number must be between 0 and FF inclusive Onumber specifies that the indicated octal number should be stored in place of the null record The number must be between 0 and 277 inclusive specifies that a single space should be stored in place of the null record specifies that the null record should be ignored that is not copied specifies no special processing will occur An error will be returned if a null record is encountered specifies no special processing will occur The record will be accepted as is specifies that an error should be returned if a null record is encountered specify a value the default specified in the server account be used e Applies only to non VSAM files e This qualifier is valid only for Digital to IBM transfers It will be ignored when copying files from IBM to Digital e VM Null records cannot be written to CMS files If a null record is encountered an error will be
37. 1 ii of the Rights in Technical Data and Computer Software clause at DFARS 252 227 7013 Copyright 1988 1996 Digital Equipment Corporation EDS Defense Limited All Rights Reserved The following are trademarks of Digital Equipment Corporation Alpha DEC DEC CMS DEC MSS DECnet DECsystem 10 DECSYSTEM 20 DECUS DECwriter DIBOL EduSystem IAS MASSBUS OpenVMS PDP PDT RSTS RSX UNIBUS VAX VAXduster VMS VT and the Digital logo IBM RACF and OS 2 are registered trademarks of International Business Machines Corporation CA ACF2 and CA TOP SECRET are registered trademarks of Computer Associates International Inc MS DOS is a registered trademark of Microsoft Corporation UNIX is a trademark of American Telephone and Telegraph Preface a ree a a en ate Chen lon Rac eh dee GRE Contents 1 Introducing the Data Transfer Facility DTF Product hu EE ee E Cree Cree Cs Cee Ces Cs Ce Coe hp aRWWWN HH Multiple User Interfaces All Clients 0005 DECnet User Interfaces 0 anaana aaa IBM User Interfaces 0 Data Translation All Clients 0 00000 ee eee Multiple File Types All Clients 000 0c eee Supported Non IBM Files 00000 e eee e ees Supported IBM Files 0 cee ees Remote J ob Submission and Post Processing All Clients Directory Capability OpenVMS Digital UNIX ULTRIX RSX 11M M PLUS MS DOS and OS 2 Clients
38. 18 9 8 9 14 specifying sequence number 2 29 9 10 9 16 specifying tape label 2 21 9 9 9 14 specifying unit 2 32 9 11 9 17 Transfer parameters EXTENDED 7 9 7 14 NETWORK SUBSYSTEM 7 4 POSTPROCESS 7 9 RECOVERABLE 7 13 SERVER NODE 7 4 TRANSLATE 7 9 7 14 TRANSFER subcommand 9 23 canceling 9 24 examples 9 26 POST keyword 9 23 prompts 9 24 TRANSFER DTF utility 1 2 commands CANCEL J OB 6 20 COPY 6 3 SET QUEUE 6 14 SHOW ERROR 6 21 SHOW J OBS 6 17 SHOW QUEUE 6 19 SHOW VERSION 6 20 DEFAULT INTERVAL value 6 14 DEFAULT RETRIES value 6 14 DEFAULT TIME value 6 14 SENTRY 6 3 exiting 6 3 invoking 6 2 MAXIMUM RETRIES value 6 15 MAXIMUM TIME value 6 15 MINIMUM INTERVAL value 6 16 qualifiers AFTER 6 6 CHARACTERISTICS 6 6 CHECKPOINT_INTERVAL 6 6 HOLD 6 7 ADENTIFY 6 7 JINTERVAL 6 7 LOG_ FILE 6 7 NAME 6 8 NOTIFY 6 8 POST PROCESSING 6 9 PRIORITY 6 9 QUEUE 6 9 RECOVER 6 9 RETRIES 6 9 SINCE 6 10 TIME 6 10 supported commands 1 9 Transferring files between MS DOS and IBM 12 1 between RSX 11M M PLUS and IBM 11 1 between OpenVMS and IBM 5 1 between OS 2 and IBM 12 1 between ULTRIX UNIX and IBM 10 1 TRANSLATE keyword 9 21 TRANSLATE qualifier F 1 TRANSLATE filespec 2 31 Translating data types F 1 Translation modes DMCS to EBCDIC F 1 field level translation F no translation F 1 F 2 Translation of Digital and IBM data types F 4 Translation tables
39. 35 sequential file structure D 1 Writing records to a file specifying buffer space for 2 42 See Files writing records to Index 12
40. 7 if you type Y in the OPTIONS field for a remote node in the Send to Remote or Receive from Remote panel This panel contains information about the remote node that DTF uses to perform transfers Fill in the appropriate fields and press the ENTER key If you did not specify any other options the transfer begins immediately You can press PF3 to return to the operation panel that invoked this panel without initiating the operation The following pages describe the fields on this panel 7 22 Using the DTF for IBM Panel Interface NODE NAME if more space is required EXTENDED NODE NAME Specify the name of the node you are copying the file to in this field You can specify either a DECnet node name or an abbreviation that names an IBM system See your system programmer for a list of the DTF system abbreviations used at your site You can enter node names that are up to 255 characters long If you made an entry on the operation panel that invoked this panel the entry will be displayed on this panel SYNTAX of remote file names follows the rules of NODE TYPE This field lets you indicate the operating system on the remote node This allows DTF to check that the file name you specify is syntactically correct for that operating system DTF fills in this field only if the name you entered in the NODENAME field on the previous panel matches an entry in the abbreviations list Otherwise DTF displays the value UNKNOWN You
41. 9 10 INNUM keyword 9 10 INPASS keyword 9 10 Input File Specification panel entry fields DENSITY 7 26 7 29 7 32 7 37 FILE DEFINITION 7 26 7 29 7 37 FILE NUMBER 7 25 7 29 7 32 7 37 MIXED CASE NAME 7 24 PASSWORD 7 11 Input File Specification panel entry fields cont d TAPE LABEL 7 25 7 28 7 32 7 36 UNIT 7 25 USERID 7 11 VOLUME 7 25 INRMT keyword 9 11 INUNIT keyword 9 11 INUSER keyword 9 11 INVOL keyword 9 12 ISPF See Panel interface K KEY position length posi tion ength 2 20 Keyed access to files 3 10 L LABEL labd 2 21 LIST subcommand 9 28 example 9 29 MDADDRESS disk address 2 21 MDMPASSWORD password 2 21 MDRPASSWORD password 2 21 MDWPASSWORD password 2 21 Minidisks specifying addresses 2 21 specifying owners 2 26 specifying passwords 2 21 MIXED CASE NAME entry field 7 24 7 28 7 30 7 36 Modifying an entry in the file definition database 2 35 MS DOS file specification format 2 7 MVS Output File Options Panel entry fields MIXED CASE NAME 7 30 NULL RECORDS 7 31 PRIMARY ALLOCATION 7 31 SECONDARY ALLOCATION 7 32 N NAME file definition attribute 2 43 NETMGR keyword 9 20 9 37 NFT commands DECnet RSX JAP 11 2 AT 11 11 BR 11 11 copy 11 4 DE 11 9 EX 11 14 FU 11 11 LI 11 11 SB 11 14 supported commands 1 10 MS DOS supported commands 1 11 OS 2 supported commands 1 11 PATHWORKS for DOS APPEND 12 2 COPY 12 3
42. 9 17 OUTUNIT keyword 9 17 OUTUSER keyword 9 17 OUTVOL keyword 9 18 RECDEF keyword 9 19 RECOVERY keyword 9 19 9 37 SERVER keyword 9 20 9 37 transfer parameter keywords 9 18 TRANSLATE keyword 9 21 Defining file names DE Cnet file specification syntax 2 4 IBM file specification syntax 2 1 MS DOS file specification syntax 2 7 OpenVMS file specification syntax 2 5 OS 2 file specification syntax 2 7 RSX 11M M PLUS file specification syntax 2 6 ULTRIX and Digital UNIX file specification syntax 2 8 DELETE command OpenVMS DCL 5 16 PATHWORKS for DOS NFT 12 5 PATHWORKS for OS 2 NFT 12 5 RSX 11M M PLUS DCL 11 9 DELETE RMS service call B 11 Deleting files See Files deleting from OpenVMS DCL 5 16 DENSITY entry field 7 26 7 29 7 32 7 37 DENSITY density 2 18 DIFFERENCES command OpenVMS DCL 5 18 Digital UNIX file specification format 2 8 DIRECTORY command OpenVMS DCL 5 20 PATHWORKS for DOS NFT 12 7 PATHWORKS for OS 2 NFT 12 7 RSX 11M M PLUS DCL 11 11 Directory listings from OpenVMS DCL 5 20 Directory listings files See Files listing a directory Index 4 Directory operations introduction 1 7 DIRECTORY_BLOCKS n 2 19 DISCONNECT RMS service call B 11 DISP keyword 9 13 DISPLAY RMS service call B 12 Displaying file definitions from the file definition database 2 35 Displaying files on a terminal See Files displaying on a terminal from OpenVMS DCL 5 33 dis DECnet ULTRIX comma
43. Batch Mode Operations 9 45 9 8 Initiating DTF Command Processor Operations from Command Procedur eSis ninn aita Aarra a EAR ME Oa E NE A EA a ane 9 45 9 8 1 Variables Set by DTF 1 aaan 9 46 vii 10 ULTRIX and UNIX File Transfer Operations 11 10 1 10 2 10 3 10 4 10 5 10 6 10 7 Transferring Files Between ULTRIX UNIX and IBM DTF GleNtSs m aii wate sa Se aie wai Ped oka dae atid ea heed dcat Command 0 cece dep Command sient pra es ete bent ete ae desea ore Remote Backup and Restore Operations dis Command 2 seca eea naa aa e ae de eee a drm Command 22 ee eee eee eee te Daher e tee Ero REDOING eiai vie beh eee tee eye tke a Fa RSX 11M M PLUS File Transfer Operations 11 1 11 2 11 3 11 4 11 5 11 6 11 7 11 8 11 9 11 10 Transferring Files Between RSX 11M M PLUS DTF Clients and IBM DTF Cleit ins AxedcGA ik 24 eid Wand ada n a ar a Qe Se APPEND Command 00 cece eee e eee teens COPY COMMANA wia a Yi Sahn dine oa eel SE ke Sash eae di CREATE Command 0 00 cece eens DELETE COMMANA ane dar aada taaa Salted gale adn dada tad DIRECTORY Command 000c eee eee eee eens SUBMIT REMOTE Command 000 cee eee eee TYPE Command asias i a aia aa eo Bede ead Gaye ad we a AETA Setting Default File Information 00000005 Error Reporting aaas asa Ea A atla i Da DEDA ets 12 MS DOS and OS 2 File Transfer Operations v
44. DELETE 12 5 DIRECTORY 12 7 SUBMIT 12 9 TYPE 12 10 PATHWORKS for OS 2 APPEND 12 2 COPY 12 3 DELETE 12 5 DIRECTORY 12 7 SUBMIT 12 9 TYPE 12 10 NODE entry field 7 16 NULL RECORDS entry field 7 31 NULL option 2 26 O OPEN command OpenVMS DCL 5 27 OPEN RMS service call B 16 Index 7 Opening files See Files opening from OpenVMS DCL 5 27 OpenVMS file specification format 2 5 OS 2 file specification format 2 7 OUTCASE keyword 9 12 OUTDEN keyword 9 14 OUTFDEF keyword 9 14 OUTFILE keyword 9 12 OUTLABEL keyword 9 14 OUTMDADDR keyword 9 15 OUTMDOWNER keyword 9 15 OUTMDPASS keyword 9 15 OUTNUM keyword 9 16 OUTPASS keyword 9 16 OUTPRIMARY keyword 9 16 OUTRMT keyword 9 17 OUTSECONDARY keyword 9 17 OUTUNIT keyword 9 17 OUTUSER keyword 9 17 OUTVOL keyword 9 18 OWNERID owne 2 26 P PASSWORD entry field 7 11 7 16 PASSWORD password 2 27 Passwords specifying IBM 2 27 PDS Se Partitioned data set PDS Post processing with TRANSFER DTF 6 9 Post processing using the panel interface 7 41 PRIMARY ALLOCATION entry field 7 31 7 36 Printer files restrictions 3 9 Proxy benefits 4 4 DECnet proxy 4 7 introduction 4 4 OpenVMS proxy 4 5 Proxy database changing default entry 2 18 PUT RMS service call B 19 Q Panel interface Data Translation Options panel 7 39 introduction 1 5 invoking 7 1 MVS Input File Options panel 7 24 MVS Output File Option
45. Digital UNIX file specification 2 8 File types supported 1 6 as input files 3 1 as output files 3 4 Digital 1 6 IBM 1 6 Files See also VSAM files adding contents to 11 2 12 2 from OpenVMS DCL 5 2 backing up from OpenVMS DCL 5 5 Files cont d closing from OpenVMS DCL 5 8 comparing contents from OpenVMS DCL 5 18 copying indexed and relative from OpenVMS DCL 5 9 copying sequential 11 4 copying sequential files from OpenVMS DCL 5 11 copying with checkpoint and recovery 6 3 creating from OpenVMS DCL 5 14 creating on an IBM system 11 7 deleting 11 9 from OpenVMS DCL 5 16 displaying on aterminal 11 16 from OpenVMS DCL 5 33 listing a directory 11 11 from OpenVMS DCL 5 20 null record handling in VM 2 26 opening from OpenVMS DCL 5 27 reading records from from OpenVMS DCL 5 28 searching for 11 11 from OpenVMS DCL 5 20 searching for strings in from OpenVMS DCL 5 29 submitting 11 14 from OpenVMS DCL 5 31 writing records to from OpenVMS DCL 5 35 FILE_DEFINITION filedefinition 2 19 FIND RMS service call B 14 FREE RMS service call B 14 FTAM file types E 6 overview E 1 restrictions E 6 FTAM append facility E 2 components E 3 copy facility E 2 Index 5 FTAM cont d delete facility E 2 directory facility E 2 FTS commands DECnet RSX JAP 11 2 copy 11 4 DE 11 9 EX 11 14 SB 11 14 supported commands 1 10 G GDG See Generation data group GDG Generati
46. FAB V_UPD Ignored U pdate access to file and explicit file extension FAB L_FOP File processing options FAB V_CBT Disallowed Contiguous best try FAB V_CIF Disallowed Create if FAB V_CTG Disallowed Contiguous FAB V_MXV Disallowed Maximize version FAB V_NFS Ignored Non file structured FAB V_OFP Disallowed Output file parse FAB V_POS Disallowed Current position FAB V_RCK Disallowed Read check FAB V_RWC Always in effect Rewind on dose applies to magnetic tape only FAB V_RWO Disallowed Rewind on open FAB V_SPL Disallowed Spool FABS V_TEF Ignored Truncate at end of file Never done B 8 RMS File System and Programming Constraints for MVS files To deallocate unused space use the RELEASE attribute or RELEASE qualifier in your file definition Always done for VM files continued on next page Table B 3 Cont CREATE FAB Input Fields Field Name Option Restriction Description FAB V_TMD Disallowed Temporary marked for delete FAB V_TMP Disallowed Temporary FAB V_WCK Disallowed Write check FAB B_FSZ Ignored Fixed control area size FAB L_MRN Ignored Maximum record number FAB B_RFM Record formats Record format indicates type of record not listed are format FAB C_FIX and FAB C_VAR disallowed are fully supported FAB C_VFC is supported only if the FAB V_PRN option in the FAB B_RAT field has been specified FAB B_RTV Ignored Retrieval window size FAB B_SHR Disallowed File sharing If FAB V_GET is specified FAB V_SHRPUT is also
47. IBM file specifications Ifthe original request involved a DECnet file that had no user ID associated with it e The CLIENTUSER keyword will be ignored in the following situations Ifthe CLIENT keyword is not used Ifthe CLIENT keyword value has access control information within it CLIENTPASS password Specifies the password for the DE Cnet file specification involved in the original transfer request 9 32 Using the DTF for IBM Command Processor password The password for the DE Cnet file specification involved in the original transfer request Length 1 to 31 characters Usage Notes If you specify the CLIENTPASS keyword the password will be visible on the screen A better alternative is to let DTF prompt you for the password which you then enter in a nondisplay field The DTF processor may prompt you to enter a password after you issue the RESUME subcommand The DTF processor prompts you to enter a client password under the following circumstances If you specified the CLIENT keyword If you specified the CLIENTUSER keyword or specified the client user ID in the access control information portion of the CLIENT keyword If you did not specify the CLIENTPASS keyword or the client password in the access control information portion of the CLIENT keyword IftheTSO profileis set to PROMPT The CLIENTPASS keyword should not be used in the following situations Ifthe original request involved two IBM
48. Mvs The TSO profile is set to PROMPT Using the DTF for IBM Command Processor 9 25 TRANSFER Subcommand Examples The following example shows you how to use the TRANSFER subcommand to transfer an input and an output file specification set up with the DEFINE subcommand The DEFINE subcommands are omitted from this example They are entered prior to the TRANSFER subcommand TRANSFER DTF0030I REQUEST SUBMITTED TO DTF1 1 DTF0037I THIS REQUEST ASSIGNED REQUEST NUMBER 00022 DTF0066I THE RECOVERABLE COPY REQUEST IS ABOUT TO BEGIN DTF0062I THIS REQUEST ASSIGNED RETRY NUMBER 00151 2 DTF0067I SERVER NODE HANDLING THE TRANSFER IS NODE1 VERSION 3 1 0 3 DTF0068I CLIENT NODE INVOLVED IN TRANSFER IS NODE1 VERSION 3 1 0 4 DTF0055I SUBSYSTEM DTF1 REPORTS COMPLETION OF REQUEST gt SNADTF S COPIED USER3 lt VMSUSER gt LOGIN COM 127 COPIED TO gt NODE1 SNADTF IBMUSER LOGIN COM USER IBMUSER PASS PASSWORD gt CHEC 1000 73 RECORDS DTF0048I ENTER CLEAR DEFINE END LIST RECALL RESUME SET SHOW OR TRANS END READY 1 This message displays the name of the DTF subsystem that receives the transfer request 2 This message is displayed after the OpenVMS dient node accepts the request and assigns a retry number This is written for a recoverable copy request only This message displays the name of the OpenVMS DTF server node 4 This message displays the name of the client node The server node and clie
49. Note To simulate a TYPE command NFT users can copy a file to the TI device Table 11 8 DTF Level of Support for TYPE Command Qualifiers For IBM File Qualifier Specifications LOG supported NOWARNINGS supported MACY 11 not supported Example MVS 11 16 RSX 11M M PLUS File Transfer Operations TYPE TENNIS PROS GARY DTF TYPE This command types the contents of the PDS member TYPE of the GARY DTF data set located on the IBM system The OpenVMS DTF server node is TENNIS and the server account is PROS Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers VM TYPE CITIES DTFVM PROFILE EXEC Al USER SAM This command types the contents of the file PROFILE EXEC A1 on the IBM system The OpenVMS DTF server node is CITIES the server account is DTFVM and the IBM user is SAM The VM password the MDADDRESS value and the MDRPASSWORD value are taken from the OpenVMS DTF server s proxy database 11 9 Setting Default File Information The DECnet RSX NFT and FTS utilities allow you to set up default file specifications for both input and output files For DTF file transfers this allows you to specify the server node and password as a partial default file specification For example FTS gt CHIEF SNADTF DF OUT FTS gt DF Destination defaults CHIEF SNADTF Source defau
50. OUTPASS Send Receive and Resume panels POST POST None FILENAME on the Post Processing Options panel RECORD_DEFINITION RECDEF None RECORD DEFINITION on the Data Translation Options panel INOJRELEASE MVS None None None RETENTION PERIOD None None None RFA None None None SECURITY_DATA None None None SEQUENCE_NUMBER INNUM NUMBER FILE NUMBER on the OUTNUM MVS Input and Output File Options panels No equivalent SERVER SERVER SERVER NODE on the Operations Selection panel AINOJSINGLE None None None SMSxCLASS MVS None None None 1Specify using the IBM file specification qualifiers described in Chapter 2 in the file name continued on next page Correspondence Between DTF for IBM Keywords and OpenVMS DTF Qualifiers G 3 Table G 1 Cont Correspondence Between OpenVMS DTF Qualifiers DTF for IBM Command Processor Keywords and DTF ISPF Entry Fields Equivalent DTF for IBM OpenVMS DTF Command DTFSEND Equivalent DTF ISPF IBM File Specification Processor DTFRECV Entry Field Qualifier Keyword DTFRESUM and DTF ISPF Panels INOJSPANNED None None None INOJTRANSLATE TRANS TRANSLATE TRANSLATE on the Send and Receive panels UNIT INUNIT UNIT UNIT and TAPE UNIT OUTUNIT on the Input and Output File Options panels USERID INUSER user name USERID on the Send OUTUSER parameter and Receive panels VOLUME INVOL VOLUME VOLUME SERIAL on OUTVOL the MVS Input and Output File Options panels VSAM None VS
51. On same OpenVMS YES node On IBM DTF dlient On another DTF client NO node OpenVMS DTF dient On any DTF client On any DTF dient NO without TRANSFER DTF This chapter describes how to use the TRANSFER DTF utility command interface to perform the following tasks Invoking the TRANSFER DTF utility Exiting from the TRANSFER DTF utility Copying files with checkpoint and recovery Defining OpenVMS DTF queue attributes Displaying the status of your file transfer jobs Displaying OpenVMS DTF queue characteristics Displaying the OpenVMS DTF software version number Canceling your file transfer jobs Displaying OpenVMS DTF error messages For information on starting the OpenVMS DTF software and on creating DTF queues see the Digital SNA Data Transfer Facility for OpenVMS Installation manual 6 1 Invoking the TRANSFER DTF Utility Invoke the TRANSFER DTF utility by entering the following command TRANSFER DTF command 6 2 OpenVMS TRANSFER DTF File Transfer Operations If you specify a command TRANSFER DTF will exit back to DCL after the requested operation completes or is queued Otherwise TRANSFER DTF will prompt you for a command with the TRANSFER DTF prompt TRANS DTF gt 6 2 Exiting the TRANSFER DTF Utility Exit the TRANSFER DTF utility by entering the EXIT command or by typing CTRL Z in response to the TRANSFER DTF prompt 6 3 Copying Files with the TRANSFER DTF Utility To transfer files between a DECnet D
52. Operations NOJHOLD Specifies whether or not a job is available for immediate processing If you specify the HOLD qualifier the job is not released for processing until you release it with a DCL SET QUEUE ENTRY command with one of the following qualifiers e NOHOLD e RELEASE NO IDENTIFY Specifies whether the COPY command displays a message containing the job number and job name of the file transfer and the name of the OpenVMS DTF queue in which the file transfer is entered The default qualifier IDENTIFY displays the job number the job name and the queue name to which the job is queued INTERVAL delta time Specifies a delta time interval applied to a recoverable copy operation The delta time is the interval that elapses before DTF attempts to resume a stalled copy operation because of a network link going down If you specify a short time interval DTF attempts to resume the transfer more frequently This qualifier is not supported for VSAM file transfers The ANTERVAL value you specify can not be less than the minimum interval specified on the queue by the system manager You can use the SHOW QUEUE FULL command to determine what this value is If you specify an INTERVAL value less than the system minimum you get an error message and the system minimum interval value is used in its place If you do not specify an INTERVAL value the system default interval is used To determine what this value is use the TRANSFER
53. Qualifiers DTF Level of Support for dcat Command Options DTF Level of Support for dcp Command Options DTF Level of Support for dls Command Options Supported RSX 11M M PLUS File Transfer Commands DTF Level of Support for APPEND Command Qualifying SWITCHES 3 ct ai ses aro nated ie at aiaa Sp eee ake ee DTF Level of Support for COPY Command Qualifying SWIECHES ec sie oari aa a 2 an Gand neta She E a TE DTF Level of Support for CREATE Command Qualifying SWICHHES a ias SA ok ee Soe bw Pa oa Bee DTF Level of Support for DELETE Command Qualifying SWICGES i Sie 25h chi ee ea ae Se a ee ae ee DTF Level of Support for DIRECTORY Command Qualifying SWICK ES joie cat tue She a E Dalen avd dea E thal Sa bree atte 2 amp DTF Level of Support for SUBMIT REMOTE Command Qualifying Switches 0 0 ccc eee eee DTF Level of Support for TYPE Command Qualifiers DAP Error COdES 5 sci res eh eda eth Gawd oe a eee DTF Level of Support for APPEND Command Switches DTF Level of Support for COPY Command Switches OpenVMS DTF Level of Support for DELETE Command SWIT oc aea toss a a a a dais de Par i aTa 2S aoa Ea DTF Level of Support for DIRECTORY Command SWIER aie ea a eed a aid E a Ba ad eat aie aea DTF Level of Support for SUBMIT Command Switch DTF Level of Support for TYPE Command Switch DAP Erro Codes esne ke roaa tee MEN eee a tre he Sl a es CLOSE FAB and XAB Inpu
54. SERIAL gt FILE NUMBER gt UNIT gt DENSITY gt DTF options FILE DEFINITION LKG 8300 93R DTF displays the MVS Input File Options panel see Figure 7 8 if you type Y in the OPTIONS field for an MVS input file in the Send to Remote or Receive from Remote pane You can press PF3 to return to the operation panel that invoked this panel without initiating the operation The following pages explain the fields on this panel FILE options MIXED CASE NAME This field specifies whether DTF should accept the case in which the file name was entered A value of Y will cause DTF to open the file in a case sensitive fashion N or blank will default to uppercase 7 24 Using the DTF for IBM Panel Interface Note This option has no effect unless NODE PARMS LOWERCASECREATE is set to ON See the CASE qualifier in Chapter 2 for information on MIXED CASE VOLUME SERIAL Specifies the volume serial number that contains the IBM input file This number can be up to 6 characters long If the input file you are trying to copy is not cataloged or you want to avoid a catalog search to find the file you should specify both the volume name and the unit name UNIT Specifies a generic device name that describes the device type that holds the IBM input file The length can be 1 to 8 characters If the input file you are trying to copy is not cataloged or you want to avoid a catalog search to find the file
55. TO RESTART THE TRANSFER ECAUSE THE SERVER NODE RETAINS MOST OF THE INFORMATION FROM THE RIGINAL TRANSFER THE RESUME SUBCOMMAND DOES NOT USE ANY OF THE FORMATION SUPPLIED WITH THE DEFINE SUBCOMMANDS TYPE HEL ESUME TO SEE MORE INFORMATION ABOUT RETRYING A FAILED TRANSFER SYNTAX DIF REQUIRED NONE DEFAULTS NONE OPERANDS NONE m1 WwW U JH O wW IKJ56804I FOR MORE INFORMATION ENTER THE HELP SUBCOMMAND NAME OR HELP HELP DTF0047I DTF Example 2 display information about the LIST subcommand HELP LIST FUNCTION THE LIST COMMAND PROCESSOR DISPLAYS ALL DEFINED PARAMETERS SYNTAX LIST REQUIRED NONE DEFAULTS NONE OPERANDS NONE DTF0047I DTF 9 3 6 LIST Subcommand The LIST subcommand allows you to display all the DEFINE subcommands you have set up but have not transferred with the TRANSFER subcommand The syntax of the LIST subcommand is aS The LIST subcommand will not display passwords Instead a representative number of asterisks will be displayed to show the presence of a password 9 28 Using the DTF for IBM Command Processor LIST Subcommand Example The following example shows how you use the LIST subcommand to check the values that were defined for a file transfer DEFINE INFILE NODE LOGIN COM INUSER VMSUSER INPASS VMSPASS DTFOO47I DT DEFINE OUTFILE IBMUSER LOGIN COM DTFOO47I DT DEF SERVER NODE1 DTF0047I DTF
56. TSOVL6 PATH NAME PAYROLL EMPNO ALTERNATE_INDEX NAME PAYROLL MAIN AIX3 INDEX NAME PAYROLL MAIN AIX3 IDX VOLUME TSOVL7 DATA NAME PAYROLL MAIN AIX3 DAT VOLUME TSOVL8 PATH NAME PAYROLL JOBCODE 2 38 DTF File Specifications The following DTF file definition entry might be used to define attributes when creating a VSAM sequential file BASE RECORD_DEFINITION CDD SALES MONTHLY VSAM YES 2 4 5 BASE and ALTERNATE_INDEX Sections The BASE section is used to specify the attributes for creating non VSAM files and VSAM clusters You must specify the BASE section BASE specifies the attributes of e non VSAM files including CMS minidisk e VSAM sequential files e VSAM relative record files e theVSAM base cluster for VSAM indexed files The ALTERNATE_INDEX section is used to specify the attributes for creating the alternate index clusters for VSAM multikey indexed files ALTERNATE_INDEX is used by IBM to create additional keys of reference for an indexed file For more information about VSAM file structure refer to Appendix D 2 4 6 INDEX DATA and PATH Subsections The INDEX and DATA subsections are components of the BASE and ALTERNATE_INDEX sections The PATH subsection is a component of the ALTERNATE INDEX section INDEX VSAM indexed files contain data records and an index that lets you access these records by way of the key field The INDEX subsection allows you to assign particular VSAM attributes to the index
57. The request will be rejected with the message 5 2 OpenVMS File Transfer Operations RMS F FOP invalid record options Table 5 1 DTF Level of Support for APPEND Command Qualifiers Qualifier For IBM File Specifications Comments ALLOCATION n BACKUP BEFORE time BY_OWNER uic NO JCONFIRM INOJCONTIGUOUS CREATED EXCLU DE filespecf EXPIRED supported not supported supported supported supported ignored supported ignored supported For IBM files enough tracks or cylinders are allocated to hold n 512 byte blocks If ALIGNMENT TRACKS is specified the allocation is in tracks if ALIGNMENT CYLINDERS is specified the allocation is in cylinders IBM files do not have a BACKUP date All IBM resident files have a UIC of 0 0 If you specify the BY _ OWNER qualifier with IBM input file specifications with a UIC other than 0 0 this qualifier is ignored lf specified an IBM file specification the qualifier is ignored 31f specified for an IBM input file specification no file will be selected 4See Section 5 10 1 for restrictions continued on next page OpenVMS File Transfer Operations 5 3 Table 5 1 Cont DTF Level of Support for APPEND Command Qualifiers For IBM File Qualifier Specifications Comments MVS JEXTENSI ON n supported For IBM files each extension allocates enough tracks or cylinders to hold n 512 byte
58. This parameter is the name of the DTF Network Manager component On VM systems the name is the 1 to 8 character virtual machine name On MVS systems the name is the 4 character subsystem ID Examples DTFRESUM RETNUM 5 NODE HARPO In this example the interrupted file operation with the retry number 5 is resumed The DECnet node involved in the transfer is HARPO DTFRESUM RETNUM 4 NODE SMOG USER JONES PASS SECRET In this example the interrupted file operation with the retry number 4 is resumed The DECnet node involved in the transfer is SMOG the user ID is J ONES and the user password is SECRET DTFRESUM RETNUM 222 NODE TOOK USER BARNEY PASS FRED In this example the interrupted file operation with the retry number 222 is resumed The DECnet node involved in the transfer is TOOK the user ID is BARNEY and the user password is FRED Using the DTF for IBM File Transfer Commands 8 13 9 Using the DTF for IBM Command Processor This chapter describes how to use the DTF command processor to transfer files It provides examples that show you how to perform the most common command processor tasks The chapter is divided into three sections e How to invoke the DTF command processor e A detailed description of the DTF command and all of the supported subcommands keywords and keyvalues that you can use to transfer files e A description of DTF command processor batch mode operations and DTF command processor operations th
59. Unsupported OpenVMS RMS Service CallS Unsupported RMS Extended Attribute Blocks Record Locking 00 cece eee eee Programming Considerations for VSAM Indexed PUlCSeice ed eke hae Cees i ace edt woe Bd Bd Programming Considerations for VSAM Relative Files Sieg a Pe Wats ve aed Ai w Seba a Pee ade es Programming Considerations for VSAM Sequential PUES ey iea8 cP Pedy hd yb alate ag PAR DAB dee amp Botha he Record Level Access to IBM Non VSAM Files Supported RMS Service Calls 00 eee eee eee CLOSE airna tae ae ae Mee ba Sve been a Sea ME aa SCONNEGT 2s o ecoecia de aeaa tule da Pum tale d earn a a tas SCREATE te i dered a ia BA aie La ahead wk aye Bh Me SDELETE wa rte Sat de da es Pea A DISCONNECT nitrace bh eee ae Rw ea eared Be DISPLAY maaie ae a teva e ne n Sara anata aonb arava sansa tages SRE WIND ia Tearrain i a tal sae ATA EE a AERA SSEARCH cc Fami a hep actin roa halide gp dace lal A cao ns accel tai foe hed A 1 A 1 A 2 A 2 A 3 B 1 B 2 B 2 B 2 B 3 B 3 B 4 B 5 B 5 B 5 B 7 B 7 B 8 B 11 B 11 B 12 B 14 B 14 B 14 B 15 B 16 B 19 B 19 B 19 B 19 B 20 B 20 C Maintaining the OpenVMS DTF File Definition Database C 1 Adding Entries to the File Definition Database C 1 C 2 Displaying File Definition Attributes C 3 C 3 Modifying a File Definition 0 0 0 c eee eee C 6 C 3 1 Modifying the File Definition BASE Se
60. VM EXCHANGE NETWORK TRANSFER_MODE RECORD FDL INDEX FDL MYFILE IDX _S O DTFVM ROLAND DTFIDX USER ROLAND MDADDR 192 MDWPASS WCMS VSAM This command copies the file MYFILE IDX on the OpenVMS system to the file ROLAND DTFIDX on the VM system The OpenVMS DTF server node is the local OpenVMS system and the server account is DTFVM The destination minidisk address is 192 and the minidisk write password is WCMS Account verification on the VM system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers Note that the TRANSFER_MODE and FDL qualifiers are required for VSAM file transfer VM EXCHANGE NETWORK LOG PARIS DTFVM DTF MACLIB MEMBER1 OWNER JIM MDRPASS SECRET USER JIM PASSWORD GUESSME MEMBER1 MACRO This command must be entered with no continuators within double quotation marks Because of line length restrictions in this manual the command is represented as a wrapped command line This command copies the maclib member MEMBERL1 to the local file MEMBER1 MACRO The server account is DTFVM the OpenVMS DTF server node is PARIS the VM user ID isJ IM and the VM password is GUESSME VM EXCHANGE NETWORK DEV LOG _S OXEN DTF TESTS EXEC USER GARY PASS 4BY4 MDADDR 192 MDWPASS XYZ This command copies the DEV LOG file located on the current OpenVMS directory to TESTS EXEC on the IBM VM system The server a
61. VM systems specify SL BLP or NL MDADDR The input file s 1 to 4 character hexadecimal minidisk address This option is valid only when transferring files from a VM system MDOWNER The input file s 1 to 8 character minidisk owner This option is valid only when transferring files from a VM system MDPASS The input file s multiwrite minidisk password This option is valid only when transferring files from a VM system For more information about minidisk passwords see the MDxPASSWORD qualifier in Section 2 3 3 NETMGR Specifies the name of the DTF Network Manager component If you specify a name the value overrides the name in the DTFUSER parameter file On VM systems the name is the 1 to 8 character virtual machine name On MVS systems the name is the 4 character subsystem name as it appears in the subsystem name table NULL The action that DTF should take when it encounters a null record during a transfer toa VM system Using the DTF for IBM File Transfer Commands 8 9 SPACE DTF inserts a record containing a single space x 40 in place of the null record REJ ECT DTF gives an error message if transferring an MVS record IGNORE DTF ignores all null records Note that the output file may have fewer records and that the null records lost will not be restored if DTF is used to transfer the file from the VM system NONE DTF accepts the records as is if transferring to an MVS system Transfers to a VM system w
62. a CMS batch machine you must provide the minidisk address and a link password in the transfer parameters so that the batch virtual machine can link to the minidisk If the minidisk is not linked and accessed you must supply a minidisk address link password and an optional owner ID to link and access the minidisk If you are copying a file from an unlinked and unaccessed minidisk use the read password unless the file is a file mode 0 file in which case follow the WRITE LINK rules When copying to an unlinked unaccessed minidisk always supply the minidisk multiwrite password e The preceding information and other usage notes are shown in Figure 2 1 and Figure 2 2 e For mode 0 read access IBM users must specify the multiwrite password using the M DM PASSWORD qualifier within the quoted file name You cannot simply specify the multiwrite password using the panel fields or the PASSWORD options 2 22 DTF File Specifications Figure 2 1 Using the MDxPASSWORD Qualifier Part 1 Does minidisk No password required require access password ignored passwords if supplied Does VMS DTF No password required account database password overrides contain minidisk default if supplied passwords Was DTF on IBM system No password required configured to supply password overrides minidisk pass default if supplied words LKG 4416A 93R DTF File Specifications 2 23 Figure 2 2 Using the
63. blocks If ALIGNMENT TRACKS is specified the extension is in tracks If ALIGNMENT CYLINDERS is specified the extension is in cylinders INO LOG supported MODIFIED supported NO NEW_VERSION not supported NOJOVERLAY supported PROTECTION code ignored NO JREAD_CHECK not supported SINCE time supported NO WRITE_CHECK not supported 2Command fails with the following error message RMS F SUPPORT Network operation not supported FAL F FOP1 File processing options field rejected 4See Section 5 10 1 for restrictions Examples MVS APPEND TEST LOG DRAGON SNADTF LOU DTF TEST This command appends the latest version of the file TEST LOG in the current OpenVMS default directory to the PDS member TEST of the LOU DTF data set The server account is SNADTF on the OpenVMS DTF server node DRAGON Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers MVS APPEND INDU IBMSYS1 ROCKY STOCK AMT USER ROCKY PASS SECRET _ STOCK QUOTE 5 4 OpenVMS File Transfer Operations This command appends the PDS member AMT of the ROCKY STOCK data set located on the IBM DTF client to the OpenVMS file STOCK QUOTE located on the current default directory The server account is IBMSYS1 on OpenVMS DTF server node INDU and the MVS user ID is ROCKY Account verificatio
64. can override this value by typing in a different operating system keyword The valid operating system names are MVS VM OpenVMS Digital UNIX ULTRIX RSX MS DOS OS 2 and TCP Note If you specified Y in the OPTIONS field for a remote file then you must enter a node type value in order to see the correct file options panel ACCESS to remote node provided by this SERVER or GATEWAY NODENAME This is the node name of the OpenVMS DTF server node providing access to the IBM DTF client system or the DECnet l nternet Gateway node providing access to the TCP network You can enter a node name only if the node type was specified as MVS VM or TCP SERVER ACCOUNT The account on the OpenVMS DTF server node that is used to perform transfers to the IBM DTF client See your OpenVMS DTF server manager for a list of accounts and IBM systems available on the OpenVMS DTF server No account is necessary to connect to a TCP IP network SERVER PASSWORD This is the password for the account on the OpenVMS DTF server node Not all OpenVMS DTF server accounts use passwords see your OpenVMS DTF server manager No password is necessary to connect to a TCP IP network Using the DTF for IBM Panel Interface 7 23 7 8 The MVS Input File Options Panel Figure 7 8 MVS Input File Options Panel COMMAND gt Fill in the required fields and press ENTER to continue FILE options TAPE options MIXED CASE NAME gt TAPE LABEL gt VOLUME
65. command displays all data sets beginning with J ONES DTF T located on the IBM system on volume DTFV1 The OpenVMS DTF server node is RABBIT and the server account is DTIFMVS Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers VM C NET FT gt DIRECTORY PARIS DTFVM HOURS MACLIB USER WARNER PASS XXXABC This command displays a list of all files in the macdlib HOURS on the VM system The OpenVMS DTF server node is PARIS and the server account is DTFVM The VM user ID is WARNER and the VM password is XXXABC 12 8 MS DOS and OS 2 File Transfer Operations Additional Information The DIRECTORY command does not accurately display information about the following fields e Size Always contains two numbers in the format nn nn The first number is always the same as the second number and does not indicate the amount of space currently in use as it should These numbers are only approximations of the number of 512 byte blocks in a file These numbers are always 0 for partitioned data set PDS members e Owner Never displayed e Created Never displayed e File protection Always indicates that system owner group and world have complete access Access is really determined by the access control information user name and password specified in the IBM file specification MVS If a file is uncataloged the
66. control characters e IBM ANSI printer control characters are not fully supported by the OpenVMS FORTRAN printer control statements e ThelBM ANSI printer triple line feed character is not recognized by OpenVMS FORTRAN printer control it is interpreted as a single line feed 3 3 5 Transferring IBM Tape Resident Files DTF does not support IBM input tapes that have a label type of NL In addition DTF for VM does not support tapes that have a label type of AL OpenVMS utilities that use the LIB FILESCAN system service cannot access IBM tape resident files This service causes an extra open and close sequence before accessing the file for the requested operation Utilities that use LIB FILESCAN include the COPY TYPE and DELETE commands Therefore you must use the TRANSFER DTF utility to access IBM tape resident input files The following restrictions apply if you use the TRANSFER DTF utility s RECOVER qualifier or the RECOVERY option in the IBM interfaces when reading and writing IBM tape resident files e The label type must be SL or AL AL not supported by DTF for VM e The MVS operating system will call for the tape to be mounted several times during the transfer To avoid having to remount the tape use the PUBLIC attribute when the tape is first mounted The VM operating system will call for the tape to be mounted once at the beginning of the transfer DTF for MVS supports tapes that have a label type of AL for both
67. corresponding qualifier in Section 2 3 3 Table 2 3 MVS File Attributes and Their Usage in the BASE and ALTERNATE_INDEX Sections VSAM INDEX VSAM VSAM BASE ALTERNATE _ and DATA PATH File Attribute Section INDEX Section Subsections Subsection BUFFERSPACE supported supported not allowed not allowed COMPONENT_ALLOCATION supported supported supported not allowed HSMRECALL supported supported not allowed not allowed IGNORE supported supported not allowed not allowed MRS supported not allowed not allowed not allowed NAME not allowed supported supported supported RECORD_DEFINITION supported not allowed not allowed not allowed REPLICATE supported supported supported not allowed RETENTION_PERIOD supported not allowed not allowed not allowed REUSE supported supported supported not allowed llf specified in a subsection overrides the value specified in the section 2 40 DTF File Specifications continued on next page Table 2 3 Cont MVS File Attributes and Their Usage in the BASE and ALTERNATE __ INDEX Sections VSAM INDEX VSAM VSAM BASE ALTERNATE _ and DATA PATH File Attribute Section INDEX Section Subsections Subsection RFA supported not allowed not allowed not allowed SECURITY_DATA supported not allowed not allowed not allowed SHARE_OPTIONS supported supported supported not allowed SMSDCLASS supported supported not allowed not allowed SMSMCLASS supported supported not allowed not allowed SMSSCLASS supported supported
68. data class SMSDCLASS management class SMSMCLASS or storage class SMSSCLASS used during storage allocation at file creation time SMS class names are 1 to 8 characters long Usage Notes These qualifiers are valid only for creating a file If you do not specify values for these qualifiers DTF for IBM supplies the defaults specified at the IBM site Prior to allocating storage DTF makes a call to the security exit to determine if you have access to the indicated storage class and management class A security violation will occur if you do not have access to the classes you specified IBM does not recommend that users code these parameters Therefore the IBM site s system programmer may have restricted the use of these parameters The IBM system programmer can specify values that will override any values you may specify Check with the IBM system programmer for more information Access to SMS files can be disabled when DTF is installed on an MVS system Check with the MVS system programmer if you receive indications that SMS files are not supported at the IBM client NO JSPANNED Specifies whether variable length records are spanned across a physical block or whether files with fixed length records are assigned the standard attribute Usage Notes This qualifier is valid only for creating a file The default qualifier is NOSPANNED You cannot append a file to fixed block standard files DSORG BS with DTF or any
69. database Maintaining the OpenVMS DTF File Definition Database C 3 The file definition you specify can include wildcard characters If you choose to use wildcards information about all file definitions with matching wildcards is displayed A percent sign indicates a single wildcard character and an asterisk indicates a wildcard string Refer to the description of the OpenVMS RTL routine STR MATCH_WILD in the DCL Dictionary for more information about wildcards Command Qualifiers BRIEF Displays only the file definition names By default the entire contents of a file definition are displayed OUTPUT file specification The name of the file where the output of the SHOW FILE_DEFINITION command is to be placed If the OUTPUT qualifier is used without an argument SYS OUTPUT is used as the default SHOW FILE_DEFINITION Examples DIFCFG gt SHOW FILE_DEFINITION BRIEF DAT File definition l RAWDATA SWD_DATA This example displays the file definition names in the database containing the string DAT The BRIEF qualifier causes only the names to be displayed rather than the entire file definition DTFCFG gt SHOW FILE_DEFINITION OUTPUT VSAM_ESDS VSAM_ESDS_FDL C 4 Maintaining the OpenVMS DTF File Definition Database This example displays the VSAM_ESDS FDL file definition The OUTPUT qualifier directs the output from this command to the VSAM_ESDS SNADTF F DL file in the current directory DIFCFG gt SHOW FI
70. dtfmvs Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers MVS dcp A veena dtfmvs mike dtf veena snadtf lendl dtf append This command appends the file mike dtf located on the IBM DTF client to the file lendl dtf append on the IBM DTF client The input file is accessed through the server account dtfmvs on the OpenVMS DTF server node veena The output file is accessed through server account snadtf on the OpenVMS DTF server node veena Server accounts snadtf and dtfmvs can point to different IBM DTF clients or to the same IBM DTF dient No password prompt will appear after this command is entered because two slashes have replaced the password 10 4 ULTRIX and UNIX File Transfer Operations VM dcp i binary a dtfsrv spot a exec user richards pass guessit notrans This command copies the file binary a on the ULTRIX system to the file a exec on the VM system The OpenVMS DTF server node is dtfsrv and the server account is spot The two slashes indicate that no password prompt will be generated The VM user ID is richards and the user password is guessit Note the use of the notrans qualifier to indicate that no data translation should occur because the file is an image file VM dcp S vmlogin com dtfsrv spot login exec user richards pass guessit This command copies
71. field The revision number will always be 0 CMS does not maintain information in the other date and time fields e VSAM files Date and time will be returned to the created and expires fields Because the IBM file system maintains a date stamp for these file structures only the time will always be returned as 00 00 00 00 MVS All files Date and time will be returned to the created and expires fields Because the IBM file system maintains a date stamp for these file structures only the time will always be returned as 00 00 00 00 5 11 EXCHANGE NETWORK Command To transfer files between a DECnet DTF client and an IBM DTF client use the DCL EXCHANGE NETWORK command EXCHANGE NETWORK input file spec output file spec The EXCHANGE NETWORK command allows you to do the following e Copy sequential files to and from IBM clients 5 24 OpenVMS File Transfer Operations e Copy indexed and relative files to and from IBM clients When indexed or relative files are copied you must use the TRANSFER_MODE RECORD and FDL DCL qualifiers The EXCHANGE NETWORK command does not support the checkpoint or recovery feature If you require the checkpoint and recovery feature use the TRANSFER DTF COPY command described in Chapter 6 See Chapter 2 for the IBM file specification syntax Table 5 10 shows the level of support DTF provides for the DCL EXCHANGE NETWORK command qualifiers For more detailed information about
72. file e DIRECTORY display a file listing e SUBMIT submit a file to a batch subsystem e TYPE display a file on the terminal OpenVMS RMS Programming Access e CLOSE e CONNECT e CREATE e DELETE e DISCONNECT e DISPLAY e ERASE e FIND e FREE e GET e OPEN e PARSE e PUT Introducing the Data Transfer Facility DTF Product 1 11 e RELEASE e REWIND e SEARCH e UPDATE 1 12 Introducing the Data Transfer Facility DTF Product 2 DTF File Specifications This chapter covers in detail the DTF file specification syntax for remote file names On DECnet clients the commands used to invoke DTF are the commands usually used for network file transfer To use DTF you substitute an IBM VM or MVS file specification for one or more of the file names in any DTF supported file transfer command On IBM clients remote file specifications are entered using mechanisms available in each interface File specifications are entered directly only when you wish to specify an option not available in the interface 2 1 Specifying Remote IBM Files for DTF File Access To specify a remote IBM file to DTF use the following syntax For OpenVMS RSX 11M M PLUS MS DOS and OS 2 clients node access control ibm filename ibm file spec qualifiers For ULTRIX and Digital UNIX clients node access control ibm filename ibm file spec qualifiers For IBM clients ibm filename ibm file spec qualifiers The surroun
73. file resides The file mode number specifies the access mode 0 6 to be used DTF for IBM ignores the file mode letter and defaults the file mode to 1 if the file mode parameter is not specified maclib member specifies an optional maclib member name that must be enclosed in parentheses and must be 1 to 8 characters long Use the name stored in the madib directory No checking is done for MACRO MEND or COPY statements If this option is specified then the file type must be specified as MACLIB For example PROG EXEC Al references the file PROG of type EXEC using access mode 1 Note that the mode letter A is ignored MVS ibm filename specifies an IBM MVS sequential file name or a VSAM file name All MVS file names have the following syntax name pds member or gdg number where name specifies either a qualified or unqualified file name An unqualified file name must be 1 to 8 characters long and must begin with an alphabetic character A qualified file name consists of a series of unqualified segments separated by periods Each unqualified segment must follow the syntax rules for an unqualified file name The entire qualified file name can be up to 44 characters long Tape resident file names are further limited see Section 3 3 5 Many IBM sites require you to use your user ID as the first segment in a qualified file name This is not required by DTF but if this convention is required by your s
74. file spec switches or the standard FTS command output file spec switches nput file spec switches These commands allow you to do the following e Copy a sequential file from any IBM DTF client to any location in a DECnet network e Copy a sequential file from any location in a DECnet network to any IBM DTF client e Copy a sequential file from any IBM DTF client to any other IBM client By using an IBM file specification as either the input file the output file or both you can initiate a transfer to or from that IBM file See Chapter 2 for the IBM file specification syntax 11 4 RSX 11M M PLUS File Transfer Operations Table 11 3 shows the level of support DTF provides for the COPY command qualifying switches of the various file transfer interfaces For more detailed information about the COPY commands refer to the DE Cne amp RSX Guide to User Utilities Table 11 3 DTF Level of Support for COPY Command Qualifying Switches For IBM File DCL COPY Qualifier NFT Switch FTS Switch Specifications CONCATENATE ME i supported CONTIGUOUS CO l not supported DATA_TYPE ASCII AS AS supported DATA_TYPE IMAGE IM AM supported LOG LO filespec LO filespec supported MACY11 RAT MACY11 2 not supported NEW_VERSION INV not supported NO_SPAN RAT NOSPAN 2 ignored OWNER uic F O owner not supported PRINT SP not supported PROTECTION code PR pr info not supported REPLACE SU supported SUBMIT SB suppor
75. file specifications Ifthe original request involved a DECnet file specification that had no password associated with it The CLIENTPASS keyword will be ignored in the following situations If you did not specify the CLIENT keyword If you specified the CLIENT keyword with access control information that contains a password If you did not specify the CLIENTUSER keyword and the CLIENT keyword contains no access control information CLIENT node Identifies the client node that was specified for the DE Cnet file involved in the original TRANSFER subcommand Using the DTF for IBM Command Processor 9 33 node The node portion of the DECnet file specification that was involved in the original TRANSFER subcommand Length 1 to 64 characters Usage Notes e The CLIENT keyword should not be used if the original request involved two IBM files e f you specify the CLIENT keyword but do not specify the node keyvalue the DTF command processor will use the SERVER value for the CLIENT keyvalue In this case no CLIENTUSER or CLIENTPASS keyvalues will be associated with the CLIENT keyword e The node specification can contain OpenVMS access control information however this is not recommended because the DECnet password will be visible on the screen The recommended method of specifying access control information is to use the CLIENTUSER keyword and let DTF prompt you for the password NETMGR component name Specifies the
76. file specifications have a file name a file type and optionally a file mode and may be VM maclib members MVS files may be Partitioned Data Set members Refer to your local operating system file system manuals for information on how to specify the correct file syntax Options CHECKPOINT Sets the number of logical records between checkpoints The number of logical records can be from 1 to 65535 Note If you do not specify a value for this option the TRANSFER DTF utility uses a default value of 1000 The CHECKPOINT option is valid only if you specify the RECOVERABLE option as YES If you specify the RECOVERABLE option as NO DTF does not permit you to enter a value in the CHECKPOINT field DENSITY The density of the tape containing the output file The value must be either 1600 or 6250 8 8 Using the DTF for IBM File Transfer Commands DISP This option specifies the disposition of the new file You can choose one of the following three values 1 NEW 2 OLD 3 REP NEW creates a new output file If a file with the same name already exists DTF does not copy the file This is the default OLD creates a new output file that overlays an existing file of the same name If the file does not exist DTF issues an error message REP creates a new output file even if a file with the same name already exists LABEL The type of tape labels used on the output file s tape For MVS systems specify SL AL BLP or NL For
77. for IBM OpenVMS DTF Command DTFSEND Equivalent DTF ISPF IBM File Specification Processor DTFRECV Entry Field Qualifier Keyword DTFRESUM and DTF ISPF Panels Server s node and access INRMT None SERVER NODE control information OUTRMT SERVER ACCOUNT and SERVER PASSWORD on the Network Node Options panel IBM file name INFILE file and FILENAME on the OUTFILE node name Input and Output File parameters Options panels ALIGNMENT MVS None None None ALLOCATION OUTPRIMARY None PRIMARY SE CONDARY OUTSECONDARY ALLOCATION on Output File Option panels 1Specify using the IBM file specification qualifiers described in Chapter 2 in the file name continued on next page Correspondence Between DTF for IBM Keywords and OpenVMS DTF Qualifiers G 1 Table G 1 Cont Correspondence Between OpenVMS DTF Qualifiers DTF for IBM Command Processor Keywords and DTF ISPF Entry Fields Equivalent DTF for IBM OpenVMS DTF Command DTFSEND Equivalent DTF ISPF IBM File Specification Processor DTFRECV Entry Field Qualifier Keyword DTFRESUM and DTF ISPF Panels BLOCK_SIZE MVS None None None CASE INCASE None MIXED CASE NAME OUTCASE on Input Output File Option panels CATALOG MVS None None CATALOG on the MVS Output File Options panel DEFAULT None None None DENSITY INDEN DENSITY DENSITY on the Input OUTDEN and Output File Options panels Cho
78. in Section 7 8 and Section 7 9 TO this USER at this remote NODE NODENAME Specify the name of the node you are copying the file to in this field You can specify either a DECnet node name or an abbreviation that names an IBM system See your system programmer for a list of the DTF system abbreviations used at your site If you leave this field blank DTF displays the Remote Node Options panel see Section 7 7 The Remote Node Options panel always precedes all other panels because it determines the operating system at the remote node If an abbreviation will not fit in the space provided leave the field blank and specify the abbreviation on the Remote Node Options panel USERID Specifies the user ID that should be used to access the output file on the remote system See Section 4 2 for information on user ID syntax 7 6 Using the DTF for IBM Panel Interface Note If the remote client node is running Digital UNIX or ULTRIX you must enter the user ID with the proper case PASSWORD Specifies the password of the user ID on the remote system See Section 4 2 for information on password syntax Note If the remote client node is running Digital UNIX ULTRIX you must enter the password with the proper case OPTIONS There may be additional information about the remote node that you can specify To see the panel for entering this information type the letter Y in the OPTIONS field and press the ENTER key This pane
79. in an IBM environment Because the CMS file system does not support null length records DTF cannot write them to the indicated device For more NULL 9 36 Using the DTF for IBM Command Processor information about the NULL option see the NULL qualifier description in Chapter 2 SPACE A 1 byte record is inserted in place of the zero length record The one byte is set to an EBCDIC space character x 40 REJECT The file transfer is rejected with an invalid record length message IGNORE The null record is simply ignored when writing the file The result is that the output file has fewer records than the input file NONE e vM Null records cannot be written to CMS files If a null record is encountered an error will be returned e MVS The record will be accepted as is YES RECOVERY NO A required keyword that specifies whether the transfer is executed in recoverable mode or nonrecoverable mode Chapter 1 provides additional information about recoverable copy YES The transfer executes in recoverable mode NO The transfer executes in nonrecoverable mode SERVER node Selects the server session to which the transfer request is sent for execution node The node name of the node running the OpenVMS DTF server software NETMGR dif name A required keyword that specifies which DTF Network Manager subsystem should receive the transfer request The syntax of the SET subcommand is
80. index components clusternameDATA for data components where clustername is the first portion qualifier of the qualified file name used in the TRANSFER DTF COPY command or the CONVERT command D 6 VSAM File Support D 2 3 Choosing Your Own Name for ALTERNATE_INDEX An alternate index is BM s data structure for defining a key of reference IBM and DTF do not keep track of the KRF sequence For example suppose an RMS indexed file has three keys Offset of Key in Data Record Length of Key 0 5 KRF 0 primary key 7 3 KRF 1 first alternate 15 8 KRF 2 second alternate RMS would store the following data as part of the prolog information The key field for KRF 0 begins at position 0 and has a length of 5 and KRF 1 begins at offset 7 while KRF 2 begins at offset 15 Since IBM does not maintain the KRF order another mechanism is required to preserve this order when an RMS indexed file is copied to the IBM system DTF for IBM uses the alternate index cluster name to assign the KRF value When an IBM indexed file is opened by DTF DTF collects all the alternate index cluster names associated with the file It then sorts by the full alternate index cluster name and uses the position of the name within the list of names to determine the KRF value So if you wanted to maintain the RMS KRF order when copying the previous file to the DTF for IBM system you might specify the following alternate index cluster names Offset of Ke
81. information provided An absolute path name is prefixed by a slash filename is an alphanumeric string of up to 256 characters that identifies a file A file name cannot contain any colon characters or any slashes before a colon Example of an absolute path usr rogers report txt refers to the file report txt that is accessed using the path usr rogers Example of a relative path dnnode jones passwd bin chess refers to the file chess that is accessed using the path jones bin 2 8 DTF File Specifications 2 3 IBM File Specification Qualifiers You can use the IBM file specification qualifiers described in this section to supply attributes that are unique to IBM files When you specify IBM file specification qualifiers with a value you must use a colon to separate the qualifier from the value If you use an equals sign as a separator instead of a colon your request is rejected and the following message is displayed SYSTEM F NOSUCHOBJ Network object is unknown at remote node A user entering a DIRECTORY command and incorrectly entering an equals sign in the IBM file specification will observe the following dir O snadtf file user owner Directory O snadtf file user owner Total of 1 file For ULTRIX and Digital UNIX client nodes only All qualifiers in this chapter are shown in uppercase letters Unlike typical Digital UNIX or ULTRIX commands ULTRIX client users may use either
82. line define SNA_TRANSPORT_ORDER tcp decnet If you want the software to never try the DECnet transport and to try only the TCP IP transport you can enter the following command line define SNA_TRANSPORT_ORDER nodecnet tcp If you want the software to never try the TCP IP transport and to try only the DECnet transport you can enter the following command line define SNA_TRANSPORT_ORDER decnet notcp Note If the SNA_TRANSPORT_ORDER logical is not defined the default transport order for OpenVMS Alpha will be decnet tcp and the default transport order for OpenVMS VAX will be local decnet tcp Specifying TCP IP Hostnames If you want to specify a full path hostname the hostname must be enclosed in a pair of double quotes for example foo bar company com If you want the TCP IP transport to be used as the preferred transport without specifying a TCP IP full path hostname then define the SNA_TRANSPORT _ ORDER with tcp as the first element in the transport list If the hostname ends with a single full colon then the TCP IP transport will be used for example foo or foo Note If you specify a double full colon you force the DE Cnet transport to be used for example foo or foo Manual Structure This manual is divided into the following twelve chapters and seven appendixes Chapter 1 Introduces the DTF software and describes the OpenVMS DTF software compo
83. name must be terminated with a colon is a directory name on the OpenVMS system A directory name can be up to 39 characters acceptable characters are alphanumeric characters the underscore _ and the dollar sign Subdirectories can be specified by entering a chain of up to 8 directory names each separated by a period The login procedure on the dient node can include a default for the directory specification In OpenVMS the entire directory name is enclosed with square brackets This symbol is not available in the EBCDIC character set therefore angle brackets lt gt are substituted DTF File Specifications 2 5 filename type version For example is a character string that names the file This string can be up to 39 characters acceptable characters indude alphanumeric characters the underscore _ and the dollar sign The file name is terminated with a period is a character string that identifies the file type This string can be up to 39 characters acceptable characters include alphanumeric characters the underscore _ and the dollar sign iS an optional file version number The version number is a decimal number between 1 and 32767 Multiple versions can exist the latest version of a file is the one with the highest version number If the file specification includes a version number that number is separated from the file type by a semicolon USERS 656 lt ROBERTSON
84. octal The login procedure on the dient node can indude a default for the directory specification In RSX 11M M PLUS the entire directory name is enclosed with square brackets This symbol is not available in the EBCDIC character set therefore angle brackets lt can be substituted is a character string that names the file This string can be up to 9 characters acceptable characters are A Z and 0 9 The file name is terminated with a period is a character string that identifies the file type This string can be up to 9 characters acceptable characters are A Z and 0 9 is an optional file version number The version number is a decimal number between 1 and 32767 Multiple versions can exist the latest version of a file is the one with the highest version number If the file specification includes a version number that number is separated from the file type by a semicolon DL2 lt PHIL gt DOCPLAN FINAL 22 refers to the file DOCPLAN of type FINAL and version 22 that is stored in the directory PHIL on device DL2 2 2 3 Specifying Remote MS DOS or OS 2 Files Enter the remote MS DOS or OS 2 file specification as shown The node and optional access control portions of the file specification were previously described in Section 2 2 The file name portion of the file specification must be enclosed in double quotation marks as shown node access control drive directory fileaametype where nod
85. optional if you have the minidisk linked and accessed For more information on minidisk passwords see the MDxPASSWORD qualifier description in Section 2 3 3 FILE options VSAM If the input file is VSAM format you must indicate this by typing a Y in this field TAPE UNIT If the input file is on tape you must indicate this by specifying a tape unit in this field The TAPE UNIT must match what is defined in the DTFUSER PARMS for NODEPARMS TAPEUNITS An IBM site can use additional or different unit names Check with the system programmer of the site where the input file resides to get the unit names in use at the site MIXED CASE NAME This field specifies whether DTF should accept the case in which the file name was entered A value of Y will cause DTF to open the file in a case sensitive fashion N or blank will default to uppercase Note This option has no effect unless NODEPARMS LOWERCASECREATE is set toON See the CASE qualifier in Chapter 2 for information on MIXED CASE TAPE options TAPE LABEL Specifies the format of the tape label on the tape that is read You can specify one of the following tape labels AL ANSI V1 labels or ISO ANSI FIPS V3 labels 7 28 Using the DTF for IBM Panel Interface SL Standard labels Tape restrictions may apply You should fill in this field only if the input file resides on a tape If the input file resides on disk DTF ignores this field If you do not specify this fi
86. output file will be created DTF supports the following OpenVMS file types as output e Sequential This file format will be created if the input file has either an IBM sequential or VSAM ESDS organization e Relative This file format will be created if the input file has a VSAM RRDS file organization This file organization is not supported in recoverable mode e Indexed This file format will be created if the input file has a VSAM KSDS file organization This file organization is not supported in recoverable mode DTF supports only RSX 11M M PLUS sequential files as output The Digital UNIX ULTRIX OS 2 and MS DOS operating systems can create only files that have a sequential organization DTF supports sequential files as output on these systems 3 2 2 Supported Record Formats An MVS or VM file created during a transfer will have the record format of the input file DTF supports the following record formats for output e Fixed No restrictions Note OpenVMS fixed format records are converted to variable format records when transferred to VSAM sequential files DTF Supported File Types 3 5 e Variable A variable length record file will be created if the input OpenVMS file has a record format of V or VFC or if the file is transferred from an Digital UNIX ULTRIX MS DOS or OS 2 system Any fixed printer control characters in a record will not be written to the file e Variable spanned A variable spann
87. residing on an IBM client use the DCL TYPE command TYPE file spec Table 5 15 shows the level of support DTF provides for the DCL TYPE command qualifiers For more detailed information about the TYPE command refer to the DCL Dictionary OpenVMS File Transfer Operations 5 33 Table 5 15 DTF Level of Support for TYPE Command Qualifiers For IBM File Qualifier Specifications Comments BACKUP not supported BEFORE time supported BY_OWNER uic supported All BM resident files have a UIC of 0 0 If you specify the BY_OWNER qualifier with both OpenVMS and IBM input file specifications with a UIC other than 0 0 this qualifier affects only the OpenVMS input file specification INOJCONFIRM supported CREATED supported EXCLUDE filespec ignored EXPIRED supported MODIFIED supported INOJOUTPUT file supported spec NO PAGE supported SINCE time supported z lf specified an IBM file specification the qualifier is ignored 31 specified for an IBM input file specification no file will be selected 4See Section 5 10 1 for restrictions Example MVS TYPE TENNIS PROS GARY DTF TYPE This command types the contents of the PDS member TYPE of the GARY DTF data set located on the IBM DTF client The OpenVMS DTF server node is TENNIS and the server account is PROS Account verification on the MVS system is installation dependent Contact your syst
88. site INUSER user id Specifies the user ID used to access the input file user id The user ID used to access the input file The syntax of the input file will determine the format of the user id keyvalue DECnet The logon ID to use when contacting the client node Length 1 to 40 user ID characters IBM The logon ID to use when the DTF Network Manager verifies access to the user ID input file Length 1 to 8 characters Using the DTF for IBM Command Processor 9 11 Usage Notes e If the remote client node is running Digital UNIX or ULTRIX you must enter the user ID with the proper case e f you specified the INFILE keyword with access control information the DTF command processor will ignore this keyword INVOL volume serial number Specifies a volume serial number that contains the IBM input file volume serial number A volume serial number that contains the IBM input file Length 1 to 6 characters Usage Notes e If theinput file is not cataloged you should specify this keyword e To avoid a catalog search to find the file you should specify this keyword 9 3 2 2 Keywords and Keyvalues for Specifying the Output File The following sections explain the keywords and keyvalues that describe the output file created or overlaid during the transfer OUTCASE This field specifies whether DTF should accept the case in which the file name was entered A value of Y will cause DTF to open the file in a case sensitive
89. specification using the qualifiers described in Chapter 2 or a local file specification the file is submitted to the batch subsystem on the indicated IBM system or to the local batch subsystem Several messages are written to the terminal to indicate the status of the transfer request The following messages are the most important DTFM037I THIS REQUEST ASSIGNED REQUEST NUMBER xxxxx The xxxxx value indicates the internal request number assigned by the DTF Network Manager subsystem Use this number when you report problems to the IBM system support staff They use the number to locate a variety of trace information DTFM062I THIS REQUEST ASSIGNED RETRY NUMBER yyyyy The yyyyy value indicates the retry number assigned by the DECnet client node Use this number if the transfer request fails and you want to issue a retry request later The yyyyy value is used as the rery number keyvalue of the RETNUM keyword with the RESUME subcommand Note The DTF processor displays this message only if you specified RECOVERY YES Using the DTF for IBM Command Processor 9 23 DTFM055I SUBSYSTEM zzzz REPORTS COMPLETION OF REQUEST Processing has completed This is followed by messages from the server node that report the outcome of the transfer request The Digital SNA Data Transfer Facility for OpenVMS Problen Solving and Messages provides more information about messages from the server node After displaying the DTF M0551 message and the r
90. the EXCHANGE NETWORK command refer to the DCL Dictionary Table 5 10 DTF Level of Support for EXCHANGE NETWORK Command Qualifiers For IBM File Qualifier Specifications Comments BACKUP not supported z BEFORE time supported BY_OWNER uic supported All BM resident files have a UIC of 0 0 If you specify the BY_ OWNER qualifier with both OpenVMS and IBM input file specifications with a UIC other than 0 0 this qualifier affects only the OpenVMS input file specification INOJCONFIRM supported CREATED supported EXCLUDE filespecf ignored EXPIRED supported MODIFIED supported INO LOG supported SINCE time supported TRANSFER_MODE mode supported llf specified for an IBM file specification the qualifier is ignored 31f specified for an IBM input file specification no file will be selected 4See Section 5 10 1 for restrictions OpenVMS File Transfer Operations 5 25 Examples MVS EXCHANGE NETWORK RABBIT DTF PRIMA ACCOUNTS PAYABLE ACCOUNTS_P DAT This command copies the PDS member PAYABLE of the PRIMA ACCOUNTS data set located on the IBM DTF client to the ACCOUNTS P DAT file located on the current OpenVMS directory The OpenVMS DTF server node is RABBIT and the server account is DTF Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers
91. the IBM file specification syntax Table 11 6 shows the level of support DTF provides for the DIRECTORY command qualifying switches of the various file transfer interfaces For more detailed information about the DIRECTORY commands refer to the DECne amp RSX Guide to User Utilities RSX 11M M PLUS File Transfer Operations 11 11 Table 11 6 DTF Level of Support for DIRECTORY Command Qualifying Switches DCL DIRECTORY For IBM File Qualifier NFT Switch Specifications NOWARNINGS NM supported OUTPUT filespec 2 supported WIDTH supported 10peration not available 2Specify an output file in the command line Examples MVS SDIR ATTRIBUTES ONE SNADTF BILL RSX USER BILL PASS DOLLAR Directory ONE ETSOVI 13 JUN 91 15 47 53 BILL RSX TEST USER BILL Size 94 94 Created lt none_specified gt Owner Revised lt none_specified gt Expires lt none_specified gt File protection System RWED Owner RWED Group RWED World RWED File organization Sequential File attributes Allocation 94 Record format Variable length maximum 251 bytes Record attributes Carriage return Total of 94 94 blocks in 1 File This command displays all the fields for all files containing BILL RSX in the beginning of their names for the user BILL The password for the user account is DOLLAR The OpenVMS DTF server node is ONE and the server account is SNADTF VM DIR BRIEF CANDY DTFVM FILE1 US
92. this field and the output file resides on tape the DTF command processor will assume that standard tape labels are used OUTMDADDR owner name VM If the minidisk where the output file will reside is not currently linked and accessed then use this keyword to supply the address of the minidisk This may refer to a minidisk you own or one owned by the user ID specified in the OUTMDOWNER keyword OUTMDOWNER owner name M The owner of the minidisk which you would like to have own the output file If you own the minidisk then you do not need to use this keyword OUTMDPASS owner name M If the minidisk where the output file will reside is not currently linked and accessed use this keyword to supply the multiwrite minidisk password to the minidisk identified with the OUTMDADDR keyword For more information about minidisk passwords see the MDxPASSWORD qualifier in Section 2 3 3 Using the DTF for IBM Command Processor 9 15 OUTNUM file number Specifies a sequential file number on tape It is valid only with an IBM output file file number A file number on a tape volume number from 1 to 9999 Usage Notes e Tape restrictions may apply Section 9 4 1 describes these restrictions e Ifthe output file resides on disk the DTF command processor will ignore the OUTNUM keyword e f you do not specify this keyword and the output file will be written to tape the DTF command processor will default to OUTN
93. to specify the name of a file definition contained in the OpenVMS DTF server s file definition database Any file specification qualifiers included with the FILE_ DEFINITION qualifier add to or override the qualifiers set up in the file definition Note You must use the file definition method described in Section 2 4 to specify certain VSAM file qualifiers Refer to the IBM J CL Reference manual for a complete description of MVS file names or the CMS Primer manual for a complete description of VM file names 2 2 Specifying Remote DECnet Files for IBM Initiated DTF File Access Remote DE Cnet file specifications must contain a client node or TCP IP host name and any associated access control string followed by a double colon at the beginning of the file specification If a file specification does not begin with a client node specification the DTF command processor assumes that the file is a remote IBM file name Note DTF does not support DE Cnet node to DE Cnet node file transfers Use the standard DECnet file transfer utilities for this purpose 2 4 DTF File Specifications A remote DE Cnet file specification has the following general format node access control operating system speci fic filename where node access control operati ng system speci fic filename is the name of the DECnet client node The client node name can be either the DECnet node name or the DECnet duster alias The
94. user ID of 1 to 8 alphanumeric characters to verify access through the appropriate IBM security system Usage Notes e The default is not to supply a user ID e Donot specify this qualifier if the IBM site does not use a security system e The use of this qualifier depends on whether a proxy database is set up See Chapter 4 for more information VOLUME vol name Specifies a user defined volume serial name of 1 to 6 alphanumeric characters for creating an IBM data set on MVS and VM clients or reading an uncataloged IBM data set on MVS clients You can include a total of 252 alphanumeric characters The parentheses are required if more than one volume serial name is supplied Usage Notes e The default is not to supply a volume serial name 2 32 DTF File Specifications e MVS A volume name is required for reading uncataloged data sets If a volume name is not specified for MVS output files the MVS operating system determines where the file will be located A total of 42 volumes can be specified with the VOLUME qualifier e vm A volume name is required for accessing specific tape resident data sets Omit the qualifier if the IBM operator is mounting a scratch tape for the requested operation The qualifier is ignored in all other cases Only 1 volume can be specified with the VOLUME qualifier NO VSAM Specifies whether an IBM file is a VSAM file Usage Notes e vM This qualifier is requ
95. you do not specify a name for a particular entity the default values described in the following sections are used D 2 1 DTF for IBM Naming Conventions As noted previously DTF for IBM will generate the default names for the alternate index and path components This is because VSAM does not provide defaults for these components The following conventions are used by DTF for IBM e The name of the alternate index cluster component is the name of the base cluster followed by Annnn for example FILE NAME A0001 where nnnn corresponds to RMS s key of reference KRF e The name of the path component is the name of the base cluster followed by Pnnnn for example FILE NAME P0001 where nnnn corresponds to RMS s KRF For each additional key defined for the file an additional pair of names for the alternate index cluster and path component is generated The last four digits of those names will correspond to the RMS KRF number If the six characters appended to the base cluster name cause DTF for IBM to generate a name that is longer than 44 characters then the base cluster portion of the name is truncated so that the resulting name truncated base cluster name and appended characters does not exceed 44 characters D 2 2 VSAM Naming Conventions If names for the data and index components are not specified in a file definition at creation time then VSAM will generate these names using the following algorithm clusternamelNDEX for
96. you should specify both the volume name and the unit name TAPE options TAPE LABEL Specifies the format of the tape label on the tape that is read You can specify one of the following tape labels AL ANSI V1 labels or ISO ANSI FIPS V3 labels SL Standard labels e Tape restrictions may apply e You should fill in this field only if the input file resides on a tape e If the input file resides on disk DTF ignores this field e If you do not specify this field and the input file resides on tape DTF assumes that standard tape labels are used FILE NUMBER Specifies a sequential file number on tape between 1 and 9999 e Tape restrictions may apply e If the input file resides on disk DTF ignores this field e If you do not specify this field and the input file resides on tape DTF assumes that the FILE NUMBER is 1 Using the DTF for IBM Panel Interface 7 25 DENSITY Specifies the density of the tape volume from which the input file is read Accepted values are 1600 or 6250 e Tape restrictions may apply e If theinput file is not on tape DTF ignores this field e f you do not specify this field and the input file is on tape DTF assumes the highest density allowed for the tape unit DTF options FILE DEFINITION Specifies the name of an entry in the DTF file definition database on the OpenVMS DTF server node Chapter 2 explains file definition records 7 26 Using the DTF for IBM Panel Interface 7 9 The VM Input Fi
97. 1 day defines the queue s default time attribute The value day hh mmiss cc specifies the time a transfer operation can exist before it is aborted If the assigned time is exceeded during a copy operation however the job is not aborted and finishes copying You cannot set a default time value that is more than the value for the queue s maximum time attribute By default the default time value is 1 00 00 00 00 1 day MAXIMUM option You can use the MAXIMUM qualifier with the following options e RETRIES e TIME time The definitions for the options that you can use with the MAXIMUM qualifier are RETRIES defines the queue s maximum retries attribute The value n specifies the maximum retries a user can request with the RETRIES qualifier If the number specified with the RETRIES qualifier on the COPY command is greater than the queue s maximum retries value the rate specified with the COPY command is ignored and the queue s maximum retries value is used in its place To clear the maximum retries attribute enter the word RETRIES without typing a number after the equals sign as in the following example SET QUEUE MAXIMUM RETRIES OpenVMS TRANSFER DTF File Transfer Operations 6 15 TIME time defines the queue s maximum time attribute The value time specifies the maximum time a user can request with the TIME qualifier If the value specified with the TIME qualifier on the COPY command
98. 234 is state submitted on 20 JUL 1984 15 50 24 by SMITH Command COPY NOTIFY BOSTON SMITH password DTFTEST A USER SMITH Last error No error has occurred Elapsed time 0 01 10 51 Number of Retries 2 Maximum time 3 00 00 00 Maximum Retries 100 6 18 OpenVMS TRANSFER DTF File Transfer Operations BOSTON SMITH password DQA0 SMITH DTFTEST A 3 Transferred 64 blocks out of 872 blocks for the current file 6 6 Displaying OpenVMS DTF Queue Characteristics To display the name and characteristics of the queues to which DTF jobs are submitted use the TRANSFER DTF SHOW QUEUE command SHOW QUEUE quwienamd qualifiers Command Parameter queue name Specifies an OpenVMS DTF queue name The queue name must be an OpenVMS DTF queue name If you do not specify a queue name DTF displays information about all the OpenVMS DTF execution queues and the generic queues that regulate OpenVMS DTF execution queues For further information about queues see the SET QUEUE command You can use wildcard characters in the queuename parameter The rules that apply to wildcard characters for file specifications also apply to queue names The default queue name is an asterisk which displays information about all initialized DTF queues You can also use generic and logical queue names with the queuename parameter SHOW QUEUE Command Qualifiers SHOW QUEUE Qualifier Default BRIEF BRIEF FULL None BRIEF Displays a shortened listing of in
99. 3 1 for restrictions on DTF support for FTAM 1 StrSig VAR document type Note The APP FTAM qualifier for the APPEND command is supported by FTAM However it is not supported when used against the unsupported DTF file COPY Command Examples VM COPY APP FTAM OSISSMOG DRAKE DTFVM FTAM2 NOT FTAM2 VAR E 8 FTAM File Support The example COPY command illustrates how you can copy a single local file FTAM2 NOT to FTAM2 VAR on a remote IBM VM system OSI SMOG is the association name which points to the FTAM responder DRAKE is the OpenVMS DTF server node name DTFVM is the DTF server account The file name that is created on the IBM VM system is FTAM2 VAR MVS COPY APP FTAM FTAM1 FIXED OSISSMOG DRAKE SNADTF DTFUSER FTAM1 The example COPY command illustrates how you can copy a single local file FTAM1 FIXED to a remote IBM MVS system OSI SMOG is the association name which points to the TAM responder DRAKE is the OpenVMS DTF server node name SNADTF is the DTF server account The file name that is created on the IBM MVS system is DTFUSER FTAM 1 Note The APP FTAM qualifier for the COPY command is supported by FTAM However it is not supported when used against the unsupported DTF file DELETE Command Example VM DELETE APP FTAM OSISSMOG DRAKE DTFVM FTAM1 FIXED The example DELETE command illustrates how you can delete a local file FTAM1 FIXED
100. 3 Multiple File Types All Clients You can use the DTF software to transfer a variety of non IBM and IBM file types 1 3 3 1 Supported Non IBM Files On OpenVMS clients DTF software can transfer and create all local RMS file types On Digital UNIX ULTRIX RSX 11M M PLUS MS DOS and OS 2 clients DTF software can transfer and create the sequential file type 1 3 3 2 Supported IBM Files On IBM clients the DTF software can transfer and create VSAM and non VSAM file types VSAM file types supported in transfers between IBM clients and OpenVMS clients are entry sequenced data sets ESDS relative record data sets RRDS and key sequenced data sets KSDS IBM disk resident files are supported and can be transferred to and from OpenVMS RMS files 1 6 Introducing the Data Transfer Facility DTF Product Non VSAM file types supported in transfers between IBM clients and all supported DECnet clients have a sequential organization This includes partitioned data set PDS members on MVS clients and CMS maclib members on VM clients Both IBM disk and tape resident files are supported and can be transferred to and from files on the DE Cnet clients For more specific information about file types supported and any restrictions on transfer operations see Chapter 3 1 3 4 Remote Job Submission and Post Processing All Clients DECnet clients can use the DTF product to submit jobs to IBM batch subsystems Some DECnet clients allow you to copy
101. 4 MDADDR 192 MDWPASS XY2 This command copies the DEV LOG file located on the current OpenVMS directory to TESTS EXEC on the IBM VM system The server account is DTF the OpenVMS DTF server node is OXEN and the VM user ID is GARY The minidisk address is 192 and its password is XYZ The file is created as a mode 1 file 5 7 CREATE Command To create a file on an IBM client use the DCL CREATE command CREATE file specf Table 5 6 shows the level of support DTF provides for the DCL CREATE command qualifiers For more detailed information about the CREATE command refer to the DCL Dictionary Note VM You cannot create an empty CMS file The CMS file system does not support the notion of allocating an empty file The CREATE operation will succeed but the VM system will delete the empty file when it is dosed Note that you can use the CREATE command with 5 14 OpenVMS File Transfer Operations VM DTF clients as long as you enter data before ending the file data with CTRLZ Table 5 6 DTF Level of Support for CREATE Command Qualifiers Qualifier For IBM File Specifications Comments DIRECTORY FDL fdl file spec NO LOG OWNER_UIC uic PROTECTION lt code VOLUME not supported supported supported ignored ignored not supported VM Not supported this qualifier creates an empty file which will be deleted by VM when the file is closed If you use the V
102. 5 B 16 B 17 B 19 B 19 B 20 E 2 E 6 E 7 F 4 F 6 F 7 Preface The Digital SNA Data Transfer Facility DTF software is a Digital Equipment Corporation product that allows you to transfer files between IBM MVS and VM systems in an SNA network and systems in a Digital DE Cnet network To use the DTF access routine you must first install the appropriate versions of the software and hardware that you plan to use Refer to the Software Product Description SPD for this information The DTF access routine consists of two major parts the BM resident software DTF for IBM systems and the Digital resident software OQpenVMS DTF The BM resident software can reside on a VM or MVS system DTF for VM or DTF for MVS Manual Objective This manual explains how to use the DTF product to access and transfer files between OpenVMS ULTRIX RSX 11M M PLUS MS DOS and OS 2 systems in a Digital DECnet network and MVS and VM systems in an IBM SNA network Intended Audience This manual is intended for the user who has access to the DTF software for the purpose of transferring files between systems DTF software can be accessed from OpenVMS DECnet ULTRIX DECnet RSX PATHWORKS for DOS PATHWORKS for OS 2 IBM MVS and IBM VM systems Changes and New Features The Digital SNA Data Transfer Facility for OpenVMS Version 3 2 differs from the Version 3 1 product only in that it includes support for utilizing TCP IP to exchange messages
103. ADTF is the server account SMOG is the target node where the DAP FTAM Gateway software is running OSI PUTTY is the association name MVS Initiated from IBM DEF INFILE JONES DTF 1 DEF OUTFILE SMOG OSIGTWY OSISPUTTY SYSTEM OSIUSERPASSWORD DTFTEST DAT 2 DEF SERV DRAKE NETMGR DTFR RECOVERY N 3 TRANS 4 DTFM030I REQUEST SUBMITTED TO DTFR 5 DTFM037I THIS REQUEST ASSIGNED REQUEST NUMBER 01143 DTFM055I SUBSYSTEM DTFR REPORTS COMPLETION OF REQUEST DTFM1011I SUCCESSFUL TRANSFER RECORD COUNT IS 163 gt SSNADTF S COPIED DRAKE SNADTF ETSOV1L JONES DTF CORR 01143 gt COPIED TO SMOG OSIGTWY OSISPUTTY OSIUSER password SYSS SYSROOT gt OSIUSER DTFTEST DAT 2 163 RECORDS DTFM048I ENTER CLEAR DEFINE END LIST RECALL RESUME SET SHOW OR TRANS KKK E 10 FTAM File Support The example illustrates an IBM TSO user using the DTF command processor commands to transfer an FTAM 2 NOTsignificant file to the OSI network 1 2 The input file in the transfer request is defined as J ONES DTF The output file is defined as DTIFTEST DAT The output file is identified with the node name DRAKE where the DAP FTAM Gateway is running and OSI PUTTY the association name points to the OSI node address The OSI user and OSI password are included with the file name DRAKE has been defined as the server session to which the transfer request is sent for execution DTFR has been def
104. AGE_CONTROL is also specified When this data set is subsequently opened by RMS it has a record format of VARIABLE and a record attribute of CARRIAGE_RETURN CARRIAGE_CONTROL If this data set is copied back to an OpenVMS system the resulting OpenVMS file has similar attributes In other words the FAB C_VFC FAB V_PRN options are transformed to FAB C_VAR and FAB V_CR RMS File System and Programming Constraints B 1 e Record attributes No carriage control A record attribute of FAB V_CR FAB V_FTN or FAB V_PRN must be specified when creating a data set on the IBM system with variable length records You do not need to specify carriage control for creating data sets with fixed length records Data sets without carriage control have a record attribute of CARRIAGE RETURN CARRIAGE _CONTROL when opened by RMS If you copy these data sets to an OpenVMS file the resulting file contains similar attributes If the files were originally text files with embedded carriage control then they appear to be double spaced after copying to the IBM system and then back to the OpenVMS system e Record access modes Block I O is not supported B 2 RMS Programming Restrictions You can use the standard RMS programming interface when writing an application program to access BM resident files You should however be aware of certain programming limitations when using the RMS programming interface with DTF For more information about the RMS programming inter
105. AM DISK VSAM on the Input and Output File Options panels TRANSFER DTF CHECKPOINT CHKPT CHECKPOINT CHECKPOINT on the Send or Receive panels TRANSFER DTF RECOVER RECOVERY RECOVERY RECOVERABLE on the Send or Receive panels 1Specify using the IBM file specification qualifiers described in Chapter 2 in the file name G 4 Correspondence Between DTF for IBM Keywords and OpenVMS DTF Qualifiers A Access control information for accessing DECnet files 2 4 for accessing IBM files 2 1 for the server account 2 1 ADD FILE_DEFINITION SNADTFCFG command 2 34 C 1 ALIGNMENT option 2 15 ALLOCATION number of 512 byte bl ocks 2 15 APPEND command OpenVMS DCL 5 2 PATHWORKS for DOS NFT 12 2 PATHWORKS for OS 2 NFT 12 2 RSX 11M M PLUS DCL 11 2 Appending files Se Files adding contents to Appending files to files from OpenVMS DCL 5 2 Backing up files Se Files backing up from OpenVMS DCL 5 5 BACKUP command OpenVMS DCL 5 5 Batch processing BATCHID qualifier 2 16 CLASS qualifier 2 18 command processor running in batch mode 9 39 9 40 introduction 1 7 submitting jobs Index Batch processing submitting jobs cont d from MS DOS clients 12 9 from OS 2 clients 12 9 with DECnet ULTRI X commands 10 3 with RSX 11M DCL 11 14 with DECnet RSX FTS 11 14 with DECnet RSX NFT 11 14 with OpenVMS DCL 5 31 with the command processor 9 23 with the panel interface 7 42 with TRANSFER DTF 6 9 BATCH
106. BM site BLOCK_SIZE blocksize Specifies a number from 1 to 32760 to define the block size for creating a data set Usage Notes e This qualifier is valid only when creating a file e By default DTF for IBM creates a blocked file with the block size set to the default value specified by DTF for IBM e TheDTF for IBM default is recommended for this qualifier e VM This qualifier is valid only when creating tape resident files e The SINGLE qualifier overrides the BLOCK_SIZE qualifier and creates an unblocked file e f you specify a block size you must use the following rules 1 For files with fixed length records you must specify a block size that is an even multiple of the record length 2 For files with variable length records you must specify a block size that is at least 4 more than the maximum record length 3 For files with variable spanned records you must specify a block size that is at least 8 CASE Specifies whether the IBM file specification contains lowercase characters Usage Notes e IfthelBM file type is VSAM and a lowercase character is given in the file specification the user will get a message that the file is not found VSAM files cannot contain lowercase characters e Wildcard directories that return file specifications with lowercase characters will have a CASE qualifier returned with those file specifications 2 16 DTF File Specifications e The DTF for IBM system instal
107. CES 5 18 DIRECTORY 5 20 EXCHANGE NETWORK 5 24 OPEN 5 27 READ 5 28 SEARCH 5 29 SUBMIT 5 31 supported commands 1 8 TYPE 5 33 WRITE 5 35 RSX 11M M PLUS APPEND 11 2 COPY 11 4 CREATE 11 7 DELETE 11 9 DIRECTORY 11 11 SUBMIT 11 14 supported commands 1 10 TYPE 11 16 dcp DECnet ULTRIX command 10 3 dcp_i DECnet ULTRIX command 10 5 DECnet file specification format 2 4 DECnet ULTRIX backup and restore operations 10 5 dcat command 10 1 dcp command 10 3 dcp_i command 10 5 dis command 10 6 drm command 10 8 supported file commands 1 10 DE Cnet I nternet Gateway specifying node name and account for 9 11 9 17 DEFAULT 2 18 DEFINE subcommand 9 5 CHKPT keyword 9 18 DISP keyword 9 13 example 9 22 INCASE keyword 9 7 INDEN keyword 9 8 INFDEF keyword 9 9 INFILE keyword 9 7 INLABEL keyword 9 9 INMDADDR keyword 9 9 INMDOWNER keyword 9 10 INMDPASS keyword 9 10 INNUM keyword 9 10 INPASS keyword 9 10 input file keywords 9 7 INRMT keyword 9 11 INUNIT keyword 9 11 INUSER keyword 9 11 INVOL keyword 9 12 NETMGR keyword 9 20 9 37 OUTCASE keyword 9 12 OUTDEN keyword 9 14 OUTFDEF keyword 9 14 OUTFILE keyword 9 12 OUTLABEL keyword 9 14 OUTMDADDR keyword 9 15 OUTMDOWNER keyword 9 15 OUTMDPASS keyword 9 15 OUTNUM keyword 9 16 OUTPASS keyword 9 16 OUTPRIMARY keyword 9 16 output file keywords 9 12 OUTRMT keyword 9 17 Index 3 DEFINE subcommand cont d OUTSECONDARY keyword
108. CH OPTIONS Fill in the required fields and press ENTER to continue FUNCTION gt i SUBmit or GENerate SAVE generated job in this file FILE NAME gt OVERWRITE gt NO JOB CONTROL information BATCH MACHINE to do copy JOB CLASS Your A disk READ PASSWORD LKG 8295 93R DTF displays the Batch Options panel see Figure 7 15 and Figure 7 16 if you type Y in the BATCH SUB field in any of the three operation panels The Batch Options panel differs slightly between the VM and MVS version The panel prompts you for job control information and DTF builds a default job card The panel allows you modify the default job card and to enter additional J CL as needed You can press PF3 to return to the operation panel that invoked this panel without initiating the operation 7 42 Using the DTF for IBM Panel Interface The fields on this panel are described following Figure 7 16 Figure 7 16 Batch Options Panel MVS Systems DTF ISPF BATCH OPTIONS Fill in the required fields and press ENTER to continue FUNCTION gt SUBmit or GENerate SAVE generated job in this file Sequential or PDS Member DATA SET NAME gt OVERWRITE gt Y N JOB CONTROL information LKG 8296 93R FUNCTION Enter SUB to submit the job immediately to the batch subsystem Enter GEN to generate the J CL required to submit the batch transfer operation and store the job in a file You m
109. DTF Account verification on the VM system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers The minidisk address is 181 and the minidisk passwords are taken from the proxy database default entry 5 30 OpenVMS File Transfer Operations 5 15 SUBMIT REMOTE Command To submit selected files for remote execution use the DCL SUBMIT REMOTE command SUBMIT REMOTE filespec Table 5 14 shows the level of support DTF provides for the DCL SUBMIT command qualifiers For more detailed information about the SUBMIT REMOTE command refer to the DCL Dictionary Note Files submitted to IBM batch subsystems must not contain any records that exceed 80 bytes Table 5 14 DTF Level of Support for SUBMIT REMOTE Command Qualifiers For IBM File Qualifier Specifications Commenis BACKUP not supported IBM files do not have a BACKUP date BEFORE time supported BY_OWNER uic supported All BM resident files have a UIC of 0 0 If you specify the BY_ OWNER qualifier with both OpenVMS and IBM input file specifications with a UIC other than 0 0 this qualifier affects only the OpenVMS input file specification CONFIRM supported CREATED supported EXCLUDE filespecf ignored EXPIRED supported MODIFIED supported lf specified for an IBM file specification the qualifier is ignored 31f specified for an IBM input file specific
110. DTF SHOW QUEUE FULL command NO LOG_FILE file name Specifies whether a log file is created If you use the LOG FILE qualifier DTF writes the log file to a file you specify The log file you specify must be located on the local node and wildcard characters are not allowed in the file specification The default is LOG_FILE SYS LOGIN job nameLOG If you use the NOLOG FILE qualifier a log file is not created You can also use the LOG_FILE qualifier to send the log file to a specific device The logical names that you include in the file specification are translated in the context of the process that submits the job OpenVMS TRANSFER DTF File Transfer Operations 6 7 For more information about specifying a job name refer to the NAME qualifier NAME job name Specifies a job name consisting of 1 to 39 characters to identify a job The SHOW J OBS command displays all the job names you specified If you do not specify a job name with the NAME qualifier the name defaults to the first or only input file in the job In this case the job name is based on the input file specification The following list explains how different input file specifications are used to create a job name 1 OpenVMS file specification Uses the name portion of the input file specification as the job name For example DRA1 SMART JRAW_DATA DAT 6 produces a job name of RAW_DATA 2 IBM partitioned data set or maclib member Uses the PDS member name or m
111. DTFNET SERVER NODE gt LKG 8307 93R The Operation Selection panel see Figure 7 1 is the first panel that you see when you select the DTF option from the ISPF main menu This panel does not appear when you use the non ISPF panel interface you will immediately see one of the operation panels Use the Operation Selection panel to select one of the three file transfer operations e You can send a local file from the system you are on to a file on a remote system e You can receive a file from a remote system and store it in a local file on your system Using the DTF for IBM Panel Interface 7 3 e You can resume a recoverable file transfer operation that was previously interrupted To begin an operation select one of the menu options and press the ENTER key This will cause DTF to display one of the three operation panels These panels are described in Section 7 3 Section 7 4 and Section 7 5 The Operation Selection panel lets you choose the network subsystem and server node that you want to use to transfer files DTF supplies defaults for these names but you can type over the names that are provided DTF SERVICES provided by NETWORK SUBSYSTEM Selects the Network Manager component which processes the transfer request For VM systems enter a 1 to 8 character Network Manager machine name For MVS systems enter a 1 to 4 character subsystem ID SERVER NODE Selects the server which processes the transfer request Type i
112. Digital SNA Data Transfer Facility for OpenVMS Use Part Number AA JM75F TE May 1996 This manual provides the information necessary to use the Digital SNA Data Transfer Facility DTF product Revision Update Information Operating System and Version Software Version This is a revised manual OpenVMS VAX Versions 6 1 6 2 or 7 0 OpenVMS Alpha Versions 6 1 6 2 or 7 0 RSX 11M M PLUS Version 4 2 M Version 4 0 M PLUS or later MS DOS Version 3 0 or later OS 2 Version 1 2 or later MVS SP MVS XA MVS ESA VM SP VM XA See the SPD for the latest operating system version Digital SNA Data Transfer Facility for OpenVMS Version 3 2 May 1996 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation or EDS Digital Equipment Corporation or EDS assumes no responsibility for any errors that may appear in this document The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies Digital conducts its business in a manner that conserves the environment Restricted Rights Use duplication or disclosure by the U S Government is subject to restrictions as set forth in subparagraph c
113. END subcommand allows you to remove your terminal from DTF mode The syntax of the END subcommand is END END Example The following example shows you how to use the END subcommand to exit DTF DEFINE INFILE CLUSTER LOGIN COM 1 DTF0047I DTF DEFINE OUTFILE IBMUSER LOGIN COM 2 DTF0047I DTF DEF SERV NODE1 3 DTF0047I DTF END 4 READY 1 This DEFINE subcommand specifies the input file 2 This DEFINE subcommand specifies the output file 3 This DEFINE subcommand specifies the server session 4 This END subcommand exits DTF all previously defined values are lost 9 22 Using the DTF for IBM Command Processor If a TRANSFER subcommand had been issued instead of the END subcommand the transfer request would have been submitted 9 3 4 TRANSFER Subcommand The TRANSFER subcommand passes the information supplied by the DEFINE subcommands to the DTF Network Manager subsystem The subsystem selects an OpenVMS DTF server node to process the file transfer request and forwards the information from the DEFINE subcommands to that node The syntax of the TRANSFER subcommand is TRANSFER IRANS POST filename POST file name Specifies a file that DTF should submit if an operation completes successfully The file can be an OpenVMS command procedure an MVS J CL file or a VM proc file If you specify a DE Cnet file specification the file is submitted on the indicated DECnet node If you specify an IBM file
114. ER ROGERS PASS SHADOW FILE1 EXEC 1 USER ROGERS FILE1 SCRPT 1 USER ROGERS FILE1 SUB 1 USER ROGERS 11 12 RSX 11M M PLUS File Transfer Operations This command displays a brief listing of all files of mode 1 for the user ROGERS The server account is DTFVM the OpenVMS DTF server node is CANDY and the user password is SHADOW Note that this command assumes there is an entry in the proxy database that will supply the MDRPASSWORD MDWPASSWORD and MDMPASSWORD qualifier information VM FT gt MIAMI DTFVM RSX USER MATTIS PASS GLOIN BR FILE1 EXEC 1 USER MATTIS FILE SCRPT 1 USER MATTIS FILE1 SUB 1 USER MATTIS This command displays a brief listing of all files with the name RSX for the user MATTIS The server account is DTFVM the OpenVMS DTF server node is MIAMI and the user password is GLOIN Note that this command assumes there is an entry in the proxy database that will supply the MDRPASSWORD MDWPASSWORD and MDMPASSWORD qualifier information Additional Information The DIRECTORY command does not accurately display information about the following fields e Size Always contains two numbers in the format nn nn The first number is always the same as the second number and does not indicate the amount of space currently in use as it should These numbers are only approximations of the number of 512 byte blocks in a file These numbers are always 0 for partitioned data set PDS members e Owner Always di
115. F 3 F 4 Field Level Translation 0 0 0 c eee es F 3 F 4 1 Creating a New Record Definition F 3 F 4 2 Supported CDD Data Structures 00 ce eee F 4 F 4 3 Translation of Digital CDD and IBM Data Types F 4 G Correspondence Between DTF for IBM Keywords and OpenVMS DTF Qualifiers Index Examples 9 1 9 2 9 3 Figures 7 5 7 7 7 8 7 9 7 10 7 11 7 12 7 13 7 14 7 15 7 16 D 1 Sample REXX EXEC to Perform Post Processing Sample J CL to Perform a Post Processing Function Sample REXX EXEC to Automatically Recover a Transfer Software Components in a DTF Environment Using the MDxPASSWORD Qualifier Part 1 Using the MDxPASSWORD Qualifier Part 2 Request Verified by MVS Proxy 0 00 eee eee eee IBM Initiated Access DECnet Client Node Not Running DANE vs aunak tel oe Aisne doe Soars a Oe a ee Oak eae Aaa Operation Selection Panel 000 cece eee eee Send to Remote Panel 0 00 c cece ees Receive from Remote Panel 0 000 eens Resume Previously Failed Transfer Panel Transfer Execution Panel MVS Systems Transfer Execution Panel VM Systems Remote Node Options Panel 00 cece ee ene MVS Input File Options Panedl 0005 VM Input File Options Panel 00 MVS Output File Options Panel
116. F Configuration utility to perform operations on the file definition database C 1 Adding Entries to the File Definition Database To add a new entry to the file definition database use the ADD FILE _ DEFINITION command ADD FILE_DEFINITION qualifier node access control file definiti on name input file spec or ADD FILE_DEFINITION qualifier node access control file definition name ibm file spec quals Command Parameters node access contro The node parameter specifies the OpenVMS DTF server node where the file definition database resides If you omit the node parameter from the ADD FILE_DEFINITION command the server node defined by the last USE NODE command is selected by default If you have not issued a USE NODE command then your current node is selected The access control parameter specifies the account name and password of an account on the server node with read and write access to all the databases The account name is usually SNADTF MGR Maintaining the OpenVMS DTF File Definition Database C 1 Note Do not use an account in the OpenVMS DTF server account database for the access control parameter file definition name Specifies the user assigned name of the file definition in the definition database input file spec The name of the file used to define file creation parameters This file can be used for all supported file types including VSAM files See Chapter 2 for information o
117. FTAM 3 Unstructured binary files e NBS 9 NBS file directories Note The FTAM document types are supported by FTAM initiators and responders The DAP FTAM Gateway does not support NBS 9 E 3 1 Restrictions Table E 2 describes the restrictions on two of the supported FTAM document types Table E 2 Restrictions Document Type Restrictions FTAM 1 StrSig VAR Files can be copied to the IBM system but will loose the FTAM 1 file type definition The file is translated as an FTAM 2 NOTsignificant file when the file is pulled back File contents do not alter FTAM 3 StrSig FIX Files can be copied to the IBM system but will loose the attributes when the file is pulled back The FTAM 3 file type changes to an FTAM 1 StrSig FIX when the file is pulled back File contents do not alter E 6 FTAM File Support Table E 3 shows the DTF support and mapping among FTAM OpenVMS and IBM file attributes Table E 3 DTF Support and Mapping Among FTAM OpenVMS and IBM MVS and VM File Attributes FTAM OpenVMS Equivalent IBM Equivalent DTF DocType StrSig RAT RFM ORG RECFM ORG Support FTAM 1 FIX CR FIX SEQ FIX SEQ Yes FTAM 1 VAR CR VAR SEQ VAR SEQ Restrictions FTAM 1 NOT CR STM SEQ Not supported No FTAM 2 FIX Not supported Not supported No FTAM 2 VAR Not supported Not supported No FTAM 2 NOT CR VAR SEQ VAR SEQ Yes FTAM 3 FIX None FIX SEQ Not supported Restrictions FTAM 3 VAR Not supported Not supported No FTAM 3 NOT N
118. Facility software processes Variable Sequential Access Method VSAM files D 1 A VSAM Primer for Non IBM Users DTF supports three VSAM file types e Sequential files e Relative record files e Indexed files VSAM file types consist of components The components are e Data component exists for all VSAM file types e Index component exists for indexed files only Each component has a name In addition the file itself has a name For information on how to specify the names for VSAM files and their components as file creation parameters refer to Section 2 4 D 1 1 Sequential and Relative Files Figure D 1 illustrates the file structure of VSAM sequential and relative files where A is the name of the cluster and is specified on the command line A DATA is the data component name for A The value of the NAME attribute for the DATA subsection of the BASE section is used here If this value is not specified then the default value is used by VSAM VSAM File Support D 1 Figure D 1 File Structure of VSAM Sequential or Relative Files A DATA LKG 4261 93R D 1 2 Indexed Files Figure D 2 illustrates the file structure of a VSAM indexed file with a single key of reference where A is the name of the base cluster and is specified on the command line A DATA is the data component name for A The value of the NAME attribute for the DATA subsection of the BASE section is used here If this value is not specified then the default value is u
119. File Support Users in an OSI network can transfer files to and from an IBM system by using OpenVMS FTAM in conjunction with DTF software IBM users can also transfer files to and from systems in an OSI network by using DTF software and the DAP FTAM Gateway This appendix covers the FTAM product s APPEND COPY DELETE and DIRECTORY facilities and its associated Digital Command Language DCL interface E 1 Overview of FTAM The OpenVMS FTAM software is an Open Systems Interconnection OSI product that implements the OSI File Transfer Access and Management FTAM OSI 8571 standard When implemented by different computer vendors the FTAM standard enables the transferring accessing and managing of files that reside on other vendors computer systems An FTAM system can be defined as any system containing an FTAM implementation that conforms to the FTAM standard and the necessary underlying OSI software In OpenVMS systems FTAM software conforms to the FTAM standards FTAM software can transfer unstructured files containing either binary or text data and sequential files having a variable record format to and from an FTAM system See Table E 3 for information on supported file types FTAM using the DAP FTAM Gateway allows users to transfer files to and from an OSI network FTAM File Support E 1 E 2 FTAM User Facilities FTAM provides the capability for other OSI FTAM compliant systems to use the approved International Organizatio
120. File System and Programming Constraints B 3 4 DELETE Table B 5 describes the special fields of the DELETE RMS service call Table B 5 DELETE RAB Input Fields Field Name Option Restriction Description RAB L_ROP Record processing options RAB K_FDL Disallowed Fast delete B 3 5 DISCONNECT There are no restrictions associated with the DISCONNECT input and output fields RMS File System and Programming Constraints B 11 B 3 6 DISPLAY Table B 6 and Table B 7 describe the special fields of the DISPLAY RMS service call Table B 6 DISPLAY NAM Input Fields Field Name Option Restriction Description NAM B_NOP NAM block options NAM V_ Ignored Do not conceal device name NOCONCEAL Table B 7 DISPLAY FAB and XAB Output Fields Field Name Option Restriction Description FAB L_ALQ Not filled in Allocation quantity in blocks FAB L_BKS Not filled in Bucket size FAB L_FSZ Not filled in Fixed control area size FAB L_GBC Not filled in Global buffer count FAB L_MRN Not filled in Maximum record number FAB L_RTV Not filled in Retrieval window size XABALL Allocation XAB XAB B_ALN Not filled in Alignment boundary type XAB B_AOP Not filled in Allocation options XAB W_DEQ Not filled in Default extension quality XAB L_LOC Not filled in Location XAB W_RFI Not filled in Related file identifier XAB W_VOL Not filled in Related volume number XABDAT Disallowed Date and time XAB XABKEY Key definition XAB XAB B_DBS Not fille
121. HSMRECALL MVS The HSMRECALL qualifier is used to indicate whether the IBM system should recall an archived file if the file is not in the system s first level storage Usage Notes e The default is NOHSMRECALL e If you use HSMRECALL your request stays pending until the secondary level storage is made available This can cause the system to hang DTF File Specifications 2 19 e Because access to HSM files can be disabled when DTF is installed on an MVS system you should check with the MVS system programmer if you receive indications that HSM files are not supported at the IBM client IGNORE condition Specifies an error condition that should be suppressed during a file operation The condition value may be set to the following PRECISION _ causes DTF to ignore the error CVTPRELOS This error occurs LOSS when DTF is unable to convert a floating point field between IBM and Digital formats because precision would be lost See Digital SNA Data Transfer Facility for OpenVMS Problem Solving and Messages for additional information about this error condition Usage Note e The default is to detect and report all errors KEY position length position length The KEY qualifier is used only for VSAM indexed files It lets you dynamically manipulate key of reference KRF numbers If a VSAM indexed file has multiple keys the keys are assigned KRF values based on file name collating sequences Refer to Appendix D for a
122. HUA SMITH to access KENT s account 3 The IBM security system grants access based on rules set up by the IBM system programmer 4 6 IBM Initiated Proxy Users on IBM client systems can submit DE Cnet file specifications without specifying the DE Cne password This type of transfer is called IBM initiated access DTF initiates the access on the Digital side with a user ID based on the IBM user ID This allows the remote OpenVMS system manager to grant access through DE Cnet proxy to the DE Cnet accounts that the IBM users want to access The IBM account is allowed to access only specific DE Cnet accounts 4 6 1 Example of IBM Initiated Transfer Request Figure 4 2 illustrates a request made from an IBM user for access to DE Cnet files The remote DECnet node is not running DTF Note You can use TCP IP as a transport between the DTF Server software and the SNA Gateway instead of DECnet when the SNA Gateway is either a Digital SNA Domain Gateway or a Digital SNA Peer Server Data Security 4 7 Figure 4 2 IBM Initiated Access DECnet Client Node Not Running DTF IBM client system DTF for IBM software DECnet SNA Gateway NASHUA TAMPA 4 DTF server software OpenVMS SNADTF DISPATCHER SNARCOPY DECnet remote node DTF server node TAMPA MARTIN RAFAL DECnet proxy database LKG 5494 93R 4 8 Data Security IBM user MARTIN issues a DTF
123. IBM file specification qualifier VOLUME is required with the DIRECTORY command This qualifier indicates the volumes on which the files reside on the IBM system If WOLUME is not specified then an MVS catalog search will be performed 12 6 SUBMIT Command To submit a file for remote execution on an IBM DTF client use the NFT SUBMIT command SUBMIT switch filespec Table 12 5 shows the level of support DTF provides for the NFT SUBMIT command switch For more detailed information about the SUBMIT command refer to the PATHWORKS for DOS DECnet User s Guide or PATH WORKS for OS 2 Utilities Guide manuals Table 12 5 DTF Level of Support for SUBMIT Command Switch Switch For IBM File Specifications INO LOG supported MS DOS and OS 2 File Transfer Operations 12 9 Examples MVS C NET FT gt SUBMIT DOCTOR DTFVM SPOON TEST JCL USER SPOON PASS DTFPASS This command submits the file SPOON TEST J CL located on the MVS system to an MVS batch queue The OpenVMS DTF server node is DOCTOR and the server account is DTFVM The MVS user ID is SPOON and the password is DTFPASS The file SPOON TEST J CL should not contain any records that exceed 80 bytes VM C NFT FT gt SUBMIT MIAMI HUMOR PRANKS EXEC USER JOKER PASS LAUGH This command submits the file PRANKS EXEC located on the VM system to the batch machine CMSBATCH with a class of A The OpenVMS DTF server node is MIAMI and th
124. IBM utility The SPANNED qualifier is not recommended with either fixed or variable length records unless it is specifically required 2 30 DTF File Specifications NO SUPERSEDE Specifies creation of a new output file or if the output file already exists overlaying the existing file If the SUPERSEDE qualifier is specified and the file transfer fails the original IBM data set is unaffected Usage Notes e The default qualifier is NOSUPERSEDE e The SUPERSEDE qualifier creates a temporary file during the file transfer When the copy operation is successful it renames the temporary file using a DELETE RENAME operation e The SUPERSEDE qualifier is not supported for VSAM files e The SUPERSEDE qualifier is not supported for elements of an SMS managed generation data group NOJTRANSLATE file spec Specifies whether the data is to be translated If you specify the TRANSLATE qualifier data is translated using a default translation table If you specify a file specification with the TRANSLATE qualifier you can include your own translation table For information about translation tables refer to the Digital SNA Gateway for Synchronous Transport Digital Gateway for Channd Transport and OpenVMS SNA Management Guides If you specify the NOTRANSLATE qualifier data translation does not occur Usage Notes e The default qualifier is TRANSLATE e Ifthe RECORD_DEFINITION qualifier is also specified the TRANSLATE q
125. ID name 2 16 BLOCK_SIZE blocksize 2 16 BUFFERSPACE file definition attribute 2 42 C CANCEL J OB TRANSFER DTF command 6 20 CASE 2 16 CATALOG option 2 17 CDDL See Common data definition language Checkpoint support See Recoverable copy operations CHKPT keyword 9 18 CLASS class name 2 18 CLEAR subcommand 9 4 example 9 4 Index 1 CLIENT 9 46 CLIENT keyword 9 33 CLIENTPASS 9 47 CLIENTPASS keyword 9 32 CLIENTUSER 9 46 CLIENTUSER keyword 9 32 CLIST variables CLIENT 9 46 CLIENTPASS 9 47 CLIENTUSER 9 46 RETNUM 9 46 CLOSE command OpenVMS DCL 5 8 CLOSE RMS service call B 7 Closing files See Files closing from OpenVMS DCL 5 8 Command processor batch mode execution 9 39 9 40 batch mode restrictions 9 44 CLEAR subcommand 9 4 CLIST variables set 9 46 DEFINE subcommand 9 5 END subcommand 9 22 entering a DECnet file specification 9 3 entering an IBM file specification 9 3 HELP subcommand 9 26 introduction 1 5 invoking 9 1 keyvalue syntax 9 3 keyword syntax 9 2 list of subcommands 9 2 LIST subcommand 9 28 overriding the server 9 39 overriding the server account 9 39 RECALL subcommand 9 29 RESUME subcommand 9 30 return codes 9 45 RE XX exec variables set 9 46 SET subcommand 9 36 SHOW subcommand 9 38 TRANSFER subcommand 9 23 Common data definition language CDDL creating CDDL file F 3 RECORD_DEFINITION qualifier 2 27 supported data structures F 4 In
126. IS PASS LEAVES This command copies the MAPLE TXT file to the TREES maclib on the IBM VM system The VM user ID is HARRIS and the VM user password is LEAVES The OpenVMS DTF server node is BOSTON and the server account is DTFVM VM FT gt BOSTON DTFVM TREES MACLIB MAPLE USER HARRIS PASS LEAVES MAPLE TXT AP This command must be entered with no continuators within double quotation marks Because of line length restrictions in this manual the command is represented as a wrapped command line This command performs the same operation as the previous example except it uses the NFT utility The command copies the MAPLE TXT file to the TREES madib on the IBM VM system The VM user ID is HARRIS and the VM user password is LEAVES The OpenVMS DTF server node is BOSTON and the server account is DTFVM 11 6 RSX 11M M PLUS File Transfer Operations 11 4 CREATE Command To create a file on an IBM DTF client use the DCL CREATE commana CREATE filespec or the NFT command output file spec switches TI switches See Chapter 2 for the IBM file specification syntax Table 11 4 shows the level of support DTF provides for the DCL CREATE command qualifiers For more detailed information about the CREATE command refer to the DECna amp RSX Guide to User Utilities Notes VM You cannot create an empty CMS file The CMS file system does not support the allocation of an empty file The CREATE operation will su
127. KUP Command Qualifiers 5 6 5 3 DTF Level of Support for CLOSE Command Qualifiers 5 8 5 4 DTF Level of Support for CONVERT Command Qualif S i ee ei araea i i e ede eee hE o 5 9 5 5 DTF Level of Support for COPY Command Qualifiers 5 12 5 6 DTF Level of Support for CREATE Command Qualifiers 5 15 5 7 DTF Level of Support for DELETE Command Qualifiers 5 16 5 8 DTF Level of Support for DIFFERENCES Command QUAIIMERS sas aea gea ae ne te Bae Se a Vea hk SO eed 5 18 5 9 DTF Level of Support for DIRECTORY Command QUaAIIMERS 2 Bia a duc dated ag eee Pe Fae de KAO da etaa ea 5 20 5 10 DTF Leve of Support for EXCHANGE NETWORK Command Qualifiers 0 0 eee 5 25 5 11 DTF Level of Support for OPEN Command Qualifiers 5 27 5 12 DTF Level of Support for READ Command Qualifiers 5 28 5 13 DTF Level of Support for SEARCH Command Qualifiers 5 29 DTF Level of Support for SUBMIT REMOTE Command Quali nS zas te ad r Bae a Bene sae Bar 5 31 5 15 DTF Level of Support for TYPE Command Qualifiers 5 34 5 16 DTF Level of Support for WRITE Command Qualifiers 5 35 xii 6 2 6 3 10 1 10 2 10 3 11 1 11 2 11 3 11 4 11 8 11 9 12 1 12 2 12 3 12 4 12 5 12 6 12 7 B 1 B 2 B 3 B 4 B 6 B 7 Recoverable File OperationS 00 cee eee eee TRANSFER DTF Support for DCL COPY Command Qu lifi S e i Yas wads by ate ets Death edd tec diet ie Unique TRANSFER DTF COPY Command
128. LE NODE LOGIN COM INUSER VMSUSER INPASS ILE IBMUSER LOGIN COM DEF SERVER NODE1 NETMGR DTF1 RECOVERY Y DTF DEFINE SERVER NODE2 6 TRANSFER 7 1 This TRANSFER subcommand started the transfer 2 Thetr 3 ThisL When ansfer failed because an active server session was not available IST subcommand shows the default values only a transfer request fails DTF automatically issues a CLEAR command to erase the input and output file specifications and to reset the default values 4 This RECALL subcommand calls back all the values defined prior to the last TRANSFER subcommand 5 ThisL IST subcommand displays the input and output file specifications and the transfer parameters 6 TheD EFINE command corrects the error in this case by specifying SERVER and a keyvalue that specifies an active server session 7 Another TRANSFER subcommand resubmits the transfer 9 3 8 RESUME Subcommand The RESUME subcommand allows you to restart a previously failed recoverabl TRANSFE e transfer from the point of failure Its function is similar to the R subcommand However the RESUME subcommand does not use information provided by the DEFINE subcommands Instead all information must be provided as part of the RESUME subcommand The syntax of the RESUME subcommand is 9 30 Using the DTF for IBM Command Processor RESUME RETNUM rery number CLIENT RES CLIENTPASS CLIENTUSER NETMG
129. LE DEFINITION PERSONNEL FILE File definition PERSONNEL_FILE BASE RECORD_DEFINITION PERSONNEL _RECORD RELEASE O SINGLE O SPANNED O SUPERSEDE O TRANSLATE YES UNIT DISK01 USERID PERONL VOLUMES VOL1 VSAM_SEQUENTIAL O This example displays the PERSONNEL _ FILE file definition on the user s terminal Maintaining the OpenVMS DTF File Definition Database C 5 C 3 Modifying a File Definition The process for modifying file definitions depends on whether you are modifying the BASE section or an ALTERNATE_INDEX Section The following two subsections describe the modify process for each instance C 3 1 Modifying the File Definition BASE Section To modify entries in the file definition s BASE section use the MODIFY FILE_ DEFINITION command MODIFY FILE_DEFINITION qualifier node access control file definition name ibm file spec quals Command Parameters node access contro The node parameter specifies the OpenVMS DTF server node where the file definition database resides If you omit the node parameter from the MODIFY FILE_DEFINITION command the server node defined by the last USE NODE command is selected by default If you have not issued a USE NODE command then your current node is selected The access control parameter specifies the account name and password of an account on the server node with read and write access to all the databases The account name is usually SNADTF MGR N
130. LIST DEF INFILE NODE LOGIN COM INUSER VMSUSER INPASS DEF OUTFILE IBMUSER LOGIN COM DEF SERVER NODE1 NETMGR DTF1 DTFO0471 DTF mj mj The output of the LIST subcommand also allows you to type over minor errors in the file specification and enter corrections by pressing Enter You are limited however to one typeover for each DEFINE list 9 3 7 RECALL Subcommand The RECALL subcommand allows you to reuse all of the DEFINE subcommands you created immediately before you entered a TRANSFER subcommand After you enter a TRANSFER subcommand all DEFINE subcommands are erased and can no longer be displayed with the LIST subcommand The syntax of the RECALL subcommand is F RECALL Subcommand Example The following example shows how you use the RECALL subcommand if you start a transfer with the TRANSFER subcommand and the transfer fails because of the parameters you defined DEFINE INFILE NODE LOGIN COM INUSER VMSUSER INPASS VMSPASS DTF0047I DTF DEFINE OUTFILE IBMUSER LOGIN COM DTF0047I DTF DEFINE SERVER NODE1 NETMGR DTF1 RECOVERY Y DTF0047I DTF TRANSFER 1 DTF0030I REQUEST SUBMITTED TO DTF1 gt DTF0612I A SERVER SESSION IS NOT AVAILABLE FOR THIS REQUEST 2 gt DTF0047I DTF gt Using the DTF for IBM Command Processor 9 29 LIST 3 DTF0047I RECALL 4 DTF0047I LIST 5 DEF INFI DEF OUTF DTF0047I DEF NETMGR DTF1 RECOVERY Y DTF DTF
131. M file specification e f you do not specify this field and the output file is written to tape the DTF command processor will specify the highest density allowed for that device OUTFDEF file specification Directs the DTF processor to read a file definition record in the file definition database Chapter 2 explains file definition records file specification A file specification in the file definition database Length 1 to 32 characters Usage Note e The filespecification keyvalue is valid only if the output file is an IBM file specification OUTLABEL label Specifies the format of the tape label on the output tape 9 14 Using the DTF for IBM Command Processor label The format of the tape labels on the tape that will be written You can specify one of the following tape labels AL ANSI V1 labels or ISO ANSI FIPS V3 labels Not supported for VM output files BLP Bypass label processing NL Non labeled SL Standard labels Usage Notes e If you specify OUTLABEL BLP or OUTLABEL NL you must specify RECOVERY NO You can specify RECOVERY YES only if you specify either OUTLABEL AL or OUTLABEL SL e Additional tape restrictions may apply Section 9 4 1 describes any additional restrictions e Specify this keyword only if the output file is an IBM file e Specify this keyword only if the output file will reside on a tape e If the output file resides on disk this keyword will be ignored e If you do not specify
132. OLUME qualifier the following error message is displayed SCREATE E BADVALUE VOLUME is an invalid keyword value The CREATE command will continue to create the file Examples MVS CREATE BRIDGE MVSDTE _S GARY DTF CREATE USER GARY PASS SECRET This command creates a new member CREATE in the GARY DTF data set on the IBM DTF client The OpenVMS DTF server node is BRIDGE and the server account is MVSDTF You can follow this command with data or press CTRL Z to exit VM CREATE MOOSE VMDTF GAME EXEC USER GARY PASS TOOHARD This command creates a new file GAME EXEC on the IBM DTF client The OpenVMS DTF server node is MOOSE the server account is VMDTF the VM account is GARY and the VM password is TOOHARD You must follow this command with data and then press CTRL Z to exit OpenVMS File Transfer Operations 5 15 5 8 DELETE Command To delete a file on an IBM client use the DCL DELETE command DELETE filespec Table 5 7 shows the level of support DTF provides for the DCL DELETE command qualifiers For more detailed information about the DELETE command refer to the DCL Dictionary Notes If you attempt to delete an MVS file that was created with an expiration date and that expiration date has not been reached MVS will prompt the MVS console operator for permission to delete the file The file operation will wait until the console operator replie
133. OP1 File processing options field rejected Example READ FILE RECORD This command reads a single record from the data set that was opened prior to this command and assigns the contents of the record to the symbol RECORD Note that because no file name is ever used directly in a READ statement this command is no different than any other OpenVMS READ command 5 28 OpenVMS File Transfer Operations 5 14 SEARCH Command To search one or more files for a specified string or strings use the DCL SEARCH commana SEARCH file sped search string Every line containing a matched string is displayed Table 5 13 shows the level of support DTF provides for the DCL SEARCH command qualifiers For more detailed information about the SEARCH command refer to the DCL Dictionary Table 5 13 DTF Level of Support for SEARCH Command Qualifiers For IBM File Qualifier Specifications Commenis BACKUP not supported BEFORE time supported BY_OWNER uic supported All BM resident files have a UIC of 0 0 If you specify the BY_OWNER qualifier with both OpenVMS and IBM input file specifications with a UIC other than 0 0 this qualifier affects only the OpenVMS input file specification INOJCONFIRM supported CREATED supported INOJEXACT supported EXCLU DE filespec ignored EXPIRED supported F ORMAT option supported INOJHEADING supported INO LOG supported MATCH option supported
134. OYEE VSAM CLUSTER identifies the IBM file that will be opened when a DATATRIEVE READY command is issued USERID RFA are IBM file specification qualifiers Review Chapter 2 for applicable qualifiers When a DATATRIEVE READY command is issued a DTF session will be set up to access the file on the IBM system A 2 Preparing a DATATRIEVE Domain for Access to an IBM File Use the DATATRIEVE READY command to access a domain that references an IBM file Read and write access is supported for all file types For example DTR gt READY IBM_DOMAIN WRITE This READY command creates an SNA session to DTF for IBM and opens the file that was identified in the DATATRIEVE DEFINE command Using the example from the previous section this command would open the EMPLOYEE VSAM CLUSTER file If security is installed on the IBM system then access rights are checked and enforced before the file is opened A 2 Using OpenVMS DATATRIEVE with DTF Note Shared access to domains opened for write access is supported only for VSAM file types If you are accessing VSAM indexed files and you receive a status code indicating that the RFA table space size has been exceeded and the requested operation will not be performed your file has exceeded the RFA table size specified during DTF for IBM installation To free your table space close and open the indexed file by issuing a DATATRIEVE FINISH command followed by a READY command A 3 Manipulating Rec
135. OpenVMS DTF server node is PARIS and the server account is DTFVM The VM user ID is DTFMAN and the VM password is CURIOUS VM C NET FT gt COPY SUBMIT EXEC_FILE DAT OCEAN DTFVM DTFPROC EXEC USER ROBERTS PASS SHADOW BATCH CMSBATCH CLASS A This command copies the local file EXEC_FILE DAT to the file DTFPROC EXEC on the VM system The OpenVMS DTF server node is OCEAN and the server account is DTFVM The VM user ID is ROBERTS and the VM password is SHADOW After the file is successfully copied it will be submitted to the CMSBATCH batch machine with a class value of A The file EXEC_FILE DAT should not contain any records that exceed 80 bytes 12 4 DELETE Command To delete a file on an IBM DTF client use the NFT DELETE command DELETE switch filespec Table 12 3 shows the level of support DTF provides for the NFT DELETE command switch For more detailed information about the DELETE command refer to the PATHWORKS for DOS DECnet User s Guide or PATH WORKS for OS 2 Utilities Guide manuals MS DOS and OS 2 File Transfer Operations 12 5 Notes If you attempt to delete an MVS file that was created with an expiration date and that expiration date has not been reached MVS will prompt the MVS console operator for permission to delete the file The file operation will wait until the console operator replies You may terminate the operation by using a CTRL You cannot delete IBM tape resident files You c
136. Options Panel COMMAND gt Fill in the required fields and press ENTER to continue MINIDISK information TAPE options DEVICE OWNER gt TAPE LABEL wees DEVICE ADDRESS gt FILE NUMBER gt PASSWORD gt DENSITY gt FILE options VSAM Y N TAPE UNIT NULL RECORDS REJECT IGNORE SPACE NONE MIXED CASE NAME Y N PRIMARY ALLOC SECONDARY ALLOC DTF options FILE DEFINITION LKG 8297 93R DTF displays the VM Output File Options panel see Figure 7 11 if you type Y in the OPTIONS field for a VM output file in the Send to Remote or Receive from Remote pane You can press PF3 to return to the operation panel that invoked this panel without initiating the operation The following pages describe each field on this panel MINIDISK information DEVICE OWNER This field specifies the owner of the minidisk that will contain the output file For a local output file this field is optional if you have the minidisk linked and accessed For a remote output file see the description of the OWNER_ID qualifier in Chapter 2 7 34 Using the DTF for IBM Panel Interface DEVICE ADDRESS This field specifies the device address of the minidisk that will contain the output file For a local output file this field is optional if you have the minidisk linked and accessed For a remote output file see the description of the MDADDRESS qualifier in Chapter 2 PASSWORD This field specifies the read p
137. Options panel see Figure 7 12 if you type Y in the OPTIONS field for a non IBM input or output file in the Send to Remote or Receive from Remote panel You can press PF3 to return to the operation panel that invoked this panel without initiating the operation The following describes the field on this panel NETWORK FILE NAME if more space is required FILE NAME This is the name of the file you are copying as it exists or will exist on the remote system You must supply this file name See Chapter 2 for more information on specifying file names for DTF 7 38 Using the DTF for IBM Panel Interface 7 13 The Data Translation Options Panel Figure 7 13 Data Translation Options Panel DATA TRANSLATION options TRANSLATE gt Jj RECORD DEFINITION LKG 8294 93R DTF displays the Data Translation Options panel see Figure 7 13 if you type Y in the EXTENDED field in the Send to Remote or Receive from Remote panel You can press PF3 to return to the operation panel that invoked this panel without initiating the operation The following paragraphs describe the fields on this panel DATA TRANSLATION options TRANSLATE Specifies whether you want your files translated Appendix F provides additional information about data translation If you type YES DTF uses the standard EBCDIC to DMCS translation table To translate using a different translation table specify the file name of the file on th
138. R SERVER The minimum entry for the RESUME subcommand includes the RETNUM NETMGR and SERVER keywords The RESUME subcommand passes the information supplied by the keywords to the DTF Network Manager subsystem The subsystem selects an OpenVMS DTF server node to process the resume request and forwards the information from the keywords to that node For the duration of the retry the terminal keyboard is locked Several messages are written to the terminal to indicate the status of the retry request The following messages are the most important DTFM037I THIS REQUEST ASSIGNED REQUEST NUMBER xxxxx The xxxxx value indicates the internal request number assigned by the DTF Network Manager subsystem You use this number when you report problems to the IBM system support staff They use this number to locate a variety of trace information DTFM055I SUBSYSTEM yyyy REPORTS COMPLETION OF REQUEST Processing is complete Messages from the server node report the outcome of the retry request Digital SNA Data Transfer Facility for OpenVMS Problem Solving and Messages provides additional information about OpenVM S DTF messages from the server node Canceling a RESUME Subcommand MVS You can cancel a resumed transfer that is in progress at any time The method used to cancel the transfer depends on the terminal you are using On non SNA terminals press Reset then PA1 On SNA terminals press Attn Both terminals will display the following
139. Read of locked record allowed RAB V_RRL Ignored Read regardless of lock RAB V_ULK Ignored Manual unlocking RAB V_WAT Disallowed Wait B 3 9 FREE There are no restrictions associated with the F REE input and output fields When using FREE with VSAM files only the current record or control interval is unlocked because only one record or control interval can be locked at atime F REE is ignored for non VSAM files B 14 RMS File System and Programming Constraints B 3 10 GET Table B 9 describes the special fields of the GET RMS service call Table B 9 GET RAB Input Fields Field Name Option Restriction Description RAB L_ROP Record processing options RAB V_LIM Disallowed Limit RAB V_NLK Disallowed No lock RAB V_NXR Ignored Nonexistent record processing RAB V_REA Disallowed Lock for read RAB V_RLK Disallowed Read of locked record allowed RAB V_RRL Disallowed Read regardless of lock RAB V_ULK Disallowed Manual unlocking RAB V_WAT Disallowed Wait RMS File System and Programming Constraints B 15 B 3 11 OPEN Table B 10 and Table B 11 describe the special fields of the OPEN RMS service call Table B 10 OPEN FAB Input Fields Field Name Option Restriction Description FAB W_DEQ Ignored Default file extension quantity if a nonzero value is present in this field it applies only to this open of the file FAB B_FAC File access FAB V_BIO Disallowed Block I O access to file FAB V_BRO Disallowed Block or r
140. SER KRINGLE PASS SNOW JOB MVS SB As in the previous two examples this command submits the file KRINGLE LIST J CL to the batch system on the MVS system However this command first copies the file from the RSX file J OB MVS Also this command deletes the MVS file after execution is complete VM SSUBMIT REMOTE _ gt CASTLE DTFVM TESTBAT EXEC USER GIBSON BATCH CMSBATCH CLASS A RSX 11M M PLUS File Transfer Operations 11 15 This command submits the file TESTBAT EXEC to the batch machine CMSBATCH in the class A The OpenVMS DTF server node is CASTLE and the server account is DTF VM The IBM user ID is GIBSON and the user password is taken from the proxy database The file TESTBAT EXEC should not contain any records that exceed 80 bytes VM FT gt HOMER DTFVM GUIDE EXEC USER NEWELL PASS SNOWY EX This command submits the file GUIDE EXEC to the batch machine CMSBATCH in the class A The OpenVMS DTF server node is HOMER and the server account is DTFVM The IBM user ID is NEWELL and the user password is SNOWY The file GUIDE EXEC should not contain any records that exceed 80 bytes 11 8 TYPE Command To display on a terminal a file residing on an IBM DTF dient use the DCL TYPE command TYPE filespec Table 11 8 shows the level of support DTF provides for the DCL TYPE command qualifiers For more detailed information about the TYPE command refer to the DE Cnet RSX Guide to User Utilities
141. SHOW ERROR command SHOW ERROR status code You can use this command to help discover the cause of an error when using DTF supported DCL commands Command Parameter status code Specifies the status code for which you are requesting the error message text The status code is a hexadecimal number OpenVMS TRANSFER DTF File Transfer Operations 6 21 Note The Digital SNA Data Transfer Facility for OpenVMS Problem Solving and Messages manual contains two appendixes one which lists the numeric status codes and their abbreviated text and one which lists the full error message along with an explanation and suggested action Example TRANSFER DTF TRANS DTF gt SHOW ERROR X023A80B2 SSNADTF E APPNOTAVA DTF for IBM is not available sense code X 0801 This example displays information about reason code X023A80B2 6 22 OpenVMS TRANSFER DTF File Transfer Operations l Using the DTF for IBM Panel Interface This chapter explains how to use the DTF for IBM panel interface to transfer files It describes all of the fields on the panels and provides examples of what the panels look like The sections show you how to move from panel to panel in order to copy files 7 1 The DTF Panel Interface The DTF panel interface provides a series of panels that prompt you through the process of transferring files between an IBM system and a DECnet node or between two IBM systems The panels can be used by CMS and TSO E Interact
142. SL can be specified with a VM tape input file e mvslYou can specify AL BLP NL or SL with an MVS tape output file You cannot specify BLP or NL if you are using the OpenVMS TRANSFER DTF COPY command with the RECOVER qualifier e vMlYou can specify BLP NL or SL with a VM tape output file You cannot specify BLP or NL if you are using the OpenVMS TRANSFER DTF COPY command with the RECOVER qualifier MDADDRESS disk address M Specifies the address of the minidisk On VM SP systems the address consists of three hexadecimal digits On VM XA systems the address consists of four hexadecimal digits Usage Note e f you do not specify a value DTF for IBM supplies the default specified at the IBM site MDMPASSWORD password VM MDRPASSWORD password VM MDWPASSWORD password VM Specifies the multiwrite M DM PASSWORD read MDRPASSWORD or write MDWPASSWORD minidisk password for minidisk access Minidisk passwords are 1 to 8 characters long DTF File Specifications 2 21 Usage Notes e The DTF software follows standard CMS minidisk linking rules to allow access to files If you have a minidisk linked for read only you can use any of the files on the minidisk as the input file to a transfer If the minidisk is linked for write mode you can use any files on that disk as input or output files for a transfer If you submit a transfer to
143. T This command opens an existing file FIFTIES EXEC located on the IBM client under the VM user ID PAT This data set is opened for both read and write operations Record level access to FIFTIES EXEC is performed through READ and WRITE commands that reference INFILE The OpenVMS DTF server node is CARS and the server account is SNADTF Account verification on the OpenVMS File Transfer Operations 5 27 VM system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers 5 13 READ Command To read a record from any file opened with the DCL OPEN command use the DCL READ commana READ logical namd symbol name Table 5 12 shows the level of support DTF provides for the DCL READ command qualifiers For more detailed information about the READ command refer to the DCL Dictionary Table 5 12 DTF Level of Support for READ Command Qualifiers For IBM File Qualifier Specifications Commenis DELETE supported END_OF_FILEAabd supported ze ERRORASabd supported AINDEX supported KEY string supported MATCH option supported When you use the GT greater than or GE greater than or equal to options be aware that records are returned in EBCDIC collating order NO LOCK not supported 3 PROMPT string not supported NOJTIME_OUT n not supported 1Command fails with the following error message RMS F SUPPORT Network operation not supported FAL F F
144. T LEDGER The IBM file specification contains three qualifiers The USERID and PASSWORD qualifiers specify a user account ACCT and password SECRET used by the appropriate security product to allow access to the IBM system The RECORD_DEFINITION qualifier directs DTF to perform a field by field translation on each record of the file using the LEDGER_RECORD entry in the VAX Common Data Dictionary Notice that a hyphen continues a command line that is too long for the screen After you execute this command the system by default enters the copy request on the OpenVMS DTF queue named SNADTF QUEUE MVS TRANSFER DTF TRANS DTF gt COPY QUEUE NIGHTLY NAME NIGHTLY_UPDATE NOTIFY _From NODES INVENTORY INV STOCK ABC FILE INV_UPDATE PASS SECRET _To 1 DUA3 INVENTORY DATA STOCKROOM_UPDATE DAT Job NIGHTLY_UPDATE queue NIGHTLY entry 106 started on NIGHTLY This COPY command copies the data set in INV STOCK ABC from the IBM DTF client using the INVENTORY server account on OpenVMS DTF server node NODE5 The data set is copied to a file called STOCK ROOM _ UPDATE DAT in the INVENTORY DATA directory on the OpenVMS system user disk 1 DUA3 The command qualifiers specify that the copy request be entered on the queue called NIGHTLY that the job name be NIGHTLY_UPDATE and that the system notify you with a broadcast message when it completes the job The IBM file specification qualifier FILE_ DEFINITION su
145. TF client and an IBM DTF client use the TRANSFER DTF COPY command COPY input file spec output file spec By default this command includes a checkpoint and recovery feature RECOVER for non VSAM files If communications fail or a system goes down during a copy operation the checkpoint and recovery feature resumes copying at the last checkpoint when communications are reestablished or when the system comes back up To transfer VSAM files you must specify the NORECOVER option TRANSFER DTF does not support recoverable file transfers for VSAM files After a user issues a TRANSFER DTF COPY command the E NTRY symbol is set to the value of the entry number that was assigned to the queued job Note You cannot use wildcard characters either in the input file or output file specification COPY Command Qualifiers Table 6 2 describes the level of support for TRANSFER DTF COPY qualifiers that are also available through the DCL COPY command Table 6 3 lists the TRANSFER DTF COPY qualifiers that are unique to TRANSFER DTF These qualifiers are described following Table 6 3 OpenVMS TRANSFER DTF File Transfer Operations 6 3 Table 6 2 TRANSFER DTF Support for DCL COPY Command Qualifiers For IBM File Qualifier Specifications Comments ALLOCATION supported For an IBM output file enough tracks or cylinders are allocated on the IBM system to hold a number n of 512 byte blocks Enough 512 byte blocks i
146. Table 12 1 DTF Level of Support for APPEND Command Switches Switch For IBM File Specifications ASCII supported DELETE not supported IMAGE supported NOLOG supported PRINT not supported STREAM ignored SUBMIT supported UNDEFINED not supported Examples MVS C NET FT gt APPEND FILE1 DAT IBMI DTFMVS WHITE DTF TALL This command appends the local file FILE1 DAT to the member TALL of the PDS WHITE DTF located on the MVS system The OpenVMS DTF server node is IBM1 and the server account is DTFMVS Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers 12 2 MS DOS and OS 2 File Transfer Operations MVS C NFT FT gt APPEND RABBIT DTFMVS JONES DTF MAIL FILE2 DAT This command appends the member MAIL of the data set J ONES DTF located on the MVS system to the local file FILE2 DAT The OpenVMS DTF server node is RABBIT and the server account is DTFMVS Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers VM C NFT FT gt APPEND STATS1 DAT TENNIS DTFVM STATS MACLIB STATS1 MDWPASS SECRET This command appends the local file STATS1 DAT to the maclib member STATS1 in the maclib STATS on the VM system The OpenVMS DTF server node is TENNIS and the server account is DTF
147. The DELETE APP FTAM command allows you to delete any remote file any local file or a combination of local and remote files OSI SMOG is the association name which points to the FTAM responder DRAKE is the OpenVMS DTF server node name DTFVM is the DTF server account DIRECTORY Command Example MVS DIRECTORY APP FTAM OSISSMOG DRAKE SNADTF DTFUSER DTFPDS MEM1 US DTFUSER DTF can support directory listings only when the user gives a full file specification The example shows a PDS member file which is a sequential flat file by itself When FTAM does a OPEN DTF for IBM can provide the necessary information for directory output FTAM File Support E 9 E 4 1 Examples of File Transfers Using the DAP FTAM Gateway You can use the DAP FTAM Gateway to transfer files to or from an OSI network IBM users can transfer files to or from an OSI network DE Cnet users can also do a third party copy of IBM files to and from an OSI network using the DAP FTAM Gateway Note All references to systems in the following examples are based on the configuration in Figure E 1 COPY Command Examples VM Initiators to OSI COPY APP FTAM OSISSMOG DRAKE DTFVM FTAM2 FILE SMOG OSIGTWY OSISPUTTY OSIUSER OSIPASS DTFTEST DAT The example illustrates an OpenVMS user typing a COPY command to copy an IBM VM file using DTF to an OSI node using the DAP FTAM Gateway DRAKE is the OpenVMS DTF server node SN
148. Translation Table F 1 Cont Correspondence of CDD Data Types and IBM Data Types CDD Data Type IBM Data Type UN SIGNED QUADWORD UN SIGNED OCTAWORD D_FLOATING D_FLOATING COMPLEX F_FLOATING F_FLOATING COMPLEX G_FLOATING G_FLOATING COMPLEX H_FLOATING H_FLOATING COMPLEX PACKED DECIMAL ZONED NUMERIC LEFT RIGHT SEPARATE NUMERIC not supported not supported Long floating point not supported Short floating point not supported Long floating point not supported Extended floating point not supported Packed decimal Zoned decimal not supported LEFT RIGHTJOVERPUNCHED not supported NUMERIC Most supported data types transferred between Digital and IBM systems are converted without any restrictions or limitations but you should be aware of the few exceptions that do exist Table F 2 and Table F 3 list all the data types supported for transfer and any limitations that might occur in data transfers between Digital and IBM Note When a field cannot be mapped exactly between the two different data formats an error is reported and the file transfer is aborted DTF Data Translation F 5 Table F 2 Limitations on Data Transferred from Digital to IBM Digital Data Types IBM Data Types Limitations 2 byte integer word 2 byte integer None half word 4 byte integer 4 byte integer word None longword Packed decimal Packed decimal None DMCS text EBCDIC text None Zoned numeri
149. U The OpenVMS DTF server node is MYFAIR and the server account is DTFMVS PROD Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers MVS DIFF MYFAIR DTF200 LOU STATUS TEXT1 _ MYFAIR DTF200 LOU STATUS TEXT2 This command displays any differences between the PDS member TEXT1 of the LOU STATUS data set located on the IBM DTF client and the PDS member TE XT2 of the LOU STATUS data set located on the same IBM DTF client under the user ID LOU The OpenVMS DTF server node providing access to both IBM files is MYFAIR and the common server account is DTF 200 Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers VM DIFF SYSSLOGIN LOGIN COM BOSTON DTFVM LOGIN COM OpenVMS File Transfer Operations 5 19 This command displays any differences between the file LOGIN COM located in the SYS LOGIN OpenVMS directory with the file LOGIN COM on the IBM DTF client The OpenVMS DTF server node is BOSTON and the server account is DTFVM Account verification on the VM system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers 5 10 DIRECTORY Command To list one or more files on an IBM cient use the DCL DIRECTORY command DIRECTORY filespec
150. UM 1 OUTPASS password Specifies the password associated with the OUTUSER account password The password associated with the OUTUSER account The syntax of the input file specified with the OUTFILE keyword will determine the format of the password keyvalue DECnet The password that corresponds to the user ID to be used when contacting password theclient node Length 1 to 31 characters IBM The password that corresponds to the user ID to use when the DTF password Network Manager verifies access to the file Length 1 to 8 characters Usage Notes e If the remote client node is running Digital UNIX or ULTRIX you must enter the password with the proper case e f the node portion of the file specification that you specified with the OUTFILE keyword contains access control information that includes a password the command processor ignores this keyword e f you do not specify a user ID either in the access control information or with the OUTUSER keyword the command processor ignores this keyword OUTPRIMARY A 5 digit number specifying the number of 512 byte blocks that DTF will initially allocate when creating a file on the IBM system 9 16 Using the DTF for IBM Command Processor OUTRMT node server account name Specifies an OpenVMS DTF server node and server account name or a DE Cnet Internet Gateway node node server account name server account name An OpenVMS DTF server node name and a server account name or a DECn
151. UNCATE not supported NOLUME n JINOJWRITE_CHECK not supported not supported For an IBM output file protection is set up with a file definition 2Command fails with the following error message RMS F SUPPORT Network operation not supported FAL F F OP1 File processing options field rejected 4See Section 5 10 1 for restrictions Table 6 3 Unique TRANSFER DTF COPY Command Qualifiers Qualifier Default AFTER time None CHARACTERISTICS None characteristic CHECKPOINT_INTERVAL interval INOJHOLD INO JIDENTIFY INTERVAL ddta time AINOJLOG_FILE filename NAME 5ob name INO NOTIFY INO POST_PROCESSING filespec PRIORITY n INOJQUEUE queuenamd 1000 records NOHOLD IDENTIFY Default interval time for the queue SYS LOGIN job nameLOG First file name NONOTIFY NOPOST_PROCESSING DEFQUEPRI SYSGEN value SNADTF QUEUE continued on next page OpenVMS TRANSFER DTF File Transfer Operations 6 5 Table 6 3 Cont Unique TRANSFER DTF COPY Command Qualifiers Qualifier Default INOJRECOVER RECOVER RETRIES Default retry limit for the queue SINCE time SINCE TODAY TIME time Default time value for the queue Command Qualifiers Unique to TRANSFER DTF AFTER time Specifies holding the copy operation until after a time that you have specified If the time specified with the AFTER qualifier has passed the job is queued for immediate processing
152. VM Note that no IBM user ID or IBM password is given DTF accesses the files on the IBM system by using information in the OpenVMS DTF server s proxy database The minidisk write password is SECRET 12 3 COPY Command To transfer ASCII or binary files between an MS DOS or OS 2 DTF client and an IBM DTF cient use the NFT COPY command COPY switch input file spec output file spec The COPY command allows an MS DOS or OS 2 user to do the following e Copy an ASCII or binary file residing on an IBM DTF dient to the local system e Copy an ASCII or binary file residing on the local system to any IBM DTF client If a remote file has additional attributes besides ASCII or binary the file will lose those attributes when transferred to an MS DOS or OS 2 system Table 12 2 shows the level of support OpenVMS DTF provides for the NFT COPY command switches For more detailed information about the COPY command refer to the PATHWORKS for DOS DECnet User s Guide or PATHWORKS for OS 2 Utilities Guide manuals MS DOS and OS 2 File Transfer Operations 12 3 Notes All files submitted for execution on IBM systems using the SUBMIT switch must contain records that do not exceed 80 bytes Files copied and submitted for execution on IBM systems are not deleted after the job is submitted Table 12 2 DTF Level of Support for COPY Command Switches Switch For IBM File Specifications ALLOCATION supported ASCII s
153. VS files each qualifier can be used for non VSAM disk resident files tape resident files and VSAM files Each qualifier is described in greater detail in Section 2 3 3 Table 2 1 IBM File Specification Qualifiers and Their Usage for Remote VM Files Tape Resident Qualifier CMS Files Files VSAM Files ALIGNMENT ignored ignored ignored ALLOCATION supported ignored supported BATCHID supported ignored ignored BLOCK_SIZE ignored supported ignored CASE supported supported rejected CATALOG ignored ignored ignored CLASS supported ignored ignored DEFAULT 1234 5 supported supported supported DENSITY 1236 ignored supported ignored DIRECTORY_BLOCKS ignored ignored ignored FILE_DEFINITION 12345 supported supported supported HSMRECALL ignored ignored ignored IGNORE 123 supported supported supported KEY ignored ignored supported LABEL 236 ignored supported ignored This qualifier is used when reading IBM input files for copy search compare and display operations 2This qualifier is used when writing over existing IBM output files 3This qualifier is used when creating a new IBM file 4This qualifier is used when deleting an IBM file gt This qualifier is used when listing an IBM directory 6This qualifier is used only for IBM tape resident files 7This qualifier is used only for SUBMIT REMOTE operations continued on next page 2 10 DTF File Specifications Table 2 1 Cont IBM File Specification Qualif
154. a beast decd a 5 2 5 3 BACKUP Command 000 cece eee eens 5 5 5 4 CLOSE COMMANA warara daikon Dale we eal h ad ati aetar a die alias 5 8 5 5 CONVERT Command 00 cece eee eee eens 5 9 5 6 COPY Command i iaden Sor 6 eee he ee Fa ed 5 11 5 7 CREATE Command 000 cece eee eens 5 14 5 8 DELETE Commande sianie cece a datea and 4 had ale weed 5 16 5 9 DIFFERENCES Command 0 00 eects 5 18 5 10 DIRECTORY Command 0000 a 5 20 5 10 1 Date and Time Restrictions for Created Revised and Expires Fields u ici eae a od ee aA eee 5 24 5 11 EXCHANGE NETWORK Command 00000 5 24 5 12 OPEN Command 000 cee eee 5 27 5 13 READ Command isis tac adayid aarge ds Sd ae ae aS 5 28 5 14 SEARCH Command 0 aaea 5 29 5 15 SUBMIT REMOTE Command 0000 00 eee 5 31 5 16 TYPE Command wis cj ek ewe cae dene Od dae ee eae ae 5 33 5 17 WRITE Command 0 00 cece eee eee ene 5 35 6 OpenVMS TRANSFER DTF File Transfer Operations Invoking the TRANSFER DTF Utility Exiting the TRANSFER DTF Utility Copying Files with the TRANSFER DTF Utility Defining OpenVMS DTF Queue Attributes Displaying the Status of File Transfer Jobs Displaying OpenVMS DTF Queue Characteristics Displaying the OpenVMS DTF Software Version Number Canceling File Transfer J obs
155. aclib member name as the job name For example MAIN J CL COM BACKUP and DTF MACLIB DTFMCS produce job names of BACKUP and DTFMCS respectively 3 IBM generation data set Uses the last portion of the file specification before the parentheses as the job name For example TOASTER OVEN 1 produces a job name of OVEN 4 All other MVS or VSAM IBM data sets Uses the last portion of the name as the job name For example TOP LEVEL1 LEVEL2 LEVEL3 BOTTOM produces a job name of BOTTOM 5 All other VM file names Uses the whole file name to create the job name The job name is formed by concatenating the parts of the file name together using the underline character For example PROFILE EXEC 1 produces a job name of PROFILE_EXEC_1 NO NOTIFY Specifies whether a message is broadcast to any terminal at which you are logged in notifying you when your print job completes or aborts If you delete a job while it is not currently executing you do not receive a deletion message By default a message is not broadcast 6 8 OpenVMS TRANSFER DTF File Transfer Operations NO POST_PROCESSING file spec Specifies a file that DTF should submit if an operation completes successfully The file can be an OpenVMS command procedure an MVS J CL file or a VM proc file The default is NOPOST_PROCESSING If you specify a DECnet file specification or a local OpenVMS file specification the file is submitted on the indicated DECnet node or on the
156. all DTF You may select one of the following options Y The transfer takes place in recoverable mode N The transfer operation takes place in nonrecoverable mode Note If you specify the RECOVERABLE field as Y but the DECnet VAX node does not have the DTF utilities software installed DECnet client nodes running MS DOS OS 2 Digital UNIX or ULTRIX do not have recoverable copy capability DTF rejects the transfer request CHECKPOINT This field allows you to set the number of logical records between checkpoints The number of logical records can be from 1 to 65535 Note e If you do not specify a value for this field the TRANSFER DTF on the client node uses a default value of 1000 7 8 Using the DTF for IBM Panel Interface e The CHECKPOINT field is valid only if you specify the RECOVERABLE field as YES If you specify the RECOVERABLE field as NO DTF does not permit you to enter a value in the CHECKPOINT field TRANSLATE Type N in this field to disable the translation of data from DMCS to EBCDIC No translation takes place if you copy a file from one IBM system to another EXTENDED This field lets you use the Data Translation Options panel to specify data translation options other than standard DMCS to EBCDIC translation Typing Y lets you see this panel This panel is described in Section 7 13 POSTPROCESS This field lets you use the Post Processing Options panel to specify a file at the remote node tha
157. and defines input and output file specifications and the environment associated with a file transfer You can define an input and an output file specification with one or more DEFINE subcommands then start the file transfer with a TRANSFER subcommand The syntax of the DEFINE subcommand is Using the DTF for IBM Command Processor 9 5 CHKPT OLD DISP NEW REP INCASE 1600 INDEN S50 INFDEF INFILE INLABEL INMDADDR INMDOWNER INMDPASS INNUM INPASS INRMT INUNIT INUSER INVOL OUTCASE DEFINE 1600 ber J OUTDEN 6250 OUTPRIMARY OUTSECONDARY OUTFDEF OUTFILE OUTLABEL OUTMDADDR OUTMDOWNER OUTMDPASS OUTNUM OUTPASS OUTRMT OUTUNIT OUTUSER OUTVOL NETMGR NULL RECDEF RECOVERY SERVER TRANSLATE 9 6 Using the DTF for IBM Command Processor 9 3 2 1 Note All transfer requests must specify an INFILE and an OUTFILE Most of the other keywords have defaults available The DEFINE subcommand is associated with keywords and keyvalues that define the following e The input file used in the transfer e The output file created or overlaid during the transfer e Parameters that define the environment in which the transfer is performed The following sections explain these keywords and keyvalues Keywords and Keyvalues for Specifying the Input File The following sections explain the DEFINE subcommand keywords and keyvalues that describe the input file used in the transfer INCASE This field specifies wh
158. and submit in one operation while some clients require two separate operations In addition IBM and OpenVMS clients have the capability of submitting a batch job to perform post processing after a successful file transfer 1 3 5 Directory Capability OpenVMS Digital UNIX ULTRIX RSX 11M M PLUS MS DOS and OS 2 Clients You can use the DTF software to obtain listings of files on IBM clients All clients supporting this directory capability allow you to specify wildcard characters that you can use to display groups of files 1 3 6 Recoverable File Transfer OpenVMS TRANSFER DTF and IBM Clients Only The OpenVMS DTF utilities and DTF for IBM software allow you to initiate a recoverable file transfer between a Digital OpenVMS client and an IBM MVS or VM dient for non VSAM files DTF for IBM software also allows you to initiate non VSAM recoverable copy operations between an IBM client and another IBM client If a recoverable file transfer operation fails because of a system or network error the transfer can be resumed from the last checkpoint after the system or network recovers The checkpoint and recovery feature is a valuable time saver especially for transferring large amounts of data An OpenVMS client does not support this recovery capability unless it has the TRANSFER DTF utility installed OpenVMS users should refer to Chapter 6 for a complete description of the TRANSFER DTF utility IBM users should refer to the chapter describing
159. ands you entered Recall all the DEFINE subcommands you entered RECALL immediately before a TRANSFER subcommand Restart a previously failed transfer from the last RESUME successful checkpoint Change the operation of the DTF command processor SET Show DTF defaults SHOW Remove input and output file specifications set up with CLEAR the DEFINE subcommand and reset default values Exit DTF END Syntax for Keywords Keywords are separated from the DTF subcommands by one or more spaces dtf subcommand keyword keyvalue 9 2 Using the DTF for IBM Command Processor Multiple keywords can be specified for the DTF subcommands by separating each keyword by one or more spaces dtf subcommand keyword keyvalue keyword keyvalue All keywords can be abbreviated to the shortest possible unique string Syntax for Keyvalues Keywords that allow keyvalues must use parentheses to enclose the keyvalue The opening parenthesis must immediately follow the keyword and the closing parenthesis must immediately follow the keyvalue Spaces cannot be embedded within the parentheses except for CMS file specifications dtf subcommand keyword keyvalue keyword keyvalue Keyword and Keyvalue Examples The following examples illustrate how to enter keywords and keyvalues DEFINE NETMGR DTF The DEFINE command was entered with the keyword NETMGR and the keyvalue DTF DEFINE SERVER NODE1 NETMGR DTF2 The DEFINE command was entered with the two
160. annot use wildcard characters in the IBM file specification when deleting files Table 12 3 OpenVMS DTF Level of Support for DELETE Command Switch Switch For IBM File Specifications NOLOG supported 12 6 MS DOS and OS 2 File Transfer Operations Examples MVS C NET FT gt DELETE PARIS DTFMVS WHITE DTF SPECS This command deletes the member SPECS from the PDS called WHITE DTF located on an IBM system The OpenVMS DTF server node is PARIS and the server account is DTFMVS Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers MVS C NET FT gt DELETE BOMBAY DTFMVS JONES DTF TEST VOL DTFV1 USE JOE PAS SECRET This command deletes the member TEST from the data set J ONES DTF located on the IBM system on volume DTFV1 The DTF server is BOMBAY and the server account is DTF MVS The IBM user ID J OE and IBM password SECRET are used to access the data set Assuming that the DTF server has a proxy record for IBM user ID J OE and that the operation is successful the password in the OpenVMS DTF server s proxy database is set to SECRET VM C NEFT FT gt DELETE NEWYRK DTFVM FLOWERS IRIS 1 USER NORMAN PASS IDUNNO This command deletes the file FLOWERS IRIS 1 The OpenVMS DTF server is NEWYRK and the server account is DTFVM The VM user ID is NORMAN and the VM p
161. ansfers e OPEN open a file for record access e READ read a record from a file e SEARCH search a file for a character string e SUBMIT REMOTE submit a file to a batch subsystem 1 8 Introducing the Data Transfer Facility DTF Product TYPE display a file on the terminal WRITE write a record to a file 1 4 2 OpenVMS TRANSFER DTF Commands COPY copy a file to another file SET QUEUE set TRANSFER DTF queue characteristics SHOW J OBS show active TRANSFER DTF requests SHOW QUEUE show TRANSFER DTF queue characteristics SHOW VERSION show TRANSFER DTF version number CANCEL J OB cancel a pending TRANSFER DTF request SHOW ERROR convert error codes to error messages 1 4 3 IBM DTF Panel Interface Operations Send a local file to a remote system Receive a file from a remote system Resume a failed transfer request 1 4 4 IBM DTF File Transfer Commands DTFSEND copy a local file to a remote file DTFRECV copy a remote file to a local file DTFRESUM resume a failed transfer request 1 4 5 IBM DTF Command Processor Commands DEFINE define transfer parameters LIST show defined transfer parameters TRANSFER transfer a file using defined parameters RECALL recall defined parameters RESUME resume a failed transfer request SET set interface characteristics SHOW show interface characteristics CLEAR clear transfer parameters and reset interface characteristics Introducing the Data Transfer Facility
162. assword is IDUNNO Assuming that the OpenVMS DTF server node has a proxy record for IBM user ID NORMAN and that the operation is successful the password in the OpenVMS DTF server s proxy database is set to IDUNNO 12 5 DIRECTORY Command To display a file list on an IBM DTF client use the NFT DIRECTORY command DIRECTORY switch filespec Table 12 4 shows the level of support DTF provides for the NFT DIRECTORY command switches For more detailed information about the DIRECTORY command refer to the PATHWORKS for DOS DECnet User s Guide or PATHWORKS for OS 2 Utilities Guide manuals MS DOS and OS 2 File Transfer Operations 12 7 Table 12 4 DTF Level of Support for DIRECTORY Command Switches Switch For IBM File Specifications BRIEF supported FULL supported Examples MVS C NFT FT gt DIR BRIEF RABBIT DTFMVS WHITE DTF USER WHITE PASSWORD TCHDWN Directory of RABBIT DTFMVS ETSOV2 WHITE DTF MONDAY USER WHITE PASS TCHDWN WHITE DTF TUESDAY USER WHITE PASS TCHDWN WHITE DTF FRIDAY USER WHITE PASS TCHDWN WHITE DTF WEEKEND USER WHITE PASS TCHDWN This command displays the names of all the members of the PDS called WHITE DTF located on an IBM system The OpenVMS DTF server node is RABBIT and the server account is DTF MVS The MVS user ID is WHITE and the user password is TCHDWN MVS C NET FT gt DIRECTORY RABBIT DTFMVS JONES DTF T VOL DTFVL This
163. assword of the minidisk that will contain the output file For a local output file this field is optional if you have the minidisk linked and accessed For more information on minidisk passwords see the MDxPASSWORD qualifier description in Section 2 3 3 FILE options VSAM If the output file is in VSAM format you must indicate this by typing a Y in this field TAPE UNIT If the output file is being written to tape you must indicate this by specifying a tape unit in this field The TAPE UNIT must match what is defined in the DTFUSER PARMS for NODEPARMS TAPEUNITS An IBM site can use additional or different unit names Check with the system programmer of the site where the output file will reside to get the unit names in use at the site NULL RECORDS This keyword indicates how DTF handles null records length 0 in an IBM environment Since the CMS file system does not support null length records DTF cannot write them to the indicated device You can enter one of the following four values e REJECT returns an error message e IGNORE ignores all null records The output file may have fewer records and the null records will not be restored if DTF is used to transfer the file from the VM system e SPACE inserts a 1 byte record in place of the zero length record The one byte is set to an EBCDIC space character e NONE accepts the record as is in an MVS environment In a VM environment an error will be given if a null record is enc
164. at the remote node If an abbreviation will not fit in the space provided leave the field blank and specify the abbreviation on the Remote Node Options panel USERID Specifies the user ID that should be used to access the input file on the remote system See Section 4 2 for information on user D syntax Note If the remote client node is running Digital UNIX or ULTRIX you must enter the user ID with the proper case PASSWORD Specifies the password of the user ID on the remote system See Section 4 2 for information on password syntax Using the DTF for IBM Panel Interface 7 11 Note If the remote client node is running Digital UNIX or ULTRIX you must enter the password with the proper case OPTIONS There may be additional information about the remote node that you can specify To see the panel for entering this information type the letter Y in the OPTIONS field and press the ENTER key This panel is described in Section 7 7 STORE on your local system AS this file name FILENAME This required field specifies the name the file you are copying from the remote system will have on your system after the transfer completes DISP This field specifies the disposition of the new file You can choose one of the following three values 1 NEW 2 OLD 3 REP NEW creates a new output file If a file with the same name already exists DTF does not copy the file This is the default OLD creates a new output f
165. at you can initiate from procedure languages 9 1 Invoking the DTF Command Processor Users of both TSO on MVS systems and CMS on VM can use the DTF command processor Type the DTF command after the READY prompt to start the DTF command processor and initiate DTF mode as shown DIF You can now use the DTF subcommands to transfer files between IBM and DECnet systems The following sections explain the DTF command and subcommands Using the DTF for IBM Command Processor 9 1 9 2 The DTF Command The DTF command allows you to use DTF to transfer files between an IBM system and DECnet nodes After you enter DTF you use the DEFINE subcommand to set up input and output file formats Then use the TRANSFER subcommand to transfer files The DTF command does not allow keyword parameters and cannot be abbreviated The syntax of the DTF command is DTF 9 3 DTF Subcommands Through the use of the following subcommands the DTF command allows you to perform the following functions Use this DTF subcom If you want to do this mand List all of the DTF subcommands and briefly explain the HELP function syntax and parameters of each subcommand Define the input file the output file and the environment DEFINE that the transfer will execute in Display all the DEFINE subcommands that you entered LIST but have not invoked with the TRANSFER subcommand Initiate the file transfer and erase all of the DEFINE TRANSFER subcomm
166. ate records from a domain on an IBM system e Enda DATATRIEVE session that is accessing an IBM file A 1 Defining a DATATRIEVE Domain to Access an IBM File A 1 1 Before Defining Your DATATRIEVE Domain Prior to issuing a DATATRIEVE DEFINE command to define your DATATRIEVE domain you should review the following considerations that might apply to your files 1 Alphanumeric data stored on IBM systems is typically in EBCDIC format while data on OpenVMS systems is usually stored in ASCII format Although DTF provides data translation between these two data formats you may need to use the VAX Common Data Dictionary and DTF data translation 2 If you are accessing a VSAM indexed file from DATATRIEVE you must specify the IBM file specification qualifier RFA when defining your domain if you are e modifying the file Using OpenVMS DATATRIEVE with DTF A 1 e forming collections using the FIND command The RFA qualifier ensures that your VSAM relative byte addresses RBAs will map to your RMS relative file addresses RFAs Refer to Chapter 2 for more information A 1 2 Using the DATATRIEVE DEFINE Command In the DATATRIEVE DEFINE command an IBM file specification identifies the domain that will be used to access an IBM file For example DTR gt DEFINE DOMAIN IBM DOMAIN USING EMPLOYEE _RECDEF ON DFN gt O SNADTF EMPLOYEE VSAM CLUSTER USERID DIFUSER RFA where O SNADTF is the node and server account information EMPL
167. ating an IBM data set The unused space is released to the smallest integral allocation used to create the file Usage Notes e This qualifier is valid only for creating or modifying a file e The default qualifier is NORELEASE RETENTION_PERIOD n Specifies the retention period in days before which a data set cannot be deleted Usage Notes e This qualifier is valid only for creating a file DTF File Specifications 2 27 e The default is not to specify a retention period e vm This qualifier is valid only for VSAM files e This qualifier is not recommended unless you specifically need it e If you attempt to overwrite a taperesident file before its retention period expires DTF for IBM waits until an operator grants permission to delete the file On MVS systems this operator is the MVS console on VM systems this operator is the Node Manager machine You can abort the operation locally by terminating the operation using a command or control character appropriate to your local system NO RFA OpenVMS clients only Tells DTF for IBM to maintain a table of VSAM relative byte addresses RBAs by primary key value RBAs are similar to the relative file addresses RFAs used in RMS Usage Notes e This qualifier is used only for indexed files requiring RFA access DATATRIEVE uses RFA access e The default is NORFA e The table of VSAM RBAs is maintained only for the life of the access e The am
168. ation no file will be selected 4See Section 5 10 1 for restrictions continued on next page OpenVMS File Transfer Operations 5 31 Table 5 14 Cont DTF Level of Support for SUBMIT REMOTE Command Qualifiers For IBM File Qualifier Specifications Commenis SINCE time supported 4See Section 5 10 1 for restrictions 5 32 OpenVMS File Transfer Operations Examples MVS SUBMIT REMOTE O SNADTF SMITH CNTL JCL USER SMITH This command submits the PDS member J CL of the SMITH CNTL data set to the MVS batch system The OpenVMS DTF server node is the local node and the server account is SNADTF The MVS user ID is SMITH Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers The file J CL must not contain any records that exceed 80 bytes VM SUBMIT REMOTE O DTFVM TESTBAT EXEC USER GIBSON BATCH CMSBATCH CLASS A This command submits the file TESTBAT EXEC to the batch machine CMSBATCH in the dass A The OpenVMS DTF server node is the local node and the server account is DTFVM The VM user ID is GIBSON Account verification on the VM system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers The file TESTBAT EXEC must not contain any records that exceed 80 bytes 5 16 TYPE Command To display on a terminal a file
169. ault extension quality XAB L_LOC Not filled in Location XAB W_RFI Not filled in Related file identifier XAB W_VOL Not filled in Related volume number XABDAT Disallowed Date and time XAB XABKEY Key definition XAB XAB B_DBS Not filled in Data bucket size XAB W_DFL Not returned Data bucket fill size XAB B_DTP Not filled in Data type of the key XAB L_DVB Not filled in First data bucket virtual block number XAB B_IBS Not filled in Index bucket size XABSW_IFL Not filled in Index bucket file size XAB L_KNM Not filled in Key name buffer address XAB B_LVL Not filled in Level of root bucket XAB W_MRL Not filled in Minimum record length XAB B_NSG Always 1 Number of key segments XAB B_NUL Not supported Null key value XAB W_POSn Only POSO Key position returned XAB B_ Always 3 Prolog level PROLOG continued on next page RMS File System and Programming Constraints B 17 Table B 11 Cont OPEN XAB Output Fields Field Name Option Restriction Description XAB L_RVB Not returned Root bucket virtual block number XAB B_SIZn Only SIZO Key size returned XABPRO Disallowed Protection XAB XABRDT Disallowed Revision date and time XAB XABSUM Summary XAB XAB W_PVN Always 3 Prolog version number B 18 RMS File System and Programming Constraints B 3 12 PARSE There are no restrictions associated with the PARSE input and output fields B 3 13 PUT Table B 12 describes the special fields of the P UT RMS service call Table B 12 PUT RAB Input F
170. ay statistics on current transfer LKG 8302 93R Using the DTF for IBM Panel Interface 7 19 MVS You can cancel a transfer that is in progress at any time The method used to cancel a transfer depends on the terminal you are using On non SNA terminals press Reset then PA1 and then type C followed by Enter On SNA terminals press Attn and then type C followed by Enter MVS You can request a status report for transfer in progress at any time The method used to get a status report for a transfer depends on the terminal you are using On SNA terminals press Reset then PA1 and then type Q followed by Enter On non SNA terminals press Attn and then type Q followed by Enter After typing Q the system provides a continuously updated display of the transfer in progress To return to the wait state from SNA terminals press Reset then PA1 and then type W followed by Enter To return to the wait state from non SNA terminals press Attn then type W followed by Enter On VM systems you can cancel a transfer that is in progress at any time by typing the command CANCEL and pressing Enter You can request a status report for a transfer in progress by typing the command QUERY and pressing Enter 7 20 Using the DTF for IBM Panel Inte
171. ay then submit this file at any time SAVE generated job in this file FILENAME or DATA SET NAME If you chose the GENerate function specify the file or data set where DTF should save the generated job OVERWRITE Specify Y if you wish to overwrite an existing file Using the DTF for IBM Panel Interface 7 43 JOB CONTROL information BATCH MACHINE to do copy VM This is the name of the virtual machine you wish to perform the copy JOB CLASS VM Specify a job class valid for the indicated batch machine Your A disk READ PASSWORD M This is the READ password for your A minidisk For more information on minidisk passwords see the MDxPASSWORD qualifier description in Section 2 3 3 JCL COMMANDS gt Enter up to four lines of J CL commands to be stored in the file you indicated Note VM You must provide the minidisk address owner and password for the local file involved in the transfer In addition when accessing a local file for write access you must log off before the batch job runs or the batch job will not be able to obtain write access 7 44 Using the DTF for IBM Panel Interface 8 Using the DTF for IBM File Transfer Commands In addition to the DTF for IBM panel interface you can use single line DTF for IBM commands to transfer files This chapter explains how to use the DTF file transfer commands to copy files from one system to another You ca
172. c Bit string D_ FLOATING F_FLOATING G FLOATING H_ FLOATING Zoned decimal Bit string Long floating point Short floating point Long floating point Extended floating point An error might be reported when running an IBM application program IBM accepts a variety of sign conventions for zoned decimal data types while Digital has only one sign convention for zoned numeric data types When translating from the Digital format to the IBM format DTF always uses the most common IBM sign convention for zoned decimal None If precision is lost in the data mapping an error is reported and the file transfer is aborted You can tell DTF to ignore precision loss errors by using the IGNORE qualifier see Chapter 2 If precision is lost in the data mapping an error is reported and the file transfer is aborted You can tell DTF to ignore precision loss errors by using the IGNORE qualifier see Chapter 2 If an underflow or overflow condition occurs in the data mapping an error is reported and the file transfer is aborted If precision is lost or if an underflow or overflow condition occurs in the data mapping an error is reported and the file transfer is aborted You can tell DTF to ignore precision loss errors by using the IGNORE qualifier see Chapter 2 F 6 DTF Data Translation Table F 3 Limitations on Data Transferred from IBM to Digital IBM Data Type Digital Data Type Limitations 2 byt
173. can contain the DTF command However that record must precede the record containing the first DTF subcommand e The record that contains the DTF command cannot contain any DTF subcommands All subsequent DTF subcommands must occupy separate records e A DTF subcommand such as DEFINE could have several keywords thereby using more characters than a single CL card can accept assuming 80 characters as the norm If the subcommand and its keywords and keyvalues do not fit on a single J CL card you can use standard TSO line continuation rules and continue the subcommand string on the next card 9 40 Using the DTF for IBM Command Processor The IBM manuals TSO Command Language Reference or the TSO E Command Language Reference explain how to use line continuation The manuals also explain how to enter comments in the SYSTSIN file records e The SYSTSIN file can contain other TSO commands or command processors However these must either precede the record containing the DTF command or follow the record containing the DTF END subcommand The following example shows three files each with records that contain the DTF command DTF subcommands and a TSO command The first file is acceptable the last two are not File 1 File 2 File 3 Record 1 DTF DTF DEFINE DTF Record 2 DEFINE Any TSO command Record 3 TRANSFER DEFINE File 1 is acceptable The first record contains the DTF command the DTF command precedes the DTF subcommands and
174. cated on the IBM DTF client under the user ID mike to the standard output Note that in the IBM file specification the options userid and password are given This serves to override the default account set up for the account dtfmvs and the user mike on the server veena Also the password for the server account dtfmvs is null as indicated by the double slashes VM deat dtfsrv dtfvm tuesday orders 10 2 ULTRIX and UNIX File Transfer Operations This command displays the file tuesday orders to the standard output The VM user ID and password are taken from the OpenVMS DTF server s proxy database The password for the server account dtfym on OpenVMS DTF server node dtfsrv is null as indicated by the double slashes 10 3 dcp Command To transfer ASCII or binary files between a DECnet ULTRIX or DECnet OSI for Digital UNIX node and an IBM DTF dient use the DECnet ULTRIX or DECnet OSI for Digital UNIX dcp command dcp option input file spec output file spec The dcp command allows an ULTRIX or UNIX user to do the following e Copy an ASCII or binary file residing on an IBM DTF client to any location in a DECnet network e Copy an ASCII or binary file on a DECnet network to any IBM DTF client e Copy an ASCII or binary file residing on an IBM DTF client to any other IBM DTF dient e Append the specified input file to the specified output file Be sure that the output file you specify already exists Note
175. cceed but the VM system will delete the empty file when it is closed Note that you can use the CREATE command with VM DTF clients as long as you enter data before ending the file data with CTRL The FTS utility does not support a file creation command Table 11 4 DTF Level of Support for CREATE Command Qualifying Switches For IBM File DCL CREATE Qualifier NFT Switch Specifications CONTIGUOUS CO not supported LOG LO filespec supported MACY 11 RAT MACY11 not supported NEW_VERSION INV not supported NO_SPAN RAT NOSPAN_ ignored OWNER uic F O owner not supported PRINT SP not supported PROTECTION code PR pr info not supported REPLACE SU supported continued on next page RSX 11M M PLUS File Transfer Operations 11 7 Table 11 4 Cont DTF Level of Support for CREATE Command Qualifying Switches For IBM File DCL CREATE Qualifier NFT Switch Specifications SUBMIT SB supported Examples MVS SCREATE BIGVAX MVSDTF GARY DTF TUESDAY USER GARY PASS SECRET This command creates a new member TUESDAY in the GARY DTF data set on the IBM system You can now enter data or press CTRUZ to exit The OpenVMS DTF server node is BIGVAX the server account is MVSDTF the MVS account is GARY and the MVS password is SECRET VM SCREATE DTFSRV VMDTF NEWDATA EXEC USER GARY PASS GUESSME This command creates a new file NEWDATA EXEC on the IBM system Yo
176. ccount is DTF the OpenVMS DTF server node is OXEN and the VM user ID is GARY The minidisk address is 192 and its password is XYZ The file is created as a mode 1 file 5 26 OpenVMS File Transfer Operations 5 12 OPEN Command To open a file residing on an IBM client for either reading or writing use the DCL OPEN command OPEN logical namd filespec Table 5 11 shows the level of support DTF provides for the DCL OPEN command qualifiers For more detailed information about the OPEN command refer to the DCL Dictionary Table 5 11 DTF Level of Support for OPEN Command Qualifiers For IBM File Qualifier Specifications Comments APPEND supported ERRORAabd supported READ supported SHARE option supported Not supported for non VSAM output files WRITE supported Examples MVS OPEN READ WRITE FILE TENNIS PROS GIBSON DTF OPEN This command opens an existing PDS member OPEN of the GIBSON DTF data set located on the IBM client This data set is opened for both read and write operations Record level access to GIBSON DTF OPEN is performed through READ and WRITE commands that reference FILE1 The OpenVMS DTF server node is TENNIS and the server account is PROS Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers VM OPEN READ WRITE INFILE CARS SNADTF FIFTIES EXEC USER PA
177. cessing file is an EXEC file on a DTF for IBM VM system MVS TRANSFER DTF TRANS DTF gt COPY SYSSLOGIN LEDGER DAT _TRANS DTF gt O SNADTF USERID LEDGER ACCOUNT _TRANS DTF gt POST 0 SNADTF USERID JCL POST This COPY command requests that once the file SYS LOGIN LEDGER DAT is copied to O SNADTFE USERID LEDGER ACCOUNT and the file transfer completes successfully then DTF will submit the O SNADTF USERID J CL POST file to a J ES subsystem The post processing file is an MVS J CL file on a DTF for IBM MVS system OpenVMS TRANSFER DTF TRANS DTF gt COPY POST USER DTFUSER POST COM _TRANS DTF gt USERS DTFUSER LEDGER DAT O DTFVM ACCOUNT DAT This COPY command requests that once the file LEDGER DAT is copied to O DTFVM ACCOUNT DAT and the transfer completes successfully then DTF will submit the file POST COM to SYS BATCH The post processing file is an OpenVMS command procedure file on an OpenVMS system OpenVMS TRANSFER DTF File Transfer Operations 6 13 6 4 Defining OpenVMS DTF Queue Attributes To define and modify OpenVMS DTF queue attributes use the TRANSFER DTF SET QUEUE command SET QUEUE queuenamel l qualifiers Operator OPER privileges are required to use the SET QUEUE command Command Parameter queue name Specifies an OpenVMS DTF queue name The queue name must be an OpenVMS DTF queue name The default for this parameter is SNADTF QUEUE You can
178. cifies the kind of sharing allowed among users across multiple regions of a single CPU 1 specifies that any number of users can have read access or that a single user can have read and write access to a data set This is the default setting for VSAM files 2 specifies that any number of users can have read access and that a single user can have read and write access to a data set 3 specifies that any number of users can have read and write access to a data set 4 specifies that any number of users can have read and write access to a data set and that buffers used for direct processing are refreshed for each request e The optional value option 2 specifies the amount of sharing allowed among users across systems 3 specifies that any number of users can have read and write access to a data set This is the default setting for VSAM files 4 specifies that any number of users can have read and write access to a data set and that buffers used for direct processing are refreshed for each request Usage Notes e For data integrity purposes you should make sure that the values supplied for this attribute are the same for the DATA and INDEX subsections e ThelBM system programmer can set a default for SHARE_OPTIONS at installation time This value will be used at creation time 2 44 DTF File Specifications 3 DTF Supported File Types This chapter describes the file types supported by DTF and restrictions on the types of file tran
179. command removes the data set richards dtf file on the BM DTF client The OpenVMS DTF server node is veena and the server account is dtfmvs The MVS user ID is richards and the password is snowy MVS drm veena dtfmvs eric dtf vol tsov2 This command removes the data set eric dtf on the IBM DTF dient The file is on volume tsov2 The OpenVMS DTF server node is veena and the server account is dtfmvs Account verification on the MVS system is installation dependent Contact your systems administrator for information on the USERID and PASSWORD qualifiers VM drm dtfsrv dtfvm test dtf user james This command removes the data set test dtf on the VM system The OpenVMS DTF server node is dtfsrv and the server account is dtfvm The VM user ID is james and the IBM password is taken from the OpenVMS DTF server s proxy database 10 8 ULTRIX and UNIX File Transfer Operations 10 7 Error Reporting Most error messages consist of a primary message and a secondary message followed by a secondary status value STV The primary and secondary messages are usually self explanatory STV codes are reported as hexadecimal numbers Messages appear in a format similar to the following command primary text secondary text Secondary Status OX he number where command is the command that caused the error primary text is the primary error message secondary text is the secondary error message and hex numb
180. command to access files owned by NASHUA RAFAL The DTF server software on node TAMPA receives the request DTF changes its name to the IBM user name and a SNARCOPY request is issued NASHUA sees that TAMPA MARTIN is trying to access a file in the RAFAL account DECnet proxy checks if user TAMPA MARTIN is set up for access to RAFAL If the proxy entry is defined the copy continues Note For more detail on how proxy works refer to the Digital SNA Data Transfer Facility for OpenVMS Management Data Security 4 9 9 OpenVMS File Transfer Operations This chapter describes how to use the OpenVMS DCL command interface with the DTF software to transfer files You can use the DCL commands supported by DTF at any OpenVMS VAX or OpenVMS Alpha node in a DECnet network so long as that node can access the OpenVMS DTF server You simply include the OpenVMS DTF server node as part of the file specification No special software is required at the client node You should use the DCL command interface when you need to copy small amounts of data quickly and interactively The DCL command interface does not provide you with a checkpoint and recovery feature usually desired for large file transfers You should use the TRANSFER DTF utility to transfer large amounts of data or when you desire transfer operations to occur as batch jobs The TRANSFER DTF utility provides you with a checkpoint and recovery feature that restarts a file trans
181. ction C 6 C 3 2 Modifying File Definition ALTERNATE_INDEX Sections C 7 C 4 Removing an Entry from the File Definition Database C 8 D VSAM File Support D 1 A VSAM Primer for Non IBM Users 0000 00000 ee D 1 D 1 1 Sequential and Relative Files 0 00005 D 1 D 1 2 Indexed Filesi wake atea E She Sve eR Was ate wa a D 2 D 2 DTF for IBM and VSAM Naming Conventions D 5 D 2 1 DTF for IBM Naming Conventions assas aaa D 6 D 2 2 VSAM Naming Conventions s saaa D 6 D 2 3 Choosing Your Own Name for ALTERNATE_INDEX D 7 D 3 VSAM Cluster Attribute Defaults anaana D 8 E FTAM File Support E 1 Overview of FTAM 0 ccc eee eens E 1 E 2 FTAM User Facilities nuun eee ene E 2 E 2 1 FTAM Components a liai paa taag 0c eee eee E 3 E 2 2 File Transfers Using FTAM Software and a DAP FTAM Gateway ie tev ees Peele Ped eee be eee EP ee ee E 3 E 3 FIAM Document TYPES ros sateka cee es E 6 E 3 1 RESUrICUONS see ad bs Bene a al Weed i a E 6 E 4 Examples of OSI Initiated File Transfer Operations E 8 E 4 1 Examples of File Transfers Using the DAP FTAM GalOWay resas i eats ante en ae eee en ae wae ee E 10 F DTF Data Translation F 1 Controlling Data Translation on DECnet I nitiated File Transfer Sieur bata Stade eaten aay hehe EEG ae PEG ae F 1 F 2 Controlling Data Translation on BM Initiated File Transfers F 2 F 3 DMCS EBCDIC Translation Tables
182. cular code An explanation of both sets of abbreviated message text and suggested actions to correct any problems can be found in the Digital SNA Data Transfer Facility for OpenVMS Problem Solving and Messages manual If you receive any messages that are not listed see your OpenVMS DTF server manager Table 12 7 DAP Error Codes Status Code ASCII Text 4 471 DTFCDDREC 4 472 DTFCFGFIL 4 473 DTFCVT 4 474 DTFDEFFIL 4 475 DTFFALSHT 4 476 DTFNOFIL 4 477 DTFNOREC 4 501 DTFOPRABO 4 502 DTFQUASYN 4 503 DTFQUAVAL 4 506 DTFSESEST 4 507 DTFSESTER 4 510 DTFTRATBL 4 511 DTFUNSTYP continued on next page 12 12 MS DOS and OS 2 File Transfer Operations Table 12 7 Cont DAP Error Codes Status Code ASCII Text 4 512 DTFVERMIS 4 513 DTFACC 4 514 DTFCRE MS DOS and OS 2 File Transfer Operations 12 13 A Using OpenVMS DATATRIEVE with DTF DATATRIEVE access to IBM file types is a feature that enables you to define DATATRIEVE domains that reference non VSAM sequential VSAM sequential VSAM relative and VSAM indexed files that reside on an IBM system Refer to the VAX DATATRIEVE User s Guide for more information about VAX DATATRIEVE You can use DATATRIEVE ADT to define record definitions for your IBM files or to use existing record definitions if they are available You can use DATATRIEVE commands to e Define a DATATRIEVE domain to access an IBM file e Prepare a DATATRIEVE domain for access to an IBM file e Manipul
183. curity 4 5 DECnet Initiated Proxy The IBM proxy mechanism passes the user s DECnet node or TCP IP host name and account directly to one of the IBM security systems such as ACF 2 The IBM security system verifies that a proxy entry has been made for that user at that node and directly grants access based on rules set up by the IBM system programmer The IBM system programmer or security administrator implements the security system based on predetermined rules Refer to Digital SNA Data Transfer Facility Installation MVS or Digital SNA Data Transfer Facility Installation VM for information on DE Cnet initiated proxy through MVS proxy or VM proxy Figure 4 1 illustrates a verification to access data by MVS proxy Note that this DE Cnet environment could also be TCP IP Data Security 4 5 Figure 4 1 Request Verified by MVS Proxy DECnet remote node NASHUA OpenVMS 4 6 DECnet server node TAMPA DTF server software T DTF for IBM software IBM client system Data Security NASHUA SMITH SNADTF KENT VMS DTF proxy database Security system database LKG 5577 93R 1 DECnet user NASHUA SMITH requests access to files owned by IBM user KENT 2 The DTF for IBM software passes the DECnet user s DECnet node name NASHUA and account SMITH directly to the IBM security system The IBM security system verifies that a proxy entry has been made for NAS
184. d N O PAD H b x supported PROLOG n supported INOJSHARE supported continued on next page OpenVMS File Transfer Operations 5 9 Table 5 4 Cont DTF Level of Support for CONVERT Command Qualifiers For IBM File Qualifier Specifications Comments INOJSPREADSHEET ignored INOJSTATISTICS supported WORK_FILES supported INOJREAD_CHECK ignored RECLAIM not supported INO SORT ignored INOJTRUNCATE supported INOJWRITE_CHECK ignored You may need to use the CONVERT MERGE command to prevent transfer failures due to differences in collating key sequences between EBCDIC and ASCII Examples MVS CONVERT FDL FIXED FDL LKG IBMSYS2 GARY VARIABLE LEN _S FIXED_LEN DAT PAD This command converts the variable length data set VARIABLE LEN on the IBM DTF client to the fixed length file FIXED_LEN DAT located on the current default OpenVMS directory Nulls are used to pad the record if there are any discrepancies in length The FDL file used is FIXED FDL The OpenVMS DTF server node is LKG and the server account is IBMSYS2 Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers MVS CONVERT MERGE EMPLOYEE_INDEX DAT LKG IBMSYS1 GARY LARGE This command will merge all the records in the EMPLOYEE_INDEX DAT file into the indexed file GARY LARGE Note that GARY LARGE m
185. d All BM resident files have a UIC of INOJCONCATENATE supported INOJCONFIRM supported NO JCONTIGUOUS ignored CREATED supported 0 0 If you specify the BY_OWNER qualifier with both OpenVMS and IBM input file specifications with a UIC other than 0 0 this qualifier affects only the OpenVMS input file specification lf specified for an IBM file specification the qualifier is ignored 31 specified for an IBM input file specification no file will be selected 4See Section 5 10 1 for restrictions 5 12 OpenVMS File Transfer Operations continued on next page Table 5 5 Cont DTF Level of Support for COPY Command Qualifiers For IBM File Qualifier Specifications Comments EXCLUDE filespecf ignored EXPIRED supported MVS EXTENSION n supported For IBM files each extension allocates enough tracks or cylinders to hold n 512 byte blocks If ALIGNMENT TRACKS is specified the extension is in tracks If ALIGNMENT CYLINDERS is specified the extension is in cylinders INO JLOG supported MODIFIED supported NOJOVERLAY supported PROTECTION code ignored INOJREAD_CHECK not supported INO JREPLACE supported SINCE time supported INOJTRUNCATE ignored VOLUME n ignored If you use the VOLUME qualifier the following error message is displayed SCOPY E BADVALUE VOLUME is an invalid keyword value The CREATE command will continue t
186. d Qualifying Switches For IBM File DCL APPEND Qualifier NFT Switch FTS Switch Specifications Command Qualifiers LOG LO filespec LO filespec supported NOWARNINGS NM I supported lOperation not available continued on next page 11 2 RSX 11M M PLUS File Transfer Operations Table 11 2 Cont DTF Level of Support for APPEND Command Qualifying Switches For IBM File DCL APPEND Qualifier NFT Switch FTS Switch Specifications File Qualifiers DATA_TYPE ASCII AS AS supported DATA_TYPE IMAGE IM AM supported MACY11 RAT MACY11 2 not supported OWNER uic F O owner not supported PRINT SP not supported PROTECTION code PR pr info not supported TRANSFER_MODE AX supported AUTO TRANSFER_MODE BK supported BLOCK TRANSFER_MODE _ RC supported RECORD 10peration not available Examples MVS SAPPEND PUFF TEST SEA SNADTF DRAGONS MAGIC PUFF USER JACKIE This command appends the latest version of the file PUFF TEST in the current RSX default directory to the PDS member PUFF of the DRAGONS MAGIC data set The server account is SNADTF on the OpenVMS DTF server node SEA The MVS user ID is J ACKIE Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers MVS FTS gt INVENTORY DAT F INGER SNADTF GIBSON FILTERS USER GIBSON PASS SMALL FTS
187. d in Data bucket size XAB W_DFL Not returned Data bucket fill size XAB B_DTP Not filled in Data type of the key XAB L_DVB Not filled in First data bucket virtual block number B 12 RMS File System and Programming Constraints continued on next page Table B 7 Cont DISPLAY FAB and XAB Output Fields Field Name Option Restriction Description XAB B_IBS Not filled in Index bucket size XABSW_IFL Not filled in Index bucket file size XAB L_KNM Not filled in Key name buffer address XAB B_LVL Not filled in Level of root bucket XAB W_MRL Not filled in Minimum record length XAB B_NSG Always 1 Number of key segments XAB B_NUL Not supported Null key value XAB W_POSn Only POSO Key position returned XAB B_ Always 3 Prolog level PROLOG XAB L_RVB Not returned Root bucket virtual block number XAB B_SIZn Only SIZO Key size returned XABPRO Disallowed Protection XAB XABRDT Disallowed Revision date and time XAB XABSUM Summary XAB XAB W_PVN Always 3 Prolog version number RMS File System and Programming Constraints B 13 B 3 7 ERASE There are no restrictions associated with the ERASE input and output fields B 3 8 FIND Table B 8 describes the special fields of the FIND RMS service call Table B 8 FIND RAB Input Fields Field Name Option Restriction Description RAB L_ROP Record processing options RAB V_NLK Ignored No lock RAB V_NXR Ignored Nonexistent record processing RAB V_REA Ignored Lock for read RAB V_RLK Ignored
188. d then rejects the subcommand Internal error conditions An internal error condition in DTF return code 12 causes DTF to cease operations in batch mode and immediately return to TSO TSO then processes any remaining records within the SYSTSIN file If these records contain DTF subcommands TSO issues an error message for each record and then rejects the subcommand Missing passwords DTF does not prompt for missing passwords in batch mode Lower case Digital UNIX or ULTRIX file specifications user IDs and passwords Be careful when you use DTF in batch mode to access Digital UNIX or ULTRIX nodes Digital UNIX or ULTRIX file specifications user IDs and passwords must all be entered in lowercase Since IBM J CL requires uppercase for control cards files are usually edited with the uppercase option in the ISPF editor this is CAPS ON in the edit profile The editor option must be reset to allow the use of lowercase characters when you enter the DTF DEFINE subcommands 9 44 Using the DTF for IBM Command Processor 9 7 DTF Return Codes in DTF Batch Mode Operations The DTF command processor returns with a completion code that reflects the most severe error encountered MVS TSO uses this completion code as the job step completion code If other TSO commands are included within the SYSTSIN file TSO uses the most severe error encountered in all TSO commands including the DTF completion code as the job step completion code
189. de 1 The server account is DTFVM the OpenVMS DTF server node is PARIS and the user account on the VM system is ROBERT The password for the ROBERT account is supplied from the OpenVMS DTF server s proxy database VM FTS gt BANGOR MUSIC BLUES EXEC USER BROTHERS DE 11 10 RSX 11M M PLUS File Transfer Operations This command deletes the file named BLUES EXEC The server account is MUSIC the OpenVMS DTF server node is BANGOR and the user account on the VM system is BROTHERS The password for the BROTHERS account is supplied from the OpenVMS DTF server s proxy database VM FT gt CONWAY DTFVM COUNTRY EXEC USER ROBERT DE This command deletes the file named COUNTRY EXEC The server account is DTFVM the OpenVMS DTF server node is CONWAY and the user account on the VM system is ROBERT The password for the ROBERT account is supplied from the OpenVMS DTF server s proxy database 11 6 DIRECTORY Command To list one or more files on an IBM client use the DCL DIRECTORY command DIRECTORY filespec or the NFT command with the LI FU AT or BR switch output file switches input filaswitches LI width FU width AT BR Refer to the sample directory shown at the end of this command description for information about directory contents Notes The DIRECTORY command is not supported for IBM tape volumes The FTS utility does not support a file directory command See Chapter 2 for
190. des on disk DTF ignores this field 7 36 Using the DTF for IBM Panel Interface e If you do not specify this field and the output file resides on tape DTF assumes that standard tape labels SL are used FILE NUMBER Specifies a sequential file number on tape between 1 and 9999 e Section 3 3 5 describes additional restrictions that may apply for tape resident files e If the output file resides on disk DTF ignores this field e If you do not specify this field and the output file resides on tape DTF assumes that the FILE NUMBER is 1 DENSITY Specifies the density of the tape volume where the output file will be written Accepted values are 1600 or 6250 e Section 3 3 5 describes additional restrictions that may apply for tape resident files e If the output file is not on tape DTF ignores this field e f you do not specify this field and the output file is on tape DTF assumes the highest density allowed for the tape unit DTF options FILE DEFINITION Specifies the name of an entry in the DTF file definition database on the OpenVMS DTF server node Chapter 2 explains file definition records Using the DTF for IBM Panel Interface 7 37 7 12 The Network File Options Panel Figure 7 12 Network File Options Panel DTF ISPF NETWORK FILE OPTIONS Fill in the required fields and press ENTER to continue NETWORK FILE NAME if more space is required FILE NAME gt LKG 8293 93R DTF displays the Network File
191. description of VSAM indexed file structures If the assigned KRF sequence is not satisfactory to you then use this qualifier to assign the desired KRF sequence The values for this qualifier are given in position length pairs The first pair identifies the position and length of the primary key key of reference number 0 the second pair identifies the first alternate index key of reference number 1 and so forth Usage Notes e The default is to use key of reference number 0 the primary key e You are altering the KRF sequence only for the life of this access Use this qualifier only if you have an existing application that requires a different KRF sequence than the default e If you supply a position flength pair that does not match any key then the access will fail with an error e The number of position length pairs that you specify can be less than the actual number of keys in the file e You can specify a maximum of 255 key pairs in one KEY qualifier 2 20 DTF File Specifications LABEL label Specifies one of the following directory label formats for reading or writing data sets to tape e AL ANSI Version 1 labels or ISO ANSI FIPS Version 3 labels e BLP Bypass label processing e NL Non labelled e SL Standard label Usage Notes e This qualifier is ignored with nontape devices e The default for this qualifier is LABEL SL e mvs Only SL or AL can be specified with an MVS tape input file e VM Only
192. dex 2 Comparing files See Files comparing contents from OpenVMS DCL 5 18 COMPONENT_ALLOCATION file definition attribute 2 42 CONNECT RMS service call B 7 CONVERT command OpenVMS DCL 5 9 Converting files See Files copying indexed and relative from OpenVMS DCL 5 9 COPY TRANSFER DTF command 6 3 COPY command OpenVMS DCL 5 11 PATHWORKS for DOS NFT 12 3 PATHWORKS for OS 2 NFT 12 3 RSX 11M M PLUS DCL 11 4 Copying files See Files copying indexed and relative See Files copying sequential See Files copying with checkpoint and recovery from OpenVMS DCL 5 11 5 24 CREATE command OpenVMS DCL 5 14 RSX 11M M PLUS DCL 11 7 CREATE RMS service call B 8 Creating a data definition F 3 Creating files See Files creating from OpenVMS DCL 5 14 D Data definition creating F 3 Data security IBM passwords 2 27 introduction 4 1 SECURITY_DATA qualifier 2 29 specifying IBM user IDs 2 32 Data translation F 1 See also TRANSLATE and TRANSLATE keyword See also Translation modes Data translation cont d errors during F 5 introduction 1 6 RECORD_DEFINITION qualifier 2 27 TRANSLATE qualifier 2 31 using the panel interface 7 39 Data types translation of Digital and IBM F 4 DATATRIEVE and DTF A 1 Date and Time Restrictions 5 24 dcat DECnet ULTRIX command 10 1 DCL commands OpenVMS APPEND 5 2 BACKUP 5 5 CLOSE 5 8 CONVERT 5 9 COPY 5 11 CREATE 5 14 DELETE 5 16 DIFFEREN
193. ding single quotation marks are optional if no file qualifiers are specified where node specifies the node on which the OpenVMS DTF server software resides DTF File Specifications 2 1 access control VM ibm filename 2 2 DTF File Specifications specifies the name of the OpenVMS DTF server account assigned by your OpenVMS DTF server manager The account name is usually SNADTF For more information about the correct value for the access control parameter contact your OpenVMS DTF server manager Digtial UNIX ULTRIX MS DOS and OS 2 Clients Only If you do not enter a password in the access control string the DECnet ULTRIX DECnet OSI or PATHWORKS for DOS software will prompt you for the password If you enter a double slash in the access control string no password prompt appears specifies an IBM VM CMS file name or a VSAM file name VM VSAM file names follow the same syntax rules as MVS file names VM CMS file names have the following format name filetype fil emode maclib member where name specifies an unqualified file name that must be 1 to 8 characters long filetype specifies an IBM file type 1 to 8 characters long If the file is a maclib then the filetype must be MACLIB filemode specifies an optional two character IBM file mode The file mode is made up of an optional file mode letter followed by an optional file mode number The file mode letter specifies the minidisk on which the
194. e Length 1 to 8 characters Using the DTF for IBM Command Processor 9 17 Usage Notes e If the remote client node is running Digital UNIX or ULTRIX you must enter the user ID with the proper case e Ifyou are using a batch dialog you must include your user ID e If you specify the OUTFILE with access control information the DTF command processor will ignore this keyword OUTVOL volume serial number Specifies a volume serial number that will contain the IBM output file volume serial number A volume serial number that will contain the IBM output file Length 1 to 6 characters Usage Note e The OUTVOL keyword is valid only with an IBM file specification 9 3 2 3 Keywords and Keyvalues for Specifying Transfer Parameters The following sections describe the keywords and keyvalues that you use to specify the transfer parameters that define the environment that the transfer will be executed in CHKPT checkpoint interval Specifies the number of logical records that can be transferred between checkpoints during a recoverable file transfer checkpoint interval The number of logical records that can be transferred between checkpoints Range 1 to 65535 Usage Notes e If you do not specify a keyvalue for the CHKPT keyword the TRANSFER DTF on the client node uses a default value e The CHKPT keyword is valid only if you specify the RECOVERY keyword as YES If you specify RECOVERY NO the command processor does not
195. e access control drive directory is the 1 to 6 character name of the DECnet cient is optional information that can include a user ID and password is an optional drive name The drive name is terminated with the colon and backslash characters such as A and C is an optional path name to a directory The path name is terminated by the backslash DTF File Specifications 2 7 filename is an alphanumeric file name of up to 8 characters The file name must be terminated by a period type is an alphabetic file extension of up to 3 characters For example C ROGERS REPORT TXT refers to the file REPORT TXT that is stored in the directory ROGERS on device C 2 2 4 Specifying Remote ULTRIX and Digital UNIX Files Enter the renote ULTRIX or Digital UNIX file specification as shown The node and optional access control portions of the file specification were previously described in Section 2 2 The file name portion of the file specification must be enclosed in slashes as shown Note ULTRIX file names are case sensitive That is file abc is not the same file as ABC node access control path filename where node is the 1 to 6 character name of the DECnet client node access control is optional information that can include a user ID and password path is the absolute or relative path name If you do not specify an absolute path name the absolute path used is based on the access control
196. e qualifier allows you to pass from 1 to 255 characters to the IBM security system The qualifier s use depends on the installation options chosen for DTF for IBM Check with the IBM system programmer for more information on how to use this qualifier Usage Note e The default is to supply no security data SEQUENCE_NUMBER n Specifies a sequential file number from 1 to 9999 for reading or writing files on tape Usage Notes e This qualifier is ignored with nontape devices e The default qualifier is SEQUENCE_NUMBER 1 NO SINGLE Specifies whether data is written as a separate block or multiple records are written to each block The SINGLE qualifier specifies an unblocked file that is every record is written as a separate block If the NOSINGLE qualifier is specified a blocked file is created that is multiple records are included in a single block Usage Notes e This qualifier is valid only for creating a file e The default qualifier is NOSINGLE e vM This qualifier is valid only for taperesident files e The SINGLE qualifier is not recommended because in most cases it results in inefficiently used disk space DTF File Specifications 2 29 SMSDCLASS data class MVS SMSMCLASS management class MVS SMSSCLASS storage class MVS If you specify the SINGLE qualifier the BLOCK_SIZE qualifier is ignored Refer to the BLOCK_SIZE qualifier for additional information Specifies the SMS
197. e Copy a sequential file from any IBM client to any other IBM client The COPY command does not support the checkpoint or recovery feature If you require the checkpoint and recovery feature use the TRANSFER DTF COPY command described in Chapter 6 The COPY command does not support indexed or relative file transfers To copy indexed or relative files use the DCL CONVERT command see Section 5 5 the EXCHANGE NETWORK command see Section 5 11 or the TRANSFER DTF utility See Chapter 6 By using an IBM file specification as either the input file the output file or both you can initiate a transfer to or from that IBM file See Chapter 2 for the IBM file specification syntax OpenVMS File Transfer Operations 5 11 Table 5 5 shows the level of support DTF provides for the DCL COPY command qualifiers For more detailed information about the COPY command refer to the DCL Dictionary Note You must use the TRANSFER DTF utility to copy from IBM tape files Table 5 5 DTF Level of Support for COPY Command Qualifiers For IBM File Qualifier Specifications Commenis ALLOCATION n supported For IBM files enough tracks or cylinders are allocated to hold n 512 byte blocks If ALIGNMENT TRACKS is specified the allocation is in tracks If ALIGNMENT CYLINDERS is specified the allocation is in cylinders BACKUP not supported IBM files do not have a BACKUP date BEFORE time supported BY_OWNER uic supporte
198. e OpenVMS DTF server Using the DTF for IBM Panel Interface 7 39 that contains the desired translation table If you type NO the file is not translated This is the default action for IBM to IBM transfers RECORD DEFINITION Specifies the path name that is used to access a record definition in the VAX Common Data Dictionary CDD on the OpenVMS DTF server node The maximum length for this value is 255 characters Appendix F provides additional information about field level translation with the CDD 7 40 Using the DTF for IBM Panel Interface 7 14 The Post Processing Options Panel Figure 7 14 Post Processing Options Panel the required fields and press ENTER to continue PROCESS this file on the remote node after the transfer completes FILENAME gt fJ LKG 8308 93R DTF displays the Post Processing Options panel See Figure 7 14 if you type Y in the POSTPROCESS field of the Transfer to Remote panel You can press PF3 to return to the operation panel that invoked this panel without initiating the operation The following paragraph describes the field on this panel PROCESS this file on the remote node after the transfer completes FILENAME Supply a file name on the remote system that you want to submit to the remote node s batch system when the transfer completes Using the DTF for IBM Panel Interface 7 41 7 15 The Batch Options Panel Figure 7 15 Batch Options Panel VM Systems DTF ISPF BAT
199. e integer 2 byte integer word None half word 4 byte integer word 4 byte integer None longword Packed decimal Packed decimal None EBCDIC text DMCS text None Zoned decimal Zoned numeric None Bit string Bit string None Long floating point D_FLOATING If an underflow or overflow condition occurs in the data mapping an error is reported and the file transfer is aborted Short floating point F_FLOATING If an underflow or overflow condition occurs in the data mapping an error is reported and the file transfer is aborted Long floating point G_ FLOATING If precision is lost or if an underflow or overflow condition occurs in the data mapping an error is reported and the file transfer is aborted You can tell DTF to ignore precision loss errors by using the IGNORE qualifier see Chapter 2 Extended floating point H_FLOATING None DTF Data Translation F 7 G Correspondence Between DTF for IBM Keywords and OpenVMS DTF Qualifiers Table G 1 shows the correspondence between OpenVMS DTF IBM file specification qualifiers and the DTF for IBM keywords and fields used in the TSO and CMS command processors and in the ISPF interface You should be familiar with the relationships between these qualifiers when transferring files between IBM systems and Digital networks Table G 1 Correspondence Between OpenVMS DTF Qualifiers DTF for IBM Command Processor Keywords and DTF ISPF Entry Fields Equivalent DTF
200. e server account is HUMOR The VM user ID is OKER and the VM password is LAUGH The file PRANKS EXEC should not contain any records that exceed 80 bytes 12 7 TYPE Command To display a file on an IBM client use the NFT TYPE commana TYPE switch file spec Table 12 6 shows the level of support DTF provides for the NFT TYPE command switch For more detailed information about the TYPE command refer to the PATHWORKS for DOS DECnet User s Guide or PATHWORKS for OS 2 Utilities Guide manuals Note No wildcards are allowed in IBM file names when using the TYPE command 12 10 MS DOS and OS 2 File Transfer Operations Table 12 6 DTF Level of Support for TYPE Command Switch Switch For IBM File Specifications NOLOG supported Examples MVS C NFT FT gt TYPE BOSTON DTFMVS WHITE DTF SPECS This command displays the member SPECS from the PDS called WHITE DTF located on an IBM system The OpenVMS DTF server node is BOSTON and the server account is DTFMVS Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers MVS C NET FT gt TYPE RABBIT DTFMVS JONES DTF ACCOUNTS VOL DTFV1 This command displays the member ACCOUNTS from the data set J ONES DTF located on the IBM system on volume DTFV1 The OpenVMS DTF server node is RABBIT and the server account is DTFMVS Account verif
201. e_1 attribute_n DATA attribute_1 attribute_n PATH NAME value_1 value_n value_1 value_n value_1 value_n value For example the following file definition describes an MVS file BASE HSMRECALL RECORD_DEFINITION RELEASE SINGLE SPANNED SUPERSEDE TRANSLATE VSAM NO CDD TOP TRANSBIN NO NO NO NO YES YES The following file definition describes a VM file BASE BATCHID LASS DADDRESS WNERID ELEASE INGLE PANNED UPERSEDE RANSLATE VSAM HNnNANNDWDOZA CMSBATCH A 197 BIRD NO NO NO NO YES NO The following example of a file definition entry defines the attributes for an indexed file BASE SPANNED TRANSLATE ALTERNATE_INDEX NAME PATH NAME NO YES DEPTA AIX1 DEPTA PATH1 DTF File Specifications 2 37 The following example of a file definition entry specifies attributes for creating a multikey VSAM file containing four keys Each component of the file is located on a different volume BASE RETENTION_PERIOD 1000 TRANSLATE YES USERID PAYROLL INDEX NAME PAYROLL MAIN BASE IDX VOLUME TSOVL1 DATA NAME PAYROLL MAIN BASE DAT VOLUME TSOVL2 ALTERNATE_INDEX NAME PAYROLL MAIN ATX1 INDEX NAME PAYROLL MAIN ATX1 IDX VOLUME TSOVL3 DATA NAME PAYROLL MAIN AIX1 DAT VOLUME TSOVL4 PATH NAME PAYROLL NAME ALTERNATE_INDEX NAME PAYROLL MAIN AIX2 INDEX NAME PAYROLL MAIN AIX2 IDX VOLUME TSOVL5 DATA NAME PAYROLL MAIN AIX2 DAT VOLUME
202. ecified when the file was opened FILE1 is the logical name that was assigned by the OPEN command when the IBM data set was opened Note that because no file name is ever used directly in a CLOSE statement this command is no different than any other OpenVMS CLOSE command 5 8 OpenVMS File Transfer Operations 5 5 CONVERT Command To copy records from indexed files or relative files use the DCL CONVERT command CONVERT input filespec output filespec If you want to change the organization and format of the input file to those of the output file use the CONVERT command and a suitable OpenVMS file definition file By using an IBM file specification as either the input file the output file or both you can initiate a transfer to or from that IBM file See Chapter 2 for the IBM file specification syntax Table 5 4 shows the level of support DTF provides for the DCL CONVERT command qualifiers For more detailed information about the CONVERT command refer to the OpenVMS Convert and Convert Reclaim Utility Manual Table 5 4 DTF Level of Support for CONVERT Command Qualifiers For IBM File Qualifier Specifications Comments INOJAPPEND supported INOJCREATE supported INOJEXCEPTIONS _ supported FILE file spec INOJEXIT supported INO JFAST_LOAD ignored FDL fdl file spec supported AINOJFILL_BUCKETS supported Ignored for IBM indexed files JINOJFIXED_CONTROL supported KEY n supported MERGE supporte
203. ecord I O access to file FAB V_DEL Ignored Delete access to file FAB V_TRN Ignored Truncate access to a file FAB V_UPD Ignored U pdate access to file and explicit file extension FAB L_FOP File processing options FAB V_OFP Disallowed Output file parse FAB V_POS Disallowed Current position FAB V_RCK Disallowed Read check FAB V_RWC Always in effet Rewind on dose applies to magnetic tape only FAB V_RWO Disallowed Rewind on open FABS V_TEF Ignored Truncate at end of file Never done for MVS files To deallocate unused space use the RELEASE attribute or RELEASE qualifier in your file definition Always done for VM files FAB V_WCK Disallowed Write check FAB B_FSZ Ignored Fixed control area size FAB B_RFM Record formats Record format indicates type of record not listed are disallowed B 16 RMS File System and Programming Constraints format FAB C_FIX and FAB C_VAR are fully supported FAB C_VFC is supported only if the FAB V_PRN option in the FAB B_RAT field has been specified continued on next page Table B 10 Cont OPEN FAB Input Fields Field Name Option Restriction Description FAB B_SHR Ignored File sharing For non VSAM files files opened for write are not shareable Table B 11 OPEN XAB Output Fields Field Name Option Restriction Description XABALL Allocation XAB XAB B_ALN Not filled in Alignment boundary type XAB B_AOP Not filled in Allocation options XAB W_DEQ Not filled in Def
204. ed SL Standard labels e Section 3 3 5 describes additional restrictions that may apply for tape resident files e You should fill in this field only if the output file resides on a tape e If the output file resides on disk DTF ignores this field e If you do not specify this field and the output file resides on tape DTF assumes that standard tape labels SL are used FILE NUMBER Specifies a sequential file number on tape between 1 and 9999 e Section 3 3 5 describes additional restrictions that may apply for tape resident files e If the output file resides on disk DTF ignores this field e If you do not specify this field and the output file resides on tape DTF assumes that the FILE NUMBER is 1 DENSITY Specifies the density of the tape volume where the output file will be written Accepted values are 1600 or 6250 7 32 Using the DTF for IBM Panel Interface e Section 3 3 5 describes additional restrictions that may apply for tape resident files e If the output file is not on tape DTF ignores this field e f you do not specify this field and the output file is on tape DTF assumes the highest density allowed for the tape unit DTF options FILE DEFINITION Specifies the name of an entry in the DTF file definition database on the OpenVMS DTF server node Chapter 2 explains file definition records Using the DTF for IBM Panel Interface 7 33 7 11 The VM Output File Options Panel Figure 7 11 VM Output File
205. ed for in nondisplayable fields The DTF command processor prompts you to enter the password for the input file if the following requirements are met e You specified the INUSER keyword 9 24 Using the DTF for IBM Command Processor Note If the INFILE specifies a DECnet file specification you can specify the INUSER value within the access control information portion of the INFILE node specification This is not recommended for security reasons You did not specify the INPASS keyword Note If the INFILE specifies a DECnet file specification you can specify the INPASS value in the access control information portion of the INFILE node specification This is not recommended for security reasons MVS The TSO profile is set to PROMPT The DTF command processor prompts you to enter the password for the output file if the following requirements are met You specified the OUTUSER keyword Note If the OUTFILE specifies a DECnet file specification you can specify the OUTUSER value in the access control information portion of the OUTFILE node specification This is not recommended for security reasons You did not specify the OUTPASS keyword Note If the OUTFILE specifies a DECnet file specification you can specify the OUTPASS value in the access control information portion of the OUTFILE node specification This is not recommended for security reasons
206. ed record format will be created if the output IBM file name is specified with the SPANNED qualifier Section 2 3 3 explains how to use the SPANNED qualifier OpenVMS output files will take the record formats from the IBM input files DTF supports the following record formats on output e Fixed e Variable RSX 11M M PLUS output files will take the record formats from the IBM input files DTF supports the following record formats on output e Fixed e Variable The Digital UNIX ULTRIX OS 2 and MS DOS operating systems can support only stream format records On these systems DTF ignores the format of the input record and creates an output file with stream format records 3 2 3 Supported Record Lengths The output file record length is taken from the input file DTF supports output files with a record length of up to 32760 bytes MVS MVS output files with variable record lengths will have record lengths 4 bytes greater than that of OpenVMS input files This difference is due to the MVS access method BSAM QSAM requirements Conversely output files on DECnet nodes running OpenVMS RSX 11M M PLUS MS DOS OS 2 Digital UNIX or ULTRIX will have record lengths 4 bytes less than that of MVS input files MVS When an output MVS file is created a record length may have defaults set by DTF for MVS This is the case if the input OpenVMS file does not have a maximum record size MRS Quite often this is the default for Op
207. elated lines DTF displays the DTF prompt All previous defined values have been reset to their default values The RECALL subcommand can be used to reset all defined values to the values that were set at execution time Canceling a TRANSFER Subcommand MVS You can cancel a transfer that is in progress at any time The method used to cancel a transfer depends on the terminal you are using On non SNA terminals press Reset then PA1 On SNA terminals press Attn Both terminals will display the following C CANCEL Q QUERY W WAIT ELSE IGNORED Take one of the following actions e Type C and press Enter to cancel the request and free the terminal e Type Q and press Enter to receive status for the request e Type W and press Enter to continue processing If you respond with C the DTF processor halts the transfer at the current position You must then clean up the partial files You cannot issuea RESUME subcommand to restart a canceled request On VM systems you can cancel a transfer that is in progress at any time by typing the command CANCEL and pressing Enter You can request a status report for a transfer in progress by typing the command QUERY and pressing Enter TRANSFER Subcommand Prompts The DTF command processor may prompt you to enter passwords after you issue the TRANSFER subcommand You will enter the information you were prompt
208. eld and the input file resides on tape DTF assumes that standard tape labels are used FILE NUMBER Specifies a sequential file number on tape between 1 and 9999 Tape restrictions may apply If the input file resides on disk DTF ignores this field If you do not specify this field and the input file resides on tape DTF assumes that the FILE NUMBER is 1 DENSITY Specifies the density of the tape volume from which the input file is read Accepted values are 1600 or 6250 Tape restrictions may apply If the input file is not on tape DTF ignores this field If you do not specify this field and the input file is on tape DTF assumes the highest density allowed for the tape unit DTF options FILE DEFINITION Specifies the name of an entry in the DTF file definition database on the OpenVMS DTF server node Chapter 2 explains file definition records Using the DTF for IBM Panel Interface 7 29 7 10 The MVS Output File Options Panel Figure 7 10 MVS Output File Options Panel COMMAND gt Fill in the required fields and press ENTER to continue FILE options MIXED CASE NAME VOLUME SERIAL gt UNIT gt CATALOG gt VSAM gt NULL RECORDS gt PRIMARY ALLOC gt SECONDARY ALLOC gt DTF options FILE DEFINITION gt f TAPE options Y N TAPE LABEL gt FILE NUMBER gt DENSITY gt Y N Y N REJECT IGNORE SPACE NONE LKG 8299 93R DTF displays the MVS Ou
209. eline interface the TRANSLATE option The TRANS and TRANSLATE options control whether translation is done The RECDEF and RECORD DEFINITION options control which translation tables are used in the translation process The three basic translation modes you should be aware of are as follows e EBCDIC to DMCS e Notranslation e Field level translation By default a standard EBCDIC to DMCS translation table is used for data translation If you specify data translation however you can use a user defined translation table Translation using the standard translation table or a user defined translation table can occur on the OpenVMS DTF server node or on the IBM system The location of the translation is defined by the OpenVMS DTF server manager See Section F 3 for for information on translation tables If you specify no translation the data is transferred without being translated You might want to use this mode of translation for transferring binary or image data The RECDEF and RECORD DEFINITION options allow you to specify a CDD record definition to control field level translation If you use these options with the translate option you can use a loadable translation table to define the way character data is translated at the field level Translation using a CDD record F 2 DTF Data Translation definition always occurs on the OpenVMS DTF server node See Section F 4 for information on field level data translation F 3 DMCS EBCDIC Tran
210. em The command to add the file definition file MYINDEX FDL to the server s file definition database as the file definition INDEXED is DIFCFG gt ADD FILE_DEFINITION INDEXED MYINDEX FDL Refer to Appendix C for more information about the ADD FILE_DEFINITION command 2 34 DTF File Specifications 2 4 2 Modifying an Entry in the File Definition Database To modify an entry in the file definition database you must use three SNADTFCFG commands You should perform the following steps 1 Use the SHOW FILE_DEFINITION command with the OUTPUT qualifier to produce a copy of the file definition that you want to change Edit this copy of the file to make your changes 3 Delete the file definition that you want modified using the REMOVE FILE _ DEFINITION command 4 Replace the file definition with your modified file using the ADD FILE _ DEFINITION command Your commands would resemble the following DTFCFG gt SHOW FILE_DEFINITION OUTPUT temp file file def name EDIT temp file DTFCFG gt REMOVE FILE_DEFINITION file def name DTFCFG gt ADD FILE_DEFINITION file def name temp file Appendix C contains more detailed information about the commands used for modifying file definitions 2 4 3 Displaying File Definitions from the File Definition Database To display your file definitions use the SHOW FILE_DEFINITION command This command allows you to display the contents of a particular file definition or to list the names of file defi
211. em administrator for information on the USERID and PASSWORD qualifiers VM TYPE CITIES DTFVM PROFILE EXEC Al1 USER SAM 5 34 OpenVMS File Transfer Operations This command types the contents of the file PROFILE EXEC on the IBM DTF dient The OpenVMS DTF server node is CITIES the server account is DTFVM and the IBM user is SAM Account verification on the VM system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers the USERID and PASSWORD qualifiers The MDADDRESS value and MDRPASSWORD MDWPASSWORD and MDMPASSWORD values are taken from the OpenVMS DTF server s proxy database 5 17 WRITE Command To write a record to a file that was opened with the DCL OPEN command use the DCL WRITE command WRITE logical name expression Table 5 16 shows the level of support DTF provides for the DCL WRITE command qualifiers For more detailed information about the WRITE command refer to the OpenVMS DCL Dictionary Table 5 16 DTF Level of Support for WRITE Command Qualifiers For IBM File Qualifier Specifications ERRORSabd supported SYMBOL supported UPDATE supported Example WRITE FILE1 RECORD This command writes the specified data to the output data set indicated by the logical name FILE1 The data is written as one record in the output data set Note that because no file name is ever used directly in a WRITE statement this co
212. en the file must be closed and opened after records have been inserted in order to gain read access to the file through the use of alternate keys Primary key restriction Indexed files cannot support duplicate primary keys Key data types The keys in an indexed file are not typed as in RMS for example bin1 Keys are merely hexadecimal strings and records are retrieved in this collating sequence Note that ASCII collating sequence differs from EBCDIC collating sequence in that EBCDIC sorts numbers after letters Multikey access IBM multikeyed index files have alternate indexes associated with them These alternate indexes are initialized after the primary index has been loaded and closed Once they are initialized they can be accessed If you attempt to access an indexed file with uninitialized indexes a message is returned to indicate that the file s index tree is in error Contact the IBM system programmer to help identify the uninitialized index You can find the file name in the DTF for IBM console log B 2 1 5 Programming Considerations for VSAM Relative Files The following should be considered when accessing VSAM relative files Record length Records in relative files are fixed length only Nonexistent record processing B 4 RMS File System and Programming Constraints Nonexistent record processing is not supported with relative files If your program attempts to read by relative record number and the record is not the
213. enVMS RSX 11M M PLUS MS DOS OS 2 Digital UNIX and ULTRIX files with stream or variable format records The MVS access methods BSAM QSAM VSAM require a maximum record length so DTF for MVS must provide a default for this when it creates an output file with variable length records DTF for MVS does this by following these steps 3 6 DTF Supported File Types 1 Round the longest record in file LRL attribute up to the next highest multiple of 256 Subtract 1 3 Add the 4 byte requirement of BSAM QSAM if pertinent 3 2 4 Supported Record Attributes MVS output files and VM tape resident output files will be created with the record attribute of the input file DTF supports the following combinations of record attributes for MVS output files e Any combination of the supported record formats with or without blocking including fixed blocked standard FBS and variable blocked spanned VBS See the BLOCK_SIZE and SINGLE qualifiers in Section 2 3 3 for their effect on blocking e Any combination of the supported record format and blocking used with ANSI printer control The input OpenVMS file must have the FORTRAN printer control character Section 3 3 4 explains FORTRAN printer control restrictions DTF supports OpenVMS output files with the following record attributes e Records with the FORTRAN printer control The input MVS file must have the ANSI printer control character Section 3 3 4 explains ANSI printer control
214. ents indicate that the enclosed values are optional You can enter none or one Default values apply for unspecified options Do not type the brackets Press the RETURN key The RETURN key which you must press to execute commands is assumed in command examples and therefore is not shown in command displays Enter VM MVS OpenVMS Press the ENTER key The ENTER key is used to enter IBM commands Instructions or comments that apply to IBM s VM operating system only Also used to indicate instructions or comments that apply only when accessing files on an IBM VM system Instructions or comments that apply to IBM s MVS operating system only Also used to indicate instructions or comments that apply only when accessing files on an IBM MVS system Indicates a Digital to Digital OpenVMS only process xxiii 1 Introducing the Data Transfer Facility DTF Product This chapter answers the following major questions about the Digital SNA Data Transfer Facility DTF product What is the DTF product What are the components of the DTF product What are the capabilities of the DTF product What does the DTF product allow me to do 1 1 What Is the DTF Product The Digital SNA Data Transfer Facility software is a DECnet SNA access routine that connects a OpenVMS DTF server node and its clients on a DECnet network IBM MVS and VM client systems on an SNA network The DTF software s
215. equest involved two IBM files Ifthe original request involved a DECnet file that did not have a password associated with it OPTIONS There may be additional information about the remote node that you can specify To see the panel for entering this information type the letter Y in the OPTIONS field and press the ENTER key USING these options BATCH SUB This field lets you use the Batch Options panel to specify job control information needed to create a batch job for the file transfer operation Optionally this job can be directly submitted after all panels have been completed Typing Y lets you see the Batch Options panel This panel is described in Section 7 15 Using the DTF for IBM Panel Interface 7 17 7 6 The Transfer Execution Panel Figure 7 5 Transfer Execution Panel MVS Systems Transfer in progress SNA terminals Press the ATTN key Non SNA terminals Press RESET then the PA1 key Commands Available J CANCEL current transfer QUERY statistics on current transfer RETURN to WAIT state from Query auto update LKG 8303 93R DTF displays the Transfer Execution panel see Figure 7 5 and Figure 7 6 after you initiate a transfer using one of the operation panels All usage notes for the two panel s follow Figure 7 6 7 18 Using the DTF for IBM Panel Interface Figure 7 6 Transfer Execution Panel VM Systems Transfer in progress Commands Available J CANCEL Terminate current transfer QUERY Displ
216. er is a hexadecimal number Refer to the DECnet ULTRIX Use manual for help in understanding the primary and secondary error messages Refer to the Digital SNA Data Transfer Facility for OpenVMS Problem Solving and Messages manual for the corresponding abbreviated ASCII message text of a particular STV code an explanation of the abbreviated message text and a suggested course of action to correct the problem If you receive any messages that are not listed see the OpenVMS DTF server manager Some user actions for example those that require you to use the SNADTF CFG commands may require the assistance of the OpenVMS DTF server manager ULTRIX and UNIX File Transfer Operations 10 9 11 RSX 11M M PLUS File Transfer Operations This chapter describes how to use the three RSX 11M M PLUS file transfer interfaces DCL NFT and FTS with the OpenVMS DTF server software to transfer files You can use the RSX 11M commands supported by DTF at any RSX 11M M PLUS node in a DECnet network so long as that node can access the OpenVMS DTF server You simply include the OpenVMS DTF server node as part of the file specification No DTF software is required at the client node 11 1 Transferring Files Between RSX 11M M PLUS DTF Clients and IBM DTF Clients You can use the DTF supported RSX 11M M PLUS file transfer commands described in Table 11 1 with an IBM file specification Table 11 1 Supported RSX 11M M PLUS File Transfer Commands DCL Co
217. er is valid only for creating a file e The default specifies that DTF for IBM should supply a default The DTF for IBM default is specified at the IBM site when DTF for IBM is installed The default is recommended for this qualifier e The CYLINDER option allocates the smallest number of full cylinders to hold the data set This option can result in inefficiently used disk space e The TRACK option allocates the smallest number of full tracks to hold the data set This option is generally more appropriate because it results in more efficiently used disk space ALLOCATION number of 512 byte blocks Specifies or overrides the file size for the file being created The number of blocks can be up to x7F FFF FFF Usage Notes e This parameter should be used only for those Digital accessors for example DCL BACKUP that do not send the allocation quantity to the IBM system e Use of this qualifier with other accessors including TRANS DTF could cause the file to be overallocated or underallocated This results in a space error file exceeded allocation e Use of this qualifier allows the installation to back up files on IBM system disks and specify a file size DTF File Specifications 2 15 BATCHID name M Specifies the name of the batch machine to use when submitting a batch job The name must be 1 to 8 characters long Usage Note e If you do not specify a value DTF for IBM supplies the default specified at the I
218. erating systems Although DTF supports stream record formats as input the stream record formats will be converted into variable format records and assigned the carriage control attribute 3 1 3 Supported Record Lengths The input file record length determines the output file record length DTF supports input files with a record length of up to 32760 bytes On OpenVMS systems you should set the RMS NETWORK _BLOCK_ COUNT tothe record length plus 5 divided by 512 rounded to the next highest integer For example to transfer 512 byte records you should set RMS NETWORK_BLOCK_ COUNT to 2 RMS NETWORK_BLOCK_COUNT INTEGER 512 5 512 2 3 1 4 Supported Record Attributes DTF supports the following combinations of record attributes for MVS input files and VM taperesident input files e Any combination of the supported record formats with or without blocking including fixed blocked standard FBS and variable blocked spanned VBS e Any combination of the supported record format and blocking used with ANSI printer control Section 3 3 4 explains ANSI printer control restrictions DTF supports OpenVMS input files with the following record attributes e Records with the FORTRAN printer control Section 3 3 4 explains FORTRAN printer control restrictions e Records with implied carriage return The access methods used by DTF for MVS will not retain the record attribute See Section 3 2 4 for additional information about the record attribute
219. es occur only in the BASE section of the file definition C 3 2 Modifying File Definition ALTERNATE_INDEX Sections To modify file definition ALTERNATE_INDEX sections do the following 1 Usethe SHOW FILE_DEFINITION command with the OUTPUT qualifier This creates a copy of the file definition you want to modify Edit this copy of the file and make your changes 3 Use the REMOVE FILE_DEFINITION command to remove the file definition you want modified 4 Usethe ADD FILE DEFINITION command to replace the file definition with your modified file Maintaining the OpenVMS DTF File Definition Database C 7 Example RUN SYSSSYSTEM SNADTFCFG DTFCFG gt SHOW FILE_DEFINITION OUTPUT NEW_CHANGES DAT PERSONNEL_FILE DTFCFG gt EXIT EDIT NEW_CHANGES DAT EXIT RUN SYSSSYSTEM SNADTFCFG DIFCFG gt REMOVE FILE DEFINITION PERSONNEL_FILE DIFCFG gt ADD FILE_DEFINITION PERSONNEL FILE NEW_CHANGES DAT DTFCFG gt EXIT In this example PERSONNEL_FILE is the file definition you want to modify NEW_CHANGES DAT is the copy of the file definition that you use to make your actual changes C 4 Removing an Entry from the File Definition Database To remove a file definition from the file definition database on a specified server node use the REMOVE FILE_DEFINITION command REMOVE FILE_DEFINITION node access control filedefinition name Command Parameters node access contro The node parameter specifies the OpenVMS DTF ser
220. esponder for the association and converts the FTAM protocol messages into RMS system services The DTF server is invoked by RMS system services The DTF server connects to DTF for IBM DTF for IBM completes the request SNA Network Initiated File Transfer to an OSI Network 5 6 7 DTF for IBM receives a request to copy a file DTF for IBM transfers the request to the DTF server The following is an example of an MVS user request DEF INFILE JONES DTF DEF OUTFILE SMOG OSIGTWY OSISPUTTY SYSTEM OSIUSERPASSWORD DTFTEST DAT DEF SERV DRAKE NETMGR DTFR RECOVERY N TRANS The DTF server connects to the DAP FTAM Gateway The DAP FTAM Gateway makes the association with FTAM or the third party responder OSI FTAM completes the transfer request Note For more information on FTAM operation and general OSI information see the DECnet OSI FTAM and VT Use and Management manual For information on how to access the FTAM features of a non OpenVMS system see the FTAM user documentation for that system FTAM File Support E 5 E 3 FTAM Document Types The FTAM facilities require that you supply one or more file specifications for each operation For FTAM a file specification is a unique string of characters that an FTAM application uses to create or select a file stored on an FTAM system in the same network FTAM document types are e FTAM 1 Unstructured text files e FTAM 2 Sequential files e
221. et Internet Gateway node If a DECnet I nternet Gateway node is specified do not specify the account name OUTSECONDARY A 5 digit number specifying the number of 512 byte blocks that DTF will extend the file if the initial allocation is insufficient to hold the transferred file OUTUNIT unit specification Specifies a generic device name that describes the device type that will hold the IBM output file unit specification A generic device name that describes the device type that will hold the IBM output file Length 1 to 8 characters Usage Note e The OUTUNIT keyword is valid only with an IBM file specification e For VM systems if the output file is on tape you must indicate this by specifying a tape unit in this field You can specify the tape unit as TAPE T3420 or T3480 An IBM site can use additional or different unit names Check with the system programmer of the site where the output file resides to get the unit names in use at the site OUTUSER user id Specifies the user D associated with the file name specified with the OUTFILE keyword user id The user ID associated with the output file Length 1 to 40 characters The syntax of the input file specified with the OUTFILE keyword will determine the format of the user id keyvalue DECnet The logon ID to use when contacting the client node Length 1 to 40 user ID characters IBM The logon ID to use when the DTF Network Manager verifies access to the user ID fil
222. ether DTF should accept the case in which the file name was entered A value of Y will cause DTF to open the file in a case sensitive fashion N or blank will default to uppercase Note This option has no effect unless NODE PARMS LOWERCASECREATE is set to ON See the CASE qualifier in Chapter 2 for information on MIXED CASE INFILE file specification Specifies the input file used in the transfer request The file transfer must include at least one IBM file as either an input file or an output file A file transfer between two DE Cnet files is not allowed If you define an input file as an IBM file specification then change that file specification to a Digital file specification by entering another DEFINE subcommand the DTF command processor will clear the BM related parameters automati cally Using the DTF for IBM Command Processor 9 7 file specification The type of input file will determine the syntax of the file specification keyvalue IBM file Does not indude a node name or the double colon node syntax specification DECnet file ndudes an OpenVMS DTF dient node name and the double colon specification node syntax as shown in the following format node access control information filename Chapter 2 provides detailed information that describes the proper syntax to use for OpenVMS RSX 11M M PLUS MS DOS OS 2 Digital UNIX and ULTRIX file specifications Usage Notes e Client nodes running Digi
223. evice You can enter one of the following four values e REJECT returns an error message e IGNORE ignores all null records The output file may have fewer records and the null records will not be restored if DTF is used to transfer the file from the VM system e SPACE inserts a 1 byte record in place of the zero length record The one byte is set to an EBCDIC space character e NONE accepts the record as is in an MVS environment In a VM environment an error will be given if a null record is encountered See the NULL qualifier in Chapter 2 for information on NULL PRIMARY ALLOCATION A 5 digit number specifying the number of 512 byte blocks that DTF will initially allocate when creating a file on the IBM system See the ALLOCATION qualifier in Chapter 2 for information on ALLOCATION Using the DTF for IBM Panel Interface 7 31 SECONDARY ALLOCATION A 5 digit number specifying the number of 512 byte blocks that DTF will use to extend the file if the initial allocation is insufficient to hold the transferred file See the SECONDARY_ ALLOCATION qualifier in Chapter 2 for information on SECONDARY_ALLOCATION VSAM If the output file is VSAM format you must indicate this by typing a Y in this field TAPE options TAPE LABEL Specifies the format of the tape labels to be used for the output tape You can specify one of the following tape labels AL ANSI V1 labels or ISO ANSI FIPS V3 labels BLP Bypass label processing NL Non label
224. face refer to the OpenVMS Systems Routines Record Management Services manual The following sections are an aid for those who intend to write their own programs Most of the differences between OpenVMS and IBM are in the area of indexed file support You should review these differences before performing record level access to IBM VSAM file types There is also a section listing differences for record level access to IBM non VSAM files B 2 1 Record Level Access to VSAM Files B 2 1 1 In general all accesses Such as FIND GET PUT or UPDATE are supported for VSAM sequential relative and indexed file types However there are differences that should be considered Unsupported OpenVMS RMS Service Calls The following OpenVMS RMS service calls usually supported between two OpenVMS nodes are not supported between an OpenVMS node and an IBM node e ENTER e EXTEND e FLUSH e NXTVOL B 2 RMS File System and Programming Constraints READ e REMOVE e RENAME e SPACE e TRUNCATE WAIT e WRITE B 2 1 2 Unsupported RMS Extended Attribute Blocks The following RMS extended attribute blocks usually supported between two OpenVMS nodes are not supported between an OpenVMS node and an IBM node e Protection XAB zeroes are returned as values for this XAB e Revision date and time XAB e Terminal XAB B 2 1 3 Record Locking As documented in the sections of this appendix that describe the supported RMS ser
225. fashion N or blank will default to uppercase Note This option has no effect unless NODEPARMS LOWERCASECREATE is set toON See the CASE qualifier in Chapter 2 for information on MIXED CASE OUTFILE file specification Specifies the output file that will be either created or overlaid as a result of the transfer request The file transfer must include at least one IBM file specification as either an input file or an output file Two DECnet file specifications are not allowed 9 12 Using the DTF for IBM Command Processor file specification The name of the output file that will be either created or overlaid during the transfer The type of output file will determine the syntax of the file specification keyvalue IBM file Does not include a node name or the double colon node syntax specification DECnet file ndudes an OpenVMS DTF client node name and the double colon specification node syntax as shown in the following format node access control information filavame Chapter 2 provides detailed information that describes the proper syntax to use for OpenVMS RSX 11M M PLUS MS DOS OS 2 Digital UNIX and ULTRIX file specifications Usage Notes e Ifthe transfer request does not include at least one IBM file specification the transfer will fail e If the filespecification keyvalue specifies a DECnet file the only applicable output file related keywords are DISP OUTUSER and OUTPASS e The DE Cnet f
226. fer from the last checkpoint after a network or system failure The TRANSFER DTF utility does not provide checkpoint and recovery for VSAM files Refer to Chapter 6 for more information about the TRANSFER DTF utility 5 1 Transferring Files Between OpenVMS DTF Clients and IBM DTF Clients You can use the following DTF supported DCL commands with an IBM file specification e APPEND e BACKUP e CLOSE e CONVERT e COPY OpenVMS File Transfer Operations 5 1 e CREATE e DELETE e DIFFERENCES e DIRECTORY e EXCHANGE NETWORK e OPEN e READ e SEARCH e SUBMIT REMOTE e TYPE e WRITE Note DTF does not support wildcards for output file names 5 2 APPEND Command To add the contents of one or more specified input files to the end of a specified output file use the DCL APPEND command APPEND input file spec output file spec Table 5 1 shows the level of support DTF provides for the DCL APPEND command qualifiers For more detailed information about the APPEND command refer to the DCL Dictionary Notes When DTF for MVS creates an MVS file it calculates a maximum record length that is greater than the maximum record length of the input file record length is the next greater multiple of 256 minus 1 Any attempt to append a file with records larger than the calculated maximum record length of the existing file will result in an error DTF does not support append operations to files with RECFM FBS
227. finition file is stored in the file definition database on the OpenVMS DTF server DTF File Specifications 2 33 Note You must use this method to specify certain VSAM file parameters that cannot be specified using the IBM file specification qualifiers To set up a DTF file definition file use the editor of your choice to create a sequential file that contains the appropriate specifications The values specified in this file allow you to override the default values that are assigned by the IBM system programmer at installation time or used by VSAM when creating VSAM files Notes Attributes for non VSAM files can be specified directly with the ADD FILE_DEFINITION command using the qualifiers described in Section 2 3 3 See Appendix C for more information about this technique The OpenVMS DTF server manager can associate a default file definition for each server account Check with your OpenVMS DTF server manager 2 4 1 Adding an Entry to the File Definition Database To add an entry to the file definition database you must use the SNADTFCFG ADD FILE_DEFINITION command OpenVMS client users need the OpenVMS DTF utilities software installed on their node and may have to contact the OpenVMS DTF server manager to obtain the necessary privileges to perform this operation All other client users must contact the OpenVMS DTF server manager to have the manager place the file definition in the file definition database for th
228. for files accessed on a remote system Data security is further enhanced through proxy methods What proxy is and the benefits of proxy are covered in this chapter 4 1 Local Data Security The DTF software uses the rules established by the local security system to allow access to files On MVS cients the DTF software internally verifies the right to access a file This is done using calls to the security system by a security exit that can be customized during installation On VM clients the DTF software follows standard CMS minidisk linking rules to allow access to files If the minidisk is not linked and accessed you must supply a minidisk address link password and an optional owner ID to link and access the minidisk On OpenVMS and RSX 11M M PLUS clients your file access is determined by the access privileges associated with the account you use to log in On Digital UNIX dients ULTRIX clients MS DOS clients and OS 2 clients your file access is determined in a manner consistent with DE Cnet file access Data Security 4 1 4 2 Remote Data Security Without Proxy The DTF software sends the user ID and password you type in to the remote system to allow the remote system to check if access is allowed The rules for the user ID and password depend on the remote operating system Table 4 1 shows the user ID and password syntax rules for each supported operating system Table 4 1 User ID and Password Syntax Rules Opera
229. formation about the specified DTF queues The following information is displayed e Queue name e Queue status FULL Displays complete information about the specified DTF queues The following information is displayed e Queue name e Queue settings OpenVMS TRANSFER DTF File Transfer Operations 6 19 Example TRANSFER DTF TRANS DTF gt SHOW QUEUE FULL SNADTF queue SNADTFSQUEUE on DRAGON BASE_PRIORITY 4 OWNER SYSTEM PROTECTION S E 0 D G R W W Default INTERVAL 0 00 01 00 00 Minimum INTERVAL Unspecified Default RETRIES 48 Maximum RETRIES Unspecified Default TIME 1 00 00 00 00 Maximum TIME Unspecified This example shows the output from a SHOW QUEUE FULL command 6 7 Displaying the OpenVMS DTF Software Version Number To display the current version of the OpenVMS DTF software use the TRANSFER DTF SHOW VERSION command SHOW VERSION This version number should be listed on all submitted Software Performance Reports SPRs Example TRANSFER DTF TRANS DTF gt SHOW VERSION Digital SNA Data Transfer Facility for OpenVMS Vn n This SHOW VERSION command displays the current version of the OpenVMS DTF software 6 8 Canceling File Transfer Jobs To remove a job from a queue before it executes or to abort a currently running job use the TRANSFER DTF CANCEL J OB command CANCEL J OB job namg qualifier A privileged user can cancel any job that standard OpenVMS protection mechanisms allow For example a
230. g this table for the FTS DAP codes parse the value as nn nnnn The Digital SNA Data Transfer Facility for OpenVMS Problem Solving and Messages manual contains explanations and user actions for these error messages Note The DECnet RSX interfaces do not return the DAP secondary status codes These codes are an important aid in determining the solution to any DTF problems You can see the error messages generated by these codes by accessing the NETSERVER LOG files in the SNADTFS MANAGER account on the OpenVMS DTF server node Because these files are not available for world access you will have to ask the OpenVMS DTF server manager for assistance Table 11 9 DAP Error Codes Status Code ASCII Text 4 471 DTFCDDREC 4 472 DTFCFGFIL 4 473 DTFCVT 4 474 DTFDEFFIL 4 475 DTFFALSHT continued on next page 11 18 RSX 11M M PLUS File Transfer Operations Table 11 9 Cont DAP Error Codes Status Code ASCII Text 4 476 DTFNOFIL 4 477 DTFNOREC 4 501 DTFOPRABO 4 502 DTFQUASYN 4 503 DTFQUAVAL 4 506 DTFSESEST 4 507 DTFSESTER 4 510 DTFTRATBL 4 511 DTFUNSTYP 4 512 DTFVERMIS 4 513 DTFACC 4 514 DTFCRE RSX 11M M PLUS File Transfer Operations 11 19 12 MS DOS and OS 2 File Transfer Operations This chapter describes how to use the PATHWORKS for DOS and PATHWORKS for OS 2 NFT file transfer commands with DTF software to transfer files between MS DOS and OS 2 DTF clients and IBM DTF cients You can use the NFT command
231. gnored with nontape devices 2 18 DTF File Specifications DIRECTORY_BLOCKS n MVS Specifies a number from 1 to 999999 to define how many 256 byte directory blocks are allocated to a partitioned data set PDS directory for creating the first member of a PDS Usage Notes e This qualifier is valid only for creating a PDS e If you do not specify a value DTF for IBM supplies the default specified at the IBM site e This qualifier is ignored if a new member is added to an existing PDS e Ifthe IBM data set name does not specify a PDS member name this qualifier is ignored and a non PDS data set is created e You should overallocate the value for this qualifier because the value cannot be expanded e The value you specify can contain 20 member names in each directory block However if other utilities such as the ISPF editor write member names to the data set you should plan on only five member names for each directory block FILE_DEFINITION file definition Specifies the use of an entry in the file definition database This entry contains a list of default attributes for file creation and file access Usage Notes e The default is not to use a file definition e Any additional qualifiers included with the FILE_DEFINITION qualifier override the defaults set up in the file definition database e For more information about setting up file definitions and the file definition database see Section 2 4 NO J
232. gt FINGER SNADTF GIBSON TIRES USER GIBSON PASS SMALL AS AP This command appends the files GIBSON FILTERS and GIBSON TIRES on the MVS system to the local file INVENTORY DAT The OpenVMS DTF server node is FINGER and the server account is SNADTF The MVS files are accessed using the MVS user ID GIBSON and the password SMALL Note the use of the AS ASCII switch and the AP append switch RSX 11M M PLUS File Transfer Operations 11 3 VM SAPPEND ASHFLD DTFVM PROFILE EXEC Al1 USER GIBSON LOGIN CMD This command appends the file PROFILE EXEC A1 to the RSX file LOGIN CMD located in default local directory By default file access on the VM system is done using mode 1 The server account is DTFVM the OpenVMS DTF server node is ASHFLD and the VM user ID is GIBSON The VM password is retrieved from the server s proxy database VM FT gt EAST DTFVM WEEK DATA USER JONES MONDAY DATA AP This command appends the file MONDAY DATA to the VM file WEEK DATA File access on the VM system is done using mode 1 The server account is DTFVM the OpenVMS DTF server node is EAST and the VM user ID is J ONES The VM password is retrieved from the server s proxy database 11 3 COPY Command To transfer sequential files between a DECnet RSX DTF client and an IBM DTF client use the DCL COPY command COPY input file spec output file spec the standard NFT command output file spec switches i nput
233. hapter 12 for information on using the MS DOS and OS 2 client interfaces 1 3 1 2 IBM User Interfaces DTF provides three user interfaces for MVS clients and three user interfaces for VM clients that you can use to copy files The interfaces for MVS clients are as follows e Panel interfaces for TSO ISPF interactive users e Interactive and batch TSO commands e TSO command processor The interfaces for VM clients are as follows e Panel interfaces for CMS ISPF and non I SPF users e Interactive and batch CMS commands e CMS command processor The DTF panel interface provides an easy to use method of transferring files The panels prompt you for the information required to copy a file The panel interface is recommended if you are a new DTF user The panel interface allows you to submit a copy request to the batch subsystem Refer to Chapter 7 for more information about the DTF panel interface The set of DTF file transfer commands is an alternative to the ISPF interface These are singleline commands that you enter from either the TSO or CMS READY prompt on either MVS or VM Refer to Chapter 8 for more information about the DTF file transfer command interface The final way to copy files is by using the DTF command processor The command processor offers the most flexibility and functionality for copying files across a network You should use the command processor if you are an experienced DTF user and you need its robust interface Refer to C
234. hapter 9 for more information about the DTF command processor interface Introducing the Data Transfer Facility DTF Product 1 5 1 3 2 Data Translation All Clients The DTF product allows you to translate text between DMCS Digital Multi national Character Set a superset of ASCII American Standard Code for Information Interchange and EBCDIC Extended Binary Coded Decimal Interchange Code on a record by record basis Data translation is performed by default in all cases except when a file is transferred between two MVS clients two VM clients or an MVS client and a VM client You can change the data translation default in the following ways e Turn data translation on or off to override the default e Specify a different translation table to control data translation This table resides on the OpenVMS server node e Specify a VAX CDD record definition to provide field level data translation For more information on selecting data translation see the TRANSLATE qualifier in Section 2 3 3 The OpenVMS DTF server manager can control whether data translation occurs on the OpenVMS DTF server or on the DTF for IBM client For more information on controlling where translation is performed see the Digital SNA Data Transfer Facility for OpenVMS Management manual For more information about field level data translation refer to the Common Data Dictionary Data Definition Language Reference manual and Appendix F of this manual 1 3
235. he level of support DTF provides for the DECnet ULTRIX dcat command options For more detailed information about the dcat command refer to the DECna ULTRIX Use manual or the DECne OSI for Digital UNIX Introductory User s Guide ULTRIX and UNIX File Transfer Operations 10 1 Table 10 1 DTF Level of Support for dcat Command Options For IBM File Option Specifications Commenis V supported You cannot specify wildcard characters in an IBM file specification Examples MVS dcat veena snadtf mike dtf test This command displays the member test from the PDS called mike dtf located on an IBM DTF client The DTF server node is veena and the server account is snadtf Note that no server account password is given The dcat command will prompt you for a password Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers MVS dcat veena dtfmvs ward dtf vol tsov2 user ward pass hunter gt output txt This command displays the data set ward dtf located on the IBM DTF dient on volume tsov2 The OpenVMS DTF server node is veena and the server account is dtfmvs The display output is directed to the file output txt The MVS user ID is ward and the password is hunter MVS dcat veena dtfmvs mike basin txt userid mike password secret This command displays the data set mike basin txt lo
236. her the transfer is recoverable or nonrecoverable Chapter 1 provides additional information about recoverable copy You can select one of the following options Y The transfer operation will execute in recoverable mode N The transfer operation will execute in nonrecoverable mode Notes e DTF uses a default that is set up when DTF is installed at your site e If you specify the RECOVERY as Y but the client node does not have the DTF utilities software installed OpenVMS client node without the DTF utilities software or DECnet client nodes running MS DOS RSX 11M M PLUS OS 2 Digital UNIX or ULTRIX the transfer request will be rejected SERVER This name specifies the OpenVMS DTF server to which DTF sends the transfer request SERVER is the name of a DECnet node Using the DTF for IBM File Transfer Commands 8 5 TRANSLATE If you specify Y for this option DTF performs the default standard translation of EBCDIC to DMCS If you type N DTF does not translate the file from EBCDIC to DMCS format UNIT This parameter describes a generic device that holds the IBM input file The name can be up to eight characters long MVS If the input file you are trying to copy is not cataloged or you want to avoid a catalog search to find the file you should specify both the volume name and the unit name VM If the input file is on tape you must indicate this by specifying a tape unit in this field You can specify
237. ication on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers VM C NFT FT gt TYPE TROLLS DTFMUSIC FIFTIES TEXT USER MUSIC PASS CRUISE This command displays the file FIFTIES TEXT located on the VM system The OpenVMS DTF server node is TROLLS and the server account is DTFMUSIC The VM user ID is MUSIC and the password is CRUISE 12 8 Error Reporting This section lists the top level status messages you may receive when using DTF You will usually see a primary and secondary message followed by secondary status value STV The top level messages are usually self explanatory The STV codes are reported as hexadecimal numbers Messages appear in a format similar to the following MS DOS and OS 2 File Transfer Operations 12 11 primary text secondary text STV hex number where primary text is the primary error message secondary text is a secondary message offering additional information and hex number is a hexadecimal number The secondary message can contain a DAP error code of the form nn nnn The primary and secondary messages are standard NFT error messages Table 12 7 provides the corresponding abbreviated ASCII message text for any DAP error codes received For the STV codes refer to the Digital SNA Data Transfer Facility for OpenVMS Problem Solving and Messages manual for the corresponding abbreviated ASCII message text of a parti
238. ice of DCL CREATE or DISP DISP DISP on the Send and COPY command Receive panels DIRECTORY_BLOCKS MVS None None None FILE_DEFINITION INFDEF None FILE DEFINITION on OUTF DEF the Input and Output File Options panels IKEY None None None HSMRECALL MVS None None None LABEL INLABEL LABEL TAPE LABEL on the OUTLABEL Input and Output File Options panels MRS MVS None None None MDADDRESS VM INMDADDR VSAMDISK DEVICE ADDR in the OUTMDADDR MDADDR local file section of the Send and Receive panels MDxPASSWORD VM INMDPASS MDPASS PASSWORD in the local OUTMDPASS file section of the Send and Receive panels 1Specify using the IBM file specification qualifiers described in Chapter 2 in the file name continued on next page G 2 Correspondence Between DTF for IBM Keywords and OpenVMS DTF Qualifiers Table G 1 Cont Correspondence Between OpenVMS DTF Qualifiers DTF for IBM Command Processor Keywords and DTF ISPF Entry Fields Equivalent DTF for IBM OpenVMS DTF Command DTFSEND Equivalent DTF ISPF IBM File Specification Processor DTFRECV Entry Field Qualifier Keyword DTFRESUM and DTF ISPF Panels Not applicable NETMGR NETMGR SUBSYSTEM on the Operations Selection panel NULL NULL NULL NULL RECORDS on Output File Options panels OWNERID VM INMDOWNER MDOWNER OWNER in the local file OUTMDOWNER section of the Send and Receive panels PASSWORD INPASS PASS PASSWORD on the
239. ields Option or Field Name XAB Type Restriction Description RAB L_ROP Record processing options RAB V_RLK Disallowed Read of locked record allowed RAB V_TPT Disallowed Truncate on put RAB V_UIF Disallowed Update if RAB V_WBH Disallowed Write behind B 3 14 RELEASE Table B 13 describes the special fields of the RELEASE RMS service call Table B 13 RELEASE RAB Input Fields Field Name Restriction Description RAB W_RFA Ignored Record s file address ignored for non VSAM files only Note When using RELEASE only the current record or control interval is unlocked because only one record or control interval can be locked at a time B 3 15 REWIND There are no restrictions associated with the REWIND input and output fields RMS File System and Programming Constraints B 19 B 3 16 SEARCH There are no restrictions associated with the SEARCH input and output fields B 3 17 UPDATE Table B 14 describes the special fields of the UPDATE RMS service call Table B 14 UPDATE RAB Input and Output Fields Field Name Option Restriction Description RAB L_ROP Record processing options RAB V_WBH Disallowed Write behind B 20 RMS File System and Programming Constraints C Maintaining the OpenVMS DTF File Definition Database A file definition database resides on each OpenVMS DTF server node and contains the file definitions that are used to access files on the IBM system Use the SNA DT
240. iers and Their Usage for Remote VM Files Tape Resident Qualifier CMS Files Files VSAM Files MDADDRESS 23 49 supported ignored supported MDMPASSWORD 2 3 4 supported ignored supported MDRPASSWORD 345 supported ignored supported MDWPASSWORD 23 45 supported ignored supported MRS ignored ignored ignored NULL 3 supported ignored ignored OWNERID 2 34 supported ignored supported PASSWORD 2 3 4 5 supported supported supported RECORD_DEFINITION 23 supported supported supported RELEASE ignored ignored ignored RETENTION PERIOD ignored ignored supported IRFA 123 ignored ignored supported SECONDARY_ALLOCATION supported ignored supported SECURITY_DATA 23 45 supported supported supported SEQUENCE_NUMBER 2 gt ignored supported ignored SINGLE ignored supported ignored SMSDCLASS ignored ignored ignored SMSMCLASS ignored ignored ignored SMSSCLASS ignored ignored ignored SPANNED ignored supported supported SUPERSEDE supported ignored rejected TRANSLATE 23 supported supported supported UNIT 2 3 amp ignored supported ignored 1This qualifier is used when reading IBM input files for copy search compare and display operations 2This qualifier is used when writing over existing IBM output files 3This qualifier is used when creating a new IBM file 4This qualifier is used when deleting an IBM file 5This qualifier is used when listing an IBM directory 6This qualifier is used only for IBM tape resident files
241. iii 12 1 12 2 12 3 12 4 12 5 12 6 12 7 12 8 Transferring Files Between MS DOS or OS 2 DTF Clients and BMAD TFG WGntS Hac keer aa a a a a a de a a APPEND Command sasaaina aeaaea COPY Command ass aiibi aag eai ari a a a a ara a dul Sha A DELETE Command 0 000 ccc a a a eee eee DIRECTORY Command 0 0 00 aa eee eee SUBMIT Command 0 000 cece eee TYPE GOmMMan eissa aare teu ads wets Seka aa ye ieee ane Ara Oh Erro REpOntinG sos eis aie oe ee hoe E eee Oe Re A 11 1 11 2 11 4 11 7 11 9 11 11 11 14 11 16 11 17 11 18 A Using OpenVMS DATATRIEVE with DTF A 1 A 1 1 A 1 2 A 2 A 3 A 4 Defining a DATATRIEVE Domain to Access an IBM File Before Defining Your DATATRIEVE Domain Using the DATATRIEVE DEFINE Command Preparing a DATATRIEVE Domain for Access to an IBM File Manipulating Records from a Domain on an IBM System Ending a DATATRIEVE Session That Is Accessing an IBM Fil keon Pataca Mate hawaii ak Ee wn eae a Soe ea eS B RMS File System and Programming Constraints B 1 B 2 B 2 1 B 2 1 1 B 2 1 2 B 2 1 3 B 2 1 4 B 2 1 5 B 2 1 6 B 2 2 B 3 B 3 1 B 3 2 B 3 3 B 3 4 B 3 5 B 3 6 B 3 7 B 3 8 B 3 9 B 3 10 B 3 11 B 3 12 B 3 13 B 3 14 B 3 15 B 3 16 B 3 17 RMS File System Constraints 0 000 eee eee RMS Programming Restrictions 00 cee eee Record Level Access to VSAM Files 004
242. ile specification can contain access control information within the node portion of the file name However this is not recommended because the password will remain visible on the screen The preferred method of entering access control information is through the OUTUSER and OUTPASS keywords e If you specify an IBM file specification for the OUTFILE and then change the OUTFILE toa DECnet file specification by entering another DEFINE subcommand the DTF processor will clear the IBM related parameters automatically NEW DISP OLD REP A required keyword that specifies whether the output file is a new or existing file NEW NEW creates a new output file If a file with the same name already exists DTF does not copy the file This is the default Using the DTF for IBM Command Processor 9 13 OLD OLD creates a new output file that overlays an existing file of the same name If the file does not exist DTF issues an error message REP REP creates a new output file even if a file with the same name already exists OUTDEN et Specifies the density of the tape volume to which the DTF processor will write the output file 1600 1600 bits per inch bpi 6250 6250 bits per inch bpi Usage Notes e Tape restrictions may apply Section 9 4 1 describes these restrictions e The DTF command processor will ignore the OUTDEN keyword if you direct the processor to write the OUTFILE toa disk or if the output file is not an IB
243. ile that overlays an existing file of the same name If the file does not exist DTF issues an error message REP creates a new output file even if a file with the same name already exists OWNER vM This field specifies the owner ID of the minidisk that will contain the output file This field is optional if you currently have the minidisk linked and accessed DEVICE ADDR M This field specifies the device address of the minidisk that will contain the output file This field is optional if you currently have the minidisk linked and accessed 7 12 Using the DTF for IBM Panel Interface PASSWORD vm This field specifies the multiwrite password of the minidisk that will contain the output file This field is optional if you currently have the minidisk linked and accessed For more information on minidisk passwords see the MDxPASSWORD qualifier description in Section 2 3 3 OPTIONS There may be additional information about the remote output file that you can specify To see the panel for entering this information type the letter Y in the OPTIONS field and press the ENTER key These panels are described in Section 7 10 and Section 7 11 USING these options RECOVERABLE Controls whether the transfer runs in recoverable mode or nonrecoverable mode Chapter 1 provides additional information about recoverable copy You may select one of the following options Y The transfer executes in recoverable
244. iles toa VM system MDPASS The output file s multiwrite minidisk password This option is valid only when transferring files toa VM system For more information about minidisk passwords see the MDxPASSWORD qualifier in Section 2 3 3 NETMGR Specifies the name of the DTF Network Manager component If you specify a name the value overrides the name in the DTFUSER parameter file On VM systems the name is the 1 to 8 character virtual machine name On MVS systems the name is the 1 to 4 character subsystem name as it appears in the subsystem name table NULL The action that DTF should take when it encounters a null record during a transfer to the local system 8 4 Using the DTF for IBM File Transfer Commands SPACE DTF inserts a record containing a single space x 40 in place of the null record REJ ECT DTF gives an error message if transferring an MVS record IGNORE DTF ignores all null records Note that the output file may have fewer records and that the null records lost will not be restored if DTF is used to transfer the file from the VM system NONE DTF accepts the records as is if transferring to an MVS system Transfers to a VM system will result in an error message NUMBER The file number for input files residing on tape The number must be in the range of 1 to 9999 PASS This is the user s password on the remote system If you do not specify a password DTF will prompt you for one RECOVERY Controls whet
245. ill result in an error message NUMBER The file number for output files being written to tape The number must be in the range of 1 to 9999 PASS This is the user s password on the remote system If you do not specify a password DTF will prompt you for one RECOVERY Controls whether the transfer is recoverable or nonrecoverable Chapter 1 provides additional information about recoverable copy You can select one of the following options Y The transfer operation will execute in recoverable mode N The transfer operation will execute in nonrecoverable mode Notes e DTF uses a default that is set up when DTF is installed at your site e If you specify the RECOVERY as Y but the client node does not have the DTF utilities software installed OpenVMS client node without the DTF utilities software or DECnet client nodes running MS DOS RSX 11M M PLUS OS 2 Digital UNIX or ULTRIX the transfer request will be rejected SERVER This name specifies the server to which DTF sends the transfer request SERVER is the name of a DECnet node 8 10 Using the DTF for IBM File Transfer Commands TRANSLATE If you specify Y for this option DTF performs the default standard translation of EBCDIC to DMCS If you type N DTF does not translate the file from EBCDIC to DMCS format UNIT This parameter describes a generic device that holds the IBM output file The name can be up to eight characters long VM If the output file i
246. imary key the transfer will terminate with errors This restriction applies to both OpenVMS and BM initiated transfers e f you specify an OpenVMS file specification as the keyvalue do not include a node name user ID or password as part of that file specification e TRANSLATE NO is the default value if you are initiating a transfer that has IBM file specifications for both the input and output file specifications e TRANSLATE YES is the default value if the transfer has a DECnet file specification as either the input or output file specification This concludes the discussion of the keywords you can use with the DEFINE subcommand Using the DTF for IBM Command Processor 9 21 DEFINE Example The following example shows you how to define the values necessary to set up a file transfer DEFINE INFILE CLUSTR LOGIN COM INUSER VMSUSER INPASS VMSPASS 1 DTF0047I DTF DEFINE OUTFILE IBMUSER LOGIN COM 2 DTF0047I DTF DEFINE SERVER NODE1 NETMGR DTF1 3 DTF0047I DTF 1 This DEFINE subcommand sets up an input file specification The input file definition is an OpenVMS file specification because it contains a node name followed by a double colon 2 This DEFINE subcommand sets up an output file specification The output file definition is an IBM file specification because it does not contain a node name or a double colon 3 This DEFINE subcommand sets up the transfer parameters 9 3 3 END Subcommand The
247. implied Table B 4 CREATE XAB Output Fields Field Name Option Restriction Description XABALL Allocation XAB XAB B_ALN Not filled in Alignment boundary type XAB B_AOP Not filled in Allocation options XAB W_DEQ Not filled in Default extension quality XAB L_LOC Not filled in Location XAB W_RFI Not filled in Related file identifier XAB W_VOL Not filled in Related volume number XABDAT Disallowed Date and time XAB XABKEY Key definition XAB XAB B_DBS Not filled in Data bucket size XAB W_DFL Not returned Data bucket fill size XAB B_DTP Not filled in Data type of the key continued on next page RMS File System and Programming Constraints B 9 Table B 4 Cont CREATE XAB Output Fields Field Name Option Restriction Description XAB L_DVB Not filled in First data bucket virtual block number XAB B_IBS Not filled in Index bucket size XABSW_IFL Not filled in Index bucket file size XAB L_KNM Not filled in Key name buffer address XAB B_LVL Not filled in Level of root bucket XAB W_MRL Not filled in Minimum record length XAB B_NSG Always 1 Number of key segments XAB B_NUL Not supported Null key value XAB W_POSn Only POSO Key position returned XAB B_ Always 3 Prolog level PROLOG XAB L_RVB Not returned Root bucket virtual block number XAB B_SIZn Only SIZO Key size returned XABPRO Disallowed Protection XAB XABRDT Disallowed Revision date and time XAB XABSUM Summary XAB XAB W_PVN Always 3 Prolog version number B 10 RMS
248. ined as the DTF Network Manager subsystem that should receive the transfer request Nonrecoverable has been defined as the mode of execution Executes the request J ob message output for transfer Note The DEFINE subcommand defines input and output file specifications and the environment associated with a file transfer See Chapter 9 for more information on the DEFINE subcommand Note The COPY and APPEND commands are the only commands supported in a third party transfer request FTAM File Support E 11 DTF Data Translation This appendix discusses both Digital and IBM data types and the way that data is translated between Digital and IBM data types It also briefly describes the way to create a record definition referred to as a data definition in CDD terminology For more information on Digital data types refer to the OpenVMS VAX Architecture Handbook For more detailed information about Digital data types and the creation of a data definition refer to the Common Data Dictionary Data Definition Language Reference For more information about IBM data types refer to the IBM Principles of Operations manual F 1 Controlling Data Translation on DECnet Initiated File Transfers Translation of data types is controlled by the TRANSLATE and RECORD _ DEFINITION qualifiers The three basic translation modes you should be aware of are as follows e DMCS to EBCDIC e Notranslation e Field level translation
249. ing MVS command at an MVS console M unit VOL SL volse USE PUBLIC Only standard label tapes can be mounted 9 4 2 Using Tapes VM Systems When you copy a file to or from a tape DTF prompts the user ID specified in the TAPEOPER parameter to attach a tape drive to that ID The transfer continues once the tape drive is attached 9 4 3 Overriding the Server and Server Account If the INRMT the OUTRMT or both keywords are used to override the server node or server account you should be aware of the following The DTF Network Manager subsystem that accepts the transfer request may not be the one that executes the file transfer If this happens there will be no logging information about the file transfer in the DTF Network Manager subsystem that did not execute the transfer The OpenVMS DTF proxy database is stored on a server node If the server node is overridden to a different node the proxy database on the different node will be used The OpenVMS DTF file definition database is stored on a server node If the server node is overridden the file definition database on the different node will be used 9 5 Executing the DTF Command Processor in Batch Mode VM Systems There are two ways to initiate batch transfers in CMS Execute an exec file that stacks DTF subcommands before invoking DTF For example Queue def netmgr dtfgcs server dtfsrv Queue def infile profile exec a Queue def outfile vmssys a b
250. input and output DTF assumes that files on these tapes are in ASCII format therefore do not specify field level data translation Data set names for IBM tape resident files are effectively limited to 17 characters DTF interfaces allow longer data set names however MVS and VM limit data set names on tapes to 17 characters If you specify more than 17 characters when accessing a tape resident file the name is truncated on the LEFT resulting in the 17 RIGHTMOST characters being used as the file name DTF Supported File Types 3 9 Be sure to specify the UNIT qualifier when accessing tapes If you fail to specify the UNIT qualifier the default unit is used This is usually set to point to a disk device This can cause problems when you work with unmounted tapes DTF for MVS will issue a mount requested message on the MVS console indicating a request to mount a disk not a tape DTF for VM will send a similar message to the virtual machine defined during DTF for VM installation as indicated by the TAPEOPER keyword 3 3 6 Transferring Files with Horizontal Tab Characters If an OpenVMS file with DMCS horizontal tab characters is transferred to an IBM file the tab characters are translated to EBCDIC tab characters Most IBM utilities do not recognize the horizontal tab character therefore the file will appear to contain no horizontal tabs When the file is transferred back to the OpenVMS system the EBCDIC tab characters will be translated t
251. ion ULTRIX and UNIX File Transfer Operations 10 5 10 5 dis Command To display a file list on an IBM DTF client use the DECnet ULTRIX or DECnet OSI for Digital UNIX dls command dls opti on file spec Table 10 3 shows the level of support DTF provides for the DECnet ULTRIX or DECnet OSI for Digital UNI XdIs command options For more detailed information about the dis command refer to the DECna ULTRIX Use manual or the DECne OSI for Digital UNIX Introductory User s Guide Note You can use the dis command to obtain directory listings of IBM tape resident files Table 10 3 DTF Level of Support for dls Command Options For IBM File Option Specifications Commenis 1 supported a supported C supported l supported Examples MVS dls 1 veena dtfmvs gary dtf file This command displays the names of all the members of the PDS called gary dtf file located on an IBM DTF client The OpenVMS DTF server node is veena and the server account is dtfmvs The display is in a single column format 1 Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers MVS dls 1 veena snadtf betty dtf vol tsov2 10 6 ULTRIX and UNIX File Transfer Operations This command displays all data sets beginning with betty dtf located on the IBM DTF client on volume tsov2 The OpenVMS DTF server n
252. ion fails before completing and the assigned time passes or has passed the copy operation is aborted This qualifier is not supported for VSAM file transfers The time value you select cannot exceed the queue maximum time value set by the system manager You can use the TRANSFER DTF SHOW QUEUE FULL command to determine what this value is If the value associated with the TIME qualifier is greater than the system maximum the value you specified causes an error and the system maximum value is used in its place If you do not specify the TIME qualifier the queue default time value is substituted You can use the TRANSFER DTF SHOW QUEUE FULL command to determine what this value is You cannot use the TIME qualifier with the NOQUEUE qualifier You may need to use the IBM file specification qualifier NOTRANSLATE to prevent transfer failures due to differences in collating key sequences between EBCDIC and ASCII 6 10 OpenVMS TRANSFER DTF File Transfer Operations Examples MVS TRANSFER DTF TRANS DTF gt COPY DAILY _LEDGER DAT NODE5S SNADTF _TRANS DTF gt ACCT LEDGER USER ACCT PASS SECRET RECORD LEDGER_RECORD Job DAILY_LEDGER queue SNADTFSQUEUE entry 1075 started on SNADTFSQUEUE This COPY command copies the latest version of the file DAILY_LEDGER DAT in the current OpenVMS default directory to the IBM system using the SNADTF server account on OpenVMS DTF server node NODE5 It creates an IBM data set called ACC
253. ired for all VSAM accesses e MVS This qualifier is valid only for creating a file and is ignored otherwise The VSAM qualifier is used to specify that a VSAM entry sequenced data set ESDS should be created instead of a non VSAM sequential data set e The default is NOVSAM e MVS This qualifier is supported only if it is indicated during DTF for IBM installation time that VSAM file creation is supported e mvs When transferring a VSAM ESDS to another MVS client you must specify this parameter 2 4 Setting Up DTF File Definition Files This section discusses creating file definition files File definition files are used in conjunction with the FILE_DEFINITION qualifier to establish default values for remote IBM file creation and file access File definition files can be used to significantly decrease the number of qualifiers that you have to enter on the command line File definition files are a convenience option and are not required to use DTF You may wish to skip this section and its subsections and proceed to Chapter 3 until you become more familiar with DTF You can use the IBM file specification qualifiers to specify file creation parameters but this may lead to typing errors and is more time consuming It is much easier to create a DTF file definition file containing this information You can then specify many parameters using the FILE_ DEFINITION qualifier Once created the DTF file de
254. is greater than the queue s maximum time value the rate specified with the COPY command is ignored and the queue s maximum value is used in its place To dear the maximum time attribute enter the word TIME without typing a number after the equals sign as in the following example SET QUEUE MAXIMUM TIME MINIMUM option You can use the MINIMUM qualifier with the following option e INTERVAL ime The definition for the option associated with the MINIMUM qualifier is as follows INTERVAL defines the queue s minimum interval attribute The value time time specifies the minimum interval a user can request with the INTERVAL qualifier If the number specified with the ANTERVAL qualifier on the COPY command is less than the queue s minimum interval value the rate specified with the COPY command is ignored and the queue s minimum interval value is used in its place To clear the minimum interval attribute simply enter the word INTERVAL without typing a number after the equals sign as in the following example SET QUEUE MINIMUM INTERVAL Examples TRANS DTF gt SET QUEUE _TRANS DTF gt DEFAULT INTERVAL 00 45 RETRIES 50 NIGHTLY This SET QUEUE command defines a default interval of 45 minutes and a default retry of 50 for the DTF queue named NIGHTLY TRANS DTF gt SET QUEUE _TRANS DTF gt MAXIMUM TIME 5 DEFAULT TIME 23 00 00 This SET QUEUE command defines a maximum time of 5 days and a defa
255. ite use of an invalid qualified file name results in a privilege violation error pds member or specifies an optional partitioned data set gdg number PDS member name or generation data group GDG number VSAM files do not use PDS members or GDG numbers A PDS member name is enclosed in parentheses and must be from 1 to 8 alphabetic characters long A GDG number is enclosed in parentheses and must be one of the following e n to indicate a new version e 0 to indicate the current version e n to indicate a previous version When using a GDG number with qualified file names the qualified portion of the file name cannot be more than 35 characters long For example JONES TEST FILE DATA references the file DATA in the partitioned data set J ONES TEST FILE DTF File Specifications 2 3 ibm file can be appended after a file name when using DTF Most IBM spec qualifiers file specification qualifiers can be associated with defaults that are set up during installation of the DTF for IBM software as described in the Digital SNA Data Transfer Facility Installation MVS and Digital SNA Data Transfer Facility Installation VM manuals These defaults are often modified so you may need to contact an IBM system programmer for the most current IBM file specification qualifier defaults You can specify a group of IBM file specification qualifiers with the FILE_DEFINITION qualifier The FILE_DEFINITION qualifier allows you
256. ive System Productivity Facility ISPF users and by CMS interactive users CMS and TSO E ISPF users must select an option from an ISPF menu to use the DTF panel interface If ISPF is not installed you can use the DTF panel interface from CMS by typing one of the DTF singleline file transfer commands see Chapter 8 without any parameters Note The DTF panels for ISPF and non ISPF users are identical except for two characteristics e ThelSPF panel sequence has an Operation Selection panel from which you can select one of three options After you select an option DTF displays one of three operation panels The non ISPF pane sequence does not have the Operation Selection panel instead DTF immediately displays one of the three operation panels The panel DTF displays depends on the DTF singleline command you entered DTFRECV DTFRESUM or DTFSEND Using the DTF for IBM Panel Interface 7 1 The three non ISPF operation panels have two extra fields that allow you to specify the information that ISPF users supply with the Operation Selection panel These fields allow you to specify the network subsystem name and the server node name 7 2 Using the DTF for IBM Panel Interface 7 2 The Operation Selection Panel Figure 7 1 Operation Selection Panel File transfer commands S SEND local file to remote system R RECEIVE file from remote system C RESUME previously failed transfer DTF SERVICES provided by NETWORK SUBSYSTEM gt
257. keywords SERVER and NETMGR which have the keyvalues NODE1 and DTF 2 respectively DEFINE SERVER The DEFINE command was entered with a keyword and a null keyvalue Entering an IBM File Specification An IBM file specification does not include a node name or the double colon node syntax An IBM file specification can include IBM file specification qualifiers if the entire file specification is enclosed within single quotation marks Chapter 2 explains the syntax of an IBM file specification and describes the qualifiers you can include Entering a DECnet File Specification A DECnet file specification includes a OpenVMS DTF client node name and the double colon node syntax as shown in the following format node filename Chapter 2 explains the syntax of OpenVMS RSX 11M M PLUS MS DOS OS 2 Digtial UNIX and ULTRIX file specifications Using the DTF for IBM Command Processor 9 3 You can enter optional access control information within the node portion of the specification by enclosing that information in quotation marks as shown in the following format node access control information filename Although the access control information can include user IDs and passwords associated with the input and output files this is not recommended When this information is entered within the node portion of the file specification the password is visible on the screen A better alternative is to use the INUSER OUTUSER a
258. l is described in Section 7 7 STORE on the remote node AS this file name FILENAME This is the name that the file you are copying will have on the remote system after the transfer completes You must supply this file name See Chapter 2 for more information on entering IBM file names when using DTF Note If the remote client node is running Digital UNIX or ULTRIX you must enter the file name with the proper case DISP This field specifies the disposition of the new file You can choose one of the following three values 1 NEW 2 OLD 3 REP Using the DTF for IBM Panel Interface 7 7 NEW creates a new output file If a file with the same name already exists DTF does not copy the file This is the default OLD creates a new output file that overlays an existing file of the same name If the file does not exist DTF issues an error message REP creates a new output file even if a file with the same name already exists OPTIONS There may be additional information about the remote output file that you can specify To see the panel for entering this information type the letter Y in the OPTIONS field and press the ENTER key These panels are described in Section 7 10 and Section 7 11 USING these options RECOVERABLE This field controls whether the transfer runs in recoverable mode or nonrecoverable mode Chapter 1 provides additional information about recoverable copy The default action is set up when you inst
259. le Options Panel Figure 7 9 VM Input File Options Panel COMMAND gt Fill in the required fields and press ENTER to continue MINIDISK information TAPE options DEVICE OWNER gt TAPE LABEL DEVICE ADDRESS gt FILE NUMBER PASSWORD gt DENSITY FILE options VSAM TAPE UNIT MIXED CASE NAME DTF options FILE DEFINITION LKG 8298 93R DTF displays the VM Input File Options panel see Figure 7 9 if you type Y in the OPTIONS field for a VM input file in the Send to Remote or Receive from Remote panel You can press PF3 to return to the operation panel that invoked this panel without initiating the operation The following pages describe the fields on this panel MINIDISK information DEVICE OWNER This field specifies the owner of the minidisk containing the input file For a local input file this field is optional if you have the minidisk linked and accessed For a remote input file see the description of the OWNERID qualifier in Chapter 2 Using the DTF for IBM Panel Interface 7 27 DEVICE ADDRESS This field specifies the device address of the minidisk containing the input file For a local input file this field is optional if you have the minidisk linked and accessed For a remote input file see the description of the MDADDRESS qualifier in Chapter 2 PASSWORD This field specifies the read password of the minidisk containing the input file For a local input file this field is
260. ler must specify that NODEPARMS LOWERCASECREATE is a supported feature e Ifthe IBM file is SMS system manage storage managed then lowercase file specifications are unsupported Examples VM Using file specification with mixed upper and lowercase characters DIR ARBOR VMXADEV 0 CASE OWNER IBMOWNER Directory ARBOR VMXADEV LIONS NAMES 0 OFS Sremind 0 CASE OFSMAIL OFSLOG 1 0 CASE Total of 3 files MVS Using file specification with a wildcard DIR O SNADTF IBMID CASE Directory O SNADTEF IBMVOL IBMID login CASE IBMVOL IBMID AAA In both examples the CASE qualifier is added to the file specifications which contain upper and lowercase characters CATALOG option MVS Specifies whether the data set you create is cataloged The possible options and their meanings are as follows e YES Catalog the data set e NO Do not catalog the data set Usage Notes e This qualifier is valid only for creating a file e The default specifies that DTF for IBM should supply a default The DTF for IBM default is specified at the IBM site when DTF for IBM is installed The default is recommended for this qualifier e ThelBM site can require or prevent cataloging of all new files If the IBM site does not have a global cataloging default specified it may have another default level specified In this case the IBM site selects a default setting for request
261. llowed by PA1 For SNA terminals you must first press Attn Then type C to cancel a transfer or type Q to query the status of a transfer and then press Enter To exit the automatically updated query screen type W and then press Enter 8 2 Using the DTF for IBM File Transfer Commands 8 1 DTFSEND You use the DTFSEND command to transfer a file on either the local MVS or VM system to a node on a DECnet network or to another IBM system DTFSEND input file TO user name AT node name AS output file options input file This is the name of the file you want to copy as it exists on the local system You must specify the correct file syntax for the type of system you are using VM system file specifications have a file name a file type and optionally a file mode and may be VM maclib members MVS files may be Partitioned Data Set members You should refer to manuals that describe your operating system s file system for the correct file syntax user name This is the user ID on the remote system to which you want to copy the file node name This is the node name of the remote system In most cases this is a node on a DECnet network You can however specify node name abbreviations for BM systems output file This parameter identifies the output file on the remote system You must know how to specify the name of the file on this system correctly see Chapter 2 This is a required pa
262. local OpenVMS system If you specify an IBM file specification using the qualifiers described in Chapter 2 the file is submitted to the batch subsystem on the indicated IBM system See the examples that follow this section PRIORITY n Requires OPER operator or ALTPRI alter privilege to raise the priority value of the SYSGEN parameter MAXQUEPRI Specifies the scheduling priority for the specified job The priority value can be in the range of 0 to 255 where 0 is the lowest priority and 255 is the highest The default value for PRIORITY is the value of the SYSGEN parameter DEFQUEPRI No privilege is needed to set the priority lower than the MAXQUEPRI value The PRIORITY qualifier has no effect on the process priority The queue establishes the process priority NO QUEUE queue name Specifies the name of the queue in which the job is entered If the transfer fails the job is rescheduled for a later transfer By default the file transfer job is entered in the SNADTF QUEUE queue You can override this queue by specifying another queue with the QUEUE qualifier The NOQUEUE qualifier allows you to specify that the copy operation be performed from the current process The NOQUEUE qualifier cannot be used with the RECOVER qualifier NO JRECOVER Indicates whether an attempt to retry a failed copy operation should be made The RECOVER qualifier cannot be used with the NOQUEUE qualifier The default is RECOVER You mu
263. lts FTS gt GRANGER DTF2 DTFSAMPLE TXT In this example the first line sets the output file default to be the OpenVMS DTF server node name The second line causes the third and fourth lines to be displayed The fifth line copies the file DTFSAMPLE TXT on the RSX system to the file GRANGER DTF2 on the MVS system using the OpenVMS DTF server node CHIEF and the server account SNADTF Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers RSX 11M M PLUS File Transfer Operations 11 17 11 10 Error Reporting Most error messages for the DCL and NFT interfaces are returned as normal DCL or NFT error messages Such as File already exists In some cases the DCL or NFT interface may return a secondary message indicating a DAP error code in the form nn nnn Usually the DAP error code is returned when the error is DTF specific Table 11 9 provides the corresponding abbreviated ASCII message text for all DTF specific DAP codes The Digital SNA Data Transfer Facility for OpenVMS Problem Solving and Messages manual contains explanations and user actions for these error messages The FTS utility creates log files where it records transfer information and any error messages The log file errors are recorded using the DAP code in the form nnnnnn Table 11 9 provides the corresponding abbreviated ASCII message text for all DTF specific DAP codes Before usin
264. ludes four logical components The DTF command processor accepts requests from IBM users and passes these requests to the local Network Manager The Network Manager establishes network connections For BM initiated requests the connections are between local File Managers and remote nodes For DE Cnet initiated requests the connections are between remote nodes and the local Node Manager The Node Manager receives incoming requests and selects File Managers to handle the requests File Managers control the actual file transfers Figure 1 1 shows the relationship of the software components in a DTF environment containing a DECnet SNA Gateway Note that the DECnet SNA Gateway can also be TCP IP node 1 3 What Are the Capabilities of the DTF Product The DTF software has the following capabilities Multiple user interfaces all clients Data translation all clients Multiple file types all clients Remote job submission and post processing all clients Directory capability OpenVMS RSX 11M M PLUS Digital Unix ULTRIX MS DOS and OS 2 clients Recoverable file transfer OpenVMS TRANSFER DTF and IBM clients only RMS programming interface OpenVMS clients only Record level access OpenVMS clients only Introducing the Data Transfer Facility DTF Product 1 3 Figure 1 1 Software Components in a DTF Environment MVS OpenVMS DTF for MVS VM OpenVMS
265. mmand NFT Primary Switch FTS Primary Switch APPEND JAP COPY no switch CREATE use TI as input DELETE DE DIRECTORY LI FU AT or BR SUBMIT SB or EX TYPE use TI as output AP no switch 1 DE 1 SB or EX 1 10peration not available RSX 11M M PLUS File Transfer Operations 11 1 11 2 APPEND Command To add the contents of one or more specified input files to the end of a specified output file use the DCL APPEND command APPEND input file spec output file spec the NFT command with the AP switch output file spec switches input file spec switches AP or the FTS command with the AP switch output file spec switches input file spec switches AP See Chapter 2 for the IBM file specification syntax Table 11 2 shows the level of support DTF provides for the DCL APPEND command qualifiers For more detailed information about the APPEND command refer to the DECna amp RSX Guide to User Utilities Notes When DTF for MVS creates an MVS file it calculates a maximum record length that is greater than the maximum record length of the input file record length is the next greater multiple of 256 minus 1 Any attempt to append a file with records larger than the calculated maximum record length of the existing file will result in an error DTF does not support append operations to files with RECFM FBS The request will be rejected Table 11 2 DTF Level of Support for APPEND Comman
266. mmand is no different than any other OpenVMS WRITE command OpenVMS File Transfer Operations 5 35 6 OpenVMS TRANSFER DTF File Transfer Operations This chapter describes how to use the TRANSFER DTF utility s command interface to transfer files You should use the TRANSFER DTF command interface to transfer large amounts of data or when you desire transfer operation to occur as batch jobs The TRANSFER DTF interface provides you with a checkpoint and recovery feature that resumes a file transfer from the last checkpoint after a network or system failure Note Although the TRANSFER DTF utility can be used to transfer both VSAM and non VSAM files it does not support recoverable copy for VSAM files You should use the OpenVMS DCL command interface when you need to copy small amounts of data quickly and interactively The DCL command interface does not provide you with the checkpoint and recovery feature Table 6 1 summarizes the conditions when recoverable file operations are possible Table 6 1 Recoverable File Operations Recoverable Copy Initiated From Input File Output File Copy OpenVMS client with On same OpenVMS On IBM DTF client YES TRANSFER DTF node continued on next page OpenVMS TRANSFER DTF File Transfer Operations 6 1 Table 6 1 Cont Recoverable File Operations Recoverable Copy Initiated From Input File Output File Copy On another DTF client On IBM DTF dient NO node On IBM DTF dlient
267. mode N The transfer operation executes in nonrecoverable mode Note If you specify the RECOVERABLE field as Y but the DECnet VAX node does not have the DTF utilities software installed DE Cnet client nodes running MS DOS OS 2 Digital UNIX or ULTRIX do not have recoverable copy capability DTF rejects the transfer request CHECKPOINT This field allows you to set the number of logical records between checkpoints The number of logical records can be from 1 to 65535 Note If you do not specify a value for this field the TRANSFER DTF on the client node uses a default value which is defined during the DTF installation The CHECKPOINT field is valid only if you specify the RECOVERABLE field as YES If you specify the RECOVERABLE field as NO DTF does not permit you to enter a value in the CHECKPOINT field Using the DTF for IBM Panel Interface 7 13 TRANSLATE Type N in this field to disable the translation of data from DMCS to EBCDIC No translation takes place if you copy a file from one IBM system to another EXTENDED This field lets you use the Data Translation Options panel to specify data translation options other than standard DMCS to EBCDIC translation Typing Y lets you see this panel This panel is described in Section 7 13 POSTPROCESS This field lets you use the Post Processing Options pane to specify a file at the remote node that should be submitted to the remote node s batch subsystem after the t
268. mp SNA Gateway Problem Determination Guide DECn amp SNA Gateway CT Installation DECne amp SNA Gateway CT Problem Solving OpenVMS amp ULTRIX DECne amp SNA Gateway CT Management OpenVMS DECn amp SNA Gateway CT Guide to IBM Parameters DECn amp SNA Gateway ST Installation DECne SNA Gateway ST Problem Solving OpenVMS DECn amp SNA Gateway ST Guideto IBM Parameters DECne amp SNA Gateway Management for OpenVMS Digital Peer Sever Installation and Configuration Digital Peer Saver Managenent Digital Peer Server Network Control Language Reference Digital Pee Server Guide to IBM Resource Definition xix XX e OpenVMS SNA Installation e OpenVMS SNA Problem Solving e OpenVMS SNA Guideto BM Parameters e OpenVMS SNA Management e OpenVMS SNA Problem D eermination Guide OpenVMS client users may also find the following Digital OpenVMS manuals to be helpful e OpenVMS User s Manual e OpenVMS Record Management Utilities Reference Manual e DEC DATATRIEVE User s Guide e OpenVMS DCL Dictionary e VMS DCL Concepts Manual e Guideto OpenVMS File Applications ULTRIX client users may also find the following Digital DECnet ULTRIX manual to be helpful e DECne ULTRIX Use Digital UNIX client users can also find the following Digital DE Cnet OSI manual helpful e DECn e OSI for Digital UNIX Introductory User s Guide RSX 11M M PLUS client users may also find the following Digital DE Cnet RSX manual to be helpful
269. n for Standardization ISO 8571 protocols These protocols support file transfer access and management through the use of the FTAM user facilities The facilities supported by DTF software are described in Table E 1 The descriptions include the respective FTAM commands Note OpenVMS users will access the FTAM user facilities to perform FTAM tasks Users on other operating systems will use an initiator on their systems to access FTAM on OpenVMS through the FTAM responder Table E 1 FTAM User Facilities Supported by DTF Software Facility Description Append Enables you to append files by using the APPEND command The facility allows the appending of one or more input files to the end of a single output file within or between FTAM applications Copy Enables you to copy files by using the COPY command The facility allows the copying of one or more input files to a single output file within or between FTAM applications Delete Enables you to delete files by using the DELETE command Directory Enables you to display file attributes for one or more files by using the DIRECTORY command Note RENAME is the FTAM user facility that enables you to rename files using the RENAME command The RENAME facility is the only FTAM user facility that DTF software does not support E 2 FTAM File Support E 2 1 FTAM Components FTAM consists of the following components e FTAM initiators Initiate associations for use
270. n on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers VM APPEND MASS DTFVM PROFILE EXEC Al USER RICHARDS _ DISK 1 RICHARDS LOGIN COM This command appends the file PROFILE EXEC to the OpenVMS file LOGIN COM located in directory RICHARDS File access on the VM system is done using mode 1 The server account is DTFVM the OpenVMS DTF server node is MASS and the VM user ID is RICHARDS Account verification on the VM system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers 5 3 BACKUP Command To create backup images of selected files use the DCL BACKUP command BACKUP input file spec output filespec Important DTF supports only OpenVMS to IBM backup requests and only IBM to OpenVMS restore requests Table 5 2 shows the level of support DTF provides for the DCL BACKUP command qualifiers For more detailed information about the BACKUP command refer to the OpenVMS Backup Utility Manual Note Always specify the NOTRANSLATE IBM file specification qualifier when using the BACKUP command OpenVMS File Transfer Operations 5 5 Table 5 2 DTF Level of Support for BACKUP Command Qualifiers For IBM File Qualifier Specifications NOJASSIST supported BACKUP supported BEFORE time supported BLOCK_SIZE n supported BRIEF suppor
271. n setting up this file ibm file spec quals Specifies IBM file specification qualifiers These qualifiers are described in Chapter 2 Command Qualifier NO LOG Provides the option of displaying informational messages about the operation ADD FILE_DEFINITION Examples DIFCFG gt ADD FILE_DEFINITION PERSONNEL _FILE PERSONNEL This example creates the PERSONNEL_FILE file definition record in the file definition database on the default node the node defined by the last USE NODE command The DTF file definition attributes are read from the PERSONNEL SNADTF F DL file in the current directory DTFCFG gt ADD FILE_DEFINITION LOG RAWDATA TAPE_SPECS TXT SNADTF I ADDFIL file definition RAWDATA added This example creates the RAWDATA file definition record in the file definition database on the default node The LOG qualifier indicates that a message should be displayed indicating that the file definition has been created The DTF file definition attributes are read from the TAPE _SPECS TXT file in the current directory DTFCFG gt ADD FILE_DEFINITION SWNODE SNADTFSMGR SECRET SWD_DATA _DTFCFG gt SWD_DATA C 2 Maintaining the OpenVMS DTF File Definition Database This example creates the SWD_DATA file definition record in the file definition database on node SWNODE The DTF file definition attributes are read from the SWD_DATA SNADTF F DL file in the current directory DTFCFG gt ADD FILE_DEFINITION NON_VSAM1 NOSUPERSEDE MDADDRESS 193
272. n the DE Cnet server node name that you wish to use to perform the transfer Note If you specify a value for the SERVER NODE field there must be an active server session that uses the same server name If there is no such server session DTF rejects the transfer request If you do not fill in the SERVER NODE field DTF selects a server node from the pool of active server sessions DTF attempts to select a server node with the same name as the client node from the request If the request does not specify a client node or if the client node is not a server node DTF selects the first available server node 7 4 Using the DTF for IBM Panel Interface 7 3 The Send to Remote Panel Figure 7 2 Send to Remote Panel SEND this local file FILENAME OWNER OPTIONS gt DEVICE ADDR gt PASSWORD gt Y N gt gt TO this USER at this remote NODE NODENAME USERID PASSWORD OPTIONS gt gt gt Y N gt STORE on your local system AS this file name FILENAME DISP OPTIONS gt gt NEW OLD REP Y N gt USING these options RECOVERABLE gt TRANSLATE gt POSTPROCESS gt BATCH SUB gt Y N CHECKPOINT Y N EXTENDED Y N Y N LKG 8306 93R DTF displays the Send to Remote panel Figure 7 2 shows the VM version after you select the SEND local file to remote system menu option from the Operation Selection panel or afte
273. n tracks are allocated if ALIGNMENT TRACKS is specified as part of the IBM file specification Enough 512 byte blocks in cylinders are allocated if ALIGNMENT CYLINDERS is specified as part of the IBM file specification BACKUP not supported IBM files do not have a BACKUP date BEFORE time supported BY_OWNER uic supported All BM resident files have a UIC of 0 0 If you specify the BY_OWNER qualifier with both OpenVMS and IBM input file specifications with a UIC other than 0 0 this qualifier affects only the OpenVMS input file specification INO JCONTIGUOUS ignored CREATED supported EXPIRED supported EXTENSION supported For IBM files each extension allocates enough tracks or cylinders to hold n 512 byte blocks If ALIGNMENT TRACKS is specified the extension is in tracks If ALIGNMENT CYLINDERS is specified the extension is in cylinders MODIFIED supported NOJOVE RLAY supported 11f specified for an IBM file specification the qualifier is ignored 31f specified for an IBM input file specification no file will be selected 4See Section 5 10 1 for restrictions continued on next page 6 4 OpenVMS TRANSFER DTF File Transfer Operations Table 6 2 Cont TRANSFER DTF Support for DCL COPY Command Qualifiers For IBM File Qualifier Specifications Commenis PROTECTION supported INOJREAD_CHECK not supported INOJREPLACE ignored SINCE time supported INOJTR
274. n use these commands from TSO Time Sharing Option on MVS systems TSO E with RE XX support or from CMS Conversational Monitor System on VM systems There are three interactive DTF file transfer commands that you can use 1 DTFSEND 2 DTFRECV 3 DTFRESUM The following sections describe these commands and their parameters You can use options with all of the DTF file transfer commands You must separate the command options from the rest of the command line with a single left parenthesis as in the following example DTFSEND PROFILE EXEC A TO JONES AT NYC AS ACCOUNTING DAT PASS SECRET All command options can be abbreviated as long as they remain unique VM If you type in one of the DTF file transfer commands without specifying any further information DTF enters the DTF non ISPF panel interface see Chapter 7 The panels prompt you for the rest of the information DTF needs to complete the file transfer MVS The panel interface cannot be entered by using DTF singleline commands VM You can cancel a transfer at any time by typing the CANCEL command and pressing Enter You can also find out the status of a transfer by typing the QUERY command and pressing Enter Using the DTF for IBM File Transfer Commands 8 1 MVS The method you use to cancel or query a transfer depends on the type of terminal you are using For non SNA terminals you must press Reset fo
275. name of the DTF Network Manager component If you specify a name the value overrides the name in the DTFUSER parameter file component name On VM systems the name is the 1 to 8 character virtual machine name On MVS systems the name is the 1 to 4 character subsystem name as it appears in the subsystem name table SERVER server name This name specifies the OpenVMS DTF server to which DTF sends the transfer request SERVER is the name of a DECnet node or TCP IP host server name The 1 to 6 character node name of the OpenVMS DTF server node you wish to handle the transfer request RESUME Subcommand Example The following example shows you how to use the RESUME subcommand to restart a failed transfer request DEFINE INFILE NODE1 lt JONES DTF TEST gt TEST123 RES INUSER JONES INPASS 1 DEFINE OUTFILE JONES DTFTEST MEMBER 2 DEFINE SERVER NODE1 NETMGR DTF2 RECOVERY Y 3 DTF0048I ENTER CLEAR DEFINE END LIST RECALL RESUME SET SHOW OR TRANS 9 34 Using the DTF for IBM Command Processor TRANSFER DTF0030I REQUEST SUBMITTED TO DTF2 DTF0037I THIS REQUEST ASSIGNED REQUEST NUMBER 00014 DTF0066I THE RECOVERABLE COPY REQUEST IS ABOUT TO BEGIN DTF0062I THIS REQUEST ASSIGNED RETRY NUMBER 00051 4 DTF0067I SERVER NODE HANDLING THE TRANSFER IS NODE1 VERSION 3 1 0 5 DTF0068I CLIENT NODE INVOLVED IN TRANSFER IS NODE1 VERSION 3 1 0 6 gt DTF0630E RECOVERABLE ERROR REPORTED FROM SERVER NODE1 7 gt
276. nd 10 6 drm DECnet ULTRIX command 10 8 DTF command 9 2 DTFRECYV file transfer command 8 8 DTFRESUM file transfer command 8 13 DTFSEND file transfer command 8 3 E END subcommand 9 22 example 9 22 ERASE RMS service call B 14 Error reporting displaying error messages 6 21 MS DOS dients 12 11 OS 2 clients 12 11 ULTRIX clients 10 9 Errors during data translation F 5 EXCHANGE NETWORK command OpenVMS DCL 5 24 F File definition adding to the file definition database 2 34 C 1 attributes BUFFERSPACE 2 42 COMPONENT_ALLOCATION 2 42 NAME 2 43 REPLICATE 2 43 REUSE 2 43 SHARE_OPTIONS 2 44 creating 2 33 File definition cont d displaying 2 35 C 3 examples 2 37 FILE_DEFINITION qualifier 2 19 modifying 2 35 C 7 removing from the file definition database C 8 sections ALTERNATE _INDEX 2 39 BASE 2 39 subsections DATA 2 39 INDEX 2 39 PATH 2 39 syntax 2 36 using IBM file qualifiers in 2 40 File definition database adding file definitions 2 34 C 1 displaying file definitions from 2 35 C 3 modifying a file definition 2 35 C 7 removing file definitions C 8 FILE DEFINITION entry field 7 26 7 29 7 37 FILE NUMBER entry field 7 25 7 29 7 32 7 37 File specification syntax DECnet file specification 2 4 IBM file specification 2 1 MS DOS file specification 2 7 OpenVMS file specification 2 5 OS 2 file specification 2 7 RSX 11M M PLUS file specification 2 6 ULTRIX and
277. nd PASSWORD qualifiers Note that this example looks only at the specified volume and is not a catalog directory The MVS system maintains a date stamp only It does not maintain a time stamp As shown in the example all times will be returned as 00 00 00 00 VM DIR FULL SIZE BONN DTFVM PROFILE EXEC Directory BONN DTFVM 5 22 OpenVMS File Transfer Operations PROFILE EXEC 1 File ID None Size 3 3 Owner 0 0 Created lt None specified gt Revised 17 SEP 1991 12 45 07 00 0 Expires lt None specified gt Backup lt No backup recorded gt File organization Sequential File attributes Allocation 3 Extend 0 Global buffer count 0 Version limit 0 Record format Variable length Record attributes Carriage return carriage control RMS attributes None Journaling enabled None File protection System Owner Group World Access Cntrl List None Total of 1 file 3 3 blocks This command displays a listing of all CMS files for the user SMITH The server account is DTFVM the OpenVMS DTF server node is BONN Note that the revised date is the only date maintained by the VM CMS file system Additional Information The DIRECTORY command does not accurately display information about the following fields File 1ID Always displayed as None Size Always contains two numbers in the format nn nn The first number is always the same as the second number and does not indicate
278. nd INPASS OUTPASS keywords when you define the input and output files Chapter 2 explains the syntax you must use when entering IBM and DECnet file specifications and explains the defaulting that is available Chapter 3 describes any limitations that must be observed when specifying input and output file specifications and lists the types of file organizations record formats and file attributes that are supported for input and output files You should read these chapters carefully before using the DTF command processor interface 9 3 1 CLEAR Subcommand The CLEAR subcommand allows you to remove the input and output file specifications set up with the DEFINE subcommand The syntax of the CLEAR subcommand is eae CLEAR Example The following example shows how to use the the CLEAR subcommand to erase the values set up with the DEFINE subcommand LIST 1 DEF INFILE CLUSTR LOGIN COM INUSER USER1 INPASS DEF OUTFILE IBMUSER LOGIN COM DISP OLD DEF SERVER NODE1 NETMGR DTF2 RECOVERY N DTF0047I DTF CLEAR 2 DTF0047I DTF LIST 3 DEF NETMGR DTF RECOVERY Y DTF0047I DTF 1 This LIST subcommand displays the values that were defined before the CLEAR subcommand was entered 9 4 Using the DTF for IBM Command Processor 2 The CLEAR subcommand clears or resets all previously defined values 3 This LIST subcommand displays all currently defined values 9 3 2 DEFINE Subcommand The DEFINE subcomm
279. nents Chapter 2 Describes the DTF file specifications and IBM file definition attributes Chapter 3 Describes the file types supported by DTF and restrictions DTF places on file types and file transfers Chapter 4 Describes data security with or without proxy Chapter 5 Describes how to use the OpenVMS DCL command interface to perform tasks using the DTF software xvii xviii Chapter 6 Chapter 7 Chapter 8 Chapter 9 Chapter 10 Chapter 11 Chapter 12 Appendix A Appendix B Appendix C Appendix D Appendix F Appendix E Appendix G Describes how to use the OpenVMS TRANSFER DTF utility to initiate recoverable file transfers It also describes commands for monitoring and controlling recoverable file transfers Describes how to use the menu driven MVS and VM DTF panel interface Describes how to use the basic MVS and VM DTF file transfer commands Describes how to use the robust MVS and VM DTF command processor Describes how to use DECnet ULTRIX and DECN amp OSI commands to perform tasks using DTF software Describes how to use the DECnet RSX commands to perform tasks using the DTF software Describes how to use PATHWORKS for DOS and PATHWORKS for OS 2 NFT commands to perform tasks using DTF software Describes how to use OpenVMS DATATRIEVE to access IBM file types using DTF Discusses the OpenVMS Record Management Services RMS programming interface and limitations to be aware of when you use DTF
280. nitions The command to show the file definition SPANNED is DIFCFG gt SHOW FILE DEFINITION SPANNED BASE HSMRECALL NO RELEASE NO SINGLE NO SPANNED YES TRANSLATE YES Refer to Appendix C for more detailed information on the SHOW FILE_ DEFINITION command DTF File Specifications 2 35 2 4 4 File Format and Syntax The file definition format is a grouping of IBM file attributes into related sections and subsections BASE and ALTERNATE_INDExX are the section headings INDEX DATA and PATH are the subsection headings Attributes can be defined within each section or subsection The syntax rules for this file are e Except for the BASE section all sections are optional e Only the BASE section can be specified for non VSAM files e Comments are preceded by an exclamation point e Blank lines may be included e There must be at least one space between an attribute and the value associated with it e Only one attribute is allowed on each line The format of the syntax is the following BASE fattribute_l value_l fattribute_n value_n INDEX attribute_1 value_1 attribute_n value_n DATA attribute_1 value_1 attribute_n value_n ALTERNATE_INDEX attribute_1 value_1 attribute_n value_n INDEX attribute_1 value_1 attribute_n value_n DATA attribute_1 value_1 attribute_n value_n PATH NAME value ALTERNATE_INDEX 2 36 DTF File Specifications attribute_l attribute_n INDEX attribut
281. node along with any optional access control information is always terminated by a double colon the DTF command processor uses this information to differentiate between IBM and DECnet file specifications is optional information that can include a user ID and password Although this information can be induded as part of the file specification this practice is not recommended When the user ID and password are entered this way they remain visible on the screen It is better to use the PASSWORD entry fields on the DTF panel interface or use the prompting feature of the DTF command interface to enter this information The file name portion of the file specification will vary based on the operating system running on the client node The formats for the file names are described in the sections that follow 2 2 1 Specifying Remote OpenVMS Files Enter the remote OpenVMS file specification as shown The node and access control portion of the file specification were previously described in Section 2 2 node access contr ol device lt directory gt filenametypeversion where node access control device directory is the 1 to 6 character name of the DECnet dient node is optional information that can include a user ID and password is a device on the OpenVMS system such as DRV1 or USER A device name can be up to 15 characters The login procedure on the dient node can include a default for the device specification The device
282. not allowed not allowed SPANNED supported not allowed not allowed not allowed TRANSLATE supported not allowed not allowed not allowed USERID supported not allowed not allowed not allowed VOLUME supported supported supported not allowed VSAM supported not allowed not allowed not allowed llf specified in a subsection overrides the value specified in the section Table 2 4 VM File Attributes and Their Usage in the BASE and ALTERNATE_INDEX Sections VSAM INDEX VSAM VSAM BASE ALTERNATE _ and DATA PATH File Attribute Section INDEX Section Subsections Subsection BATCHID supported not allowed not allowed not allowed BUFFERSPACE supported supported not allowed not allowed CLASS supported not allowed not allowed not allowed COMPONENT_ALLOCATION supported supported supported not allowed IGNORE supported supported not allowed not allowed MDADDRESS supported ignored not allowed not allowed NAME not allowed supported supported supported OWNERID supported not allowed not allowed not allowed llf specified in a subsection overrides the value specified in the section continued on next page DTF File Specifications 2 41 Table 2 4 Cont VM File Attributes and Their Usage in the BASE and ALTERNATE _ INDEX Sections VSAM INDEX VSAM VSAM BASE ALTERNATE _ and DATA PATH File Attribute Section INDEX Section Subsections Subsection RECORD_DEFINITION supported not allowed not allowed not allowed REPLICATE supported supported sup
283. not use wildcard characters in the queuename parameter You cannot use a generic or logical queue name as a parameter SET QUEUE Command Qualifiers SET QUEUE Qualifier Default DEFAULT option none MAXIMUM option none MINIMUM optior none DEFAULT option You can use the DEFAULT qualifier with the following options e INTERVAL nh mmi ss e RETRIES n e TIME day hh mmiss cc The definitions for the options that you can use with the DEFAULT qualifier are as follows INTERVAL defines the queue s default interval attribute The value hh mm ss hh mm ss specifies the default delta time that elapses before a stalled DTF operation because of a network failure is resumed If you specify a short time interval the queue restarts and tests more frequently to determine whether the DTF operation has restarted You cannot set a default interval value that is less than the value for the queue s minimum interval attribute By default the default interval value is 30 minutes 6 14 OpenVMS TRANSFER DTF File Transfer Operations RETRIES n TIME day hh mmiss cc defines the queue s default retries attribute The value n specifies the default number of times a file transfer is attempted before the operation is aborted You cannot set a default retries value that is greater than the value for the queue s maximum retries attribute By default the default retry value is 48 48 retries 30 minutes
284. nslation F 3 F 4 2 Supported CDD Data Structures You can use any of the following CDD structures for creating a record definition e ARRAY You can use the ARRAY OCCURS DEPENDING or OCCURS field attribute statements to define an array data structure e STRUCTURE You can use the STRUCTURE field description statement to define a nested data structure e VARIANTS You can use the VARIANTS field description statement to define a variant data structure All translations are based on the first variant in the list e VARIANTS OF The VARIANTS OF data type allows you to define a record that may have one of several formats depending on the value of a field known as the tag variable DTF supports the following data types for the tag variable TEXT SIGNED WORD and SIGNED LONGWORD F 4 3 Translation of Digital CDD and IBM Data Types Table F 1 lists the Digital CDD data types indicates whether DTF supports the data type and if supported shows the corresponding IBM data type Table F 1 Correspondence of CDD Data Types and IBM Data Types CDD Data Type IBM Data Type DATE not supported VIRTUAL not supported UNSPECIFIED not specified BIT Bit string Bit string TEXT DMCS text EBCDIC text VARYING STRING not supported POINTER not supported UN SIGNED BYTE not supported UN SIGNED WORD 2 byte 2 byte integer half word integer UN LONGWORD 4 byte 4 byte integer word integer continued on next page F 4 DTF Data
285. nt node are the same in this example 9 3 5 HELP mvs The HELP subcommand provides you with a list of DTF subcommands and a brief explanation of the function syntax and parameters of each subcommand The syntax of the HELP subcommand is CLEAR DEFINE END HELP TRANSFER LIST RECALL RESUME SET 9 26 Using the DTF for IBM Command Processor HELP Subcommand Examples The following examples show common uses of the HELP subcommand Example 1 display a list of all DTF subcommands HELP SUBCOMMA SUBCOM CLEA DEFI TRA LIST RECA SUBCOMMA RESUME SUBCO END HEL SET FUNCTION THE DTF AN IBM P THE DTF TRANSFER COMMAND INITIATI TO 1 D A R S Li D P jaa IDENTIFY T 1 2 3 D oO c RE O oO H DMHOHYK NEN P ADH E D RAM ESE FTER FORI BCO BCO U CAN RACK EV ET ECAL S C E DEF FER TRANS L REC DS FOR INITIATING A NEW TRANSFER REQUEST D FOR RESTARTING A PREVIOUSLY FAILED TRANSFER RES DS FOR CONTROLLING DTF TSO OPERATION TSO COMMAND ROCESSOR RU TSO COMMAND S RESUME PROCESSOR O GAN RA ITIATE E 5 Fj al a HE a EW T A FO Li a F THE THE O PARAI F UTPUT HANDLE RS REFINE ETER KEY YO AT A INFO A BCO PE S p T T D S T R O USE ON THAT TO IN ATION I O D RI D SE THE
286. o DMCS tab characters and the tabs will be recognized by many OpenVMS utilities If you wish to have the file appear the same on both systems you should run the OpenVMS file through a utility that converts horizontal tab characters to the required number of space characters If you do not mind losing horizontal tab information you can design a translation table that translates DMCS horizontal tabs to EBCDIC space characters 3 3 7 Keyed Access to Sequential Files RMS allows application programs to directly access records in sequential files by using the record s relative file address RFA or by using the record s key or relative record number DTF supports direct access to IBM sequential files using RFA access DTF simulates keyed access to IBM sequential files The IBM operating systems allow blocks that are not filled to capacity therefore DTF cannot simply use the key value to compute the record s address To simulate keyed access DTF reads from the beginning of the file until it finds the correct record This simulation results in greater performance degradation as the size of the file increases or as the requested record nears the end of the file 3 10 DTF Supported File Types 4 Data Security This chapter covers the data security measures provided by the operating systems that are supported by DTF software Data security can be described in terms of data security for files accessed on the local system and data security
287. o create the file NO WRITE_CHECK not supported 11f specified for an IBM file specification the qualifier is ignored 2Command fails with the following error message RMS F SUPPORT Network operation not supported FAL F FOP1 File processing options field rejected 4See Section 5 10 1 for restrictions Examples MVS COPY RABBIT DTF PRIMA ACCOUNTS PAYABLE ACCOUNTS_P DAT OpenVMS File Transfer Operations 5 13 This command copies the PDS member PAYABLE of the PRIMA ACCOUNTS data set located on the IBM DTF client to the ACCOUNTS P DAT file located on the current OpenVMS directory The OpenVMS DTF server node is RABBIT and the server account is DTF Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers VM COPY LOG PARIS DTFVM DTF MACLIB MEMBER1 OWNER JIM MDRPASS SECRET USER JIM PASSWORD GUESSME MEMBER1 MACRO This command must be entered with no continuators within double quotation marks Because of line length restrictions in this manual the command is represented as a wrapped command line This command copies the maclib member MEMBER 1 to the local file MEMBER1 MACRO The server account is DTFVM the OpenVMS DTF server node is PARIS the VM user ID isJ IM and the VM password is GUESSME VM COPY DEV LOG _S OXEN DTF TESTS EXEC USER GARY PASS 4BY
288. ode is veena and the server account is snadtf Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers VM dls 1 dtfsrv dtfvm a user white pass gray Directory dtfsrv ACCOUNTS DATA 1 USER WHITE PASS GRAY 4096 AMERICA DATA 1 USER WHITE PASS GRAY 512 AMOUNTS DATA 1 USER WHITE PASS GRAY 3584 ANIMALS DATA 1 USER WHITE PASS GRAY 512 4 files in 1 directory This command displays all files beginning with a located on the VM system The OpenVMS DTF server node is dtfsrv and the server account is dtfvm ULTRIX and UNIX File Transfer Operations 10 7 10 6 drm Command To remove a file on an IBM DTF client use the DECnet ULTRIX or DECnet OSI for Digital UNIX drm commana drm option file spec DTF does not provide support for any DECnet ULTRIX or DECnet OSI for Digital UNIX drm command options Notes If you attempt to delete an MVS file that was created with an expiration date and that expiration date has not been reached MVS will prompt the MVS console operator for permission to delete the file The file operation will wait until the console operator replies You cannot delete IBM tape resident files You cannot use wildcard characters in IBM file specifications when using the drm command Examples MVS drm veena dtfmvs richards dtf file user richards pass snowy This
289. of a base or alternate index cluster The INDEX subsection can be specified only when defining a VSAM indexed file DATA The DATA subsection describes the attributes of the data records in the VSAM file The DATA subsection can be specified for all VSAM file types PATH PATH associates the alternate index with the base cluster PATH contains information about the key of reference assigned to a VSAM file Refer to Appendix D for more information about VSAM files DTF File Specifications 2 39 2 4 7 File Attributes All IBM file specification qualifiers with the exception of the password qualifiers can be used as file attributes in the file definition BASE section subject to the same restrictions described in Section 2 3 Note Attributes in the file definition file do not begin with a slash and do not use the colon used in qualifiers Qualifiers with the NO option use YES and NO as argument values in the file definition file For VSAM files Table 2 3 lists the file attributes used for MVS VSAM files and shows in which sections and subsections the attributes can be used Table 2 4 lists the file attributes used for VM VSAM files and shows in which sections and subsections the attributes can be used Both tables contain six VSAM file attributes that can only be defined using a file definition file These attributes are described following the tables For a description of the other attributes see the description of the
290. ommand 00 ccc cece eee ene 9 5 9 3 2 1 Keywords and Keyvalues for Specifying the Input Filey tive teno Wa oaa WY a lek hace alate saan Mahal OOo 9 7 9 3 2 2 Keywords and Keyvalues for Specifying the Output Eile iether Bk ins RPA a a aaa 8 Foci Pena aE Oo Bian 9 12 9 3 2 3 Keywords and Keyvalues for Specifying Transfer Parameters iiia tas Bees Bee Wak a Panera ot 9 18 9 3 3 END Subcommand 00 cece eens 9 22 9 3 4 TRANSFER Subcommand 0000 cece e eens 9 23 9 3 5 HELP MYSI se die e n bee eda Maes a raa we eae 9 26 9 3 6 LIST Subcommand s es saaa aaea aaa 9 28 9 3 7 RECALL Subcommand 0 0000 e cence eee eens 9 29 9 3 8 RESUME Subcommand 000 cece eee eens 9 30 9 3 9 SET Subcommand 0 00 c ee eee ee eens 9 36 9 3 10 SHOW Subcommand 00 c eee eee eens 9 38 9 4 DTF Command Processor Usage Considerations 9 38 9 4 1 Using Tapes MVS Systems 0 000 eee eee 9 39 9 4 2 Using Tapes VM Systems 0 0000 9 39 9 4 3 Overriding the Server and Server Account 9 39 9 5 Executing the DTF Command Processor in Batch Mode VM Systems as ial eae Pata ed Gta baad ai whew e Sa kad evs 9 39 9 6 Executing the DTF Command Processor in Batch Mode MVS SYSCQMS feos ead dew gods a aA a died Maw de eae heats 9 40 9 6 1 TheSYSTSIN DD Card 0 020 es 9 40 9 6 2 Notes and Restrictions for DTF Batch Mode Operations 9 44 9 7 DTF Return Codes in DTF
291. on data group GDG specifying member 2 1 GET RMS service call B 15 H HELP subcommand 9 26 HSMRECALL 2 19 IBM file specification format 2 1 IBM file specification qualifiers 2 9 ALIGNMENT 2 15 ALLOCATION 2 15 BATCHID 2 16 BLOCK_SIZE blocksize 2 16 ICASE 2 16 CATALOG option 2 17 CLASS class name 2 18 DEFAULT 2 18 defaults 2 9 DENSITY density 2 18 DIRECTORY_BLOCKS n 2 19 FILE_DEFINITION filedefinition 2 19 HSMRECALL 2 19 I GNORE condition 2 20 KEY position length position ength 2 20 LABEL labd 2 21 Index 6 IBM file specification qualifiers cont d MDADDRESS disk address 2 21 MDMPASSWORD3 password 2 21 MDRPASSWORD password 2 21 MDWPASSWORD password 2 21 NULL option 2 26 OWNERID owne 2 26 PASSWORD password 2 27 RECORD_DEFINITION record definition 2 27 RELEASE 2 27 restrictions 2 10 RETENTION_PERIOD n 2 27 RFA 2 28 SECONDARY_ALLOCATION 2 28 SECURITY_DATA data 2 29 SEQUENCE_NUMBERin 2 29 SINGLE 2 29 SMSDCLASS data class 2 30 SMSMCLASS data class 2 30 SMSSCLASS data class 2 30 SPANNED 2 30 SUPERSEDE 2 31 TRANSLATE filespec 2 31 UNIT unit spec 2 31 2 32 USERID userid 2 32 NOLUME vol namd 2 32 VSAM 2 33 I GNORE condition 2 20 INCASE keyword 9 7 INDEN keyword 9 8 INFDEF keyword 9 9 INFILE keyword 9 7 INLABEL keyword 9 9 INMDADDR keyword 9 9 INMDOWNER keyword 9 10 INMDPASS keyword
292. on of file definition records refer to Chapter 2 file specification A file definition record in the file definition database Length up to 32 characters Usage Note e The filespecification keyvalue is valid only if the INFILE is an IBM file specification If the input is not an IBM file specification the DTF command processor will ignore this parameter INLABEL label Specifies the format of the tape labels on the tape that the input file is read from label One of the following directory labels AL ANSI V1 labels or ISO ANSI FIPS V3 labels Not supported for VM input files SL Standard labels Usage Notes e Tape restrictions may apply Section 9 4 1 describes any restrictions e You should specify the INLABEL keyword only if the input file resides on a tape e Ifthe input file resides on disk the DTF command processor will ignore this keyword e If you do not specify this keyword and the input file resides on tape the DTF command processor will assume that standard tape labels are used INMDADDR file number VM If the minidisk where the input file resides is not currently linked and accessed use this keyword to supply the address of the minidisk This may refer to a minidisk you own or the one owned by the user in the INM DOWNER field Using the DTF for IBM Command Processor 9 9 INMDOWNER user id MM The owner of the minidisk where the input file is located If you own the minidisk you do not ha
293. one UDF SEQ UDF SEQ No NBS 9 No Legend for Table E 3 CR Carriage Return FIX Fixed NOT NOTsignificant ORG Organization PS Partitioned Sets RAT Record Attributes RECFM and RFM Record Format SEQ Sequential STM Stream Record Format StrSig String Significance UDF Undefined Format VAR Variable Record FTAM File Support E 7 E 4 Examples of OSl Initiated File Transfer Operations To activate the FTAM facilities the FTAM DCL interface requires a single command qualifier APPLICATION_PROTOCOL FTAM which operates with the APPEND COPY DELETE and DIRECTORY DCL commands See Chapter 5 for the level of support DTF provides for the DCL APPEND COPY DELETE and DIRECTORY command qualifiers Note All references to systems in the following examples are based on the configuration in Figure E 1 APPEND Command Example VM APPEND APP FTAM FTAM2 NOT OSISSMOG DRAKE DTFVM FTAM2 NOT The example APPEND command illustrates how you can append concatenate a local input file FTAM2 NOT an FTAM 1 StrSig FIXED file to a single remote IBM system output file FTAM2 NOT The input file and output file can be any combination of local and remote files OSISSMOG is the association name which points to the FTAM responder DRAKE is the OpenVMS DTF server node name SNADTF is the DTF server account The file name that is created on the IBM VM system is FTAM2 NOT See Section E
294. operating systems that do not support keyed or relative file organizations If a file is copied from one of these DE Cnet clients to an IBM system it will be stored as a variable format record If an IBM file is copied to one of these DECnet clients it will be stored as stream format variable format in RSX 11M M PLUS The IBM operating systems do not support stream format records these DE Cnet clients have operating systems that support stream format records only 3 3 3 VSAM File Transfer Restrictions The following restrictions apply to VSAM file transfers If an OpenVMS TRANSFER DTFE transfer request involves VSAM files the transfer must execute in nonrecoverable mode only If a transfer request involves VSAM RRDS and ESDS files you can not overlay an existing file VSAM RRDS or KSDS files cannot be copied to client nodes running MS DOS OS 2 RSX 11M M PLUS Digital UNIX or ULTRIX VM DTF for VM supports only one VSAM access at a time If a request arrives that requires access to a DOS disk and a VSAM access is already in progress then VSAM is already active is returned 3 8 DTF Supported File Types 3 3 4 Printer File Transfer Restrictions The DTF product cannot transfer IBM files in machine print format However DTF can be used to transfer both IBM FORTRAN ANSI print format files and OpenVMS RMS FORTRAN carriage control format files The following restrictions apply to IBM ANSI and OpenVMS FORTRAN printer
295. ords from a Domain on an IBM System Use the same commands to retrieve read write modify and delete records from an IBM file as you would use for an RMS file A 4 Ending a DATATRIEVE Session That Is Accessing an IBM File Issue the DATATRIEVE FINISH or EXIT command to end a session toa domain that is accessing an IBM file Using OpenVMS DATATRIEVE with DTF A 3 B RMS File System and Programming Constraints This chapter describes the Record Management Services RMS file system and programming constraints that you should be aware of when using the RMS programming interface to access files on an IBM system The information provided here should be used along with the information found in the OpenVMS Record Management Services manual B 1 RMS File System Constraints The DTF software causes IBM files to appear to the OpenVMS operating system as remote RMS files You can access the IBM files with direct RMS calls or with certain utilities such as COPY that are layered on RMS The underlying differences in the file systems used by IBM and OpenVMS impose a number of constraints on accessing IBM files The following types of files and access methods are not supported by OpenVMS when communicating with an IBM system e Sequential Stream STM Stream CR STMCR Stream LF STMLF Undefined UDF VFC When creating a data set on the IBM system a VFC format can be specified if the record attribute PRINT CARRI
296. ormation about recoverable copy YES The transfer executes in recoverable mode Using the DTF for IBM Command Processor 9 19 NO The transfer executes in nonrecoverable mode Usage Notes e If you specify RECOVERY YES but the client node does not have the OpenVMS DTF utilities software installed OpenVMS dient node without the OpenVMS DTF utilities software or DECnet client nodes running MS DOS RSX 11M M PLUS OS 2 Digital UNIX or ULTRIX the transfer request will fail e f you specify RECOVERY NO and the server or client nodes involved in the transfer request are running DTF for MVS V1 0 the command processor ignores the NO keyvalue and the transfer operation will proceed in recoverable mode SERVER node Selects the server session to which the transfer request is sent for execution node The node name of the node running the OpenVMS DTF server software Usage Notes e If you specify a keyvalue for the SERVER keyword there must be an active server session with the DTF Network Manager subsystem that uses the same server name If there is no such server session the transfer request will be rejected e If you do not specify a keyvalue for the SERVER keyword by default DTF selects an OpenVMS DTF server node from the pool of active server sessions DTF first attempts to select a server node with the same name as the client node from the request If the request does not specify a client node or if the client node is n
297. orted supported supported supported supported supported supported All BM resident files have a UIC of 0 0 If you specify the BY_ OWNER qualifier with both OpenVMS and IBM input file specifications with a UIC other than 0 0 this qualifier affects only the OpenVMS input file specification 11f specified for an IBM file specification the qualifier is ignored 2See Section 5 10 1 for restrictions OpenVMS File Transfer Operations 5 21 Examples MVS DIR FULL O DTFMVS6 SMITH T VOL TSOVL2 Directory O DTFMVS6 TSOVL2 SMITH TOM File ID None Size 1 1 Owner 0 0 Created 4 OCT 1991 00 00 00 00 Revised lt None specified gt Expires 4 OCT 1992 00 00 00 00 Backup lt No backup done gt File organization Sequential File attributes Allocation 1 Extend 0 Global buffer count 0 Version limit 0 Record format Fixed length 10 byte records Record attributes Carriage return carriage control RMS attributes None Journaling enabled None File protection System Owner Group World Access Cntrl List None Total of 1 file 1 1 blocks This command displays all the fields for all files containing SMITH T in the beginning of their names for the user SMITH The OpenVMS DTF server node is the local node and the server account is DTFMVS6 Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID a
298. orted supported supported SUPERSEDE supported ignored rejected TRANSLATE 123 supported supported supported UNIT 2 3 4 5 supported supported ignored USERI D12345 supported supported supported NOLUME 345 supported supported supported NSAM 3 ignored ignored sequential files only 1This qualifier is used when reading IBM input files for copy search compare and display operations 2This qualifier is used when writing over existing IBM output files 3This qualifier is used when creating a new IBM file 4This qualifier is used when deleting an IBM file 5This qualifier is used when listing an IBM directory 6This qualifier is used only for IBM tape resident files 2 14 DTF File Specifications 2 3 3 Qualifier Descriptions This section describes the IBM file specification qualifiers used when accessing files on IBM DTF clients Qualifiers supported only when accessing files on IBM VM clients are followed by a VM Qualifiers supported only when accessing files on IBM MVS clients are followed by a MVSj If VM or MVS is not present the qualifier is supported for both VM and MVS file access The qualifiers are described in alphabetical order All qualifiers can be abbreviated as long as the abbreviation remains unique ALIGNMENT option MVS Specifies allocating data sets on one of the following boundaries when creating a data set e TRACK e CYLINDER Usage Notes e This qualifi
299. orts that a recoverable error was reported from server NODE1 Additional OpenVMS DTF error messages report what caused the recoverable error This RESUME command restarts the transfer This message reports that the transfer was successfully completed Using the DTF for IBM Command Processor 9 35 9 3 9 SET Subcommand The SET subcommand allows you to change the way the DTF command processor operates SET alters the parameters described in the following sections for the duration of the DTF command processor session or until you alter the parameter with another SET command These same parameters that you change with the DEFINE command stay in effect for one transfer The default value for this subcommand is set during installation of the DTF for IBM software The Digital SNA Data Transfer Facility Installation VM or Digital SNA Data Transfer Facility Installation MVS manual provides additional information about how to establish the default CONVERSE LONG SHORT Gives you the option to display full or abbreviated messages LONG Full messages are displayed SHORT Abbreviated messages are displayed ON DEBUG OFF Gives you the option to display and mask DTF processor messages ON All DTF command processor messages are displayed OFF Non essential DTF command processor messages are masked SPACE REJECT IGNORE NONE This keyword is used to indicate how DTF processes null records length 0
300. ot also a server node DTF selects the first available OpenVMS DTF server node NETMGR dif name A required keyword that specifies which DTF Network Manager subsystem should receive the transfer request dtf name For MVS systems this is the 1 to 4 character name defined for DTF in the subsystems name table For VM systems this is the 1 to 8 character name of the Network Manager virtual machine 9 20 Using the DTF for IBM Command Processor Usage Note e If you do not specify a keyvalue for this keyword the DTF command processor will use the site defined default name The Digital SNA Data Transfer Facility Installation VM or Digital SNA Data Transfer Facility Installation MVS manual explains how to establish the default subsystem name YES TRANSLATE NO OpenVMS file specification An optional keyword that specifies whether you want your files translated For more information about data translation refer to the section in Appendix F that describes translation tables Also see Appendix G YES Data is translated using standard translation tables NO Data is not translated OpenVMS file specification An OpenVMS file specification for loading a nonstandard translation table Length 1 to 255 characters Usage Notes e Ifthe transfer involves an indexed file that contains binary data specify TRANSLATE NO because data translation could generate duplicate keys VSAM does not allow duplicate keys If this occurs on the pr
301. ot contain any records that exceed 80 bytes Table 11 7 DTF Level of Support for SUBMIT REMOTE Command Qualifying Switches For IBM File DCL SUBMIT Qualifier NFT Switch FTS Switch Specifications l JAS AS supported 1 M IM supported LOG LO filespec LO filespec supported NOWARNINGS NM 1 supported 1 INV l not supported 10peration not available 2Switch available for SB operations only continued on next page 11 14 RSX 11M M PLUS File Transfer Operations Table 11 7 Cont DTF Level of Support for SUBMIT REMOTE Command Qualifying Switches For IBM File DCL SUBMIT Qualifier NFT Switch FTS Switch Specifications FO owner not supported z AX supported 1 BK supported RC2 l supported l peration not available 2Switch available for SB operations only Examples MVS SSUBMIT REMOTE WINTER SNADTF KRINGLE LIST JCL USER KRINGLE PASS SNOW This command submits the file KRINGLE LIST J CL to the batch system on the MVS system The OpenVMS DTF server node is WINTER and the server account is SNADTF The IBM user ID is KRINGLE and the user password is SNOW The file KRINGLE LIST J CL should not contain any records that exceed 80 bytes MVS FTS gt WINTER SNADTE KRINGLE LIST JCL USER KRINGLE PASS SNOW EX This command is identical to the preceding except it uses the FTS interface MVS FTS gt WINTER SNADTF KRINGLE LIST JCL U
302. ote Do not use an account in the OpenVMS DTF server account database for the access control parameter file definition name Specifies the user assigned name of the file definition in the definition database ibm file spec quals Specifies IBM file specification qualifiers These qualifiers are described in Chapter 2 C 6 Maintaining the OpenVMS DTF File Definition Database Command Qualifier NO LOG Provides the option of displaying informational messages about the operation MODIFY FILE_DEFINITION Examples DIFCFG gt MODIFY FILE DEFINITION PERSONNEL_FILE PERSONNEL This example modifies the PERSONNEL_FILE file definition record in the file definition database on the default node the node defined by the last USE NODE command The DTF file definition attributes are read from the PERSONNEL SNADTF FDL file in the current directory DTFCFG gt MODIFY FILE_DEFINITION NON_VSAM1 TRANSLATE NOSUPERSEDE _DTFCFG gt MDADDRESS 195 This example updates the NON_VSAM1 file definition Files created using the NON_VSAM1 file definition will now use DMCS EBCDIC data translation will not be superseded and will be on the minidisk with address 195 DTFCFG gt MODIFY FILE_DEFINITION MVS_VSAM USERID PAYROLL _DTFCFG gt EXPIRATION_DATE 1 JAN 1999 TRANSLATE This example alters the values associated with the EXPIRATION DATE and USERID attributes and allows data translation for the file definition MVS_ VSAM Note that all of these chang
303. ount and password needed to gain access to the IBM system The NOTRANSLATE qualifier specifies that no translation is to be performed on the file during transfer The CONTIGUOUS qualifier specifies that the OpenVMS output file should occupy consecutive physical disk blocks VM TRANSFER DTF TRANS DTF gt COPY INTERVAL 00 10 TIME 02 00 MEMO TXT _TRANS DTF gt DAPPER DTFVM RAISE SCRIPT USER SMITH PASS JOHN Job MEMO queue SNADTFSQUEUE entry 17 started on SNADTFSQUEUE This COPY command copies the OpenVMS file MEMO TXT using the DTFVM server account on OpenVMS DTF server node DAPPER to the IBM file RAISE of type SCRIPT 6 12 OpenVMS TRANSFER DTF File Transfer Operations The command qualifiers specify what you want to happen if the copy operation fails The ANTERVAL qualifier causes DTF to attempt to resume the copy operation every 10 minutes The TIME qualifier aborts the operation if the file transfer does not complete within 2 hours The IBM file specification qualifiers specify the user account named SMITH and the password J OHN VM TRANSFER DTF TRANS DTF gt COPY POST 0 DTFVM POST EXEC _TRANS DTF gt SYSSLOGIN LEDGER DAT O DTFVM LEDGER DAT This COPY command requests that once the file SYS LOGIN LEDGER DAT is copied to O DTFVM LEDGER DAT and the file transfer completes successfully then DTF will submit the O DTFVM POST EXEC file on the remote batch system The post pro
304. ount of table space you are allowed is determined at DTF for IBM installation time If you exceed this table space size you will receive a status code indicating that RFA table space has been exceeded and the requested operation for example GET or PUT will not be performed e To free your table space the indexed file must be closed and opened If you are a DATATRIEVE user you must issue a FINISH command followed by a READY command to close and open a file e If a record is added to a PDS member DTF rewrites the member Therefore RFA values for records in the member will no longer be valid If the application that added the record to the PDS member requires valid RFA values DATATRIEVE requires this the RFA values need to be reestablished In DATATRIEVE this means reestablishing the collection SECONDARY_ALLOCATION number of 512 byte blocks Specifies or overrides the defined default extension quantity for the input file The number of blocks can be up to X7FFFFFFF 2 28 DTF File Specifications Usage Notes e This qualifier should be used only if the default extension quantity defined for the input file is insufficient for future growth e Note that the DCL BACKUP utility will not send this value to the IBM system If you are writing savesets to IBM disks this qualifier may be necessary if the ALLOCATION value has been underestimated SECURITY_DATA data The SECURITY_DATA qualifier is an IBM site dependent qualifier Th
305. ountered See the NULL qualifier in Chapter 2 for information on NULL Using the DTF for IBM Panel Interface 7 35 MIXED CASE NAME This field specifies whether DTF should accept the case in which the file name was entered A value of Y will cause DTF to open the file in a case sensitive fashion N or blank will default to uppercase Note This option has no effect unless NODEPARMS LOWERCASECREATE is set toON See the CASE qualifier in Chapter 2 for information on MIXED CASE PRIMARY ALLOCATION A 5 digit number specifying the number of 512 byte blocks that DTF will initially allocate when creating a file on the IBM system See the ALLOCATION qualifier in Chapter 2 for information on ALLOCATION SECONDARY ALLOCATION A 5 digit number specifying the number of 512 byte blocks that DTF will use to extend the file if the initial allocation is insufficient to hold the transferred file See the SECONDARY_ ALLOCATION qualifier in Chapter 2 for information on SECONDARY_ALLOCATION TAPE options TAPE LABEL Specifies the format of the tape labels to be used for the output tape You can specify one of the following tape labels AL ANSI V1 labels or ISO ANSI FIPS V3 labels BLP Bypass label processing NL Non labeled SL Standard labels e Section 3 3 5 describes additional restrictions that may apply for tape resident files e You should fill in this field only if the output file resides on a tape e If the output file resi
306. penVMS DTF B 6 RMS File System and Programming Constraints B 3 1 CLOSE Table B 1 describes the special fields of the CLOSE RMS service call Table B 1 CLOSE FAB and XAB Input Fields Option or Field Name XAB Type Restriction Description FAB I_FOP File processing options FAB V_RWC Always in effect Rewind magnetic tape volume on close applies to magnetic tape only FAB V_TEF Ignored Truncate at end of file Never done for MVS files To deallocate unused space use the RELEASE attribute or RELEASE qualifier in your file definition Always done for VM files FAB L_XAB Next XAB address XABPRO Ignored Modify file protection and ownership XABRDT Ignored Modify revision date and number B 3 2 CONNECT Table B 2 describes the special fields of the CONNECT RMS service call Table B 2 CONNECT RAB Input Fields Field Name Option Restriction Description RAB L_ROP Record processing options RAB V_BIO Disallowed Block 1 O RMS File System and Programming Constraints B 7 B 3 3 CREATE Table B 3 and Table B 4 describe the special fields of the CREATE RMS service call Table B 3 CREATE FAB Input Fields Field Name Option Restriction Description FAB B_BKS Ignored Bucket size FAB W_BLS Ignored Block size FAB B_FAC File access FAB V_BIO Disallowed Block I O access to file FAB V_BRO Ignored Block or record I O access to file FAB V_DEL Ignored Delete access to file FAB V_TRN Ignored Truncate access to file
307. permit you to specify a keyvalue for the CHKPT keyword SPACE REJECT IGNORE NONE NULL 9 18 Using the DTF for IBM Command Processor This keyword is used to indicate how DTF processes null records length 0 to an IBM file Because the CMS file system does not support null length records DTF cannot write them to the indicated device For more information about the NULL option see the NULL qualifier description in Chapter 2 SPACE A 1 byte record is inserted in place of the zero length record The one byte is set to an EBCDIC space character x 40 REJECT mvs An error is returned if a null record is encountered IGNORE The null record is simply ignored when writing the file The result is that the output file has fewer records than the input file NONE VM No special processing will occur An error will be returned if a null record is encountered MVS No special processing will occur The record will be accepted as is RECDEF path name Specifies the path name that is used to access a record definition in the VAX Common Data Dictionary CDD Appendix F provides additional information about field level translation with the CDD path name A CDD path name on the server node Length 1 to 255 characters YES RECOVERY NO A required keyword that specifies whether the transfer is executed in recoverable mode or nonrecoverable mode Chapter 1 provides additional inf
308. play If this parameter is not specified information on all your jobs is displayed SHOW JOBS Command Qualifiers SHOW JOBS Qualifier Default ALL ALL BRIEF BRIEF FULL None QUEUE queue name QUEUE USER user name None OpenVMS TRANSFER DTF File Transfer Operations 6 17 ALL Displays the names of all DTF job entries By default the SHOW J OB command displays only jobs owned by the current process This qualifier is mutually exclusive with the USER qualifier BRIEF Displays a shortened listing of information about job entries in the queue When you use the BRIEF qualifier the following information is displayed e User name e Jobname e Queue name FULL Displays complete information about all jobs in DTF queues owned by the current process The information on jobs includes the following e The date and time the COPY command was submitted e The entire COPY command you entered e The status of the the COPY operation QUEUE queue name Specifies a queue name If you omit this qualifier jobs on all queues are displayed You can use wildcard characters with this qualifier USER user name Displays information about jobs owned by the specified user Examples TRANSFER DTF TRANS DTF gt SHOW JOB BRIEF Job 1234 is state submitted on 26 NOV 1984 15 50 24 by SMITH With the SHOW J OB BRIEF command stateis either QUEUED INITIALIZED ACTIVE or PAUSED TRANSFER DTF TRANS DTF gt SHOW JOB FULL Job 1
309. ported not allowed RETENTION_PERIOD supported not allowed not allowed not allowed REUSE supported supported supported not allowed RFA supported not allowed not allowed not allowed SECURITY_DATA supported not allowed not allowed not allowed SHARE_OPTIONS supported supported supported not allowed TRANSLATE supported not allowed not allowed not allowed USERID supported not allowed not allowed not allowed VOLUME supported supported supported not allowed VSAM supported not allowed not allowed not allowed 11f specified in a subsection overrides the value specified in the section Attributes Unique to File Definition Files BUFFERSPACE n Specifies the minimum space required for buffers as a decimal number that is less than 16776704 decimal Usage Notes e If you do not specify BUFFERSPACE VSAM determines the size by using default values for the control intervals e The default value is recommended for this attribute COMPONENT_ALLOCATION option Specifies how the space for a component is allocated e UNIQUE VSAM data space is created and assigned exclusively to each component e SUBALLOCATION space from one of the VSAM data spaces on the volume is assigned to the component 2 42 DTF File Specifications Usage Notes e For VSAM files SUBALLOCATION is the default The default value is recommended ICF Users Note that UNIQUE is the default for ICF catalogs SUBALLOCATION is ignored e You cannot specif
310. pplies all of the values other than the password including the user ID required for the transfer These values have been previously defined in a record named INV_ UPDATE The system by default performs EBCDIC to ASCI text translation on the file OpenVMS TRANSFER DTF File Transfer Operations 6 11 Notice that the system prompts you for an input file From and an output file To if you execute the COPY command without including the file names MVS TRANSFER DTF TRANS DTF gt COPY _TRANS DTF gt O SNADTF DEPT DATA USER JONES PASS SECRET NOTRANS _TRANS DTF gt RAW_DATA DAT CONTIGUOUS Job RAWDATA queue SNADTFSQUEUE entry 62 started on SNADTFSQUEUE TRANS DTF gt EXIT SHOW SYMBOL SENTRY SENTRY 62 SHOW ENTRY SENTRY Jobname Username Entry Blocks Status RAW_DATA JONES 62 500 Executing On Server queue SNADTFSQUEUE DELETE ENTRY SENTRY This COPY command copies the IBM file DEPT DATA using the SNADTF server account on the local OpenVMS DTF server node The file is copied to the file RAW_DATA DAT in the current OpenVMS directory After exiting the TRANSFER DTF utility the user issued the SHOW SYMBOL command to get the job entry number stored in E NTRY The SHOW ENTRY command displayed the status of the entry The user then issued the DELETE ENTRY command to delete the job The IBM file specification has three qualifiers The USERID and PASSWORD qualifiers specify the user acc
311. quential file and the VSAM qualifier is added to the output MVS file name Section D 3 explains the VSAM duster attribute defaults e Physical sequential This includes sequential files members of a partitioned data set generation data group files and tape resident data sets If the PDS already exists the member will be added otherwise a new PDS file will be created If the input file is either a sequential file or a VSAM ESDS file and the VSAM qualifier is not specified a physical sequential output file will be created DTF supports the following VM file organizations as output e WVSAM This includes KSDS RRDS and ESDS organizations Section 3 3 3 describes the VSAM restrictions 3 4 DTF Supported File Types A VSAM KSDS will be created if the input file was an RMS indexed file or a VSAM KSDS Section D 3 explains the VSAM cluster attribute defaults A VSAM RRDS will be created if the input file was an RMS relative file or a VSAM RRDS Section D 3 explains the VSAM cluster attribute defaults A VSAM ESDS will be created if the input file was an RMS sequential file or an IBM sequential file and the VSAM qualifier is added to the output VM filename Section D 3 explains the VSAM cluster attribute defaults e Physical sequential This includes CMS files MACLIB members and tape resident files If the input file is either a sequential file or a VSAM ESDS file and the NSAM qualifier is not specified a physical sequential
312. r ULTRIX you must enter the password keyvalue with the proper case e If you enter the INFILE keyword with access control information that includes a password the DTF command processor will ignore this keyword 9 10 Using the DTF for IBM Command Processor e f you do not specify a user ID either in the access control information or with the INUSER keyword the DTF command processor will ignore this keyword INRMT node server account name Specifies an OpenVMS DTF server node name and server account name or a DE Cnet I nternet Gateway node server account name A DECnet OpenVMS DTF server node or TCP IP host name and optional access control information If a DECnet Internet Gateway node is specified do not specify the access control information INUNIT unit specification Specifies a generic device name that describes the device type that contains the IBM input file unit specification The unit specification Length 1 to 8 characters Usage Notes e Ifthe input file is not cataloged you should specify this keyword e To avoid a catalog search to find the file you should specify this keyword e For VM systems if the input file is on tape you must indicate this by specifying a tape unit in this field You can specify the tape unit as TAPE T3420 or T3480 An IBM site can use additional or different unit names Check with the system programmer of the site where the input file resides to get the unit names in use at the
313. r processes e FTAM responder Receives an initiator s request for an association e DAP FTAM Gateway Allows any DECnet system to communicate with an OSI FTAM system e FTAM Configuration Allows you to configure the FTAM database See DECne OSI FTAM and VT Useand Management for more information on this component E 2 2 File Transfers Using FTAM Software and a DAP FTAM Gateway Figure E 1 shows an OSl initiated file transfer request and an BM initiated file transfer request Note All references to PUTTY in Figure E 1 are based on the premise that PUTTY is an OpenVMS system running an FTAM initiator FTAM File Support E 3 Figure E 1 File Transfers Using FTAM Software and a DAP FTAM Gateway IBM client system FTAM DTF for IBM software initiators responder OSI network SNA network OpenVMS FTAM responder DAP FTAM Gateway DTF server node DECnet network LKG 5578 93R E 4 FTAM File Support Callouts for Figure E 1 OSI Initiated File Transfer to the SNA Network 1 4 An OSI user on PUTTY issues the COPY command COPY APP FTAM LOG OSI SMOG DRAKE SNADTF IBM FILESPEC CAPE EXT to request the IBM file be copied to the OSI file CAPE EXT This request causes the FTAM initiator to request an association with a remote FTAM application defined by OSISFTAM In this example the association is to the node SMOG The remote FTAM application acts as the r
314. r you enter the DTFSEND command see Section 8 1 The Send to Remote panel prompts you for all the information you need to transfer a file from your system to a remote system You enter information on this panel in four categories The following pages describe each of the fields on this panel You can press PF3 to return to the Operation Selection panel without initiating the send operation Using the DTF for IBM Panel Interface 7 5 SEND this local file FILENAME This required field specifies the name of the file you wish to copy from your system OWNER M This field specifies the owner ID of the minidisk containing the local file This field is optional if you currently have the minidisk linked and accessed DEVICE ADDR M This field specifies the device address of the minidisk containing the local file This field is optional if you currently have the minidisk linked and accessed PASSWORD vM This value is the read password for the minidisk containing the local file This field is optional if you currently have the minidisk linked and accessed For more information on minidisk passwords see the MDxPASSWORD qualifier description in Section 2 3 3 OPTIONS There may be additional information about the local input file that you can specify To see the panel for entering this information type the letter Y in the OPTIONS field and press the ENTER key These panels are described
315. rameter Options CHECKPOINT Sets the number of logical records between checkpoints The number of logical records can be from 1 to 65535 Note If you do not specify a value for this option the TRANSFER DTF utility uses a default value of 1000 The CHECKPOINT option is valid only if you specify the RECOVERABLE option as YES If you specify the RECOVERABLE option as NO DTF does not permit you to enter a value in the CHECKPOINT option DENSITY The density of the tape containing the input file The value must be either 1600 or 6250 Using the DTF for IBM File Transfer Commands 8 3 DISP This option specifies the disposition of the new file You can choose one of the following three values 1 NEW 2 OLD 3 REP NEW creates a new output file If a file with the same name already exists DTF does not copy the file This is the default OLD creates a new output file that overlays an existing file of the same name If the file does not exist DTF issues an error message REP creates a new output file even if a file with the same name already exists LABEL The type of tape labels used on the input file s tape For MVS systems specify SL or AL For VM systems specify SL MDADDR The output file s 1 to 4 character hexadecimal minidisk address This option is valid only when transferring files toa VM system MDOWNER The output file s 1 to 8 character minidisk owner This option is valid only when transferring f
316. ransfer completes Typing Y lets you see this panel This panel is described in Section 7 14 BATCH SUB This field lets you use the Batch Options panel to specify job control information needed to create a batch job for the file transfer operation Optionally this job can be directly submitted after all panels have been completed Typing Y lets you see the Batch Options panel This panel is described in Section 7 15 7 14 Using the DTF for IBM Panel Interface 7 5 The Resume Previously Failed Transfer Panel Figure 7 4 Resume Previously Failed Transfer Panel Fill in the required fields and press ENTER to continue RESUME this transfer RETRY NUMBER gt WITH this remote node NODENAME gt USERID gt PASSWORD gt OPTIONS gt USING these options BATCH SUB gt LKG 8304 93R DTF displays the Resume Previously Failed Transfer panel see Figure 7 4 after you select the RESUME previously failed transfer menu option from the Operation Selection panel or after you enter the DTFRESUM command see Section 8 3 You can press PF3 to return to the Operation Selection panel without initiating the resume operation The following pages describe the fields on this panel Using the DTF for IBM Panel Interface 7 15 RESUME this transfer RETRY NUMBER The five digit number you see in message DTF 00621 when you submit the original request Note If your site uses TSO E or CMS the re
317. re then a record not found condition is raised B 2 1 6 Programming Considerations for VSAM Sequential Files The device type should be considered when accessing VSAM sequential files VSAM sequential files must reside on disk Note that non VSAM sequential files can reside on tape or disk B 2 2 Record Level Access to IBM Non VSAM Files Use these programming considerations when writing your own program for non VSAM sequential files File sharing You cannot share a file for output with another program Update support Update support is disallowed for IBM sequential files with the spanned record attribute Append You should not use sequential record access when appending records to an existing sequential file If you do multiple I Os will be required if sequential record access is performed when the IBM file has the blocked record format attribute B 3 Supported RMS Service Calls The following is a list of OpenVMS RMS service calls that are supported with DTF CLOSE CONNECT CREATE DELETE DISCONNECT DISPLAY ERASE FIND F REE RMS File System and Programming Constraints B 5 e GET e OPEN e PARSE e PUT e RELEASE e REWIND e SEARCH e UPDATE The rest of this chapter lists each supported RMS service alphabetically and describes which input and output file parameters require special consideration Note Any parameters that are not supported for DE Cnet operations are not supported by O
318. re are some restrictions for this file organization DTF supports only sequential files as input from RSX 11M M PLUS systems The Digital UNIX ULTRIX MS DOS and OS 2 operating systems can support only files that have a sequential organization DTF supports sequential files from these systems as input 3 1 2 Supported Record Formats DTF supports MVS and VM input files with fixed variable or variable spanned record formats DTF supports OpenVMS input files that have the following record formats e Fixed No restrictions Note OpenVMS fixed format records are converted to variable format records when transferred to VSAM sequential files e Variable No restrictions Variable with fixed control There are some restrictions Section 3 2 4 describes restrictions for output file record attributes e Stream DTF accepts input files with the OpenVMS stream stream LF or stream CR record formats However the output file will be created with variable format records with the carriage control attribute DTF supports RSX files that have the following record formats e Fixed No restrictions Note RSX fixed format records are converted to variable format records when transferred to VSAM sequential files 3 2 DTF Supported File Types e Variable No restrictions DTF supports Digital UNIX ULTRIX MS DOS and OS 2 input files in stream record format only this is the only format allowed by these op
319. record definition 2 27 F 1 Recoverable copy operations See also RECOVERY keyword introduction 1 7 RECOVER TRANSFER DTF qualifier 6 9 RECOVERY keyword 9 19 9 37 RELEASE 2 27 RELEASE RMS service call B 19 Remote backup and restore operations 10 5 REMOVE FILE_DEFINITION SNADTFCFG command C 8 REPLICATE file definition attribute 2 43 RESUME subcommand 9 30 canceling 9 31 CLIENT keyword 9 33 CLIENTPASS keyword 9 32 CLIENTUSER keyword 9 32 example 9 34 minimum entry 9 31 RESUME subcommand cont d RETNUM keyword 9 32 RETENTION_PERIOD n 2 27 RETNUM 9 46 RETNUM keyword 9 32 RETRY NUMBER entry field 7 16 Retry Request panel entry fields CLIENT USERID 7 16 NODENAME 7 16 PASSWORD 7 16 REUSE file definition attribute 2 43 REWIND RMS service call B 19 RFA 2 28 RMS file system constraints B 1 RMS service calls CLOSE B 7 CONNECT B 7 CREATE B 8 DELETE B 11 DISCONNECT B 11 DISPLAY B 12 ERASE B 14 extended attribute blocks B 3 FIND B 14 FREE B 14 GET B 15 introduction 1 8 OPEN B 16 PARSE B 19 programming restrictions B 2 PUT B 19 record locking B 3 RELEASE B 19 REWIND B 19 SEARCH B 20 supported 1 11 B 5 unsupported B 2 UPDATE B 20 when accessing non VSAM files B 5 when accessing VSAM indexed files B 4 when accessing VSAM relative files B 4 when accessing VSAM sequential files B 5 Index 9 RSX 11M M PLUS file specification format 2 6 S
320. red supported LABEL 236 ignored supported ignored MDADDRESS ignored ignored ignored MDMPASSWORD ignored ignored ignored MDRPASSWORD ignored ignored ignored MDWPASSWORD ignored ignored ignored MRS supported supported supported NULL supported supported ignored OWNERID ignored ignored ignored PASSWORD 2345 supported supported supported 1This qualifier is used when reading IBM input files for copy search compare and display operations 2This qualifier is used when writing over existing IBM output files 3This qualifier is used when creating a new IBM file 4This qualifier is used when deleting an IBM file 5This qualifier is used when listing an IBM directory 6This qualifier is used only for IBM tape resident files continued on next page DTF File Specifications 2 13 Table 2 2 Cont IBM File Specification Qualifiers and Their Usage for Remote MVS Files Non VSAM Disk Resident Tape Resident Qualifier Files Files VSAM Files RECORD_DEFINITION 4 supported supported supported RELEASE supported ignored ignored RETENTION_PERIOD supported supported supported RFA 23 ignored ignored supported SECONDARY_ALLOCATION supported ignored supported SECURITY_DATA 23 45 supported supported supported SEQUENCE_NUMBER 23 ignored supported ignored SINGLE supported supported ignored SMSDCLASS supported ignored supported SMSMCLASS supported ignored supported SMSSCLASS supported ignored supported SPANNED supp
321. restrictions e All OpenVMS files are created with the implied carriage control attribute unless the ANSI printer control attribute is assigned instead DTF does not support any RSX record attributes for output files Digital UNIX ULTRIX MS DOS OS 2 and VM disk resident files have no record attributes 3 3 File Transfer Considerations This section describes various additional considerations that you should be aware of when transferring files using DTF DTF Supported File Types 3 7 3 3 1 Transferring Files Between IBM Clients Files transferred between IBM clients always pass through an OpenVMS server node the IBM clients are not directly connected Be aware of the following when transferring files between two IBM clients IBM output files will use the default operating system attributes MVS Copy only one partitioned data set PDS member at a time No ISPF style statistics will be kept for the output file VSAM cluster component names will be generated for the output file 3 3 2 Transferring Files Between an IBM System and an Digital UNIX ULTRIX RSX 11M M PLUS MS DOS or OS 2 Client Be aware of the following when transferring files between an IBM system MVS or VM and an Digital UNIX ULTRIX RSX 11M M PLUS MS DOS or OS 2 client Do not copy VSAM Keyed Sequence Data Set KSDS or Relative Record Data Set RRDS files between an IBM system and one of these DECnet clients These DE Cnet clients have
322. returned OWNERID owner VM Specifies the 1 to 8 character minidisk owner as specified in the VM directory 2 26 DTF File Specifications Usage Note e The default is to use the IBM USERID qualifier provided or the IBM user ID provided by a proxy mechanism If the USERID qualifier is not specified then the OWNERID qualifier is required PASSWORD password Specifies a 1 to 8 character password for verifying access for a particular user ID through the appropriate IBM security system Usage Notes e The default is to supply no password e Do not specify this qualifier if the IBM site does not use a security system e The use of this qualifier depends on whether a proxy database is set up See Chapter 4 for more information RECORD_DEFINITION record definition Specifies a 1 to 32 character full dictionary path name of a record definition in the VAX Common Data Dictionary CDD that controls field level data translation during a DTF file transfer For more information about using the CDD product refer to the VAX Common Data Dictionary User s Guide For more information about data translation in OpenVMS DTF see Appendix F Usage Notes e The default is not to use a record definition e Ifthe TRANSLATE qualifier is also specified the table you specify with the TRANSLATE qualifier determines how text fields will be translated NO RELEASE mvs Specifies the release of any unused tracks after cre
323. rface The QUERY command results in a display similar to the following DT F DIF D DT DT DIF E F F DIF DIF DT DT E F DIF DIF DTF WORK UNITS DTF SERVICES NETMGR DTF3 LIENT SMAUG DIF SERVICES C NET PATH VTAM COUNTS VTAM COUNTS FILE ACCESS FILE COUNTS FILE COUNTS TY TY REQUEST DATA ACCESS 00039 RETRY NUMBER PE SEND DTF TEST PDS MEMBER PE READ PE RECV PE WRITE V V 3 1 0 TRANSFER DATA HO1AA073 ACCESS 00040 TOTAL 0000071 TOTAL 0000081 FILE DATA TOTAL 0000050 TOTAL 0000000 A SERVER SMAUG BYTE 0005480 BYTE 0001263 BYTE 0006160 BYTE 0000000 V 3 1 0 MBYTE 0000000 MBYTE 0000000 MBYTE 0000000 MBYTE 0000000 The message fields are explained in Appendix A of the Digital SNA Data Transfer Facility for OpenVMS Problem Solving and Messages manual Using the DTF for IBM Panel Interface 7 21 7 7 The Remote Node Options Panel Figure 7 7 Remote Node Options Panel Fill in the required fields and press ENTER to continue NODE NAME if more space is required EXTENDED NODE NAME gt SYNTAX of remote file names follows the rules of NODE TYPE gt ACCESS of remote node provided by this SERVER or GATEWAY NODENAME gt SERVER ACCOUNT gt SERVER PASSWORD gt LKG 8301 93R DTF displays the Remote Node Options panel see Figure 7
324. riables Set by DTF DTF sets the values of CLIST and CMS global variables by taking the appropriate values from the DEFINE subcommands that are in effect when a TRANSFER subcommand is processed These values are the key pieces of information that DTF requires to resume transfers that fail with a recoverable error DTF will set the variables under the following conditions e TSO E or CMS was used to invoke the DTF command processor e A TRANSFER subcommand was issued to initiate the transfer request e Thetransfer was executed in recoverable mode e The OpenVMS client node accepted the transfer request Under these conditions DTF will set the following variables RETNUM e CLIENT e CLIENTUSER e CLIENTPASS The following sections describe these variables RETNUM Contains a value that can later be used with the RESUME subcommand and the RETNUM keyword to restart the transfer from the last successful checkpoint before the transfer failed CLIENT Contains a value that can later be used with the RESUME subcommand and the CLIENT keyword to restart the transfer from the last successful checkpoint before the transfer failed Cleared for BM to 1BM transfers CLIENTUSER Contains a value that can later be used with the RESUME subcommand and the CLIENTUSER keyword to restart the transfer from the last successful checkpoint before the transfer failed Cleared for BM to IBM transfers 9 46 Using the DTF for IBM Command Processor
325. s 0 00 cece ee eens Supported Record Attributes 0 cee eee File Transfer Considerations 0 000 ccc eens Transferring Files Between IBM Clients I J ONNOAARKRWOWND H WWWWWWWAWAWWWW 3 3 2 Transferring Files Between an IBM System and an Digital UNIX ULTRIX RSX 11M M PLUS MS DOS or OS 2 Ghent e henaint adie te elie bastante dhe sb a a a Bae eet aed a 3 8 3 3 3 VSAM File Transfer Restrictions 00000 3 8 3 3 4 Printer File Transfer Restrictions 05 3 9 3 3 5 Transferring IBM Tape Resident Files 3 9 3 3 6 Transferring Files with Horizontal Tab Characters 3 10 3 3 7 Keyed Access to Sequential Files 0 3 10 4 Data Security 4 1 Local Data Security side chains Bow dads Beare ade b Belew adie os 4 1 4 2 Remote Data Security Without Proxy 0405 4 2 4 3 How to Specify an IBM User ID and Password 4 4 4 4 Wihatilis RFOXWe gt oaa SAO eas betes tie BAe a cake eee he ce S 4 4 4 4 1 Benefits of Using Proxy AccesS 00 0c eee eee 4 4 4 5 DECnet Initiated Proxy 0 0 c cece 4 5 4 6 IBM Initiated Proxy 0 0 es 4 7 4 6 1 Example of IBM Initiated Transfer Request 4 7 5 OpenVMS File Transfer Operations 5 1 Transferring Files Between OpenVMS DTF Clients and IBM DIF iCWents a r wt Al ce dranalia atin etna Dae Geeta oa a raa BA 5 1 5 2 APPEND Command iss sinaia
326. s You cannot delete IBM tape resident files Table 5 7 DTF Level of Support for DELETE Command Qualifiers For IBM File Qualifier Specifications Commenis BACKUP not supported IBM files do not have a BACKUP date BEFORE time supported BY_OWNER uic supported All BM resident files have a UIC of 0 0 If you specify the BY_OWNER qualifier with both OpenVMS and IBM file specifications with a UIC other than 0 0 this qualifier affects only the OpenVMS file specification INOJCONFIRM supported CREATED supported NO E RASE ignored 31f specified for an IBM input file specification no file will be selected 4See Section 5 10 1 for restrictions continued on next page 5 16 OpenVMS File Transfer Operations Table 5 7 Cont DTF Level of Support for DELETE Command Qualifiers For IBM File Qualifier Specifications Comments EXCLU DE filesped ignored P EXPIRED supported INO LOG supported MODIFIED supported SINCE time supported llf specified an IBM file specification the qualifier is ignored 4See Section 5 10 1 for restrictions Examples MVS DELETE MYFAIR DTFV200 _ NICK ACCOUNTS PAYABLE USER NICK This command deletes the PDS member PAYABLE of the NICK ACCOUNTS data set from the account under the user ID NICK The OpenVMS DTF server node is MYFAIR and the server account is DTFV200 MVS DELETE MYFAIR DTFV200
327. s of the output file e Records with no record attributes if the record format is fixed e Records with printer control if the record format is variable with fixed control VFC See Section 3 2 for additional information about printer control DTF does not support any RSX record attributes DTF Supported File Types 3 3 Digital UNIX ULTRIX MS DOS OS 2 and VM disk resident files do not have record attributes 3 2 Supported Output File Types This section describes considerations that you should be aware of before you use the interfaces to define output files as targets of DTF transfers These considerations include the following areas e File organizations e Record formats e Record lengths e Record attributes If a transfer operation results in the creation of an output file the attributes of the output file are assigned using the attributes of the input file 3 2 1 Supported File Organizations DTF supports the following MVS file organizations as output e WSAM This includes KSDS RRDS and ESDS organizations Section 3 3 3 describes the VSAM restrictions A VSAM KSDS will be created if the input file was an RMS indexed file or a VSAM KSDS Section D 3 explains the VSAM cluster attribute defaults A VSAM RRDS will be created if the input file was an RMS relative file or a VSAM RRDS Section D 3 explains the VSAM duster attribute defaults A VSAM ESDS will be created if the input file was an RMS sequential file or an IBM se
328. s on tape you must indicate this by specifying a tape unit in this field You can specify the tape unit as TAPE T3420 or T3480 An IBM site can use additional or different unit names Check with the system programmer of the site where the output file resides to get the unit names in use at the site VOLUME Specifies the 1 to 6 character volume serial number for the volume containing the output file VM This option is valid only for output files on tape VSAMDISK The 1 to 4 character minidisk address for the VSAM output file This option is valid only when issued on a VM system and only when the output file is on a VSAM minidisk Examples MVS DTFRECV LOGIN COM FROM SMITH AT MIAMI AS FRED LOGIN COM PASS ZEWOJUDE This example shows how to copy a file called LOGIN COM from a DECnet node named MIAMI to the local file FRED LOGIN COM on an MVS system The file on the DECnet node is accessed through the SMITH account using the password ZEWO UDE MVS DTFRECV TEXT LIS FROM JONES AT SMAUG AS JONES TEXT LIST PASS SECRET DISP NEW This example shows how to copy a file called TEXT LIS from a DECnet node named SMAUG to the local file J ONES TEXT LIST on the local MVS system The file on the DECnet node is accessed through the J ONES account using the password SECRET Using the DTF for IBM File Transfer Commands 8 11 VM DTFRECV MONDAY DAT FROM SIMPSON AT WMASS AS MONDAY DATA
329. s panel 7 30 Network File Options panel 7 38 Operation Selection panel 7 3 Post Processing Options panel 7 41 Receive from Remote panel 7 10 Remote Node Options panel 7 22 Resume Failed Transfer panel 7 15 Send to Remote panel 7 5 Transfer Execution panel 7 18 VM Input File Options panel 7 27 7 42 VM Output File Options panel 7 34 PARSE RMS service call B 19 Partitioned data set PDS DIRECTORY_BLOCKS qualifier 2 19 specifying member 2 1 Index 8 Queues canceling jobs 6 20 defining attributes 6 14 displaying characteristics of 6 19 displaying job status of entries 6 17 SNADTF QUEUE 6 14 specifying with TRANSFER DTF COPY command 6 9 R READ command OpenVMS DCL 5 28 Reading individual file records from OpenVMS DCL 5 28 Reading records from a file See Files reading records from RECALL subcommand 9 29 example 9 29 RECDEF keyword 9 19 Receive from Remote Panel POSTPROCESS 7 14 Record attributes supported for input files 3 3 supported for output files 3 7 Record formats supported for input files 3 2 supported for output files 3 5 Record lengths supported for input files 3 3 supported for output files 3 6 Record level access CLOSE command 5 8 introduction 1 8 OPEN command 5 27 READ command 5 28 restrictions for B 2 IBM non VSAM files B 5 VSAM files B 2 VSAM indexed files B 4 VSAM relative files B 4 VSAM sequential files B 5 WRITE command 5 35 RECORD_DEFINITION
330. s supported by DTF at any MS DOS or OS 2 node in a DECnet network so long as that node can access the OpenVMS DTF server node You simply include the OpenVMS DTF server node as part of the file specification No DTF software is required at the client node 12 1 Transferring Files Between MS DOS or OS 2 DTF Clients and IBM DTF Clients You can use the following DTF supported PATHWORKS for DOS and PATHWORKS for OS 2 NFT commands with an IBM file specification e APPEND appends a file to a file on an MS DOS OS 2 or IBM system e COPY transfers a file between an MS DOS or OS 2 DTF client and an IBM DTF client e DELETE deletes a data set on an IBM DTF dient e DIRECTORY lists data sets stored on an IBM DTF dient e SUBMIT submits a remote file for execution on an IBM DTF dient e TYPE displays the contents of a data set on an IBM DTF client MS DOS and OS 2 File Transfer Operations 12 1 12 2 APPEND Command To append the contents of one or more input files to the end of a specified output file use the NFT APPEND command APPEND switch input file spec output filespec Table 12 1 shows the level of support DTF provides for the NFT APPEND command switches For more detailed information about the APPEND command refer to the PATHWORKS for DOS DECnet User s Guide or PATHWORKS for OS 2 Utilities Guide manuals Note DTF does not support append operations to files with RECFM FBS The request will be rejected
331. s that do not specify the CATALOG qualifier DTF File Specifications 2 17 e If you use tape volumes for output you may want to use the NO option Check your IBM site for the recommended tape option e For SMS managed data sets this qualifier is ignored and the data sets are always cataloged CLASS class name VM Specifies the class name to use when submitting a batch job The class name is a single character A Z or 0 9 and must have already been defined by the system programmer Usage Note e If you do not specify a value DTF for IBM supplies the default specified at the IBM site DEFAULT Used to change your default entry in the OpenVMS DTF server s proxy database see Section 4 2 When the OpenVMS DTF server manager has created more than one entry for you in the OpenVMS DTF proxy database the manager designates one entry as your default entry This entry is used when you do not specify the USERID qualifier The DEFAULT qualifier is used to designate a new default entry in the proxy database different from the original default entry Usage Note e f you do not have an entry in the server s proxy database then this qualifier is ignored DENSITY density Specifies one of the following tape densities when reading or writing a file on tape e 800 e 1600 e 6250 Usage Notes e The default is to select the highest density allowed by the device for reading or writing files e This qualifier is i
332. sed by VSAM A INDEX_ is the index component name for A The value of the NAME attribute for the INDEX subsection of the BASE section is used here If this value is not specified then the default value is used by VSAM D 2 VSAM File Support Figure D 2 File Structure for VSAM Indexed Files A DATA A INDEX LKG 4262 93R Like RMS VSAM can support indexed files with multiple keys of reference You create multiple keys of reference for an IBM file by creating alternate indexes An alternate index is actually an indexed file unto itself that is it has data and index components So the file structure of an alternate index is identical to the one shown in Figure D 2 However in order to access a VSAM file through an alternate index a PATH association must be made between the alternate index and the VSAM indexed file that contains the data records Unlike RMS this association is not implicit Figure D 3 illustrates the file structure of a VSAM multikey indexed file where A KRF1 A KRF1 DATA A KRF 1L INDEX is the name of the first alternate key of reference and is specified by the value of NAME in the ALTERNATE_INDEX section or generated by DTF for IBM is the data component name for A KRF1 The value of the NAME attribute for the DATA subsection of the ALTERNATE_INDEX section is used here If this value is not specified then the default value is used by VSAM is the index component name for A KRF 1 The value of the NAME
333. sfer operations you can perform 3 1 Supported Input File Types This section describes considerations that you should be aware of before you use the interfaces to define input files to be transferred These considerations include the following areas File organizations Record formats Record lengths Record attributes 3 1 1 Supported File Organizations DTF supports the following MVS file organizations as input VSAM This group of files includes Key Sequenced Data Set KSDS Relative Record Data Set RRDS and Entry Sequenced Data Set ESDS file organizations There are restrictions on VSAM file transfers Section 3 3 3 explains these restrictions Physical Sequential This group of files includes sequential files members of a partitioned data set PDS generation data group GDG files and tape resident files DTF supports the following VM file organizations as input VSAM This group of files includes Key Sequenced Data Set KSDS Relative Record Data Set RRDS and Entry Sequenced Data Set ESDS file organizations There are restrictions on VSAM file transfers Section 3 3 3 explains these restrictions DTF Supported File Types 3 1 e Physical Sequential This group of files includes CMS files MACLIB members and tape resident files DTF supports the following OpenVMS file types as input e Sequential No restrictions e Relative There are some restrictions for this file organization e Inmdexed The
334. slation Tables If you need information about modifying translation tables refer to the VMS SNA Managenent Guide DTF uses translation tables located on the OpenVMS DTF server node to convert EBCDIC characters received from IBM to DMCS characters used by Digital and from DMCS to EBCDIC EBCDIC is a standard convention used by IBM and DMCS is a superset of the standard American Standard Code for Information Interchange ASCII character set Note The file name you specify with the translation qualifier or option must reside on the OpenVMS DTF server node By default DTF looks for the file in SYS LIBRARY with a default extension of TBL F 4 Field Level Translation The following sections describe the steps necessary to create and use a field level translation table F 4 1 Creating a New Record Definition To create a new record definition you must do one of the following e Use the CDD DEFINE RECORD command e Create a common data definition language CDDL file After you create the CDDL file you must add the record definition to the data dictionary by running the CDDL compiler In either case the record definition should describe the contents of the file You can then use the path name of the entry in the data dictionary as the value for the RECORD_DEFINITION qualifier Refer to the Common Data Dictionary Data Definition Language Reference for more detailed information about creating new record definitions DTF Data Tra
335. specification when deleting IBM files RSX 11M M PLUS File Transfer Operations 11 9 Table 11 5 DTF Level of Support for DELETE Command Qualifying Switches For IBM File DCL DELETE Qualifier NFT Switch FTS Switch Specifications Command Qualifiers LOG LO filespec LO filespec supported NOWARNINGS NM l supported 10peration not available Examples MVS DELETE MYFAIR DTFMVS NICK ACCOUNTS PAYABLE USER NICK This command deletes the PDS member PAYABLE of the NICK ACCOUNTS data set from the account under the user ID NICK The OpenVMS DTF server node is MYFAIR and the server account is DTFMVS Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers MVS DELETE MYFAIR DTFV200 NICK DTF USER NICK This command deletes all the data sets beginning with NICK DTF Caution is recommended when using wild cards The OpenVMS DTF server node is MYFAIR and the server account is DTFV200 Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers VM DELETE LOG PARIS DTFVM ASHFLD 1 USER ROBERT Files deleted PARIS DIFVM ASHFLD C 1 USER ROBERT PARIS DTFVM ASHFLD M 1 USER ROBERT PARIS DTFVM ASHFLD Z 1 USER ROBERT This command deletes all files named ASHFLD with mo
336. splayed as 0 0 e Creation date Always displayed as none _specified gt e Expiration date Always displayed as none _ specified gt e File protection Always indicates that system owner group and world do not have access Access is really determined by the access control information user name and password specified in the IBM file specification MVS If a file is uncataloged the IBM file specification qualifier VOLUME is required with the DIRECTORY command This qualifier indicates the volumes on which the files reside on the IBM system If VOLUME is not specified then an MVS catalog search will be performed RSX 11M M PLUS File Transfer Operations 11 13 11 7 SUBMIT REMOTE Command To submit selected files for remote execution on IBM DTF cients use the DCL SUBMIT REMOTE command SUBMIT REMOTE filespeqd the standard NFT command with the SB or EX switch output file spec switches input file spec switches SB EX or the standard FTS command with the SB or EX switch output file spec switches input file spec switches SB EX See Chapter 2 for the IBM file specification syntax Table 11 7 shows the level of support DTF provides for the SUBMIT REMOTE command qualifying switches of the various file transfer interfaces For more detailed information about the SUBMIT REMOTE commands refer to the DECne amp RSX Guide to User Utilities Note Files submitted to IBM batch subsystems must n
337. st specify NORECOVER for VSAM files RETRIES n Specifies the number of times that DTF attempts to resume a file transfer operation after an initial failure This qualifier is not supported for VSAM file transfers OpenVMS TRANSFER DTF File Transfer Operations 6 9 The value for n cannot exceed the queue maximum retries value set by the system manager You can use the TRANSFER DTF SHOW QUEUE FULL command to determine what this value is If the value you set with the RETRIES qualifier is greater than the queue maximum you get an error message and the system maximum retries value is used in its place If you do not specify a value with the RETRIES qualifier then the queue default retries value is used You can use the SHOW QUEUE FULL command to determine what this value is You cannot use the RETRIES qualifier with the NOQUEUE qualifier SINCE time Specifies files dated after a specified time You can specify an absolute time or a combination of absolute and delta times Refer to the OpenVMS General User s Manual or the on line help topic SPECIFY DATE_TIME for more complete information about setting time values See also the TODAY TOMORROW and YESTERDAY keywords If you do not specify a time SINCE TODAY is the default qualifier TIME time Specifies the duration of a file transfer operation before it is aborted If the assigned time is exceeded during a copy operation the job continues and is not aborted If the copy operat
338. t Fields CONNECT RAB Input Fields 00000 e eee CREATE FAB Input Fields 000 c ee eee CREATE XAB Output Fields 0 0 c eee DELETE RAB Input Fields 0 000 c eee DISPLAY NAM Input Fields 000 c eee DISPLAY FAB and XAB Output Fields 6 1 6 4 6 5 10 2 10 4 10 6 11 1 11 2 11 14 11 16 11 18 12 2 12 4 12 6 12 8 12 9 12 11 12 12 B 7 B 7 B 8 B 9 B 11 B 12 B 12 xiii xiv B 8 B 9 B 10 B 11 B 12 B 13 B 14 E 1 E 2 E 3 Ft F 2 F 3 FIND RAB Input FieldS 0 0 0 GET RAB Input FieldS 0 0 ees OPEN FAB Input Fields 0 0 e eee ees OPEN XAB Output FieldS 0 0 ccc eee ees PUT RAB Input Fields naana 0 0 ees RELEASE RAB Input Fields 0 00 eens UPDATE RAB Input and Output Fields FTAM User Facilities Supported by DTF Software Restrictions heard Kea his ds bee Ae whe owas ae wedged DTF Support and Mapping Among FTAM OpenVMS and IBM MVS and VM File Attributes Correspondence of CDD Data Types and IBM Data Types Limitations on Data Transferred from Digital tolIBM Limitations on Data Transferred from IBM to Digital Correspondence Between OpenVMS DTF Qualifiers DTF for IBM Command Processor Keywords and DTF ISPF Entry PIGS aie Batak Bacar Rule Dis Basen ek eae as B 14 B 1
339. t should be submitted to the remote node s batch subsystem after the transfer completes Typing Y lets you see this panel This panel is described in Section 7 14 BATCH SUB This field lets you use the Batch Options panel to specify job control information needed to create a batch job for the file transfer operation Optionally this job can be directly submitted after all panels have been completed Typing Y lets you see the Batch Options panel This panel is described in Section 7 15 Using the DTF for IBM Panel Interface 7 9 7 4 The Receive from Remote Panel Figure 7 3 Receive from Remote Panel COMMAND gt RECEIVE this remote file FILENAME gt OPTIONS gt FROM this USER at this remote NODE NODENAME gt USERID gt PASSWORD gt OPTIONS gt Y N STORE on your local system AS this file name FILENAME DISP OWNER OPTIONS USING these options RECOVERABLE gt TRANSLATE gt POSTPROCESS gt NEW OLD REP DEVICE ADDR gt PASSWORD gt Y N Y N CHECKPOINT Y N EXTENDED Y N LKG 8305 93R DTF displays the Receive from Remote panel Figure 7 3 shows the VM version after you select the RECEIVE file from remote system menu option from the Operation Selection panel or after you enter the DTFRECV command see Section 8 2 The Receive from Remote panel prompts you for all of the information needed to transfer a file from a remote system to your system
340. tal UNIX or ULTRIX use case sensitive file names Make sure that you use the proper case when the input file resides on an Digitial UNIX or ULTRIX systems e The node portion of the DE Cnet file specification can contain access control information However for security reasons this is not recommended because the password you enter is visible A better way to enter access control information is by using the INUSER keyword and having the system prompt you for the INPASS in a nondisplay field e If you specify an IBM file specification you can include IBM file specification qualifiers by enclosing the entire file specification within single quotation marks Appendix G lists the qualifiers that you can use 1600 INDEN 6250 Specifies the density of the tape volume from which the input file is read 1600 1600 bits per inch bpi 6250 6250 bits per inch bpi Usage Notes e Tape restrictions may apply Section 9 4 1 describes these restrictions e If you do not specify a keyword value and the input file is on tape the DTF command processor will select the highest density allowed for that tape volume 9 8 Using the DTF for IBM Command Processor e Ifthe input file is neither on tape nor an IBM file specification the DTF command processor will ignore this parameter INFDEF file specification Specifies reading a file definition record in the OpenVMS DTF server s file definition database For a complete discussi
341. ted BUFFER_COUNT supported BY_OWNER uic supported COMMENT sstring supported COMPARE supported CONFIRM supported CREATED supported INOJCRC supported DELETE supported DENSITY supported EXCLUDE filesped supported EXPIRED supported FAST supported FULL supported GROUP_SIZE n supported NO IGN ORE option supported IMAGE supported INCREMENTAL supported JINOJINITIALIZE supported INOJINTERCHANGE supported OURNAL filespec supported LABEL string ignored LIST filespec supported INO LOG supported continued on next page 5 6 OpenVMS File Transfer Operations Table 5 2 Cont DTF Level of Support for BACKUP Command Qualifiers For IBM File Qualifier Specifications MODIFIED supported NEW_VERSION supported NOJOVERLAY supported PHYSICAL not supported PROTECTION code ignored RECORD supported INOJREPLACE supported INOJREWIND supported SAVE_SET supported SELECT filespec supported SINCE time supported TAPE_EXPIRATION date ignored INOJTRUNCATE ignored INO VERIFY not supported NOLUME n not supported 1Command fails with the following error message RMS F SUPPORT Network operation not supported FAL F FOP1 File processing options field rejected Examples MVS BACKUP IMAGE IGNORE INTERLOCK USER 100 _ DTIFSVR VAXBACKUPS DTFMAN BACKUP USER DTFMAN UNIT TAPE NOTRANS SAVE The command backs up the OpenVMS disk USER 100 to the MVS tape
342. ted TRANSFER_MODE AX supported AUTO TRANSFER_MODE _ BK supported BLOCK TRANSFER_MODE RC supported RECORD NOWARNINGS NM supported tOperation not available Note When jobs are submitted to IBM batch subsystems the file records must not exceed 80 bytes The file will be deleted from the IBM system after the job completes RSX 11M M PLUS File Transfer Operations 11 5 Examples MVS SCOPY SNPY DTF COMICS SUNDAY GAR USER SMITH PASS CHUCKLES CAT TXT This command copies the PDS member GAR of the COMICS SUNDAY data set located on the IBM system under the MVS user ID SMITH to the CAT TXT file located in the current RSX directory The OpenVMS DTF server node is SNPY and the server account is DTF MVS FTS gt SAMPLE MVS HORSES SNADTF LIBBY SAMPLE USER LIBBY PASS GOBBLED This command copies the file LIBBY SAMPLE on the MVS system to the file SAMPLE MVS file located in the current RSX directory The MVS user ID is LIBBY and the password is GOBBLED The OpenVMS DTF server node is HORSES and the server account is SNADTF VM SCOPY CHESS DTFVM PAWN EXEC USER ROOK PASS BISHOP KNIGHT TXT This command copies the file PAWN EXEC to the local file KNIGHT TXT The server account is DTF VM the OpenVMS DTF server node is CHESS the VM user ID is ROOK and the VM password is BISHOP VM SCOPY MAPLE TXT BOSTON DTFVM TREES MACLIB MAPLE USER HARR
343. the amount of space currently in use as it should These numbers are only approximations of the number of 512 byte blocks in a file These numbers are always 0 for partitioned data set PDS members Owner Always displayed as 0 0 Creation date See Section 5 10 1 Revision date See Section 5 10 1 Expiration date See Section 5 10 1 Backup date Always displayed as lt No backup done gt File attributes Extend Always displayed as 0 Global buffer count Always displayed as 0 OpenVMS File Transfer Operations 5 23 5 10 1 Version limit Always displayed as 0 Journaling enabled Always displayed as None e File protection Always indicates that system owner group and world do not have access Access is really determined by the access control information user name and password specified in the IBM file specification e Access control list Always displayed as None MVS If a file is uncataloged the IBM file specification qualifier VOLUME is required with the DIRECTORY command This qualifier indicates the volumes on which the files reside on the IBM system If WOLUME is not specified then an MVS catalog search will be performed Date and Time Restrictions for Created Revised and Expires Fields The DTF for IBM software returns date and time information to the DE Cnet system for the following file types VM e CMS files Date and time will be returned to the revised
344. the DTF subcommands are in separate records File 2 is not acceptable Record 1 contains both the DTF command and a DTF subcommand File 3 is not acceptable Although Record 1 contains the DTF command it is followed by a TSO command The TSO command must be either in a record that precedes the record containing the DTF command or in a record that follows the record containing the DTF END subcommand Using the DTF for IBM Command Processor 9 41 Example 9 1 Sample REXX EXEC to Perform Post Processing DTF for VM Batch Job with post processing Queue Queue Queue Queue Queue Queue Queue def netmgr dtf4 server boston def infile payroll data a def outfile boston a a def outuser smith outpass secret def recovery y transfer post post com end re dtf batc return rc This is an example REXX EXEC that shows how the post processing feature may be used The local file PAYROLL DATA on the user s A disk is being transferred to the renote OpenVMS node named BOSTON When the transfer completes successfully the DCL command procedure named POST COM will be submitted on the remote node Example 9 2 Sample JCL to Perform a Post Processing Function DTFT STEP DTFU SYST SYSL SYSH SYST DTF St DEF DEF R DEF I DEF O LIST TRANS END Li Li C ESTB JOB 1 DIFTEST CLASS A MSGCLASS X EXEC PGM IKJEFTO1
345. the file vmlogin com on the ULTRIX system to the file login exec on the VM system The OpenVMS DTF server node is dtfsrv and the server account is spot The two slashes indicate that no password prompt will be generated The VM user ID is richards and the user password is guessit Note the use of the S option This causes the file to be submitted to the VM batch machine for execution after the file is dosed Note that the file login exec should not contain any records exceeding 80 bytes After the file is executed it will be deleted from the VM system 10 4 Remote Backup and Restore Operations To backup and restore files on an IBM DTF client system use the DECnet ULTRIX or DECnet OSI for Digital UNIX dcp i command dcp i option file spec Examples MVS dls 1 veena dtfmvs gary dtf file tar cvf filenames dcp i boston SNADTF dtftest tar notrans dcp i boston SNADTF dtftest tar notrans tar tf These examples show how to back up and restore ULTRIX or UNIX files on IBM disks If you would like to do a backup on IBM tape devices use the appropriate UNIT and VOLUME qualifiers in the IBM file specification The examples show how to pipe the output from tar to dcp which routes the transfer to DTF for IBM systems Similarly using dcp you can pipe the output to tar which can display or restore files archived using tar Note that you must use the NOTRANSLATE qualifier in the IBM file specificat
346. the revision file is in the same location same node and access information Therefore you should fully specify each file when comparing a file on a DECnet system to a file on an IBM system Table 5 8 shows the level of support DTF provides for the DCL DIFFERENCES command qualifiers For more detailed information about the DIFFERENCES command refer to the DCL Dictionary Table 5 8 DTF Level of Support for DIFFERENCES Command Qualifiers For IBM File Qualifier Specifications CHANGE_BAR formatt supported COMMENT_DELIMITER supported deimiter IGNORE S option supported MATCH size supported MAXIMUM_DIFFERENCES supported f MERGED n supported MODE Sradix supported NO NU MBER supported OUTPUT filespec supported PARALLEL n supported continued on next page 5 18 OpenVMS File Transfer Operations Table 5 8 Cont DTF Level of Support for DIFFERENCES Command Qualifiers For IBM File Qualifier Specifications SEPARATE D input supported fild SLP supported WIDTH n supported WINDOWssize supported Examples MVS DIFF MYFAIR DTFMVS_PROD _ LOU STATUS REPORT USER LOU PASS SECRET _ MYVAX LOU PASSWORD56 STATUS TXT This command displays any differences between the PDS member REPORT of the LOU STATUS data set located on the IBM DTF client and the STATUS TXT file located in the default OpenVMS directory for the OpenVMS account LO
347. the tape unit as TAPE T3420 or T3480 An IBM site can use additional or different unit names Check with the system programmer of the site where the input file resides to get the unit names in use at the site VOLUME Specifies the 1 to 6 character volume serial number for the volume containing the input file MVS If the input file you are trying to copy is not cataloged or you want to avoid a catalog search to find the file you should specify both the volume name and the unit name VM This option is valid only for input files on tape VSAMDISK The 1 to 4 character minidisk address for the input file This option is valid only when the VSAM input file is on a minidisk Examples MVS DTFSEND GIBSON TESTS TEST5 TO JONES AT BOSTON AS TEST DAT This example shows how to copy the PDS member called TEST5 in the PDS GIBSON TESTS on the local MVS system to a user named J ONES at node BOSTON on a DECnet network The new filename on the DECnet node is TEST DAT 8 6 Using the DTF for IBM File Transfer Commands MVS DTFSEND JONES TESTFILE TO RICHARDS AT BOSTON AS TEST DAT PASS SECRET This example shows how to copy the file ONES TESTFILE from the local MVS system to a user named RICHARDS on node BOSTON on a DECnet network The new filename on the DECnet node is TEST DAT The password for user RICHARDS on the DECnet node is SECRET VM DTFSEND TEST DSDS VSAM
348. their preferred interface Introducing the Data Transfer Facility DTF Product 1 7 1 3 7 RMS Programming Interface OpenVMS Clients Only You can use the standard Record Management Services RMS programming interface transparently with DTF to access data sets on an IBM client from an OpenVMS client Refer to Appendix B for a detailed description of the RMS programming interface and restrictions associated with DTF 1 3 8 DCL Record Level Access and DATATRIEVE Access OpenVMS Clients Only The DTF software allows you to perform DCL initiated record level access to VSAM and non VSAM files VSAM file types supported are sequential files relative files and indexed files including multikey VSAM files Refer to Chapter 5 for more information DTF supports the use of DATATRIEVE operations on IBM files 1 4 What Does the DTF Product Allow Me to Do DTF allows you to transfer and manipulate files on Digital and IBM clients using the commands and programming calls listed in the sections that follow 1 4 1 OpenVMS DCL Commands e APPEND append one file to another e BACKUP archive and restore a file or set of files e CLOSE dose a file e CONVERT convert and merge files e COPY copy a file to another file e CREATE create a new file e DELETE delete an existing file e DIFFERENCES show the differences between two files e DIRECTORY show a listing of files e EXCHANGE NETWORK copy a file using block or record mode tr
349. ting System Length of User ID Length of Password Case Sensitivity OpenVMS MS DOS and OS 2 Digital UNIX and ULTRIX RSX 11M M PLUS MVS VM 1 12 characters 1 40 characters 1 8 characters 1 14 characters 1 8 characters 1 8 characters 1 39 characters 1 10 characters 1 8 characters 1 39 characters 1 8 characters 1 8 characters Not case sensitive Not case sensitive Case sensitive Not case sensitive Not case sensitive Not case sensitive 4 2 Data Security Table 4 2 shows the information the user supplies in a transfer request to a remote system for a specific file type Table 4 2 Access to Remote Systems Without Proxy Remote System What You Supply Security System VM User ID password and Validates that the access information matches system minidisk password and links to the minidisk using the password you supplied in the transfer request MVS User ID and password Validates access before performing the transfer system DECnet 1D and password Validates access before performing the transfer node Data Security 4 3 4 3 How to Specify an IBM User ID and Password IBM users can specify a user ID and password on the command line for BM to IBM or DECnet to IBM requests The USERID and PASSWORD qualifiers are used to verify access for a particular user ID through the appropriate IBM security system If you do not know the password or if you do not have privileges for a particular user
350. to 255 plus header if the file does not have an MRS value If the file has records more than 255 bytes then the transfer will fail with invalid record size To correct this problem convert the file and insert MRS in to the file using the CONVERT FDL command The maximum record size MRS value or the Longest Record Length LRL value if MRS is not sent is used to determine what record size th file should be created with when a OpenVMS file is sent to the IBM system If this value is a good indication of the average record size in the file then the allocation quantity that DTF for MVS calculates will be quite good This is because it is a close approximation to how many records are in the file based on the number of 512 byte blocks RMS has told DTF for MVS to allocate and the record size chosen for the output file If the MRS or LRL is a bad indication of the average record size consider using the ALLOCATION qualifier with the correct value Examples MVS Specifying maximum record size for file with records longer than 255 The file X X is variable length with the longest record equal to 350 bytes and the MRS set to 0 COPY X X O SNADTF file x MRS 350 DTF File Specifications 2 25 NULL option Specifies the action to take when a null record is to be written to an IBM file You can choose from the following options value SPACE IGNORE NONE VM NONE MVS REJECT U sage Notes
351. to be the OpenVMS DTF server node The server node performs data translation if required and transfers the data between DTF clients The OpenVMS DTF server software includes the OpenVMS DTF utilities software so you must not install both kits on the server node An OpenVMS DTF server can serve a large number of clients e OpenVMS DTF utilities software The OpenVMS DTF utilities software kit is optional software that can be installed on additional OpenVMS nodes chosen to be DTF client nodes The client nodes communicate with the OpenVMS DTF server node The OpenVMS DTF utilities software includes the following two utilities The TRANSFER DTF utility Allows you to recover and continue transferring files after a communications failure The SNADTFCFG utility Allows a server manager to configure the OpenVMS DTF server and create file definitions that are used to create IBM files This utility also lets a server manager monitor and control several databases on the OpenVMS DTF server node 1 2 Introducing the Data Transfer Facility DTF Product All IBM clients are required to have DTF for IBM software installed The BM resident software is packaged in two software installation kits one kit for MVS systems and one kit for VM systems The IBM software takes requests from IBM users and forwards those requests to the OpenVMS DTF server The software also handles transfer requests from the OpenVMS DTF server The BM resident software inc
352. tput File Options panel see Figure 7 10 if you type Y in the OPTIONS field for an MVS output file in the Send to Remote or Receive from Remote panel You can press PF3 to return to the operation panel that invoked this panel without initiating the operation The following pages describe the fields on this panel FILE options MIXED CASE NAME This field specifies whether DTF should accept the case in which the file name was entered A value of Y will cause DTF to open the file in a case sensitive fashion N or blank will default to uppercase 7 30 Using the DTF for IBM Panel Interface Note This option has no effect unless NODE PARMS LOWERCASECREATE is set to ON See the CASE qualifier in Chapter 2 for information on MIXED CASE VOLUME SERIAL Specifies the volume serial number that will contain the output file UNIT Specifies a generic device name that describes the device type that holds the IBM output file Length 1 to 8 characters CATALOG The MVS system which creates the output file provides the default for this Type the letter N in this field if you do not want to catalog this file See the description of the CATALOG qualifier in Chapter 2 for more information about cataloging files NULL RECORDS This keyword indicates how DTF handles null records length 0 in an IBM environment Since the CMS file system does not support null length records DTF cannot write them to the indicated d
353. try number is automatically set whenever a transfer request executes with the RECOVERABLE COPY option set to YES WITH this remote node NODENAME Specifies the name of the client node that processed the original transfer request e If your site uses ISPF this is automatically set whenever a transfer request has failed with a recoverable error and the RECOVERABLE option was set to YES e Donot make an entry in the NODENAME field if the original transfer request involved two IBM files USERID Specifies the user ID specified for the DECnet file involved in the original transfer request e If your site uses ISPF this is automatically set whenever a transfer request has failed with a recoverable error and the RECOVERABLE option set to YES e Donot make an entry in the USERID field in the following situations Ifthe original transfer request involved two IBM files Ifthe original transfer request involved a DECnet file that had no user ID associated with it PASSWORD Specifies the password associated with the DE Cnet file involved in the original transfer request 7 16 Using the DTF for IBM Panel Interface e If your site uses ISPF this is automatically set whenever a transfer request has failed with a recoverable error and the RECOVERABLE option set to YES However the value is not retained if the current ISPF dialog ends e Donot make an entry in the PASSWORD field in the following situations Ifthe original r
354. u must now enter data you cannot create empty VM files and then press CTRL Z to exit The OpenVMS DTF server node is DTFSRV the server account is VMDTF the VM account is GARY and the VM password is GUESSME 11 8 RSX 11M M PLUS File Transfer Operations 11 5 DELETE Command To delete a file on an IBM DTF client use the DCL DELETE commana DELETE filespec the NFT command with the DE switch input file spec switches DE or the FTS command with the DE switch output file spec jinput file spec switches DE See Chapter 2 for the IBM file specification syntax Table 11 5 shows the level of support DTF provides for the DELETE command qualifying switches of the various file transfer interfaces For more detailed information about the DELETE commands refer to the DE Cn amp RSX Guide to User Utilities You can use FTS to move a file that is copy the file to another system and then delete the original To move a file specify both a source and a destination along with the DE switch for instance A B DE copies file B to file A and then deletes B Notes If you attempt to delete an MVS file that was created with an expiration date and that expiration date has not been reached MVS will prompt the MVS console operator for permission to delete the file The file operation will wait until the console operator replies You cannot delete IBM tape resident files You cannot use wildcard characters in an IBM file
355. ualifier determines how data is translated in text fields e The translation table must be stored on the OpenVMS DTF server node and must be accessible to all DTF server accounts Digital recommends storing the translation table in SYS LIBRARY e If you specify TRANSLATE translation is performed by either OpenVMS DTF or by DTF for IBM The translation location depends on information in your OpenVMS DTF server account e The file name used with the TRANSLATE qualifier must be a fully specified file name UNIT unit spec MVS Specifies a unit from 1 to 8 alphanumeric characters long to classify devices for creating a data set or creating an uncataloged data set DTF File Specifications 2 31 Usage Note e If you do not specify a value DTF for IBM supplies the default specified at the IBM site UNIT unit spec VM Specifies one of the following unit types for tape resident files e TAPE allows the operator to select the appropriate tape unit e 13420 specifies that a 3420 type open reel tape unit be used e 13480 specifies that a 3480 type cartridge tape unit be used Usage Notes e This parameter is required for all tape accesses and must not be used for any other accesses e An IBM site can specify additional or different unit names during DTF for IBM installation Check with the IBM system programmer to get the unit names in use at the site you will be accessing USERID userid Specifies a
356. ue end re dtf batc end return rc This is an example of REXX EXEC that demonstrates how a failed recoverable transfer may be resumed Usage Notes e Ifthe transfer fails with a recoverable error the retry number client node user and password are all stored using CMS s GLOBALYV facility Using the DTF for IBM Command Processor 9 43 The return code from the transfer may be interrogated to determine if the transfer failed and if it may be recovered SYSTSIN File The example shows a set of DTF subcommands used to copy an IBM file to two different OpenVMS client nodes The DEFINE subcommands are written with continuation characters and comments to make the procedure more readable 9 6 2 Notes and Restrictions for DTF Batch Mode Operations The following restrictions apply when DTF is used in batch mode Multiple error messages returned Whenever possible DTF continues processing subcommands even after an error occurs If multiple errors occur the return code passed back to TSO indicates the most severe error that has occurred Information missing from TRANSFER and RESUME subcommands If a TRANSFER or RESUME subcommand is rejected because that subcommand is missing parameters return code 4 DTF ceases operations in batch mode and immediately returns to TSO TSO then processes any remaining records within the SYSTSIN file If these records contain DTF subcommands TSO issues an error message for each record an
357. ult time of 23 hours for the default DTF queue named SNADTF QUEUE 6 16 OpenVMS TRANSFER DTF File Transfer Operations 6 5 Displaying the Status of File Transfer Jobs To display the status of all your jobs or a single job identified by a job name use the TRANSFER DTF SHOW J OBS command SHOW J OBS job name qualifiers J ob names for a file transfer operation are specified with the NAME qualifier on the TRANSFER DTF COPY command By default the status of all your jobs is displayed To display a complete listing of other users jobs with the FULL qualifier you must have group or world privileges For information about protection privileges refer to the DCL Dictionary Each job displayed with the SHOW J OBS command is listed as being in one of the following four states QUEUED A job has not yet started copying This state occurs when the AFTER qualifier is specified with the COPY command or if another job is already executing on the DTF queue INITIALIZING A job has started parsing the input and output files but has not yet started copying This state can last for some time before copying begins If the job stops at any time the status automatically changes to PAUSED ACTIVE A job is currently running and copying is in progress PAUSED A job has stopped running because a file transfer operation failed and the job is awaiting retry Command Parameter job name Specifies the name of the job whose status you want to dis
358. upper or lower case in the entire IBM file specification 2 3 1 Qualifier Defaults Most IBM file specification qualifiers have a default value You select the default value by omitting the IBM file specification qualifier The default value is always controlled by the DTF for IBM software on the remote client In many cases the default value can be defined when installing the DTF for IBM software Refer to the Digital SNA Data Transfer Facility Installation MVS and Digital SNA Data Transfer Facility Installation VM manuals for more information on assigning default values at DTF for IBM installation time Depending on whether the default value can be changed the default value for an IBM file specification qualifier is determined by one of the following two rules e The default value of the qualifier cannot be changed The qualifier s default is documented in the description of the qualifier e The default value of the qualifier can be changed when DTF for IBM is installed You should contact your IBM site for the most current value of the qualifier s default DTF File Specifications 2 9 2 3 2 Qualifier Restrictions When Accessing Remote VM and MVS Clients Table 2 1 lists the DTF for IBM qualifiers and the types of VM files each qualifier can be used for CMS files tape resident files and VSAM files Each qualifier is described in greater detail in Section 2 3 3 Table 2 2 lists the DTF for IBM qualifiers and the types of M
359. upported BLOCK supported CC gt xx supported DELETE not supported FIXED supported IMAGE supported LSA not supported MACY 11 not supported MRS nnn supported NOCONVERT not supported NOLOG supported NOSPAN supported PRINT not supported STREAM ignored SUBMIT supported UNDEFINED not supported VARIABLE supported VFC nnn not supported Examples MVS C NFT FT gt COPY FILE1 DAT RABBIT DTFMVS WHITE DTF TALL 12 4 MS DOS and OS 2 File Transfer Operations This command transfers the local file FILE1 DAT to the member TALL of the PDS called WHITE DTF located on the IBM system The OpenVMS DTF server node is RABBIT and the server account is DTFMVS Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers MVS C NET FT gt COPY RABBIT DTFMVS WHITE DTF SMALL FILE2 DAT This command copies the member SMALL of the data set WHITE DTF located on the IBM system to the local file FILE2 DAT The OpenVMS DTF server node is RABBIT and the server account is DTFMVS Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers VM C NFT FT gt COPY FILE1 DAT PARIS DTFVM VMSFILE DAT USER DTFMAN PASS CURIOUS This command copies the local file FILE1 DAT to the file VMSFILE DAT on the IBM system The
360. upports the following DE Cnet clients OpenVMS ULTRIX Digital UNIX RSX 11M M PLUS MS DOS OS 2 Note You can use TCP IP between the OpenVMS DTF server node and the Digital SNA Domain Gateway or Digital SNA Peer Server Introducing the Data Transfer Facility DTF Product 1 1 The purpose of DTF is to extend the DECnet file transfer facilities to the IBM MVS and VM environments therefore the DTF software does not support file transfers between two DECnet clients You should use the DE Cnet file transfer utilities for this purpose On OpenVMS clients DTF supports the DCL interface the TRANSFER DTF utility supplied with OpenVMS DTF the RMS programming interface and the VAX DATATRIEVE product On RSX 11M M PLUS clients DTF supports the DCL interface and the DECnet file transfer commands On ULTRIX Digital UNIX MS DOS and OS 2 clients DTF supports the DE Cnet file transfer commands On IBM clients DTF supports a menu driven panel interface a basic set of file transfer commands and the more robust DTF command processor 1 2 What Are the Components of the DTF Product The DTF access routine requires two major pieces of software the Digital resident software OpenVMS DTF and the BM resident software DTF for IBM The OpenVMS DTF software is packaged into the following two software installation kits e OpenVMS DTF server software The OpenVMS DTF server software kit is installed on the OpenVMS node chosen
361. user with group privileges can cancel a job owned by another person in the same group To delete a job from a queue you must have operator OPER privileges execute E access to the specified queue or delete D access to the specified job 6 20 OpenVMS TRANSFER DTF File Transfer Operations Command Parameter job name Specifies the job name that you want to cancel You can display a list of job names by entering the TRANSFER DTF SHOW J OBS command CANCEL JOB Command Qualifier CANCEL JOB Qualifier Default QUEUE queue name QUEUE SNADTFS QUEUE QUEUE Specifies the name of the DTF queue in which the job you want to cancel was entered If the QUEUE qualifier is not specified the CANCEL J OB command checks for the job on the SNADTF QUEUE queue Examples TRANSFER DTF TRANS DTF gt CANCEL JOB DATA010 This CANCEL J OB command removes the job named DATAO10 from the DTF default queue SNADTF QUEUE If this job is waiting to execute the system deletes it If the job is already executing the system aborts it and then deletes it TRANSFER DTF TRANS DTF gt CANCEL JOB QUEUE NIGHTLY ACCOUNTING This CANCEL J OB command removes the job ACCOUNTING from the DTF queue called NIGHTLY 6 9 Displaying OpenVMS DTF Error Messages Most DTF error messages are RMS error messages that include a secondary numeric status code To display the text associated with the secondary status code in an RMS error message use the TRANSFER DTF
362. ust be an indexed file as the MERGE qualifier can only be used with indexed output files The OpenVMS DTF server node is LKG and the server account is IBMSYS1 Account verification on the MVS system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers 5 10 OpenVMS File Transfer Operations VM CONVERT LIST_INDEX DAT MAIN DTFVM PETER LIST USER PETER PASS SECRET MDADDR 192 MDWPASS ABC VSAM This command must be entered with no continuators within double quotation marks Because of line length restrictions in this manual the command is represented as a wrapped command line This command copies the indexed file LIST_INDEX DAT located in the current directory to the VSAM file PETER LIST Note that the VSAM qualifier is required for all VM VSAM accesses The OpenVMS DTF server node is MAIN and the server account is DTFVM Account verification on the VM system is installation dependent Contact your system administrator for information on the USERID and PASSWORD qualifiers 5 6 COPY Command To transfer sequential files between a DECnet DTF client and an IBM DTF client use the DCL COPY command COPY input file spec output file spec The COPY command allows you to do the following e Copy a sequential file from any IBM client to any location in a DE Cne network e Copy a sequential file from any location in a DECnet network to any IBM client
363. ve to use this keyword INMDPASS password M If the minidisk with the input file is not currently linked and accessed then use this parameter to supply the read minidisk password for a link to the minidisk identified in the INMDADDR keyword For more information about minidisk passwords see the MDxPASSWORD qualifier in Section 2 3 3 INNUM file number The INNUM keyword specifies a sequential file number on tape for an IBM input file file number A sequential file number on tape Range 1 to 9999 Usage Notes e Tape restrictions may apply Section 9 4 1 describes these restrictions e Ifthe input file resides on disk the DTF command processor will ignore the INNUM keyword e If you specify the INNUM keyword but do not specify a value for file number the DTF processor will default to INNUM 1 if the input file is on tape INPASS password Specifies the password associated with the INUSER account password The password associated with the INUSER account The syntax of the input file will determine the format of the password keyvalue DECnet The password that corresponds to the user ID to be used when contacting password the client node Length 1 to 31 characters IBM The password that corresponds to the user ID that the DTF Network password Manager subsystem uses when it verifies access to the input file Length 1 to 8 characters Usage Notes e If the remote client node is running Digital UNIX o
364. ver node where the file definition database resides If you omit the node parameter from the REMOVE FILE_DEFINITION command the server node defined by the last USE NODE command is selected by default If you have not issued a USE NODE command then your current node is selected The access control parameter specifies the account name and password of an account on the server node with read and write access to all the databases The account name is usually SNADTF MGR Note Do not use an account in the OpenVMS DTF server account database for the access control parameter file definition name Specifies the user assigned name of the file definition in the definition database C 8 Maintaining the OpenVMS DTF File Definition Database REMOVE FILE_DEFINITION Examples DIFCFG gt REMOVE FILE DEFINITION ACCOUNTING_FILE This example deletes the record called ACCOUNTING FILE from the file definition database on the current node DTFCFG gt REMOVE FILE DEFINITION MOOSE SNADTFSMGR SECRET POP_FILE This example deletes the record called POP_FILE from the file definition database on node MOOSE The access control information within double quotation marks consists of an account name SNADTF MGR and password SECRET for an account with read and write access to the file definition database Maintaining the OpenVMS DTF File Definition Database C 9 D VSAM File Support This appendix describes how the Digital SNA Data Transfer
365. vice calls the record locking RAB L_ROP bits are not supported with DTF for IBM However if a program has a VSAM file open for read and write then a record is locked when it is read or located through F IND The record can be unlocked by e Issuing another read e Issuing a write e Issuing a free e Issuing a release VSAM record locking is different from RMS record locking When an RMS record is locked only that particular record is locked However when a VSAM record is locked the entire control interval is locked because VSAM stores data records in control intervals similar to RMS buckets Therefore a record lock condition may exist not because another program owns the record you are trying to retrieve but because the other program owns another record in the control interval RMS File System and Programming Constraints B 3 B 2 1 4 Programming Considerations for VSAM Indexed Files The following should be considered when accessing VSAM indexed files Null keys VSAM does not support the null key attribute If an RMS indexed file has been transferred to an IBM system with DTF the null key attribute will be ignored This means that if you are accessing the file through a KRF that has a null key defined records that have the null key string will not be suppressed on a read Your program will have to do the checking for the null key string Loading a VSAM file If you are using your own program to load an empty VSAM file th
366. with a cooperating application on the IBM host and the Digital SNA Domain Gateway or Digital SNA Peer Server XV The information relevant to TCP IP transport support include the following e SNA _TCP_PORT logical e SNA _TRANSPORT_ORDER logical e Specifying TCP IP hostnames SNA_TCP_PORT Logical The SNA_TCP_PORT logical refers to the remote connection TCP IP port The default connection TCP IP port number is 108 For example if you want the remote connection TCP IP port number to be 1234 you can enter the following command line define SNA_TCP_PORT 1234 If you want the remote connection TCP IP port to be made to a service defined and enabled in the UCX database for example service name you can enter the following command line define SNA_TCP_PORT service_name SNA_TRANSPORT_ORDER Logical xvi The SNA_TRANSPORT_ORDER logical refers to a transport list which is used in automatic selection of transports Connections are attempted once for each transport in the list until either a successful connection is made or an error is returned when all transports in the list fail to connect For example if you want the software to try the DECnet transport and if this fails then to try the TCP IP transport you can enter the following command line define SNA_TRANSPORT_ORDER decnet tcp If you want the software to try the TCP IP transport and if this fails then to try the DECnet transport you can enter the following command
367. y in Data Record Length of Key Alternate Index Name 0 5 Since this is the primary key the name of the file specified on the command line is used This name is not sorted 7 3 userid Al X KRF1 15 8 userid Al X KRF2 Specifying the names in this way allows them to be sorted in the correct KRF order VSAM File Support D 7 D 3 VSAM Cluster Attribute Defaults DTF uses the standard Access Method Services I DCAMS utility to create VSAM clusters The DCAMS utility provides defaults for most of the VSAM file attributes However DTF does provide defaults for the following VSAM cluster attributes e ATTEMPTS e EXCEPTIONEXIT e SHAREOPTIONS e VOLUME The following sections describe the defaults for these attributes ATTEMPTS DTF provides a value for the DCAMS ATTEMPTS keyword The default is not to use this keyword however this can be overridden during installation EXCEPTIONEXIT DTF provides a value for the IDCAMS EXCEPTIONEXIT keyword The default is not to use this keyword however this can be overridden during installation SHAREOPTIONS DTF provides a value for the IDCAMS SHAREOPTIONS keyword if the user does not specify a value The default for this keyword is 1 3 however this can be overridden during installation VOLUME DTF provides a value for the IDCAMS VOLUME keyword if the user does not specify a volume A default volume name must be specified during the DTF installation D 8 VSAM File Support E FTAM
368. y the REUSE attribute if you specify UNIQUE e If you do not specify UNIQUE as the value VSAM data space must already be available on the volume that will be used by the component NAME enitry name Specifies the name of a component so that you can assign each component a name Usage Notes e f you do not specify a name a name will be generated e Names must conform to the MVS file name standards described in Section 2 1 REPLICATE option Specifies whether each index record in a component is repeatedly written on a direct access device track in the following manner e YES Each index record is written as many times as possible e NO Each index record is written only once Usage Notes e The default value for this attribute is NO e This attribute interacts with the default for VSAM s IMBED attribute to determine the physical attributes of the index record e This attribute relates only to a key sequenced data set KSDS REUSE option Specifies whether a component can be used repeatedly to load new records If REUSE is specified then the file is treated as if it were empty each time the file is opened with write access DTF File Specifications 2 43 Usage Note e If you specify YES you cannot specify UNIQUE as the value for the COMPONENT ALLOCATION attribute SHARE_OPTIONS option 1 option 2 Specifies 1 or 2 single digit numbers that control how a component can be shared among users e The value option 1 spe

Digital SNA Data Transfer Facility for OpenVMS Use

Contents

Download Pdf Manuals

Related Search

Related Contents