Digital PDFs

XX-F0D3A-00

August 1978

29 pages

Original

1.4MB

Document:	RSX-11M Project Plan
Order Number:	XX-F0D3A-00
Revision:	0
Pages:	29
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsx11m_s/RSX11M_V3.2_Jun79/RSX11_3.2_projPlan_197808.pdf

OCR Text

CAD-78-001-00-U

Doc:
D~.e:

~S-August•78

RSX•11~ Software Development
C~arge ~umbersl P2~~0q701/09731

~~
'J',/')12~-

Pro)ecti

Product.IDs:

~qp~~

QJ628 1 QJ62q,QJ636,QJ637,GJ728,QJ737

PROJECT PLAN FOR
RSX•11M VERSION 3.2

Submitted By:

C1ark D-Eiie, Project Leader/Suoervisor
Fra~k

Hassett, Software

Engineer{~g

Manager

Ri11 Heffner, RT/C Grouo Manager
Kurt Fr~edr~ch, Software Product Manager
3rad G1ass, So1tware Gua1itv Manager

Don van Vo1kenburg, Software Documentat{on Suoervisor

T~e

informat~o~ ~n this document is sublect to change
without
notice
and s~ou1d not be eo~strued as a co~~itment bv Digital Eouioment
CorPoration, Digitai EouiPment Corooration assumes ~o respor.Sib;litY
~o~ any errors that ~ay appear in th~s manual.

The so~tware deser~bed in th~s document ~s fur~ished to the purchaser
under a l~cense tor us~ on a single comouter svstem and can be copied
(with inelus~o~ of DIGITAL's copyright not1ee) only io~ use in such
svste~~ exceot as may otherwise be provided in ~riti~q by DIGITAL.
-

Digita1 Eou;P~eMt Coroo~atio~ assumes no resoonsibilitv 1or the use er
re11ab~i~ty
o~
its software on eouipment that is not suool~ed by

DIGITAL,
CoPvrigMt CC) 1978, by Digita1 Ecu\pment Corporation

PAGE 2

1,~

EXECUTIVE SUMMARY

1,1

ProJeet Abstract

RSX•11M Ve~sio~ J,2 is en updated re1ease of tne disk-based RSX•11M
operating sY~tem~ The main purpose of the proJect is to provide, in a
timely man"~r, increased dev~ce support to e~tend our r~a1time ~reduct
o f f e r 1·rr g ,
to
c on t i rt u e
s u Pp o r t
f o r t tr. e 1 ow• end R S X• 11 tA u s e r , and t o
provide easier SYSGEN, auto oaten kits and other ease•of•use features.

The deve1ooment o~ RSX·11M V3,2 wi11 have a schedule which is
approximate1v 14 months from start to finish, This update to RSX•11M
V3,1 will be developed to suoport new devices and to 1~ve up to our
maintenance o1an eommitt~ent to shio uodates at a~oro~imatelv on~ year
interva1s, lt wil1 contain fixes to all know~ bugs end will snip in
Aori 1 197q.

1,2

SummarY

Goa1s

The goai of RSX•31M v3.2 is to provide oua~ity so1twar~ w;tk ease of
use end suppert features and new device support for t~e sma11 to
middle-sized ~DP-11 system.

1.3

Su~mary

Costs and Work Plan

1.a

Sum~ary

sc~edule

and Mi1estones

develop~ent
of
RSX•l1~
eomp1etio~
of eac~ stage will

V3.2 w~11
be done in stapes,
The
be marked by tne combinatio~ of a1l new
software into a Base 1eve1 uoon which t~e ~ext staQe of development
will be done, ease levels will be spaced at app~oximately 2·3 mont~
i rite r v a 1s.

The

suggested sc~edule for RSX•11M V3.2 is for first customer
to begi~ April, 1q7q,
I~ t~is time frame the io11ewi~g is
se"'edu1ed:

The

sl-\'ipments

Base 1eve1

Base 1eve1 2l.l
Base

levei

Field test

1S•Seo•78

PAGE 3

15•Feb .. 79

B(-e 1eve1 26
S~bm~ssion

to SOC

First Customer Skipments
In add~tion, RSX~11M V3;1 Auto-Patch k~ts wi11 be subm~tted to the SOC
in the fo11owing months·~cquarter1y sta~ting wit~ Q4 FY78):
May•78

Nov•7B

2.0

DESCRIPTION OF PRODUCT

2.1

Prob1em Statement

T('

rr.air\ ;:;ur;:ieses of RSX•11M

New

dev~ee

V3~2 is to provide the fo11owiMo:

support

3. scs-11 operating system kerne1
Fixing of a11 k~own bugs

and tne distr;but;on of.
confidence and e~hanee
uodate services,
It
snou1d also heip to create
customer image as to the oua1itv Ca~d our ded4eat~o~
of t~e RS~·11M p~oduet.

shou1d

mai~tain

eusto~er

auto-patch kfts
tMe viab;1ity of
an eve~ better
to that aua1itv)

Addf tio~~l Per•Phera1 device suooort broadens the market
i~
w~ich
RSX•11M V3.2 ea~ be so1d and provides the eapabi1ity to c~fer a 1arger
s~eetrum of competitive eonfigu~ations,
The addition o~ new exeeut~ve and MCR featur~s ste~s f~om reouests
made by t~e SCS•11 deveiopment 9rouo, RSX•11M V3.2 wi11 be used as
the OPerati~Q system kerne1 for that svstem,

PAGE LI

2.2

Product Definition

2.2.1

New Features

Proposed enhenceme~ts are listed be1ow. Note that items marked w;th
an asterisk(•) are reQuested by tne SCS·11 project. They will not be
done ff manpower ;s not orovided by CSSG.

Prov~de an oot~ona1 (new RSX•11M
supoort the fo11o~ing features:

PLUS)

termina1

•

1imited type ahead

•
•
•
•

ful i dup1e>e operation
VT100 suoport {ANSI escape sequences)
DH11 OMA cutout exo1oitation
fui 1·V bufter-ed IlO internai to the dr"'iver

Su~oort

~ard~are

of the fo1lowing new

d~vices

d~iver

wi11 be added based

uoon

avei1~bilitY a~d com~1et~on Of device dr~vers by the

PT/C !/0 Subsystems

G~ouo,

Rxe2 • .s MB dis~ette
RX03 • 1 MB dis~et~e .
TSeu - ~s iPs taPe drive
TU77 • TU45 repiaeeme~t (reouires no softwa~e
RP~7

•
TU78 •
RLe2 TUSB •
o

new nigh•seeed
fo11owin~ goa1s1

Provide!

•
•
•

backup/restore

uti1itv

wit~

•
•

-•

*Exit-~ith-status
~Subset of the RSX•11~+ pare~t~6ffsoring
di~eetives
.
_
Tes~ STO~·bit syMchronizatio~ directives

Support ~or the
Add su~port ~or
C1ean•UP oi QIO
o1 user written

exeeutive

PDP·11/23 and 11/UU orecessors
2/U ~1le w~~dows
proeessi~g to ease integration
ACPs,

File Svstem Imorovements
•

t~e

total vo1ume or i~crementa1 ooeratio~s
back uo a~ RP07 to TU78 in aoo~o~i~ately 3~ ~inutes
replacement of DSC for middle• to 1arge•s;zed svste~s

Add n~w Executive features as ~o11ows~

•

m.odifieat~o~s)

300MB t;~e~ media disk
12S ios Ce2S0 boi) t~pe system
10 MB dis~
,25 MB block•structured cartridge taoe

Use of 2/4 fi1e wi~dows

PAGE 5

MCR

f mcrovements
•

•

-.
-•

Provide exoanded HELF fi1e
*A conso1e device driver to control printing o~
console messages and logging of them to a consoie 1o9
1;1e,
.
*A special INSTALL for s~mi-transparent mu1ti-user
taslc supoort
Generie device a11ocat~on
New commands (STOP, UNSTOP, SSM)
LOA/UNL improvements
Others TBS

SYSGEN improvementsJ improve numaM
or mo~e of tne fo11owing:
•
•
-

en9in~ering

doing

one

Provi~e

system packages
Suoport 1or e standa~d FCSRES for system ut11ities
?rovide a RSTS/TRAX•stvle program to dYnamicellY
detect o~1ine device eonfigu~ation1
or e~hance
tne
existing
procedures
performing
the
interactive
~ortions of SYSGEN to use validation, auto-answer, and
ot~er techni~ues •

Re~acka;e

RSX•11S to a11ow for generation and kost support

RSX•11M PLUS

a~d

IAS as we1l as RSX•11M V3.2.

FLXI
•

/•RW to inhibit magtepe rewindi~g

•

1b00 BPI support
RXA2/RX03, RK0b/RK07, TUSB, a~o RL01/RLe2 SUOPort in.
RT•11 format.
(Note that RT-11 · autoreatie bed block
rep1ecement can not be supported.)

•

SLP:
•
•

Cnecksum suocort
Support 132 bvte

•

•Prov~de

iMOUt

1ines

LBRI
the

•
•

BAD:

/R~

support for a general librarv ~egardless of
of tne modu1es Ctext, tasks, data, ete.)

