G H 2()'()858-1

Type III Class A Program'p

Control Program-67/Cambridge Monitor:. System(CP-67/CMS) Version 3.2
Program Number 360D~05.2.005
Hardware Maintainability Guide

The CP-67/CMS Hardware MaintainabilityGuide
contains the f,ollowing information:• Conventions, instructions, and restrictions forrunning Customer Engineer Diagnostics under
the system'•

CP-67 Error-Recording Facility, including error­
recording mechanism, conditions and devices
involved in recording, and instructions for
retrieval of I/O error, channel check, andmachine check information•

Sample terminal sessions for running DME and
FRIEND

Note: This document must be read in its entirety
by customer engineers before they use theserviceability features of CP-67,

GH20-0858-1, Page Modified by TNL GN20-2620, May 15, 1973

NOTICE
This Type III Program performs~unctions which may be fundamental
to the operation and maintenance of a system. It has not been
subjected to formal test by IBM.
Until program reclassification, IBM will provide••

Central Programming service, including design error correction
and automatic distribution of corrections
FE Programming Service, including:(1)
Design error verification(2)
APAR documentation and submission(~
Application of Program Temporary Fixes or development 6f
an emergency bypass when required.

IBM does not guarantee service results or represent or warrant
that all errors will be corrected.
The user is expected to make the final evaluation as to theusefulness of this program in his own environment.
THE FOREGOING ,IS IN LIEU OF ALL WARRANTIES EXPRESSED OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

~Sg!!g

Editio!! (Octcber 1971)

This edition, together with Technical Newsletters GN20-2497 dated
January 24, 1972 and GN20-2620 dated May 15, 1973, applies to Version 3,
Modification Level 2, of the Control Program-67/cambridge lIonitor System(360D-OS.2.00S) and to all subsequent versions and modifications until
otherwise indicated in new editions or Technical Newsletters.
Information in this publication is subject
sure youhave the latest
edition andNewsletters.
Changes to text and illustrations are
the left of the change.

to change.
Therefore, beanypertinent Technicalindicated by a verticalline toRequests for copies of IBM publications should be made to yourrepresentative or to the IBM branch office serving your locality.

IBII

A form has been provided at the back of this publication for readers'comments.
If this form has been removed. address comments to: IBM
Corporation. VM/370 Publications. 24
New England Executive Park.
Burlington. Massachusetts 01803.
©

copyright
1973

International Business

Machines Corporation

1970, 1971,

GH2o-0858-1, page Modified by TNL GN20-2620, May 15, 1973.
PREF~CEThis publication is a guide for th~ maintenance of the hardware using
CP-67/CMS. The following publications are referenced in this manual:~=!1LCMS

User's §uide, GH2o-0859
CP-67 Program Logic Manual, GY20-0590

Additional references are:
~R-~LCMS_Slstem DescriEti2P ManYA!, GH20-0802~R~ OEerato~'s Guid~, GH20-0856~=&1LCMS Inst4llation Guide, GH20-0857~MS.Pr29ram_Logic

Manua!, GY20-0591~R:§1~_QEerating-~Istem§in a firtual Machine, GH20-1029- - - ----.--

#

..

.'~

GH2o-0858-1, Page Modified by TNL GN20-2620, May 15, 1973"

RUNNING CE PROGRAMS UNDER CP-67 •••••••••••••••••••••••••• ~ ••••••••••• 1
DEFINING A CUSTOMER ENGINEER'S VIRTUAL MACHINE ••••••••••••••••••••••• 2
CONVENTIONS FOR RUNNING DIAGNOSTICS UNDER CP-67 CONTROL •••••••••••••• 3

I/\1

INSTRUCTIONS FOR RUNNING DIAGNOSTICS UNDER CP-67CONTROL~ •••••••••••• 4
Running DME from Tape ••••••••••••••••••••••••••••••••••••••••••••• 4
Building an EXEC File for Loading DME •••••••••••••••••• ~ •••••••••• 4
Sample Command Stream to Run'a Diagnostic •••••••••••• ~ ••••••••••• ~9
OLTS Test Procedure for a 342U •••••••• ~ ••••••• ~ •••••••••••••••••• 13
INSTRUCTIONS FOR RUNNING FRIEND UNDER CP-67 .'•••••••••••••••••••••••• 14.1
ERROR-RECORDING FACILITY IN.CP-67 •••• ~ •••••••••••••••••••••••••••• ~.16
Error Recording Te·ch·niques •••• '•••••••.•• "••••••••••••••••••••·•·••••• 16
Conditions and Devices Involved in Recording ••••••••••••••••••••• 25
Instructions for Recordiri"g and Retrieval ••••••••••••••••••••••••• 32
Print Logrec ••••••••••••••••••••••••••••• ~ ••• ~ •••••••••••••••• 32
Create 3420 History:Tape~ ••••••••••••••••••••••••••••••••••••• 35
Clear·Lo9rec •••••••••••••••••••••••••••••••• ~,•••••••• ••••••••• 35.4
Change Sens~ Counter Limit •••••••••••••••••••••••••••••••••••• 35.4
APPENDIX A:

STATUS OF DIAGNOSTICS UNDER CP-67•••••••••••••••••••••• 36

2820-2301 Test •••••••••••••••••••••••••••.••••••••••••••••••••••• 37

2841-2311 Test ••••••••••••••••••••••••••••••••••••••••••••••••••• 38
2314 Test •••••••••••••••••••••••••••••••••••••••••••••••••••••••• 40
2402-2403 Test ••••••••••••••••••••••••••••••••••••••••••••••••••• 42
2703 Test •••••••••••••••••••••••••••••••••••••••••••••••••••••••• 45
2540 Test ••••••••••••••••••••••• c • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 46

1403 Test •••••••••••••••••••••••••••••••••••••••••••••••••••••••• 48
APPENDIX B:

CP-67·0N-LINE TESTING USER's GUIDE ••••••••••••••••••••• 49

APPENDIX C:

CP-67 ON-LINE TESTING GENERATION AND
MAINTENANCE GUIDE •••••••••••••••••••••••••••••••••••••• 58

GH20-0858-1, Page Modified by TNL GN20-2620, May 15, 1973
FIGURESI Figure 1.

I

Sample Terminal Session for Running DME from Tape ••••••••• 5
Figure 2. Sample Terminal Session To Build DME EXEC File •••••••••••• 8
Figure 3. Sample Terminal Session for Running 2314 Diagnostics ••••• 11
Figure 3.1. Sample Printout of OLTSEP Test from a Virtual Terminal.14
Figure 4. sample Terminal S~ssion to Display FRIEND EXEC File •••••• 14.1
Figure 5. Sample Terminal Session for Running FRIEND ••••••••••••••• 15
Figure 6. CP-67 Format for 2311/2314 •••••••••••••••••• i • • • • • • • • • • • • 17
Figure 7. Initializing Logrec Records •••••••••••••••••••••••••••••• 18
Figure 8. Logrecln-Core Pointers •••••••••••••••••••••••••••••••••• 19
Figure 9. Physical and Machine-Check Record Formats •••••••••••••••• 20
Figure 10. Physical and I/O Error Record Formats .................... 22
Figure 11. Summary of CP-67 Error Recording and Recovery ••••••••••• 24
Figure 12. Sample Printout of 1/0 Error Record ••••••••••••••••••••• 27
Figure 13. Sample Printout of Machine Check Record ••••••••••••••••• 29
Figure 14. Sample Printout of Channel Error Record ••••••••••••••••• 31
Figure 15. Sample Terminal Session To Load CE Serviceability Files.33
Figure 16. Sample Terminal Session for Running LOGPRINT •••••••••••• 34
Figure 16.1. Terminal Printout and User Input·Under M3420 EXEC ••••• 35.1
Procedu're
Figure 16.2. structure of 3420 History Tape •••••••••••••••••••••••• 35.2
Figure 16.3. Contents of 3420 History Tape ••••••••••••••••••••••••• 35.3
Figure 16.4. Hex Printout of Four History Tape Records ••••••••••••• 35.4

RUNNING CE PROGRAMS UNDER CP-67_ _ _ _ _,_._ _ __4_- - - -_ _ _ _0_ __ _ _ _ _ _ _ _ _ __••_. - - - - - - ­0Control program-67 is a multiprogramming, time-sharing
system that runs on an IBM System/360 Model 67.
Itsfunction is to create virtual machines in which users canrun the operating system of their choice concurrently withother users. The virtual machine created by CP looks to theuser like a typical System/360 in the range from a Model 30
to a Model 67. Operating systems that run on the real 360
can run on the virtual 360 as long as they. do not havetiming dependencies or c~rtain types of dynamically modified
I/O CCIl chains.
In a time-sharing system such as CP-67, a facility isneeded for running diagnostic . programs in order to allow
testing of I/O units concurrently with the operation ofother system tasks. This assists diagnosis, testing, andcheckout of malfunctioning I/O units, while maintaining
system operation.
>­

The capability to 'run unit tests under control of CP-61
provides the flexibility necessary to determine the impact
of malfunctioning devices. In most cases, it is possible todetermine the problem at the device level and thereby take
immediate correctiv« action.
Certain restrictions are imposed in orderdiagnostic
programs undercontrolof CP-61.
restrictions are as follows:•

Timing dependencies in a program cannot(for example, tape motion test).

•

Certain dynamically mOdified CCIltranslated by CP-67.

•

The DIAGNOSE instruction cannot be executed.

to

run
These

be guaranteedsequences cannot

beCertain CE diagnostics contain these restrictions andtherefore cause erroneous diagnostic messages. The DIAGNOSE
restriction eliminates running almost all CPU, storage, andchannel diagnostics, and some control unit tests. Although
it is now possible-to ipl DME from tape this does not ensurethat every self-modifying ipl sequence will necessarily work
correctly.

I ~-.

1

GH20-0858-1, Page Modified by TNL GN20-2620, May 15, 1973
DEFINING A CUSTOMER ENGINEER'S VIRTUAL MACHINE-------------.-------------------------------.---

I

,--"

The CE's virtual machine must be defined in the System
Directory.
This can be accomplished by contacting theoperations personnel at the system location.
'p

The following are the necessary directory entries that
the CE must have in order to create and save cataloged
procedures (called EXEC files)and Diagnostic Monitors, andto run the error-recording edit and print programs.
Note 1
Note
Note
Note
Note
Note
Note
Note
Note
Note

2
2
2
2
3
4
5
6
7

Note 1.

useridUSER password, accounta,C,30
CORE 256K
UNIT 009,1052
UNIT 00E,1403
UNIT 00C,2540R
UNIT 00D,2540P
UNIT OFF,TIMRUNIT 190,231X,CMS190,OOO,053,RDONLY'
UNIT,191,231X,CPDSK5,160,166
UNIT 230,231X,CPDSK1,004,004,RDONLY*EOU*

The CE should have privilege class C, as thisprevents error ~ecordings from being generated
when diagnostics are being run, and authorizes him
to clear the recording area.

Note 2.

Standard CMS devices.

Note 3.

Standard CMS pseudo-timer device.

Note 4.

The CMS system disk. The X is 1 or 4 depending
UpOn the type of disk dri~e on which the system
resides. This entry may be different, depending on
installation practices.

Note 5.

Private disk storage area. The X is 1 or 4. This
example gives 7 cylinders.
In order to utilize
the serviceability facilities in CP-67, it isnecessary to allocate at least seven cylinders fora 2314, or twenty five cylinders for a 2311.

Note 6.

The error-recording cylinder on the CP SYSRES
device. The
location of
the error-recording
cylinder is specified at CP SYSGEN time. Cylinder
four (004) is the default value. The X is 1 or 4.
CPDSK1 is the valid of the CP SYSRES device. Check
with the installation to ensure the volid has notbeen changed.
.

2

I~

Note 7.

~

A tape drive has not been assigned since theoperator will normally "attach" one to the user
(if DME is to be run from tape.)

Note that after CMS has been IPL'ed during the customer
engineer's in~l terminal session, a FORMAT P ALL should
be issued in order to have his P-disk area formatted. Thisshould only have to be performed ~ unless the P-disk area
is destroyed.
CONVENTIONS FOR RUNNING DIAGNOSTICS UNDER CP-67 CONTROL-----------------------------When diagnostics are being run under CP-67, the 1052
request key has to be simulated to cause the diagnostic
program to issue a read to the console~ To simulate the1052 request key, hit the ATTN key once, let the keyboard
unlock, and then hit ATTN a second time. The second ATTN isreflected to the virtual machine, whose operating systemthen reads the console~,

To simulate the cancel key on the 1052 console, theuser may employ the CP Console Function SET LINEDIT ON.
Once having issued this command, all input-lines are editedby CP before being passed to the virtual machine.
Bothcharacter-delete (m)' and line delete (ft)symbols may be
employed.
To stop the virtual machine at any time, hit ATTN once.
To start it running again from the location at which it was
stopped, type in BEGIN or B, followed by a carriage return.
To simulate the interrupt button on the System/360
console, there is a CP console function called EXTERNAL or
EXT. To generate an external interrupt while a diagnostic
is running, hit ATTN once and type in EXT, followed by acarriage return. The external interrupt i~ reflected to thevirtual machine, and control is returned to the virtual
machine's external interrupt processor.
To have a device that CP is using for paging or
spooling attached to your machine, it is necessary that thedevice be offline at system IPL time. After CP is IPL'ed,
the device may be switched online and attached to the CE'smachine by the operator's ATTACH console function.
!~: Terminals
which are equivalent to those explicitly
supported may also function satisfactorily. The customer is
r~sponsible
for establishing equivalency. IBM assumes noresponsibility for the impact that any changes to theIBM-supplied products
or programs
may haveon suchterminals.

3GH20-0858-1, Page Modified by TNL GN20~2620, May 15, 1973
INSTRUCTIONS FOR RUNNING DIAGNOSTICS UNDER CP-67 CONTROLRUNNING DME FROM TAPE
Previous versions of CP-67 were not able to properly
execute the self-modifying CCW sequences encountered in thetape loader of the Diagnostic Monitors. The restriction nolonger applies.
To ipl from tape it is necessary to have the system
operator "attach" a tape drive to the virtual machine. This
physical tape drive on which the Diagnostic Tape is mounted
has a real hardware address. CP allows the operator to
attach it to the configuration of the virtual machine at any
unused address, referred to as the virtual address. Usually
the real and virtual addresses will be the same. Should theydiffer, however, (for example, the tape is mounted on real
, address OC4 and the message DEV 181 ATTACHED appears at theterminal indicating the virtual machine will operate as
though a tape drive e~isted at address 181) the customer
engineer must use the virtual address in all DME commands.
Communication with CP-67 is established by the user
andisindicatedwith theCP-67
onlinemessage.
(Instructions for operating each type of terminal supported
are contained in the £f=67/£~~ser's_Q~~.)
ATTN is depressed once causing the keyboard to unlock.
This allows the user to log in with his userid. After themessage ENTER PASSWORD is typed, the keyboard is again
unlocked. The user then enters his password. Terminals
having the print inhibit feature prevent printing of thepassword on the terminal. For TTY 33/35, three lines ofcharacters are overprinted before the user enters his
password. This keeps the security of the password.
The operator's log message (if any) is then printed.
The keyboard unlocks and the user may ipl the tape drive(once the system operator has attached it to the virtual
machine) by issuing the command IPL ccu, where ccu is thevirtual address of the tape drive.
If an attempt is made to ipl before the drive isattached, the system action by CP will be equivalent toattempting to ipl a nonexistent address on the real hardware(the message will be typed.)
The copy of DME used should have UDT entries which atleast include the devices in the virtual configuration noted
above. Note the address of the console (which is usually009) may differ. Secondly, the console and not the printershould be configured as the primary output device.

4

~

~

'

\

A sample terminal sessioncommands is shown in Figure 1.
cp-61 online
login ce
ENTER PASSWORD

showing

the sequence

of

RI
CI
RI
CI
RI
RI
RI

xd.65 qsyosu

CP-61 WILL RUN TILL 11:00 AND FROM 18:00 to 24:00
READY AT 14.50.12 ON 12/03/69
CP

RI
RI
RI

DEV 181 ATTACHED <-Diagnostic tape mounted on this drive
DEV 236 ATTACHED <-Device to be tested
CPCI

ipl 181

M21

WTE IPL DME REV LEVEL 9

RI

CP

II
M21
RI
CI

l/b
MODEL 65
CP
ext

M21
M21
RI
CI
RI

WTE DME 9
CP<---ATTN key hit
detach 236
DEV 236 DETACHED

CI
RI

detach 181
DEV 181 DETACHED

CI
RI
RI

logoutCONNECT= 00.12.11 VIRTCPO= 003.11.66 TOTCPU= 005.23.51
LOGOUT AT 15.45.58 ON 12/03/69<---ATTN key hit<---ATTN key hit
256K
03FFFF<--~ATTN key hit

~

I

I
I
I

T

C = Command issued by user
I = Instruction for diagnostic monitor issued by user
M2 = Message from diagnostic monitor
R = Response from CP-61
Figure 1.

Sample Terminal Session for Running DME from Tape

5

BUILDING AN EXEC FILE FOR LOADING DME
Although diagnostic routines are usually tape resident
they can be put on disk. This enables diagnostics to be run1) without tying up a tape drive and 2) from remotelocations without operator intervention.
The necessary
EXEC files
to assistin running
diagnostics are included in the CE serviceability files. For
an example of how these were created see Figure 1 and the
explanation below; otherwise, -skip to ·Sample Command Stream
to Run a Diagnostic".
Improved EXEC procedures, invoked by DIAGS EXEC, are
now included in the serviceability files.
However, sincethese are somewhat more complex, the description of how tobuild and use an EXEC procedure deals with a very simple
case so as not to obscure the process.
DIAGS EXEC is described in a self-contained appendix,"CP-67 Online Testing User's Guide" and should be consulted
for information on its use.
Communication with CP-67 is established by the user andis indicated with the CP~67 online message.
(Instructions_for operating each type Of terminal supported are containedin the CP-67/CMS User's Guide.)
ATTN is depressed "once causing the keyboard to unlock.
This allows the user to log in with his userid. Afterthe
message ENTER PASSWORD is typed, the keyboard is again
unlocked.
The user then enters his password.
Terminals
having the print inhibit feature prevent printing of thepassword on the terminal.
For TTY 33/35, three lines ofcharacters are overprinted before the user enters his
password. This keeps the security of the password.
The operator's log message (if any) is then printed.
The keyboard unlocks and the user may enter the command IPL
CMS. The next message is documentary in nature. Note that
if the installation does not have a "saved" copy of CMS,
substi tute IPL 190 for IPL CMS.
The next twelve lines cause a file of the name of DME
EXEC to be built. This is the series of commands that will
be executed when the command DME is typed under CMS.
The command EDIT is used to create a file as indicatedby the return message NEW FILE. INPUT signifies that the
input environment has been entered, and the next six lines
are input data to the user's file DME EXEC. When the return
key is depressed without entering any characters on that
line, theedit environment is entered.
This allows

6

1\,

additions and changes to be made to the file. ~hen FILE isentered, the data lines are written out on disk as file OME
EXEC.
The user is now ready to read in a deck of cards
containing OME. These cards are used to build a file withthe filename of DME, but a filetype of IPL. First, however,two control cards must be put in front of the card deck.
The first card must be the normal CP-67 10 card (ID must be
punched in columns 1 and 2, and the userid starting incolumn 10).
The second control card must contain thefollowing information starting in column 1: OFFLINE READ DME
IPL. Tbe DME deck with these two control cards can then beplaced in the system card reader and read in by CP-67.
CP-67 puts the deck on the spooling disk (which is the"virtual card reader").
.
When the user types in the command OFFLINE READ *, thedeck is read from the virtual card reader by CMS.
This
causes the file DME IPL to be built on the P-disk and the
Diagnostic Monitor cards to be written into it.
The last command issued is LOGOUT, which terminates theuserWs operation unde~ CP-67.
When the command DME is entered while operating under
CMS, a deck of cards representing the Diagnostic Monitor DME
is transferred into the userws virtual card reader, fromwhich DME is automatically IPLWed into the virtual machine.
The EXEC file need be created only once, and the
OFFLINE READ * function need be performed only once, since
the files are permanently saved on the P-disk.

7

RI
I
CI
RI
CI
RI
RI
RI
CI
VI

·

cp-67 online
xd.65 qsyosu<----Hit ATTN Key
login ce<----Log in with your userid
ENTER PASSWORD:<----Type protected password
CP67 WILL RUN UNTIL 24:00 <--~-Message of the day
READY AT 09.41.29 ON 12/09/69
CP
ipl cms
CMS••• VERSION 3.0 -- 11/04/69(See FORMAT note at the end of "Defining a Customer
Engineer's Virtual Machine")
CI
EI
EI
DI
DI
DI

DI
DI
DI
Et
CI
VI
VI

edit drne exec
NEW FILE.
INPU'l':&typeout off
cp close c
cp purge rdr
cp xferd to * <--* means the userid issuing the commandoffline punch dme ipl
cp ipl c<---Hit RETURN for null line
EDIT:
file
R; T=0.05/0.35 09.42.39** CARDS HAVE BEEN RE!U) **<--deck entered by operator

CI
VI
VI

offline read * <---Reads deck in virtual card reader
OFFLINE READ DME IPL <---This is the information contained
R; T=0.08/0.20 09.45.00
in offline read control card.

CI
RI

cp logout
CONNECT= 00.04.42 VIRTCPU= 000.00.17 TOTCPU= 000.00.83

01

C = Command forCP-67/CMS issued by user
D - Data for CP-67/CMS issued by user
R = Response from CP-67
V = Response from CMS
E = Response from CMS EDIT command
Figure 2. Sample terminal session to build DME EXEC file8

SAMPLE COMMAND STREAM TO RUN A DIAGNOSTIC
A sample command
shown in Figure 3:

I.
I
I
I

streamforrunning diagnostics

isNote: For consistency, the sample describes the running of
the DME EXEC file built in the previous section. The DIAGSEXEC procedures are more inclusive and easier to run and aredescribed in Appendix A.
Initially, the communications between the user
terminal and CP-61 must be established.

at the

The userpassword.

correctlogs inwith

hisuserid andtheFollowing the log message, two messages are written
indicating that devices 181 and 236 are attached to theuser. This is a result of having asked the operator to
ATTACH these devices, either verbally or via the message
function.
After these mess~ges, the user can enter the command
IPL CMS.
This causes the Cambridge Monitor System to beloaded into the user's virtual machine.
Following thedeclaratory message for CMS, the command DME is entered.
This causes the command sequence explained in the section"Building an EXEC File for Loading DME w to be executed. The
Diagnostic Monitor DME has now been IPL'ed and the user isin the environment of DME. This means that the Diagnostic
Monitor has overlaid CMS in the user's virtual machine. The
terminal now appears to the user as the console typewriter.
The only difference is that the user must communicate with
CP-61 for certain preparatory functions to be performed in
the diagnostic program.
One of these functions is thesimulation of the external interrupt key. One depression of_
the ATTN key at any time during this period puts the user incommunication with CPo
This is illustrated by the sequence beginning after themessage WTE IPL DME REV LEVEL 9. ATTN causes CP to be given
control. A second ATTN causes control to be passed to DME.
The Diagnostic Monitor CDME) instruction "l/b" is entered,and DME is given control. Depressing the ATTN key the nexttime allows the ·user to type in EXT, which tells CP tosignal an external interrupt to DME. The next two ATTN
requests put DME in control, so the user can type in themessage describing the DM Loader Device and what DME is to
run for diagnostics.
The Diagnostic Monitor writes an appropriate message on
the terminal after running the requested diagnostics. The
user should then hit ATTN. This puts CP in control, and the9user can issue DETACH commands to release the devices
ATTACH'ed by the console operator at the start of the run.
The user then issues the command LOGOUT to release theterminal. Figure 3 follows.

