GH20'D85i-8

Type III - Class A Program

Control Program-67/Cambridge
Monitor System(Cp·67/CMS) Version 3
Program Number 3600-05.2.005
Installation Guide

The purpose of this document
is to provide theinstallation with instructions
on creating a runnable
CP·67/CMS system tailored to his configuration.
There
are also considerations
maintaining\:'-~

as well as

both CP.·57 and CMS.

This manual
installing

for tuning the systemshould be read in its entirety

the system,as procedures

beforehave changed.

·,

PREFACEThe
manua Isfollowing

publications

arereferenced

CP-67/CMS User·s Guide

GH20-0859-0

CP-67 Operator·s Guide

GH20-0856-0

The
followi_ng· publications
information on CP-67/CMS:

thisadditional

provideCP-67/CMS System Description ~0nualin

GH20-0802-1

CP-67 Program Logic Manual, GY20-0590-0
CMS Program Logic Manual

GY20-0591-0

CP-67/CMS Installation Guide
SCRIPT User·s Manual

GH20-0857-0

GH20-0860-0

CP--67/CMS Hardware Maintainability Guide

First Edition(October

GH20-0858-0

1970)This Type III Programof a system.

performsfunctions

It has not been subjected

to formalthat may be fundamental

to the operationand maintenancetest by IBM,

Until the program is reclassified.
IE,'-l will provide for it: (:I) Central Programming
Service, including
design error correction
and automatic
distributionof correctionsrand(b) FE Programming
Service,including cesign error verification,
APAR documentationand submission, and applicationof Program
Temporary
Fixes or developmentof an emergency
bypass when required.
IBM does not guarantee
service results or represent or WaIIJnt that all errors will be corrected.
You

are expected

to makethefinal evaluation

as to the usefulnessof thisprogramin yourown

environment.
THE FOHEGOfNG
rs 1:-; UEU or ALL WARRANTIESBUT NOT LIilHTED TO, THE IMPLIED WARRANTIESFOR A PARTICULARPURPOSE.

EXPRESSEDOH IMPLIED, INCLUDING,OF MERCHANTABILITY
AND FITNESSThis edition applies to Version 3, Modification
Level 0, of Control Program-S? /Carnbridze
Monitor
System (360D:05.2:005)
and to all subsequent versions and modifications
until otherwise ~dicatedinnew cditions or Technical Newsletters.
Changesale continually

;::'"

made

t~~"t2:l pro\i;j·,<.'d It

to the information

herein.

Therefore,

the b;~c-k:of ~::1i~~~~~tJj.:·,·:ti'~·nfor readers'beforecomments.

using this publication,

If thisfC;-~1"!h~lS ;)cen

removed, address comments to: IB~l Corporation, Technical Publications Department, 112 East Post
Rc<~;; \i::l~l'!:- Pt:.-:~n~:.~..~...- .....Y--·'r1.~,ID~::e!.

CONTENTS
Introduc.tion

1

Installing

2

CP-67

CMS for CP-67 SYSGEN
Setup of Machine Configuration
Selection of Options
Real Tirner--&RTIMR
Virtual 67--&V67
ISAM Option--&ISAM
Obtaining CP~67
Obtaining the Utilities
Formatting of Volumes
Allocation and Directory creation
Creation of 'Permanent Residence Volume
obtaining CP-67 from an Existing CI-1S

CP-67

2
4

5
6
6
7
7
8
9

10
11
12

13

EXEC Procedures

CPUPAS11
CPMACGENCPMACADD
CPMACREP
CPGEN
CPUPMACCPSYS
CPPUNCHCPLIST
CPASr-~EN
CPTGEN

13
13
13
13
14
14
14
15

CP-67 Deck Formats

17

15
15

CP-.67 System
CP Utilities

f<1achi.ne

REALIOiguration

M-'lcroDefinition

for CP-67
19

SYSPES l-lacro
SYSGEN r-:ac ro
SIMPLEX Macro
I/O Block Definition Macros
Define Channel Macro
Define control unit Macro
Define Device Macro
Define Multiplexor Device

Macro

20
20
20
21
21
21
22
22

•
Generating-Named'"operating
Systems
under CP-67
CP-67 Maintenance Procedure
CPPTF EXEC

Tuning

CP-6J

InstallingCMS

DUMP/RESTORE Utility
CMS System Disk
Block Information
Bare Machine~-CMS
CMS Source Disk

Altering

the CMS System Disk

25
27
27

28

30

30
32
32
33
33

34

Nucleus
IPL'able System Disk
Saving eMS under CP-67
CMS EXEC Procedures

34
34
35
36

Maintaining the CMS System DiskCMS Maintenance Procedures

38
38

Changing Nucleus Resident Commands
Changing Disk-Resident
Commands
C-Disk as a Read-Only Extension of S-DiskeMS Considerations
Formatting the P-Disk
Obtaining a Nucleus Load l"lap
P-Disk Considerations
for the Bare Machine
Command Abbreviations
Im·t3~.12ticnof the Cr-1SB3.b::!h r.~onitor
Sanple Problem

39
40
40

42

42
42
43
43
44
45

I

INTRODUCTION•

The initial installation of CP-67 involves running CMS
on the bare machine. CMS is used to load the CP-67 basic
distribution tape
onto a disk,
read inthe F.EALIO
configuration for the installation and assemble the REALIO
and other modules, if necessary, to select the desired
options. Once this is done, an EXEC procedure is invoked topunch", the cp-67 nucleus, utilities, and' loaders.
The
punched decks are then used on the bare machine to format
the CP-67 v()lumes (sysres, drums, etc.) and to load thenucleus and directory on the residence volume. If CP-67 isalready installed, regenerations or new installations can be
performed from a CMS virtual machine.
Version 3 t.eve'I 0 of CP-67 has many new features thatmake it incompatible with previous versions.
For thisreason. users must not use utilities, loaders, or nucleus
decks from previous releases. In particular, the realmachineconfiguration description
requiresadditional
information to produce a valid RIO module.

~

.•..

CP-67eMS FOR CP-67

SYSGEN

To obtain CP-67. the CMS system is>used.
A description
follow~ of how to obtain eMS andrun it on the real machine(not under
cpl.
This
description
is intendedasaconvenientsummary, as moredetailed
information canbefound under ..
Installing CI'1S·.

disk.

First, restore the DUMP/RESTORE copyof the CMS System
The eMS System tape contains the following files:
file 1--IPL'able DUMP/RESTORE
file 2--a D/R copy of the ct-1S System

disk.

Then. IPL therestored disk.
Hit REQUEST
on the 1052
console. CMS
now allows you
to reconfigure theeMS device
address table to match thereal device configuration of theinstallation. The followi·ng question is asked:
Q1:

REDEI·'INEADDRESSES?
(YES, NO):
Answer YES, if the real addresses are different
from the standard CMS virtual addresses.

It is then necessary toenter the four-digit addresses
for the f o l Lowi nq devices:
console ..S-disk, P-disk, reader,punch, printer,tape one" and tapetwo.
Answer NO
to theCP-SAVE question.
The standard
Device.

addresses

VirtualAddress

Symbolic
Name

009
190
191**
192**
000**
000**
190**
OOE

CONI
D51<1
DS1\2
OSK3
DSK4
D5K5
DSK6
PRN1
RDRl

1052
2311,2314
2311, 2314
*2311, 231Ll·*2311r2314*2311,2314*2311" 231.4·
1403

ooe

25!}O
.-,
L.

eMS device

0-

{)OD

