![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to batdes.txt CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [Power 6/32 Unix Tahoe 4.2BSD] / cci / usr / src / usr.bin / bsc / doc|
Return to batdes.txt CVS log | Up to [Power 6/32 Unix Tahoe 4.2BSD] / cci / usr / src / usr.bin / bsc / doc |
1.1 root 1: .RP
2: .TL
3: 2780/3780 Terminal Emulator
4: for UNIX*-Compatible Operating Systems
5: .br
6: General Operation Description
7: .AU
8: David L. Buck
9: .AI
10: D. L. Buck and Associates, Inc.
11: .LP
12: The most common environment for the 2780/3780 Terminal Emulator
13: product when used in a UNIX\(dg
14: .FS \(dg
15: UNIX is a trademark of Bell Laboratories.
16: .FE
17: development environment has the
18: computer system connected via leased lines to an IBM or compatible
19: mainframe.
20: In such an environment, one wishes to "submit" a file or series of
21: files to the host computer for batch execution, and receive program
22: listings in response. Often, several people are sending and receiving
23: these files via the remote link, and it is difficult to automatically
24: associate files sent back from the host with the person who sent
25: for them.
26: .LP
27: The following scenerio illustrates the sequence one might follow
28: in sending a file to a remote host and obtaining the response file.
29: .NH 1
30: FILE SUBMISSION
31: .LP
32: The user has prepared an Ascii or binary file for submission to the
33: host. The following command format may be used:
34: .DS C
35: bscbatch [-to=hostname] [-copy] [-mail] [file ...]
36: .DE
37: .LP
38: The
39: .I hostname
40: identifies which of possibly several hosts is to receive this file.
41: Normally any files specified will not be copied into the spool area,
42: but instead the filename noted and sent in whatever condition it
43: is at time of transmission; if the file should be copied and the
44: copy sent in order to protect the data, the user may specify
45: .I -copy.
46: The user will be notified by mail if the file for any reason
47: cannot be sent; the user may specify that mail be sent upon successful
48: transmission as well via
49: .I -mail.
50: If no input file is specified on the command line, standard input may be used.
51: If more than one file is specified, each is sent as a separate file.
52: .NH 1
53: DAEMON STARTUP
54: .LP
55: The
56: .I bscbatch
57: command invocation will cause entries to be made in
58: /usr/spool/bsc/hostname.
59: There will be a control file (C*), and a
60: data file (D*) if
61: .I -copy
62: was specified.
63: The bisync daemon
64: .I (bscd)
65: will usually be started by the
66: .I cron
67: process at user-specified intervals during the day.
68: The daemon reads the specifications from host parameter files in
69: .I /usr/lib/bscbatch
70: to determine which communications device to use,
71: the inactivity timeout interval, and the name of a file to be sent
72: when first establishing communications, if necessary (for example,
73: a /*SIGNON card, as frequently found in IBM RJE shops).
74: All spooled files awaiting transmission are sent to the host; all
75: received files are placed in the spool area with an assigned name
76: (P*). If there are no files to be sent, and there is no line activity
77: for the timeout interval specified in the
78: host parameter file, the daemon terminates.
79: .NH 1
80: CHECKING FOR OUTPUT
81: .LP
82: The user will periodically scan the host queue for received files
83: via the following command:
84: .DS C
85: bscbatch -q[=hostname] [-t=time] [-l=lines]
86: .DE
87: .LP
88: This command will display information on all files received from
89: the specified host (default is the first entry in the
90: host parameter file) that have arrived in the last
91: .I time
92: hours. Information displayed is the file name, time received,
93: size in characters, and the first
94: .I lines
95: (default 20) of received data.
96: The user will determine from this the names of all files of interest
97: to that user, and either make a copy of or link to those files.
98: .LP
99: If the installation has a means of automatically recognizing the
100: owner of received files, an installation exit routine can be used
101: to place the file in the owner's directory and optionally send mail
102: to the owner.
103: .NH 1
104: CLEANUP
105: .LP
106: As the users are not usually permitted to directly remove received files
107: from the spool area (since there is no straightforward way to identify
108: the files' owners), the spool area may build up quite a collection.
109: The following command may be periodically invoked to clean up the
110: spool area:
111: .DS C
112: bsclean [-t=time] [hostname]
113: .DE
114: .LP
115: This command removes all files older than
116: .I time
117: hours (default 72)
118: from the bscbatch spool area.
119: .FS
120: @(#)batdes.txt 1.5 8/27/84
121: .FE
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.