eonte~ts

switch to a11ow user contro1 of taoe hanolinQ
An option to produce a detai1eo, lab~led dum~ of
Fil es•11 CODS•1) fi 1 e neaders.

P~GE

Prov;de t~e abi1ity to add bad block data ~anually to
the 1ast track without wr;ting on t~e entire disk.

•

Volume Utilitiesi
INI supoort for the RX02/03, RP~7, aMd TU58
MOU/DMD modifications to store voiu~e labels for error
1ogging, end a11ow muit;pie mounts

•
•
o

Develop a new print spoo1er having the foiiowing capabilities:
•
•
•

Support mu1tip1e line printers
Store Pri~t ~ueue on disk
A11ow user access to the print queue

Error Loqgi~g

•
•

A11ow ooerator i~out to be stored in the error 1og
Diso1ay tne voi~me name on error reoorts (for ~ounted

•

Su~port

vo1umes)
t~e RX02/~3,TS~4,TU77,TU78,TUS8,P?07,

Performa~ee ana1ysis •• t~is wi11 be done bv
a Joint
betw~en deve1ooers and Software Qua1itY E~gineers.

Mu1t~~1e

end RL02
effort

command 1ine i~terpreter support
g1obai eve~t f jegs CEFNs) usi~g
as a bas~s.
(Note this must eiso be
RSX•11M+ to be ;nc1uded i~ RSX•11M.)

Increase number of svstem
VAX/V~S
do~e i~

imo1ementat~on

DCLS support as a SYSGEN option,

K~C·11

LPA•11 suppart for 22•bit mode oPeration

File Svstem

LiMe

~rinter

Contro11er driver

!m~roveme~ts

•

Maoping file wi~dows iM the ACP's address spaee,
removing the~ from the executive pool.

•

Create a 12K F11ACP to
soaee for FCBs, windows,

acouire
buffe~s,

-- rCS biq buf feri~g suooort.

additio~a1

ete,

add~ess

PAGE 7

~.c(
...

Supplied Software• RSX•11M

rhe RSX-11~
V3,2 System in addition
;ervices, and I/O Drivers is
:omPone,-,tsr

Executive

Services,

MCR

A F~ies•11, ODS·I Compatib1e File System CF11ACP)
in three
packa9es of 2K, 2.SK, and SK refieeting functionalitv, size,
and soeed options.
t

A subset MACR0w11 assemb1er- (MAC•8K)

A fu11 MACR0•11 assemble~ e~ntaining e11 features including
floating ~oint and Cross,Re~erenee suPport CBIGMAC • 1~K)

Task Builder with Global Cross Reference suoport CTKB) in
t~ree
eackages of SK, 1~K and 22K ~efleeting functio~al;tv,
s~ze, and speed options.

I~teraetive

Source Language Input Program CSLP)

0~1

Exeeut~ve

Edito~

CED!)

;,.,e Debugging Too1 COOT)
Oebuogin~

Too1 CXDT)

10. Svstem Generatio~ Procedures (Command files)
11, Bad Block Locator Program CBAD) cepabie o~

12. Disk Structure Ver;fieation Prog~am (VFY)
13. Fi1e Exchange Uti11tY (FLXl
1 IJ. Peripl-lere1 Intei-change Program (PIP)

15. Librer~an Ut11ity CLBR)
10. Fi 1e Du mo Uti1itv (DHP)
17, Task Image Pate !"I

udiitv CZAP)

18. Test Routiries/SamP1e Procedure
19. Disk Save

a~d

Compress utiiitv CDSC)

20, Cross Referenee Program (CRF)
21, ANSI Magtaoe Suooort (MTAACP)

22, LOGIN/LOGOUT suoport CACNT, HEL, BYE)

run~i~q

bot~

PAGE 8

23, Hulti~user suooort utilities CSHUTUP,BROAD)
2~.

Object Module Paten Program (PAT)

25, PRESRV • Volume Prese~vat~on Program • (for

distribution

only)

26, RMS•11 macro and subroutine libraries and utilities
27, F~1~ Compare Ut~l~ty CC~P)
28, L~ne ~rfnte~ desPoo1er CPRT) and
packege

