|
|
1.1 root 1: README for the Apsend and Apstat Commands
2:
3: APSEND
4:
5: Apsend is a command that send device-independent troff output from the
6: user's 'home' UNIX system to the dedicated UNIX driving the APS-5
7: phototypesetter.
8:
9: Take the following steps to prepare apsend for your system.
10:
11: 1) Compile the file apsend.mkhd.c (which uses the file apsend.h).
12:
13: 2) Move the a.out file to apsend.mkhd.
14:
15: 3) Check the following shell variables in the apsend command and change if
16: necessary: NODE, MKHEAD, FNTABLES, NETWORK.
17:
18: NODE - use '`uname -n`' or the actual system nodename
19:
20: MKHEAD - use 'apsend.mkhd' (if apsend and apsend.mkhd will reside in
21: the same directory); otherwise use full pathname of apsend.mkhd
22:
23: FNTABLES - use '/usr/lib/font' or the actual pathname of the troff font
24: directory
25:
26: NETWORK - use 'uucp1' or 'uucp2' or 'usend' or 'nusend' as explained
27: below:
28:
29: use 'uucp1' for those systems selecting uucp network - AND uucp
30: BY DEFAULT copies source files to the spool directory. (Note:
31: 'uucp -C' is usually illegal on these systems.)
32:
33: use 'uucp2' for those systems selecting uucp network - AND uucp
34: does NOT by default copy source files to the spool directory
35: (invokes '-C' option of uucp)
36:
37: use 'usend' for those systems selecting usend network;
38: must also have the entry 'mhuxm mhuxv /usr/asp/unpackm'
39: in /usr/asp/udest
40:
41: use 'nusend' for those systems selecting nusend network (must
42: have NSC link to MHCC dedicated UNIX)
43:
44: 4) Be sure to leave a blank line as the first line of the apsend shell script.
45:
46: The apsend command resides in /usr/lbin on the Murray Hill Computer
47: Center UNIX systems.
48:
49: The man page for apsend is included as file apsend.1.
50:
51: APSTAT
52:
53: The apstat command sends a request for the current status of apsend jobs
54: (both APS-5 and imagen) to the dedicated UNIX driving both devices. The
55: UNIX acknowledges the status requests via UNIX mail, prepending a brief
56: bulletin indicating unusual turnaround conditions, if such exist. The reply
57: is sent to the <system>!<login> of the apstat submitter.
58:
59: Take the following steps to prepare apstat for your system.
60:
61: 1) Compile the file apstat.mkhd.c.
62:
63: 2) Move the a.out file to apstat.mkhd.
64:
65: 3) Check the following shell variables in the apstat command and change if
66: necessary: NODE, MKHEAD, REMOTEX, NETWORK.
67: NODE - use '`uname -n`' or the actual system nodename
68: MKHEAD - use 'apstat.mkhd' (if apstat and apstat.mkhd will reside in
69: the same directory); otherwise use full pathname of apstat.mkhd
70: REMOTEX - set value to '1' to request status via remote execution
71: of aps.status command; set value to '0' to request status without
72: remote execution of aps.status command
73: NETWORK - use 'uucp1' or 'uucp2' or 'usend' or 'nusend' as explained
74: above for the apsend command
75:
76: 4) Be sure to leave a blank line as the first line of the apstat shell script.
77:
78: The apstat command resides in /usr/lbin on the Murray Hill Computer Center
79: UNIX systems.
80:
81: The man page for apstat is included as file apstat.1.
82:
83: Please contact Virginia Turner, MH-2F-113, x4661, mhuxm!vbt if you have
84: trouble installing apsend or apstat on your system or if the commands do not
85: appear to work properly thereafter.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.