TcpLink 3000 CS		INAC Computer Innovative Netzwerkanwendungen

Benutzerhandbuch TcpLink 3000 CS in englischer Sprache

Chapter 6

Fetching Files from a Network or Archive

Files that have been sent from an ASPECT to another computer or to an archive using TCP can be transferred back to the ASPECT using TCP. Other files require to be converted to the appropriate format before they can be fetched with TCP (see chapter on file formats). For data files, Bruker's UXNMR program provides such a utility (back-conversion to ASPECT format). For text files, the program aspcon may be used. aspcon is delivered on the TCP installation diskette.

6.1 Fetching files from the ADAKOS command line

The general syntax for fetching files is

TCP G <file specification>, or TCP <data destination file>:G <file specification>.

The syntax is quite similar to sending/archiving files. Just the send option S is replaced by the get option G. There is also some difference in the handling of the wildcard characters * and ?. When sending/archiving files, the data source is the ASPECT disk, and wildcard specifications must be ADAKOS compatible. When fetching files, the data source is either a UNIX machine, a DOS PC or a SPECSTORE archive. Accordingly, in the first and second case you may use * and ? in the UNIX or DOS manner, respectively. In the second case it is important to know that SPECSTORE archives are DOS compatible, and wildcard specifications must conform to the DOS operating system.

The following table presents a number of examples.

Command	Operation
`TCP G DATA.001`	Fetch file, store it on disk D1
`TCP G DATA.001=D2`	Fetch file, store it on disk D2
`TCP G DATA.001 =D2`	Fetch file, store it on disk D2 (note: space before =D2 allowed)
`TCP G DATA.SER =D2`	Fetch file, store it on disk D2
`TCP G DATA??*.001`	Fetch selected files, store on disk D1
`TCP G * =D2`	Fetch all files, store on disk D2
`TCP SUN:G DATA.001`	Fetch file, use destination file 'SUN.TCP'
`TCP G DATA.001 =F1`	illegal (note: only disk devices are supported)

All these commands may be entered in lower case or capital letters. The name of a file to be fetched from a host is expected to not contain lower case letters in order to avoid confusion on the ASPECT disk that cannot handle mixed case letters.

When fetching a file from a host computer via TCP ip, and the file is larger than 512K ASPECT data points the program extract must be available in the user's home directory of the host. Please see the chapter Utility Programs on how to install extract. Alternatively, the unit may be equipped with additional memory.

6.2 Fetching files from the DISNMR command line

From DISNMR, fetching files from the network or an archive is quite similar to sending files as described earlier via the PASC command. We have learned that the command

PASC TCP

sends out the current data file since this is the default configuration of TCP . In order to receive files, you must use a name other than TCP , e.g.

PASC TCPF,

where TCP f is a copy of the TCP program which is configured for fetching files from a destination. Please refer to the section Changing/printing default configuration parameters that describes how to make such a copy.

There is one important difference when you want to fetch a file. Before sending a file you must define its name via the DISNMR RE command. This is not possible when fetching a file because the file usually does not exist on disk. For this reason you must define the name of the file to be fetched via the DISNMR WR command. This is necessary because WR sets the internal DISNMR file name parameters used by the TCP program. The file created by WR will be overridden shortly after by the received file.

The following table summarizes the most important cases.

Command	Operation
`WR DATA.001` `PASC TCP`	define data file fetch it
`WR DATA.002=D2` `PASC TCP`	define name and destination device fetch it, store on D2
`DU=D2` `WR DATA.002` `PASC TCP=D1`	set default disk to D2 define data file fetch it to D2 (assuming TCP only available on D1)
`DU=D2` `AU MKSER` `PASC TCP=D1`	set default disk to D2 define data filename fetch it to D2 (assuming TCP only available on D1)

The last example demonstrates how to fetch a .ser file. Since it is not possible to define a .ser file via WR, you must provide an AU program to generate it. The following one serves this purpose:

1 RF #1 1 WR #1 IN=1 EXIT

When you execute it via AU MKSER (let's assume you have given it this name), it will ask for the file name to create, which should be the name of the file you want to fetch. Type in <desired name>.SER. After the program has terminated, you can enter the PASC command to fetch the file as the example shows.

6.3 Fetching files from a DISNMR AU program

This section provides a number of examples how to fetch files from the network or an archive from a DISNMR AU program.

Example 1:

RF DATA.001 ; define data file WR DATA PASC TCP ; fetch it EXIT

Example 2:

WR DATA.SER ; define data file PASC TCP ; fetch it EXIT

Example 3:

RF DATA.002=D2 ; define data file WR DATA=D2 PASC TCP ; fetch it (and store disk D2) EXIT

Example 4:

; fetch NE files ; 1 RF DATA.001 ; define data file 2 WR DATA PASC TCP ; fetch next files IF DATA ; increment extension IN=2 ; do NE times EXIT

Files that are defined in an AU program via the WR @ command may also be fetched by a subsequent PASC TCP command.