optio~a1

eMha~eed

spooler

29, Ind~rect command ~i1e processor C.,.AT,)
30.

Cras~

Dump Analvzer Program CCDA)

31. DEC standard ed~tor CEDTl

32, New ~i;~·speed BACKUP/RESTORE Utility

~.3

Produet Audience

~SX•11M

V3.2 ~s targeted to the cur~ent users o~ RSX•11M CRea1time,
eon~rc1 and Communieations/Networks) as well as soohisticated
ise~s w~e wis~ te operete a multi•user svstem for Program deve1opment
!~d ru~~in~ o~ applications,

'reeess

~.4

Com~~rison

:o~pet4tive

~.s

With The Comoetition

data ;s

~vai1ab1e

from ?reduct

Ma~ege~e~t.

Product Eve1uation Strategy

iee Sect~o" 11 (the QA P1an) that
~a"agement.

provideo

Software

Quality

PAGE q

PROJECT GOALS

3,1

Functiona1 Goa1s

•
;

Prov4de bug fi~es and re1iabi1ity enhancements •
Prov~de new device support

in ti~e

e~o1oit

"ew

ha~dwa~e

peripher"a1s,

•
'

SYSGEN

a~d

ease of use enhancements,

Provide an ooerating system kerne1 for SCS•11,

It 1s a reoufr~ment of RSX•11M V3,2 that a11 non-Privileged orograms
wr•tten to ru~ o~ ~SX·~1M ?LUS V1,0 1 RSX·i1M V3,i, or RSX•iiS V2.1
wf11 ru~ wit~eut modifieatio~i Tasks written for these versions of
RSX• 11 M or RSX .·11 S wi 1 1 !" u /*l on RSX· 11 D V6. 2 or I AS Ver s i on 2 by
rebuildi~g tne tasks orovided they do Mot use
tke Me~ory Management
CPLAS) directives~

It is plan~ed thet RSX•11M V3 9 2 tasks wii1 run unchanged with
~< ib1e ~e1i~k under VAX•VMS A~E.

onlv

No new functio~aiity is o1enned that wou1d compromise the svstem's
real
time
resoonse
or
reliabiiity.
furt~ermo~e,
fu~etio~al
enkaneements not direct1y re1ating to the above can on1y be considered
if fundi~g a~d/Or person~el eom~itme~ts aceomoeny the reouests,

3,3

Performance Goais

The per~ormance o~ RSX•11M V3,2 wi11 eoua1 that o~ RSX·11M V3.1,
The
perf~rma"ee
of RSX·11M eaua1s or surpasses that o~ RSX·11D V6.2 and
!AS in most eateqories o~ eomp~reb1e eonfiguratio~s,

3( ,1

Minimum Hardware Corifigurations

All minimum ~ardware co~f1gurations currentlv 1isted i~ the V3.1 SPD
wi11
be
supported,
IM
add~t1oM,
the
foiiowi~g
~ew
minimum
eo~f~guretioMs w~11 be $UPPorted:

P~GE

RP07 system device
2UK

memo~v

a~d

RH11/RH70 controller and

o~e

RP07 drive

and
T~11

controller and one TE/TU10 drive or,

RH/iM02/G3 eontrolier and one TE/TU16 or TU45

or TU77

drive,

or
RH/T~78

TS11
2,

controller and one TU78

eont~o11er

d~ive

or,

and o~e TS04 drive.

RL02 system device
2~K o~

RL11

memorv

eont~o11er

and

RL02 drives,

t~e

RL11 ee~t~o11er and o~e RL02 dr~ve
er.d
eo~tro1ler

e~d

TEITU10 drive

o~e

O '~.
r

RH/TH02/03 contro11er and one TE/TU16 or TU45 or

TU7i

drive

or,
RH/T~7B

contro11er

e~d

one TU78 drive or,

TS11 cont~o11er and one TS~~ drive.

3.~.2

Supported Hardware Options

RSX•11M V3.2 w~ll ~rov~de support for the processor ootions, real ti~e
eioe~s,
and oeriP~era1 devices currently 1isted ;n the V3.1 $PD, In
addition, the ~o11owing ~ard~are oPtions ~~11 a1so be supported,
RL11•RL02

ca~tridge

disk CF11es•1l Structure• System Dev1ee)

RH11/RH7~·RP07 F~xed Med~a D~sk
R~211•RX02/RX03

CF~les•11

Structure• Svstem Dev~ce)

Ftopoy Disk (Fi1es•11 structure
or RT11 format su~Ported via FLX)

PAGE 11