10----------------------------------------~---"-~--~--

RI
CI
RI
CI
,r\RI
RI
RI
RI

cp-61 online
xd.65 qsyosu
login ce
ENTER PASSWORD:
CP-61 WILL RUN TILL 11:00 AND FROM 18:00 TO 24:00
READY AT 14.50.12 ON 12/03/69
CP

RI

DEV
DEV
CP

CI
VI

ipl cms
CMS••• VERSION 3.0 -­FRI

181 ATTACHED <-Diagnostic tape mounted on this drive
236 ATTACHED <-Device to be tested

11/04/69
o

CI
VI
VI
M21

dme
NO FILES PURGED** CARDS XFERED BY CE
WTE IPL DME REV LEVEL 9 **

RI

CP

II
M21
RI
CI

l/b
MODEL 65
CP
ext

M21
RI

WTE DME 9
CP<---ATTN ke~ hit<---ATTN key hit
a50,0181/a6a,0236/il0181/16aO,6bd,0236/b <-initialize DME
S
F6A03
loader and specify
T
tests.
F6A13
S

r\

II
M21
M21
M21
M21
M21
M21
M21
M21
M21
M21
M2
. M2
M2
M2
, M2
M2
M2
M2
M2
M2
M2
M2

<---ATTN key hit<---ATTN key hit
256K
03F.FFF<---ATTN key hit

T

S
T
S
T

F6A23

S
T
S

F6A43

F6A33

F6A53
F6A53 01 0035B2 0236
SHLD GET eCl ON SEEK INDICATING CUB BUT DID NOT CSW IS 000035E80COOOOOO

*SOO
T

S
F6A63
*SDO F6A63 01 0033B4' 0236
ERR esw 0000363002000011 CSW SHLD BE 0000363072000011
SNS 801000400100 SNS SHLD BE 80100040XXXX
T

S
F6A13
*SOO F6A13 01 0033B40236
ERR CSW 000035002000009 CSW SHLD BE 0000350072000009

11

,I

I

M21
M21
M21
M21
M21
M21
M21
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2J
M21
M21
M21
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2
M2

SNS 801000400100 SNS SBLD BE 80100D40XXXX*SOO F6A73 01 0033B40236
ERR CSW 0000356802000009 CSW SHLD BE 0000356812000009
SNS 801000400100 SNS SHLD BE 80100040XXXX*SOO F6A13 01 0033B40236
ERR CSW 000031200200000E CSW SHLO BE 000037201200000E
SNS 801000400100 SNS SHLD BE 80100040XXXX
T
S
T
S
T

F6A83
F6A93

S
F6AA4
*SDO F6AA4 01 003350
0236
ERR-E R A S E CAW 00J458
E~ CSW 000034781COOOOOO ACT CSW 000034780COOOOOOEXP SNS 00000040XXXX ACT SNS 000000400100
EXP READ OOC3000003 ACT READ 00C3000003*S-oO F6AA4 02 00358A
0235
ERR-SPACE COUNT CAW 0031FO
EXP CSW 0000381872000003 ACT CSW 0090381802000003
EXP SNS 00000040XXXX ACT SNS 080000400100
EXP RD DATA 2000000002
ACT RD DATA 2000000002
T
S
T
S

F6AB3
F6AC3

T
S

F6AE3

T
S

F6AF3

T

S
T
S
T
S

F6B03
F6B13
F6B23

*SOO F6B23 01 003394
0236
CSW 000036C000200000 CSW SHLD BE 000036COOC000001 SNS 000000400100
SNS SHLD BE 000000400XOO CAW 00003698
ERR WHEN SCAN BQ KEY DATA REMAINDER OF CYL, AFTER DEF TRK VIA 6TH SYS BY
TO LOOP ERR TURN ON SSWO
T

S

F6B33

T

S

F6BA3

T

S

F6BBJ

T

S
T

12

F6BC3

l

GH20-08 58-1, Page Modified by_ TNL GN20-262 0, May 15, 1973
/~

S

F6BD4

M21
M21
M21
RI
ci
RI

WTE DME 9
CP<---ATTN key hit
detach 236
DEV 236 DETACHED

CI
RI

detach 181
DEV 181 DETACHED

CI
RI
RI

logoutCONNECT= 00.12.17 VIRTCPU= 003.11.66 TOTCPU= 005.23.51
LOGOUT AT 15.45.58 ON 12/03/69

T

C = Command issued by user
I = Instruction for diagnostic monitor issued by user
M2 = Message from diagnostic monitor
R = Response from CP-67
V = Response from CMS
Figure 3. sample Terminal session for Running 2314 Diagnostics-

The Process of initiating an OLTS Test on a 3420 is similar
to DME and 240X diagnostics. To initiate an OLTS test, thefollowing procedure is followed:•

Mount the 3420 with a blank reel of tape with the file
protect ring installed. 'READY' the device.

•

Mount the OLTSEP diagnostic tape on another tape drive.
'READY' the device.

•

System operator attaches (ATTACH) the above two devices
to the CE's virtual machine.

•

CE logs in (LOGIN) and IPLs the OLTSEP diagnostic tape.

•

The response on the terminal indicates OLTS operation.

•

CE selects test and options described in OLTS and
OLTSEP literature.

Figure 3.1 illustrates the virtual machine printout of theoperation just described.

13

GH20-0858-1, Page Modified by TNL GN20-2620, May 15, 1973
xd.65 qsyosu

CP-67 online
1 ce

ENTER PASSWORD:'I

194 NOT AVAILABLESYSTEM WILL RUN FROM 08:30 TO 17:00
AND FROM 18:00 TO 24:00
READY AT 11.35.33 ON 10/30/71
CPm operator please attach 181 and 390 to me as 181 and 390.
DEV 181 ATTACHED
DEV 390 ATTACHED
CP
ipl 18104 SEP188D ENTER DATE IN FOLLOWING FORMAT 'MM/DD/YY'
r 04, '10/30/71'
04 SEP330D ENTER TIME IN THE FORMAT 'HH.MM.SS'
r04, '11.38.00'
04 SEP102I OLTS RUNNING'
04 SEP107I OPTIONS ARE~NTL,NEL,NPP, FE,NMI, EP, CP, PR, SI
01 SEP1050 ENTER DEV/TEST/OPT/
r 01, '390/2313a-f/nte,pp(3)/'04 SEP158I S T2313A- UNIT 0390
04 SEP158I T T2313A UNIT 0390
The start terminate messages will c'ontinue down throughtest 2313F at which time OLTSEP will request the next
device, test, and options to be run.
Figure 3.1.

