PREFACE
This guide :s designed
as
a handy, quick reference for System 370 operators
of
all
levels and
models. It includes a problem determination chart, S/370 general information,
CPU
manual
procedures for Models 115 to 195, operator commands for the various operating svstems,
IPl
procedures for DOSIVS and
VS1
and VS2, 1/0 information (status and sense data,
restart proceduras, operating hints!' utilities information, a glossary, bibliography, and
index.
Since its purpose
is
to selve
as
a qu
ick
reference··a memory jogger to the operator
in
a
dynamic, operating situation·· its content
is
slanted toward translation
of
code (bit informa-
tion such as condition code", status and sense bytes, etc.); command and record formats;
operating procedures; and error restart procedures.
System 370 model, embrace different kinds of hardware
cOr.:PQ,1e~ts
and input/output
<Jr.its.
The prob:em determination chart
in
the front of
the
guide
is
a generalized procedure
for
isolating
t~ouble
in
the S/370. Once the malfunctioning unit has been isolated, flow
charts for checking
out
that
unit can be found in the relevant Operating Procedures SR
l.
CPU
manual precedures, by model, are provided
in
Section 3. The procedure for loading a
secondary nucleus
and the hard stop procedure are new
in
the guide. The rest
of
the proced-
u."es
parallel those provided
in
the S/360 Operator's Reference Guide.
Depending on the oiJerating system generated, $/370 operators use a variety of commands.
OSIVS operators use
VS1
and
VS2
commands; DOSIVS operators use
DOSNS
and
POWER
commands: VM;'370 operators,
CP
and
CMS
cOIT\rnacds;
remote workstation operators, RES
commands; and so on.
In
other words, each operator uses
the
commands suitable
to
his
computer, operating system, and operator assignment. Section 4 contains the command
formats
fer
the various operating systems and operator consoles, and for remote
as
well
as
central
CPU
operators.
1/0
status and sense byte information
is
summarized
in
Section
5.
For the most part, only
the
first
six
bytes are
show~,
since these are
ali
that
concern
the
operator; the remaining
bytes are
of
interest
to
the field engineer. Complete status and sense byte information usual-
ly
appears
in
t~e
Component Description
SR
L.
For some of
the
smaller systems, however,
status and se"se information on 1/0 devices
is
presented
in
the Functional Characteristics
SRL.
Of
necessity, the information
in
this guide
is
highly condensed. Complete information
is
provided
in
theSRls.
To save the operator time we have noted the source of
all
information
in
this guide
in
order to steer him directly to the proper
SRl.
If
the
source appears just
:Jnce, as at the beginning of Section 2,
tris
means
that
all
the information
in
that
section
comes from
that
single source. The titles of the source publications can be found
in
Biblio-
graphy
1,
a numerically ordered list of
all
publications cited
in
this guide. Bibliography 2
lists publications
not
quoted frem directly,
is
more comprehensive, and
is
arranged by sub-
ject matter.
Since this
is
an operator's guide, we have included only information which concerns
the
uperator. For programming and field engineering information, consult
the
OS/VS Program·
mer's Reference Digest, the DOSIVS Handbook, and the
FE
Handbook.
Finally, a word of caution. For release-dependent information, check
the
appropriate
SRl
to
determine whether the information contained
in
this guide has changed
as
a result
of
the
r·ow
release.
As
of
the
date of publication, operator commands are current for
OSNSl
Release 3, OSIVS2 Release 2, VM/370 Release 2, and DOSIVS Releese 29.
To Next Page
Loading...
Need help?
General