T( 3 TaPe Cartridge CFi1eS•11 st~ucture or RT11 for~at
"' FLXl
Ha~tape

TS11 • TS0U

suPPorted

via

(ANSI ri1e Structured or DOS format

Supported via fLX)
TM~3-TU7i

St~uctured

Magtape (ANSI File

or DOS format Supported

vf a FLXl

TM78•TU78 ~agtape (ANSI fi1e struetu~ed or DOS Format SUPPorted
via F'LX}.

Note
-

DL11•E modem support for termiMS1s will
be
avai1ab1e o~1v w;t~ the optional ~ew
terminai driver,

3tS

Support Cest Goals

I( Is our ~oa1 to ~educe support costs below the
V!i1 (see seet~on 7.0).

3,6

levels

~or

RSX•11M

ReHabiHty Goals

O~V-44M
l"\.,,, . . . - " - ' 1 '

H't

YJtl;.

ul,'I
~I! I

~,,...,,...,..
-w
..................
-\,

-r•,..,. ,,..,...,..;_.,. n1>

f'VC

l\J't'1'!:111!~

rl
. ~'v'',t"'I!!
---

3a
1 .•1 ~·,.~
~
-

1:i'

f~f"'
-

A1,1,

rJl,$1.,.
.... ""
-

;;;,

wel1
as loggi~g of CPU parity errors on th~
PDP•11/~~/60/70/74 processors.
These features snould im~rove the.
reliabiiitv of t~e tote1 svstem by catching devices as t~ey begin to
fai11
tota1 system uptime shou1d tnus be inc~eased._
The software
system goe1
is to be at least as re1iab1e as previous versions of
RSX•11M,

and

taoes

3,7

T~ade o~~ o~

Priorities

The key goa1 of RSX·11M V3 1 2 is to provioe a
~e1ease
i~
a timely ma~ner,
Key items
~

re1iab1e

;moortarice are tne 1o1 lowing:

Reiiabilitv of Software•• Re1eesed on schedul~.

Device Support

SVSGEN

New

a~d

other ease-of-use enhancements

hig~·speed disk

backup/restore

order

system uod~te
of decreasif"lg

PAGE 12

Ne~

termina1 driver

New Print spooler
RSX•11S su6port for IAS
Time wi11 be traded off for tne inclusion of the above featu~es,
however the system wi11 not be released until we are satisfied wit~
its reiiab~litv,

~.0

RELATIONSHIP TO OiHER PRODUCTS

4,1

Relatio~sh1P

A.1.1

RSX•11M V3,2

Ot~e~

w~t~

System Projects

RSX•11M PLUS V1

~SX•11M ?LUS was based en RSX•11M V3

but has undergone sign;ficant
internal
redesign and enhancement e~~ecia11y to make the system more
attractive i~ t~e nio~-avei1abilfty and commercial environments.
It
w~l1
be ~arketed for t~e very hi9h•end PDP•11 svstems. Tn~~efore,
RSX•11M re~~'~s the major ~u1t1•taskinQ,
real
ti~e
system for the
corPor~tie~.

A signif•cant amount of funetionei
overiap (about 80X) will ex;st
V3.2 end RSX·11D Vb.2. RSX·11M reouires sig~;f;ca~tly
1ess memory C!o~roximate1v one ~alf) and, wit~ t~e except1o~ of tne
CD11 card reader, suoports more perionera1 devices.

betwee~ RSX·11M

RSX•11M wi11 compete best in situations where:
1.

T~e lowest ~rice

Rea1tim.e resPonse

RMS ~ec~1~ties, 8ASIC+2, or COBOL V3

f s important,

soecif;c 1aborato~v Job 1s reou4red
a~d/or

~etwork

t~roughPut

are

esse~tial,

reouired.

PAGE 13

U(\,3

RSX-!IM V3,2 with RT!!•F/B

Rtil•F/B is targeted toward sing,e Cone•at•a•tfme) task operatfo~ with
parallel program development i~ the backgrou~d. As suen, an over1ao
..
,..,~v
,,7
"') e
-. •.
l-•&.. ....
:., . . l _ l _ ... ,
-.-..i
•• ~11
;11','·v-w
w ,1 't... r. r;
v,.. ••u
l l
y
Ill: l
u IW \, ..\.. i..l,.. -··--•-v '! t:: r
f.i
1
!¥
our
eusto~ers to make trade•offs Csingie user vs,
multi•program~i"g'
smaller executive size vs. RSX•11 comoatibi1ity, ete.) wfth~~ a range
o; DEC oroduets rather thaM buy from our co~pet;tors.
1..

~·t

.;J •

'!;; :; ,

I' l

I 0

l:)

,,.

l I' l

'!I Cl

f I \.,I

~·

As compared with RSX•11D V6,2 there w;ii be a 1esser amou~t of overlap
;n fu~etionaiitv between RSX•11M V3,2 a~d IAS. RSX•11~ w;11 requi~e
sig~~fieant1v 1ess memorv,
How~ver, I~S
~s
targeted to the la~ge

multi-functio~ o~e~ sho~ enviro~ment,

a subset of RSX·11M V3.2 and will be directly
In edditio~, RSX-115 v2.2 will be
ge"efatab1e ~~om the 1atte~:
packaged sue~ that RSX-11M ?LUS~ IAS and RSX-110 V6.2 may aiso serve
host svstenis,

RSX•11S v2.2 is

lie

RSX•11M V3 9 2 is depende~t upo~ the RT/C I/O Subsystems Group for
~~iting
drivers for the TUS8, TU78f RX02/RX03, RC07 and jS04 as we11
as fer maintenance a~d enhance~eMt of a11 disk and taoe drivers.
Mai~te~e~ce e~d en~enceme~t
of the 1;ie syste~ softwa~e CF11ACP,
MTAACP, MOU, DMO, UFO, INI, BAD, FCS, DSC, PRESRV, PIP, DMP and VFY)
~ests with tne RSX files Group,

Support.of RMS~11 as wei1 as the RMS utiiities ~esides with the
Com~ercia1
Software Svstems Group. Because the basic RHS~11 software
iS bund1ed ~it~ RSX•11~,
an up•to•date,
re1easab1e RHS-11 oackage
shou1d
be
avai1ab1e by the Fie1d Test base levei.
(Current
indicatio~s are thet this shou1d be RMS-11 v1.e.)
The co~mereia1 Software Systems Grouo is responsible for o~ovidinq an
updated version of EDT,
t~e
DEC standard ed\tor, fo~ release with
RSX•11M V3 .• 2.

Support of user mode diagnostics wi11
be done
by
Oiag~ostic
~1 .... ineerinQ.
Additiorie1
di.agnos~ics
fol" ne\-: devfees CRL~2, RM03,
1\_ 1J, R K~ 7, etc. ) w i. 1 1 a 1 so be the i r res o of"! s i b < 1 i t y.

PAGE 14

We are heav;iv deoendent o~
products to run on our system
they operate properly and can
our users.
Because these
invo1veme~t
to be limited
production of base 1eve1s for

out.side grouos that provide layered
Ceomoi1ers, DE~NET, ete,) to e~sure that
be integrated into t~e system easily by
products are so numerous, we expect our
meinJy to tecknica1 co~su1tat;on and
test in~.

See the RSX•11M V3.2 Svstem Plan for a detailed list .of dependenc;es.

q,3

Depe~dence

OtMe~

Projects on This Project

SCS•11 (Small Co1T1mercial Svstem) will be usirig
operat4n~

RSX•11M

V3,2

the

system kernel,

App1icat~ons software consis~~~g of
nonprivi1eged tasks w~ic~ were
deve1ooed for RSX·11M V3,1 ~i11 continue to operate u~der RSX-11~
V3,2, Priv1ieged tasks whic~ nterface to svste~ data structures wi11
reQuire 1itt1~ or MO ~odifiea~ ~Ms,

S.0

A?PLlCABLE STANDARDS

5,1

Extant Standards

The following aoproved standards are suPoorted:
DEC 125 Cassette Format
DEC 051 Coded Character Sets
DEC 112 Data Format +or Output
DEC 1~q Drive Seleetion
DEC 11~ Eseaoe sequences .
DEC 111 Te~minal Synck~onization

s.2

PendiM9

Sta~dards

If the new comma~d 1anguage i~te~faee ;s to be
Section
2,2,2),
the Digita1 Command LaM9uage
~mpleme"ted o~ RSX•11M PLUS wi11 be used.

•mc1e~ented

soecification