14

Sample Printout of OLTSEP Test from a virtual
Terminal

I!

GH20-0858-1,

P~ge

Modified by TNL GN20-2620, May 15, 1973

INSTRUCTIONS FOR RUNNING FRIEND UNDER CP-67?

In addition to the standard diagnostics under CP,
FRIEND has been used extensively with no known problems. It
should be noted that in the CP-67 error-recording mechanism,
the failing CCW string on I/O errors is recorded with theerror information. This makes. FRIEND much more valuable asa trouble-shooting aid under CP.
The contents of FRIEND EXEC are shown in Figure 4.

::;

print friend exec
&TYPEOUT OFF
CP PURGE RDR
CP XFER D TO *OFFLINE PUNCH FRIEND IPL
CP IPL C
R; T=0.03/0.10 09445.00
Figure 4. Sample Termin~l Session To Display FRIEND EXEC
File
When the command FRIEND is entered while operating
under CMS, a deck of cards representing FRIEND is ~ritten
into the user's virtual card reader, from which it is IPL'ed
into the virtual machine.
A sample terminal
in Figure 5.

session for running FRIEND

is shown

FRIEND can be loaded by an alternate means if necessary
if it does not already exist on a CMS disk. "This alternate
procedure is as follows: An ID card can be placed in frontof the FRIEND deck and put in the system card reader. CP-67
reads the deck in, and puts it on the spooling disk (thevirtual card reader).
Then, when CP control has been
established, type in IPL C and wait a couple of seconds. The
keyboard unlocks.
Signal an EOB, and the FRIEND heading
types out. If you wish to re-IPL FRIEND a number of times,
issue the SET CARDSAVE ON command to CP. When ypu havefinished using FRIE·ND, issue to CP the command SET CARDSAVEOFF.
To clear FRIEND from the virtual card
CP command PURGE RDR.

reade~,

issue the· 14.1

Rl
I

,r\

ci

'"

RI
CI
RI
RI
RI

CI
RI
vI

ci

VI

vI
R
C
M2
M2
I
I
I
I
I
M2
I
M2
R

CI
RI
RI

cp-61 online

xd.65<---Hit ATTN

login ce
ENTER PASSWORD:<---Password entered
CP-61 WILL RUN TILL 24:00
READY AT 13.33.43 ON 12/08/69
CP
ip1 cms
DEV 101 ATTACHED
CMS ••• VERSION 3.0 -- 11/04/69
friendNO FILES PURGED** CARDS XFERED BY CE<---keyboard should unlock - hit RETURNFRIEND-3-DES"CP <---Friend now running in users
reset
virtual machine - hit ATTN
DEV = DEVICE ADDRESS XXX = 101 .
ENTER CCW LIST IN ENGLISH
skcyl=OO
hd=190read haloop
NUMBER OF TIME = 100go
LOOP IS FINISHED ON UNIT 101
CP<---ATTN key was hit
log
CONNECT=.
.02.21 VIRTCPU= .2.23.62
LOGOUT AT 11.16.23 ON 01/08/69

C = Command for CP-61/CMS--issued by user.
M2 = Message from FRIEND
I = Instructions to FRIEND--issued by user
R = Message from CP-61
V = Message from CMS
Figure 5. Sample terminal session for running FRIEND

15

'.i

ERROR-RECORDING FACILITY IN CP-67
ERROR-RECORDING TECHNIQUESThis section is written for the customer engineer tomore fullyacquaint himself withthe error· recording
mechanism used by CP-67.
The Logrec (SYSERR) area used by CP-67 is located on
the CP system residence device (normally the label is
CPDSKl), which can be a 2311 Disk Storage Drive or 2314
Direct Access Storage Facility. It is one cylinder long, andits location is specified in the CP SYSGEN macro SYSRESSYSERR=xxx, where xxx is the cylinder address desired. If
the SYSERR option was not specified, the default cylinder
address would be set to cylinder 4.
Before a CP-67 sysgen, the CP system residence volume
must be initialized by the CP Format utility program, which
writes dummy records without key fields for the entire disk
(as shown in Figure 6).
When the newly created CP-67 control program is IPLwed
the first time, it further formats the Logrec cylinder by
locating its address (passed via the SYSGEN macro), andinserts eightbytes ,; of control information
into thebeginning of each physical data record contained on thatcylinder (as shown in Figure 7).

1615 RECORDS PER PAIR OF TRACKS,}~REPEATED FOR THE ENTIRE DISK

0-·
1 ..

/

HA

RO

Rl

L.:.J GEJ B/7/CountField ~~ /bataField~
.

/

R3~

R2

v

Evenn
Trk

S291

GJ EEJ ~ r-l
HA

Odd
Trk

lsi

RO

RS,

R9

R4

B

Rl0

Special CKD ~

B
Rll

RS

R6

B~
R12

R13

R7

RS~

lsi S29·1

~

R14

R15

-'11r-~T""'1-S2-9...." r-lsT""'1-S2-9-'1 r-ls 'T""I-S2-9-'1 ....
I S'T"I-S2-9-, . ~s 'T""I-S2-9-'11r-s'T""]'--S2-9

0-·

~--~
r::
~R_2~_-_-_-~--R-3---------R-4----~~ ·EEJ ~Is:"-I --'''sli""'I~Isr-I-S29~'
RO

Rl

-S2-9

S291

S'T-,-S2-9--"Figure 6. CP-61 Format for 2311 and 2314

11

0-­
1 -­

CYLINDER = SYSERR

18-­
19-- ....._ __~R""3...-____

R2

8

Never chg

829

GI

829

I FI

829

:pR..;,15;.,-_ _-,I~II~ 118

829

Data index~~
I C Icl HI H I R 1 0

I

IN N , ...........- - - - - - - - < 8 2 1 Bytesavailable-----------Jl..--iyControl Field

CC
HH
R

o
N

N

Note:

SYSERI3

Head this physical record on
Same as physical record in counll field'FF' - Flag - Always FF} Data Index - Initialized to zero. As error records are added,
it contain~ the .number of bytes used in the record.

