 |
File transfer to and from Cray-Cyber machines
Now, since Monday 3rd of February 2003 it's possible to transfer files
from and to computers of the Cray-Cyber Project
Important notice:
Please do not transfer files from your local computer to login.cray-cyber.org
on saturdays as the performance of the interactive sessions
would suffer from it.
How it works:
You have to relay through login.cray-cyber.org for every file. Direct
connections forwarded through the firewall to the internal machines are not
possible for security and practical reasons.
So - first get your file to login.cray-cyber.org - this can only be done using:
- SCP (Secure CoPy) (please see http://www.freessh.org for a client matching your operating system
The SCP client program you use may NOT issue any shell commands, so e.g. WinSCP will not work.
One efficient implementation for Windows is found at
pscp download
You MUST enforce usage of the scp protocol, so for pscp use you need these commandlines (open up a DOS command box for Windows):
pscp -scp user@login.cray-cyber.org:source localtarget
pscp -scp localsource user@login.cray-cyber.org:target
Log on using your normal username and password. Above, source is a file you want to download from the login server to the file localtarget to your computer at home. Localsource is your local file you want to upload to the login server with filename target.
Your files are now stored on the local HDD of login.cray-cyber.org.
For all our machines except the Cyber / DtCyber each user has its home mounted via NFS, therefore the
file will "just be there" in your home directory automatically on all machines (except the Cybers)
File transfer from/to the Cyber 960, DtCyber, other Cybers
If you have files you want to transfer from or to the Cyber, the only possible
way is relaying over the server.
To put a file on the Cyber, you first need to upload it to the server via
scp. Please keep in mind that Cyber NOS filenames are seven characters, alphabetic or numeric only. Then you connect to login (=our central fileserver) from the Cyber
/ftp
WELCOME TO THE NOS CLIENT FTP (VERSION 1.0 , PSR LEVEL 803 ).
--INFORMATIVE-- CONNECTING TO TCP/IP NETWORK.
--INFORMATIVE-- CONNECTED TO TCP/IP NETWORK.
--WARNING-- PROLOG FILE NOT FOUND OR BUSY.
FTP/open login
User? guest
Password? guest
FTP/dir
[...]
FTP/disci put
[... display_command_information for put command ...]
FTP/disci get
[... display_command_information for get command ...]
FTP/get login_file 'cybfil,cs=d'
FTP/put 'cybfil,cs=d' login_file
FTP/bye
The files on the server are your home directory, so you can see the files
you just uploaded via scp to the server (=login.cray-cyber.org) and transfer via the FTP connection
to the Cyber.
If you want to download a file from the Cyber you first have to put it
to the login server and then download it to your local machine by scp.
The character code used on login is ASCII. Unless you use the "cs=d" character set conversion command
shown above FTP will not affect the character code. ASCII can be used on the Cybers for some purposes,
but mostly (e.g., program text input to compilers) DISPLAY code (6-bit bytes) is expected.
The above given "cs=d" conversion option affects the ASCII from/to DISPLAY conversion within FTP.
Another way to achieve the same is to employ the standard FTP ASCII transfer, and then use the
FCOPY command for code conversion (see users guide or NOS2 reference manual).
File transfer between the Cyber 960, DtCyber, other Cybers
Of course you may use FTP from/to any of the Cybers and login. However, there are two different
methods of direct file transfers between the Cybers, much more in line with historical use:
You may use FTP in between the Cybers, e.g. open cy960 on DtCyber or open dtcyber on cy960.
The preferred method, however, is MFLINK as described in
chapter 10 of the NOS 2 Referecne Manual.
Cyber 960 is mainframe MAA here, and DtCyber is mainframe MDA within MFLINK.
In a similar way you may route batch input files or print files in between the Cybers.
Batch input files are routed with ...,ST=Mxx on the job statement, output files with the
ROUTE command, see NOS 2 Reference Manual.
|
