G H20-0856-O

Type III

Control Program-67/Cambridge Monitor System(CP-67/CMS) Version 3
Program Number 3600-05.2.005
CP-67 Operator's Guide

CP-67 is a multiaccess system which allows multiple
System/360 operating systems to run under it
concurrently in a time-shared mode_ These operating
systems run in the same manner as they do on a
dedicated System/360 computer. Some systems thathave run under CP-67 are CMS, CMS Batch, OS, DOS,
APL\360, RAX, and CP-67.
This publication is intended to present to the operations
staff responsible for the operation of CP-67, the facilities
and responsibiliti.es of the systems operator andadministrator. It is divided into two basic parts: (1) the
operator's guide, including instructions for systemstartup, shutdown, and emergency recovery procedures,and (2) instructions on the utilities included with thesystem, including device-formatting, allocation, anduser definition.

Class A Program

REFERENCES
The following publications provide additional information on
CP-61/CMS:
CP-61/CMS System Description Manual
CP-61/CMS User's Guide

GH20-0859-0

CP-61 Program Logic Manual
CMS Program Logic Manual
CP-61/C~S

GH20-0802-1

GY20-0590-0
GY20-0591-0

Installation Guide

GH20-0851-0

CP-61/CMS Hardware ~aintainability Guide

GR20-085tl-O

First Edition (October 1970)
This Type 111 Program performs functions that may be fundamental to the operation and maintenanceof a system.
It has not been subjected to formal test by IBM.
Until the program is reclassified, IB~I will provide for it: (a) Central Programming Scrvkc. including
design error correction and automatic distribution of corrections; and (b) FE Programming Savice,including design error vcrilication. APAR documentation and submission. and application of Program
T"mporary Fixes or development of an emergenq' bypass when required. IBM docs not guarantee
service results or represent or warrant that all errors will be corrected.
You arc "xpeeled to make the tinal evaluation as to the usefulness of this program in your own
environment.
THE FOREGOING IS IN LIEU OF ALL WARRANTIES EXPRESSED OR IMPLIED. INCLUDING.
BUT NOT LI~IITFD TO. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESSFOR A PARTICULAR PURPOSE.
This edition applies to Version 3, !.lodilkation Level 0, of Control Program-67/Cambridge Monitor
System (360D-05.2.005) and to all subsequent versions and modifications until oth,'rwise indicated in
new editions or Technical Newslo:tters.
Changes arc continually made to the information herein. Therefore, before using this publication.
consult the latest SystL'm/360 SRL Newsletter (GN20-0360) for the editions that are applicable andcurrent.
Copies of this and other IBM publications can be obtained through IBM branch offiL:es.
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. Te.:hnical Publications Department. 112 East Post
Road. White Plains. New York 10601.

CONTENTS
System Startup
Initiating CP-67
AUTO LOGIN
Owned Volumes, Core, CECYLAUTODUMP and RE-IPL
En,ergency Console
Emergency Logout

1
1
2
4

5
6

7

System operation

7

General Operating Principles
Spooled Output
Abend of Spooled Output
Spooled Input
Accounting Information
Accounting Cards for Dedicated Devices
Attached Devices
I/O Error Recording
Machine Check Error Recording

7
7
9
9
10
10
11

System Shutdown

15

Utility Operation

16

BUZZARD
DIRECT
FORMATSAVESYS
VDUMP

16
17
18
19
21

Directory Allocation and Creation
Allocation
Directory Creation
Appendix A:

11
13

Operator Console Functions

23
23
24
33

Appendix B: Relationship of Console Functions
to Privilege Class

4q

Appendix C:

Running CP-67 in a Virtual Machine

47

Appendix D:

Selective Relocatinq Loader

GO

Index

63

SYSTEM STARTUP
INITIATING CP-61
CP-61 and CMS, with the exception of the utilities, areentirely disk-resident systems. Each of the disks mayor
may not be labeled. If they are to be used for CMS file
residence or paging and spooling (temporary use) by CP, they
wust be labeled with a six-character label in real cylindero track 0 record 3 by using the utility program FORMAT.
The CP system is device-independent and each of thevolumes which have CP labels may reside on any 2311, 2301,
2303, or 231q direct access storage device available anddefined to it.
The systems residence volume (a 2311 or2314) roust be IPLwed to bring up the system. All resident
volumes should be ready at system startup time, although
they can be attached to the system while it is in operation.
This can cause inconvenience to the users residing on thosevolumes, however, and should be avoided if possible. If theIPLdevice is
not recognizable
tothe CP-61
I/O
configuration, the following message is printed on theoperator's console:•• UNDEFINED IPL DEVICE ••The CP-61 sysres volume must be mounted on a defined device
address (that is, one defined in the REALIO configuration).
The console switches should be
CP-61 operation and not in thestart is desired, the operator
IPL'ing.

in a normal position forstop position. If a cold
should clear core before

If a hardware machine
check occurs during CP-61
initialization (that is, while the CPINIT module is incontrol), the following message is printed:•• MACHINE CHECK DURING CP-67 INITIALIZATION ••The operator of the CP-61 system is defined as thefirst user to log in to CP-67 with privilege class A:
consequently, this unique operator is called the systems
operator. There may be any number of users defined withprivilege class A, but there is only one systems operator in
CP-67.

- 1 -AUTO LOGIN
Once the systerr. residence voluroe has been IPL'ed, theCP-67 initialization program takes control. This program
reads all the labels of~llavailable DASD devices,
calculates the real machine core storage size and theninitiates the login of the operator. The CP-67 system shouldbe generated with anauto-login operator userid (seeCP-67/C~S
Installation
Guide fordetails).
~uto-login
automatically logs
in thesystem operator
with thepredefined userid. No password is required to be entered.
If the auto-login fails, norroal login proceeds as outlined
below. Once auto-login has finished, the initialization
program continues to prompt the operator for the date andtime (as described below) following a successful login.

To initiate operation of the system without auto-login,
the operator must log in to the system as a user.
The
system performs a prompting operation
OPERATOR LOGIN PLEASE
Then the operator enters
LOG use rid

where USERID is an operator's
identification, and to which thesystem replies

ENTER PASSWORD:
The operator then types the installation password (definedby the system administrator in the directory).
After areplies

successful login of
SET DATE

the operator,

mm/dd/yy:

where the response is
mm/dd/yy
The system then replies
SET TIME-

2 -hh.mm.ss:

the systemwhere the response is
hh.mm.ss
If errors are made in the date and time, the request isreissued. After replying successfully to the SET TIME
request, the system replies with
START «COLDISHUT) (REQ»:
where the response is
COLD
if a cold start (one withinformation) is desired,no spool

files oraccounting'null'
if a warm start (retrieve
is required, or

saved spool files and accounting)SHUT
if no action is to be taken, and spool files and accounting
information are preserved on disk for a warm start when thesystem is re-IPL'ed some time later.
The REQ option specifies that no spooling output willcommence until a START command is issued. The spoolingreaders, punches, and printers are essentially in a drained
status. This is useful if the operator wishes to change
forms, etc., before printing commences. The users are notaware that output has temporarily ceased (see -Appendix A:
Operator Console Functions· for details).
The systero responds to a START
following:

request with one of the•• WARM START ••for a warm start request:•• COLD START ••for a cold start request:•• SYSTEM ACCOUNTING AND SPOOL FILES SAVED•••• SYSTEM SHUTDOWN CO~LETE ••for a shut request.

- 3 -After a warm or cold start the system again respondswith a message stating the number of current spool files.
The message has the same format as the QUERY FILES response.
OWNED VOLUMES, CORE, CECYL
The system may alert the operator during initialization
time to abnormal system conditions encountered. The system
is generated with an expected core size (see CP-67/CMS
Installation Guide for details). If that amount of core is
not available at IPL time, the operator receives themessage•• xxxxK STORAGE SIZE ••where xxxx is filled in with the actual storage size at IPL.
The alarm is also rung. The system will continue with thecore available.
If, during IPL time, the system determines that volumes
in the DIRECTORY ·OWNED· list are not available, theoperator receives the message•• SYSTEM VOLUME xxxxxx NOT MOUNTED ••where xxxxxx is the device VOLID.

The alarm is also rung.

Part of CP-67 initialization involves setting up theerror-recording control information. If it is determined at
IPL time that the error-recording cylinder (CECYL) is full,the message is printed to the operator•• CECYL FULL: xxx ERRORS NOT RECORDED ••where xxx is either I/O or M/C, depending upon which error
recording is suppressed. The alarm is also rung.
At this point the system is ready for normal use. The
operator has the responsibility of establishing a "messageof the day" to be issued to users at the time they log in,
if desired.
If not, theoperator must
enable thecommunication lines to permit users to enter the system.
Also, at this time, theoperator may elect to makemodifications to some of the operating parameters of thesystem (for example, the maximum number of users permitted
to log in).
The use of the SET and ENABLE commands should
be reviewed for these functions.

- 4 -AUTODUMP and RE-IPL
Unless it is changed by the operator's issuing the SETDUMP command, thedump unit for system
failures is
automatically selected from available disk spooling space at
IPL time. In the event of a system failure, the dump
program dumps selected parts of core storage on to theselected disk and then it automatically re-IPL's the CP-67
system. Upon re-IPL, the checkpoint program is first brought
in to preserve all accounting information and spool filedata
on disk.
When thisiscomplete, theCP-61initialization programis started.
The operatorisautomatically logged in, and, since it is a restart after a
failure, a warm start is also automatically initiated. The
system LOGMSG that may have been set up by the operator ispreserved and restored. The decimal clock maintained by thesystem is updated and system operation continues by allowing
the users to re-log in. It is not necessary to reenable thelines, since none of the lines, during dump and re-IPL, havebeen disturbed. When the system re-IPL's, a special restart
message is printed on the 1052 console,******************************
CP-67 SYSTEM RESTART IN PROGRESS******************************and the alarm is rung twice.
The total elapsed time fromsystem abend to restart in progress is from two to ten
seconds, depending upon the amount of core storage dumped.
The fact that the system has failed and restarted
should be brought to the attention of the responsible system
programmer. The dump that is on disk is accessible to a
specific user (see CP-67/CMS Installation Guide for details>
to be printed from his virtual machine under regular system
operation.
Once the system has been restarted and the operator has
logged in, the punch may be started to retrieve theaccounting cards.
If certain devices were attached tousers, they will have to be reattached, at the user's
request, after he has logged in.
If the operator sets the dump unit to a printer or tapeunit, then system failures will dump to these units. When-5 -the dump is complete, the system re-IPL's to preserve systemspooling and accounting information, and then stops. The
message appears** SYSTEM ACCOUNTING AND SPOOL FILES SAVED **** SYSTEM SHUTDOWN COMPLETE **and the alarm is rung twice. When shutdown is complete
after the dump, the operator can re-IPL the system tocommence
operation.
The LOGMSG
ispreserved.
butcommunication lines have to be reenabled.
If the DSKDUMP program fails during a system abend,
whether dumping to disk, tape, or printer, the message isprinted,** system CHECK ** SYSTEM DUMP FAILURE **where system is, PROGRAM, ~mCHINE or DUMPDISK depending upon
the nature of the failure. The system then reIPL's to
shutdown the system; no restart is attempted.
If the CHKPT program fails during a system restart, themessages are printed,** system CHECK: SYSTEM RECOVERY FAILURE **** CLEAR CORE: COLD START **** RE-IPL FOR RE-TRY **where system is PROGRAM, MACHINE or SYSDISK depending upon
the nature of the failure. The operator can retry by simply
re-IPL'ing the system disk, but in most cases the same error
occurs.
The only recourse is to clear core and re-IPL.
This must be followed by a cold start, since if a warm startis atte~pted checkpointing is incomplete and can cause
further system failures.
System dump and recovery failUres of this nature arerare and areusually the result ofserious machine
malfUnctions
or asystem failure
resulting inthedestruction of vital information.
EMERGENCY CONSOLE
Should the 1052 online console be inoperative,
emergency console can be used to bring up CP-61. To

-

6 -

an
do

this. place thebutton).

1052

ina non-readystatus,(NON-READY

IPL the CP-67 system in the normal fashion.
If the1052 malfunctions (which it now will), CPINIT, the startup
module will ring the bell and then enable one 2702 or 2703
line * so that the operator may log in. The 2702 or 2703
line address must be defined in the RIO module SYSGEN macro.
(See CP-67/CMS Installation Guide for the definition of theline address.)
The operator may now establish a link with the computer
through a terminal connected to the enabled line. Once theterminal has been identified in the normal procedure, theoperator presses the BREAK key.
The CP-67 system thenproceeds through auto-login.
EMERGENCY LOGOUT
If the 1052 console becomes completely inoperative
during operations such that the operator cannot even log
out, depressing the System 360/Model 67 'external' interrupt
button will force a DISCONNECT of the operator and thus
allow him to login and RECONNECT on any other terminal thathas been previously enab1e1.

*

Support for non-IBM terminals:
Terminals which areequivalent to those explicitly supported may alsofunction satisfactorily. The customer is responsibleforestablishingequivalency.
IBMassumesnoresponsibility for the impact that any changes to theIBM-supplied products or programs may have on suchterminals.

SYST~:OPERATION

The operator's duties while theare the following:

system is in operationa.

Routine handling of spooled input and outputb.

Handling of accounting cardsc.

Attaching and detaching of user and system volumes

GENERAL OPERATING PRINCIPLES- 7 -The operator of CP is like any other user of the system, butwith some important differences:a.

He is allowed to exercise certain console
which the normal user cannot.

functionsb.

His terminal normally stays in console fUnction mode andis usually dormant in a mode to receive messages fromthe system and other users.

In order to type a command into the system, the operator
must depress the REQUEST button on the 1052 console. The
system responds with the time and a read to the console.
Commands may then be entered into the system.
All co~mands (which are described in full in Appendix A) may
be entered in lowercase or uppercase, or a mixture of both.
The arguments are generally separated by one or more blanks.
All responses from the system are prefixed with the time ofstacking for the operator's ter~inal.
Commands are terminated by the FOB signal (alternate codeand 5 pushed simultaneously), while a CANCEL response(alternate code and 0 pushed simultaneously) reestablishes
the read function and ignores the line. In addition, two
editing features are provided to improve interaction withthe operator. The a key serves as a logical backspace, andthe t key (the uppercase a) serves as a logical line-delete.
Thus,
attcksltattach 183 to jones as 18xiaa281
is functionally equivalent to
attach 183 to jop-es as 281
where the tsign has erased the errors at the beginning of
the line and aa~ erased the erroneous three characters 18x.
Note here that the t character and the CANCEL key performthe same logical function.
SPOOLED OUTPUT
Output for the printer generated by users is preceded
time and rtate of printing and the external userid(eight characters) for which the printing was done.
Aby the-8 -message also appears on the operator's terminal describing
the output.
Output for the punch is preceded by similar
information on the first card.
Punch output is directed tothe second stacker.
cards on which errors are detectedduring the punching operation are selected to stacker 1 andrepunched correctly into stacker 2.
All cards in stacker 1
can be considered rejects.
To facilitate separation of punched output, the systempauses between the punch operations for each file and waits
for the operator to remove the cards from the punch. It is
not necessary to run-out the cards since CP-67 spooling will
send a blank card into pocket Pl ensuring that the complete
deck is in pocket P2. When the punch is readied, the system
continues and punches the next pending file, if any. Smooth
operation of the system is accomplished by depressing thepunch STOP and START buttons after collecting punched
output, and thereby enabling the system to initiate punchingwhen required without operator intervention.
Ap?ropriate
prompting messages,
as wellas theregular message
describing the output an~ for whom it is intended, areissued.
ABEND OF SPOOLED OUTPUT
If it is desired to terminate a user's spooling output
on the printer or punch, the TERM command may be used (see"Appendix A: Operator Console Functions").
SPOOLED INPUT
Decks to be read into the system are preceded by a card
giving the external user identification for the deck in thereader. The format of the identification card isColumns 1-10 CP67USERID
Columns 13-20 userid (left-justified)or the alternate format ofColumns 1-2 ID
Columns 10-17 useT~d
All decks must be separated by a physical end of file and,as such, must be loaded into the reader separately. The
system handles multiple card rea~ers. A confirming message
is typed on the operator's terminal when card reading
commences.
If no user identification card precedes thedeck, the operator is so notified.

-

9 -The user does not have to be logged in at the time, but
the directory is scanned to confirm that the userid isvalid.
ACCOUNTING

INFOR~ATION

Accounting cards are punched and selected to the center
stacker (pocket RP3) when a user logs out of the system.
These should be kept for systews accounting purposes. In
the distributed system, one card is punched for each userwhen he logs out.
The information on this card is asfollows:
ColumnColumncolumnColumnColumn

1 - 8
9 -16
17-28
29-40
41-48

Column49-80

UseridAccount NUITlber
Date and 'rime of Logon mmddyyhhmmss
Date and Time of Logoff mmddyyhhmmss
Tirr.e used by userid in milliseconds(CPU cycle ti~e in problem state,plus the supervisor time required
for userid)
hex 'F'

ACCOUNTING CARDS FOR DEDICATED DEVICES
Accounting cards are also punched and selected topocket RP3 when a previously dedicated device is released
from a user by DETACH or LOGOUT or releasing from DIAL. A
dedicated device is any device assigned to a virtual machinefor that machine's exclusive use.
These include devices
dedicated by the ATTACH command, being assigned at login bydirectory entries, or by a user DIAL'ing a system with
virtual 2702 or 2703 lines. The information on this card is
as follows:
ColumnColumnColumncolumnColumnColUmnColumn

1 - 8
9 -16
17 -2829 -4041 -4849 -5051 -80UseridAccount number
Attached time mmddyyhhmmOO
Detached time wmddyyhhmmss
CP-61 device type in decimal
Identifier 'RD'
hex IFF'

Installations which
desire tofunctions foraccounting purposes
following CP ~odules:
ACCTON- 10 -

for action at logon time

perform additional
should modify
theACNTOFFfor action at logoff time

ATTACHED DEVICES
A user may request the operator (via the MSG command)
to attach input/output units (for example, tapes, disk
drives, display devices, printer,punch, card reader,
communication lines) to him on a dedicated, nonshared basis.
When doing this, the user specifies a device address. Thisis a virtual device address and bears no relation to theactual address of the device to be assigned. Any device inthe system can be readdressed when attached to a user by theoperator.
The operator can also attach a spooling card
reader, punch, or printer to a user or change the user's
virtual console andress. The device is not dedicated andcan also have any desired virtual address.
When a user requests an attachment by the operator, itis the operator's duty to determine if there is a device of
the appropriate type free to dedicate to the user.
If thereis, he must mount the requested volume and type the ATTACH
command into the system. (See "Appendix A--ATTACH"). The
systen, responds with a confirming message both to theoperator and to the user indicating that the device is
attached. If the device is not ready or is currently in use
by another user, the operator is so notified and he mustfind another device or wait until the device becomes ready.
~he usermay detach the unit at any time he wishes
before logging out of the system.
If he has not detached
the device before logging off, the system automaticallydetaches it when he does. The operator and the user getmessages indicating that the device is now free and, if thedevice is a tape drive, the volume is unloaded.

I/O ERROR RECORDING

The CP-67 system is capable of detecting errors on mostdevices being used on the system both for CP-67 usage(paging, spooling) and for user files.
These errors arerecorded on a special cylinder called CECYL on the system
residence volume.
The cylinder
must be allocated aspermanent (see "Allocation") and the cylinder number is
specified
as partofthe
SYSGEN procedure.
(See
cp-67/CMS Installation Guide fordetails.)
Duringtheprocess of error recording, certain messages appear on theoperator's console to alert him to various conditions. If
an excessive number of errors occur in a particular device,- 11 -

the message is printed** IOERROR DEV- xxx; ERR CNT = nnn: SENSE -ssssssssssss STATUS - zzzz: USERID = uuuuuuuu**

where xxx is the device
address that has the error
condition: nnn is a count of the number of errors that haveoccurred on this device since system IPL: sss are six-sense
bytes from the device: zzz is the csw status bytes for thecurrent error, and uuu is the user for whom the error
occurred. The message should be brought to the attention of
the local IBM customer engineer for his consideration.
If a nonrecoverable error occurs for CP initiated I/O
operations (paging or spooling), the message is printed (inaddition to the error message described above)** SYSTEM IOERROR *.

USERID = userid

where userid is the identification of the user for whoro the
CP operation failed.
In addition, the userid receives thefollowing message:.* SYSTEM IOERROR •• CP ENTERED, REQUEST, PLEASE
Once these messages have been printed, the system
usually abends, since it cannot continue after permanent
failures for paging or spooling. The error condition must be
brought to the attention of the local IBM customer engineer,
since it indicates possible hardware malfUnctions on thepaging or spooling devices or core storage.
If, in the process of recording an I/O error, thesystem is unable to complete the recording successfully, the~essage is printed•• IOERROR RECORDING FAILURE ON DEV - xxx**

where xxx is the device (system residence) where errors arebeing recorded. This should be brought to the attention of
the local
IBM customer
engineer and/or
the systems
programmer, since it indicates serious trouble with theerror-recording mechanism.
Only one cylinder may be used to record machine-checkand I/O errors. If this cylinder is filled during system
operation, the message is printed•• CECYL FULL: xxy- ERRORS NOT RECORDED- 12 -••

where xxx is either I/O or M/C, dependingor machine-check errors are suppressed.

upon whether I/O

The local IBM customer engineer should be notified so
the error-recording cylinder can be printed and cleared tocontinue error recording. The system continues to operate,and error messages may also print on the operators console:
however, no permanent disk record is wade of th~ error.
(See CP-67/CMS Hardware Maintainability Guide for details.)
When the error-recording
message is printed

cylinderis formatted,the** CECYL FORMATTED BY userid: xxx ERROR RECORDING INITIATED *where userid is the id of the user who initiated the format
and xxx is I/O or ~/C, depending upon which is formatted.
The alarm is also rung.
This same message (with the operator as the userid) is
printed at system initialization time if the first access tothe error-recording cylinder indicates that it has not yet
been initialized.
If, for some reason, one of the CP-67 owned volumes(used for paging or spooling) becowes nonready, the message
is printed** SYSTEM DEV - xxx ATTENTION **where xxx is the device address requiring
This 1l1essage is immediately followed byintervention.

** REPLY "GO· WHEN AVAILABLE OR "FAIL" IF NOT AVAILABLE **whereupon a r~ad is issued to the operator·s console for ar~ply.
If the operator replies "GO" after readying thedevice, the system continues normally.
If it canno~ befixed and the reply is "FAIL", a permanent system I/O error
is assuffied. and the messages associated with this condition(as described above) are printed.

~ACHINFCHECK ERROR RECORDING

The CP-67 systerr has a mechanism for recording hardware
rr.achine checks in a manner similar to I/O errors.
The
errors are recorded on th~ same predefined cylinder as the- 13 -

I/O Errors.
If a rrachine check occurs whilerunning a user, the operator receives the message** MACHINE CHECK PROBLEM~ODE**CP-61

is

USERID=userid **where userid is the name of the user running at the time of
the failure. The alarm is rung. The user (use rid) receives
the message**~ACHINECHFCK ** CP ENTERED, REQUEST, PLEASE **If the virtual w.achine PSW is not enabled to receive machine
checks, none is present~d nor is the machine check held
pending. Instead, the user receives the message**~ACHINE

CHFCK**

and his virtual machine continues to run.
machine-check error is recorded
continues to run.

~heon disk, and the system

If a machine ch~ck occurs while in CP-61
wode, the operator receives the message

supervisor** MACHINE CHECK CP-61 SUPERVISOR MODE **The alarm is rung. Th~ error is recorded on disk and theCP-61 system then forces an abend dump to the dump device.
If in the process of recording a CP-67 machine check, and so
informing the operator, another machine check occurs, themessage is printed on the systerr. console** MULTIPLE MACHINE CHECKS ** RUN SEREP AND RF-IPL **and the alarm is also rung. The CP-61 system then goes intoa hard wait with X·FFFFFF· in the address register.

SYSTEM SHUTDOWN
The system shuts down in one of two ways:a.

An abnormal
dump; orb.

An operator-initiated shutdown.

The normal systemcommandterroination where the system

shutdown is

initiated

may elect toby enteringtheshutdown
from the operator·s terminal.
The SHUTDOWN command has immediate effect. No messages
are sent to any users, and no attempt is made at any
draining of I/O activity.
The SHUTDOWN command essentiallycauses a programmed re-IPL of the system. This brings in
the CHKPT program that saves all accounting information, theOGMSG, and all spool file data.
Upon completion of the
CHKPT program, the message is printed•• SYSTEM ACCOUNTING AND SPOOL FILES SAVED •••• SYSTEM SHUTDOWN COMPLETE••

and the alarm is also rung.
The CP-67 system can now be restarted, u~ing warm start, at
a later time. The system directory and the CP-67 nucleus canbe rewritten if wanted and it will not disturb the saved
data for a warm start.

Note that the operator has the additional facility offorcing a logoff of any user in the system.
This isperformed by use of the KILL console function (see wAppendix
AW).

- 15 -

UTILITY OPERATION
Five stand-alone utilities are distributed with CP-67:
accounting

BUZZARD

To
preserve
spooling
and
information for warm start.

DIRECT

To createspace.

FORMAT

To format direct-access volumes
residence.

for CP file

SAVESYS

To save theby nawe.

for IPLing

VDUMP

To print a dump of aspooled file after an
the system.

user directory andallocate DASD

nucleus of a systemsystem crash from a
automatic re-IPL of

A self-loading relocating loader must be used to load
BUZZARD, DIRECT, FORMAT, and SAVESYS. After the card load
is complete, the programs go into wait state with allchannels unmasked, and the request key on the operator's
console should be pushed so that it may be identified.
Note:
The default value for the operator's console isassembled as X'0009'; if the installation has that address,
the console request key does not have to be pushed.

BUZZARDThe BUZZARD utility has three functions:a.
It saves accounting records on disk after abnormal
system failure.
The records are in the format describedunder RAccounting InformationR.
These cards are punchedduring normal system operation if the system is warm-started
at a later time.
b.
It preserves the system LOGMSG
up by the operator.

which may have been setc.
It saves DASD pointers for all files for the virtual
readers, printers, and punches. User printer or punch
spooling functions (virtual devices> in operation (that is,
not closed) at the time of system terwination are not saved.
User's active reader files are saved. Pen1ing user-spooled- 16 -

input and output and any currently active real printer orpunch output is saved. Real reader operations proceeding at
the time of termination are not saved and must be restarted.
This information is saved on the CP-67 system residence
volume. At system IPL time, if the warm start option ischosen, this information is used to create the necessary
in-core blocks and restart the spooled output.
Note: For warm start the spooling disks have to be mounted
on the same devices used when the BUZZARD utility was run.
BUZZARD performs the same function as the CHKPT program
performs in the CP-67 IPL sequence. Therefore, BUZZARD
should only be run if a hardware malfunction does not permit
automatic re-IPL of the system disk following an abnormal
system termination.
However, the system disk must beaccessible for writing if the spooled file pointers andaccounting records are to be preserved by BUZZARD.
The
system disk may be moved to another physical disk drive(2314) so long as the physical address of the disk is notchanged.

DIRECTThe DIRECT utility is used to write the allocationtables on each of the volumes designated as CP-owned. and towrite the user directory on the CP system residence disk.
The format of the data cards required is described under"Directory Allocation and creation."
The format of the DIRECT load deck is as follows:
Loader
DIRECT'LDT· card (12-2-9 punch in column 1:·LDT· in columns 2-4)
Allocate and Directory deck
the load deck is IPL·ed from the 2540 card reader, andthe console is identified, DIRECT asks for the input device
address~fter

ENTER INPUT DEVICE ADDRESS - CCU:
where the response is three hexadeciwal characters giving
the unit address of the appropriate reader.
The specified
unit reust be ready.
Note thatthe Directory

program canbe runin avirtual- 17 -

machine if the user has read/write privileges to the systemdisk set up in the 1irectory beforehand. The Directory canbe loaded and run by C~S after making the ALLOCATE and/or
DIRECTORY deck available to the user through his virtualcard reader.

FORMATThe FORMAT utility is used to initialize direct-accessvolumes for paging. spooling, and CP file residence.
After theoperator·s console

has been

identified, it

types
CP/67 DASD FORMAT PROGRAM
Then it requests
typin<;

thetype ofdevicebeing formatted

by

DEVICE TYPE
where the response may be four digits indicating the type of2314) and an optional
device (that is, 2301, 2303. 2311,
fifth character p which causes only partial formatting totake plaCE (that is, 2314P).
If the device
the unit address

type is recognized, thesystem requests

DASD ADDRESS =where the response is the channel and unit address as threehexadecimal digits (for example, 100, lCO, 230, A30, 9CO).
If the device is ready, the systemlabel to be written by typing

asks forthe new

VOLUME LABEL =where theresoonse issix characters(uppercase
lowercase) written on the label record of the volume.

or

If P was specified when indicating device ty~e, thesystem now asks the operator to define the area to beformatted by typing- 18 -

START CYL.(HEX) =where the response is null for cylinder 0, ·10· if only thelabel is to be written, or two hexadecimal digits specifying
the starting cylinder. The system then requests the ending
cylinder by typing
END CYL.(HEX) =where the response is null for the entire volume (whose
actual value
differs with thedevice type)or twohexadecimal digits for a specific cylinder.
The system indicates that the format operation hascommenced when its data is complete. At termination, theprogram will so indicate and may be restarted by pushing
REQUEST.

SAVESYSThe SAVESYS utility is used to save the nucleus of asystem which is normally used under CP (such as CMS). This
nucleus is saved on a disk in pageable form and allows theuser to IPL that system by name, for example,
IPL CMSin CP console fUnction mode.
The SAVESYS
formatutility accepts

a controlcard with

the

SAVE VOLID=cccccc,UNIT=ccc,FP=nn,LP=mm,CYL=ppp,DISK=tttt
where:SAVE begins in column 1;
VOLID begins in column 6;
cccccc is thevolume;volume label of thereceiving DASD

ccu is the channel, control unit,
address of the receiving volume;andnn is the page number ofwritten (in hexadecimal);page tothe first

devicebe- 19 -

mm is the page number ofwritten (in hexadecimal);the last

page tobe

ppp is the starting cylinder of the image;tttt is the device type (either 2311 or 231q).
An example of a SAVESYS control card isSAVE VOLID=CPDSK1,UNIT=230,FP=00,LP=11,CYL=200,DISK=231Q
The space indicated on the card must have been allocatedpreviously as permanent space on the volume when DIRECT wasrun. The information on the control card must match that
information provided in the SYSTEM module assembled andloaded with the system.
(See CP-67/CMS Installation Guidefor details.)
In that module, the system name, location,
shared pages(if any) and operating
conventions are
established. In the distributed SYSTEM module,
the systemname is eMS, seventeen pages are saved beginning at page 0,
up to and including page X'11'. In the distributed system,
the saved copy of CMS is written on the disk volume labeled
CPDSKl and is 231Q resident at cylinder 200.
The number of cylinders required to contain a saved
named system depends upon the number of pages saved and thedevice type where it is saved. For a 231Q, one cylinder canhold 30 (decimal) pages; for a 2311, one cylinder can hold 8(decimal) pages.
When SAVESYS saves a copy of the system, it saves fromFP to LP.
If LP is greater than X'20', the SAVESYS module
must be loaded into higher core, as it normally loads into
20000. To load SAVESYS into higher core, change the addressin the SLC 20000 card at the front of the SAVESYS text deck.
The procedure for running SAVESYS is as follows:1.

IPL the system to be saved, with the address stop
switches set to a location within that system, where
execution may be resumed without the system assuming
any previous state in the machine (registers, lower
core locations, etc.).
For C~S, the address stop
location is FO.

2.

When the system has entered manual state (that is, theaddress has been reached), load the SAVESYS deck into
the system card reader and IPL the reader. The format- 20 -

of the SAVESYS deck must be as follows:High core loader
SLC 20000 card
SAVESYS program
LOT card
SAVESYS control card
If the save was successful. the following
appears on the operator·s console:3.

message

NORMAL TERMINATION OF SAVE FUNCTIONVDUMP
The VDUMP program runs under the control of thecambridge Monitor Systerr. When a system crash occurs. aspool file is created for the virtual machine whose USERIO
isspecifiedat
SYSGENti~e(see
cp-67/CMS
Installation Guide). The spool file then may be printed asa CP-67 system dump by issuing the CMS command VDUMP to thedesignated virtual machine (see section on AUTODU~ andRE-IPL).
In order to create the CMS command called VDUMP on theappropriate virtual machine. this procedure may be followed:a.

Read the punched card deck for VDUMP TEXT into theappropriate virtual machine (attach a USERID card to
the front of the deck).

b.

IPL CMSc.

offline readd.

load VDUMPe.

genrood VDUMP*

The virtual machine which has access to the system dump
created by the autodump feature must have the standard CMS
virtual device addresses. In addition. this machine must
contain the following directory entry for a special virtual
device which reads the spooled file for the dump:
UNIT OF1.RPRTAs the dump is being printed. the following
appears at the virtual rnachine·s terminal:

message-21 -PRINTING STORAGF LOCATION xxxx
When the dump is finished, the message END OF DUMP isprinted at the terminal and control returns to CMS.
The VDUMP printed output is preceded bygiving the date and time of system crash
CP-67

SYSTtM ABENDDATE mm/dd/yy

a header page

TIME hh.rnm.ss

If the default (CP) is in effect for the SET DUMP
command, or if CP is specified as an option, thp following
is printed in the dump:
general-purpose registers 0-15,
control registers 0-15, and all of CP nucleus and freestorage. If ALL is specified as an option, the dump includes
all of real core.

- 22 -DIRECTORY ALLOCATION AND CREATIONThe DIRECT utility performs two distinct and so~ewhat
separate functions:(1) the allocation of
space ondirect-access volumes to indicate to the systero which areas
are utilized for user and CP file residence and which are to
be used for temporary use by paging and spooling functionsof the system, and (2) the creation of a directory that
contains descriptions of theusers and their virtual~achines.

ALLOCATION
CP-67 requires an allocation record to be written
behind the volume label on cylinder 0 head 0 record 3 ofeach disk that is to contain space for the directory,
paging, and spooling. The allocation record specifies which
cylinders on the disk are used as permanent space and which
are temporary space.
Permanent space on a volume consistsof the areas reserved for user files and system residence.
Temporary space consists of those areas used for paging andspooling by CP-61.
~here
are five types of allocation control cards:
ALLOCATE, DRCT, TEMP, TDSK, and PER~. The format of the
ALLOCATE card is

ALLOCATE UNIT=ccu,VOLIO=xxxxxx
ccu
xxxxxxistheaddress
allocated.

ofis the six-characterto be allocated.

thedevicetobelabel of the volume

ALLOCATE must start in column 1 and UNIT in column 11.
DRCT space is used for CP-61 directory residence.

TEMP space is used for CP-67 spooling and paginq.
PERM space is for user direct-access files.
TDSR is for DASD units in the user machine descriptions
that are to be allocated at login time from a pool of
temporary disk space. The TDSR area is ~ used by CP
for spooling or paging.

- 23 -

The control cards for the allocation of space are
DRCT
TEMP
PERM
TDSR

xxx.yyyxxx.yyyxxx.yyyxxx.yyy

where DRCT. TEMP. PERM and TDSR start in column 10. and thecylinder designations in decimal form (with leading zeros tomake three characters each) start in column 16. xxx is thefirst cylinder and yyy is the last cylinder.
There must be one ALLOCATE card for the CP residence
volume and for each disk that contains temporary space.
Each ALLOCATE card must be followed by the control cards forthat volume. When all the allocation for a device has been
specified. the following card is used to indicate the end of
allocation cards for the volume:*EOA*
The *EOA* begins in column 10.
The *EOA* card isfollowed by another ALLOCATE card or a DIRECTORY card.

thenNote that the system always makes cylinder 0 permanent
for the volume label
and allocation table residence.
Therefore. do not begin user files on real cylinder Q of
those disks~hat are being allocated. Checks are also madefor exceeding device limits on the device address specified.
~he allocationof volumes can be a separate run fromthat of the directory. Also. each volume can be allocatedindependently of the others.

Note: Do not ALLOCATE space on the 2301 or 2303 drums
since the FOR~~T program sets the allocation such that all
space is formatted for dynamic paging allocation.
---

DIRECTORY CREATIONThe CP system residence volume must contain a directorythat describes the users and their virtual machine.
The
directory portion of this utility accepts the descriptionsof the users and their virtual machines from the card reader- 24 -

specified at the operator's console and writes the directoryin the temporary space previously allocated on the system
residence volume (initially the disk must be formatted
before ALLOCATE'ing and DIRECTORY take place).
Dependingupon the size of the directory and the device type of thesystem residence volume (that is, 2311 or 231Q), at least
the first two or three cylinders should be allocated as DRCT
space on the CP system residence volume. Estimates on spacerequirements for the system directory are as follows:
231Q-- 150 USER virtual machine
descriptions per cylinder
2311-- QO USER virtual machine
descriptions per cylinder
These space requirements are in addition to cylinder 0 of
the residence volume, which is used as the master directory.
Thus, the directory allocation control card,
DRCT

000,003is sufficient to provide space on three cylinders (1, 2, and
3) for virtual machine descriptions.
Every user who is to be permitted to log in to CP-67
roust be described in the directory, including the system
operator.
The directory description must begin with the following
control card:
DIRECTORY UNIT=ccu,VOLID=xxxxxx
ccu

is the real address of the CP system's
residence volume on which the directory
is to be written.

xxxxxxis the six-character volid of the disk onwhich the directory is written.

DIRECTORY must start in column 1 and UNIT in column 11.
After theIts format is
OWN

DIRECTORY control cardcomes theOWN card.

aaaaaa,bbbbbb, ••• ,hhhhhh

where waaaaaa,bbbbbb, ••• ,hhhhhh w are the volume labels ofdisks that contain allocation tables. OW~ must start incolumn 10 and the volume labels in column 16. Only eight- 25 -

labels can be specified in one
eight, use multiple O~~ cards.

card.

To

name morethanNote that the only volumes specified in the owned list
are those that CP can use for paging and spooling, such as
drums, and the systerr residence volume. Volumes that have
no TEr-~P, DRCT, or TDSK space (for instance, OS, DOS, CMS
volumesi must not be in the owned list. It is obviously notnecessary to allocate volumes that are all PERM space.
Next are the cards that describe a user and his virtual
machine. These cards are described below.
(~otethat thelabel fiel~ always starts in column 1, the operand field,that is, card type, in column 10, and the arguments incolumn lb.)
useridUSER

password,account,priv-class,priority,options

The USER card initiates a new machine description fileand creates a user directory entry for the specified user.
"Userid" is the eight-character external name by which
the user and all spooling output are labeled; it must be
left-justified and trailing blanks included if userid is noteight characters.
"Password" is the key by which the user must respondwhen trying to log on in order to be permitted into thesystem. The password must be specified as eight characters,
left-justified, with trailing blanks if eight characters are
not specified. Note that if the terminal has the print
inhibit feature, the system turns off the printing mechanism
to maintain the security of the password.
"Account" is any eight-characterinstallation accounting uses.

identificationfor"Priv-class" is the user's privilege class: A forsysterr operator, B for system aaministrator, C for IBM
customer engineering use, and D for normal users.
This
privilege class determines what console functions in thesystem the user may exercise. (See Appendix B for a table ofconsole functions available to each privilege class.)
Note: Users with privilege class C do not have I/O errors
recorded for them by CP-61. Use of this class should
therefore be carefully restricted.
Privilege class C canalso execute certain DIAGNOSE functions to maintain theerror-recording cylinder.

-

26 -

"Priority·, in the current system, is not used and has
no bearing on dispatching or scheduling. The single decimal
number ~ay range from 1 - 9.
"Options" isa hexadecimal numberthat selects
specific options available to users at login time andexecution
time.
There
are
currently three
options
available. They, and their hex values, are:
REAL timer support
ISAM support
VIRTUAL 360/67 support

X'SO'
X'40'
X'20'

Note:
ISAM support means
supportmodified ccw strings for DASD.

ofdynamic

channelMultiple options can be selected by combining thevalues. For instance, real timer and virtual 67 would bespecified as
USER
The core card specifies thememory.
CORE

size of the user's virtual

dddd
dddK
ddaM

It may be specified as dddd where dddd is a decimal numberthat is a multiple of 8192 bytes, or by one or more decimal
digits followed by K or M, indicating a multiplier of 1024
bytes or 1,048,576 bytes respectively. The core size must
be a multiple of 8K. where 8K is the minimum.
When a user
logs in to CP-61, he receives a virtual machine of thissize. Paging space is not selected for this virtual machine
until the user references core storage; space on the paging
device is then selected one page at a time. If a user does
not need a large core space, allocate him a small one--forexample. give the operator 8K core.
UNIT

ccu,devtype
1,<xxxxxx,(TFMP),REM=IDccu,CON=YES,DED=IDccu>1
1,<relno,zzz>1
I.lastl
I.RDONLYI- 27 -

I.RDSHAR=passwordl
I.WRMULTII.WRSHAR=passwordl
The UNIT card is used to specify the input/output units
available to a user and where and on which volumes his
permanent files reside.
ccu

is the virtual address of the device.

devtypeis the device type. which ~ay be one of
the following:
1052
25QOP
2540R
1Q03
2250
2311 or 2312
231Q
2400
2701
2702
2703
TIMR
RPRT
RPUN
where a 2312 is used to designate thebottom half of a 2314 drive used as a
virtual 2311.

2312 device type is treated as a 2311 by CP-67. User seekcommands issued to the pseudo 2311 have the head address
relocated (by adding decimal 10) to access the botto~ halfof the 2314 disk. It should be noted that 2311 device types
supported on the top half of a 231Q pack may experience
difficulties
if multitrack
operations areattempted:
however. multitrack operations on the 2312 (pseudo 2311)
device typeshould work
correctly sincea physicalend-of-cylinder condition is recognizable.

~

TIMR is a pseudo-chronolog device which can provide the timeof day. date. virtual CPU time. and total CPU time to a
virtual machine. It should be specified for every C~S user.
Its format is
UNIT

-

28 -

OFF.TIMRRPRT and RPUN are special device types that allow the user
to access the disk dump created by a CP-67 system abend.
For the desired userid to receive the dump (see CP-67/CMS
Installation Guide) specify
UNIT

OF1,RPRT

xxxxxxis the volume
being described.

label ofthedisk thatis(TEMP)
specifies that the disk space is to beobtained at logon time from that allocated as TDSK
space and then removed from the user at CP-67
logoff.
RE~=IDccu

specifies a remote device with real address
ccu that is to be used for spooled output fromthis defined user. It has the same function as
the SPOOL console commands for directing spooled
output. See CP-67/CMS User's Guide for details.
The only device types supported as remote devices
are the 2SqOP and the 1q03.

DED=IDccu specifies a device with real address ccu
that is dedicated to this user at login time andunavailable to other users.
The device types
supported are the 1Q03, 2SQOR, 25QOP, 2250, 2QOO,
2701, 2702, and the 2703. If the specified device
is not available or in use when the user loqs in,
he is so informed and the device is not attachedto him. Note that a 2250 or 2QOO, if specified,must be defined as a dedicated device.
CON=YES
specifies that continuous spooled input isdesired for this virtual card reader: that is, if
there is more than one spooled input file for thecard reader, they are read as one continuous file
before end-of-data is given.
This has the samefunction as the SPOOL
console function (seeCP-67/Ct-~S User's Guide for details).
relno
is a three-digit decimal cylinder relocation
factor to bE applied to this device: for example,
if a user's permanent files started at cylinder 5Qof the specified volume, relno would be specified
as OSQ.
zzz

is a
the nUl'1ber
at logon.

three-digit decimal number specifyingof temporary cylinders to be obtained
zzz is used
only if (TEMP) was

-

29 -

specified.
last

is a three-digit decimal number specifying
the last cylinder of the user's file space. If
relno is 054 and the user is allowed 20 cylindersof space, last would be specified as 073.
specifies that the virtual direct-accessvolume can only he read and not written upon. If
RDONLY is not soecified, the user has read/write
access to the volume by himself, and no other user
can read or write that voluwe unless WRMULT is
specified for those users.
(See WRMULT.)
If thevolume being described is the CMS syste~ disk,
RDONLY should be sFecified for each user.

R~~NLYRDSHAR=password is a one to eight-character password
that allows this volume to be shared ~or readingby users knowin9 the proper password.
If ALL is
specified as a password, all users have access tothe volu~e for read-sharing.
RDSHAR is only used
for permanent volumes and not temporary ones. If
either WRSHAq or WR~ULT is specified, but not
RDSHAR, a comma must be used to show thC!. t RDSHAR
is omitted.
WRMULT
allows the user to have access to the volume
regardless of other users. If WRMULT and RDONLY
are both specified for a user's volume, he will
have read-only access to that volume, regardlessof other users. If only WR~ULT is specified, he
has read/write access regardless of other users onthat same volume. This pararr.eter is intended foruse by users using operating systems which provide
an interlocking mechanism to protect files or forsystems programmers who know what they are doing.
ct-:s does not have an interlocking mechanism.
WRSHAR=passworc is a one to eight-character password
that allows the volume to be shared for writing aswell as reading, but only one user can have accessto the volume at a time.
The volume is shared
among users knowing the proper password.
If ALL
is specified as a
password, all users havewrite-sharing privileges on the volume.
Note. RDONLY is inconsistent with WRSHAR and consequently
they ~ay not be specified together.
If RDONLY is specified
on a volume for all users but one, and that one user logs infirst, he will use the volume in a rea1/write status andother users will have no access to that volume unless they
have the WRMULT paralreter. loJhen the RDONLY users log in,- 30 -

they receive the message
DEV ccu IN USE BY userid; NOT ATTACHEDThe RDONLY users should either log out and then log back in
or issue LINK console function after userid logs out or
use rid detaches that device from his virtual machine. If
that read/write user logs in after a RDONLY user, he will
receive the message
DEV ccu IN USE BY userid; SET TO R/Oand he will have read-only access to that volume.
Theuserid will be one of the RDONLY users who logged on first.
If a read/write WRMULT user logs in after a RDONLY or aread/write user, the WRMULT user will have read/write accessregardless of the other users on that volume, and he will
receive the message
DEVICE ccu IN USE BY use rid
If a RDONLY, WRMULT user logs in after any other user, he
has read-only access to the volume, regardless of otherusers, and he receives no message.
The parameters specified with the UNIT control car1 arepositional, therefore they must be specified in order and acomma must be used for each parameter omitted.
Each user·s machine description is terminated by a card
with
*EOU*
beginning in column 10. At thedescriptions, a card withend of alluser directory*EOD*
beginning in column 10 is used to terminate the directory
creation process and to return to the ALLOCATE and DIRECTORY
card-scan routine. If there are no additional ALLOCATE or
DIRECTORY cards,
DIRFCT is terminated: if
there areadditional ALLOCATE or DIRECTORY cards, DIRECT is executed
again.

- 31 -

A sample allocation and directory deck are as follows:

ALLOCATE

UNIT=230.VOLID=CPDSK1DRCT 000.003
PEIW 004.004
TEf.IIP 005.197
PEIW 198,202·EOA*
ALLOCATE UNIT=235.VOLID=CPDSK5PERM 000.000
PERM 001,075
TDSY 076,165
PERM 166,202*EOA*
DIRECTORY UNIT=230,VOLID=CPDSK1OWNCPDSK1,CPDR01,CPDSK5OPERATOR USER CSC,A1234,A,8CORE 8K
UNIT 009,1052
*EOU*
USER1
,222
,D,3
USER PASSl
CORE 256K
UNIT 009,1052
UN I"!'
00E,1403
UNIT 00C,2540R
UNIT 00D.2540P
UNIT OFF,TIMRUNIT 190.2311,CMS190,OOO,202,RDONLYUNIT 191,2311,CPDSKS,166,175·EOU*
USER PASS2,A590,C,3,X'80~
USER2CORE 256K
UNIT 00E,1403,DED=ID030
UNIT 009,1052
UNIT OOC,2540R
UNIT OOD,2540P
UNIT 106,2250,DED=ID106
UNrr OFF,TIMRUNIT 190,2311,CMS190,000,202,RDONLYUNIT 191,2312,CPDSK6,148,152",WRMULT
UNIT 193,2311,YVR999,OOO,202
*EOU·
USER3
USER PASS3,X3214567,C,3,X'CO'
CORE 256K
UN!'!" 009,1052
UNIT 00E,1403
UNIT 00D,2540P
UNIT 00C,2540R
UNIT 190,2311,CMS190,OOO,202,RDONLYUNIT 191,2314,CPDSK3,050,060"RDSHAR=RDXX,WRMULT
UNIT 192,2314,CPDSK5,001,075""WRSHAR=MYPASS
·EOU·
*EOD*

- 32 -

APPENDIX A: OPERATOR CONSOLE FUNCTIONS

Depressing the attention button on the online 1052
keyboard causes the syste~ to turn on the proceed lightawaiting an operator console function request to be issued.
The operator may choose from (1) any console functions that
another user may choose from (although this may not be
9articularly appropriate) or (2) issue one of the commands
reserved for a user of privilege class A, or (3) issue oneof thecommands exclusively reserved forthe system
operator. The commands listed below are those which are
restricted to privilege class A or B as well as the system
operator, except where noted. Several commands are included
which facilitate debugging of the Control Program and its
algorithms. A complete set of all console functions andtheir relationship to user privilege classes are in Appendix
B.
ACNT - punch ann reset accounting information
ATTACH - attach a device to a user or the system
DCP - display contents of CP-67 me~ory
DETACH - release a device from a user or the system
DIRECT - control access to the system directory
DISABLE - disable 2702 or 2703 lines for access to system
DMCP - dump contents of CP-67 memory
DRAIN - cease spooled operation upon current completion
DUM P - force a system abend
ENABLE - enable 2702 or 2703 lines for access to system
KILL - log a user off the system
LOCK - lock certain user pages in core
MSG - send a message to the user(s)QUERY - query status of system
REPEAT - cause current spool output to be repeatedupon termination
SET - establish system para~eters
SHUTDOWN - terminate all system operation
SPACE - cause printe1 output to revert to single spacing
for current output
START - commence spooled operation on specific devices
STep - store into real core
TERM - terminate current unit record operation
UNLOCK - opposite of lock
WNG - issue a warning message to user(s)The following conventions are used throughout thisdescription:(1) variable information
is indicated inlowercase letters and system keywords are indicatea inuppercase letters, whereas either case may be used when

- 33 -

communicating with the system; (2) < and> are used tobracket choices when applicable in the 1escription (forexampl~, ~;SG <userid,ALL> would be used to indicate that MSG
userid or ~SG ALL could be used) whereas the brackets are
not typed when communicating with the system.

ACNT(ACNT)

This co~mand punches an accounting card for all active
users and resets their accounting information to new values.
A message is sent to all users informing them of theirconnect time and CPU time in a format identical to the QUERYTIME response.
The corr.mand is useful to reset accounting
inforffiation at certain times if installation rates change.

ATTACH(A)

The ATTACH command allows the operator to dynamically
add to a user's configuration any device in the real system(for example, 2QOO tape unit, 2314 module or 2250 display
Unit). This is customarily done in response to a user's
request via the MSG command.
The ATTACH command can be used to attach a multi~lexor
device (that is, printer, punch, or card reader) to a user
in a dedicated status.
The user cannot already have avirtual device with the indicated address.
(If he does, hemust DETACH it beforehand.) The format is
ATTACH ccu TO userid AS yyy
where ccu is the channel and unit designation of a device inthe real
configuration; userid is theexternal user
identification of the virtual machine which is to receive
the unit: and yyy is the virtual channel and unit address tobe assigned to the unit.
ATTACH may also be used to add a spooling device to a
virtual machine, or to change the user's virtual console
address. The format is
ATTACH xxx TO userid AS yyy
where yyy is the user's (userid) virtual address and xxx is
RDR, PRT, PUN, or CON for the desired device, card reader,
printer, punch, or console, respectively.
The following form of the ATTACH command is used to add
to the system a direct-access device which was not available- 34 -

at system initialization time:
ATTACH ccu TO SYSTEfwj AS volid
where ccu is the channel and unit address of the device
containing the pack to be added and volid is the volume
label of the ?ack which is verified before incorporation
into the system.
TO may be abbreviated as T, and AS may be abbreviated

~ote.

as A.

DCP

(D)

The DCP command is used to type out on the console thecontents of CP-67 real core locations. The forrr·at is
DCP item it~m item •••where each item is a request for a memory location or groupof memory locations, as follows:
124-13F types out the contents
124(16) through 13F(16) inclusive, andof memory

18 types78(16).

fullword containing

DETACHout the contentsof thelocations(DE) -- privilege class A only

The format is
DETl>.CHRcuu

The DETACH command is used to remove a real device froma user or the system. The ccu is the real channel and unit
address of the device to be detached.
If the device was
attached to a user, any user with the operator privilegeclass can detach it. If the device is attached to SYSTEM,
only the system operator can detach it. CP owned volumes
cannot be detached.

DIRECT(DIR)

DIRECT
This<lock, unlock>command isused tocontrol user

access to

the

-

35 -

system directory for certain functions.
when the directory is changed online.

It is normally used

lock--prevents users from being able to LOGIN. XFER. or
LINK. since these commands access the DIRECTORY.
If the DIRECTORY is in use (user LOG'ing or
LINK'ing, for example), the following message isprinted:DIRECTORY IN USE
Attempt the LOCK again in a while.
If the DIRECTORY wasmessage is printed:

already locked. the following

ALREADY LOCKED
unlock--allows users to have access to the DIRECTORY for
LOGIN, XFER. and LINK. If the DIRECTORY was notlocked before, the following message is printed:
NOT LOCKEDDISABLE(DISA)--system operator only

The DISABLE command allows the operator to selectively
or collectively inhibit 2702 or 2703 lines for access to thesystem. If the line (or lines) is (are) inactive (no user
logged in or dialed), the line is immediately disabled. If
the line is active, it is disabled when the user has
completed his terminal session. The forwat is
DISABLE<linelist,ALL>

where linelist
command.

and ALLareasdescribed inthe

ENABLE

Note. If a line is active when a DISABLE command is issued
to it, and then an ENABLE is issued to the line before theuser completes his session, the line will not be disabled
but will reenable for system communication.

DMCP(DMCP)

This coromand du~ps selected parts of real core onto avirtual spooling printer. The arguments are identical to the
DCP corr.mand.
The operation and output is similar to the
DUMP coromand.

-

36 -

DRAIN(DR}--system operator only

The DRAIN command is used to suspend output or input
upon completion of the current file until a START command isissued. The format is
DRAIN xxx ••• xxxinull
where xxx are spool devices.
A confirmation message isprovided when the device is actually drained (that is,
stopped after completing the current file):
DEV xxx DRAINED.
Note. If a card reader is drained, a START command andactual start button operation are required to initiatespooling input.

DUM P
The D_U_~_P command allows the operator tosysterr abend dump (followed by software re-IPL).

ENABLEtakea(EN}--system operator only

The ENABLE command allows the operator to selectively
enable the lines on the 2102 or 2103 Transmission Control
for access to the system. The format is
ENABLE<linelist,ALL>

where linelist is a set of line numbers (in hexadecimal ccu
form) to be enabled with each line number separated by one
or more spaces.
If ALL is specified, all 2102 lines
configured into the systew in the REALIO module are enabledwith their specified SAD commands. The ENABLE command does
not affect lines alreadi enabled.

KILL(KI}--system operator only

The KILL command is used to log a user
if desired. The format is

off the system- 31 -

KILL<userid>where userid is the eight-character (oridentification of the user 'to be logged
receives the messageless) external
off. The user

LOGOUT AT ••• **BY OPERATOR**
and is logged out from the system.

LOCK(LOCK)--system operator only

The LOCK command should not be used except with theexpress knowledge of the CP-67 systems programmer.
It
seriously
affects
systems performanceunder
certainconditions. The command locks certain user pages in core.
The format is
LOCK userid xxx yyy
where userid is a logged-in user, xxx is the first user page
desired to be locked, and yyy is the last user page to lock.
xxx and yyy are hexadecimal values.

MSG(~)--anyuser

The MSG comwand may be used to send messages to theoperator or other users. These con~ands are stacked andissued to the user when there is no read up to the console,
to avoid interrupting his output.
If the user has issued
the command SET MSG OFF, any MSG sent to him will not bereceived or saved.
A message ('USERID e NOT RECEIVING)
indicating that a user is not receiving is output. The
format is~SG<userid,ALL> message

where userid is the eight-character (or less) external user
identification by which the user is known to the system.
ALL (privilege class A or B, only) causes the message to besent to all logged-in users.
If the user to which themessage is being sent is not logged into the system, anappropriate roessage is issued and the request is ignored.

QUERY

(Q)

The QUERY command

-

38 -

may be used toascertain the status

of the system (for example, which users are logged on, whatform of the paging algorithm is in use, what is the maximum
number of users allowed on). The format is
QUERY<USERS, Q2. MAX, LOGMSG,·userid'. DEVICE, PORT, DUMP>FILES, TIME,NAMES,

where
USERS returns the number of logged-in users andnumber of users dialed to other virtual machines •the• Q2 returns the maxirouro number of users in QUEUE2.
LOGMSG returns the message of the day.
•~AX

returns the maximum user load permitted.

FILES returns the spooled file count for the system.
TIME gives the connect and CPU time since login.
NAMES prints a list (four-up) of all users currently
logged inand their associated line
address, if
applicable.
If the user is DISCONNECT'ed the line
location is given as DSCON. If the user is in the LOGIN
process, the userid is given as (LOGIN).
userid gives the device where theshows he is not on system.

user is logged in or

DEVICE (xxx)• (ATTACHED,etc.)
system, or
specified).

the status
prints a list showingof all DASD and TAPE devices on thethe status ofdevice xxx,
only (if•

PORT (xxx FREE ALL) prints a list (four-up as in NAMES)
showing the status of all active communication lines (noparameter), the status of line xxx, all the lines
currently not in use (logged in or dialed), or the
status of all lines, respectively.

•

DUMP prints the address of the abend dump unit.

• indicatesuser.

privilege class A or

B, only; others

are any

Note. Most of the above operands may be abbreviated to one
character (that is. Q N for Query Names).

- 39 -

REPEAT(REP)--privilege class A onlyThis command is used to repeat the entire output of thecurrently active file.
A message is given when the repeat
starts or if the device is not active now. A repeat of up
to ten per command is allowed: however, when output is on
the tenth repeat, another repeat can be issued to a maximumof ten again. The format is
REPEAT xxx ylnull
where xxx is the output device (printer or punch) and y is
the count (up to ten). If no count is specified, one repeat
is assumed.
DEV xxx REPEATED userid
is given when the file is repeated.
DEV xxx IDLE
is given if the device is not busy. If the operator
terminates a repeated file, using TERM, only that repetition
is deleted. The file repeats again after termination until
the repeat count is zero.
Thus, if some current output is damaged, oralignment has
been performed, thefollowing
restarts the output:

if forms
sequence

REPEAT 30--command
TERM 30--command
DEV 30 REPEATED USFRID--response

SET

(5)

The SFT command allows the operator to establish someof the operating considerations
and functions of thesession. The format is
SER <Q2= nn,MAX= nn,LOGMSG,LOGMSG NULL,LOGMSG n,DUMP xxx>
where
02= nn establishes the maximum number of users allowed
in QUEUE2 (thequeue for those notdoing heavyinteractive work at the terminal).

- 40 -

MAX= nn establishes the maximum number of users allowedon the system to nne
LOGMSG and LOGMSG n responds with a message LOGMSG:
immediately followed by a read to enter the line.
LOGMSG with no parameter sets up or adds to a log
message. The LOGMSG n specification changes the LOGMSG
line number n. A null line entered (EOB after LOGMSG:)
terminates LOGMSG entry (for adding or initial setup) or
deletes line n if that option was used. Each line of
the LOGMSG is limited to a maximum of 7q characters.
LOGMSG NULL deletes the entire LOGMSG that may
been set up, allowing a new message to be set.

have

DUMP xxx sets the CP-67 system abend dump unit, wherexxx is the printer or tape address or AUTO to set the
dump to DISK.
The command can also be used to control
the amount of core dumped. xxx is CP for a dump of the
CP-67 nucleus and FREE storage pages only, or xxx is ALL
to dump all of real core. If this command is not issued,
the system uses the default of dumping CP core only tothe assigned disk area.

SHUTDOWN(SHUTDOWN)--system operator onlyThis coromand saves all spool files and accounting
information, terminates all systerr operation, and enters adisabled wait state.

SPACE(SPA)--privilege class A onlyThis command is used in case printed output is doingexcessive forros skipping. The output is not deleted but isforced to singles pace. The command is in effect only forthe current file.

START(STA)--system operator only

The START
command is used toinitiate spooling
functions on the specific devices xxx. More than one may be
started in one command.
If no operand is specified, allspool devices are started. The format is
START xxx •••• xxx I -null'
where

xxx arespool devices.

A

confirmation message

is- 41 -

provided of the form
DEV xxx STARTEDSTCP(STCP)

This coremand
format isis used tostore into real

memory.

TheSTCP location value value value •••where location is a real memory address (fullword), andvalue is the hexadecimal word to be stored. The function issimilar to the user STORE command for virtual storage
locations. The real PSW and REGISTERS cannot be changed.
Note. Extreme caution
S1nce indiscriminate
failure.

is advised when using this function
errors and/or
use causes system(T) --syste1l' operator only

TERl~

The TER~~ command is used by the operator to flush theremaining spooling output of the file currently in process
on the indicated unit. This would normally be used if it
was obvious the user involved had an error and it was not
worth processing the rest of his offline output. The format
is
TERM ccu
where ccu is the channel and unit address of the real device
on which the output is being processed.

UNLOCK(UN)--systern operator only

The same restrictions for LOCK apply to this command.
This command can only be issued after a LOCK command, andcan only be used to UNLOCK those pages that were originally
locked. The format
UNLOCK userid xxx yyy
where the arguments are the same function as in LOCK.

- 42 -

WNG(W)

The WNG command is used to inform a user, or users, of
information which is of i~mediate importance and cannot wait
for them to enter a mode where they can receive messages via
the MSG command.
The WNG message comes immediately out on
the typewriter, regardless of its status, and thus should be
used sparingly by the operator. The format is
wNG <userid,ALL> message

where userid is the external identification of the user towhom the message is being sent. ALL may be specified if themessage is of general importance.

For other CP console functions that are not in theoperator's privilege class, refer to CP-61ICMS User's Guide.

- 43 -

APPENDIX B: RELATIONSHIP OF CONSOLEFUNCTIONS TO PRIVILEGE CLASSThe following is a list of console functions and theprivilege class (es) from which they can be issued.
The
privilege classes are A for operator privilege, B for systemadministrator, C for IBM customer engineers, and D for anormal user. The first user with privilege class A to log
in to CP-61 is known as the system operator, of which there
is only one. For the definition of privilege class, refer tothe USER card in -Directory Allocation and Creation ft •Console Function

Privilege Classes
Sys. Ope

-

A

B

C

D

ACNT

X

x

X

ATTACH

X

X

x

BEGIN

X

x

x

X

x

CLOSE

X

X

X

X

X

DCP

x

x

DETACH ccu

X

x
x

X

x

DETACH KCCl]

X

x

DIRECTx

X

x

DISABLEXDISCONN

X

x

x

X

X

DISPLAY

X

X

x

X

X

DMCP

x

x

x

DRAIN

X

DUMP

x

x

x

X

X

DUM P

- --

x

ENABLEx

EXTERNAL

x

X

x

X

IPL

x

x

x

x

x
x

",q -

x

IPLSAVE

X

KILL

X

LINK

X

LOCK

X

LOGIN

X

X

X

X

X

X

X

X

X

X

X

X

X

LOGOUT

X

X

X

X

X

MSG userid

X

X

X

X

X

MSG ALL

X

X

X

PURGE

X

X

X

X

X

QUERY users,
names,userid,logmsg,time,files

X

X

X

X

X

QUERY port,dump,max,
Q2,device

X

X

X

READY

X

X

X

X

X

REPEA'T

X

X

RESET

X

X

X

X

X

SET cardsave,msg,
run,wng

X

X

X

X

X

SET max,logmsg,
Q2,dump

X

X

X

SHUTDOWN

X

SLEEP

X

X

X

X

X

SPACE

X

X

SPOOL

X

X

X

X

X

START

X

STCP

X

X

X

STORE

X

X

X

X

X

TERM

X

- 45 --

UNLOCKx'ilNG use rid

X

x

X

WNG ALL

X

X

X

XFER

X

X

X

46 -

X

X

APPENDIX C: RUNNING CP-67 IN A
VIRTUAL MACHINE
DEFINING THE VIRTUAL 67
To be able to run in extended (PSW) wode (that is, in 67mode) a virtual machine must have the first bit of theoption byte in the USER card (see RDirectory Allocation andCreation R) set to on, and preferably, must have a real
tiroer. The option byte is X'AO' or X'20'.
Some 2702 or 2703 lines must appear in
the virtual machine running CP.

the directory of

Figure 1: Directory Entry for V67 Machine
CP67.~,7,X'AO'<----the 'AO' is a 67 optio
USER HGFEDCBA,A6230
CORE 768K
UNIT 009.1052
UNIT 010.1403
UNIT 011,2540R
UNIT 012.2540P
UNIT 030,2703
UNIT 050.2703
UNIT 051,2703
UNIT 052,2703
UNIT 230,2314,SRG001.000.060
UNIT 231, 2314.CMS190,OOO,053,RDONLYUNIT 232. 2314,19ASYS,OOO,053,RDONLYUNIT 233.2314,CPCMS2,050.08F
UNIT 234,2314,CPCMS4.102,134*EOU*- 47 -

OPERATING CONSIDERATIONS FOR THE VIRTUAL CP-67
under CP-67
does notpresent special
Running CP-67
A
few
pointswillbeemphasizedhere.
difficulties.
a. If a minidisk is used as the CP residence volume, theRIO module must be altered to reflect the nucleus residence
location and other factors, such as disk label (avoid
CPDSK1), warm start cylinder, etc.
b.
When creating allocation tables for the virtual CP
residence volume if it is a minidisk (and, more generally,
for any minidisk when an allocation table is needed), toprevent CP from trying to use the cylinders out of theminidisk, those cylinders should be declared perroanent--nottemporary. For example, if the CP residence volume is a60-cylinder disk, when the allocation for that unit is being
run, cylinders 60-202 must be declared permanent (see FigureQ).

c. Creating the Virtual Directory.
All the virtual disks
used in the virtual directory must appear in the real
directory for the (virtual) machine running CPo
It isnecessary, in that real directory, to use the addresses
which are in the REALIO deck. For example, the C~S S-disk(CMS190 cylinders
000-053) is specified in
the real
directory as virtual device 231.
Note that the defined disk devices for user CP67 (Figure 1,
the virtual 67) are minidisks and that two of them, 233 and234, are not physically at cylinder zero. Because of this,these user P-disk areas must be labeled with a unique labelso that they may be located in the virtual directory. For
example, in the virtual directory (see Figure 4), the user
VSRGA has a 191 disk defined as residing on volume VCPCM2,cylinders 000-03F.
The label VCPCM2 is physically on
cylinder 050 of the physical volume labeled CPCMS2. asdefined in the directory for user CP67, the virtual 67
system. Because the label SRG001 is physically located on
cylinder 000, that label is used in both the real andvirtual system directories and should not be changed.
d. CP cannot run correctly if, at IPL time, two disk packs
have the same label. If the residence volume of the virtual
CP begins at a real cylinder 0 Cminidisks or complete
disks), it must be given a name different from the name of
the real CP residence volume (which is normally CPDSK1). The
label of the pack is specified in the RIO module in the
SYSRES macro.

-

48 -

Fiqure 2.

EXEC Procedure for Generating a LOAD Deckcpsys exec
&TYPE OFF
&ERROR &GOTO -EXIT
OFFLINE PUNCH &1 LOADEROFFLINE PUNCHCC PSA TEXTOFFLINE PUNCHCC ~.CCTON TEXTOFFLINE PUNCHCC ACNTOFF TEXTOFFLINE PUNCHCC ACNTIt-"E TEXTOFFLINE PUNCHCC CCWTRAN TEXTOFFLINE PUNCHCC CFSCOM TEXTOFFLINE PUNCHCC CFSDBG TEXTOFFLINE PUNCHCC CFSIPL TEXTOFFLINE PUNCHCC CFSMAIN TEXTOFFLINE PUNCHCC CFSPRV TEXTOFFLINE PUNCHCC CFSQRY TEXTOFFLINE PUNCHCC CFSSET TEXTOFFLINE PUNCHCC CFSSPL TEXTOFFLINE PUNCHCC CFSTACH TEXTOFFLINE PUNCHCC CHKUACT TEXTOFFLINE PUNCHCC CONSINT TEXTOFFLINE PUNCHCC CONVRT TEXTOFFLINE PUNCHCC CPFILE TEXTOFFLINE PUNCHCC CPLOCS TEXTOFFLINE PUNCHCC CPSTACH TEXTOFFLINE PUNCHCC CPSyt.~ TEXTOFFLINE PUNCHCC DEDICATE TEXTOFFLINE PUNCHCC DIAL TEXTOFFLINE PUNCHCC DISPATCH TEXTOFFLINE PUNCHCC DSKDUMP TEXTOFFLINE PUNCHCC EXTEND TEXTOFFLINE PUNCHCC FREE TEXTOFFLINE PUNCHCC IOINT TEXTOFFLINE PUNCHCC IOERROR TEXTOFFLINE PUNCHCC LINK TEXTOFFLINE PUNCHCC LOGON TEXTOFFLINE PUNCHCC LOGFILFS TEXTOFFLINF PUNCHCC ~RIOEXEC TEXTOFFLINE PUNCHCC ~VIOEXEC TEXTOFFLINE PUNCHCC PACK TEXTOFFLINE PUNCHCC PAGTRANS TEXTOFFLINE PUNCHCC PAGEGET TEXTOFFLINE PUNCHCC PLACE TEXTOFFLINE PUNCHCC PROGINT TEXTOFFLINE PUNCHCC QUEVIO TEXTOFFLINE PUNCHCC RDCONS TEXTOFFLINE PUNCHCC RDSCAN TEXTOFFLINE PUNCHCC RECFREE TEXTOFFLINE PUNCHCC RESINT TEXTOFFLINE PUNCHCC RIOCSC TEXT <--------Virtual 67 RIO module- 49 -

OFFLINE PUNCHCC SCANUNIT TEXTOFFLINE PUNCHCC SLTSn~ TEXTOFFLINE PUNCHCC STCONS TEXTOFFLINE PUNCHCC TMPSPACE TEXTOFFLINE PUNCHCC UNSTIO TE)""T
OFFLINE PUNCRCC UNTRANS TEXTOFFLINE PUNCHCC USERLKP TEXTOFFLINE PUNCHCC USEROFF TEXTOFFLINE PUNCHCC VIOEXEC TEXTOFFLINE PUNCHCC VSERCH TEXTOFFLINE PUNCHCC WRTCONS TEXTOFFLINE PUNCHCC IPL TEXTOFFLINE PUNCHCC SYSTEM TEXTOFFLINE PUNCHCC CHKPT TEXTOFFLINE PUNCHCC CPINIT TEXTOFFLINE PUNCHCC SAVECP TEXTOFFLINE PUNCHCC LOT SAVENUC&PRINT CP-67 C~RO GEN CO~PLETE&EXIT-EXIT &PRINT CP-67 CARD GEN ERROR
&EXIT

-

50 -

••••••••

Figure 3: Generating CP-67 from CMS
Example of EXEC Procedure to Create a Virtual CP-67 Nucleus
LOADVCP EXEC
CP CLOSE C
CP CLOSE D
CP PURGE READER
CP PURGE PUNCHCP XFER D TO.
<-----------XFER to wselfw
CLOSIO PUNCH OFF
EXEC CPSYS RELDR010
CLOSIO PUNCH ON
CP XFER DOFF
CP IPL C

Execution of Above Procedure--LOADVCP
loadvcp
11.07.17 CP CLOSE C
11.01.19 CP CLOSE D
11.07.21 CP PURGE READERNO FILES PURGED
11.07.23 CP PURGE PUNCHNO FILES PURGED
11.07.27 CP XFER D TO •11.07.31 CLOSIO PUNCH OFF
11.07.33 EXEC CPSYS RELDR010
CP-67 CARD GEN COMPLETE
11.08.23 CLOSIO PUNCH ON•• CARDS XFERED BY CP67••
11.08.25 CP XFER 0 OFF
11.08.30 CP IPL CDISK LOAD OK
CP ENTERED, REQUEST, PLEASE.
CP- 51 -

Figure 4.

Example of a Virtual CP-61 Directory

VDIRECT DIRECTOR
ALLOCATE

UNIT=230,VOLID=SRG001
DRCT 000.001
TEMP 002.003
PERM 004.004
TE~P
005,019
PERM 020,202*EOA*
DIRECTORY UNIT=230.VOLID=SRG001
OWN
CPDRM1,SRG001
OPERATOR USER csc,A6230,A,5CORE 256K
UNIT 009.1052
UNIT 00C,2540R
UNIT 00D,2540P
UNIT 00E,,1403
UNIT OFF"TIMRUNIT 190"2314,,CMS190,OOO.053.RDONLYUNIT 191,2314,SRG001,020.022
UNIT 19A,2314.19ASYS,OOO,053.RDONLY
*EOU*
,A,1
VSRG61
USER HGFEDCBA,A6230
CORE 512K
UNIT 009.1052
UNIT 00£,1403
UNIT 00C.2540R
UNIT 00D,2540P
UNIT OFF ,TItv'R
UNIT 190, 2314,CMS190.000,053.RDONLYUNIT 191. 2314,SRG001,023.021.RDSHAR=HGFEDCBA
UNIT 19A.2314,19ASYS.OOO,053.RDONLY
*EOU*
,D,1
VSRGA
USER HGFEDCBA,A6230
CORE 256K
UNIT 009,1052
UNIT 00E,1403
UNIT 00C,2540R
UNIT OOD.2540P
UNIT OFF,TIf.'iR
UNIT 190, 2314"CMS190,OOO,053.RDONLYUNIT 191,2314,VCPCM2.000,03F
UNIT 195,2314,SRG001,033,042
UNIT 196.2314.SRG001,043.041
UNIT 19A.2314.19ASYS.000.053.RDONLY* EOU*
USER HGFEDCBA,A6230
,D.1
VSRGB
CORE 512K
UNIT 009.1052- 52 -

UNIT
UNIT
UNIT
UNIT
UNIT
UNIT
UNIT
UNIT
UNIT
*EOU*
*EOD*

OOE,1403
OOC,2540R
00D,2540P
OFF,Tlt'R
190, 2314,CMS190,OOO,053,RDONLY
191,2314,VCPCM4,OOO.032
195,2314,SRG001,033.042,RDONLY
196, 2314.SRG001,043,047,RDONLY
19A,2314,19ASYS,OOO,053,RDONLY- 53 -

Figure 5.

Example of EXEC Procedure to Create a Virtual Directory

VDIREC"I EXEC&TYPEOUT OFF
CP CLOSE C
CP PURGE READERCP XFER D TO *<-------XFER TO "self"
OFFLINE PUNCH &1 DIRECTORCP XFER DOFF
LOAD DIRECT (XEQ)

Execution of Above Procedure--VDIRECT
direct vdirect
NO FILES PURGED** CARDS XFERED BY CP61**
EXECUTION BEGINS •••CP /61 ALLOCAT ION/DIRECTORY PROGRAf.~
FNTER INPUT DEVICE ADDRFSS - CUU :OOc
ALLOCATION STARTED FOR VOLUME SRG001
END OF ALLOCATION ON ABOVE UNIT.
FORMING DIRECTORY ON VOLUME SRG001
FND OF DIHECTORY CREATION ON THIS UNIT

-

54 -

RUNNING VIRTUAL CP-67

Running CP-67 under CP-67 presents the same characteristics
as running on another system, such as OS/360 CMS, underCP; that is to say, only one main difference exists from theoperator's point of view between running CP-67 on a real
360/67 and on a virtual machine:
it is necessary to hit
ATTN twice to obtain control under the virtual CP.
Note. It is possible to display some location of virtual
memory, by using the Display console function under the real(first level) CP, or the DCP console function under thevirtual (second level) CP.
The same is true for Store and STeP.
RUNNING A VIRTUAL MACHINE UNDER VIRTUAL CP-67

First of all. it is necessary to Dial the virtual machinerunning CP. Afterwards, there is no difference between
running under the first or the second level CP until
DISCONNECT or LOGOUT: if one of these commands is issued
without a parameter, control is returned to the first level
CP; if it is issued with a parameter, control remains insecond level CP.

- 55 -

Figure 6.

Running CP-67 from a Virtual Machinei<----230 is CP sysres volume230

CP-67 VERSION 3 LEVEL 0<----virtual CP-67 message

READY AT 00.00.00 ON 00/00/00
00/00/00 DEV 009 LOGIN AS OPERATOR USERS = 01
00.00.04*. SYSTEM VOLUME CPDRM1 NOT MOUNTED **RRRR •••• RING •••• GGGG<----virtual bell ringing because drums not ready00.00.08 SET DATE MM/DD/YY : 02/11/70
12.10.00 SET TIME BR.MM.SS : 12.10.00
12.10.00 START ((COLDISHUT)(REQ»
cold

**

COLD START**

12.10.08 FILES:- NO RDR. NO PRT. NO PUN
cp<----hit ATTN once for real CP<----hit ATTN second time for virtual CP
12.10.14 en 50 51
cp
12.10.23
12.10.28
12.10.35

set logmsg
LOGMSG: hello
LOGMSG:

cp
12.10.44

ipl 190eMS •• VERSION 3<----IPL·ing CMS from the virtual CP operator's
consoleLEVEL 0listf aaa bbb
FILE NOT FOUND
E(00002); T=0.06/0.34 12.11.23
listf
FILENAME FILETYPE MODE NO_REC. DATECALLUSE3 TEXT
·CP
12.11.53
12.11.58- 56 -CPkt
R; T=0.04/0.18 12.12.04
CP<----hit A~TN once for real CPq u<----querying users in real CP
13 US~RS. 06 DIALED<----hit ATTN again for virtual CP
12.12.12
12.12.16
12.12.16
q u
13 USERS.

q u<----querying users in virtual CP
01 USERS. 00 DIALED
CP
05 DIALED12.12.23
eMS
erase aaaaaaa bbbbbbb
E(00002); T=0.03/0.10 12.12.53
logout<----logout of CMS
T=0.37/3.28 12.13.02<----hit ATTN once for real CP
cp
disconnect
DISCONNECT AT 12.14.52 ON 02/11/70<----virtual CP-67 still available
cp-67 online

xdh65 qsyosu

dial cp67<----dialing into real machine to connect with virtual 67•• connected
machine in order to login to virtual CP
cp-67 online

xdh65 qsyosu<-------Virtual CP-67 identification

login vsrga
ENTER PASSWORD:HELLO
READY AT 12.14.05 ON 02/11/70
CP
i

190

C~S •• VERSION

3

LEVEL

0

login noprofile
R: T=0.04/0.25 12.14.48
listf asdfg zxcvb
FILE NOT FOUND
E(00002): T=0.03/0.17 12.15.01- 57 -

1* mac1ib sy

FILETYPE MODE NO.REC. DATEEATCHLIB fJ:ACLIB
37
SY
SPL1MAC MACLIBSY51SYSLIB
MACLIB
94
12/18
SY
AEDLIB
MACLIRSY
16
CPMACSMACLIB
264
9/03
SY
OSMACRO t>~ACLIB
8/12
SY
910
6/13
BRUINLIB MACLIB
8SY
R; T=0.03/0.07 12.15.18
FILENA~ECPb

CMS
logoutT=0.35/2.72 12.16.08
CP ENTERED, REQUEST, PLEASE.
CP
log aaa<----logging out virtual CP but holding the line
CONNECT= 00.02.12 VIRTCPU= 000.00.36 TOTCPU= 000.02.87
LOGOUT AT 12.16.17 ON 02/11/70
cp-61 online

xdh65 qsyosu<----virtua1 CP identification message

1 vsrg61
ENTER PASSWORD:HELLO
READY AT 12.25.54 ON 02/11/70
CPq user03 USERS, 00 DIALED
q names
OPERATOR -009, VSRG67

ipl 190
CMS •• VERSION 3

LEVEL- 051, VSRGB

- 050

0

printf aaa zzz
FILE NOT FOUND.
E(00003). T=0.06/0.34 12.21.00
logoutT=0.26/2.26 12.27.10
CP ENTFRED, REQUEST, PLFASE.
CP
logout<----logout of virtual CP without holding the line
CONNECT= 00.01.24 VIRTCPU= 000.00.27 TOTCPU= 000.02.36
LOGOUT AT 12.27.18 ON 02/11/70
tt- 58 -

cp-67 logoff<--------- 'real' CP-67 disconnect

cp-67 online

xdh65 qsyosu<----real CP identification message

1 cp67<----reconnecting to virtual 67 machine
ENTER PASSWORD:
CP67 WILL RUN UNTIL 24:00
FOR CMS UPDATES TYPE ·PRINTF INFO MEMO- UNDER CMS
FILES:- 01 RDR, NO PRT, NO PUNRECONNECT AT 12.30.21 ON 02/11/70
CP
12.27.56
12.28.03
cp

q n
OPERATOR - 009

12.28.08 logout<----logging out the operator of virtual CP
CONNECT= 00.18.05 VIRTCPU= 000.00.38 TOTCPU= 000.03.91
LOGOUT AT 12.28.13 ON 02/11/70
cplog<----logging out the virtual 67 machine
CONNECT= 02.19.39 VIRTCPU= 001.08.54 TOTCPU= 004.23.83
LOGOUT AT 12.32.14 ON 02/11/70
cp-67 online

xdh65 qsyosu- 59 -

Appendix D

SELECTIVE RELOCATING LOADER

The loader distributed with CP-67 will accept special
control cards to allow selective skipping and loading fromcards and tape.
These cards control the module name to be
skipped. the device address to load from and the printing or
suppression of invalid cards.
1.

To control skipping:card column

1
X

2
CTL

6
SKIP

11
name

where:
X is the control (12-2-9) punch.
CTL is the control command.
SKIP is the control function. andname is the module name to be skipped on the input
device.
2.

To control reading:card column

1
X

2
CTL

6

RDR

10
CCU

where:

x is the control (12-2-9) punch.
CTL is the control command.
RDR is the control function. and
CCU is the device address for the loader to resume
loading.
3.

~ocontrol printing:card column

1
X

2
CTL

6

WTR

where:

-

60 -

10

SINV
PINV
CCU

x is the control (12-2-9) punch,
CTL is the control command,
SINV is to suppress the printing of invalid card, or
PINV is to print invalid cards, andCCU is the device address for loadmap printing.
To create the selective loading tape, place the standard
CP-67 nucleus (with or without loader) in 80-80 card image
format on a tape using any utility such as OS/360 IEBGENER
or ~he CPTGEN EXEC procedure. Note:
The last card of the
CP-67 deck placed on tape must be:card column

1 2
X LOT

17
SAVENUC

where:

x is the control (12-2-9) punch,
LDT is the control command, andSAVENUC is the name of the module to execute upon completion of loading.
The CP-67 nucleus saved on tape can, of course, containmodified or updated versions of some modules. Once thenormal nucleus has been saved on tape, the following steps
are taken to perform a selective load. Assume that 2
modules, CCWTRAN and DISPATCH are to be loaded from a newer
card deck, skipped on the tape, but loaded with all theother rr-odules on the tape. The card deck should have thefollowing for~at:
9.
8.
7.
6.
5.
4.
3.
2.
1.

X CTL RDR CCU"DISPATCH TEXT- DECRX CTL RDR CCU
X CTL SFIP DISPATCH"CCWTRAN TEXT- DECKX CTL RDR CCU
X CTL SKIP CCWTRANX CTL SINV"RELDRXXX LOADER"

where:
1is the relocating loader for the desired printer (xxx)address for the load map.

2

is to suppress printing while skipping the desired
decks.

3is to prime the loader to skip CCWTRAN.

- 61 -

4is to commence loading from the tape mounted at CCU.

5

is the newer version of the CCWTRAN module that is tobe loaded instead of the one on tape.

6

is to prime the loader to skip DISPATCH.

7

is to resume loading from the tape mounted at ccu.

ais the newer version of the DISPATCH module that is tobe loaded instead of the one on tape.

9

is to complete the loading from the tape mounted at
CCU.

Place the card deck in an available card reader and IPL thatdeck.
The loading process will commence (make sure the tape andprinter are ready and the timer is OFF). The loading process
is corrplete when the message "DISK LOAD OK" is printed on
the 1052. The SAVECP program will write the nucleus on drive
230 unless otherwise specified by the SYSRES macro in the
REALIO generation.
Note:
If a loader is the first module on the tape, anunresolved symbol may occur in the load map. This can beignored. It is advantageous to have a loader at the frontof the tape since then the tape is directly IPLable to load(without selection) the normal nucleus following it on tape.
Obviously, for selective loading, the decks must be in thecard reader in the order in which they appear on tape. If
new modules are to be added, they can be placed withreplacement decks. For instance, if it was desired to add amodule "TEST TEXT" the deck could be placed between "CCWTRAN
TEXT" DECK (last card) and the control card (cards 5 an~ 6).
selective loading is a useful but sometimes awkward way ofchanging the nucleus. The best and easiest method is tocreate iplable tapes using the CPTGEN EXEC procedure. Make
one tape that is the master backup system. When modules arechanged, create a new tape using CPTGEN and ipl that towrite a new nucleus.
The CP-67 nucleus can be rewritten
while the system is running from a virtual machine if that
virtual machine is given write access to the system disk. A
re-ipl of the disk after shutdown will load the new nucleus.

- 62 -

INDEX
Abend ••••• 5,6,9,12,14,22,29,33,37,39,41
Accounting ••••••• 3,5,6,7,10.15,16,17,26
33,34,41
Accton ••••••• 10,49
Acnt ••••••• 33.34.44
Acntoff ••••••• l1.49
Administrator ••••••• 2,26.44
Allocation control cards
ALLOCATE ••••••• 23.24.25,31,32,52
DRCT ••••••• 23-26,32,52
TEMP ••••••• 23,24,26,27,29,32,52
TDSK ••••••• 23,24,26,32
pF.~: ••••••• 23,24,26,32,52
Attach ••••••• 8,10,11,21,33,34,35,44
Attached devices •••••••••• 5,10,11,29,39
Attention ••••••• 5,12,13,33
Attn ••••••• 55,56,57
Auto-dump ••••••• 5,21,41
Auto ipl ••••••• 5,7
Auto login ••••••• 2,7
Backup ••••••• 62
Begin ••••••• 24,25,44
Bell ••••••• 7,56
Buzzard utility ••••••• 16,11
Cecyl ••••••• 4,11,12.13
Checkpoint ••••••• 5,6
Clock ••••••• 5
Closio ••••••• 51
Cold start ••••••• 1,3,4,6,56
Configuration ••••••• l.34
Console functions •••••••• 3,8,9,16,26,33
43,44
Conventlons ••••••• 20.33
Dcp ••••••• 33,35,36,44.55
Decimal clock ••••••• 5
Dedicated devices ••••••• 10,11,29
Detach ••••••• 10,11,33,34,35,44
Devtype ••••••• 27.28
Diagnose ••••••• 26
Dial ••••••• 10,49,55,57
Direct utility ••••••• 16.17,18,23
Directoryallocation •••••••• 17,23,24,25
32,44,47,48,54
Directory creation ••••••• 17,23,24,31,44
47.54
DIRECTORY ••••••• 25,31,32
UNIT ••••••• 23,25.32,47
USER ••••••• 25,32,47
Disable ••••••• 33,36,44
Disconn ••••••• 44- 63 -

Disconnect ••••••• 1.55.57.59
Display ••••••• 11.33.34.44.55
Dmcp ••••••• 33.36.44
Drain ••••••• 33.37,44
Drums ••••••• 24,26.56
Dump unit ••••••• 5.21.29.33.39.41
D_U_M_P ••••••• 33,37,44
Emergency console ••••••• 6,1
Emergency logout ••••••• 1
Enable ••••••• 4,1,33,36.31.44
Error recording ••••••• 4.11-14.26
Error recording cylinder •••••••• 4,11,12
13,14.26
Format utility ••••••••• 1.16-19.23,24.61
Ipl ••••••• 1.4-1.12,14-17.19.20.21.37.44
48.50.51,56.58,62
Iplsave ••••••• 45
Kill ••••••• 15.33,31.38,45
Kt ••••••• 51
Label .••••••••• 1.2.18,19.23-26,29,35.48
Link ••••••• 7.31,36,45,49
Loader ••••••• 16.17,21,49,60.61.62
LOck ••••••• 33,35,36,38.42,45
Log ••••••••• 1,2,4.5.1,25.26.30,31,33.37
41.44,58,59
Login •••• 2.1,10.23.21.29.36.39.45.56,57
Logmsg ••••••••• 5,6,15,16.39,40,41,45.56
Logoff ••••••• 10.11,15.29.59
Logout ••••••• 7,10,38,45.55,51.58,5~
Machine check ••••••• 1,6,12.13.14
Malfunctions ••••••• 6,7.12,11
Messages •••••••• 1.4.5,6,8,9,11-15.21.22
31,33,34.36-41.43.56.58,59,62
Nucleus •••••• 15,16,19,22,41,48,51,61.62
Null ••••••• 3,19.37.40,41
Offline ••••••• 21.42.49.50.54
Online ••••••• 6.33.36,51,58,59
Operator's console ••••••• 8.9,16
owned volu~es ••••••• 4.13,17.26,35
Operator console functions
ACNT ••••••• 33,34.44
ATTACH ••••••• 33,34,44
DCP ••••••• 33,35
DETACH ••••••• 33,35,44
DIRECT ••••••• 33,35,44
DISABLE ••••••• 33,36.44
DMCP ••••••• 33,36,44
DRAIN ••••••• 33,37,44
ENABLE ••••••• 33,37,44
KILL ••••••• 33.37,45
LOCK ••••••• 33,38,45
MSG ••••••• 33,38.45
QUERY ••••••• 33,38,45

REPEAT ••••••• 33.40.45
SET ••••••• 33,40.45
SHUTDOWN ••••••• 33.41.45
SPACE ••••••• 33,41.45
START ••••••• 33.41.45
STCP ••••••• 33,42.45
TERM ••••••• 33.42.45
UNLOCK ••••••• 33,42.46
WNG ••••••• 33,43.46
Opposite ••••••• 33
paging ••••• 1,11.12.13.18.23.24,26,27.39
Password ••••••• 2.26.28.30,57.58.59
Performance ••••••• 38
Printer •••••••• 3.5,6.8.9.11,16,17,34,36
40,41.61,62
Priority ••••••• 26,27
Privilege class •••••••• 1,26,33.35,38-41
43.44
Pseudo-chronolog ••••••• 28
Punch ••••••• 5,9.11,16.17.33.34,40,49.51
54.60.61
Purge ••••••• 45,51,54
Query ••••••• 4,33,34,38.39.45
Q2 ••••••• 39.40,45
Reader •••••••• 3,11,16,17.18.20,24.29,34
37.51,54,62
Realio ••••••• 1,37,48,62
Reconnecting ••••••• 7.59
Repeat ••••••• 33.40.45
REQ option ••••••• 3
Restrictions ••••••• 42
Rprt ••••••• 21,28.29
Rpun ••••••• 28,29
Savecp ••••••• 50,62
SAVESYS utility ••••••• 16,19
Selective relocating loader ••••••• 60,61
serep ••••••• 14
Set ••••••••• 2-5.16.18,20,22.31.33.37,38
40,41.45,47.56
SET CARDSAVE ••••••• 45
SET DATE ••••••• 2.3.22,56
SET TI~E ••••••• 2.3,56
Shutdown ••••••• 3,6.15,33.41.45.62
Sleep ••••••• 45
space •••••• 5.16.20,23-27,29.30,33.41.45
Spool file ••••••• 3,4.6.15.29.41
Spooled input ••••••• 7.9.16,17.29
Spooled output ••••••• 7,8,9.16.17.29
Spooling ••••••• l.3.5.6,9,11.12,13.16,17
18.23.26,34.36.37.41.42
Start •••••••• 1.3,4.5.6,9.15.16,17,19.23
24.25,33.37,41,45.48.56
startup ••••••• 1,7- 65 -

G H20'()85 6-()

Stcp ••••••• 33,42.45.55
Store ••••••• 33,42,45.55
Sysgen ••••••• 7,11.21
Sysres ••••••• l.48.56.62.
System operator ••••••• l.25.38
System residence •••••••• l.2.11.12.16.11
18.23-26,48
System restart ••••••• 5.6.17
Systew. shutdown ••••••••• 3.6.15,33.41.62
System startup ••••••• 1.?
Tape ••••••• 5,6,11.34.39.41.60.61.62
Tdsk ••••••• 23.24.26.29.32
Temp ••••••• 23,24.26,21.29.32.52
Term ••••••• 9,33.40,42.45
Terminal ••••••• 1.8,9.15.21.22.26,36.40
Timer ••••••• 2?41.62
Timr ••••••• 28,32.52.53
Unlock ••••••• 33.35.36.42.46
Userid ••••••• 2,8.9.10.12,13.14.21,26,29
31,34.38,39,40,42,43.45,46
Utilities ••••••• l,16-19,23,24.61
Vdump ••••••• 16,21,22
VDUMP utility ••••••• 16.21,22
Virtual machinees) ••••••• 10,21,23.24,39
Virtual 61 eV67) ••••••••• 2?,47.4S.49.51
52,54-59
Warm start ••••••• 3-6.15,16,11,48
Wng ••••••• 33,43,45.46

International Business Machines Corporation
Data Processing Division
112 East Post Road, White Plains, New York 10601(USA only)
IBM World Trade Corporation
821 United Nations Plaza, New York, New York 10017(International)

READER'S COMMENT FORM
GH20-0856-0(CP-67/CMS) Version 3
CP-67 Operator's Guide

Pleas(' ('omnwnt on the usdulm'ss and readability of this pllhlication, slIggl'st additions anddt'ldiolls. amI list spt'cifie errors and omissions (~i\'t' page numhers). All commt'nts and suggestiolls hl'colllt' tht' property of lB~1. If you wish a reply, hl' surt' to include your name and address,

COMMENTS

fold

fold

fold

fold

• Thank you for your l'O\l!ll'ratioll, :\0 postage necessary if mailed in the U.S.A.
FOLD 0:'\ TWO LINES, STAPLE AND MAIL.

GH20-0856-0

YOUR COMMENTS PLEASE ..•Your comments on the other side of this form willlll'lp us improve future editions of this publication_ Each reply will be carefully reviewed by the persons responsible for writing and publishing this materialPlease note that requests for copies of publications and for assistance in utilizing your m'-fsystem should be directed to your IB'-l representative or the IB~1 branch office serving yourlocality_

fold

fold

.............................................................................................................................................................................................................................................
FIRST CLASSPERMIT NO. 1359
WHITE PLAINS. N. V.

BUSINESS

REPLY

MAIL

NO POSTAGE NECESSARV IF MAILED IN THE UNITED STATESPOSTAGE WILL Ie PAID IV ...

IBM Corporation
112 East Post Road
White Plains, N. Y_ 10601
Attention: Technicol Publicotions................................................................................................................................. :
fold

fold

•
International Business Machinas Corporation
Data Processing Division
112 East Post Road, White Plains, N.Y.tOSOt
IU5AOnlyj
IBM World Trade Corporation
82t United Nations Plaza, Naw York, Naw York to Ot7[International I

C)

c
Ci

..