2311 w()uld be formatted exactly the same, except it wou Id havefour (41 physicill records per track_

Figure 7. Initializing Logrec Records

18

The Legrec cylinder is split into two areas by CP.
Tracks o and 1 are used to record machine-check errors:
tracks 2-19 are used to record I/O outboard and channel
errors (tracks 2-9 for 2311).
To locate the first or next available disk location for
an error record to be written, the Control Program maintains
two tables in core.
The first table (label is IOERR)
contains the disk address for the next available I/O error
record slot, and the second table (label is MCERR) contains
the disk address for the next available machine-check record
slot. The tables, called the in-core record pOinters, areinitialized during the first IPL of CP to reflect the
beginning of the I/O and machine-check recording slots (asshown in Figure 8).
IOERRIOERRBBIOERRCCIOERRHHIOERRRIOERRD
IOINDEX

DS
DC
DC
DC
DC
DC
DC

OF
X'OOOO'X·XXXX'
X'0002'
X' 01'X'FF'
X'POOO'MCERR
MCERRBBMCERRCCMCERRHH
MCERRRMCERRDMCEINDEX
SYSERREQU*X'OOOO'

Note:

Figure

DC
DC
DC
DC
DC
DC
DC

X'XXXX'X'OOOO'
X'Ol'
X' FF'X'OOOO'
H'04'

Bin--Always zero
SYSERR addr. See note.
starting head f or I/O errors
Record 1
Flag
Data index
Bin--Always zero
SYSERR addr. See note.
starting head for Mch. Ck. errors
Record 1
Flag
Data index
Set at IPL--Default to '04'

At IPL time CP initializes to whatever cylinder
address is in the SYSERR location, as specified at
SYSGEN.
8.

LegrecIOERROR

in-corepointers,

locatedinmoduleBefore the Control Program attempts to write an error
record on Legrec, CP gets the next available physical record
pointer (I/O or MCH) from the Win-core record pOinters-, andreads that physical data record into core. CP also updates
the in-core pointers for the next error-recording requester,then uses the data index bytes (in the control field of the'physical data record just read) to insert this error into
the correct physical data record offset. CP adds this error
record length to the data index bytes and writes thephysical data record back to the same location it was readfrom. Figures 9 and 10 show the format of two physical19

records, and theoutboard records.

formatofthemachine-check

and

I/O

Count Field

C

C

H

H

R

K

D

L

I

I

I

I

I

I

I

I

I

I

I

I

I

I

I

I

I

I

IOOl0410010110AIOOI0313DI

Data Field
C

C

H

R

H

N

D

N

I I I I I I I I I
100lO410010110AIFFI011801

I

I

I

I

I

I

I

I

I

Mach Ck
Rec

Empty
Slot

384

384

53
Not
Used

Machine Check Record
Byte

Field Name

Field Description, Contents, Meaning

0-5

LOGMDATE
LOGMCODELOGMCPU
LOGMPSW
LOGMGRS
LOGMCRS
LOGMFPRS

MO/Day/Yr/Hr/Min/Sec
Extended Mck I nt CodeCfU Logout Oat a
Old PSW's at time of Machine Check
General registers at time of Machine Check
Extended Control Registers
Floating Point Registers

6-7

8-183
184-223224-287288-351352-383

Note: The next available in-core record pointers would have
CC=04, HH=Ol, R=OA, O=FF, INDEX=0180
Figure 9. Physical and machine-check record formats

20- - - - -------- - - - - - - - - - - - - - - - - - -I
IIPage of GH20-0858-1
Revised January 24, 1972
By TNL GN20-2497

Count Field

C

C

H

H

R

K

D

L

I

I

I

I

I

I

I

I

I

J

I

I

I

I

I

I

I

I

IOOl0410010 7 10F IOOI0313DI

Data Field
C

C

H

R

H

N

D

N 112

I

I

I

I

I

I

I

I

I I/O

I

I

I

I

I

I

I

I

I

112

112

IOOlO410010710F IFFI031101 Rec

112

112

112

,

112

I/O I I/O I I/O I I/O
I/O I I/O I Not 1­
Rec I Rec I Rec I Rec I Rec I Rec I Usedl

I

* I

I

* I *

I

* I

*
*
*
• These may be either I/O Error
Records
or Channel
Check Records
I/O Error Record
Byte

Field Name

Field Description, Contents, Meaning

0-5

LOGSNSE~ense

Bytes from Device (up to 6, if
provides less than 6, theremainder contain 00). If the device
type is 3420 these 6 sense bytes are
not used. The 3420 provides 24 sense• bytes and they are in the LOGCCWS area.
d~vice6

LOGCODE

7

LOGTYPE

CODE
Fx
Cx
xl
x2
x3
x4

Type of I/O Error
First encountered error of this typeCounter overflow for this error type
Bus Out
Equipment Check
Data Check
Seek Check or Data Convert Cbeck
CP-67 Device Type Code (See Sec. 3,
CP PLM)

8-13

LOGVOLID

Volume Serial Number of device uponwhich the error occurred (if known to
CP)

14-15

LOGADDR

Channel/Unit Address of erring device

16-21

LOGDATE

Month/Day/Year/Hour/Minute/Second

22-27

LOGCSWcsw at the time of the error

30-31

37

Reserved for futUre use

32-103

LOGCCWS

iFailing CCW string (last 9 CCW's or'less)If the device type is 3420; the first
3 double words contain the 24 sense
bytes and only the la,S t 6 CCW' s, orless, of the failing CCW string are
retained.

104-111LOGSKLOC

Last seek address prior to the failure
21

LChannel check Record
Byte

Field Name

Field Description, Contents, Meaning

0-5

LOGSNSE,Up to 6 Sens e Bytes

6

LOGCOOE

CODE
Fx
xA

xB
xC

xD

Type of Channel Error
All Channel Errors are flagged as firstencountered errors for consistency with
I/O error records
Channel Data Check.Channel Control Check
Interface Control Check
Chaining Check

1

LOGTYPE

CP-61 Device Type Code (See Sec. 3,
CP PLM)

8-13

LOGVOLID

Volume Serial Number of device performing
I/O when Channel Check occurred (if known
to CP)·

14-15

LOGADDR

Channel/Unit Address of device

16-21

LOGDATE

MonthlDay/Year/Hour/Minute/second

22-29

LOGCSW

CSW at time of error

30-31

Reserved for future use

32-39

LOGIOPSW

Old I/O PS~ stored at time of error

40-63

LOGCHLOG

Channel Logout Data

64-61

LOGCAWCAW at time of error

68-111

UnusedNote: Tbe next available in-core record pointers would bave
CC=04, HH=08, R=Ol, D=FF, INDEX=OOOO.
Figure 10. Physical and I/O error record formats
If the attempt to read or write an error record fails,
it is retried eight times.
Upon continued failure, theerror message ** IOERROR RECORDING FAILURE ON DEV XXX ** issent to the operator, and that error record will be lost.
If there is no more room in the machine-check or I/Ooutboard areas, the message
LOGREC FULL: (I/O or M/C)ERRORS NOT RECORDED
is sent to the CP-61 operator.

*.

22

*.

'­

--------------~~~~~--~... ,- - . - If cPcraShes~-i£- must"-; on the next IPL, reestablish
the Logrec in-core record pointers. CP does this by readingin the first physical data record on the Legrec cylinder(machine-check area), and checking the control field. If
the data index bytes reflect the maximum number of bytes
that physical record can hold, CP reads in the next
sequential physical record, repeating this until a record isfound with some space left in it. CP then stores thatphysical data record control field into the machine-check
Logrec in-core record pointers.
CP repeatl3 the above
procedure for locating the next available physical record
for I/O error records, starting at head 2.. and storing its
control field into the I/O error Logrec in-core record
pointers. Error recording can now resume where it left off.
If CP found either the machine check or I/O error areas
full, the message ** LOGREC FULL: _(I/O or M/C) ERRORS NOTRECORDED ** is sent to the CP-67 operator.
A summary of the recording
system for both machine checks
are shown in Figure 11;

and recovery actions of theand I/O and channel checks

23

Problem State

Supervisor State

Recording

CPU Logout on CE Cyl(Date Time etc)

CPU Logout on GECyl

Recovery

M.C. Reflected to V.M.
Message to operator
Message to User

System Dump & Auto RE-IPL
Message to operator

I/O & CHANNELMPX

SELECTOR

CP I/O(!)

Z

V.M.I/O

IFCC
CCC

Channel logout on CE
Cyl. CAW, CSW, DEV. Addr
VaLID, Date Time·<
Msg. to operator

Data
UC
Chain

Sense bytes & up to last 9 CCW's
Time, Date, Dev. Type, Dev. Addr., Seek Addr
CSW
Msg. to Operator at Threshold

Data
UC
Chain

Retry 64 times

IFCC
CCC

Retry 64 times
Addr Known( 7)

c

0:

0

U

I
I

V.M.I/O

CP I/ONot currently implemented

W

,a::

>­a::
w

Reflect to V.M.

No recording
currently
Msg. to operator

Retry up to 9999
Times

Then log user out
Reflect to V.M.

If MPX Chain
Reset - System
must be re-IPLed

>

0
U
w
a::

Figure 11: Summary of CP-61 Error Recording and Recovery

24"

CONDITIONS AND DEVICES INVOLVED IN RECORDING
CP-67 records
various· types of
input/output andmachine-check failures so that the customer engineer canreview the specific types of hardware malfunction which
occur during normal system operation. The customer engineer
can use this information, in addition to CE diagnostic test
information, in monitoring and maintaining system hardware.
I/O Errors
Four types of I/O errors are recorded by CP-67 when auni t check occurs as the result of an I/O operation,. Theseerrors are recorded according to the bit position in sense
byte O.
Error Type Indicator

Sense Bit

1
2

2
3

3

4

4

7

Type of Error
Bus Out
Equipment Check
Data Check
Seek Check (DASD) or
Data Convert Check (24XX)

Counters for each of the above types of errors aremaintained by CP for each I/O device repre.sented by aselector channel device block (RDEVBLOK). This includes all
I/O devices
except shared unit record
equipment andnondedicated terminals.
If the virtual machine is definedwith privilege class C, no errors associated with I/O tasks
originated by that virtual machine will be recorded. This
prevents the recording of intentional errors caused by CE
diagnostic programs.
The first error of a given typeencountered after system IPL is recorded for each device.
Subsequently, every eighth error of this type causes thecounter to. overflow and a counter overflow record to . berecorded.
In cases where two of the five error conditions exist,
the error
is counted
as belonging
to thecountercorresponding to the leftmost bit within sense byte o.
In recording errors, no distinction is made between
permanent I/O failures and temporary, or intermittent,
failures, since the I/O operation is generally under controlof the virtual machine and such information is not known to
CP. For example, the eighth retry of a given I/O operation
to a given device may cause a counter overflow record to be
written. However, the eighth intermittent error of a given
type to any location on a given device also causes a counter25

overflow record to be written.
Furthermore, a counter
overflow record can be initiated by repetition of the samechannel program, or by the intermittent failures of eight
different channel programs. Therefore, successive entries
under a specific counter for a given device may reflect the
failure of unrelated channel programs.
Note that, since CP appears as an extension of the
hardware to the virtual machine, there is no mechanism
within CP to detect repeated failures of the same virtual
machine I/O sequence. Rather, error conditions are reflectedback to the virtual machine as they occur for each event.
Accordingly, only the virtual machine's control program candistinguish between temporary and permanent I/O failures andtake appropriate action. Therefore, the CP error-recording
mechanism cannot distinguish between permanent and temporary
virtual machine I/O errors.
In addition to I/O outboard errors, four types
channel errors are recorded. These are the following:
Error Type Indicator' ,CSW Bit
A
B

C
D

44
45
46
47

of

Type of Error
Channel data check
Channel control check
Interface control check
Chaining check

Every occurrence of a channel check is recorded by
CP-67. Indicators are kept in t.he Real Channel Block(RCHBLOK) for each type of channel check.
Channel errors
which do not log out (channel data check and chaining check)are retrieved by the I/O Error Edit and Print program,
CPIOEREP. Channel errors for which logout data is provided(channel control check and interface control check) are
retrieved by CPMCEREP, and the logout data is formatted by
SEREP1 (System/360 Model 67-1) or SEREP2 (System/360 Model67-2).
The utility program CPIOEREP is provided to retrieve,
edit, and print these I/O error records. The following
information is provided about each recorded I/O error,
channel data check, or chaining check:
Type of error
First encounter or counter overflow
Date and time of error
Device type and device address
Volume serial of DASD if known to CP
Sense and channel status word
The failing ccw string (up to the last nine CCW's) .
Which CCW failed (identified by *)26

Page of GH20-0858-1
Revised January 24, 1972
By TNL GN20-2497

For direct access devices, the last seek address
A sample I/O

Error Record printout isshown in Figure

12.

I/O ERIOlDATE

COUNTER

08/18/70

APLS Y.3

TYPE

CBlIlHlIG CHiCK0PIRST EICOUITEIED

09.16.59'lIKE

DEVICE 'l'YPE 2314
VOL IDNO.

DEVICE 10DR
Sf NSE

235

00 00 00 40 00 00

1100 OLE

A

CSV 00076220 OC0109CC

PAlLING CCV STRING

OP cODEDATA ADDRFLAGS

B'YTE COONTCONTIOL DAT A
B

*.

07

076230

40

0006

31

05Bl'3C'

40

0005

08

0761F8

60

0005

06

04CC78

80

0388

06

C4S0PO

80

0018

06

042634

80

0geC

B

C

C

H

H

00 00 00 16 00 11

Figure 12. sample Printout of I/O Error Record27

A total error count for each device since system IPL isalso maintained by CP-61. If this error count reaches 8, a
message is printed on the operator's console to alert him.
This message identifies the device on which the errors
occurred, the error count, sense information, and status
information. The message will be repeated after a further
256 (or multiple of 256) errors occur. Thus an error
message is printed when the error count on a device reaches
8, 264, 520, etc., in addition to the error recording on
SYSERR. These messages are printed even if error recording
is not in effect because the SYSERR is full.
All nonrecursive machine checks, whether in supervisor
or problem state, are recorded by Cp·61. If a machine checkoccurs in the problem state, the virtual machine user isplaced in console function mode, and receives the message ••MACHINE CHECK.. - CP ENTERED, REQUEST, PLEASE. The system
operator receives the message.. MACHINE CHECK PROBLEM MODE•• USERID =XXXXXXXX, and system operation continues.
If a machine check occurs in the supervisor state, thesystem operator receives the message •• MACHINE CHECK CP-61
SUPERVISOR MODE •• and the system dumps and automatically
re-IPLs.
If multiple machine checks occur while in the
supervisor state, the system operator receives the message•• MULTIPLE MACHINE CHECKS •• RUN SEREP AND RE- IPL •• andthe system goes into the wait state. Multiple machine checks
are not recorded by CP-61.
Each machine-check error record
information:

contains the following

Date and time of error
Machine check code
The five old PSW's(external,
machine check, and I/O)

SVC,

program,Standard
SEREP
output withoutstoragekey
printout. This includes the CPU logout data,
general registers, extended control registers, andfloating-point registers.
A program called CPMCEREP is used to retrieve themachine-check records from Logrec, and then to invoke the
SEREP program to format the data. Instructions for running
the CPMCEREP program as a part of the LOGPRINT CMS command
may be found in the following section, -Instructions for
Recording and Retrieval w •A sample Machine Check Record is shown in Figure 13.

28"----"'.

IIACHINE CHECK
DATE
~,

TIllE

08/211/10~ACHINE

23.54.12

SERH HAS BEEN USED TO FORMAT THE~ACHINE

0000

CHECK CODE

OLD I'ICHCKCHE£K SCAN-OUT AREA

IIODEL 67 MOD 2 SYSTEII ENVIRONIIENT RECORDING EDIT AND PRINT PROGBAII - 6F822
SEBEP INTERFACE ceDE 00
1 00
1 00 a 08
IC0
IC IN LS lIORK REG
ROS PARROS BITSCK 0-42
0-42

ROS BITS
69-99

ROS PARCK 69-99

BEG
AB REGST REGLS weRK BEG
E REG 1 82
EXTENDED IC

1 00
1 00
1 00
1 00
1 00 1 00
1 00
1 00 1 OC
1 60
1 00 1 00
1 00.
1 00 B BEG
EXTENDED
0*00

UNIT 1 CK
UNI! 2 CK
UNIT 3 CK
UNIT 4 CK
Les !lARK CKLCS S·PF CKLCS SDR CKLCS SAR CKSTOR FR 1 DATA CKSTOR FH 1 ADR CK
LCS
lCS
LCS
LCS

.----".

a0 0000000

o 0000000

1

PREY ADB A

K
J
HA
t
0000 0111100001 00000 1100101

ROS PARCK 43-68

SAR

784

1'6-42
1'1-99
G
F
0
B C
A
/ E
/
* H
000000 0000 10 00000 000 1 0000 000000 00000 00 00000

ROS fITS
43-68

Q

PROSAA 785 PROSA8ROSAB 785

(1

0
0
0
0
0
0
0
0
0

N
II
l'
00000 0000 000

1'69-99
1'43-68
/ R T
/ U
* v
000 1 0 0000 1 0000 0 000

*() Q

1 00
1 00
1 00
1 00
1 00
~ 00
1 00
.1 00 DREG
D REG 0*00

F REG
00
1 00 o 04 1 44.
00ABC
1 00 1 00 1 00
STC
2
1 00
1 00
1 00
00
GREG
0
PA LATCH 64-67
1 50 SA LATCHES 1 00
1 00 1 00
1 11111111
EXT INTRPT IIASKDA'I1< CKS

00000000

ADD
ADD
'ADD

F.S.
F.S.
F.S.

IIARK CK

ADP
ADD

0
1
00
00
00
00

00 00 00 00
46 B7 18 00

FETCH 0

TGR
TGB
TGR

a

1
2
2

0

00
00
00
00

00
00
00
00

00
00
00
00

88 98
00 00
00 00
A8 70

00 00 00 00
CO 00 00 00

00 00 00 00
47 72 70 EO

EX'! OLD PSW
SiC OLD PSi
PBG OLD PSlIIlCI OLD PSlII/O OLD PSlI

03
00
07
03
03

06
04
05
06
06

80 00
50 00
AO 00
cO 00
80 00

90
00
00
00

00 8A C800 00 00
OB D9 4000 AS DO00 00 00 00
00 00 00 00
00
00
00
00
00

00
01
00
00
00

00
OD
OF
00
00

00
20

BO
00
00

PROGRAII FINISHED

Figure 13.

Sample Printout of Machine Check Record

29Channel control checks and interface control checks arealso retrieved by the CPMCEREP program.
The following
information is provided about each error:
Sense information
Error type code
Volume serial and channel/unit address of DASD, toor from which data was being transferred whenchannel error occurred
Date and time of error
Channel status word
I/n old PSW

Channel logout data
Channel address word
This data is also formatted by the SEREP program.
,

A sample Channel ErrQr Record is shown in Figure 14.

30

INTERFACE CONTROL CHECKCHANNEL CHECI<
BATE

08/17/70

TIME

D~VICE

TYPE 231~

DEV ICE ADPR

VOLID

SENSE

MEYER1

20.32.41
MODULE

330

00 00 00 40 05 00

P

CSw F007BOD8 OC020000

SEREP HAS BEEN USED Te FORMAT THE CHANNEL LOGOUT AREAHOBEL 67 MOD 2 SYSTEM ENVIRCNMENT REcOntING EDIT AND PRINT PROGRAM - 6P822
SEREF INTERFACE CODE OF

CHUl/UNI'! IlDR

330

I/O OLD PSW

03060330 00000000

CAli

F007BOC8

esw FIELDS
KEY
COM llDE
ONIT STATUS
A'!'IENTION
CHAN END
BUSY
CHAN STATUS

P

07 BO D8pel

DATA CKPROTECT CK
CO UN'!
CHAN-

EIT 2 BC REG
BIT 1 BC REG
SEQ TGRS REG
PROGRAM FINISHED

0
1

0
0

0
0
00 00

o
0
6

STiT MODIFIERDEVICE END
UNIT, EXCEPTIONo1o

INCa fiR LENG'IH
CHAN CTRL CK'CHAINING CKo PROG CK
o l/F CTRL C KoCTRL UNIT END
UNIT CHECKFLAGSIM 1. F.

09

Figure 14: sample Printout of Channel Error Record
For a detailed description of I/O error
CP-67, see CP-67 Program Logic Manual.

recording by

31

INSTRUCTIONS FOR RECORDING AND RETRIEVAL
Print Logrec
A set of CMS files. called CE serviceability files. areprovided with the basic program rna terial for CP-67. These
programs have been included on the CP-67 basic program
material tape as file 5. (see CP-67 Application Directoryfor detai Is. )In order to load these serviceability files into avirtual machine, the customer engineer should execute thefollowing procedure after the CP-67 system source tape has
been attached to his virtual machine as 181 by the system
operator:

1.

IPL CMS.

2.

Issue the TAPE REWIND command.

3.

Issue the TAPE SKIP
4 command to position the tape,to file 5.

4.

Once the tape has been positioned, issue the TAPE
LOAD command to load the files into the virtual
machine.

5.

Issue the MODEL 1 or MODEL 2 command according towhether the Model 67 CPU is a simplex (Modell) or
half-duplex (Model 2). This enables the customer
engineer to obtain the appropriate version of
SEREP for analysis of
the machine-check andchannel error recordings.

Figure 15 is a sample terminal session
initialize the CE serviceability files.

32

to load

and

RI
CI
RI
CI
RI
RI
RI
RI
CI
VI
VI

/~'

cp-67 online
xd.65 qsyosu
login ce
ENTER PASSWORD:<---Type protected password
CP-67 WILL RUN 24·HRS. A DAY, 7 DAYS A WEEK. <-message of the day
READY AT 13.15.10 ON 04/10/70
CPDEV 181 ATTACHED
ipl cms
CMS •• VERSION 3.0 - 04/09/70
R; T=0.05/0.27 13.17.05(See FORMAT note at end of -Defining a Customer Engineer·s
Virtual Machine").
CI
VI
CI
VI
CI
TI

I
I
I
I
I
I
I

tape rewind
R; T=0.03/0.17 13.17.27
tape skip 4
R; T=0.02/0.30 13.18.05
tape load
LOADING • • •Files loaded are listed here•

VIR; T=0.10/0.53 13.19.24
CI
XI
EI
EI
EI
VI

model 2
13.19.31 EDIT LOGPRINT EXECEDIT:OFFLINE PUNCH SEREPX IPLOFFLINE PUNCH SEREP2 IPL
R. T=0.16/0.61 13.19.34

C = Command CP-67/CMS - issued by user
R = Message from CP-67
V = Message from CMS
T = Response from CMS TAPE command
X = Response from eMS EXEC command
E = Response from CMS EDIT command
Figure 15. Sample terminal session to load CE serviceability Files

33

Note that each virtual machine defined for a customer
engineer of an installation must have the privilege'class of
C in order to clear the LOGREC area~
In order to obtain amachine checks which haveshould be followed:

printout of I/O, channel, andbeen recorded, this procedure

IPL 190 Cdo not IPL eMS).
Issue the LOGPRINT command.
If only the I/O error printout is desired, the command
LOGPRINT-IO ,should be issued. If only the mach~ne-checkerror printout is desired, the command LOGPRINT MC should be
issued. A sample terminal session, in which LOGPRINT is
invoked, is shown in Figure 16.
RI
CI
RI
CI
RI
RI
RI
RI

cp-67 online
xd.65 qsyosu
login ce
ENTER PASSWORD:<---Type protepted password
CP-67 WILL RUN 24 HRS.,A DAY, 7 DAYS A WEEK.
THE" TN" CHAIN IS ON THE PRI NTER.
READY AT 13.20.44 on 04/10/70
CP

CI
VI

ipl 190** Note - do not IPL CMS
CMS •• VERSION 3.0 - 04/09/70

CI
XI
XI
PI
XI
XI
XI
RI
XI
RI
XI
XI
QI
RI
VI

logprint.,J "13.30.55 CLOSIO PRINT OFF
CPIOEREP - I/O ERROR EDIT AND PRINT
ALL RECORDS PROCESSED
13.31.03 CP XFER D TO *13.31.05 CP CLOSE OOC
13.31.07 CP PURGE RDR
NO FILES PURGED.
13.31.09 OFFLINE PUNCH SEREP2IPL** CARDS XFERED BY CE**
13.31.16 CP SET CARD ON
13.31.20 CP XFER DOFF
MACHINE CHECK ERROR EDIT AND PRI NT
01 FILES PURGED
CMS •• VERSION 3.0 -' 04/09/70**,.

C = Command CP-67/CMS, issued by user
R = Message from CP-67
V = Message from CMS
X = Message from CMS EXEC command
P = Message from CPIOEREP program
Q = Message from CPMCEREP program
Figure 16. Sample terminal session for running LOGPRINT

34~/.. ...­

Page of GH20-0858-1
Revised January 24, 1972
By TNL GN20-2497

CPIOEREP and CPMCEREP are the CMS programs which print
the I/O error log and machine-cneck log, respectively.
These commands are invoked by LOGPRINT, which is a CMS EXEC
procedure. The source for these programs is included on the
CE serviceability files as CPIOEREP SYSIN and CPMCEREPSYSIN. It is necessary to reassemble these files if theaddress of the CE cylinder is other than 004, or if a 2311
is used as the CP SYSRES. The procedure for modifying theconditional assembly options and reassembling is explainedin the module's
prose.
If these files
need to bereassembled, the macro libraries MACUP, CPMACS, and SYSLIB,
must be included at assembly time. If there is no need toreassemble these programs, CPIOEREP SYSIN and CPMCEREP SYSIN
may be erased from the P-Disk in order to conserve space.
In addition, the version of SEREP wnich is not applicable tothe installation <SEREP1 IPL or SEREP2 IPL} may also be
erased. Standard CE diagnostics, such as DME, and FRIEND,
may not be loaded into the CEIS virtual machine by theprocedure described in previous sections <i.e., by using the
CMS tape load command}. To load these diagnostics monitors
or their diagnostic sections, they must be punched (either
phYSically or virtually) . and read by the CMS "OFFLINE READ
filename fi1etype- command.
Create 3420 History TapeA special CMS EXEC procedure and program are provided
for installations with IBM 3420 tape drives. The EXEC pro­cedure (M3420 EXEC) invokes the HIST3420 program to produce
a history tape. The program scans the I/O error records on
the CE cylinder and selects those error records for the3420 tape drives. The program creates a history record foreach 3420 record and writes the record on a tape. The tapeis written with no label and unblocked l22-byte records andis suitable for processing by the Error Recording Analysis
Program (ERAP) run with OLTSEP.
The M3420 EXEC procedure should be used before the CE
cylinder is cleared but may be run either before or after
the LOGPRINT function since the data on the CE cylinder is
not modified.
The following steps should be followed to create ahistory tape for 3420 error records:
1.

Login as the I CE I virtual machine. This is the same
ID used to perform the LOGPRINT function.

2.

IPL CMS as either CMS or 190 or whatever the installa­tion provides.

35

Page ofGH20-08S8·1
Added January 24, 1972
By TNL GN20·2497

·3.

'r 4.

Request the CP-67 operator to attach the tape (to be­come the history' tape) to the ICE' machine as address
181 with the ring in •.
Issue the CMS command M3420.

The following messages will be issued by M3420 and
HIST3420 procedure:
EXECUTION BEGINS • • •3420 HISTORY TAPE BEING PRODUCEDHIST3420 - 3420 HISTORY TAPE MAKER
ALL RECORDS PROCESSED.Ri

Once the procedure has finished, the ICE' may 'de­tach 181' or 'logout' of CP-67'. The tape should be re­tained for input to the ERAP program with OLTSEP. Thisfunction may also be performed in a virtual machi~e en­
vironment subject to the uspal CP-67 timing and operation
restrictions.
Figure 16.1 shows the terminal printout and user
input when running the M3420 EXEC procedure. It shows
the output produced if the history tape is in a not-readystatus and then is made ready for nOrmal completion, andthe results if the tape is not attached.
Figures 16.2 and 16.3 show the structure and content

of the history tape records produced for the 3420.
Figure 16.4 is a hex' printout of four typical history
tape records.
m3420
TAP2 NOT READY YET(OK - READY NOW)EXECUTION BEGINS •3420 HISTORY TAPE BEING PRODUCEDHIST3420 - 3420 HISTORY TAPE MAKER
ALL RECORDS PROCESSEDRi

cp detach 181
DEV 181 DETACHED
Ri

m3420
TAP2 NOT ATTACHEDTAPE DRIVE NOT READY
Ri• Figure 16.1
35.1

Terminal printout and user input underM3420 EXEC procedurefPage ofGH20.()85S-1
Added January 24, 1972
By TNL GN20-2497

/",

o

7

6

1

RecordOP

RecordSwitches

System

Type

8

Count

Spare

'.1

Time

Date

16
Spare

Max
MCEL
LengthModel
Number·CPU
Serial;..-:-­

24

Job ID
32•
r

Failing CCW

.'

40

•
f\

CSW

48
DeviceDependent
Count

56

Failing
Channel &: Unit
Address
Primary

SDR
Count

Channel &: Unit
Address

Device Type

Numberof .
I/ORetries

Sense
Count

64
Sense Data

88
Variable Field
for Dev. Dep·and SnR
infor·mation if present
122• Figure 16.2 Structure of 3420 history tape.

35.2

Page of GH20-0858-1

Added January 24, 197.2
By TNL GN20-2497.~.

Record Type- Set to x' 30"

OP System- Set to x'63' = CP67 Release 3.1

Switches-.Set to x'03000000'= Relocate

Record Count- Set to x'll'= Indicate fixed record

Date- Actual DATE ERROR was RECORDED - from LOGDATETime-' Time FAILURE was RECORDED - from LOGDATECPU Serial= OBR unit check·

EC Mode360

Model Number= Model 67= 36-byte variable field- Set to x'0024'- Set to "CP67-3.l" = User ID not available '-'~- Actual CCW that had unit check = taken from LOGCCWS- Actual CSW that showed error status = from LOGCSW- Set to x'0067'

Max MCEL Length
Job ID
Failing CCW
Failing CSW

Device Dependant Ct. - Always set to zero'
Failing Address- Address of failing unit - taken from LOGADDR

Device type

- Set to '0000S003' - 3420 device type

SDR Count- Always set to zeroPrimary Address- Address of failing unit - taken from LOGADDR

Number of retries- Set to zero

Sense count- Set to x'OOlS' - 24 sense bytesSense data

- 24 bytes of sense information - from LOGCCWS

Variable field- To be used in future for device dependent and SDR data.

• Figure 16.3!:,-.

Contents of 3420 History Tape,/"\..

35.3

I

122

JOb 3,nOOOOOOII00 102111152204F003000000006124C301F6F1I>0F148Fl0102C9CB205C0125F003
800 ROF 00000000 00 03900000800)00 0003900000 00 1808441 OOC 00 4004000000000000814 30.2. .1 •000000lA000800000000000000000000000000000000000000000000000000000000000000000000
0000.

-• •••• ••-•••••••• 0 •••••••CP61. 3.1 •• J••-, •• 0. •••........•.........••••....
............••........•••...•..........................•

.

•..

2

122

30~ 30300000011001021111522051'003000000006724C3D7F6f160FHBF 10 101C9CB20SC0315FooJ
8D480FOOOOOOOOOOOJ900000800J00000390000000180844100COO40040000000000001143021.1.
0000001 AOOOBOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO 00000000000000000000000000
0000

3

122

"

122

••••••••••••••• 0 •••••••CP61.3.1 •• I ••••• 0 ••~ • • • • • • • • • • • • • • • • • • ~. • •• • I'"~ • • • • • • • • ••••......•....•......•...•......••.••...•••• • •••

I"•

301> 303000000 II 00 102 271183959F003000000006 7 2 4C 3D 7F6f1bO F348F 1020) 764C245C11'FF'00 3
16480f001C84000003900000B00300(00)900000001808C:OFF04014004000000000000114302IA••
000000U01CFOOOOooOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO0000000000000000000000
0000........................... "' . ........ ....••••..•...................................•••••