I>CF[i*2400* 2 i~"OO

,180

TAPl
TAP2

181

are listed

consolesystem disk (read .....
only)
permanent disk (user files)
temporary disk (workspace)
A disk (user files)
B disk (user files)
e disk (user files)
line printercard reader
tape drive
tape drivex» disk,

KG,

-

2 -

ana

the two

2ij

below ..

t..he

devices: they
configuration.

**

are .notincludeq

theinminimu.-n

The specified virtual addresses may be changed
time by the CMS LOGIN command.

at anyAfter entering the real device addressesr the eMS
initialization message is typed
CMS •• VERSION

n

LEVEL

m

Issue the eMS command
FORMAT P AIsLr

to format the P-disk to be used forcard punch and printer should bestatus~Place theTAP2 and issue

The
READY

CP-67

SYSGEN.

placedin

CP distribution tape on

symbolic drive

TAPE LOAD 4
All necessary CP files are loaded onto the P-disk.
These files
are of the following
filetypes forgeneration of CP-67 and the utilities:
SYSIN files, which are the CP source
Assembler Language:

decks written in

EXEC files, which contain procedures for assembling andupdating;
TEXT
files containing'system;theassembled

modules ofthefiles containing CP-61 macros for assembling thesystem and the real machine configuration;.

MA,CLIBASP360 and COpy files for creating and changing
macro library CPMACS MACLIB, when necessary;

thefiles containing
relocating loaderswithdifferent printer addresses (that is, 00 0,
0 0 E , 00 F ,LOADER

010, 030, 040);
Sp..MPLEfiles containing examples of therequired for system setup.

various decks

~t is
this
(on
cn
e
loaded) that the CP system is obtained.

3Note.
l:.Jhileexecuting CMS
on thereal machine,
the last
card of any punched deck must be manually run out from thecard punch.

SETUP OF ~.:.l\CHINE CONFIGURATION\.The real machine configuration
is described to CP via atext deck(object deck).
This text
deck is theresult ofassembling a group of realI/O definition macroswith theCMS Assembler(F). A re.al machine configurationis contained
among theP-disk files
as RIOeSC
TEXT. The
configurationthat RIOCSC supports is as follows:
Device3u2*.Address

1052
1Q03
25QOR
2SQOP
2703

009
010
011
012
030-03F

2400's2703 BSC
2311's
2314
2314
2314
2301
2301

040-04F
OSO-OSF
060-06F
070-07F
080-087
Oeo - OC2
OB8-08B
390
391
230 - 237260
261
330 - 337
101
100

(8 level ASCII,
110 bps Lines *)(2741 and 1050 Lines)(2741 and 1050 Lines)(2741 and 1050 Lines)(2741 and 1050 Lines)(2741 and 1050 Lines)

The customer is responsible
for terminal compatibility
with thisprogram. IBM assumes no responsibility
fort.he
impactthatanychangesto theIBr-l-supplied
products or programs may have .on terminals provided byot.hers.

If the above configuration
does not match the installation's
configuration ..a real
I/Osource-deck must
be constructedby usirg
the macros
sl?ecified in Section
IV andthe deckmust be read in and assembledo
sample simp+ex
and duplex
machine configurations
are contained
among the P-disk files\'ii t.h t~he identifiersof SIMPLEr. SAMPLE and DUPLEX SAt..jPLE.
To
getconfiauration-

4 -the real
I/O
definitions
for thetargetread
onto the P-oiskr
from t.he card reader;;rc~~~r. rEady i~~ and issue the'The

assembled

modules distrib~,Jted

with

this

13ys'tem

contain' 'the follO'1"lingoptions:&BTIMR
&V67
&ISAM

SETA
SETA

6

1
-YES·

SETC

If these options are not desired or'are to be changed,
update the LOCAL COpy file and reassemble the modules
affecteti, as described for each option below.
Real Tirner--&RTIMR
The real timer option &RTIMR provides for updating avirtual machines timer when the machine is in wait state, if
that virtual machine has the REAL TIMER option in the
DIRECTORY. This option allows
a dormant machine (forexample, APL) to be awakened by a timer interrupt.
(See
CP-67 Operator's Guide--ftDirectory Creationfl--for details.)
The module
DISPATCH.

to beassembled for

the &RTIMR

option is

For the real timer option the SETA symbol is set to thenu.111berof concurrent real timers that the installation iswilling to support. For instance, the statement
SETA&RTIMR
produces code intimerse6

the dispatcher to maintain up

to six real

Virtual 360/67 Option--&V67•

The virtual 67 option, f,V67 II provides code in the CP-67
nucleus to support virtual machines in which CP-67. can berun.
Those virtual machines '¥1iththe virtual 67 option
specified in the directory have the facility to operate invirtual extended PSW mode with
24-bit addressing. The
distributed system has the &V67 option selected. If theoption is not desired" change the LOCA.LCOPY value to'"'.--~&V67 SE'TA 0

use the exec
following modules:
and

CFSI:'!AIN
DISP1',TCH~

6 -procedure

CPUPASMtoreassembletheLOGONMVTOEXECPAGTRANSPROGINTQUEVIORESINTPSA
UNSTIO\'\USEROFF
VIOEXECISAM Option--&ISAM
The &ISAM ..
option allows the user to do I/O operations
involving self-modifying CCW commands on DASD device such as
used by OS/360 ISAM •..<;J:!,'lly
those userswith the ISAM option
in the D:(RECTORY have their
CCW ·strings checked for
self-modifying operation; thus not all users incur the
additional CP overhead.
The
Ccw'TRAN.

module to be assembled for the &ISAM option is
The distributed version has the option selected ..

If thevalue tooption is&ISAM

not desired,change the

LOCAL COPY

"NO·

SETC

and issue the eMS corr~and
CPUPASM

CCWTRAN

Note. The above procedure for options can also be applied
to code added by an installation.
The module can beassembled to selectively contain the installation's code
(1) by placing a COPY OPTIONS and a COpy LOCAL instruction
before the START card in the module being modified, (2) byadding a SETA instruction in the LOCAL COPY file,.that is,&RTlf.~R

SETA

and (3)module.

by checking for

OBTAINING

CP-67

1

the settingof the option

in thethe tailored CP-67 system, a card load deck
punched out and then loaded onto a properly

To obt.a.i n

must

be

u'cili-tiE'S
READY

£~

To
arxi card loader-Sa
ift:

i SSlli:::- t:rle

CF cardverify t~hat theCI"'lS oomma nd!

d~eck,

t.he C'p

card punch isinCPGEN(;1 62where'&1is the address of the printer that the loader
uses to print the CP load map.
A loadercalled RELDRxxx punches at the starbof the deck, where xxx, specified in'&1, is• the printer ~ddress in 3 hex characters(for example, OOE or 030)~.

&2

is the full name of the real I/O con-figuration deckthat was specifically assembled for the systemin the procedure above (for example, RIOCSC or
RIOABC) •The' above commandpunches out
the complete
CP loaddeck ,~'(about 250.0 cards with each text deck uniquely identified in,columns 73~75) and each deck
is separated by an identifying
card with the format
OFFLINE
where

fname

READ fname ftype

is the object

deck filename

and ftype is TEXT.

Note.
There is a pause after punching the
CP-67 LOAD DECK
to allow the user to clear thepunch and get the last card.
The user can continue by typing"ready" or he may stop hereby t.yp i nq '"quit-. This is clearlystated on the terminal as
the CPGEN operation proceeds.

OBTAINING

THE UTILITIESThe utilities

suppliedwith CP-61 are as follows:

BUZZARD
DIRECT
FO~,ATSAVESYSVDUNPThe CP utilities
arepunched out as partof the' CPGEN
procedure above.
The s~condfile output
contains alltheutilities~
each
identified
by a deck
separatorof theOFFLINE READ form (as outlined above for the CP load deck'.

'I'he CPutilities,
stand-alone programs

BUZZARD~
FORr.'AT and
SAVESYS,
areand must have the appropriate Loade-r on.t;"

DIRECT utility runs stand-alone or-under
CMS.
If it is run
stand-alone, it requires
a loader.
The VDUMP
utility runs
only under
CMS.
It is used toretrieve CP-67
dumps fromdisk after an ABEND in the CP supervisor;. Tl1e VDUMP utility
is run by the user specified in the SYSGEN
macro of RIOxxx
as the SYSDUMP
parameter.
In addition to th~ standard CMS
machine configuration,.
the usermust also
have a printer.reader device in his virtual machine as
UNIT

OF1,RPRTVDUMP. (See CP-67 Operator'sOperation", and~Directoryin order to run
under"Utility
details. ).

To obtain·

copiesof the loader,

OFFLINE

PUNCH

Guide--"VDUr.1P"
Creation"--forissue the CMS command

name LOADER

where name is either RELDROOO. RELDR010, RELDR030, RELDROOE.
RELDROOF. or RELDR040,. depending on the real address of t.heprinter ..

If an installation has a printer of any other address,
use the REI~DROOO LOADER and immediately' after the loader andbefore the TEXT file(s)to beloaded place
the following,
control card:
column

1 2

6

eTL

'WTR

column1 - 12, 2, 9 punchwhere

ccu is the desired

10
ccu

printeraddress.

The CPGEN procedurepunches out three loaders
for thespecified printer address &1 (that is,ODE) to be used \<lithvarious loading functions and also three loaders with a z0ro
address (RELDROOO),
which areuseful when' loading the CP
utilities.
Note.
If a 19ader
RELDROOO is used,noload
map isproduced, but the loading function
proceeds.
A load ,T::)!"' "'very usefulfor theCP-61 system. butof, little
use ',N'lH"T.
loading
the utilities,
thus
RELDROOO canbeused by an
installation to load a program without using the printer.
<0-

FORMATTING

Once

OF VOLUMES

the

CP

utilit.ies have

vol·lLn":'s

used

by

been
l)UTIcheao ur.,
system{fort.he

ci--t __
,r--:.

spoolinf]" nucleus residence, and directory) must be properly
f ormat.t.ed,
This is accomplished by meansof the FORMA'llutility ..The detailed instructions
for operating FO~"1AT arecontainedinCP-67
Operator's Guide.

Thesystem's
residence
volumefor CP is usuallyformatted with thelabel CPDSK1. as thatlabel is required
for IPLOing by name. If it is desired to change the volume
label~ the file SYSTEM SYSIN must be modified to reflect thedesiredsystem's residence
volume label
and SYSTEM SYSIN·
must be reassembled and replaced in the CP load deck.

ALLOCATION

AND DIRECTORYCREA~ION

All 2314 and 2311 volumes to be used for CP-67 spooling.and/orpaging
must
have
space
allocated.
Thesystemresidence volume
must have space
allocated for the system
directory and the nucleus ..
Note:
2301 and 2303 drums mustnot be allocated since they
arespeciallyformatted for dynamic paging allocation.
The
DIRECT utility (ALLOCATE control cards)
is used to allocate
space
for
the
systemresidence
volumeandothers,if
necessary.
(See cp-67 Operator's Guidefor details).
For
2314 residence.. the following
space mustbe allocatedaspermanent:
Cyl.

Usage

o

IPL and file directory
error recording (1 cyl required)warm start control (l cyl required)nucleus residence (2 cyl required)nucleus residence'SYSERR''SYSWRM''SYSDNC'
to'SYSDNC+l'

Thevalues fordefined in the:RIOxxx

For
allocatedtothesymbolic
cylinder locations
deck with the SYSRES macro.

2311
residence~as permanent:thefollowing

space

cyi.

Usage

0-1

IPL and file directory
error recording (1 cyl required)warm start control t1 cyl required)nucleus residence (5 cyl required)nucleus residence'SYSERR', SYSWRr<l·, SYSDNC··SYSDNC+4"

The

specif_ed..~ 10 -ayn.bc Id c

must

are

be

values are obtained
from the SYSRES macroin the real machine configuration

Cylinder 0 and others may be allocated. as DRCT space.
In addition, some cylinders may be allocated as permanent
for user file space or named system residencee
othercylinders must be allocated as TEMP (for spooling or paging)or TDSK.
•The directory roustbe created after the direct-accessvolumes are properly formatted. The detailed instructions
for setting up a directory deck are contained in the
CP-67 Operator's·Guide. A sample directory is contained on
the P-disk in the-file DIRECT SAr·1PLE.To obtain a printout'of that file, issue the CMS commandI·QFFLINE PRINT DIRECT SAMPLE
The directory is created by the utility DIRECT, theinstructions for which are in the operator's guide. The
allocation, of space on the residence volume (as des:cribedabove) must precede the directory creation.
CREATION OF PERMANENT RESIDENCE VOLUME
Once the volumes have been formatted and the directory
created.. the permanent CP residence nucleus should becreated from the CP LOAD DECK. The last module in the CP
load deck is the SAVECP module (serialization SCP)._ The
function of this module is to create, after the load thrbughthe card reader, an IPL9able copy of CP on the residence
volume from the core image.
The vo Lume address, label, and_nucleus cylinders are indicated to Sfl..VECP
from information
contained in
the RIOxxx
module, inparticular, theinformation from the SYSRES macro.
To create the permanent CP residence volume, ready the
CP load deck into an available reader. The first module in
the load deck must be the relocating loader, which prints
the load map of the system onto the printer. Perform an IPL
sequence on the card reader. The volume must be mounted andready before the load completes. It is advisable to clear
core before loading. If the disk is not ready, the message****

DISK CUD NOT READY****

is printed.
If the label on the disk is incorrect. the message.*.*

VOLID NOT dl~b21***.

is printed~
If eiti1ermessaqe is printed, remedy the situation and press
the EX'l'ERNAL button to retry. or start from the card load.
At the termination of the load and theresidence volume, the following message
operator's terminal:creation of
appears on

the
the

DISK LOAD OK
At this time, the permanent CP residence volume has beencreated and may be IPL'ed to initiate system operation.
OBTAINING CP-67 FROM AN EXISTING Ct-'1S-.

For thoseinstallations thathave anoperatingCP-67/CMS system, the CMS restore procedure outlineo.above
can be bypassed. The following steps can be used to obtain
CP-67:
1. Mount the distribution tape on an available tapedrive attached to the desired userid as '181'.

?

Using Ct-1S
issue a TAPE LOAD 4 command. The four
files will then load in their entirety onto the user's
P-disk space.
Note. About 40 cylinders of 2314 space are adequate tohold all the files and do assemblies.
3. Perform any necessary assemblies for configuration
or options
as outlined under "Setup
of Machine
Configuration" and "Selection of Options".
4. Follow the procedure
the CPGEN command.

under "Obtaining CP-67" using

S.
BE SURE TO USE THE NEWLOADEHS WITH THE NEW CP-67.

.,. 12 -UTILITIESAND THENEW

'CP-67 EXEC PROCEDURES(

The following CNS EXEC
procedures.the' CP-67
system.
These procedures
generate and maintain the system.

are distributed withshquldbe usedto..

CPUPASM
CPUPASMf&1 &2

CPUPASM is used to update a SYSIN file with an UPDA'IE file,
if it exists,
andto assemble
theupdatedfile or theoriginal if no UPDATE file
exists. &1 is the nameof theSYSIN file
to be processed.
&2 can be NODECK if no TEXT
file is to be produced.
The original SYSIN and UPDATE files
remain.
TheTEXT file createdis for the
updated Version
and is named&1 TEXT if no UPDATE file is applied,or a&lTEXT if an UPDATE was appliedleaving the original &1 TEXT.
No LISTING file is produ~ed.

Note
that
the
CPGEN/CPSYS/CPPUNCH
described below use .&1 TEXT in preference

EXEC
functionsto &1 TEXT.

CPMACGEN(CPMACGEN· &1
CPMACGEN createsand ASP360 files
should lJjUPdated

a MACLIB, named&1 MA.CLIB. fromall COpyon the P-disk.
The COpy and ASP360 files
using CPUPMAC before using this command.

CPMACADD
CPMACADD&1 &2

CPMACADD
adds file&2 <either
ASP360 or COpy) to lVj}\CLIB
named &1. The MACLIP must already exist andthe ASP360 or
COpy file should be upda t.ed before adding the file.
CPMACREP
CPMACREP&1 &2

CPMACREP replaces the file &2 {COpy or ASP360} in the MACT_,IB&1. The MACLIE rrust a~readyexist and the
ASP360 or
COpy file should be updated before replacementc
Note.
The
ASP360 filemaycontain' more than
one
MACHO
1efinition.
If one· macrois changed
theentirefile(ASP360)

IT'.mtbe aCl.ed or

replaced.. notthe

IT:2cr0:':~';'\\:

CPGENCPGEN 61 &2
CPGEN is used to punch a self-loading
utilities, and CP loaders.

CP nucleus,

the CP&1 = otrol 010 I 030 I 040 I OOE I OOF
Selectthecorrect relocating .loader
fortheinstallation, where the three characters indicate thesystem's printer address.
&2 = The name of the installation's
deck, for example, RIOCSC.

real I/O configuration

CPUFMACCPUPMAC &1
CPUFMAC updates a &1 MASTER file if it exists, and produce.sa &1 COpy or a &1 ASP360 file. If a &1 MASTER file does notexist, CPUPMAC updates an &1 COpy or &1 ASP360 file with &1
UPDATE" saving the old file as &1 MASTER and creating the
updated file as &1 COpy or &1 ASP360. There must be an &1
UPDATE file on the users disk, as well as a &1 COpy or &1
ASP360 file.
Note. This command must be used on all ASP360 or COpy files
which.~ave\updates, before using CPMACGEN.
Hint. Instead of regenerating CPMACS MACLIB every time an
ASP360 or COpy module is changed, it is more convenient tocreate a new· 1-1ACLIBcalled lVACUP MACLIB. The assemble
procedures automatically.accessr-'lACUPbefore accessing
CPMACS.
CPSYS
CPSYS
This EXEC procedure is used by the CPGEN EXEC fUnction to
pr-oducethe CP-67 load decks Tt contains control statements
and an ordered list of ·the nucleus components ..

/t- 14 -I

CPPUNCH&1 &2

CPPUNCHThis EXEC procedure.is used by the CPSYS EXEC function in
the CPGEN procedure. Its function is to select either the.&1 TEXT file if it exists or the &1 TEXT file. If neither
exists. an error message is printed.
St

CPLISTCPLIST &1
This EXEC procedure prints one or all files from a CP-67
LISTING tape generated by the CPASMGEN EXEC procedure. The
first file on the listing tape must be a TAPE LOG f i-Le , The
TAPE LOG file is merely a sequential list of the names of
the LISTINGS that follow. For example, see '.
TEMP EXEC. If&1 is ALL then all files (66) are printed, otherwise thetape is searched for thedesired file (for example,
DISPATCH) and that file {DISPATCH·LISTING) is printed.
CPASMGEN
CPASMGEN &1

c

This EXEC procedure is the one used to completely assemble
the CP-67 system producing a printed listing and a LISTING
tape. An auxiliary EXEC procedure with an ordered list of
all SYSIN
is necessary for complete
generation. For
instance, if TEMP EXFC consists of the following:
&1

&2

&1 &2
&1 &2
etc.

ACCTONACNTOFFACNTIME

then the following
in TEl.f;PEXEC:

CMS procedure assembles all

the modules

TEMP EXEC CPASMGEN
CPTGEN
CPTGEN&1 &2

This EXEC procedure is used only when running under CP~67r
since it useS
the XFER function. Its purpose is to create
an IPL'able tape for CP-67 disk loading. The &1 is the nameof the desired loader for the printer (for example, RELDROOEor RELDR030).
Th~ &2 is the name of realio configuration
ft,~<3t:le(ff)l-:-

e xan.pLe ,CPSYS EXEC procedure

F~:I(~it~S_C)
Q""~l1is E.):-l~~C:~;~coCeCtlre

to produce ac.se~; .t ....L-

load deck. A tape must beattach2G as 181: and a file called TAPE LOAD is read onto theuser·s P-disk.
Th~ reader is PURGED for this operation. The
EXEC procedure then writes the TAPE LOAD file on· taoe.

\..

-- 16 -

CP-61_DECKFORMATSThis section describes the format of the CP load deckand theutilities. The nameof each deckand its
serialization in columns 73-76 are specified ..

\CP-67 SYSTEM
The following text

files are contained in

the CP loaddeck:
ModuleSerial.. Relocating Loader (RELDRxxx))SLC·
000080loader control card--with PSA'_, PSA .
PSA
ACCTONACNTOFFACNTIME
CCWTRANS-.