(se~

PAGE 15

Sta~dards.Needed or

A good Mac~o-11
avai1ab1e.

S.4

Assemb1v

Suggested
Language

should

Corri~atibility

ComPat~b~l~ty with RSX•11M V3,1,
RSX•11M PLUS
VAX•VMS AHE wi11 not be d~sturbed,

6,0

Standard

P~ogramming

DEVELOP~ENT

and

the

ex~sting

REVIEW BOARD

Tne developm~At ~eview board wi11 be responsible for reviewing a11
fu~ctiona1
seeeif~cations re1ating to RSX•11M V3,2.
It wi11 be their
respons~bt1~ty to consider compatibility items and
support of their
products bv RSX•11M V3,2.

Kurt Friedrie~ • Product Manager
Brad Glass• Software Quaiitv Manager
FraMk Hass~tt , Soft~are Deveiopment Manager
Clark D'Ei1a •Software Development Supervisor
F;t Sa~e 7 0l'er.~t4ons Group Software Services
~ e ~ut1er • vAX-VMS Development
Rav Moaee~ ~ DECnet Project Leader
Howerd Lev ~ Software Develoom.ent Manager
Eric Fo1ieek ~Software Deveiopment Sueervisor
Erie Baatz • Sc~tware Develop~ent Supervisor
B\11 M~~so~. Software Oevelop~ent Mane~er
C~ariie Sa~tos •Software Qua1\ty Management
Bi1i Page. Software Development Superv;so~
Jo~n Morqa~ • CSSG Deve1ooment Manager
John Holz - !PG So~tware AoPlication Manager

7,0

PLAN TO REDUCE SUPPORT COSTS

We a~e actively workfng wit~ Software QualitY Manage~ent, Softwa~e
Services, a~d Edue~tio~ai ~Services to imorove the svstem generation
process. The 9oa1 of this effort will be easv RSX·11M i~sta11ation.
In
addition,
develoQ~e~t
perso~ne1
are committed to orovide
coMsultation a~d doeu~entation review services to aid
i~
the
production of the RSXw11M So~tware Su~port Ma~ua1,

As Part o1 tkis development project, mac~ine ~eadable auto•patch kits
~or
RSX•11M V3,1 w•11 be oroduced OM a cuarterly bas~s starting with

t. 1978.
8,0

COMPONENT PLANS

PAGE lb

Being a mature eroduet, RSX•11M
modifying the ex~stinQ software,

work

q,0

DEVELOPMENT STAFFING AND WORK PLAN

q,1

StaffinQ P1Bn

wi1l

~ostiy

involved

Modifications to the Executive, MCR, file syste~ and the Utilities
w111
be
performed
by
members of the RSX Deve1opmeMt GrouP,
Modifications to the device drivers wi11 be prov4ded by tne RT/C I/0
S~bsvstems
Group,
In addition, one programmer from. the SCS-11 grou~
wi11 be 1oeated ~"Tewksbury to contribute to the RSX•11~ deve1ooment
effort ~hile ~t the same time gain exte"sive sYste~ exoosure,

Management and Design

Programming and Design

Programmil"lg and Design
Charles Spitz

P rog ramm i !"\Q and DesiQn

Pav1

Programming and Desig~

Kober"

Mike Harvev

Programrn; nQ and Design (LPA11 .. K)

Debbie Girdler

Pro.gramfl'i l"'lQ and Des;g,., (Fast Baek: up)

Dale Donei"dM

Program~4ng

Walter.DunaJ

"Performance Eva1uat~on CSGMl

Mi ke Harri so,.,

Svstem packages and SYSGEN ease•oi•use tSQM)

On Loan

Prog~~mming

9,1.2

~reject

C1ark D"E1ia

Leader

and Desig,., (Fast 8aekuP)

and Design (fro~ SCS•11)

PAGE 17

Staffi~g

9,1.3

By Quarter

s<..; Sys tern P1 an,

See System Plan,

q,2

Software Develo~ment Strategy

A base 1eve1 deveioomeMt cvc1e w\11 be emp1oved periodicaiiv merging
new functionai;tv into the previous base ievei, Each Base level will
be designed so t~at erit;ea1 Sortware eomoon~nts are availabie at the
oro~er time ~o~ work to oroeede on the new features,

Mandatory Tasks
.

•

Provide

maintena~ce

e~isting

syste~

code

Produce ouarter1y au~o Patch kits for RSX•11M V3,1

•

Provide SYSGEN ease-:4~use improvements

•

Prev<oe new mass
Provide RSX•11S

9,2.2

sto~ege

su~port

device suoport

for !AS

w~ite a high-speed disk backup/restore utility

•

Provide new termina1 drivers for optional use

•

Provide en~eneed Print spooler

b~t~ona1

functio~e1ity

Addit~ona1 Tasks

See section 2,2.2.

q,3

'("' , 1

Code Reviews

Code Rev i e w P 1 a n

Spot el-ieeks on the ouaHtY wil1 be made by C1a,..k D'Elia,
Eric
and Eric Po11aek to ensure t~at a ~igh oua1ity level is upheld.

Baatz
Newer

PAGE 18

members of tne group wi11 be subject to more
code reviews.

q.3.2

i~tensive

suoervision

a~d

Code Reviews

Code wi11 be ~eviewed by the senior me~bers of the deve1o~ment team.
These rev4ews wi1' be entirely internal to the RSX-11M group and will
be conducted on an as needed basis,

q.a

Hardwa~e

Reouirements

