|
|
Power 6/32 Unix version 1.21
.RP
.TL
2780/3780 Terminal Emulator
for UNIX*-Compatible Operating Systems
.br
General Operation Description
.AU
David L. Buck
.AI
D. L. Buck and Associates, Inc.
.LP
The most common environment for the 2780/3780 Terminal Emulator
product when used in a UNIX\(dg
.FS \(dg
UNIX is a trademark of Bell Laboratories.
.FE
development environment has the
computer system connected via leased lines to an IBM or compatible
mainframe.
In such an environment, one wishes to "submit" a file or series of
files to the host computer for batch execution, and receive program
listings in response. Often, several people are sending and receiving
these files via the remote link, and it is difficult to automatically
associate files sent back from the host with the person who sent
for them.
.LP
The following scenerio illustrates the sequence one might follow
in sending a file to a remote host and obtaining the response file.
.NH 1
FILE SUBMISSION
.LP
The user has prepared an Ascii or binary file for submission to the
host. The following command format may be used:
.DS C
bscbatch [-to=hostname] [-copy] [-mail] [file ...]
.DE
.LP
The
.I hostname
identifies which of possibly several hosts is to receive this file.
Normally any files specified will not be copied into the spool area,
but instead the filename noted and sent in whatever condition it
is at time of transmission; if the file should be copied and the
copy sent in order to protect the data, the user may specify
.I -copy.
The user will be notified by mail if the file for any reason
cannot be sent; the user may specify that mail be sent upon successful
transmission as well via
.I -mail.
If no input file is specified on the command line, standard input may be used.
If more than one file is specified, each is sent as a separate file.
.NH 1
DAEMON STARTUP
.LP
The
.I bscbatch
command invocation will cause entries to be made in
/usr/spool/bsc/hostname.
There will be a control file (C*), and a
data file (D*) if
.I -copy
was specified.
The bisync daemon
.I (bscd)
will usually be started by the
.I cron
process at user-specified intervals during the day.
The daemon reads the specifications from host parameter files in
.I /usr/lib/bscbatch
to determine which communications device to use,
the inactivity timeout interval, and the name of a file to be sent
when first establishing communications, if necessary (for example,
a /*SIGNON card, as frequently found in IBM RJE shops).
All spooled files awaiting transmission are sent to the host; all
received files are placed in the spool area with an assigned name
(P*). If there are no files to be sent, and there is no line activity
for the timeout interval specified in the
host parameter file, the daemon terminates.
.NH 1
CHECKING FOR OUTPUT
.LP
The user will periodically scan the host queue for received files
via the following command:
.DS C
bscbatch -q[=hostname] [-t=time] [-l=lines]
.DE
.LP
This command will display information on all files received from
the specified host (default is the first entry in the
host parameter file) that have arrived in the last
.I time
hours. Information displayed is the file name, time received,
size in characters, and the first
.I lines
(default 20) of received data.
The user will determine from this the names of all files of interest
to that user, and either make a copy of or link to those files.
.LP
If the installation has a means of automatically recognizing the
owner of received files, an installation exit routine can be used
to place the file in the owner's directory and optionally send mail
to the owner.
.NH 1
CLEANUP
.LP
As the users are not usually permitted to directly remove received files
from the spool area (since there is no straightforward way to identify
the files' owners), the spool area may build up quite a collection.
The following command may be periodically invoked to clean up the
spool area:
.DS C
bsclean [-t=time] [hostname]
.DE
.LP
This command removes all files older than
.I time
hours (default 72)
from the bscbatch spool area.
.FS
@(#)batdes.txt 1.5 8/27/84
.FE
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.