30.63030000001100 1022 711S4000F003000M0006124C307F6F760nUF 1020 3A1CC21t5C 1f'FFJ'OO3
A8C80e001C8400000J90000080Q100000390000000180.COFF040140040000000000001143021All
0000001AOICeOOOoooOOOOOOOOOOOOOOOOOOOOOOOQOOooOOOOOOooOOOOOOOOOHOOOlIooOOooeo.ooO
0000. . . . . . . . . . . . . . . O••••••• CP67.1.1 ••••••••••" ••••••••••••••••••••••• M••••••••••••••

Figure 16.4.

••••••••••••••• O••••••• CP67.1.1 •••••••• 0 ••'0.-.

•........................................•-..

.

Hex Printout of Four History Tape Records.

f1&~!_Logr~£

In order to clea~ the CE cylinder, the programs CLEARIO
and CLEARMC may be invoked.
These programs execute a
special 'diagnose' instruction (code X'1C')
to invoke a
CP-67 routine that clears the relevant section of the CE
cylinder SYSERR
and starts error recordingfrom thebeginning.
CLEARIO and CLEARMC may be executed at thediscretion of the customer engineer, but should always be
executed when the message ** SYSERR FULL; (I/O or MC) ERRORSNOT RECORDED appears at the operator's terminal. Note that
the LOGPRINT should be run before clearing Logrec.
f~2]g~-2~~Counter

­

Limit

The customer engineer may wish to change the value atwhich the error counter overflows for one or more types of
I/O error. This location (the entry point CTRLIM in the CP
Load Map) contains a one-byte counter limit for each of thecounters types 0-4. Counter 0 is currently set to zero;consequently no command reject errors are recorded. Counters
1-4 are each set to 08 so that every eighth error of a given
type is recorded.
To display the current value of thecounters, the system programmer can display the address
indicated for CTRLIM in theload map.
He may also
dynamically modify these counter limits.
If a count isreset to 01, every error of this type is recorded, if thecounter is reset to 02, every second error is recorded, etc.

35.4GH20-0858-1, Page. Modified by TNL GN20-2620, May 15, 1973
APPENDIX A:

STATUS OF DIAGNOSTICS UNDER CP-67-------------------------------- -------------The following notes apply to the tests in this appendix:'}

Note 1.

Time dependency routine

Note 2.

Dynamically modified CCW sequence

Note 3.

Diagnose instruction used

Note 4.

Cause of failure has not been determined·

Note 5.

The core addresses in the SDO messages should be
adjusted to reflect the appropriate Diagnostic
Monitor being used.

The decision whether to include test
answers to the following questions:sections depends•

What devices
test system?

are available in system•

What test sections are available on diagnostic tape?

•

Would the test' section
should not.• )•Is the test too cumbersome to run under CP-61.?

cause

on

configuration ofa systemcrash?