This deve1opme~t sckedu1e is deoe~dent u~on the availabilitv of
adeQuate hardwa~e resources, Insufficient resources at suitable ECO
1eve1 w11l adverse1y affeet t~e sehedu1e and cause a slippage,
Starting 4n Nev•78, we must ~ave access to orototvpes for t~e 11/23
a~d
111ua p~ceessors. The e~g4neer1ng confi9urat1ons must be usab1e
to an ooerati~g svstem develooer in t~at they include at least 32K of
memory i~itia,1y a~d that t~ev heve a minimum of two RL01 (or RK05)
disk d~ives or one disk dr4ve ~~d a magnetic tape unit (800 boi,
q•tr&ekl.
(Note t~at syste~~ conf~gured with only f1oppy disks as a
system device are uM~cceotabie,) To test fu11y the extended addressing
of t~e 11/4a, tkat processor ~uat ~eve a minimum of 128K of memory by
1•Jan•7Q. we W411 re~uire uo ~o 10 hours a week aeeess startfn9
1~oec•78;

as possib1e wi11 be do"e o~ SYSTEM #1P3S~, whieh
aii the master source disks and wiii run the most recent base
1eve1 of RSX-11M~ This mac~ine will be used for edit;n.g source
~odu1es 1
asse~b1ing
and lin~ing a~d testing of aii nonorivileged
tasks. It w•ii also be used 1or bu;1ding base 1eve1s of the software,
As much

contai~s

deve1op~ent

System #1A350 wi11 b~ transfer~ed to a~other cost ce"ter in
1q1B1 svstem #1~625 w411 become its ~eplacement.

September

I~ additio~, it is recognized t~at a standalone configu~atio~ must
available fo~ at least ~ hours a day. T~is s~ould be system #372,

q,4,2

Debuggi~g

Conf iguratio~s

var;ous other configurations avai1abie i~ the Tewksbury eo~outer roo~
~f 11
be reouired averaging a total of 2 hrs per dav u~ti1 SDC
subm~ssfon,
Thi~ ·ti~e reouirement w~11 usua11Y
occur i~ bu~sts of
longer time ~eauireme~ts but should average 2 hrs oer dav,

PAGE 1 q

q,a.3

Wnere located

A{. machines must be located in the Software oeveloome~t
Tewksburv.

System #10350 (or replacement) must be
during the entire developme~t cycle.

avai1abie

~aci1fty

hours

pe~

day

Otner macriine utilization wi11 average 8PProxi~ate1y 2 hours a day of
prime time, For the two weeks p~eeeding f~eld test and sub~ission to
SDC Cdur~ng the checkout o~ the peckag~ng) we wi11 reouire up to 12
hours a day of prime t1me on various con~igurat4ons.

Speeia1 ~a~dw8~e reauirements exist on1y_with respect to new device
suoporte
Co~:erned
hardware engineering groups shou1d consult witn
tke suoervisor of tne RT/C I/O Subsvstems GrouP for eoord;~ation.
In
gen~ra1 1
fui1y _operational orototvoe ~ard~are mu~t be avai1able at
least 1 month ~r~or to the Base Leve1 listed in section 10.2 below for
~( us~o" of t~e device dr~ver into that Base 1eve1,
To

ensw~e

erop~~

~nd

11/4Uj;

tfian

1•oec•78,

i~tegration
s~ou1d have

and support for t~e new erocessors (11/23
access to the prototype hardware ~o later

10.0

IMPLEMENTATION PLAN

10,1

Major Activities and Get1nQ Factors

Suecess~ul

proJeet

progra~~in~

staff is viewed as a major

eQmpletion

d~Pends

upon.

~eeting

mac~ine

conTigu~ation/time
reQuirements set forth and timelv de1iverv of
re 1 ate d software c ~ mpo n'e n ts 1
In add 1t i o ri, the t i me 1 y
f u 1 f i l 1 men t · of

- 10.2

~aJor

depende~ey.

M11estones

The major milestones for RSX•11M V3.2 wi1l be the completio~ of the
b a ~·e
l eve i s o !"I
t i me.
The
ma 1or
co rite n t of ea eh Base 1 eve l ; s as

1(_ :ows:

Base Leve 1 23

PAGE 20

Prep~~at;on

of +u~ctio~a1 soecif;cations complete
Staff4ng como1ete
New Terminal driver running
Base Level 24

Device drivers 8Vei1ab1e for RL02,RPe7,TSC4,TU77, and RX02/03
STOP•BIT direct~ves
Base Leve1 25
Device d~iver available for TU58
New P~int Spooier
New Backu~/Restore Uti1ity
Sysgen I~o~ovements
Field Test
s~~e

Leve1

Deviee o~~ver available 1or TU78
Suoport. fer 11/23 end
Sysge~

1114~

i~orovements

processors

Risks and Conti"gency Plans

10.3

Fu1fi11ment o~ staff•ng in a time1y manner ;s viewed es a major risk.
Failure to obtain criticai team members by June, 1q7s, wi11 cause t~e
de1aY of the Product or the droPP~ng of portio~s thereof.
In
part~cular, th~ ~o11owing potentta1 ~~pact fs foreseen~
•

Fai1ure to obtain SCS•11 orogrammer wi11
result in the
e1imination of new executive features and new MCR features as
•ndicated in sectio~ 2,2.1.

s1ippage of ~ardware e~gi~eeriMg eroJects ~as oiaeed i~ Jeopardy total
supportliMte~ration
•~to
t~e
system for the following dev;ees:
RP07,rs0a,ru1a. Our deve1op~ent efforts for these dev•ces must be
ae~omplished,
tota11y using prototype ~ardware.
Announee~ent
of
offieia1 deV~ce support for these Cand a11 ot~er new hardware) will
n~t
be made by the oroduet manager unt41 the so~tware is sueeessfu11v
tested o~ production ~a~d~are,

P.6GE 21

P~ototypes

~ew

10.4

the ~ew processors C11/23 and 11/U~) should be
t e s t i n g s of t wa re b Y 1•Dec• 7 8 ,
F a i 1 u re t o g a i r'I ad e Qua t e
hardware w~11 resu1t in 14mited or no support fof the

for

a(·' q ab 1 e
a~ess to

the

processors in RSX•11M V3.2,

PERT

a~d

Milestone Teehn;0.ues

PERT wi11 not be used, Detailed monthly reports wi11 be orepared
listing milestones met and missed, work in progress, work como1eted,
and work ~1anned for succeeding month=

11.0

DOCUMENTATION STAFFING AND WORK PLAN

11. 1

The RSX•S1M group and the Tee~~;eai Writing Grouo C~eaded by Do~ Van
Vo1kenbu~g) wi11 be resoonsibie for ai1 RSX-11M V3.2 documentation.

1{ ~

Docume"tet~o~ Strategy

See

Doeume~t~~~e~

11,3

Docume-nts

11.4

Documentatio~

Plan~

Reviews

Manual review is a serious UMdertaking, We will provide t~o weeks for
review ·and construe 1ack o~ written comment as agree~ent that the
~ua1 ity of the manua1 i·s, from t"'e revie~er•s Poi,,t o.f
v4ew, up to
DEC's ~igh standa~ds,
Two reviews wi11 be eonducted w~t~ t~e first considered the ~ost
c~itieai.
T~is
review wi1l oecur at the comoietioM of the initiai
- draft a~d has a wider distr;butio~, The second review Mas li~ited
distribution end 4ncorporates ~eviewer com~ents aMd wi11 be tne
s1gnoff eooy.

I("- t i a 1 r e v i e ws wi 1 1 be e o ~ du c t e d b y i
1.

RSX•11M/M•PLUS Team

me~be~s

PAGE 22

A Software Supoort representative

A Training representative

A Software writing repr@sentative

A Software Quality Engineering representative

A Marketing representative

A Pr~duet Management representative

A Software Development Management representative

q•

An RSX•11D/IAS

10, A DECNET

11.S

re~resentative

recresentat~ve

Documentation Reviewers

A11 RSX•11M deve1opers p1us:

(Software Services)

Ed Sapp

(Software Services)

F'raneios NeuvioM

(Tf"airdnc;;)

Don Van voikenburg

{Tee~

Seritos

writing)

(Software Que1itY

Carl Ra1stori

CLOP Marketir"\g)

Berriie LaCroute

CVAX Product Manager)

Pete Kilbourn

(OEM Marketing)

Red Flakes

CIPG Tee~n~e~i Services)

Kurt F'r~edrien
Frank Hassett

(Software Deve1oPment

Manage~ent)

CI AS)

Mae~tne time r~outrements
for writers w~1l b~ dete~mined
Ooeumentatior. group and dese~ibed iM t~eir detailed plans,

the

PAGE 23

12.0

(

QUALITY ASSURANCE PLAN

The purpose of this sect~on ts to describe the p1ans for assu~ing the
Quality of RSX•11M V3,2 befoFe ~ts release to soc. A sign~ficant part
of quality assu~anee is the test process itself, the stages of and
plans for whien ere desc~ibed below.
However, tnis test process is made muc~ simpier, and the resu1tant
oua11ty cf the product higher, ~f the ent~re design and develooment
~~oeess ~s geared toward planning for testing
and "bui1dfng ouai;tv
in" rather than "adding ~t on" or waiti"g unt~l the end .of the
deve1opmeMt evc1e to see 4~ ~t's there. To that end, ~t is 4ncumbe"t
on everv deve;oper and documenter to o1a~ for oualitv ;n ter~s of both
design a"d deve~opm~Mt. Ind~vidua1 w6rk p1ans should re~lect this, es
tne system ~ust be sueeessfu11y subjected to the testing described;~
the ~ollow~ng ~ect~ons before development ~s cons~dered eomp1ete.

12e2

U~it

a~d

Svstem Testing

U~~t

a~d Svste~ Testing are
the responsibility of the develoo~ent
J~,
Eae~ RSX•11M p~og:ammer end~documenter fs r~spons~b1e for t~e
cualitY of his work, both in terms of its, design integr;tv and as
uitimatelv eereeivab1e by the user whe~ it becomes part of the total
system. E~haustive u"1t test•ng o~ the programmer's own desig~ must
be eomp1eted for each component before it cen be integrated with the
system cwnich in this ease is RSX·11M V3.2),

(

I"tegrat~on t~st~ng will be eondueted us~na the trad~t~ona1
"bu~lding
b1oek" a~oroaeh.
As iMd~vtdua1 compo"e~ts suceess~ul1y complete the
u~~t test phase described above, they
wil1 be integrated with the
existing base svstem to form a new base 1eve1.
Base 1eve1 contents
and dates are desc~ibed elsewhere in this document. The e~ite~ia for
satisfyi~g
tke reouirements of each base ievel are defined in tne
RSX·11M V3.2 Svstem P1an, and wi11 be used bY SQM to monitor and
measure. deve1opment
~roQress,
The
svstem Plan a1so defines
respons~bilit~es o~
other
groups that must be synchro~~zed with
efforts described in this o1an in order to produce a complete system,
wi11
be t~at test ~hase conducted on the last
base level:
that is, a11 Coding, unft testing and
integration testing is do~e (t~e complete system exists). Aqai~,
see
the Svstem Pla~ for specification of Svste~ Test e~try criteria.
SY!tem Testin~ wi)1 be eondueted by th~ development grouo on tke
development ~aeh~~e, by all users of that mac~;Me, bv Software
~,-~vices and by ~a~ufacturi~g
as described below.
Specifie
tests
~ .eioced
by SQM and the deve1opers must be ru~ to addr~ss svste~
~~~etional~tv, res~onse, oerforme~c~ and doeumentatio~.

System

testing

Hdeveioo~ent"

PAGE

Soeeial emphasis wi11 be
prospeet4ve OT how it
Successfui completion o~
a neeessarv eondf tion
described below,

12,3

Placed on ~ew functiona1fty,
but
from t~e
re1ates to the ooeret;on of t~e total svstem,
System Test as defined ;n tke System Plan ;s
for progression to the F1e1d Test Phase

User E"v~ronment Testi~g

As eac~ defined base 1eve1 becomes avai1eb1e, it wili be subject to
heavy use fn the Manu~actur1ng sites via exercise o~ the P.SX·11M User
Enviro~~~nt Test Package CUETP) developed by
SQ~,
UETP develooment
plens wi11 be constructed to a11ow t~;s to be possib1e. SQM and
En9ineer4ng w111 a1so use tnis ~ackage to address svstem funet,onalitv
for eae~ bas~ levei.
This test is incremental to other tests
described here;~._ As sueh it is a necessary, but ~ot a suff;cie~t
base level
requirement.
SQM wi11 assess system "goodness" based on
UETP exeeutio~ ~esu1ts at a11 locations, ~anufacturing is expected to
eo~tinue
heavy use of the fie1d test base 1eve1 a~d the UETP in
Para11e1 wit~ the Fieid Test Phase described be1o~.

12~4

Fieid iesting

T~e PU~~ose o• Fie1d Test

is to help est~blish t~e level of confidence
svstem before it is released to customers on en
u~11m<ted bas'!•
Tnis is possible because the system is exercised in
e~stomer
env\ronments ehosen because o~ their abi1itv to address
system tunetiona1itv in wavs thet we cen~ot duP1ieate or do not nave
adeQuete resources to make it feasib1e,
that

~ave

F~e1d Test

~s inc~ementa1

to svstem test. It is not a subst~tute for
it, and as such must·be de~ined as a distinct ~art of the development
~roeess,
It is furt~er constrained bY the fact t~at it is a se~;a1
effort, , Fie1d Test cannot begin unt;l design, code, unit test,
integration test and svstem test are a11 complete as defi~ed in the
system pl~~. We shou1d se~d a svste~ to the f;eld test w~th the ~dea
tnat ~ problem is en e~eeption rather than a ru1e. The o1a~ned Field
Test period for RSX•11M V3,2 is two and one Ma1~ months long, A
detailed Fie1d Test Plan will be a part of the RSX•11M V3.2 System
P1a~,
and wi1l be eut~o~ed by SQM i~ eonJunetio~ with Product and
Deve1op~e~t

~anaQeme~t

12.5

De~onstrAt~o~

a~d Softwe~e Serv~c~s.

Tests

PAGE 25

12.6

Ooeumentat;on Assurance

~easured

o(e of the primary ways that the ouality of the system Is
by
the user is via the documentation. A new user ~eeds it to start hf s
~ork1
a" ex~erienced user needs it in o~der to take advantages of new
feetures end to u~derstand changes to tne svste~s. Doeumentation
shou1d undePQO a11 the phases of test that the so~tware undergoes.
1ne respons1bi1itY for eonducting these tests is a Joint ef+ort among
documentetio~ deve1opment and SQM grouos.
Tne doeumentat;on must be
field tested aiong witn the software. It must th~refore be eo~p1ete
at the start of Field Test (See the System P1a~).

12.7

Human Factors Eva1uation

Human en9ineering concerns re1at;ng to t~e use of the svste~ software,
tne use~ doeumentatio~, a~d the svstem generation process wil1 be
addressed by SQM ~n their test4~g effort~. ~dditione11y, one of t~e
elements of feedback from customers during fie1d test w411 tnc1ude an
;mp11cit eva'u~tion of huma~ fsctors considerations for botn software
and doeumentatio~,

1'~8

Work P1an

~st DeveloPment wl11 be conciv~ted bY development (un;t,

integration,
system tests), SQ~ (UET?) a~d Software Services (misce11aneous),

Schedu1es eMd m11estones for t~e QA process are included in the System
Plan, as they re1ete to the e~ti~e svstem.

12.9

Re1ease

Criteria

sin~,emost importa~t criterion for t~e re1ease o~ RSX•11~ V3,2
's
Qua1itv.
At no t4me and fo~ no reason wiii oua1itv be co~P~omised,
The cr~ter~on of "Qua1itv".is ~mP1emented by wey o~ soeeif~c cr4ter~a
for e•eh phase of testing described above, Agai~, these criteria,
T~e

with a sehedu1e ~or th~ir eomp1et~on are contained i~ the svstem.P1a~.
SQM wil1 be re!ponsib1e fo~ determiMi~g whether or not these criter;a
are met, a~d wi11 orovide ~n1ormatio~ to the Product Manager, who has
the u1ti~ate reiease decision ~esoonsibi1~tY.

PAGE 26

13.0

DISTRIBUTION PLAN

13.1

Release Packages

Each RSX·11M V3,2 distributio~ kit contains a bootstrappab1e system
eapab1e of ru~ning on tne minimum co~f;guratio~ for which it is
intended. All svstem co~oonents reou;~eo to run and generate eusto~
tailored RSX•11M V3.2 systems are also included in tke kit,

The softw~~e ~4t provided with eacn RSX•11M V3,2 sYstem contains both
source and binary modules Csouree is erov~ded to enab1e the reauisite
conditfonai asse~b1ies w~ieh minimize the size of tne executive). The
software k4t inelud~sl
Source Modu1es
E~ecutive

Executive Cine1udes

I/0 OP";vers

File system CF11ACP)

MCR routines CMCR)