CFSCOMCFSDBGCFSIPLCFSMATNCFSPRVCFSQRYCFSSET
CFSSPLCFSTACHCHKCUACTCONSINTCONVRT
CPFILECPSTACKCPSYI'-~.
DEDICATE.
DIALDISPATCHDSKDUMPEXTENDFREE
IOINT
IOERRORLINK
LOGON
LOGFILESMRIOEXECMVIOEXECP)'.CK
PAGTRANSPAGEGET
PLACE
PROGINT
C:' t: _s \ 1.~~~;RDCONS

ACON
ACOF
ACNT

CCW
CCOM
CDBG

CIPL
MAIN

CPRV
CQRY

CSET
CSPL

TACH
CKCU

CINT
CVT

CPF
CPR
CPSM
DED
DIA

DISP
DSKD

XTND
FREE
101

TERR
LTNK
LOG
LGFL

MRIO
MVIO

PACK
PAGE
PGET
PLC

PROG
RDCN

RDSChN"

RECFREE
RESINT
RIOxxxSCANUNITSLTSIMSTCONSIOTMPSP1\CE
UNSTIOUNTRANSUSERLKP
USEROFF_c~VIOEXEC
iV$ERCH/WRTCONS.
.. ICS CPENDSLC 020000
IPL
SLC 020800
CPLOCS CPLC
SLC 021000
SYSTENSLC 022000
CHKPT
SLC 023000
CPINIT
SLC 025000
SAVECPLDT SAVENUC

RDS
REC
RST
RIO
SUN
SLT
SCN
TMP
UNS
UNTR
ULKP

USE
VIOX
VSS
WCN
loaderloaderIPL
loadercontrol
controlcard--withcard--with

IPL TEXTIPL TEXT

controlcard--with

CPLOCS

loader control
SYS
loader control
CHKP
loader control
CPI
loader control
SCP
loader control

card--with

SYSTEM TEXT

card--withCHKPT TEXT

card--with

CPINIT

CP UTII.ITIESThe following- 18 -.

files are the CP utilities:

ModuleSerialBUZZARD
DIRECT
FORMATSAVESYS
VDUMP

BUZ
DIR
FOR
SSYS
VDMP

TEXT

TEXT

card---with SAVECP TEXT
card

;!'-1ACHINECONFIGURATION

DEFINITION

FOR CP-67

