|
|
1.1 root 1: .TH CRAY 1
2: .CT 1 comm_mach
3: .SH NAME
4: cray \- run job remotely on cray-xmp
5: .SH SYNOPSIS
6: .B cray
7: [
8: .I options
9: ]
10: [
11: .I jcl
12: [
13: [
14: .B +
15: ]
16: .I file
17: ]
18: ...
19: ]
20: .PP
21: .B c1sts
22: .SH DESCRIPTION
23: .I Cray
24: submits the named files to the MHCC Cray.
25: A plus sign stands for a Cray end-of-file,
26: which separates jcl, source code, and data files.
27: A file
28: .I jcl
29: that doesn't exist in the current directory
30: is searched for in the directory specified
31: by the shell environment variable CRAYJCL.
32: .TP 1i
33: .BI -o ofile
34: Send the job output to
35: .I ofile.
36: .TP 1i
37: .BI -p pages
38: If the jcl file doesn't begin with a job line,
39: .I cray
40: supplies one.
41: In that case,
42: the option
43: .BI -p n
44: specifies the maximum number of pages
45: (actually, 45-line blocks)
46: that can be output;
47: the default is 100.
48: .TP 1i
49: .BI -s n
50: Run the job at service grade
51: .I n.
52: (The default is
53: .LR -s2 ;
54: fastest is
55: .LR -s1 ;
56: long runs should be at
57: .Lr -s4 .)
58: .TP 1i
59: .BI -t seconds
60: If the jcl file doesn't begin with a job line,
61: specifies the maximum running time;
62: the default is 15.
63: .PP
64: .I C1sts
65: gives a status report on the cray.
66: .SH EXAMPLES
67: Run a Fortran program and subroutine, reading from param
68: on unit 5 and writing on unit 6,
69: .TP
70: .L
71: cray -o output ft + main.f sub.f + param
72: Run a Fortran program and subroutine, reading from param
73: on unit 5 and writing on unit 6,
74: .SH BUGS
75: Because of a problem with the standard input, the
76: .B -o
77: option is required for remote execution via Datakit.
78: .SH "THE FIRST TIME"
79: An incredible amount of busywork is required the first
80: time you use this command.
81: Get an account on mhuxa by filing an application
82: at the computer center accounting office,
83: and if possible get password aging turned off.
84: Set up your
85: .F .profile
86: on your home machine
87: and in the comp center so that remote execution in either
88: direction gets a silent login.
89: (Otherwise, you may get a `Bad magic number'
90: message when trying to execute a push.)
91: (Try copying the mhuxa file
92: .FR /a2/c1127/ehg/.profile .)
93: Set up mail forwarding from mhuxa to your
94: home machine.
95: (See
96: .FR /usr/mail/ehg .)
97: Now, from your home machine, execute
98: .IP
99: .L dkcc mhcc/mhuxa who
100: .LP
101: to be sure everything is set up properly.
102: The first time you try this, you will be asked to
103: login; this legalizes remote execution from your
104: home machine onto the comp center machine.
105: For the reverse direction,
106: your user id should be added to
107: .F /etc/procuid.local
108: on your home machine.
109: Export
110: .L CRAYJCL=/n/swift/usr/lsrc/cmd/cray/Jcl
111: from your
112: .F .profile
113: on your home machine.
114: By editing a copy of
115: .F /usr/bin/crmail
116: in your bin,
117: you can arrange for special action to be taken when
118: your output arrives; the default is mail notification.
119: Now you should be ready to run; try
120: .IP
121: .L cray -s1 -o tmp audit
122: .LP
123: If you don't get some job output back from the cray within a few minutes,
124: something is wrong.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.