|
12. File Transfer with FT-BS2000/RDAC
CFS supports the file transfer products FT-BS2000 and RDAC. Thus, files and PLAM library elements (PLAM only under FT-BS2000) can be transferred between different hosts, or between a host and various PC systems (MS-DOS, SINIX). Files can also be printed on remote station printers using RDAC. The RDAC CFS command can also be used if the FTOS product is installed instead of RDAC.
File transfer can be invoked by a Variable Action, ONXFT ... / ONXRDAC ..., by a command FT/ RDAC, or by an Action Code FT/RD. When defining the Variable Action or command, the necessary parameters such as host system name, userid, account number, logon password etc. can be entered as positional parameters. If some or all of the necessary parameters are missing, the FT module will automatically display a so-called File Transfer mask. The missing parameters can then be entered in this mask.
These FT parameters are saved, and will remain valid for future file transfer requests as default values.
The next time an FT/RD Action Code is entered, the FT mask will be displayed, so long as the standard values had not been set by an earlier FT/RDAC command, or an earlier ONXFT/ONXRDAC Variable Action. The values entered in the FT mask will be used for all following FT/RD Action Codes. The FT mask can be displayed at any time by entering the Action Code FTM or RDM.
With a mouseclick you get a describtion of the screen item.
If the FT mask is invoked as a result of an ONXFT Variable Action, or an FT Action Code, then the 'Filename to be transferred', 'Filename in Target-System' and 'Password for remote File' fields will not be displayed, except if the data object to be transferred is a PLAM library element. In this case, the 'Libname in Target System' and 'Password for Remote File' fields will be displayed on the screen. The name of the source library will be the predefined value. If this default value is not amended, then the library elements will be transferred to a PLAM library on the target system with the same name.
The 'Password for Remote File' and 'Remote User-ID Password' fields will be blanked out in the FT mask for data security reasons.
If any values are entered into the FT mask, these will henceforth be used as the default values.
If CFS is run in batch mode, the FT mask cannot be used. The FT parameters must be entered as positional parameters to the FT command, or when defining the Variable Action. The sequence of the positional parameters is the same as that used in the FT mask.
For a full description of the individual FT mask fields, and their respective entries, see the FT command on page 7-.
Example:
ONXFT HOST5,USER2,I2222,,
The file transfer will be made to host system HOST5 under userid USER2, and using the account number I2222. There is no logon password for this userid. The default values are assumed for the other parameters by virtue of ',,' .
The explicit specification of parameters after passw2 can also be omitted in CFS batch runs. The standard values will then be used.
Activate the Job Report upon Termination of File Transfer Requests
JRFT Setting the JRFT command causes all following file transfer requests (FT-BS2000 from V3.0) which were started from CFS and which have the PROTOCOL-LISTING: YES option set to be linked to a Monitor Job variable. This will result in the protocol being displayed by the CFS Job Report following termination of the FT request.
Notes:
The termination of FT requests can be monitored by the Job Report System of CFS as from FT-BS2000 Version 3. For further information, see the JRFT/NJRFT commands on page 11-.
Refer also to the NSTAT option in the FILENAME-SELECT field of the Selection mask for selecting all files currently being transferred with FT-BS2000.
When sending files (TRANSFER-DIRECTION : TO), the files will be created in the userid on the target system that was defined in the REMOTE USER-ID field. Exception: The user enters TSOS in the REMOTE USER-ID field with the respective account number and password. In this case, the user can transfer the file to any userid on the target system by prefixing the target file name with the required userid.
When receiving files (TRANSFER-DIRECTION : FROM), the files will be created under the current userid. Exception: The user is working under the TSOS userid. In this case, the user can transfer the file to any userid on the local system by prefixing the name of the file on the local (own) system with the required userid.
File Transfer of Job Variables
Job variables cannot be transferred directly to another system with FT-BS2000 or RDAC. However, if CFS is installed on both the sending and receiving systems, then it is possible to transfer Job variables from one to the other.
The following sequence of events should be performed:
a) On the source system, the required Job variables should be saved to a file (so-called Listcat file) with an ONXLISTCAT file Variable Action. LISTCAT saves the catalog entry details, as well as the Job variable contents.
b) This Listcat file can then be transferred as normal to the target system with FT-BS2000/RDAC.
c) On the target system, the Listcat file should be processed with the CFS command RECAT: RECAT file,CJ.
This command will recreate the catalog entry and the original data content of the Job variable on the target system.
File Transfer to SINIX Systems using FT-BS2000
Files can also be transferred between BS2000 and SINIX systems using FT-BS2000.
Variable Action ONXFT:
In the parameter mask for the Variable Action ONXFT, the following could be entered, for example:
Partner-Name : mx500 BCAM name of the Sinix system
Remote User-ID : 'guest'
Remote Account-# :
Remote Password : 'siemens'
Remote-Parameter : *any
Transfer-Direction : TO
TRANSFER-DIRECTION : TO The file to be transferred will be created on the SINIX system under the /usr/guest user.
TRANSFER-DIRECTION : FROM The specified file will be transferred from the /usr/gast Id on the SINIX system.
The user can also enter the full path for the Remote User-Id, e.g. /usr2/lkz/guest.
TRANSFER-DIRECTION : TO The file names will be created on the target system such that the first 12 characters of the name of the file to be transferred will be suffixed to the path name specified in the Remote User-Id. The BS2000 file name will be converted to lowercase (Standard).
If *any is entered in lowercase in the the Remote-Parameter field, then the BS2000 file names will be transferred to the SINIX system as a lowercase name.
If *ANY is entered in uppercase in the Remote-Parameter field, then the BS2000 file name will be transferred to the SINIX system as an uppercase name.
CFS Command FT:
Filename to be transferred : cfs.d.table
Filename in Target-System : '/usr/lkz/guest/table'
Partner-Name : mx500 BCAM name of the Sinix system
Remote User-ID : 'lkz'
Remote Account-# :
Remote Password : 'siemens'
Remote-Parameter : *any
Transfer-Direction : TO
In the FT command, the name of the SINIX file to be created or fetched can be specified as part of the full path name (e.g. '/usr/lkz/guest/table'). The file name will be passed to the SINIX system without modification. The file to be transferred can be sent to any user, or from any user.
The case of *ANY in the REMOTE PARAMETER field should be noted:
*any lower case letters in the file name are passed to the SINIX system as such.
*ANY lower case letters in the file name are transmitted to the SINIX system as upper case letters.
A user must be entered in the REMOTE USER-ID field who has creation rights for the file in the SINIX system (TRANSFER-DIRECTION : TO), or a user who has read rights for the file (TRANSFER-DIRECTION : FROM).
The Remote User-ID and Remote User-ID Password entries must be enclosed in quotes, and will be passed to the SINIX system exactly as entered, irrespective of the case of the *any/*ANY parameter.
With a mouseclick you get a describtion of the screen item.
If the RDAC mask is displayed by virtue of an ONXRDAC Variable Action, or an RD Action Code, then the 'Filename to be transferred', 'Filename in Target-System' and 'Password for remote File' fields will not be displayed.
The 'Password for Remote File' and 'Remote User-ID Password' fields will be blanked out in the FT mask for data security purposes.
If any values are entered into the FT mask, these will henceforth be used as the default values.
In batch runs of CFS in which the FT mask cannot be used, the FT parameters must be entered as positional parameters to the RDAC command, or when defining the Variable Action. The sequence of the positional parameters is the same as that used in the FT mask.
For a full description of the individual FT mask fields, and their respective entries, see the RDAC command on page 7-.
Notes:
The RDAC command of CFS can also be used if the FTOS product is installed instead of RDAC. This is also valid for the ONXRDAC Variable Action, as well as the RD Action Code.
Entering YES in the Print ? parameter field will cause the specified file to be printed on the remote printer defined in the 'Partner-Name' field.
The 'Remote User-ID', 'Remote User-ID Account-#' and 'Remote User-ID Password' fields do not have to be filled in when printing a file to a remote printer.
When printing files from RDAC to some specific printers, particularly desktop laser printers, the file can be printed out using particular layouts. These can be selected by means of the Form parameter.
If YES is entered in the 'Print ?' field, the standard Form parameter, 'STD', will be used. Any other value will be interpreted as a Form parameter. In this case, it will be assumed that a print process is required (Print=YES).
If YES | form is entered in the 'Print ?' field, additional print parameters may be specified. The following are possible: SPACE=., COPIES=.., HEADER=., LINES=..
Files will be automatically printed with SPACE=E on a remote device if the RDS Action Code is specified.
Transferring files with PC Systems (MS-DOS) using RDAC
Files can be transferred between BS2000 and MS-DOS PC's using RDAC/FTOS.
RDAC Command:
Filename to be transferred : cfs.d.table
Filename in Target-System : C:~subdir~table
Partner-Name : pcd2 BCAM Name of the PC
Remote User-ID :
Remote Account-# :
Remote Password :
Transfer-Direction : TO
Print ? : NO
The name of the file to be created or to be fetched, including the path and drive, can be specified in the RDAC command. The MS-DOS file name should not be enclosed in quotes. The file to be transferred can be created in or fetched from any subdirectory, no matter how many levels below the main directory.
The entries for Remote User-ID, Remote User-ID Account-#, and Remote User-ID Password are not interpreted by MS-DOS systems, and so must contain blanks.
Transferring Files to multiple Systems
1) Select the relevant files using the Selection mask.
2) ONXFT host1 [,usid,acct-#,passw]
Define the Variable Action for the first system.
3) Mark the files with the Action Code X.
4) After executing the Variable Action: Answer the termination query with U (Updated List). The files marked with an X will remain marked.
5) ONXFT host2 [,usid,acct-#,passw]
Define the Variable Action for the second system. Note: The ONX command may not be terminated with an END marker, otherwise the X's in the file list will be deleted.
6) Start the Variable Action with the command A.
Points 4 to 6 can be repeated as often as required.
If only a few files are to be transferred, the following is a simpler method than that described above:
1) Mark the first file with the Action Code FTM (explicit request for the FT Parameter mask), and all others with FT.
2) Enter the first target system name, userid, etc. in the parameter mask, when it is displayed.
3) Enter command A (Execute the Actions), if the files extend to more than one screen.
4) Answer the termination query with U or DUE1. Finally, repeat the above procedure for the second system.