(It

Due to varying system load condition~, it is possible that
not all of the documented errors will occur; it is also
possible that some other errors could occur.
DASD diagnostics may not function properly on virtual
minidisks. In order to ensure correct operation, the DASD
device that is to be exercised by the diagnostic test
sections should be dedicated in its entirety to the virtual
machine by the use of the ATTACH command.

36

2820-2301 Test
Test section

691-3
692-3
693-3
694-4
695-3
696-3
697-3
69A-4
69B-3

Reason for Exception

None
None
None
None
None
None
None
None
Note 1

Exception Message Number(Might not work on two-drum system)

Msg. 1, 2

Msg. 1*SDO F69B3 02 007DOE 0101
LISTING ADDRESS 00~102
CHECK THAT BUSY CONDITIONS ARE RETURNED CORRECTLY.
CSW COMMAND ADDRESS - 006AF8, CSW COUNT - 0000
CONDITION CODE ERROR. ReD -00- EXP -01­
STATUS OC 00 RCVD
00 00 EXPCTD

Msg. 2*SDO F69B3 02 007F2E 0101
LISTING ADDRESS 0072A4
THIS ROUTINE HAS FAILED
DEPENDENT ROUTINES WILL NOT BE RUN

37

2841-2311 Test

Test Section

603-6
604-6
605-6
606-1
607-1
608-1
609-1
60A-6
610-2
612-2
613-3
616-0
617-0
618-1
61B-1

38

Reason for Exception

None
None
Note 1
Note 1
Note 1None
None
Note 1
Note 4
None
None
None
None.
None
None
None
I

Exception Message .Number

Msg. 1r 2
Msg. 3Msg. 4 r 5 r 6
Msg. 7
Msg. 8, 9

SF6056· Msg. 1 *SDO
F6056 01 0069F6 0391,..
SHLD GET eel ON SEEK INDICATING CUB BUT DID NOT esw IS 00006A300eoooooo· Msg.

2 *SDO F6056 03 006DF6 0391
ERR INV OP 01 esw SHLD BE 00006S2002000001 esw IS 00006S2S0eOOOOOl
SNS DATA SHLD BE 800000C8 SNS IS 000000e8
T

Msg.

S
F6061
3 *SDO F6061 01 0063A4 0391
ERR CSW 0000662002000011 esw SHLD BE 0000662072000011
SNS S01000CS SNS SHLD BE S01000es
T

S

F6071
F6071 01 0063A4 0391
ERR esw 000064F002000009 esw SHLD BE 000064F072000009
SNS S01000es SNS SHLD BE S01000es
Msg. 5 *SDO F6071 01
0063A4 '0)91
ERR esw 0000655802000009 CSW SHLD BE 0000655872000009
SNS 801000CS SNS SHLD BE'S01000es
Msg. 6 *SDO F6071 01
0063A4 0391
ERR CSW 000067100200000E CSW SHLD BE 000067107200000E
SNS 801000e8 SNS SHLD BE 801000e8
Msg.

f\

4 *SDOTS

F60A6
F60A6 01 00691E 0391
ERR-SPACE COUNT CAW 006A60
EXP esw 00006B7872000003 ACT esw 00006B7S02000003
EXP SNS 801000e8 ACT SNS 801000e8
Msg. S *SDO F60A6 02
00691E 0391
ERR-SPACE COUNT CAW 006A60
EXP esw 00006BDOOCOOOOOO ACT CSW 00006BDOOE400000
EXP SNS 000000C8 ACT SNS osooooe8
EXP RDDATA 2222222222
ACT RD DATA 2222222222· Msg. 9 *SDO F60A6 02
00691E 0391
ERR-SPACE COUNT CAW 00D416
EXP CSW 00006BFOOEOOOOOO ACT esw 00006BFOOE400000
EXP SNS OSOOOOC8 ACT SNS OSOOOOC8EXP RD DATA 11112222222222FFDDCCFFFFFFFFFF
ACT RD DATA l111EEEECCFFFFFFFFFFFFFFFFFFOO
Msg.

7 *SDO'I'

39

2314 Test
Test Section

6AO-3
6A1-3
6A2-3
6A3-3
6A4-3
6A5-3
6A6-3
6A7-3
6A8-3
6A9-3
6AA-4
6AB-3
6AC-3
6AE-3
6AF-3
6BO-3
6B1-3
6B2-3
6B3-3
6BA-3
6BB-3
6BC-3
6BD-4

40

Reason for Exception

None
None
None
None
None
Note 1
Note 1
Note 1None
None
Note 1
Note 4'None
Note 1
None
Nonec
None'
None
Note 1
None
None
None
None
None

Exception Message Number

Msg .. 1
Msg. 2
Msg. 3, 4, 5
Msg. 6, 7
Msg .. 8, 9
Msg. 10, 11.~

Msg. 12.~

19. 1 *SDO

F6A53 01 0065B2 0331
saLD GET CCl ON SEEK INDICATING CUB BUT DID NOT CSW IS 000065E80COOOOOO
T

S
F6A63
Msg. 2 *SDO F6A63 01 0063B4 0331
ERR CSW 0000663002000011 CSW SBLD BE 0000663012000011
SNS 801000400000 SNS saLD BE 80100040XXXX
T

S
F6A13
Msg. 3 *SDO F6A13 01 0063B4 0331"
ERR CSW 0000650002000000 CSW SHLD BE 0000650012000009
SNS 801000400000 SNS SHLD BE 80100040XXXX
Msg. 4 *SDO F6A13 010063B4 0331
ERR CSW 0000656802000000 CSW SHLD BE 0000656812000009
SNS 801000400000 SNS SHLD BE 80100040XXXX
Msg. 5 *SDO F6A13 01 0063B4 0331
ERR CSW 000061200200000E CSW SHLD BE 000061201200000E
SNS 801000400000 SNS SHLD BE 80100040XXXX
Msg. 6 *SDO F6AA4 01 00635C 0331
ERR-E R A S E CAW 006458.
EXPCSW 000064181COOOOOO ACT CSW 000064180COOOOOOEXP SNS 00000040XXXX ACT SNS 000000400000
EXP READ OOC3000003 ACT READ 00C3000003
Msg. 1 *SDO F6AA4 02 00658A 0331
ERR-SPACE COUNT. CAW 0061FO
EXP CSW 0000681812000003.ACT CSW 0000681802000003
EXP SNS 80100040XXXX ACT SNS 801000400000
Msg. 8 *SDO F6AA4 02 00658A. 0331
ERR-SPACE COUNT CAW 006840
EXP CSW 000068600COOOOOO ACT CSW 000068600F400000
EXP SNS 00000040XXXX ACT SNS 080000400000
EXP RD DATA 2000000002
ACT RD DATA 2000000002
Msg. 9 *SDO F6AA4 02 00658A -0331
ERR-SPACE COUNT CAW 006860
EXP CSW 000068800EOOOOOO ACT CSW 000068800E400018
EXP SNS 08000040XXXX ACT SNS 080000400000.
EXP RD DATA E1E1E1E1E1E1E1E1E1E1E1E1E1E1E1E1E1E1E1E1FFFFXX1DFF
ACT RD DATA E100000000000000000000000000000000000000C300030000
Mag.l0 *SDO F6AC3 02 0064AE 0031~.
ERR "10 EXPECT CC = 2 ACTUAL CC = 0
Co Mag.ll *SDO
F6AC3 02 006504 0331 ­ERR-"IO FAILED TO STOP CHAIN ON WRITE-DID NOT PAD WITH ZEROS
Msg.12 *SDO F6B23 01 005394 0331
CSW 0056C00000200001 CSW SOLD BE 000056COOCOOOOOl SNS 000000400000
SNS SHLD BE 000000400XOO CAW 00005698
ERR WHEN SCAN FO KEY DATA REMAINDER OF CYL, AFTER DEF TRK VIA 6TH SNS BYTE
TO LOOP ERR TURN ON SSWO~"

41

Page of GH20·08S8-1
Revised January 24, 1972
By TNL GN20·2497

2402-2403 Test
Test Section

Reason for Exception

None
None
None
Note 1
Note 1
Note
Note 1
None
None
None
None
None
None
None
None
None

501-8
502-8
503-8
504-8
505-8
506-6
507-7
508-9
50A-1
50B-1
50C-1
500-0
50E-1
50F-3
510-1
51B-5

Exception Message Number

Msg.
Msg.
Msg.
Msg.

"

1
2, 3, 4, 5, 6
7

8, 9, 103420 OLTS Test

M

V
E

A

I
H

M
0
D
E

E

L

C
H

T
E

S
T

R

L

S
I
0

V

0
P
T
I
0

E

N

R

N

L

S

S

E

C
0
M

E

R

M
B
H

R

0

T
S

------------------------------------------------------------------... --­
3420
None
A
B
C
D
E
p

NFE,PP(3)

None
None
Hone

R'l'IIl
None
_2
None
RD2

G
H
I
J

HANG

ilone

11
L

Hone
None
None
None
None
None
None
None
None
Hone

M
N

0

p

Q
R

S
T

3420 OLTS failures

3420 Test E Routine I-timing dependency failure
IWiGS SYSTEM DO NOT lWH

3420 Test G Rout.ine 2-timing dependency failure

3420 OLTS Test

RTNI
None
RTN2
Hone

Hone
Hone
Hone

42

'.

Msg. 1 *SOO F5048 29 0064F4 0181
MSG F COND CO ERR NRZISIO 006672 CAW 006CFO
CCW 04006E18 20000006
ACT CC 1 EXP CC 0
ACT INT STS 0400-EXP INT STS 0000
CSW
EXP FIN STS 0000
SNS LINK ADR 006BB2
Msg. 2 *SOO F5055 32 00695C 0181
ACT INT STS 5000-EXP INT STS 2400
MSG 45

Msg. 3 *SOO F5055 32 0064F4 0181
MSG F COND CO ERR NRZISIO 06672 CAW 006DE8
CCW 04006E30 20000006
ACT CC 1 EXP CC 0
ACT INT STS 0400-EXP INT STS 0000
CSW
EXP FIN STS ~OOO
SNS LINK ADR 006966
SNS 00 00 00 00 00 00
Msg. 4 *SOO F5055 34 006AC8 0181
ACT INT STS 3000-EXP INT STS 3400
MSG 51

Msg. 5 *SOO FSOS5 34 0064F4 0181
MSG F COND CO ERR NRZISIO 006672 CAW 0060F8
ccw 04006E30 20000008
ACT CC 1 EXP CC 0
ACT INT STS 0400-EXP INT STS 0000
CSW
EXP FIN STS 0000
SNS LINK AOR 006AD2
SNS 00 00 00 00 00 00
Msg. 6 *SOO F5055 35 . 006B70 0181
ACT INT STS 0400-EXP INT STS 1400
MSG 53
SNS 00 44 03 00 00 00
Msg. 7 *SOO F5066 44 0064F4 0180
MSG E STATUS ERROR NRZISIO 006A2A CAW 006028
CCW OCOOOOOO 20000004
ACT CC 0 EXP CC 0

43

ACT INT STS-EXP IN!' STS 0000
esw 00006030 oe010003
EXP. FIN STS oe20~

Msg. 8S
F5077*SDO F5077 51
MSG 74
SNS 00 lJ4 03

006A54

0182

00

00

00

Msg. 9*SOO F5077 52 0064FlJ 0182
MSG E STATUS ERROR NRZISIO 006B50 CAW 006CE8
CCW 01000000 20001FFOACT CC 0 EXP CC 0
ACT INT STS-EXP INT STS 1000
EXP FIN STS 0000

Msg. 10*SOO F5077 52 006B6C
MSG 76
SNS 00 4lJ 03 00 00 00
UNITS RUN 0182,XXXX

44

0182

XXXX

XXXX

XXXX

XXXX

XXXX

XXXXNRZI

2703 Test
Test Section

Reason for Exception

C21
C2B

Note" 1
None

Exception Message Number

Msg. 1, 2

Msg. 1 *SOO EC2l1 01 005BAC 0030
PRELIMINARY I/F CHECK WITH TIO, NOP, SAD.
TIO DID NOT STORE CSW
LINK 005354
CC ACT 0
CC EXP 1
Msg. 2 *SDO EC2l1 06 005BAC 0030
TEST INITIAL ~TATUS CONDITIONSSENSE COMMAND ACCEPTED, EXPECTING CONTROL UNIT BUSY
LINK 005906
CAW 00 006500
CC ACT 0
CC"EXP 1
CCW

SENSE

ADDR 006414

FLAGS=SLIBYTE CT=Ol

/~.

45

2540 Test
Test section

804-1
810-3
811-2
819-0
820-3
821-3
822-0

Reason for Exception

None
Note 1None
None
Note 1
None
None

Exception Message Number

Msg. 1, 2
Msg. 3, 4

Msg. 1 *SDO F8103 09 0063B2 OOOC
TST 0250
ADR 006AB4 LINKADR 0061AC SIO
CAW 006008<
CCW 02006740 00000050
CC 1 EXP
CC 1 ACTCSW 00000000 10000000 EXP
CSW 00000000 04000000 ACT
CSW 00000000 04000000 EXP
SNS 00 EXP
SNS 00 ACT
SET SS 0 ON FOR LOOP ON SIO, SS 1 ON FOR TIO SIO LOOP
Msg. 2 *SDO F8103 10 0063B2 OOOC
TST 0290
AOR 006B08 LINKADR 0061AC SIO
CAW 006010
CCW OC006740 00000001
CC 1 EXP
CC 1 ACTCSW 00000000 14000000 EXP
CSW 00000000 04000000 ACT
SNS 00 EXP
SNS 00 ACT
SET S5 0 ON FOR LOOP ON SIO, SS 1 ON FOR TIO SIO LOOP
*SOO F8103 11 0063B2
T5T 0350
ADR 006B64 LINKADR 0061AC SIO

46

OOOC

,

2703 Test
Test section.'­

Reason for Exception

Note. 1
None

C21
C2B

Exception Message Number

Msg. 1, 2

Msg. 1 *500 EC211 01 OOSBAC 0030
PRELIMINARY I/F CHECK WITH TIO, NOP, SAD.
TIO DID NOT STORE CSW
LINK 0053SQ
CC ACT 0
CC EXP 1
Msg. 2 *SDO EC211 06 OOS.BAC 0030
TEST INITIAL &TATUS CONDITIONSSENSE COMMAND ACCEPTED, EXPECTING CONTROL UNIT BUSYCAW 00 006Soo
LINK 005906
CC ACT 0
CC ·EXP 1
CCW

SENSE:ADDR 006414

FLAGS=SLIBYTE CT=01q5

2540 Test
Test Section

804-1
810-3
811-2
819-0
820-3
821-3
822-0

Reason for Exception

None
Note 1None
None
Note 1
None
None

Exception Message Number

Msg. 1, 2
Msg. 3, 4

Msg. 1 *SDO F8103 09 0063B2 OOOC
TST 0250
ADR 006AB4 LINKADR oo61AC SIO
CAW 006D08
CCW 02006740 00000050
CC 1 EXP
ec 1 ACTCSW 00000000 10000000 EXP
CSW 00000000 04000000 ACT
CSW 00000000 04000000 EXP
SNS 00 EXP
SNS 00 ACT
SET SS 0 ON FOR LOOP ON SIO, SS 1 ON FOR TIO SIO LOOPf

Msg. 2 *SDO F8103 10 0063B2 OOOC
TST 0290
ADR 006B08 LINKADR 0061AC SIO
CAW 006Dl0
CCW OC006740 00000001
ce 1 EXP
CC 1 ACTesw 00000000 14000000 EXP
CSW 00000000 04000000 ACT
SNS 00 EXP
SNS 00 ACT
SET SS 0 ON FOR LOOP ON SID, SS 1 ON FOR TID SIO LOOP
*SDO F8103 11 0063B2
TST 0350
ADR 006B64 LINKADR 0061AC SIO

46

oooe

-:

CAW 006008
CCW 02006140 00000050
CC 1 EXP
CC 1 ACTCSW 00000000 14000000 EXP
CSW 00000000 04000000 ACT
SNS 00 EXP
SNS 00 ACT
SET SS 0 ON FOR LOOP ON SIO, SS 1 ON FOR TIO SIO LOOP
Msg. 3 *SDO F8203 06 006388 0000
'l'ST 0150
ADR 006818 LINKADR 0061AE SIO
CAW 006F58
CCW F5006608 20000001
CC 1 EXP
CC 1 ACTCSW 00000000 14000000 EXP
CSW 00000000 04000000 ACT
SNS 00 EXP
SNS 00 ACT
SET SS 0 ON FO~ LOOP ON SIO, SS 1 ON FOR TIO SIO LOOP
Msg. 4 *SOO F8203 07 006388 0000
TST 0210.
ADR 00680A LINKADR 0061AE SIO
CAW 006F58
CCW 410066D8 20000001
CC 1 EXP
CC 1 ACTCSW 00000000 14000000 EXP
CSW 00000000 04000000 ACT
SNS 00 EXP
SNS 00 ACT
SET SS 0 ON FOR LOOP ON SIO, SS 1 ON FOR TIO SIO LOOP

41

1403 Test
Test section

F830
F832

Reason for Exception

Note 1
None

Exception Message Number

Msg. 1, 2

Msg. 1 *SDO F8304 06 006318 0010
TST 0240
ADR 006 ADC LINKADR 00619E SIO
CAW 006ECO,
ccw 05006881 00000084
CC 1 EXP
CC 1 ACTCSW 00000000 14000000 EXP
csw 00000000 14000000 ACT
SNS 00 EXP
SNS 00 ACT
SS 0 ON FOR LOOP ON SIO, SS 1 ON FOR TIO SIO LOOP
Msg. 2 *SDO F8304 12 006318 0010
TST 0480
ADR 006D26 LINKADR 00619E SIO
CAW 006ECOCCW OC006881 00000084
CC 1 EXP
CC 1 ACTCSW 00000000 14000000 EXP
CSW 00000000 04000000 ACT
SNS 00 EXP
SNS 00 ACT
SS 0 ON FOR LOOP ON SIO, SS 1 ON FOR TIO SIO LOOP

48~

APPENDIX B: CP-61 ON-LINE TESTING USER·S GUIDEPURPOSE

I
I
I
I
I
I
I

The purpose of this series of EXEC procedures is to provide
the ability to run DM-controlled diagnostics or stand-alone
programs, including I/O exercisers, in a CP-61 virtual
machine, to permit on-line testing and exercising of I/O
devices. This
document describes
only theoperatingprocedures for the on-line testing system. Generation andmaintenance of the system is described in Appendix B.

I
I
I
I
I
I

The programs to be run reside on disk within the system, andare called for execution using only a few simple commands. A
command is provided to accomplish the attaching of I/O
devices to the virtual machine in which the diagnostics areto be run. This permits conflicts between real and virtualunit addresses to be automatically avoided.

I
I
I

The objective has beeri to make on-line testing available to
all CE·s, regardless- of their level of acquaintance with
System/360 Model 61.
REQUIREMENTSI
I

Use of this system requires that the CE have access to aterminal (2141 or equivalent) to control testing. The
lon-line testing system must have been previously generated
I under CP-61 (per the Generation and Maintenance Guide,
I Appendix C), and the CE must know the USERID and PASSWORD
I under which it was generated.
OPERATING PROCEDURES

I

Concepts
CP-61 is an operating system designed to run on a System/360
model 61. It is a time-sbaring system; that is, a system
which supports many users, one at a time, but services allusers so quickly that each seems to have complete control ofthe system to himself. Eacb user communicates with thesystem from a terminal, such as a 2741. For each user in thesystem, CP-61 creates a virtual system, in other words, eachuser in the system thinks that he has a System/360 system­
which is entirely his own. The user can do anything withthis virtual system that he could do with a real System/360,
except for a very few restrictions. From his terminal, theuser can type CP-61 commands to perform all of the console

49

I
I
I
I
I

functions of a real machine: store, display, ipl, system
reset, psw restart, etc. He can also start and stop his
virtual machine at will. CP-67 also makes the user's
terminal appear to be the console 1052 of his virtual
system.

I
I
I
I
I
I

The CE also has his own virtual System/360 for testing
purposes. It is time-shared with all the other users of thesystem, and can run I/O diagnostics under DME, or run I/Oability to use I/O
exercisers such as Friend-3. The
exercisers on line will be found especially helpful inrepairing I/O problems.
Just as a real System/360 has much more I/O than a 1052, avirtual system also has various associated virtual I/O
devices. The actual card reader, card punch, printer anddisk drives have their counterparts in the virtual 360. Ifa
program in the v1rtual machine performs START I/Os andwrites on device OOE, CP-67 intercepts the START I/O andplaces the data on disk to be printed later when a realprinter in the computer room becomes available. In the sameway, a deck of cards placed in the real reader in thecomputer room with a USERID card in front of it will
instruct CP-67 to put the cards on disk and -feed- them tothe virtual reader (address OOC) when a START I/O is issued
to i t in the virtual system. The virtual card punch operates
in the same way; data punched on device OOD from a virtual
machine is held by CP-67 on disk, and is punched on the realcard punch when it is available. The two virtual disk drives
are actually parts of disk packs maintained by CP-67; they
appear to be -mini-disks- with only a few cylinders to thevirtual system. Diagnostic programs and I/O exercisers are
stored on one of them. The other one is an operating systemcalled CMS. CMS will be used to prepare a set of diagnostics
to be run. More about CMS later.

I
I
I
I
I
I
I
I
I

Thus far we have discussed a virtual system and its virtual
I/O, which allow the user to run any program that he could
run on a real System/360. There is one more thing that isneeded to test a failing device. The system operator canissue a command to ATTACH a real I/O device to aCE's
virtual machine (or any other virtual machine). When adevice is attached, it becomes part of one virtual machine
only. This is the way we will gain access to any I/O device
that we wish to test.
RESTRICTIONSThere are a few
virtual machine.

50

things thatcannot be

done

in a

CP-67 .

GH20-0858-1, Page Modified by TNL GN20-2620, May 15, 1973
1.

The diagnose instruction is not supported. Thismeans that all CPU, channel, and core diagnostics will
not function.

2.

Self-modifying
run properly.

channel programs

will notalwaysTime-dependent programs may not. run properly. Thisis because the real system is being shared with otherusers~ It willshow in some diagnostics as unexpectedcondition codes on I/O instructions or failure to get
control unit busy status when the diagnostic expects
it. The section, "Messages and Printouts", in thisguide shows some examples of the type of error printout
that may occur from this cause. The CE should learn tore~ognize thistype of message and not treat it as a
hardware failure.
Since itdepends on the otheractivity in the system, it is difficult to predict
exactly where this type of printout will occur.
DASD Diagnostics may not function properly when
run on minidisks. . To ensure correct operation, theDASD devic~ to" be exercised by the diagnostic test
section should be dedicated in its entirety to thevirtual machine by use of the "ATTACH command.

.

.

LOGIN
The following is a sample LOGIN procedure. The lines that
the CE must type are indicated by asterisks at the left. The
first message is printed by CP-67 after communication isestahlished with the system (by dialing the telephone number
assigned and going to data mode if a dial-up terminal isused).
.

**

cp-67 online
xdh65 qsyosu
login xxxxxx(HIT THE ATTN KEY FIRST)(xxxxxx IS YOUR USERID)(USE •• login •• OR •• I •. ) "ENTER PASSWORD:
yyyyyy(YOUR UNIQUE PASSWORD)READY AT ~1.01.52 ON OS/22/70

At this point the virtual System/360 is ready to use. CP-67
may now be asked to perform any console function on thesystem. To run any of the diagnostic programs or" exercisers
already stored on disk, a program called eMS must be used
first. The CP-67 IPL command is used to ipl CMS.

51

GH20-0858-1, Page Modified by TNL GN20-2620, May 15, 1973eMS IPL
The virtual disk drive 190 has alogging in to CP-67, type •••ipl 190(OR •• icopy of CMS on

it. After

190 •• )A message will be received when CMS is loaded •••CMS •• VERSION x LEVEL y(date)

The commands can now be given to start a test run. The UNIT
command is used to ask the system operator to attach the IIO
device to be tested. The DIAGS command may then be used to
select those diagnostics or stand-alone programs that are to
be run and ipl them. These commands are described in thefollowing paragraphs.
UNIT COMMAND
The unit command issuei messages to the system operator torequest him to ATTACH an 1/0 device to the virtual system sothat the CE can test it~ When the message confirming thatthe device has been attached is printed, hit the ATTN key tocontinue. To attach lID device 230, type •••unit 230
The unit command will cause messages to be printed if a
device is requested whose real address is the same as one ofthe virtual devices. lor example ••••
If it is desired to attach the real printer OOE, by typing••• unit OOe ••• CP-67 cannot attach this device with that
address, because the virtual or spooling printer is OOE. In
this case, OOE (the real printer)
will be attached to thevirtual system as 004, and can be addressed as 004. Thus,
the CE need only give the real address of the device to betested. The
unit command
will prevent
any possible
conflicts.
The attaching of multiple devices may also be requested with
one UNIT command. If ~t is desired to test devices 380, 381,
and 233, type ••••
unit 380 381 233
Unit addresses should always be typed as 3 digits.

52

GH20-0858-1,

P~ge

Modified by TNL GN20-2620, May 15,1973

DIAGS COMMAND~

Execution of the DIAGS command results in the programs
chosen being placed in the virtual card reader of thevirtual system, and the reader being IPL 1 ed. For example, toload FRIEND, type •••diags friend

52.1

If you wish to run a OM-controlled
section 504, type •••I

I
I

diagnostic, for example

diags 504
DME will automatically be "placed in front of section 504.
The same results will occur if the following is typed •••Idiags dme 504
Multiple sections may be requested••••diags 501 502 503 509

I
I

I
I
I
I

or ••••
diags dme501 502 503 509
IPL
programs
intermixed ••••

andDM-controlled

diagnostics

may

be

virtualcard

diags 601 ~03 friend 606
,

I
I
I

I
I

The precedingdeck••••

will

generate theDME,601,6~3,FRIEND,DME,606

Note that every
in front of it.

group of sections requested

Pre-defined groups of diagnostic
requested. For example••••I
I
I

follOwing

sections

has DME placed
may

also

be

diags 2311
will load all of the 2311 disk drive diagnostics, with DMEagain automatically inserted in front.
Some of the groups of sections which may
in your system are ••••
2311••••••
2841••••••
2313.......
2314••• "• ••2400 ••••••

have been defined

2311 DISK DRIVE
2841 CONTROL UNIT
2314 DISK DRIVES
2314 CONTROL UNIT
24xx TAPE DRIVESThe naming of section groups, and the diagnostic sections
and IPL programs present in the system are under the controlof the CE responsible for maintenance of the on-line testing53

system. He should be consulted for specific information.
PROGRAM CONTROLThe successful completion of the DIAGS command results in
IPL'ing the virtual card reader of the system r overlaying
CMS with the first program requested. Control of~the virtual
machine then passes to that program.. The message formats
from this point on are those of the program being run. If an
unrecoverable software problem causes loss of control of the
programrthe entire card deck can bere-positioned to thestart and re-IPL'ed by entering CP-67(ATTN key)andtyping ••••

"

c c
i c

If it is not desired to have the cards in the virtual reader
saved in this waYr the word NOSAV should be given as aparameter to the DIAGS command r e.g,. • •••diags 601 602 nosav
CONSOLE FUNCTIONS

I
I
I
I
I

virtual machine can be started r- stopped r and controlled in
the same way as a real 'machine. The 2741 ATTN key is used toalternate control between CP-67 and the virtual machine's
simulated 1052. For example, to generate a 1052 request key
operation in the virtual machine ••••

I
I

1.

Press the ATTN key once. This stops the virtual machineand passes control to CP-67.

I
I

2.

Press the ATTN key again. This restarts the virtual
machine and simulates a 1052 attention interrupt.

A

54

The following chart shows the various ways in whic~
control is passed by the user between CP-61 and theprogram(s) in a virtual machine •••••
r

I
I
I
I

CP-61

LOGIN----t--> (CP.... 61 READY msg)

I
I
I
I
I
I
I
I
I
I
I

I
I
I
I
I
I

VIRTUAL MACHINE

I
I
I
I
I
I

nipl 190" ---------t....->(CMS VERSION x LEVEL y)IfInuni t n COMMAND--FORCES IPL ooc <----1--- ndiags" COMMAND

I
I

I
- I

----------------------t--> DME, FRIEND, etc.

.

I

(STOP ,VIRTUAL M/C) <--1--- 2141 ATTN KEY-

I

2141 ATTN KEY -----t-->ATTENTION INTERRUPTI"e- -----------1--> EXTERNAL INTERRUPTI"b- -----------t--> START VIRTUAL M/C-d" (DISPLAY CMD)
"st" (STORE CMD)

I
I
I
I
I

(CP ENTERED msg) <----1--- DISABLED WAIT

I
I

55

The following chart shows theand display commands •••••I
I
I

use of the

TO DISPLAY

TYPE

d xxxxMain storage addr xxxx
(1 word)Main Storage addresses
xxxx to yyyy
(nearest fullword)(xxxx and yyyy are hex
addresses, 1 to 6
digits long)d xxxx-yyyy

GPR n
(n
is
gpr
no ... 1 to 15) I
I

1I
GPRs n to mI(nandmare 1 to 15 )I
I
l'PR nI
FPRs
n to mI
I
CURRENT PSW
I
I

I
I
I
I
I
I
I
I

I
I
I
I
1

TO STORE IN
Main storage addr xxxx
Data hhhhhhhh(hhhhhhhh is hex data
one or more fullwords
separated by blanks)

CP-61 store .

I
I
I
I
I
I
I
I
I

d gn
d gn-md yn
d yn-md psw

TYPE

st xxxx hhhhhhhh

GPRs starting at GPR n(each word into next
higher GPR)st gn hhhhhhhh hh •• etc.

FPRs starting at FPR n

st yn hhhhhhhh hh •• etc.

CURRENT PSW

st psw hhhhhhhh h •• etc.

I
I

56

MESSAGES AND PRINTOUTS

I
I
I
I
I
I
I
I
I

As previously discussed, most printouts from thissystem are self-explanatory, or are documented in theliterature provided for the programs which are being
run in the virtual machine. An exception to this arethediagnostic
printouts
which
resultfrom
time-dependencies within the code of CE diagnostics. In
most cases these time-dependencies are deliberately
created to test some function of the device under test.
A couple of examples follow ••• '• •S F6096*SOO F6096 01 0056F6 0394
ERR HIO EXPECT CC = 2 ACTUAL CC = 0*SOO F6096 01 00574A 0394
ERR-HIO FAILED TO STOP CHAIN*SDO F6096 02 0058F8 0394
ERR HIO EXPECT CC = 2 ACTUAL CC = 0*SDO F6096 02 005950 0394
ERR-HIO FAILED TO STOP CHAIN ON WRITE-DID NOT PAD
WITH ZEROSTThe previous
printout shows
an attemptby thediagnostic to issue a HIO instruction while a channel
program is running on
device 0394. The expectedcondition code of 2 (burst operation stopped) was not
returned. This occurred because of the way in which
CP-67 schedules I/O operations. The channel program
which the diagnostic was attempting to stop with a HIO
had probably already terminated by the time the HIO
instruction was executed. Other printouts may be seenin which expected control unit busy status fails to bereported to the virtual machine.
Ending interrupts may also occur at times other thanthose expected
on a real machine,
resulting inprintouts like the following •••••I
I
I*SOO F5055 34 006AC8 0181
ACT INT STS 3000-EXP INT STS 3400
MSG 51

I
I

Notice that
occur.

I
I
I

These are only two examples of the general type
printout to
expect. Only a small
percentage
diagnostic sections generate these printouts.

the expected device

end status

failed to
of
of

57

APPENDIX C:
CP-67 ON-LINE TESTING GENERATION AND MAINTENANCE GUIDE-; I

PURPOSEThe purpose of this series of EXEC procedures is to provide
the ability
to runOM-controlled CE
diagnostics or
stand-alone programs, including I/O exercisers, in a CP-67
virtual machine, to permit on-line testing' and exercising of
I/O devices. This document describes the generation andmaintenance procedures for the on-line test system. The
necessary commands and operating procedures for actual
device testing are described in a separate user·s guide.
The objective of this package is to make on-line testingavailable to
all CEs . regardlessof theirlevel ofacquaintance with CP-67.

.

Ease of operation has been,provided by making all programs
to be run resident on disk within the system, and byproviding a straightforward command language to prepare
diagnostics for execution. Commands are also provided tofacilitate initial generation and subsequent maintenance ofthe on-line testing system.
REQUIREMENTS
To make use of this on-line testing system, a virtual
machine must be defined in which to run it. A typicaldirectory entry for this virtual machine follows. Some
details of
this entry are dependent
on installation
practices.
userid USER password,accounta,c,80
CORE 256K
UNIT 009,1052
UNIT 00E,1q03
UNIT 00C,25QOR
UNIT 00D,25QOP
UNIT 190,231Q,CMS190,000,053,RDONLYUNIT 191,231Q,CPDSK5,108,117*EOU*
The P-disk space (unit 191)
cylinders.

58

should be approximately 10 2314

OPERATING PROCEDURES
INITIAL GENERATION
After the preceding virtual machine definition has beenentered into the user directory, the following procedure
should be used to load the P-disk files of the on-line
testing system•••.
1.

LOGIN on the testing system.
<See the on-line
testing user's guide, Appendi~ B, if more information
on LOGIN is needed.)
\,

