SysIII/usr/src/man/docs/rje_guide_dqs
.tr !
.ds :? User's Guide to RJE
.PH "''''"
.OH "|\s9\f2\*(:?\fP||\\\\nP\s0|"
.EH "|\s9\\\\nP||\f2\*(:?\^\fP\s0|"
.nr Pt 0
.TL
Guide to Remote Job Entry for P\s-1WB\s+1/\s-1UNIX\s+1 Users
.AU "A. L. Sabsevitz" ALS PY 3646 7311 2G-211
.AU "E. J. Finger" EJF PY 3646 4383 2G-203
.MT 4
.H 1 PREFACE
.P
A set of background processes
support remote job entry (\s-1RJE\s0)
from a P\s-1WB\s0/\s-1UNIX\s0*
.FS *
\s-1UNIX\s0 is a Trademark of Bell Laboratories.
.FE
computer
to \s-1IBM\s0 System/360 and /370 host computers,
and \s-1UNIVAC\s0 1100 host computers.
.I Hasp
is the common name used for the collection of programs and for the
file organization that provides the \s-1IBM\s0 connection;
.I uvac
is the name of the analogous connection to \s-1UNIVAC\s0.
.P
P\s-1WB\s0/\s-1UNIX\s0 communicates with \s-1IBM\s0's Job Entry
Subsystem by mimicking an \s-1IBM\s0 2770 remote station.
A real-time program on a \s-1UNIVAC\s0 1100 supports a
similar protocol except that \s-1ASCII\s0 code is used.
The
.I "P\s-1WB\s0/\s-1UNIX\s0 User's Manual"
pages
.I hasp (8)
and
.I uvac (8)
summarize the design and operating procedures.
That manual also contains a terse description
of the
.I send (1)
command,
which is the user's primary interface to \s-1RJE\s0.\*F\
.FS
In this paper, \s-1RJE\s0 refers to the P\s-1WB\s0/\s-1UNIX\s0 facilities provided by
.I hasp\^ (8)
and
.I uvac\^ (8),
and
.I not
to the Remote Job Entry feature of \s-1IBM\s0's \s-1HASP\s0 or \s-1JES\s02 subsystems.
.FE
These are the definitive sources for information
about \s-1RJE\s0.
Although the words
.I Hasp
and
.I Uvac
may be used in this guide,
they represent all \s-1RJE\s0 subsystems of the P\s-1WB\s0/\s-1UNIX\s0 system.
.P
This guide is a tutorial overview
of \s-1RJE\s0.\*F\
.FS
The original versions of this manual and of \s-1RJE\s0 itself were written by T. G. Lyons.
.FE
It is addressed to the user
who needs to know how to use the system,
but does \fInot\fP need to know details of its implementation.
The two following sections
constitute an introduction
to \s-1RJE\s0.
''' ig.2
'
''' This information is proprietary and is the property of Bell
''' Telephone Laboratories, Incorporated. Its reproduction or
''' disclosure to others, either orally or in writing, is pro-
''' hibited without written permission of Bell Laboratories.
'
.H 1 PRELIMINARIES
.P
To become a P\s-1WB\s0/\s-1UNIX\s0 user, you must receive
a login name
that identifies you to the P\s-1WB\s0/\s-1UNIX\s0 system.
You should also get
a copy of the
.I "P\s-1WB\s0/\s-1UNIX\s0 User's Manual" .
This contains a fairly complete description of the system
and includes
the section
.I "How to Get Started" ,
which introduces you to P\s-1WB\s0/\s-1UNIX\s0;
you should read that section
before proceeding with this guide.
.P
In order to begin using \s-1RJE\s0,
you need only become familiar
with a subset of basic commands.
You must understand the directory structure of the file system,
and you should know something about the attributes of files:
see
\fIcd\fP\^(1),
\fIchmod\fP\^(1),
\fIchown\fP\^(1),
\fIcp\fP\^(1),
\fIln\fP\^(1),
\fIls\fP\^(1),
\fImkdir\fP\^(1),
\fImv\fP\^(1),
\fIrm\fP\^(1).
You must know how to enter, edit, and examine text files:
see
\fIcat\fP\^(1),
\fIed\fP\^(1),
\fIpr\fP\^(1).
You should know how to communicate with other users and with the system:
see
\fImail\fP\^(1),
\fImesg\fP\^(1),
\fIwho\fP\^(1),
\fIwrite\fP\^(1).
And, finally, you might have to know how to describe your terminal to the system:
see
\fIascii\fP\^(5),
\fIstty\fP\^(1),
\fItabs\fP\^(1).
.H 1 "BASIC RJE"
.P
Let's suppose that you have used the editor, \fIed\fP\^(1),
to create a file,
.B jobfile ,
that contains your
control statements (\s-1JCL\s0 or \s-1ECL\s0) and input data.
This file should look exactly like a card deck
except that alphabetic characters, for convenience,
may be in either upper or lower case.
For \s-1UNIVAC\s0 \s-1RJE\s0 the master space
.B @
may be represented by the
.B \v'0.4m'\s+3\(ga\s0\\v'-0.4m'
character.
Here is an example for \s-1IBM\s0 \s-1RJE\s0:
.DS 1 0
$ cat jobfile
//gener job (9999\fB,\fPr740)\fB,\fPpgmrname\fB,\fPclass=x usr=(mylogin\fB,\fPmyplace)
//step exec pgm=iebgener
//sysprint dd sysout=a
//sysin dd dummy
//sysut2 dd sysout=a
//sysut1 dd \(**
.in +3n
first card of data
.sp -.5v
.in +3n
\0\fB.\fP
.if t .sp -.5v
\0\fB.\fP
.if t .sp -.5v
\0\fB.\fP
.in -3n
last card of data
.in -3n
/\(**
.DE
.ne 3
To submit this job for execution,
you must invoke the \fIsend\fP\^(1) command:
.DS 1 0
$ send jobfile
.DE
The system will reply:
.DS 1 0
10 cards\fB.\fP
Queued as /usr/hasp/xmit311\fB.\fP
.DE
Note that
.I send
tells you how many cards it submitted and
reports the position that your job has been assigned
in the queue of all jobs waiting to be transmitted to the host system.
.tr ~
Until the transmission of the job actually begins,
you can prevent the job from being transmitted
by doing a
.B "chmod 0"
on the queued file to make it unreadable.
For our example, you could say:
.B "chmod 0 /usr/hasp/xmit311" .
.P
When your job is accepted by the host system,
a job number will be assigned to it,
and an acknowledgement message will be generated.
.tr ~~
This indicates that your job has been scheduled on the host system.
Later, after the job has executed, its output will
be returned to the P\s-1WB\s0/\s-1UNIX\s0 system.
You will be notified automatically of both of these events:
if you are logged in when \s-1RJE\s0 detects these events,
and if you are permitting messages to be sent to your terminal (see \fImesg\fP\^(1)\^),
the following two messages will be sent to you (still using the example above)
when the job is scheduled and when the output is returned, respectively:
.ne 7
.DS 1 0
.in +3m
\fITwo bells\fP
.in -3m
$12\fB.\fP18\fB.\fP42 JOB 384 ON RM4\fB.\fPRD1 \-\- GENER PGMRNAME
.in +3m
\fIBell\fP
.in -3m
.DE
.DS 1 0
.in +3m
\fITwo bells\fP
.in -3m
12\fB:\fP21\fB:\fP54 /a1/user/rje/prnt0 384\fB.\fPgener ready
.in +3m
\fIBell\fP
.in -3m
.DE
.P
The job acknowledgement message is passed on directly from
the host system, as indicated by its appearance in upper case.
The output ready message is generated by \s-1RJE\s0 and
appears in lower case.
Two bells, with an interval of one second between them,
precede each message.
They should be interpreted as a warning to stop typing
on your terminal, so that the imminent message
is not interspersed with your typing.
.P
If you are not logged in when one of these events occurs,
or if you do not allow messages to be sent to your terminal,
then the notification will be posted to you
via the \fImail\fP\^(1) command.
You can prevent messages directly by executing the
\fImesg\fP\^(1)
command,
or indirectly by executing another command,
such as
\fIpr\fP\^(1),
which prohibits messages for as long as it is active.
You may inspect (by invoking the \fImail\fP command) your mail file
(/usr/mail/\fIlogname\fP)
at any time for messages that have been diverted.
Setting your
.B \s-1MAIL\s0
variable to the name of your mail file
will cause the shell to notify you when mail arrives.
For this example, the mail might look as follows:
.DS 1 0
$ mail
From rje Mon Aug 1 12\fB:\fP20\fB:\fP36 1977
$12\fB.\fP18\fB.\fP42 JOB 384 ON RM4\fB.\fPRD1 \-\- GENER PGMRNAME
.sp .5v
? d
From rje Mon Aug 1 12\fB:\fP21\fB:\fP55 1977
12\fB:\fP21\fB:\fP54 /a1/user/rje/prnt0 384\fB.\fPgener ready
.sp .5v
? d
.DE
Here is a \s-1UNIVAC\s0 example:
.DS 1 0
$\ cat jobfile
\v'0.4m'\s+3\(ga\s0\v'-0.4m'run echo\fB,\fPacct-no\fB,\fPproject-id \fB.\fP usr=(mylogin\fB,\fPmyplace)
\v'0.4m'\s+3\(ga\s0\v'-0.4m'ed\fB,\fPi \fB.\fPelt
.in +3n
first card of data
.sp -.5v
.in +3n
\0\fB.\fP
.if t .sp -.5v
\0\fB.\fP
.if t .sp -.5v
\0\fB.\fP
.in -3n
last card of data
.in -3n
\v'0.4m'\s+3\(ga\s0\v'-0.4m'fin
$\ send jobfile
.DE
.P
The system will reply:
.DS 1 0
8 cards\fB.\fP
Queued as /usr/uvac/xmit311\fB.\fP
.DE
.P
The job acknowledgement messages are:
.DS 1 0
.in +3m
\fITwo bells\fP
.in -3m
$12\fB.\fP18\fB.\fP42 001.ECHO STARTED ACCT-NO
.in +3m
\fIBell\fP
.sp .2i
\fITwo bells\fP
.in -3m
12\fB:\fP21\fB:\fP54 /a1/user/rje/prnt0 \fB.\fPecho ready
.in +3m
\fIBell\fP
.in -3m
.DE
Note that there may exist a discrepancy between the host
and P\s-1WB\s0/\s-1UNIX\s0 clocks.
.P
The job acknowledgement message performs two functions.
First, it confirms the fact that your job
has been scheduled for eventual execution.
Second, it assigns a number to the job in such a way
that the number and the name together will uniquely identify
the job for some period of time.
.P
The output ready message provides the name of a P\s-1WB\s0/\s-1UNIX\s0 file into
which output has been written and identifies the job to which
the output belongs (see \fIls\fP\^(1)):
.DS 1 0
$ ls \-l prnt0
\-r\-\-r\-xr\-\- 1 rje 1184 Aug 1 12\fB:\fP21 prnt0
.DE
.ne 6
Note that rje retains ownership of the output
and allows you only read access to it.
It is intended that you will inspect the file,
perhaps extract some information from it
and then promptly delete it (see \fIrm\^\fP(1)):
.DS 1 0
$ rm \-f prnt0
.DE
.P
The retention of
machine-generated files, such as \s-1RJE\s0 output, is discouraged.
It is your responsibility to remove files from your \s-1RJE\s0 directory.
\s-1RJE\s0 output files may be truncated if the output exceeds a set
limit.
This limit is tunable by the system administrator.
Output beyond the current limit will be discarded, with no
provision for retrieval.
If the output is truncated, a warning message will appear in the
truncated file.
The user should also be aware that \s-1RJE\s0 attempts
to keep a set number of blocks free on any file system it uses.
This number is also tunable by the system administrator.
Warning messages or suspension of
certain functions will occur as this limit is approached.
.P
The most elementary way to examine your output is to \fIcat\fP it
to your terminal.
The appendix shows the result of listing the output
of our sample job in this way.
Printouts are stored with standard tabs to conserve space,
so you must ensure that the tabs are set on your terminal
at every eighth column across the entire line; \fItabs\fP\^(1) will do that for you.\*F\
.FS
If your terminal doesn't have tabs, you should use the \fIstty\fP\^(1)
command to cause P\s-1WB\s0/\s-1UNIX\s0 to automatically convert tabs to spaces
on output to the terminal.
.FE
Because P\s-1WB\s0/\s-1UNIX\s0 has no high volume printing capability,
you should route to the host's printer
any large listings
of which you desire a hard copy.
.P
The structure of an output listing will generally conform
to the following sequence:
.DS 1 0
\s-1HASP\s0 log
jcl information
data sets
\s-1HASP\s0 end
.DE
.P
Only in \s-1IBM\s0 \s-1RJE\s0 are
.I burst
pages discarded.
Single, double, and triple spacing is reflected in the
output file, but other forms controls,
such as the skip to the top of a new page,
are suppressed.
Page boundaries are indicated by the presence
of a blank (space character) at the end of the last line of each page.
.P
The big file scanner
.I bfs (1)
or
the context editor
.I ed (1)
provide a more flexible method than
.I cat (1)
for
examining printed output;
.I bfs
can handle files of any size
and is more efficient than
.I ed
for scanning files.
.P
R\s-1JE\s0 is also capable of receiving punched output
as formatted files (see
\fIebcdic\fP\^(5)\^);
this format allows an exact representation of an arbitrary
card deck to be stored on the P\s-1WB\s0/\s-1UNIX\s0 machine.
However, there are few commands
that can be used to manipulate \s-1EBCDIC\s0 files.
You will probably want to route your punched output
to one of the host's output devices.
.H 1 "SEND COMMAND"
.P
The
\fIsend\fP\^(1)
command is capable of more general processing
than has been indicated in the previous section.
In the first place, it will concatenate a sequence
of files to create a single job stream.
This allows files of \s-1JCL\s0 and files of data
to be maintained separately on the P\s-1WB\s0/\s-1UNIX\s0 machine.
In addition, it recognizes any line of an input file that begins
with the character
.B \v'0.4m'\s+3~\s0\\v'-0.4m'
as being a \fIcontrol\fP line that can
call for the inclusion, inside the current file, of some other file.
This allows you to
.I send
a top level skeleton
that ``pulls'' in subordinate files as needed.
Some of these may be ``virtual'' files that actually
consist of the output of P\s-1WB\s0/\s-1UNIX\s0 commands or Shell procedures.
Furthermore, the \fIsend\fP command is able to
collect input directly from a terminal,
and can be instructed to prompt for required information.
.P
Each source of input can contain a format specification
that determines such things as how to expand tabs
and how long can an input line be.
The manual page for
.I fspec (5)
explains how to define such formats.
When properly instructed,
.I send
will also replace
arbitrarily defined keywords by other text strings
or by \s-1EBCDIC\s0 character codes.
(These two substitution facilities are useful in other applications
besides \s-1RJE\s0;
for that reason,
.I send
may be
invoked under the name \fIgath\fP
to produce standard output \fIwithout\fP submitting an \s-1RJE\s0 job.)
.P
Two aspects of
.I send \^,
that everyone should be acquainted
with are, the ability to specify to which computer a job is to be
submitted, and the ability to verify a job prior to submission.
To run our sample job on a host machine known to \s-1RJE\s0 as
.B \A\ ,
we would issue the command:
.DS 1 0
$ send A jobfile
.DE
When no host is explicitly cited,
.I send
makes a reasonable choice.
.P
To verify the text of a collected job stream, without
actually submitting it, set the \fB\-lq\fP flags:
.DS 1 0
$ send \-lq jobfile
.DE
The complete list of arguments and flags
that control the execution of
.I send
can be found in
.I send\^ (1).
''' ig.5
'
''' This information is proprietary and is the property of Bell
''' Telephone Laboratories, Incorporated. Its reproduction or
''' disclosure to others, either orally or in writing, is pro-
''' hibited without written permission of Bell Laboratories.
'
.H 1 "JOB STREAM"
.P
It is assumed that the job stream submitted
as the result of a single execution of
.I send
consists of a single \fIjob\fP,
i.e., the file that is queued for transmission
should contain one \s-1JOB\s0 card
for \s-1IBM\s0 \s-1RJE\s0, or one \s-1RUN\s0 card
for \s-1UNIVAC\s0 \s-1RJE\s0,
near the beginning
and no others.
A priority control card may legitimately
precede the \s-1JOB\s0 card.
The \s-1JOB\s0 card must conform to the local installation's
standard.
At \s-1BISP\s0, it
has the following structure:
.DS 1 0
//name job (acct[\fB,\fP\fB.\|.\|.\fP])\fB,\fPpgmrname[\fB,\fPkeywds=?] [usr=\fB.\|.\|.\fP]
.DE
The \s-1RUN\s0 card must conform to the local installation's
standard.
In general, it has the following format:
.DS 1 0
@run name\fB,\fPacct-no\fB,\fPproject-id [ \fB.\fP usr=\fB...\fP]
.DE
.H 1 "USER SPECIFICATION"
.P
The ``usr=\fB.\|.\|.\fP'' field is required if any print or punch output is to be delivered to the P\s-1WB\s0/\s-1UNIX\s0 user.
.DS 1 0
usr=(login\fB,\fPplace[\fB,\fP[level][\fB,\fPretry]])
.DE
where
.I login
is the P\s-1WB\s0/\s-1UNIX\s0 login name of the user,
.I level
is the desired level of notification (see end of this section for an explanation),
.I retry
is a one character code specifying the number of attempts
to retransmit an entire job if the transmission to the host computer
is interrupted by an unrecoverable error (default is three attempts;
the digits \fB1\fP through \fB9\fP specify that number of retries;
\fB0\fP, \fBy\fP, or \fBY\fP invoke the default;
any other entry in this field
limits the number of attempts to one, i.e., no retry), and
.I place
is as follows:
.AL A
.LI
If
.I place
is the name of a directory (writable by others),
then the output file is placed there as a unique
.B prnt
or
.B pnch
file (up to 500 of each allowed).
The mode of the file will be 454.
.LI
If
.I place
is the name of an existing,
writable (by others), non-executable (by others) file, then the output file replaces
it.
The mode of the file will be 454.
.LI
If
.I place
is the name of a non-existent file in a writable (by others)
directory, then the output file is placed there.
The mode of the file will be 454.
.LI
If
.I place
is the name of an executable (by others) file, then the \s-1RJE\s0 output is set up as standard input to
.I place,
and
.I place
is executed.
Five string arguments are passed to
.I place.
For example, if
.I place
is a shell procedure, the following arguments are passed as $1 \fB.\|.\|.\fP $5:
.AL 1 "" 1
.LI
Flag indicating whether file space is scarce in
the file system where
.I place
resides.
A
.B 0
indicates that space is \fInot\fP scarce,
while
.B 1
indicates that it is.
.LI
Job name.
.LI
Programmer's name.
.LI
Job number.
.LI
Login name from the ``usr=\fB.\|.\|.\fP'' specification.
.LE 1
A ``\fB:\fP'' is passed if a value is not present.
The current directory for the execution of \fIplace\fP will be set
to the directory containing \fIplace\fP.
The environment (see
.I environ\^ (7))
will contain values for
.B \s-1LOGNAME\s0
and
.B \s-1HOME\s0
based
on the login name from the ``usr=\fB.\|.\|.\fP'' specification, and a value
for
.B \s-1TZ\s0 .
Since the login name supplied on the ``usr=\fB.\|.\|.\fP''
specification cannot be believed for security purposes, the \s-1UID\s0 will
be set to a reserved value.
.LI
In all other cases, the output will be thrown away.
.LE
.P
The
.I place
value must not be a full pathname,
unless it refers to an executable file (see D above).
For cases A, B, and C above (and case D, if a full pathname is not supplied), the name of the user's login directory
will be used to form a full pathname.
.P
The ``usr=\fB.\|.\|.\fP'' field may occur anywhere within the first 100 card
images
sent and within the first 200 output images received by the P\s-1WB\s0/\s-1UNIX\s0 system.
The only restrictions are:
.BL 5
.LI
Column one must contain a \fB/\fP or a \fB\(**\fP for \s-1IBM\s0 \s-1RJE\s0,
or a
.B @
or
.B \v'0.4m'\s+3~\s0\v'-0.4m'
for \s-1UNIVAC\s0 \s-1RJE\s0.
.LI
``usr=\fB.\|.\|.\fP'' must begin after column 4 and must be preceded by a space.
.LE
Therefore, the ``usr=\fB.\|.\|.\fP'' field may be placed on
a \s-1JOB\s0 card or comment card for \s-1IBM\s0 \s-1RJE\s0,
on a \s-1RUN\s0 card or message card for \s-1UNIVAC\s0 \s-1RJE\s0.
It may also be passed as data.
.P
For redirection of output by the host, a ``usr=\fB.\|.\|.\fP'' card, if not already
present, must be supplied by the user.
This can be done by placing a job step that creates this card before your output steps.
.P
Messages generated by \s-1RJE\s0 or passed on from
the host
are assigned a level of importance
ranging from 1 to 9.
The levels currently in use are:
.DS 1 0
3 transmittal assurance
5 job acknowledgement
6 output ready message
7 transmit format error
.DE
The optional
.I level
field of the ``usr=\fB.\|.\|.\fP'' specification
must be a one or two-digit code
of the form
.I mw\^ .
A message from the host with importance
.I x
(where
.I x
comes from
the above list)
is compared with each of the
two decimal digits in
.I level .
If \fIx\fP\(>=\fIw\fP and if the user is logged in
and is accepting messages, the message
will be written to his or her terminal.
Otherwise, if \fIx\fP\(>=\fIm\fP, the message will be mailed to the user.
In all other cases, the message will be discarded.
The default
.I level
is
.B 54 .
You should specify level
.B 1
if you want to receive
complete notification,
and level
.B 59
to divert the last three messages in the above list to your mailbox.
''' ig.7
'
''' This information is proprietary and is the property of Bell
''' Telephone Laboratories, Incorporated. Its reproduction or
''' disclosure to others, either orally or in writing, is pro-
''' hibited without written permission of Bell Laboratories.
'
.H 1 "HASP CONTROL CARDS"
.P
A number of control cards are recognized by the host's \s-1HASP\s0 subsystem.
Two are of particular interest to \s-1RJE\s0 users
because they control the disposition of output.
These are the \s-1ROUTE\s0 and \s-1OUTPUT\s0 cards.
If used, both should be inserted into a job stream
\fIimmediately\fP after the \s-1JOB\s0 card.
.P
The \s-1ROUTE\s0 card can be used to direct the entire
printed or punched output of a job
to a specified destination.
Two cards are required to direct both outputs:
.DS 1 0
.ta .9i 1.6i
/\(**route punch local
/\(**route print rmt55
.DE
The \s-1ROUTE\s0 card has a fixed format such that
.B print
or
.B punch
must begin in column
.B 10 ,
and the destination field in column
.B 16 .
.P
The proper use of the \s-1OUTPUT\s0 card is a bit more complicated.
It allows you to associate parameters
with all \s-1SYSOUT\s0 data sets whose
.I forms
numbers
match the one specified on the \s-1OUTPUT\s0 card.
The
.I forms
number is fictitious and
may consist of up to four characters.
A copy count and destination are among the parameters
that may be associated with \s-1SYSOUT\s0 data sets
in this way:
.DS 1 0
//name job \fB.\|.\|.\fP
/\(**output py d=rmt56
/\(**output abcd d=local\fB,\fPn=2
//step exec \fB.\|.\|.\fP
//prt1 dd sysout=a
//prt2 dd sysout=(a\fB,\fP\fB,\fPabcd)
//prt3 dd sysout=(a\fB,\fP\fB,\fPpy)
//pnch dd sysout=(b\fB,\fP\fB,\fPabcd)
.DE
In the above example, one copy of
.B prt1
would be directed
to the default destination
and one copy
of
.B prt3
to
.B rmt56.
Two copies each would be made of
.B prt2
and
.B pnch ,
and they would remain at the \fBlocal\fP site.
''' ig.9
'
''' This information is proprietary and is the property of Bell
''' Telephone Laboratories, Incorporated. Its reproduction or
''' disclosure to others, either orally or in writing, is pro-
''' hibited without written permission of Bell Laboratories.
'
.H 1 "MONITORING RJE"
.P
R\s-1JE\s0 is designed to be an autonomous facility that
does not require manual supervision.
R\s-1JE\s0 is initiated automatically by the P\s-1WB\s0/\s-1UNIX\s0
reboot procedures
and continues in execution
until the system is shut down.
Experience has shown \s-1RJE\s0 to be reasonably robust,
although it is vulnerable to system crashes and reconfigurations.
.P
Users have a right to assume that
when the P\s-1WB\s0/\s-1UNIX\s0 system is up for production use,
\s-1RJE\s0 will also be up.
This implies more than an ability to
execute the \fIsend\fP\^(1) command,
which should be available at all times;
it means that queued jobs should be submitted
to the host for execution and their output
returned to the P\s-1WB\s0/\s-1UNIX\s0 system.
If a user cannot obtain any throughput from \s-1RJE\s0,
he or she should so advise the P\s-1WB\s0/\s-1UNIX\s0 operators.
.P
The
.I rjestat\^ (1)
command, invoked without the
.B \-
argument,
will report the status of all \s-1RJE\s0 links for which
a given P\s-1WB\s0/\s-1UNIX\s0 system is configured.
It may sometimes also print a message of the day from \s-1RJE\s0.
.DS 1 0
$ rjestat
.sp .5v
15\fB:\fP12\fB:\fP24 \s-1RJE\s0 to B is operating normally\fB.\fP
.sp .5v
15\fB:\fP12\fB:\fP25 A is not responding to \s-1RJE\s0\fB.\fP
(8 files queued since 14\fB:\fP34\fB:\fP26)
.DE
A parenthetical statement, such as the last line above,
will summarize any backlog of queued files
waiting to be transmitted to the host machine.
A backlog that persists for 20 minutes or more
often is an indication that there exists a problem
with the corresponding \s-1RJE\s0 link.
.P
A host machine may be reported to be
not responding to \s-1RJE\s0
because it is down, or because of its
operator's failure to initialize the associated line,
or because of a communications hardware failure.
.P
The interactive status terminal capability of the \fIrjestat\^\fP(1)
command
is
.ul
not
implemented for \s-1UNIVAC\s0 hosts.
.br
.ne 60
.in 0
.nf
.ta 9n,17n,25n,33n,41n,49n,57n,65n,73n,81n
.ll 75
.ss 18
Appendix\-Sample \s-1JES2\s+1 Output Listing
.sp .5v
$ cat rje/prnt0
.if t .ps 8
.if t .vs 10p
.br
14\fB.\fP40\fB.\fP31 JOB 384 $HASP373 GENER STARTED - INIT 26 - CLASS X - SYS RRMA
.br
.nf
14\fB.\fP40\fB.\fP32 JOB 384 $HASP395 GENER ENDED
-\|-\|-\|-\|-\|- JES2 JOB STATISTICS -\|-\|-\|-\|-\|-\|
1 AUG 77 JOB EXECUTION DATE
54 CARDS READ
76 SYSOUT PRINT RECORDS
0 SYSOUT PUNCH RECORDS
0\fB.\fP01 MINUTES EXECUTION TIME
1 //GENER JOB (9999\fB,\fPR740)\fB,\fPPGMRNAME\fB,\fPCLASS=X JOB 384
\(**\(**\(** USR=(MYLOGIN\fB,\fPMYPLACE)
2 //IEBGENER EXEC PGM=IEBGENER
3 //SYSPRINT DD DUMMY
4 //SYSIN DD DUMMY
5 //SYSUT2 DD SYSOUT=A
6 //SYSUT1 DD \(**
//
IEF236I ALLOC\fB.\fP FOR GENER IEBGENER
IEF237I DMY ALLOCATED TO SYSPRINT
IEF237I DMY ALLOCATED TO SYSIN
IEF237I JES ALLOCATED TO SYSUT2
IEF237I JES ALLOCATED TO SYSUT1
IEF142I GENER IEBGENER - STEP WAS EXECUTED - COND CODE 0000
IEF285I JES2\fB.\fPJOB0384\fB.\fPSO0102 SYSOUT
IEF285I JES2\fB.\fPJOB0384\fB.\fPSI0101 SYSIN
IEF373I STEP /IEBGENER/ START 77242\fB.\fP1440
IEF374I STEP /IEBGENER/ STOP 77242\fB.\fP1440 CPU 0MIN 00\fB.\fP13SEC SRB 0MIN 00\fB.\fP01SEC VIRT 36K SYS 188K
\(**\(**\(**\(**\(**\(**\(** SERVICE UNITS=0000174 SERVICE RATE=0000268 SERVICE UNITS/SECOND
\(**\(**\(**\(**\(**\(**\(** PERFORMANCE GROUP=005
\(**\(**\(**\(**\(**\(**\(** EXCP COUNT BY UNIT ADDRESS
IEF375I JOB /GENER / START 77242\fB.\fP1440
IEF376I JOB /GENER / STOP 77242\fB.\fP1440 CPU 0MIN 00\fB.\fP13SEC SRB 0MIN 00\fB.\fP01SEC
\(**\(**\(**\(**\(**\(**\(** SERVICE UNITS=0000174 SERVICE RATE=0000268 SERVICE UNITS/SECOND
\(**\(**\(**\(**\(**\(**\(** APPROXIMATE PROCESSING TIME= \fB.\fP01 MINUTES
\(**\(**\(**\(**\(**\(**\(** EXCPS=000000000
\(**\(**\(**\(**\(**\(**\(** PROJECTED CHARGES= \fB.\fP01
.in +15n
.sp .5v
.if t .ps
.if t .vs
\fIfirst line of data\fP
.sp -.5v
\0\fB.\fP
.if t .sp -.5v
\0\fB.\fP
.if t .sp -.5v
\0\fB.\fP
\fIlast line of data\fP
.sp .5v
.if t .ps 8
.if t .vs 10p
.in 0
\(**OS/VS2 REL 3\fB.\fP7 JES2\(** END JOBNAME=GENER BIN=R740 JOB #=384 PGMRNAME
\(**OS/VS2 REL 3\fB.\fP7 JES2\(** END JOBNAME=GENER BIN=R740 JOB #=384 PGMRNAME
\(**OS/VS2 REL 3\fB.\fP7 JES2\(** END JOBNAME=GENER BIN=R740 JOB #=384 PGMRNAME
.if t .ps
.if t .vs
$ rm \-f rje/prnt0
.ex
.sp
.I "January 1980"