next up previous contents
Next: 2.4 Special Note About Up: 2 REQUESTING DATA Previous: 2.2 Accessing the IUE

2.3 Transferring Data Files to Different Machines

  You can transfer RDAF-format IUE data files using binary mode in FTP. Once you have copied .DAT and .LAB files from IUE or another machine to your own, you may need to run the following procedure. This is only necessary if the two machines are not the same type.

CON_RDAF,'IMAGET',cpupar 

IMAGET Name of file to be converted. You may use wildcards. If the extension is not included, then both .DAT and .LAB files will be converted. You may not include a path name.
cpupar You may specify a code for the translation mode here. If you do not include this, CON_RDAF will prompt you.

0 ULTRIX to VMS (where both machines are Vaxes, or both MIPSEL)
1 Vax to MIPSEL
2 MIPSEL to Vax
3 Vax to SPARC
4 SPARC to Vax
5 MIPSEL to SPARC
6 SPARC to MIPSEL

The supported types are as follows:

  VAX VAXstations, MicroVAX

  MIPSEL DECstations, IBM 386 (IEEE little-endian)

  SPARC SparcStations, Sun 4nn, Macs (IEEE big-endian)

If you are uncertain which type your machine is you can run INTDAFMT:

INTDAFMT,TYPE,RMS

TYPE Internal data format of machine. Supported types are 'ieeebig', 'ieeelittle', and 'vaxformat'.
RMS Record Management Services. Set to 1 for Vaxes or MIPSELs running VMS or ULTRIX. Set to 0 for other systems.

Both parameters are output parameters that you can print (e.g., ``print,type'').

There is an analogous procedure for SAV files:

CON_SAV,'SAVFILE',cpupar/labelconsav

This procedure expects the filename to be entered without the .SAV extension. Wildcards are acceptable.

No conversion is necessary with FITS files. Just be sure to transfer them in binary mode.

FILE_CONVERT.TXT describes differences in data formats on various platforms. It's a plain text file located in the MANUALS subdirectory of the IUERDAF account.


next up previous contents
Next: 2.4 Special Note About Up: 2 REQUESTING DATA Previous: 2.2 Accessing the IUE

2/9/1998