A description of the physicalmachine must be provided
for CP-67.
This description is contained in the
text deck
RIoCSC. If the distributed RIOCSC
text deck does
not meettheinstallation's
configuration(see "Setupoff'.1achine
Configuration").
a new realI/O deckmust becons't ruc+ed..from the macros
described below,
assembled,
and usedinplace of the distributed RIOCSC text deck.

Thephysical (real)machine is describedto CP via
control blocks containing in_formation about ..
the input/outp:ut
devices, channels,
and control units. These
control blocks
are generated
by the following
CP-67
macroswhich
aredescribed
below:REALIOr SYSRES,
SYSGEN,SIMPLEX,. DRCH,
DRCn, DRDEV~ and DMXDV.
The
following
conventions areusedthroughout
thisdescription:
1. variable
information
is indicatedinlowercase andsystem key-words
are indicatedin uppercase
letters, whereas they
are written in uppercase
when macrosarepunched in cards;
2.
< and> are used to bracket
choicesandthebrackets
are
not
part
of themacrodefinition (for example, RDEVPNT=<O,dlabel»would
be usedto Ln d.ice t.e that RDEVPNT=O or RDEVPNT=dlabel
could be used i.3.
a pair of 1"5 is used to indicate an optional parameterand theI's arenot a part of the macrodefinition(forexample. SIMPLEX Inl would be used to indicate that SIMPLEX
or SIMPLEX n could be used).
CP-67

MACROSREALIOK~CRO

The REALIO
macro is the firstcard of the
purpose is to generate the prerequisite entry points
by the system and to give a CSECT. name to the deck.
isIlabell

REALIO

Its

use

iTITLE:::vListing Header'lwhere -labelbecomes thealphabetic serializationtext deck and title
appears at the top of thepageslistinq.
Note ..label must be four or fewer characters.

in theSYSRES,HACRO

The
residence\

SYSRES
volume.

macro: is used
Its format istodescribethesystemSYSRES SYSRES=ccu,SYSTYPE=type,SYSVOL=volid,SYSERR=aaa,
SYSDNC=bbb,SY~~M=ccc
where <iCU is the address of the disk onto which the nucleus
is written; typeis
2311 or
2314,;
volidis theCP-67
formatted label of the volume (that is, CPDSK1'; aaa is thecylinder allocated as ,permanent for error recording; bbb isthe starting cylinder for nucleus
residence: and ccc is th~
cylinder for warm start control.

SYSGENMACROThe SYSGEN
macro is used
to describe
certainvariables used for system .operation. Its format
SYSGENinstallationis

SYSOPER=userid,SYSDUMP=dumpid,SYSEMRG=xxx,
SYSCNSL=aaa,SYSPRT=bbb,SYSPUN=ccc,SYSCORE=dddK

where userid is the operator·s id
for AUTO LOGIN; dumpid isthe user's id fer whom system
dumps are made available fromspooling
files;
xxx
is the 270x
line
address
for theemergency
consolestartup;aaa
isthesystemconsoleaddress; bbb is the system line printer: ccc
is the system
punch,and ddd
isthe storage
sizeof the realsystemexpressed in K.

SIMPLEXMACROThe Srr-1PLEXmacro
follows the unit, control
unit, andchannel specifications
for any given
CPU.. It provides forthe crea t i.on of the necessary tables required by CP and isdepend'?nt on theconfiguration
specified.
If a simplex
configuration
is described,
theSIf>TLEX macromustbefollowed by the END card. If a duplex configuration
is beingde sc rLbed , two
SH1PLEX
macrosarerequired:
thefirst.SIMPLEX macro is followed by the I/O definitions for anotherCPU; the second SIMPLEX macro is followed by the END card.
SIMPLEX

Inl

where tn' is either null for a simplex system~'1' for the
first half of a dunlex specification.
or f2~ for the second
half of a duplex configuration.

-. 20 -('I/O BLOCK DEFINITION MACROSThe following macros are used
input/output units available:

to describe the physicalDefine Channel Macro
Ilabel)DRCH

ICHANPNT=<O,chlabel>l,
RCULIST=list,CHANADD=c

where "label" is the symbolic label of this channel: chlabel
is the symbolic label of the next channel in the channel
list; list is the symbolic label of the first control unit
on this channel: and c is the channel address.

Define Control Unit Macro
Ilabel1

DRCU

IRCUPNT=<O,culabel> I

II

DEVLIST=dlabel,RCUADD=c,
IRCUPATH=<O"path>I.CUTAIL1=taill
where "label~ is the symbolic label of this control unit;
culabel is the symbolic label of the next DRCUmacro for the
next control unit on this channel. if any: dlabel is the
symbolic label of the first device defined for this control
unit; c is the control unit address; path is the value(hexadecimal) of the logical path for this cOntrol unit
(each control unit on a channel has a unique bit of theeight bits assigned to the channel and this bit or pathdefines which devices are accessed through this controlunit); taill provides a connection to this control unit fromthe channel--use the symbolic label of the channel on which
this control unit resides.

(Define Device Macro

Ilabel IDRDEVIRDEVPNT=<O,dlabel>1 ,RDEVCU=culabel,RDEVADD=ccu,
TYPE=type,DECUPTH=path ••where "label"is the symbolic label for this device; dlabel
is the symbolic label of the next device on this control
unit; culabel is the label of the control unit on which
this device resides: ceu is the channel. control unit, andunit address of this device: type .is the device. type(specified as xxxx where xxxx is 2311, 2314, 2321, 2301,
2303, 2400, 1403, 2540P~ 2546R, 2701, 2702, 2703~ or 2250:"path" is identical to the control units path (RCUPATH Ln,
DRCU) for this device and defines which control unit thisdevice uses.
Define Multiplexor Device Macio

1 label 1

DMXDVRDEVADD=ccu, TYPE=type, I SJI..D=n
I,
IRDEVPNT=<O,mlabel>I

where "label" is the symbolic label of this multiplexor
device: ceu is the channel, control unit. and unit addressof this device: type is the device type, which is one of
the fOllowing: 1052, 1403, 2540RDR, 2540PCH, 2701T, 2702T,
2703T, or 'IT35T ( where the 2701T" 2702T, 2'703T implies 2.
1052..2741-BCD or 27[t1-correspondence terminal coming'into a
2701, 2702..or 2103 and the TT35T is a teletype 33 or 35): n
is the. SAD address of the 2101, 2702, or 2703 andhas avalue of 0, 1, 2, 3, or q (the SAD address does not indicate
terminal type); For a 2701 which does not require a Sl-.D
command. specify a value of 4. For a 2703 which ignores SAD
commands, a value of 4 can also be specified. For a 2702,
the correct SAD value for the particular line must be
specified (0, 1, 2, and 3 are valid). Your local IBMCE
can supply you with the SAD numbers for each 2702 line; andmlabel is the symbolic label of the next multiplexor device
in the chain. There must be one DMXDV macro defined for each
Z701, 2702, or 2703 line.

Note. The ordered arrangement of the real I/O macros isrequired to properly generate the correct entri~s andtables.
-,The-,' 22 -multiplexor devices

must

be

defined beforetheselec~or channel devices. Each selector chann~l must be
cornp
Let.e
Ly definedin terms of ae'<.7ices, control unit" andthen channel (in that order) before the next selector
channel is defined,. If a simplex configuration is being
cescr5..
bed, the SH1PLEX macro must be followed by the END
card. If a duplex. confi.crur
at.Lonis belng described, t~NO
SIMPLEX
macros are requiied: the first $IMPLEX macro isfollowed by the I/O deflnitions for anothe~ CPU; the second
SIMPLEX macro is followed by the END card. '.,Ah example of a real I/O
configuration is as follows:source deckfor asimplexREALIOSYSRES

TITLE='SAMPLESIMPLEX'SYSRES=230.SYSTYPE=2314,SYSVOL=CPDSK1.SYSERR=004~
SYSDNC==19 fl ,SYSWRH=2 02.
SYSGEN SYSOPER=OPERATOR,SYSDUMP=CPSYS,SYSEMRG=020,
SY~CNSL=009 ,.SYSPRT=030:,SYSPUN=032, SYSCORE=768K
TYPE=1 052
OPCONSOL DMXDV :RDEVPNT±PRIWrERl ,R.DEVADD=OO'9,
PRINTERl DMXDV RDEVPNT=CARDRDR1,RDEVADD=030,TYPE=1403
RDEVPNT=PUNCH1. RDEVADD=031, TYFE=2 5'-l
ORDR
CARDRDRl Dl'-'lXDV
Dr.-1XDVRDEVPNT=TERrvl01 •RDEVADD= 032 ,TYPE=2 5qopen
PUNCHlTERl'-lOl DMXDV RDEVPNT=TER1'102rRDEVADD=020,TYPE=2702T f SAD=l
TERl'-;02. DMXDV RDEVPNT=TERM03,RDEVADD=021,TYPE=2702T,SAD=1
TE Rl'-'l03
DMXDV RDEVPNT=TERMO 4, RDEVADD=02 3,TYFE=TT3 5T" SAD=2RIOS

RDEVADD=04E,TYPE=2703T,SAD==4
RDEVCU=R28 2OA,RDEVADD=l 0 0, TYPE=23 01,DECUPTH= 80'
DEVLIST=DRUM2,RCUADD=O,CUTAIL1=CHAN1"RCUPATH=80
RCULIST=R2820A,CHANADD=1 CHANPNT=CHAN2
RDEVCU=R2314,RDEVADD=230,T¥PE=2314,DECUPTH=40"
RDEVPNT=DISK31DRDEV RDEVCU=R2314.RDEVADD=231,TYPE=2314,DECUPTH=40,
RDEVPNT=DISK32

TERl'-'14EDMXDVDRUl'Q
DRDEV
R2820A
DRCU
CHANl
DRCH
DISK30DRDEV
DISK31'*

I1'*

e- -.••••DISK3"]
R231L~
CHAN2
DRm"il
DISK4

R2841BSCOPE1
R22_50CHAN3
TAP~:lTJ\PF2
",-,

.,_
:~""

• .'

.. ",

.,.... '.._.i- 1:'":'DRDEV RDEVCU=R2314,RDEVADD=237,TYPE=2314,DECUPTH=40
DRCU
DEVLIST=DISK30,RCUADD=3,CUTAIL1=CHAN2,RCUPATH=40
DRcn
RCULIST=R2314,CHANADD=2,CHANPNT=CHAN3DRDEV RDE\lCU=R2841B.RDEVADD=393 ,TYPE=2303 ,DECUPTH=80,
RDEVPNT=DISK4DRDEV RDEVCU=R2841B,DEVADD=390,TYPE=2311,DECUPTH==80,
RDEVPNT=DISK5DRCUDEVLIST=DRUM1l1'RCUADD=9 ,CDTAIL1=CH]\N3" RCUP]\.TH=80,
RCUPNT=R2250.
DRDEV RDEVCU=R2250.RDEVADD=306~TYPE=2250,DECUPTH=40
DRCU
DEVLIST=SCOPE1#RCUADD=0,CUTAIL1=CHAN3"RCUPATH=40
DReH
RCULIST=R2 841B II CHANADD= 3 ,CHAl'WNT=CHANODRDEV RDEVCU=R2400A RDEVADD=OCO,TYPE=2400,DECUPTH=80
RDE,lPNT=TAPE2DRDEV RDE'IlCU=R2400F",RDEVADD=OCl ~TYPE=2t~OO DEC'UPT1-!=80qf)D.(~~(~iJ DE'i'jLI!::/r'::::fl'l\f~~l l{CU.~~.DI)=C~C(J'I /i1 l.Jl ::=CI-iAl"l 0 rI l:ZCUPA rJ-l=8 0
Ff- 23 -*

CHA'KO
D2701P.

R27Cl!~

CHAl\OADRCRRCULISrI.'=R
240 Oi'''. ~ CHANAl)D= 0 ~CHANP~lT=CHANOADRDEV.F.DEVCU=R2701A;rRDEVADD=010eTYPE=2701..
DECUPTH=80
DRea
DRen

DEVLIS'I'=D2701Ag RCUp_DD=l ~CUTAIL1=CHl\NO}~,q RCUPATH=80
RCULIST=R2701A.CHAt'ADD=O~CHANPNT=cm'_NOE

R2701BDRDEV RDEVCU=R2701B,RDEVADD=012,TYPE=2701,DECUPTH=80
DRCU
DEVLIST=D 2701E ..
RCUADD=l-. CUTAILl =CHA NOB, RCUPATH=8 0

CHANOB

DRCH

D27C1B

RCULIST=R2701B,CHANADD=O

SH:PLEX
END

Note. _.,
Nonshared
multiplexor devices,
exceptfor tapes,
should be defined as
separate channel.
control unit.
anddevice blocks(macros): thatis, eachdevice has
its ownset,
as shown
for D2701A and D2701B
above. Thisavoidslock-out problems on that channel
if unusual I/O operations
are performed by users on a particular device.
Furtherexamples of REAL I/O
configuration
decks
are
available fromthe CP-67 distributed P....
disk
files: SIMPLEXSAMPLE, DUPLEX SAMPLE. ahd Rrocsc SYSIN •- 24 -

)
GENERATING "'NAMED'"OPERJ..'I'INGSYSTEi,1S
UNCER.

CP-67

Providing a user with the capability of performing an
IPL function ·by name, rather than by device, requires theinstallation management to save a copy of this system on a
DASD device in paging form. The s~lf-loading deck which
performs this is entitled SAVESYS. \It accepts a control~ard of the form
SAVE VOLID=cccccc,UNIT=ccurFP=nn,LP=IT~,CYL=ppp,DISK=tttt
where
cccccc isvolume;thevolume label

of

the

receiving

DASD

ccu is the channel ..control unit, and device address of
the receiving volume;nn is the page number of the first page(in hexadecimal);

to be written

mm is the page number of the last page(in hexadecimal).

to be written

ppp is the starting cylinder of the image:tttt is the device type <either 2311 or 2314).

The space indicated on the card must have been previously
allocated as permanent space on the volume (see "SAVESYS"
under "Utility Operation" in the CP-67 Operatbr's Guide, forformat conventions).
The information on t.he control card
must match that information provided in the SYSTE!>1
moduleassembled and loaded with the system. In that wodule thesystem name, location, shared pages, if any, and operating
conventions are established. In the distributed SYSTEM
module, the system name is CMS, and eighteen pages are
saved, beginning at page 0, up to and including page Xt11'~'I'hesaved copy of CMS is written on the 2314 volume labeled
CPDSKl at cylinder 200.
The SYSTEM' SYSIN filemacro, which has the format
SYSTEMis constructedusing aSYSTEr1

NAME=nnn,FIRSTP=aa,LASTP=bb,TABLE=ttt,
VOLID=xxx,EXADD=ccc,SYSMASK=sss,RUNKEY=kkk,
SYSTAB=yyy

where
nnn

is the name for the system:.~ 25 -

aa
bb
ttt

is the first page saved;is the last page saved~is the label of the SI;.fPTABLE macro
associated with this system:
xxx is the label of the volume on which thesystem is saved;
ccc
is the virtual machine 22(ecution address;
sss
is the virtual machine system mask;
kkk
is the virtual machine protection key:
yyy .~s the label of the shared page table
1n PAGTRANS if this system has sharedpages: otherwise it is zero.
The SWPTABLE
following format:
ttt

macro

used with th~ SYSTEM

macro

has theSWPTABLE DASDORG=ccc,FIRSTP=aa,LASTP=bb,
FIRSTSP:::::xx"
LASTSP=yy DISK=ddd
/I

where
ttt
ccc
aa

is a label (same as ttt in SYSTEM macro):is the cylinder address where the system is saved:is the first page saved:is the last page saved;is the first shared page, if any;is the last shared page" if any;is the disk type where saved, 2311 or 2314.

bb

xx
yy

ddd

The SYSTEM macro builds a table
to· define the name andrunning attributes of the saved
system.
The SWPTABLE macrobuildsa model SWPTABLE
thatis mapped to thevirtualmachine
S\'lPTABLE in core
to gi ve thatmachineaccess(through paging) to the saved system.

The number of cylinders required to hold a named systemdepends upon the number of pages .saved and the device type.
For a 2314, one
cylinder holds 30 pages: a 2311 cylinderholds 8 pages. Thus,eMS with 17 pages requires
one 2314
cylinder or three 2311 cylinders.

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
X92000Q'.
To loadSAVESYS
into tigher core,changetheaddress in the SLC··20000 card
at the front of
the SAVESYS
text deck.
The procedure
follows:

1.

-

for creating

the page-form

copy isas

Load the required system
into merrory, with t.he addressstop
switches set
to a location
within thatsyst~mwh~~eexecutionmay
be r e-sumed wi t.lrout; t.ne
system26 -,assuming any previous state in
the machine(that lSt!
registers,
lower core- locations, etc.).
For CMStheaddress stop location is X'FO'.
2.

When thesystem has entered manual state(that is, theaddress has beenreached), load the SAVESYS
deck into
the system card reader and load from the reader.

fI

3.

If the.save was successful,a message
operator's terminal to that effect.

appears

on theNote.
The following
procedure must
be used to run
Version 2 of CMS·under
Version 3 of CP as the named
system CMS:
eitherthe SYSTEM module must
be changedin CP, as version 2 of CMS
has only 3 shared pagest or
the save1 copy of Version 2 of CMS must be given a nameother than CMS.
See ftSaving CMS-under CP-67"
detailsofpreparingCMS
forfunction.

CP-67 MAINTENANCE

in thismanual for
the
CP-67
SAVESYSPROCEDURE

when corrections haveto be made to a CP-67 module, a
PTF is made available to the installation through the normal
channels. The
PTF is in a form suitable for a CHS OFFLINEREAD or TAPE
LOAD function depending upon
the distribution
medium.
A special EXEC procedure
is distributed to be used
when applying PTF·s.
A descriptionof the use and functionof this procedure is given below.
-,
CPPTF EXEC
CPPTF

&1 &2

where &1 is the name of the CP-67
module to receiv~
the PTF and &2 is the PTF number (for exarop.l e , epPLF'
DISPATCH A32486C]Q.
Having first loaded the
PTF ento the maintenance P-disk (using OFFLINE READ or TIU'E
LOAD) the pserthen issues all necessary
CPPTF EXEC
procedures to effect the change.
One PTF may involve
changes to several modules.
For instance, PTF :HE.'.>.,( ':~A32486CA
may
create(t;hrough loading
on to theP-diskl
the following files:
DISPATCH
PAGTRANS

A32fH36CA
A32486CAUNSTIO

A32486CA

The usermust then -issue

the fo Ll..ovi.nq eMS commands:

.
CPPTF

DISPATCH
PAGTRANSUNSTIO

CPP;TF

CPPTF
The function•

TUNING

A32486CA
A32486Cll
A32486CAof the CPPTF

is as follows:

The PTF file (for example. DISPATCH A32486CA) isapplied to the corresponding
SYSIN file
(thatis. DISPA'I'CH SYSIN).
using
the
CMS
UPDATE
program.
The
PTF
creates a new
SYSIN
file
replacing the oriqinal.
Iftheinstallation
wishes to preserve the original SYSIN
file, itshould be saved beforehand or copied·and given a
new name.
Once the new
SYSIN has been created,
it should remainon the disk (or be available>
since further PTF·s
that way be applied
to themodulemay
requirethata previous
PTF
beapplied first.
The CPUPASMEXEC procedureis.
then ihvoked to assemble the new SYSIN file.
Iftheinstallation
has
its
own UPDATE
file,
CPUPASM applies
it to the now modified SYSIN.
The installation
should checkthat any
UPDATE
file interfaces correctly to the SYSIN file once
PTF·s
have
been .applied.
The
CPPTF
EXEC
procedure
finallypunches the&1 TEXT file,
prints a completion message. and exits.

OF CP-67

To prevent paging overload, CP-67
allows only a subsetof theusers to be dispatchedat one time.
There
are twoqueues for such users;
both
queues are served round-robin,
and the queued
user remains in the queue until
he has used
an allottedamou~t of computer
time. A user
enters QUEUEl
whenever he issues a carriage
return from his terminal.
HE~
stays in QUEUE1 until the time quantum (400 milliseconds)
isused or his virtual machine
requires more console activity~
If a une r exceeds the QUEUE1 time quantum, heis placed in
QUEUE2 or queued to be placed
in QUEUE2, which has, a timequantum of five seconds.
The QUEUEl
time quantum is set t.oallow an average edit request to be serviced~
The
pagingalgorithm
is tiedto thisdispatchingsystem"Whenevera pageof memoryis required,
PAGTRANS
uses a page assigned
to a user who
is notin QUEUEl
or
QUEUE2{and thereby
pagingrunnableagainstunrunnable
users} •.The intent of this queue structure is to set a limitonthe numberof tasks thatcancompeteforcoropu+er
resources (men.ory and cpu), and to segregate short execution
tasks (for example
edit requests) from long execution tasks(for eYarnple,' FORTRAN compilation).
By so segregating thetasks,
limiting thenumber oflong
execution tasks,andqcan be avoided.

The queue
sizes areautomaticallyadjusted
IPL time
based upon
real core size.
The queuevarious core capacities are
256K
Q1
Q2
The operator
Q2.

512K

.3

6

1

3

has a console

768K
9
6

functionat system
sizes for1M
12
9

to change

thesize ofINSTALLING

DUMP/RESTORECNS·UTILITY

To createa CMS
System disk,
place thedistribution
tape on a tape drive~ address
acuu. Clear core and IPL thetapeby pressing
theLOAD button.
When
the wait
light
remains
on. Andthe system
andload lights
go Off"hit
REQUECT· on the online
console.
Dm,:p/RE STORE
is given
control.
CMS may be restored under
CP-67. ~f CP already exists.
~erely. attach thetape to a virtual machine
and issue IPL
ccu.
Produce an ATTENTION interrupt.

The console address is dynamicallyset. If replies are.incorrect
while
the
DUMP/RESTOR.E
is executing,m~PRST
reinitializes
itself andrepeats Question
1.
If an I/O
error is sensed on the disk or tape, it tries to rectify theerror>'condition.
If eu coe ss f u Lj it continues. If not, it
prints out a message and terminates.

Termination,either after
a successful operation
because of an errox. places the CPU in the wait state.
Q1:

TASK? (ftDU~pH • "REST"):
DUMP--disk to tape
RESTORE--tapeto disk

Q2:

DEVICE TYPE? ("2311" , "2314n):
specify the disk device type

Q3:

TAPE ADDRESS? ("OCUUR):
self-explanatory.
~ust enter a four hexadeciroal
reply (for exarople, 0181, 0275)

Q4:

DISK ADDRESS? (flOCUUW):
self-explanatory_
The reply must be four
hexadecimal digits (for example, 0191,0290).

Q5:

REwIlI.'I) 'TAPE?

("YES"qor"'NO"j:~his
applies
to before andafter
the operation.
Obviously~ since the tape after
IPL is positioned atits second file. the answer must be NO.

Q6:

NUMBER OF

CYLINDERS?

(ft ONNN"} : .

self-explanatory.
The reply {rust be four decimal
digits (for example~ 0203, 0100). For restoring the
distribution tape, specify 203 cylinders for a 2311
or 54 cylinders on a 2314.

..

STARTING

Q8:

BEGINNING OF TAPE? ("YES~ , "NO"):The answer determines if a tape mark is to be writtenahead of the file. If YES, a tape mark is written; if·NO. the·EOF at the end of the previous file serves as
the tape mark for the beginning of this·file.· (Whenrestoring the distribution tape, 08 is not asked ..
)Q7:

CYLINDER?

self-explanatory.
"0000".>(ftONNN"):

(For

the

systemdisk,

reply:.

after the last
The DUMP/RESTORE operation begins
question is answered. If either device is not ready, theprogram waits for its ready state. When restoring, the diskneed not be formatted or DASDI'ed. D~PRSTformats the disk
as it is being restored ..
Upon encountering an EOF, satisfying the amount ofcylinders specified in Q6~ or executing a SEEK beyond thedisk limits, the operation terminates with the message'DUMP/RESTORE MOVED nnn CYLINDERSTHERE WERE nnn RECOVERABLE TAPE ERRORS.'TASK? ("DUMPfi.~REST"):restore
DEVICE TYPE? (R2311","2314"):2314
TAPE ADDRESS? ·("OCUU"): 0181
DISK ADDRESS? ("OCUU"): 01.90
REWIND TAPE? ("YES"."NO"): no
NUr-mER OF CYLINDERS?
(..
ONNN"):
0054
STARTING CYLINDER?
(flONNN"): 0000
BEGINNING OF TAPE? (flYES","NO"): no
DUMP/RESTORE MOVED 054 CYLI!<iTIERS.
THERE r,JERE 001 RECOVERABLE TAPE ERRORS.

I
I
1
1
1
1
I
I
I

1

Figure .1. Restore procedure for eMS d~stribution tape

31 ---

eMS SY3TEM

DISK

once restored,
following appearance:

the· CMS

systemdisk\
Plock Information
O- 2...· . IPL pOlnters, CCW • s, etc.

=

assumesthe\

CMS190

3

label

4

Master File Directory

5-7979
1.

2.
3.
4.

Nucleus Text decks in one file called NUCLEUS 3.0, in
which each individual tex~ deck is preceded by an
OF·FLINE REJI..O filename TEXT card. The nucleus text decks·
are also present individually.
Disk Command Modules.
Disk Command Texts.
EXEC Procedures

7980-8100
IPL9able Nucleus (0-12000x and loader tables>.
The nucleus routine, NUCON, contains a device table. It
has been initialized as follows:
S-Diskp-DiskT-DiskCONSOLECREADR
PRINTER'===CPUNCH

=
=

TAPl
TAP2
DSKtl

DSK5
DSK6·

CRTl
These

values

=
=

=
=

=

=
=

are the stan~ard

0190
0191
0192
0009
OOOC
OOOE
OOOD
0180
0181
0000
0000
019C
0106
eMS wachine device addresses.

SYSI\1) of every Ct-1Sroutine.

FLTERING

NUCLEUSTHE CMS SYSTEM

DISK

•

After
CMS Sourcecommandrestoring
Disk asthe CMS Source Disk,a P-disk,
191.
Log

OFFLINEPUNCH NUCLEUS

IPL CMS. Use thein andissue the3.0.

The file
punched. about 1800
~ards, contains all
the text
decks that constitute the CMS nucleus.
The cards should now
be interpreted.
separating the individual
text decks .is an"OFFLINE READ name
TEXT" card. Keep thisnucleus deck.
It,is needed whenever changes are to be made to the contents of
the System
disk.
(NUCLEUS
3.0 is also
on theCMS Systemdisk. )The LOADER
deck supplied
is usedto IPL the nucleus
under CP(that is, it recognizes the standard
CMS virtual
deviceaddresses).
If thenucleus is to be
IPL'edonincompatible device addresses, theloader deck (first deck)
must be replaced with the appropriately
addressed loader.

The CMS
nucleus may also be created by using
the two
EXEC procedureson thesystem disk--JPUNNUC
and NUCLEUS3.
Issue thecommand NUCLEUS3EXEC JPUNNUC
userid/OFF.
Eachcomponent text deck of the nucleus
is punched.
If a userid
was specifi~d. thedeck is XFERted to that
USerlQ.
If .OFFwas specified, the physical card deck is punched.

IPL'ABLESYSTEMDISK

To rewrite
the IPLvable
nucleus onto
the CMS
Systemplace
the nucleus
in the card
reader and Dress the
LOl\I'l tru t.t()n.
Und-E-r CP
r~c~cl(lt.h e nuc l eus
de'ck Lrrto "t-t1f2' CPcard reader
with the appropriate ID card, or use "the EXEC
procedure NUCLEUS] and XFE~ the deck into
the card reader,then type the CP command IPL C. The nucleus is loaded intoc o r=
Li nka c e s C::~1.J:1 "(.}--f:ors 2rF~ r'E-~~:;ol\7E~dt anij.·71 J.·f}.i~:c !r);'::~::~:).::-:.
An
I;L~abl~core-image
copyof
the nucleus(_ tjons0-12000) ITa now be ~rittpn onto ~i3k.
diskB

i'

(

After the IPL sequence has completed
the IPLDISK··
routine is given control. It expects the standard console(terminal> address (009)' If it is other than 009, the wa i,tstate is entered, and IPLDISK accepts an ATTENTION interrupt
in order to define the console address.
The following
information is then sought:..

"REWRITE NUCLEUS? (YES,NO)":.YES--a new IPL'able copy of the CMS nucleus is to be
written onto disk
NO -:-_;nowriting takes. place. Control returns to INTI(C~S initialization routine)

#

--~

..

"DEVICE ADDRESS? (OCUU,SYS)":
A core-image copy is written onto device OCUU (ifspecified) or onto SYS, which is the System disk
address specified-in the nucleus device table.
"STARTING CYLINDER? (OXXX,SYS)":
The
core-imagecopy
isplacedOXXX--hexadecimal representation--or
cylinder. The SYS cylinder is
cc
hh
rr
block
53
199

2314:
2311:

04
05

00
00

at
on

cylinder
the
SYS

7980
7980

"VERSION IDENTIFICATICN (15 bytes)":
Fifteen bytes of information" including blanks, areused as the version title and are printed out when
IPL'ing the CMS nucleus.
An IPL'able copy of the CMS nucleus(locations 0-12000) is
written onto the specified disk. A load map showing all decknames and reference points for the nucleus is written to '_..
system printer device. There are four unresolved symbols a~
the end of the load map, as follows:
LOGIN,OFFLINE--maybedisk-resident commands.

eithernucleus

BATCH, SYSC'IL--exter-nal references for
Nucleus.
SAVING CMS UNDER CP,,;:

invoked., Cp a Ll.ows

thepz oqz-arrmerorthe Bi:rtc.~;

the ens nucleus t so that a
the Cll command 'IPL OtS.

user may invokeCM$by issu'ing

on thebare
To Save CMS,IPL the
CMS
System disk
machine(thatis, not under
CPl.
Cause
an ATTENTION
interrupt on the console.

The following

is typed:

Q1:

REDEFINE DEVICE ADDRESSES?
(wYES","NO") ••• (reply NO).
This questionis asked whenrunning CMS on
the baremachine to allow the user
to dynamicallychange thestandard device addresses.

Q2:

WILL
THE
CP-SAVEFUNCTION("YES" ,"NO") ••• (reply YES).

C1:ALL DEVICE ADDRESSESOIGITS: "OCuu".

Q3:

ENTER
THE "REAL"
address of the CMS
SYSTEM DISK ••.
reply "OCUU", where CUU is the real online address of
the CMS systemdisk--as opposed
to virtual
address
190.

, .~

MUST

FOR

CMS

BE ENTEREDBE

EXECUTED?

AS 4 HEXADECIMAL

Q4:

SET THE "ADDRESS COMPl>.RE" SWITCH FOR LaC X' FO '; REPLY"'GO"·After setting the instruction counter switches toreflect
hexadecimal location'FO',and settingthe~address compare" key ·onG, reply "GO".

C2:\~HEN "~'lANUl\L"UTILITY

STATE IS ENTERED, IPL
DECK FROM THE CARD READER

THE CP "SAVESYS'"

When the CPU
stops at location X'FO', place
the CP SAVESYS
utility deck with loader and control card into the real card
reader. reset the load address on the CPU
console, and IPL
the card
reader.
The
message NORlVIJ\LTERMINATION OF
Sl\.VEFUNCTION is typed.

-GEND

is usedto create

proJ.UCl.ng- 36 -

ruodu Le-s

overlayu

Thesestructures-GENu~or the OS

EXEC orocedures\ .

are used only when creati ncrthe overlay moe]xl1e
structure.. Do not try to use them when the text
decks of the processor
components are notpresent.
For
re-genmoding
theinterfacemodules,
use therespective GENDALL
EXEC
segment. No arguments need be passed to -GE!'ID
procedures.

(..

GENDALL

indicates which
modules contain
auxiliary
directories.
When changing the base command
module. or
moving thesecondary processor
modules. the GENDIRT command must be used.
GENDIRT is used to complete auxiliary file·
directories. It i.sto be used by the system
programmer when creating
modules containing
auxiliary directories. GENDALL requires the codename of the specific language processor to bepassed as the only ·pararneter (for example,
ASSEM,,,FORT" PLI).

C[VlSGEND

shows
the
method' ofcreatingall
CMS
disk-resident modules. The name of the disk
module to be created must be passed to CMSGEND(for example, to create the TAPE module, issue
the command CMSGEND TAPE).

.:_ e,NUCLEUS3/JPUNNUC
is used to create a physical CfvlS nucleus
deck by punching each individual TEXT deck.
Issue the command! NUCLEUS3 EXEC JPUNNUC userid,
where userid is the identity of the virtual
machine to which eMS nucleus deck is XFER'ed.

r

-

37 -

MAINTAINING

THE CMS SYSTEM DIS.K

To add or change commands in the nucleus
system disk, proceed as described below •

or on

the

•
CMS MAINTENANCE

PROCEDURES

To' update the Version 3 CMS' systemdescribed below must be applied.

theprocedure

When a PTF is received, the user should apply it to hi~
Version 3 SYSIN deck. The PTF is an update deck identified
as "filenaIl1eAxxxxyCA", where filename is the name of theroutine to which the update is to be applied and AxxxxyCA isthe f z.Le+ype ,xxxx is the f..PARnumber, and y is the AFAR
code that the PTF corrects.
Example:V3 deck
Update
The command to
AxxxxyCA (seqS inc P)·edit sysin''edit AxxxxyCA'
issue

is

UPDATE

EDIT

SYSIN

EDIT

The '''segS''
allows sequencing of up to eight digits.
,The "inc" includes the sequence numberDf the update card
into the new updated sysin file. The", P causes a newly
updated SYSIN file to be created.
The updated file created is,"edit sysin".
Note.
The original
updated copy. '"edit sysin"

isreplaced

with

the

CMSPTF EX.EC :'l'heupdating process described
previously can be
executed with the aid of a C~S EXEC file called CMSPTF EXEC.
This EXEC procedu~e takes the original SOURCE deck and
the PTF deck and creates the new SOt.JRCE de ck , assembles it
producing a TEXT deck, prints an UPDATE LOG of' the updatechanges, and an assembly LISTING onto the offline printer,and offline punches the TEXT deck.
This enables the user to update and get a
new object deck in a one-step procedurew-- 38 -

copy of theCHANGING

DISK-RESIDENTAs above,

obtainCOMMANDS
the object

deck of the new command.

Using thesystem disk
as a P-disk,
text deck of the new cowmand.
Then createby issuing
LOAD
GENMODAll system
If the newfollowing:

All system

name
name

(TYPE CLEAR)(P2)

modulesmust

have a filemodeis atransientcommandERASELOADGENMOD

offlineread thea workable module

name
name
name

modulesof P2.

routine,

issue

the

MODULE(TYPE TRANS)(P2)

must have a filemodeof P2.

The CMSGEND EXEC
procedure may be used to generate any CMS
disk-resident command.
Merely issue. the command"CMSGEt-.'D
name", where "name"is the title of the TEXT
and MODULE ofthe desired routine.

C-DISK

AS A READ-ONLY

EXTENSION

OF S-DISK~In eome installations,
it may be desirable to have an extra
disk as a read-only extension of thestandard s-Disk. This
may prove useful for one of several reasons:1.

If the system customarily has
a large number of users.
it can provide
a more efficient utilizationof system
resources to place some of the system disk prograros
libraries on one disk pack, and otherS on another pack~If some of the programs and/or libraries
currently on
the S-Disk are placed on another disk instea1, this canbe accomplished.

2.

If a s ys t.em disk getsvery full from additionof DCytprograms e it may be advisable t.o put new added prograrrs
on anextra disk insteadof adding morecylinders to+he S-Disk~

3.

:It waybe that certain new or restrict:ed programs areto be ffiadeavailable to a limited number of users.
In
thiscase. suchnroarams could
be Dut
orr thepxtra...~.~:t.

permitted

to use such programs.

t.

CMS now has the capability to provide such an Etxtradisk asa read-only extension of the S-Disk. This extr~ disk is the
C-Disk, and has a default disk-address (in the NUCON table)of 019C. If it is desired to use the C-Disk as·a read-onlyextension of the S-Disk, the following steps must be taken,
and the CMS initializ~tion procedure does the rest:..

1.

compilers and any other prograTIlswhich require the
GENDIRT procedure must be on the s-Disk. IBM-supplied
programs in CMS requiring GENDIRT currently are theAssembler, FORTRAN ..and PLII.

2.

Create the desired modules on the extra disk usinG thesame procedures you would for any read-write disk (forexample, by OFFLINE READ of text decks, Cor"BIN~, TAPE
LOAD, DISK LOAD) but taking care to ensure that themodules or libraries which are to be user-accessible
have a P2 mode (as on the S....
Disk). (See also "Altering
the CMS System Disk"--CMS EXEC Procedures.)3.

Run an update deck called CDrSK UPDATE against the IADTSYSIN deck in the CMS nucleus.. That is, with IAnTSYSIN and CDISKUPDATE
available, execute "UPDATE TADTSYSIN CDISK UPDATE (SEQ8)", assemble the resulting.IADT SYSIN, and then place the .IADT TEXT in the CMS
nucleus using the procedures described above under"Changing Nucleus Resident Commands".

":'

The aforementioned CDTSK UPDATE
deck changes thedescription of the C-:-Diskat ADTC in the IADT Initial
Active Disk table to flag the c~Disk as a read-onlyextension of the S~disk. and should be as follows:// R 20000

C-DISK(READ-ONLY EXTENSION OF S-DISK)// R 239000 2QOOOOlCOS·
DCC-DISK = READ-ONLY EXTENSIO~1OF S-GISK
ALl (ADTFRO)FIRST FLAG-BYTE (READ-ONLY BIT SET)DC
4.

Place the C-Disk as a read-only disk in the virtual
machine descriptor in the CP directory, with virtual
address 19C.,for all users who are to have the C-Diskavailable to them.

If these steps are followed, and the C.....
Disk is attached andready at
CMS Initialization time, whilethe version'
identification message is being typed, CMS automat.icallylogs in the P2 files from the C-Disk, as a read-onlyextension of the s-Disk, in ~ manner similar to the SYSGEN
fUnction for obtaining the SSTAT table from the S-Disk.
The c-Di.sk is then a read-only extension of the S-Disk,transparent to most eMS commands.
STAT C gives the

,
'

\

disk-s t.at.Ls t.Lc s : on the C-Disk (as STl>-'.T
S does the standard
S-Disk) .. and LISTF
filename filetype
C lists the C-Diskfiles just as LISTF filename
filetype S does
the standard
S-Disk files.
(LISTF and STAT
purposely do not
attempt tohandle read-only extensions of disks, to avoid ambiguity.)

CMS CONSIDERATIONS•FORMATTING

THE P-DISK

Once the CMS Systemdisk isrestored andall device
addresses are
assured correct in matching either
the baremachine configuration or the
CP allocation directory, issue
an IPL to the System disk.
Initially, eaChuser must issue
as hisfirst command
FORMAT P ALL. This command formats his p-Disk for CMS usage.
If thedisk
is notformatted,
I/O
errorsoccur
whenaccessing the P-disk.

Note.
All disks that are to be accessed
be formatted in the same manner as above.

Version

3--Version

by users must

2 compatibility

The disk
formats for Version
2 and Version
3compatible:
however,theinternal
core
tablesincompatible between these two versions of CMS.

are
are

Do notuse old commands suchas V2LOor V2L~which
manipulate
files with
Version3(such ,as LOGIN,
LISTF,OFFLINE, ERASE,
TAPE, DISK, FORMAT,
and START) as they do
not work.
If a previous version of eMS
is to be examined, log it
in as a c-disk
so that it will be searched last' and its
routines will not be used in place o~ the system routines.

OBTl>.ININGA NUCLEUS

LOAD I'~AP

A loadmap of the nucleus,
location of each nucleus routinev
IPI..; 190(eMS svstem

disk)

givingthe nameand cere
may be obtained bylciginon any formatted P~disk
MAPPRT B OFF(see other options for thiscommand in cp-67/Cr-1SUser's Guide)~he file CMS-NUC ALPHANUM Pl is created on the P-disk and isalso printed offline.
P-DISK CONSIDERATIONS FOR THE BARE MACHINE
when operating on the bare machine, the P-disk is usedfrom real cylinder o. Therefore, if a user wishes to use
his own fr Les on the bare machine
his files must be
physically located on real ~ylinder o.
#

The user must also be aware of his P-disk size when he·is operating on the bare machine. If more files are createdthan he has disk space, eMS is not aware that the user has·less than 203 cylinders and allows the user to create thefiles over the entire disk pack if the space is heeded.
COMMAND ABBREVIATIONSi

When a eMS command is issued from the terminal or froma routine, several tables are searched for the command name.
If nd command is defined for the name, CMS assumes that acommand abbreviation was used. The nucleus-resident routine
ABBREV is then searched to verify and find the ful1-na~eequivalent of the command.
Command abbreviation is definedas the minimum number of characters necessary to recognize
the full command name.
If standard system abbreviations arein eMS, the ABBREVTEXT deck should be
nucleus deck.

not to be allov;er1
remove? from the

To change, add, or delete an abbreviation, the ABBREV
routine must be reassembled, altering the abbreviation t'
as desired. The table is constructed using the macro ABRV
as f o LLows s
ABRV narner number

where nameis the full nameabbreviation.

of the oommand , andnumber is

>

'rhe

macro
must
be
abbre7iation.
For exawple:
ABRV

OFFLINE"

used

,for

each

desired1signifies thatthe acceptable abbreviation\for
OFFLINE is 0 (also, OF, OFF, OFFL, ••• l.
'
\

ABRV

.ALTER,

the cOlTh"Tland

2states thatthe abbreviation
ALTE, ALTER).

INSTALLATION

commandfor ALTER

is AL(also, ALT,_"

OF THE CMS BATCH MONITOR

From the CMS Systemdisk obtain a copy of the Batch
Monitor Nucleus, BATNUC 3.0, by issuing the command OFFLINEPUNCH BATNUC 3.0.

Set upa disk areathat is used only by the virtual
batch machine.
This diskarea, address
ccu, contains
theIPL'able copyof Batchnucleus ·and need be only two-2314
cylinders, or four-2311
cylinders.
Also, set up a P-disk,
191, for the Batch machine.
Hrite an IPL-able copy of the Batch
nucleus, BArrNUC,
onto
disk ccu
in thesame manneras the CMS nucleus
isreloaded
onto
theSystemdisk.
Twocomments:
1) inreference to Q2 about device
address, reply Ocuu, where cuu
is the disk
address
specificallydefined for
the Batchmachine;2) for Q3, answer ONNN,
where NNN is
an integer·
whose absolute value is greater thanzero but less than the
integer valueof the number of cylinders allottedto thedisk area.
Af t er writing the
Batch nucleus onto CUR,
the message
READY is typed. The Batch Nucleus
disk, CUll, must be IPL'ed
before executing any Batch Job Streams.

To run a eMS Batch job stream, first it is necessary to
IPL cuu.
'Tbe Batch nuc l eus may also be SAVE'd by CP using
tJI12 Lame
Bl\TCH4
If thename
BATCH
is un dea i.r-ab Le,adifferent
namemay be used. by changing the CP
routine
SYST~F" whichcontains thenan-es anddescriptions of all
IPL'able named systems.
Batch nucleus has set a time limit
per job(five minutes)
and an output
limit perjob (5000
pointETlines).
These
limitsmay
be modifiedbyreasspmblina therontine BAT.TCE and placing
the newcopy~nthe BAleR nucl~Gs.
g

-

44 -

\
\

SAMPLE

PROBLEt-1

A sample problem is distributed as File 5 on the tapecontaining the basic program material.
It exists in TAPE
~UMP form.
To load the sample problem onto the P-disk, position
the tape after the fifth tape mark and load it .from tape.
This is done by issuing
TAPE REWINDTAPE SKIP 4
TAPE LOAD
Then the pro'gram is ready to be compiled and executed:
The complete procedure for logging in, IPL'ing 190 for
eMS, FORMATting the P-disk" loading the FORTRAN source deckon the P-disk, and then 90mpiling and executing the sample
problem is shown Ln Figure 2. System responses are printed
inuppercase; user-enteredinformation
is typedinlowercase. Figure 3 contains a listing of the .file SAMPLEFORTRAN.

CC

SAMPLE

1
100

PRINT 100lil

FORr-iAT(.
READ 101~N
FORMAT (12)2IN (N) 2,99,2
PRINT 105

105-~

PROBLEM.

FOR TESTING

PLEASE

TYPE

FORMAT (.
FIRST NUMBER?
READ 103" SUM

CP-67/CMSTYPE

IN THE NUMBER

III DISTRIBUTION

OF VALUES

TO AVERAGE')(FORr.1ATIS F10.4)')

M=N-l
DO 3 I=l"MPRINT 102
102
103

3

104

99
106

FigureFOIW..AT(. NEXT NUMBER?')READ 103" X
FORMAT (F10.4)
SUM = SUM + X

CONTINUE
Y = N
AVG = stwJY
PRINT 104" AVG
FORMAT (15X, 'AVERAGE = ',FI0.4)
GO TO 1PRINT 106
FORMAT (.
*** TEST COMPLETE *** WELCOME
STOP
END
3.

Listingof SAMPLE

TO CP-67/Cr-1S! ')FORTRAN.r-

TNDEX

Abbreviations ••••~ ••43
ACcrON ••••••• 15.17
i\C"N"TOFF••••••• 15.17
Allocation ••••••• l0,11,42
Auxiliary directories •••••••• 37~tch
monitor •••••••• 44
BUZZARD utility ••••••• 8.18
Changing disk resident commands (CMS) ••40 ..
41
CMS source disk ••,••••• 33.34,38.45
CMS system disk ••••• 2,33.34.38,39,44.45
CMSPrF ••••••• 38.39
Command abbreviations
43
Configuration ••••••••• l.2-4.5,8,9.10 ..
12
14,15,19,20.23r24,42
CP load deck ••••••••• 7,8,10,11,14,15,17
CP residence volurne••••••• l,10,11.12,20
CPASr.1GEN••••••• 15
CPGEN ••••••• 8,9.12-15
CPLIST
15
CP~ACADD ••••••• 5 ..
13
CPMACGEN
13.14
CPt-1ACREP••••••• 5 ..
13
CPPTF ••••••• 27,28
CPPUNCH~ •••••• 13.15
CpSyS •••• ~••13-15,23
CPUPASM ••••••• 5~7.13.28
CPUP~1AC••••••• 13 .. 14
Device addressees), CMS ••••••• 2,3
DIRECT utility ••••••• a,18
Directory •••••••• 1,6,7,9,10,11,32,40-42
Directory creation ••••••• 6,9-11
Di~patching ••••••• 28.DMPRST •••••••30.31
DMXDV ••••••• 22
DRCH ••••••• 21
DRCU ••••~ •• 21DRDEV •••••••
22
Druros•.••••• 1,10
DUMP ••••••• 2,30.31 ..
33,45
DUMP/RES'.rORE •••••••
2,30,.31
Duplex ••••••• 4,20,23.24
Exec procedures, CMS ••••••
1, 32- 34 r 36- 41
Exec procedures, tp-67 •••••• 1,3,6,13.27n)R1(P..T ut.i, Li, ty •••••••

Formatting
Formatting

8 18
f

P-disk ••••••• 9,42
volurnes•••.
9,lO
FORTRAN•••••••
28 ..
41,45- t,q
FUNCTi\B •••••••
39o

GENDALL ......~.37
GENDIRT ..••.•. 37,41
lAUT' •••••••-

48 -..

Q 1.

••

IPL •••••••• 2.10.11,18,25,29r30i32,34~36
42,44~46
ISAM ••••••• 5,6,7
JPUNNUC".5 ••• o34,37
Label ••••••• l0,11,19-22,25,26.32
Language processor(s) ••••••• 36,37
Libraries •••• ~••40.~1
Loader •••• 3,8,9,11,,14,15.17 ..
18,32,34,36
LOGIN ••••••• 3,20,35,42,43,46
Machine configuration,
definition ••••••
1,19
Machine configuration.
distributed •••••
19,24
MACLIB ••••••• 3,5,13,14
MACUP •••• ~ ••5,14
Maintenance procedures, CMS •••••••••• 38~aintenance procedures, CP-67 •••••••• 27
Message ••••••• 3.11,12,15,27," 28,30,31,33
36,41,44.
Named.systemCs) ••••••• 11,25-27.44
Nucleus •••••••• 1,6,10,11,14.20,32,34-39
41-44
NUCLEUS3 ••••••• 34,37
NUCON ••••••• 32,41
Offline ••.••••••••• 5,8,9,11,27,32,34,35
38-44
Online ••••••• 30,36
Operator's console ••••••• 20,33
Options, CMS ••••••• 1,39,43
Options, CP-67 ••••••• 5-7,12
OS ••••••• 7,36
Pages.~ ••••• 19,25-27
Paging ••••••• 9.10,11,25,26,28
Password ••••••• 46
Printer ••••••• 2,3,8,9,11,14,15.20,32,35
38.39
Punch ••••••• 1t2-4,7-9~14,20,34,39,44
Queue1 ••••••• 28
Queue2 ••••••• 28
Reader ••••••• 2,4,9,11,16.27,34,36
REALIO ••••••• 1,15',19,23
Redefining device address{es) •••••••• 33
RELDRxxx ••••••• 8,17
Restoring ••••••• 31,33,34
RPRT ••••••• 9
RTIMR
6,7
SAVECP ••.•••• 11,18
Saved system ••••••• 25-28,44
SAVESYS •••••• ~8,18,25-27,36
Sa vi ng ,Cf.'IS •••27 , 35
Serialization ••••••• l1,17,19
Setup ••••••• 3.4,12,19
Shared,page(s) ••••••• 25-27
SIMPLEX,macro •. ~." ••••• 20,4,19,20,23,,24GO

SL1' •• .:,""•••••

18

SpoolingGGo •••• 1D~11,20

GH20-0857 -0,

SSTAT ••••••• 41
Startup •••• ~••20
SYSCNSL ••••••• 20.23
SYSCORE ••••••• 20,23
SYSCI'L••••••• 35
SYSDNC •••• U •• 10.20.23
SYSDUMP ••••••• 9.20.23
SYSEMRG ••••••• 20.23
SYSERR ..••••• I0,20.23
Sysgen, CftlS•••••••
2,3,30,41
Sysgen, CP-67 ••••••• 2,3,9,19,20
SYSGEN rnacro••••••• 20
SYSMASK ••••••• 25
SYSOPER •••••• ~20.23
SYSPRT ••••••• 20,23
SYSPUN ••••••• 20,23
SYSRES .•.•• ~.1..10,11,19,20 ..
23
SYSTAB ••••••• 25
SYSTEM,module •••• _••25
SYSTYPE ••••••• 20,23
SY~VOL ••••••• 20,23
SYSvillM,_•••••• 10,20.23
Tape~ •••••••• 1.2,3,12f15.16,27.30,31,33
37,41,1,12,45,46
TDSK ••••••• 11~
Terminal ••••••• 4,8.12,22,27,28,33,35,39
43,46
Timer ••••••• 5.6
TMPSPACE ••••••• 18
Tuning .•••••• 28
Userid ••.•••• 12,20,34,37
Utilities, CMS .••••••• 1,9
Utilities, CP-67 •••• 1,3,7-9,12,14,17,18
VDUMP ••••.•• 8,9.18
Virtual,I/O
2,3
Virtual 67 <V67) ••.•••••5,6
Virtual machine •••••• ~1,16,9.26,28,30,37
41,44
Volume label ••••• _••••••. l0.11,20~25,26

~-

~---

r

;

.....

_

1:';0) fv;-?
t_-:t_SL\,il_j':.

11.2 East POS! Road, Nhite Plains, New York 10601(USA c.n!;)
IBM Wodd Trade Corporation<'"w