I

2.

I
I

3.

If th~s'is a new virtual machine with no previous
P-disk files, issue the CMS command FORMAT PALL.

4.

Have a tape unit ATTACHed by thevirtual machine as address 181, andcontaining the on-line test system.

s.

Issue the CMS command TAPE LOAD. At this point theon-line test system files have been loaded into theP-disk of the vi'rtual machine.

Issue ~e CP-67 command

IPL.190 to load CMS.

operator to themount the tapeDUMPIT COMMAND
The DUMPIT command, given to CMS in the on-line test system,
will cause a report to be generated shOwing the status of
the entire on-line test system at that time. The report is
printed on the high speed printer of the real system, andconsists of 4 sections .•••
1.

A listing of filename and filetype for each fileon the CMS P-disk. certain filetypes have a special
meaning to CMS. The filetype EXEC defines a filecontaining CM.S
command statements.
Most ofthefunctions of the on-line test system are provided byusing the EXEC file capability of CMS. In addition,some filetypes have been given special meanings within
the on-line test system. The filetype SECT is assumed
to indicate that the file in question is a diagnostic
section which must be run under control of a diagnostic
monitor program. The filetype IPL must be applied toany program which can be ipl'ed from the virtual.
machine's card reader. This classification includes DME
and I/O exercisers. DME itself must have the filename
and filetype
DME IPLin orderfor itto beautomatically accessed by the testing system. To createa copy of DME IPL or FRIEND IPL punch a card deck of59