Debugging Too1)

s;nary Modules
19

MACR0~11

Tas~

Interactive Editor (EDI)

Sou~ce

Per~ohera1

F~le Exehenge Utility CFLX)

Assemb1er

(~~o;et

and fu11)

Builder CTKB)

La~gua~e

Input

Pro~ram

CSLP)

Interchange Progra~ CPIP)

7, -Disk St~ucture Veri~tcat~on Progre~ CVfV)

F~le

q•

Onl~~e

Dumo· COMP)
DebuggiMg

Tee~niaue

CODT)

10. ObJeet Module Pateh Program (PAT)

11,

Libra~ian

CLBR)

1 2 , Te s t R o u t i ri e s I S a mp 1e P 1"-0 e e d u r e

13, Post

Mo~te~

and Snap Shot Dumo Program (PMD)

PAGE 27

1Ue Bad Bloc~ Locator

Pro~ram

(BAO)

15, Task Ime9e Patch Utility CZA.?)

17, Giobai Cross Reference

18. ANSI

magta~e

Progra~

(CRf)

system CMTAACP)

1q, Mu1ti•user Protectfon Programs CACNT, SHUTUP, BROAD)

21. RMS•11

~aero

and subroutine 1ibraries and utilities

22. File Compare Ut~1itv CCMP)
23. Crash Dump Ana1yzer

