1 1
-
To: Programming Staff Oct 3, 1977
From: DWB
Re: Change Forms, Distribution 4.01, etc.
- Change Forms
+ ______ _____
0 The change forms procedure has now been automated for post-
D4 changes. The file MTS:CHANGEFORMS contains commands to cause
change forms to be placed in the file -FORMS. This uses the
program in MTS:CHGFORMPGM and the data in MTS:CHGFORMDATA.
0 This data file has been permitted read and write-append to
the staff. If you have a change to distribute, construct one in
a temporary file using the first unused change form number (they
start at 4001, for D4 base). Then add it to the file. Every
Monday I will look at the file, and send out copies of anything
accumulated during the past week. After each mailing I will add
a marker line in the file (begins with "*") thus indicating the
extent of the mailing.
0 Instructions for the form of the data in the file are
attached; you can also look at the existing data in the file to
see what is required.
0 Changes are to be expressed either in terms of the old
update program (*UPDATE), or -- preferably -- in terms of the
new update program (MTS:UBCUPDATE). If you don't have a writeup
on the new update program (and if you want one), there are some
copies in my mailbox. It is also in MTS:UBCUPDATE.W as TN
printer output (11 pages).
0 Each change "form" should be for one specific bug or
enhancement (i.e., if you fix four problems in one module then
there should be four change forms), and the name specified on
the /BEGIN block header to the new update program should consist
of the letter "C" followed by the change number. See the
examples already in the file.
-
Distribution 4.01
+ ____________ ____
0 In honour of those who are now wading through the thousands
of components of Distribution 4 that we just sent out, we are
planning to produce Distribution 4.01 along about Halloween, Guy
Fawkes Day, Armistice Day, or Turkey Day, depending on slippage.
This interim distribution is planned to include MTS updates
which are mostly to install the new GSFS, a repaired VAMREC, IG,
CLOSE enhancements. Let me know what else you want sent out.
1 2
-
Form of entries to go in MTS:CHGFORMDATA
0 A. Each line must start with specified phrase in col 1.
B. Phrase must be in upper-case
C. Phrase must be immediately followed by data.
D. Order of items must be as below:
- phrase data example
+ ______ ____ _______
0 1. Change number # nnnn #4093
2. Date issued DATE= mmm dd, yyyy DATE=Sep 20, 1977
3. Person issuing PERSON= name PERSON=Engle
4. Component name NAME= name NAME=TIME
or name(subname)
5. Component number NBR= nbr/subnbr NBR=360/1
6. (optional) base BASE= distr nbr BASE=D4.01
(default base is Distribution 4)
0 For the following, each line should be no longer than about 60
characters. As many lines, each with the phrase, may be used as
required.
0 7. Description of DESCR= description
bug fixed
8. Change expressed in OLDUPDATE= update input
*UPDATE form (optional)
9. Change expressed in NEWUPDATE= update input
UBCUPDATE form (optional)
10. Change expressed in EDIT= edit input
EDIT commands (optional)
11. Comments (optional) COMMENTS= comment
-
Following is a complete example, and the next page is the output it
generates.
0 #4003
DATE=Sept 22, 1977
PERSON=Helffrich
NAME=TABLES(DECKGEN)
NBR=004/5
DESCR=Corrects bug in generation of the CHANNELS table for selector
DESCR=sub-channels.
NEWUPDATE=/BEGIN C4003
NEWUPDATE=/COPY "TABSEL"
NEWUPDATE=/COPY COUNT=3
NEWUPDATE=TABSE5 DS 0H
NEWUPDATE=/COPY "TABSE4"
NEWUPDATE=/EDIT "TABSE1" = "TABSE5"
NEWUPDATE=/END
COMMENTS=This correction is in the restore-tape pack files
COMMENTS=MTS:DCKPCHR.S and MTS:DCKPCHR.O, and the ipl files *IPL...