On Friday 22 August DOSV3A was replaced with DOSV3B using the DEC-supplied update kit. There were no major changes to the system and all existing software should perform correctly without change.
For the most part, DOSV3B seems aimed at curing obscure bugs in the device handlers and adding new handlers. The patches for the RSX III version of the system have not as yet been made. With the DEC-tapes comprising the update came a set of programming manual updates and a description of new DOSV3B facilities. For the time being these are being kept in a binder in the PDP15 bookcase. Later it may become necessary to issue updates to those holding manuals.
Included below is a description of some of the more interesting changes in DOSV3B. The-new overlay system FASTEX was not installed because of conflict with the existing ACL fast overlay loader EXECUT. Please note that LOGOUT no longer turns VTOFF. The default DAT slot assignments have been changed slightly as well as the system password. Users should see LOF if they require access to <SYS>.
2.3.1 Overview
The V3B0000 version of the editors (EDIT, EDITVP, EDITVT) incorporates the following new commands and features:
1. LIST command to output to .DAT -12
2. The GET command to include named files.
3. A PARITY ON/OFF enable/disable parity checking on paper tapes
4. The extension of maximum text line size to 135 (decimal) characters.
2.3.2 Implementation Details
The PRINT command was modified to optionally route output to .DAT -12. GET was modified to allow directoried input, the PARITY command manipulates a switch which controls the parity checks, and the data buffers were expanded to handle the longer line sizes.
2.3.3 Source File
The source file used to create all versions of the editor is EDIT15 030.
2.3.4 Operation
The LIST command, which cannot be abbreviated, outputs the specified number of lines to the listing device assigned to .DAT -12. The form of the command is:
LIST n where n is a decimal number
This command is like the PRINT command, except that the output goes to .DAT -12, usually assigned to a lineprinter rather than a teletypewriter.
The GET command will now permit input from either a directoried or non-directoried device. If .DAT -10 is assigned to a non-directoried device, the command works as before. If, however, a directoried device is assigned to .DAT -10, the GET command will insert the contents of the file named in the command into the output file.
Example:
GET NEWFIL SRC
will put the contents of NEWFIL SRC into the output file.
The new PARITY ON/OFF command enables user control over parity checking on paper tapes. When the Editor is initially loaded and restarted, PARITY is ON, meaning that all input paper tapes will have their parity checked. However, PARITY OFF will disable parity checking, allowing input of tapes without parity. In this case, the user must take special care to insure that the data input is correct.
The editors now allow text lines of 135 (decimal) characters. This feature was included to enable editing of listing files.
2.3.5 Error Messages
2.3.5.1 .DAT -12 IS FILE ORIENTED
a. Error - The device assigned to .DAT -12 is not a listing device.
b. Corrective Action - The LIST command has been aborted. The user can elect to PRINT the lines, CLOSE the file, return to the monitor, assign the correct device to .DAT -12, call the Editor, reopen the file and try again.
2.3.5.2 "filnam ext" NOT FOUND
a. Error - The file name given in the GET command does not exist on the device assigned to .DAT -10.
b. Corrective Action - Retype the command giving the correct file name.
2.3.5.3 NO FILE NAME GIVEN
a. Error - On a GET command, .DAT -10 is assigned to a directoried device and no file name was given.
b. Corrective Action - Retype the command giving the file name, or, if input was meant to come from the paper tape reader, close the file and return to the monitor to reassign .DAT -10.
2.3.5.4 Error message deleted
Note that the error message:
.DAT -10 IS FILE ORIENTED
DO YOU WISH TO CONTINUE?
no longer exists.
2.4.1 overview
The V3B000 version of MTDUMP incorporates the new command COMPARE. COMPARE allows the user to compare two magtapes for equality.
2.4.2 Implementation Details
The tapes are manipulated in a non-directoried fashion. Free core is used as general buffer space.
2.4.3 Source File
The source file for MTDUMP V3B000 is MTDUMP 014.
2.4.4 Operation
The new feature COMPARE is explained and used as follows. The COMPARE command allows the user to perform a block-for-block comparison for all or any part of two tapes. The user types:
COMPARE u1,u2,u3
where: "u1" is the drive upon which the old master tape is mounted
"u2" is the drive upon which the new master tape is mounted
"u3" is the termination condition (number of blocks, "EOF" or "EOT").
Standard parity and density (odd parity, 8 bpi) prevail unless they have been changed by a FORMAT command.
To copy and compare a tape mounted on units 1 and 2, use the following example:
REWIND 1
REWIND 2
COPY 1,2,EOT
REWIND 1
REWIND 2
COMPARE 1,2,EOT
If the·tapes compare, the message:
TAPES ARE IDENTICAL
appears on the teleprinter and (if open) in the Dump file. Note that comparison of only part of the tapes as in COMPARE 1,2,1, if successful, will produce this same message.
2.4.5 Error Messages
2.4.5.1· BLOCK #n LENGTHS NOT EQUAL
a. Error - The block number n (where n is controlled by the current radix and is the number of blocks to skip from the beginning of the COMPARE operation) on the old and new master did not have the same number of words. The shortest block length is used for the comparison and comparison proceeds.
b. Corrective Action - None
2.4.5.2 BLOCK #n WORD #m O.M. WORD -XXXXXX N.M. WORD - YYYYYY
a. Error - The word m in the block n is not the same on old and new master. The block and word numbers are displayed in the current radix (the word number, m, corresponds to the word number seen in DUM output). The differing words are displayed in octal format, independent of the MODE switch. The comparison process continues.
b. Corrective Action - None
2.4.5.3 ERRORS DETECTED DURING COMPARISON
a. Error - Comparison is over and the portions of the tape compared are not the same.
b. corrective Action - None
2.4.5.4 EXPECTED END OF FILE NOT ENCOUNTERED ON NEW MASTER
EXPECTED END OF TAPE NOT ENCOUNTERED ON NEW MASTER.
a. Error - An EOF or physical EOT was encountered on the old master with no corresponding EOF/EOT on the new master. The comparison terminates.
b. Corrective Action - None
2.4.5.5 NOT ENOUGH CORE FOR COMPARISON
a. Error - Both blocks from o PRINT the lines, CLOSE the file, return to the monitor, assign the correct device to .DAT -12, call the Editor, reopen the file and try again.
2.3.5.2 "filnam ext" NOT FOUND
a. Error - The file name given in the GET command does not exist on the device assigned to .DAT -10.
b. Corrective Action - Retype the command giving the correct file name.
2.3.5.3 NO FILE NAME GIVEN
a. Error - On a GET command, .DAT -10 is assigned to a directoried device and no file name was given.
b. Corrective Action - Retype the command giving the file name, or, if input was meant to come from the paper tape reader, close the file and return to the monitor to reassign .DAT -10.
2.3.5.4 Error message deleted
Note that the error message:
.DAT -10 IS FILE ORIENTED
DO YOU WISH TO CONTINUE?
no longer exists.
2.4.1 overview
The V3B000 version of MTDUMP incorporates the new command COMPARE. COMPARE allows the user to compare two magtapes for equality.
2.4.2 Implementation Details
The tapes are manipulated in a non-directoried fashion. Free core is used as general buffer space.
2.4.3 Source File
The source file for MTDUMP V3B000 is MTDUMP 014.
2.4.4 Operation
The new feature COMPARE is explained and used as follows. The COMPARE command allows the user to perform a block-for-block comparison for all or any part of two tapes. The user types:
COMPARE u1,u2,u3
where: "u1" is the drive upon which the old master tape is mounted
"u2" is the drive upon which the new master tape is mounted
"u3" is the termination condition (number of blocks, "EOF" or "EOT").
Standard parity and density (odd parity, 8 bpi) prevail unless they have been changed by a FORMAT command.
To copy and compare a tape mounted on units 1 and 2, use the following example:
REWIND 1
REWIND 2
COPY 1,2,EOT
REWIND 1
REWIND 2
COMPARE 1,2,EOT
If the·tapes compare, the message:
TAPES ARE IDENTICAL
appears on the teleprinter and (if open) in the Dump file. Note that comparison of only part of the tapes as in COMPARE 1,2,1, if successful, will produce this same message.
2.4.5 Error Messages
2.4.5.1· BLOCK #n LENGTHS NOT EQUAL
a. Error - The block number n (where n is controlled by the current radix and is the number of blocks to skip from the beginning of the COMPARE operation) on the old and new master did not have the same number of words. The shortest block length is used for the comparison and comparison proceeds.
b. Corrective Action - None
2.4.5.2 BLOCK #n WORD #m O.M. WORD -XXXXXX N.M. WORD - YYYYYY
a. Error - The word m in the block n is not the same on old and new master. The block and word numbers are displayed in the current radix (the word number, m, corresponds to the word number seen in DUM output). The differing words are displayed in octal format, independent of the MODE switch. The comparison process continues.
b. Corrective Action - None
2.4.5.3 ERRORS DETECTED DURING COMPARISON
a. Error - Comparison is over and the portions of the tape compared are not the same.
b. corrective Action - None
2.4.5.4 EXPECTED END OF FILE NOT ENCOUNTERED ON NEW MASTER
EXPECTED END OF TAPE NOT ENCOUNTERED ON NEW MASTER.
a. Error - An EOF or physical EOT was encountered on the old master with no corresponding EOF/EOT on the new master. The comparison terminates.
b. Corrective Action - None
2.4.5.5 NOT ENOUGH CORE FOR COMPARISON
a. Error - Both blocks from old and new masters could not fit in core. The comparison terminates and the old and new masters are positioned after the records which would not fit in core.
b. Corrective Action - None
2.4.5.6 UNEXPECTED END OF FILE ENCOUNTERED ON NEW MASTER
UNEXPECTED END OF TAPE ENCOUNTERED ON NEW MASTER
a. Error - An EOF or physical EDT was detected on the new master with no corresponding EOF/EOT on the old master. The comparison terminates.
b. Corrective Action - None
5.1.1 Disk Handlers
1. The-disk handlers no longer allow a truncated file to be renamed.
2. Concurrent use of disk and paper tape punch caused loss of punched columns (PI system only). This problem has been corrected by a modification to the DOSRFA disk handler.
3. Modification to the DOSRFA disk handler enables correct error handling for the RP2 disk pack. The B status register is now read before interrupts are allowed. The disk timing error is now sent to parity retry logic (can cause disk corruption unless retried) instead of typing an IOPS20 message. A disk error without any identifying error bit is now called IOPS20 instead of IOPS21.
4. Modification of the DOSRFA disk handler corrects a timing problem occurring with the simultaneous use of two different disk types under API or the use of one disk type and use of the API level 4 software interrupt facility.
WARNING
The correction to this problem uses the API disable breaks and enable breaks instructions. These instructions were generated by ECOs BB-15#12 and KP-15 #50, February, 1971. Machines manufactured at a later date should already have these ECOs. Also, note that it is not necessary to install these ECOs into older machines unless API is being used. It is also not necessary unless either two disks are being used, or one disk and the API level 4 software interrupt is being used.
5.1.2 DOSSAV
DOSSAV no longer prints a DECtape error message when, in fact, the error occurred on the disk pack.
5.1.3 DTA.
DTA. now reports errors ·(putting DECtape status register B in the AC) after a .WAIT following a .TRAN.
5.1.4 EDITOR
The EDITOR no longer has an incorrect interaction between OUTPUT OFF and TOP.
5-1 DOS-15 V3BJ Update Document5.1.5 LINKING LOADER
The Linking Loader outputs the error message NAME ERROR and then restarts if it cannot find the named file on the input device. Further, null file names are ignored if the input device is directoried. This allows recovery after a carriage return has been typed at the end of the command line, rather than an altmode.
5.1.6 MTA.
MTA. now handles error conditions correctly.
5.1.7 PIP
PIP no longer changes protection codes during COPY (with no switches) operations and the Editor will use default protect codes.
PIP now gives lines input during G switch correction the correct word pair count.
5.1.8 RESMON
Mp>The resident monitor (RESMON) has the correct API channel address for the LT19.A modification was made to the Resident Monitor such that illegal interrupts from keyboard devices attached to LT15s and LT19s are dismissed, instead of allowing them to crash the system (RESMON) with incessant IOPS3s.
5.1.9 SGEN
SGEN no longer deletes the skip mnemonics for PDP-15 devices when the delete request was for the like PDP-11 devices.
5.1.10
VT ON/OFF will return to the default condition as established at SGEN time at LOGIN/LOGOUT time. Further, if VT is on, the state of +x will be retained.
5.1.11 FORTRAN COMPILER
The version has been changed to:
F4X V3B00
or
FPF4X V3B000 (FPP systems only)
or
F4X9 V3B000 (PDP-9 systems)
1. Erroneous error <E < is no longer reported instead of <08E<.
2. Missing parentheses in implied DO loops are now detected and error message <33X< has been added.
3. Extraneous characters at the end of or within assignment statements now report added error message <34X<.
5.1.12
A problem that caused occasional bad blocks during copying operations has been corrected.
5.2.1 ABSL11
ABSL11 was modified so that it could correctly load a 12K module into a 12K UNICHANNEL. Note that the bootstrap order is now important; read ABSL11, start the PDP-11 and then read the PDP-11 binary tape. If the original tape has no starting address, additional tapes can be loaded by CONTINUEing the PDP-11, and CONTINUEing the PDP-15 twice. In no case can a PDP-11 module containing a core address larger than PDP-11 local memory be loaded.
5.2.2 CARD READER
The CR11 Card Reader under PIREX gave IOPS45 and IOPS76 error messages when powered up. The IOPS76 and IOPS45 no longer occur.
5.2.3 RKBOOT
RKBOOT was modified so that temporary TCBs to be sent to the PDP-11 were generated in the data channel locations rather than the API locations.
The use of the VT ON feature reduces the amount of core available for the MAC11 assembler. The message INSUFFICIENT CORE may print out for large assemblies, and the assembly will terminate. Type VT OFF, and retry the assembly. Note, that if you specify VT ON to SGEN, VT ON will remain in force, even when the CONTROL X has not yet been typed.
The use of LTORG in a program will sometimes result in the SIZE of the binary being calculated as being larger than it should be.
It is not possible to do argument concatenation in nested macros. Global declarations that follow macro definitions are not handled correctly. The problem can be circumvented by putting all .GLOBLs before any macro definitions.
The Copy function to or from magtape does not work correctly.
Since the editor LIST command does not issue a .CLOSE after each use, the output may become "stuck" in the spooler print buffer. Additional output (or a program issuing a .CLOSE) will force this information to the printer.
The "Halt at End of File" option will not work correctly if the switch is engaged (up) during the output of the last file in a sequence. The succeeding file may under rare circumstances not be printed when the "Halt at End of File" switch is lowered. If another file is printed, the last file will be printed and normal operation will be resumed.
ACL PROBLEMS
6.5 PIP does not transfer (T) binary files with extensions other than BIN properly.
6.6 CHAIN and XCHAIN do not handle multiple entry points in MACRO segments properly.