Prog~am

(COA)

2a, DEC standard editor CEDT)
25. New hi;n•speed BACKUP/RESTORE uti1ity
;~( :ontent of the documentation kit is soeelfied In the Documentat~on

13,2

Fo~ecast

Per Quarter by Type of

Dist~ibution

Mediu~

See Business Plan.

13e3

Pre•Release Po1iey

Due to the ava~1ab~1ity of s~te~ for f~e1d test,· the~e wi11 be "o
o~ this product,
After RSX·11M V3.2 is submjtted to the
soc, software pre-releases may be made by tne· Product Lines or by
Software services.
Al.1 ~eouests m~st b~ approved by the Product
Ma~ager.
P~epa~atio~
of the distr~bution
media,
documentation
avai1abi1itv, and suopo~t become the so1e resoons{bility of the
requesti~g partv.
prepre1eas~s

PAGE 28

13.4

Subseouent Release And Po1;c4es

To be suoplied es oart of business pian.

13,S

Soitware Support D~str~but~on Packages

Software supoort's automatic distribution. svste~ will be
distributing software kfts to specia1ists.

14,0

utii;zed

TRAINING PLAN

Minimal Software Support train~ng shou1d be required for RSX•11H V3,2
beyond that a1ready orovided for RSX•11H V3.1, A one or two dav
seminar eoveri~; PSX·11M V3,2 e~nance~ents and new faeil;ties snouid
be suffieie~t.
Key develop~e~t Personne1 wi11 be available for
consultation a~d i~itiai p~ese~tations.

T~e

e~ist1~g

m;n1mu~

15,0

P.5Xei1~

course wii1 be adaotabie

RSX•11M

V3,2

wit~

effort,

SOFTWARE SUPPORT PLAN

TBS.

1b,0

MAINTENANCE PLAN

16~1

SPR

P1a~

V3,1 wi11 be supoo~ted for 6 moMt~s after the reiease
SDC. A~ter that ti~e, 9nlv V3,2 wi11 be supoorted,
Furthe~more, no intermediate base leveJs wi11 be suoported beyond
the
geMeration of the next' t~erefore, it is a reoui~e~e~t that layered
software Products be based o~ the finai V3.2 relea5ed svste~.

SPRs for
of V3.2

RSX•11~

~rom t~e

16; 2
1

Maintenar"\ce Release P1an

NS speci~ic
ma~ntenance release 4s sc~eduied.
w111 be ereeted ouarter1y
RSX•llM V3.1.
kits

t-4owever,

auto

pat eh

for

17.0

POSi RELEASE PLAN

17.1

Post Partum Review

Post Pa~tum Review for this ~roJeet
Qua Ht y

Mar'la~e

wi11

[E~d

of Project P1anJ

keld

t~e

Software