the program andcommand.

I
I
I
I

follow the directions in

the NEWFILES

2.

The second part of the DUMPIT report is a listingof the configuration cards of DME. This printout will
be used to assist in changing the DME configuration
using the SYS command, which will be described later.

3.

The third report from DUMPIT lists the first (ESO)
card of each SECT file on the P-disk. This provides areference to the revision level, part number, and EC
level of all diagnostic sections.

4.

The final part of the DUMPIT report is a printoutof the contents of all the EXEC files on the P-dis·k.

A current copy of the DUMPIT report should be kept on handto indicate the status of the on-line test system, and to
aid in modifying the system.
SYS COMMAND

The command SYS is used to. initiate modifications to DME in
the on-line test system. It starts a CMS EDIT of OME IPL,
locates the DMIO card, and then unlocks the keyboard toallow EDIT commands to be entered. N.B. the user shouldverify that DME IPL contains only one OMIO card for thiscommand to function correctly. The edit commands whichshould be used are .•••
1.

LOCATE Command
The LOCATE command is used to scan the file beingedited until a specified character string is found. The
string can be any combination of characters and spaces.
It may be positioned anywhere on the line. The LOCATE
command has the following format ••••
L $string$where string is the sequence of characters to belocated. The string must be enclosed in two uniquecharacters which do not appear in the data being
searched <dollar signs were used here). When the stringis located, the entire line containing the string will
be printed.

2.

CHANGE Command
The CHANGE command is used to alter the data on thecurrent line of the file being edited. It has the60following format ••••
C $string1$string2$
The character string, string1, will be replaced
string2. The changed line will be printed.
3.

PRINT Command
To print the current line, type p. To print
starting with the current one, type p x.

4.

byx lines

UP conunandTo move the pointer up x lines in the file, type u x.

5.

NEXT Command
To move the pointer down x lines in the file, type n x.

6.

FILE Command
When all editing is completed, type file.

For further information on the above commands, consult theControl Proqram-67/Camhridqe Monitor System User's Guide.
Note that while other commands are available in EDIT to makechanges to a data record, only the CHANGE command should be
used under SYS. This will protect the data in columns 1 to
12 and 73 to 80 of the configuration cards.
A sample printout of the SYS operation follows ••••sys
USE EDIT COMMANDS "C","L", AND "FILE" TO MODIFY DME TABLES.
DEFAULT TABS SET.
EDIT:
TXT
DMIO
001F001F
1 $230$TXT
UDT4 6A,,0230-0237/6A,,0340-0347/
c $237$234$
TXT
UDT4 6A,,0230-0234/6A,,0340-0347/
1 $udtd$
TXT
UDTD
c $udtd$udtd 50,28,0380-0385/$
TXT
UDTO 50,28,0380-0385/
file
END DME MODIFY.
R: T=0.78 15.59.26
An inspection of the DUMPIT printout of the DME tables in
the on-line test system willshow four unusual unit

61

addresses. The unit addresses 0001,0002,0003, and 0004
should be used when describing the real I/O devices 0009 (or001F), OOOC, OOOD, and OOOE respectively. The UNIT command
will cause them to be attached with these special unit
addresses to prevent conflict with the virtual devices atthese addresses.
In addition, UDTs should be provided for the virtual devices
0009 (or 001F), OOOC, and OOOE to permit DME to use thesevirtual devices as loader, input, and output devices.
The DMIO card should also reflect the address of the virtual
1052, to force the initial messages from DME to print at theterminal.

I
I
I
I

The SRT card should describe a 256K model 65. If it should
be decided to replace DME with a new deck using the NEWFlLES(described below),thefollowing shouldbecommandchecked ••••

I
I
I
I
I

1.

Some DME decks have two groups of configuration
cards at the end. One of these decks must be removed inthis case. The OUMPIT printout will show the presenceof the second deck'if this is not done, and the SYS
command will not function properly.

2.

All of the SRT, SDT, and UOT cards should have asequence number in column 16, i.e. UOTa, UDT9, UDTA,
etc. This will facilitate editing with the LOCATE
command under SYS.

NEWFILES COMMAND
To add new files to the system, or replace existing ones,
issue the command NEWFlLES. This command will automaticallypurge any files which may have been left in the virtual
reader by the OIAGS command, and will request the files tobe added to be placed in the real card reader. The deckshould be preceded by a USERID card (columns 1-2 punched 10,
and columns 10-11 punched with your USERIO). Each filewithin the deck to be read should be preceded by an OFFLINEREAD card(punched
OFFLINE READ
filename filetypestarting in column 1). For example, to add or replace thediagnostic SOa, a card punched OFFLINE READ 50A SECT should
be used. When the message *CARDS HAVE BEEN READ* has been
printed at the terminal, hitting the ATTN key on the 2741
will cause the files to be read into the P-disk, replacing
any files of the same name which are already there.

62

~

I

DEFINING GROUPS OF SECTIONS

I
I
I
I
I
I
I
I
I

Groups of diagnostic sections to be called by a single namein the DIAGS command must have an EXEC created defining thegroup. Models of this type of EXE~ can be found in the
D~lPIT printout. If the user is proficient with EDIT, groups
can be changed or added using it. Otherwise, i t is suggested
that the group EXEC be punched into cards with an
OFFLfNE
READ groupname EXEC
card in front of it, and theNEWFILES
command be used. to insert the EXEC. Group EXECs which may be·found in the initial system are 2311, 2841, 2313 and 2314.
TERMEX TERMINAL EXERCISERSTERMEX is a collection of exercisers designed for a·2741
terminal. It is essentially self-documenting. To obtain auser's guide for TERMEX, type ••••TERMEX#.

When a pattern name and count is requested, give any reply.
TERMEX will respond with instructions on obtaining a list ofavailable tests.
PRINrOUTS

I
I
I
I

Most of the printouts h,ave been discussed. They. are largely
self-explanatory. It should be stressed that a DUMPIT
printout should be on hand at all times .'for reference·
purposes.

/63

INDEXATTACH ••••••• 3, 10
ATTN key ••••••• 3, 9
BEGIN ••••••• 3
chaining••••••• 22, 26
Channel ••••••• 30, 1, 19, 25, 34
Channel check ••••••• 26, 31
Clearing logrec •••• '• •• 35
CLEARIO ••••••• 35
CLEARMC ••••••• 35
Close••••••• 14
CMS••••••• 35
CMS devices ••••••• 2
CMS190••••••• 2
Conventions ••••••• 3
Core ••••••• 2, 19, 36
Counters ••••••• 25, 26, 28
CPDSK1. •••••• 16
CPIOEREP ••••••• 26, 34, 35­
CP~~ACS ••••••• 35
CPMCEREP ••••••• 26, 28, 30, 34
CPu ••••••• 1, 28, 32
CTRLIM ••••••• 35
DETACH••••••• 13
Device••••••• 25, 1, 3, 9, 9, 21
DIAGNOSE instruction ••••••• 1, 35
Diagnostics••••••• 36
2314 ••••••• 38
2841. •••••• 38
2311. •••••• 38
2820 ••••••• 37
2301. •••••• 37
2402 ••••••• 42
2403 .•••••• 42
2703 ••••••• 45
2540 ••••••• 461403••••••• 48
Directory ••••••• 2
Disk ••••••• 2, 6
DME ••••••• 1, 6, 7, 35
Drum••••••• 31
EDIT••••••• 6, 2, 26, 33
Error rnessages ••••••• 22, 28, 37
Error recording area ••••••• 2, 16, 19
Error recording techniques ••••••• 16
Error type indicators ••••••• 25
Exec ••••••• 2, 6, 14, 35
External interrupt ••••••• 3
Format utility ••••••• 3
FRIEND••••••• 1464

In-core pointers ••••••• 19
20, 22
Indicator ••••••• 25
I/O check ••••••• 25
IOINDEX••••••• 19
IPL ••••••• 3, 9, 14, 19, 22, 34
Keyboard••••••• 3, 6, 14
Label ••••••• 16, 19
Libraries macro ••••••• 35
Loader••••••• 9
Log ••••••• 6, 8, 9, 26, 35
Login ••••••• 8, 11, 33, 34
Logout••••••• 7, 8, 10, 20, 26, 30
LOGPRINT••••••• 28, 33, 34, 35
LOGREC ••••••• 16, 17, 22, 28, 32, 35
Machine check ••••••• 28, 19, 22
Macro••••••• 16
Macro libraries ••••••• 35
MACUP ••••••• 35
Message••••• ~.8, 9, 13, 33, 34, 36
Offline••••••• 3, 8, 14, 33, 34
Online••••••• 3, 6, 8
Operator ••••••• 6, 8, 28
Option ••••••• 16
Outboard••••••• 19, 22, 26
Output ••••••• 28
Paging.••••••• 3
Password••••••• 2, 6, 8, 9Privilege class ••••••• 2
Pseudo-timer ••••••• 2
RCHBLOK ••••••• 26
RDEVBLOK ••••••• 25
Record formats ••••••• 19
Recording cylinder ••••••• 2, 16, 19, 25, 35
Restrictions ••••••• l
Retrieving LOGREC ••••••• 32
Sense counter limit••••••• 35
SEREP ••••••• 28, 30, 35
SEREPl. •••••• 26
SEREP2••••••• 26, 34
Spooling••••••• 3, 7
SYSERR ••••••• 16, 19, 28, 35
SYSGEN ••••••• 2, 16, 19
SYSLIB••••••• 35
SYSRES ••••••• 2, 16, 35
Tape.,•••••• 32, 1, 4, 6, 11
Tape drive••••••• 2
Terminal ••••••• 3, 6, 8, 9, 13, 32, 35
User••••••• 6, 9
Virtual machine ••••••• 2, 3, 9, 33, 35
Userid••••••• 2, 6, 8, 9
Xfer ••••••• 8, 14
Index~._ •••• 19,

/

,---

65

GH20-0858-1~\g......
:>

2­

"tl

0

.,

Cfl
3

en-..J

0.,
3

g­

o:

cc
CD

s::
0
:>

;+

Q
en
<

....
CD

3

0"'t:I

en

-..J
-.
(')

s:

~

~

~

.,...

...5"
CD

a.
5"

c

CI'l

l>
G)

J:

I\)

0

6.

(Xl
(J1

~

International Business Machines Corporation
Data Processing Division
1133 Westchester Avenue, White Plains, New York 10604(U.S.A. only)
IBM World Trade Corporation
821 United Nations Plaza, New York, New York 10017(International),~

Technical Newsletter

B8sePubl. No. GH20·0858·1
This Newsletter No. ·GN20·2497
Date January 24, 1972
Previous Newsletter Nos. None

Control Program-67/Cambridge Monitor System. (CP-67/CMS) Version 3.1
Hardware Maintainability Guide
Program Number 3600.05.2.005
This Technical Newsletter, a part of Version 3, Modification Levell, of Control Program-67/Cambridge
Monitor System, provides replacement pages for the subject manual. These replacement pages remain in
effect for subsequent versions and modifications unless specifically altered. Pages to be inserted and/or
removed are listed below.

Contents/Figures
13,14
13.1 (added)
21,22
27,28
35
35.1-35.4 (added)
36
41,42
Minor additions and changes have been made to promote program support information on IBM 3420
Magnetic Tape Unit as well as information on OLTSEP diagnostics for the 3420.
Vertical rules in the left margin indicate changes.
Please me this cover letter at the back of the manual to provide a record of changes .

. IBM Corporation, Technical Publications Dept., 1133 Westchester Avenue, Wh!te Plains, N. Y. 10604
Printed in U.S.A.

~rn~I-Chnical Newsletter

This Newsletter No.

Qate.

(\

GN20-2620
May IS, 1973

Base Publication No.
File No.

GH20-0858-1

Previous Newsletters

GN20-2497(CP-67!CMS
Version 3.2)"
Control Program-67/Cambridge Monitor System(CP-67/CMS) Version 3.2
Program Number 360D-05.2.005.. Hardware Maintainability Guide©

IBM Corp. 1973

This Technical Newsletter, a part of Version 3, Modification Level 2 of Control Program-67/Cambridge
Monitor System (CP-67/CMS), provides replacement pages for your publication. These replacement
pages remain in effect for subsequent CP-67/CMS releases unless specifically altered. Pages to be
removed and/or inserted are listed below.
Title page, 2Preface
Contents
Figures

1-4
13,14-14.1
35.4-36
51,52-52.1

Changes or additions to the text and ~ustrations are indicated by a vertical line to the left of the change.

SUMMARY OF AMENDMENTS
This TNL reflects:• The possibility of encountering errors when running diagnostic test sections on a virtual
machine's minidisk.
• Other minor technical corrections.

Note: Please file this cover letter at the back of your publication to provide a record of changes.

IBM Corporation, VM/370 Publications, 24 New England Executive Park, Burlington, Massachusetts 01803

Printed in U.S.A.

GH20-0858-1

Control Program-67/Cambridge Monitor System(CP"67/CMS) V_ 3.1

Please comment on the usefulness and readability of this publication, suggest additions anddeletions, and list specific errors and omissions (give page numbers). All comments and sugges­
tions become the property of IBM. If you wish a reply, be sure to include your name and address.

COMMENTS

fold

fold

fold

fold

• Thank you for your cooperation. No postage necessary if mailed in the U.S.A.
FOLD ON TWO LINES, STAPLE AND MAIL.

",

GH20-0858-1

YOUR COMMENTS PLEASE •••Your comments on the other side of this form will help us improve future editions of this pub­lication_ Each reply will be carefully reviewed by the persons responsible for writing and pub­lishing this material.

fold

fold

....................................................................................... ·w.·················
g

..2.
:::l

FIRST CLASS..."1:1

PERMIT NO. 1359

0
cc

iil

WHITE PLAINS, N. Y.

3
Ol
.....

~
3

...

CT

BUSINESS REPLY MAil

c:

'!6

s::

NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES

0"

:::l

~.

POSTAGE WILL BE PAID BY ...

!f

IBM Corporation(;

1133 Westchester Avenue

-s:

..3

~

"1:1

Ol
.....
0

White Plains, N.Y. 10604

~

~

~

Attention: Technicol Publicotions..."1:1....................................................................................................... .

:;'
lit
Q.

,

fold

:;'

fold

c
en
l>
Cl
J:

N

0

6

00
01

.~

Intarnational Business Machines Corporation
Data Procassing Division
1133 We.tchester Avenu., White, Plain., Haw York 10604[U.S.A. only)
IBM World Trade Corporation
821 United Hations Plaza, Haw York, Haw York 10017[International)."~