Trailing-Edge
-
PDP-10 Archives
-
bb-bt99g-bb
-
utl702.d09
There is 1 other file named utl702.d09 in the archive. Click here to see a list.
EDIT DESCRIPTIONS FOR UTILITIES-10-V702
EDIT 515 FOR BACKUP
[SYMPTOM]
BACKUP will not read old BACKUP tapes which are labelled anything
other than BYPASS.
[DIAGNOSIS]
Edit 426 put in checks to compare the label the tape was written with
and the label the tape is currently mounted with. If the comparison
was not appropriate, BACKUP gave the error %BKPDLT Tape being read xxx
was written yyy BKPTGC errors may occur type "GO" to continue. This
check is unnecessary because PULSAR does all the label checking before
BACKUP ever reads the tape.
[CURE]
Delete the checks for label types. This also deletes the error
messages.
********************************************************************************
EDIT 516 FOR BACKUP
[SYMPTOM]
If a user is PATHed to an SFD and types a LIST command before SAVEing,
the listing file begins in the SFD and finishes in the UFD.
[DIAGNOSIS]
The LIST command causes a LOOKUP and ENTER to be done to the SFD.
After finishing a UFD SAVE, BACKUP CLOSEs the listing file preserving
the PPN word, then does a LOOKUP and ENTER with the PPN word filled
in. This LOOKUP/ENTER established the file in the UFD because the
monitor is forced to put the file in the UFD with the PPN word
non-zero.
[CURE]
Zero the PPN word before the LOOKUP so that the monitor will default
to the job's current path.
********************************************************************************
EDIT 517 FOR BACKUP
[SYMPTOM]
BACKUP gets an ?Illegal instruction at user PC 401661.
[DIAGNOSIS]
If a customer site has SUPER I/O disabled, has a LIB: which contains
a listing file, and types APPEND to the listing file, BACKUP does a
LOOKUP which succeeds, and ENTER which fails with error ERISU%
(execution of an illegal sequence of monitor calls), and then does a
USETI -1 to append to the file. With SUPER I/O disabled, the USETI -1
causes an illegal instruction.
[CURE]
Do not do the USETI -1 if the ENTER fails with ERISU%.
********************************************************************************
EDIT 520 FOR BACKUP
[SYMPTOM]
If a user is connected to his UFD, and specifies a listing file to an
SFD, BACKUP splits the listing file across the UFD and SFD.
[DIAGNOSIS]
BACKUP initiates the listing file in the SFD. To preserve the listing
file, BACKUP CLOSEs the file and then establishes the file in update
mode using the LOOKUP/ENTER block. Edit 517 zeroed the ppn word
(.RBPPN) in the LOOKUP block to allow the monitor to find the file in
the default path which is not the desired effect in this case.
[CURE]
Solve all problems of preserving the listing file by converting the
routine CLSUF2 to do a FILOP. checkpoint. This edit will not run in
pre-6.03 monitors. Another side effect of this edit is that the
listing files will become smaller. The LOOKUP/ENTER/USETI combination
positioned the file at the end of a block boundary. The behavior of
the checkpoint function is to position the file at the next word
boundary.
********************************************************************************
EDIT 521 FOR BACKUP
[SYMPTOM]
Under 7.01 BACKUP may abort during the CHECK command after
%BKPPBR Prior block repeated with an ?Illegal address in UUO
or ?UUO error. This problem was not reproducible in-house.
[DIAGNOSIS]
When a %BKPPBR Prior block repeated situation occurs during
a check command, BACKUP starts twiddling the virgin buffer
and uses bits to reset the disk input buffers to continue
checking the file. If I/O is still active, the buffer
modifications may cause UUO errors in 7.01 or 7.01A.
[CURE]
Add a WAIT UUO to wait for disk file activity to stop before
twiddling the buffers. This should not be necessary under
7.02, but a WAIT UUO does not hurt anything and will not
adversely affect performance since this is an unusual case.
********************************************************************************
EDIT 444 FOR COMPIL
[SYMPTOM]
/SAVE and /SSAVE do not work on output filename
specification. The form is: LOAD A/SSAVE=B.REL,C.REL
This produces the file B.EXE when COMPIL incorrectly
parses the string and passes the wrong info to LINK.
[DIAGNOSIS]
Nobody ever thought of this case before. When using
the output filename, only specific switches other than LINK
switches actually will affect it. The two save switches are
one case.
[CURE]
Rewrite the sections dealing with the output filename
and the two save switches to be intraline as well as
possibly on the output filename.
********************************************************************************
EDIT 445 FOR COMPIL
[SYMPTOM]
DEBUG A.MAC/NOCOMP DOES NOT WORK
[DIAGNOSIS]
/NOCOMP SWITCH DOESN'T WORK FOR "DEBUG A.MAC/NOCOMP"
[CURE]
FIX /NOCOMP SWITCH SO THAT IT WORKS WITH DEBUG A.MAC/NOCOMP
********************************************************************************
EDIT 446 FOR COMPIL
[SYMPTOM]
COMPIL gives the error "too many switches" when many
switches passed to LINK.
[DIAGNOSIS]
Buffer size is fairly small.
[CURE]
Increase the buffer size for to accept more switches.
********************************************************************************
EDIT 451 FOR COMPIL
[SYMPTOM]
COBOL-74 DOESN'T DEFAULT TO COBOL COMPILER
[DIAGNOSIS]
COBOL-68 WAS DEFAULTED TO COBOL COMPILER
[CURE]
MAKE COBOL-74 DEFAULT TO COBOL COMPILER
********************************************************************************
EDIT 452 FOR COMPIL
[SYMPTOM]
No support for SIMULA compiler although LINK and SPRINT
provide it.
[DIAGNOSIS]
Code never written.
[CURE]
Implement it. LINK recognizes /DEBUG:SIMULA with LINK
edits 1321 and 1267, so just implement the source file
recognition.
********************************************************************************
EDIT 453 FOR COMPIL
[SYMPTOM]
With edit 444 installed, the sequence "LOAD A/SAVE=B,C"
would put garbage into file B.
[DIAGNOSIS]
When resetting names after setting the output name for
the /SAVE switch, the extension would be carried over
incorrectly.
[CURE]
Clear the extension always to allow compiler to produce
".REL"s.
********************************************************************************
EDIT 454 FOR COMPIL
[SYMPTOM]
LABEL command does not work.
[DIAGNOSIS]
It was incorrectly thought to be no longer supported
and was so removed.
[CURE]
Reinstall the removed code.
********************************************************************************
EDIT 455 FOR COMPIL
[SYMPTOM]
COMPIL outputs the character "S" at the beginning of TMPCOR files
to editors.
[DIAGNOSIS]
The "S" character was a command to LINED to select a file. Since
LINED support was removed, the character is superfluous.
[CURE]
Pass a "<space>" instead so that we can slowly remove the crock.
********************************************************************************
EDIT 456 FOR COMPIL
[SYMPTOM]
File copies take much longer.
[DIAGNOSIS]
Edit 430 removed the core argument to the RUN uuo which setup PIP
with a 5K lowseg. It now has no such argument and never expands.
[CURE]
Reinsert the code that was erroneously removed by edit 430.
There was no such debugging purpose. Calculations showed the optimal
size for PIP is 10P lowseg along with taking into account the increase
to 11P of the highseg.
********************************************************************************
EDIT 457 FOR COMPIL
[SYMPTOM]
If a user tries to compile a COBOL-74 program with a non-standard
extension (i.e. not .CBL), and uses "/C74", COMPIL will compile the
program with FORTRAN.
[DIAGNOSIS]
This has been a long standing feature of COMPIL. If a filename
has a non-standard extension, the default compiler will be FORTRAN.
[CURE]
Make the compiler selection switches (/C74,/C68,/F40,/F10) imply
the compiler type. This has been a long overdue correction to the
compiler selection schema of COMPIL.
********************************************************************************
EDIT 460 FOR COMPIL
[SYMPTOM]
LABEL command does not exist.
[DIAGNOSIS]
LABEL command was incorrectly removed. Edit 454 put
routine back but omitted the command table entry.
[CURE]
Insert command LABEL into command table CTABLE.
********************************************************************************
EDIT 461 FOR COMPIL
[SYMPTOM]
File copies run too slow.
[DIAGNOSIS]
Edit 430 removed the core argument to the RUN uuo which setup PIP
with a 5K lowseg. It now has no such argument and never expands.
Edit 456 reinserted the code to do the RUN uuo with the core argument
but is still slow.
[CURE]
Increase the core argument to 40P.
********************************************************************************
EDIT 462 FOR COMPIL
[SYMPTOM]
If user types "DEBUG/REL FOO" where FOO.REL is a binary
file produced by Fortran, you get DDT instead of FORDDT.
[DIAGNOSIS]
When COMPIL sees the "/REL" switch it decides to save
itself some work and simply passes the filename to LINK.
Consequently it doesn't know what kind of a REL file it is
and LINK decides to load DDT.
[CURE]
Since COMPIL already reaches into the REL file to find
out what kind of REL block it is for some of the processor
incompatibilities, it is preferable to do the debugging
selection in COMPIL. In the case that we have a REL file,
we are debugging, and the processor is unknown, the new
routine LKREL will find out the processor type and set the
flag for the debugger choice to default to the processors
debugger if none else specified. This required considerable
reordering of some routines, to allow consistent calling
mechanisms between the routines that look up files.
********************************************************************************
EDIT 564 FOR COMPIL
[SYMPTOM]
Compil gets "address checks" while processing commands and grows
larger than necessary in size.
[DIAGNOSIS]
Disk buffers were being setup incorrectly and wrongly returned to
free core.
[CURE]
Remove most of EDIT 241 and use the disk buffer setup during
initialization.
********************************************************************************
EDIT 565 FOR COMPIL
[SYMPTOM]
COMPIL gives misleading error message when source files are not
found or .REL files are specified in the "+" construction.
[DIAGNOSIS]
COMPIL outputs erroneous error message.
[CURE]
Create new error message and use it for this case.
********************************************************************************
EDIT 566 FOR COMPIL
[SYMPTOM]
COMPIL can fail in several ways when using indirect command files
that contain comments on the first line(s).
[DIAGNOSIS]
COMPIL expects a continuation character after every command line
terminator (i.e. comma). This continuation character is not found
after an initial comment line, therefore COMPIL gets confused and
fails erroneously.
[CURE]
Add code to COMPIL to check for a initial comment line and ignore
it properly.
********************************************************************************
EDIT 567 FOR COMPIL
[SYMPTOM]
Do .COMP/CREF -files-
.COMP/CREF -more files-
where both command strings are long. Only the files in the first
command line are processed by CREF.
[DIAGNOSIS]
When the CREF command file is too large to be written out to
TMPCOR, COMPIL writes the .TMP file to disk, without deleting the
original TMPCOR file. When the CREF program is run, only the files in
TMPCOR get processed and the .TMP file on disk is never looked for
because the CREF TMPCOR file was found.
[CURE]
Add code to COMPIL to delete the TMPCOR file when writing to
disk.
********************************************************************************
EDIT 570 FOR COMPIL
[SYMPTOM]
COMPIL does not allow a "minus sign" to be used in specifying
COBOL-74 processor switches.
[DIAGNOSIS]
COMPIL assumes that all switches only contain alphanumerics.
COBOL-74 allows the use of non-alphanumeric characters in its
compiler switches(i.e., "-").
[CURE]
Allow the "minus sign" in specifying processor switches.
********************************************************************************
EDIT 571 FOR COMPIL
[SYMPTOM]
COMPIL does not use language specific debugger for ALGOL.
[DIAGNOSIS]
COMPIL uses DDT as default debugger for ALGOL.
[CURE]
Change default to ALGDDT instead of DDT. User can use the /DDT
switch to override ALGDDT.
********************************************************************************
EDIT 572 FOR COMPIL
[SYMPTOM]
COMPIL "seems" to handle defaulting of SFDs in filespecs, but
does not. For example; .COPY A=C[,,,,Sfd]
[DIAGNOSIS]
COMPIL does not have code to handle this case. COMPIL does not
complain when it parses the "defaulted" filespec and passes an
erroneous directory specification to the program it's dispatching to.
[CURE]
We have termed this a temporary restriction due to the fact that
many utilities that COMPIL dispatches to, do not know how to handle
the defaults either. In the meantime, COMPIL will issue an error
message to the effect that it does not allow SFD defaulting.
********************************************************************************
EDIT 573 FOR COMPIL
[SYMPTOM]
LINK complains about "incorrect file specifications" when loading
a /LIB file when an explicit device is specified and recompilation
into our area is necessary (usually a different file structure).
[DIAGNOSIS]
COMPIL mistakenly bypasses this check. It only checks to see if
a /LIB file was specified and propagates the specified input device to
LINK. This is wrong, because the the recompilation causes the .REL
file to be created in our directory (or current path) on a possibly
different file structure.
[CURE]
Remove the check in COMPIL and see if the .REL file for the /LIB
file specified was found. If not found, pass "DSK:" to LINK instead
of the explicit device given.
********************************************************************************
EDIT 574 FOR COMPIL
[SYMPTOM]
COMPIL does not know about /GFLOAT and /F66 switches for FORTRAN.
[DIAGNOSIS]
No code to handle them.
[CURE]
Add code to process these switches. Document these two new
switches in the System Commands section of TOPS-10 Software Notebook
Set Volume 2.
********************************************************************************
EDIT 72 FOR CREF
[SYMPTOM]
The ALGOL nested-table listing gives the heading 'E----1
PROGRAM' where E----1 is mistaken for a program name.
[DIAGNOSIS]
When CREFing a FAIL program the last entry in the linked
list of the nested-table is the program name. There was
nothing to distinguish an ALGOL program from a FAIL program,
consequently the last entry in the ALGOL nested-table list
was used as the program name.
[CURE]
Don't try to print a program name for ALGOL cref files.
********************************************************************************
EDIT 73 FOR CREF
[SYMPTOM]
A cross reference listing will have symbol names longer than
seven characters translated incorrectly if they are in lower
case.
[DIAGNOSIS]
Characters are read one at a time in the routine at FM4 and
translated into sixbit. Edit 21 converted each character to
upper case ASCII first if necessary. If a symbol cannot fit
into one word, the LNGSYM routine is used. This routine
gets more core and continues getting characters and
translating them. It should also translate the lower case
characters into upper case.
[CURE]
Edit 73 will add the necessary code to test for lower case
data and convert to upper case.
********************************************************************************
EDIT 74 FOR CREF
[SYMPTOM]
During program execution the following error message is
issued:
?CRFIMA Insufficient memory available
[DIAGNOSIS]
All the core available to the low segment has been
allocated, up to the lower limit of the high segment.
[CURE]
The high segment can be raised from 400K to 560K without
causing any problem. This will free up 160K of core for the
low segment. Edit 74 will make the necessary changes.
********************************************************************************
EDIT 76 FOR CREF
[SYMPTOM]
Program execution halts with the error message:
?IO to unassigned channel at user PC 402770
if the /T switch is used on the input file specifications.
[DIAGNOSIS]
The switch is tested on while setting up the positioning for
the input file, but then the output file's channel is used
in the monitor call.
[CURE]
Change the channel to the input file's channel.
********************************************************************************
EDIT 100 FOR FILCOM
[SYMPTOM]
If the right angle bracket of the second input file specification is
missing in the command "=A.B[C,D,E],A.B[F,G]", FILCOM reports a LOOKUP
error 23 (SFD not found). Note that the PPNs are different.
[DIAGNOSIS]
Edit 50 added to code to accept a line-terminating character in lieu
of a right angle bracket to be similar to programs that use SCAN.
However, it did not catch all cases.
[CURE]
Add line-terminating checks in all cases of a check of "]" to
determine if a term is complete (there is only one other case).
********************************************************************************
EDIT 101 FOR FILCOM
[SYMPTOM]
If the right angle bracket of the second input file specification is
missing in the command "=A.B[C,D,E],A.B[F,G]", FILCOM reports a LOOKUP
error 23 (SFD not found). Note that the PPNs are different.
[DIAGNOSIS]
Edit 50 added to code to accept a line-terminating character in lieu
of a right angle bracket to be similar to programs that use SCAN.
However, it did not catch all cases.
[CURE]
Add line-terminating checks in all cases of a check of "]" to
determine if a term is complete (there is only one other case).
********************************************************************************
EDIT 102 FOR FILCOM
[SYMPTOM]
If the right angle bracket of the second input file specification is
missing in the command "=A.B[C,D,E],A.B[F,G]", FILCOM reports a LOOKUP
error 23 (SFD not found). Note that the PPNs are different.
[DIAGNOSIS]
Edit 50 added to code to accept a line-terminating character in lieu
of a right angle bracket to be similar to programs that use SCAN.
However, it did not catch all cases.
[CURE]
Add line-terminating checks in all cases of a check of "]" to
determine if a term is complete (there is only one other case).
********************************************************************************
EDIT 103 FOR FILCOM
[SYMPTOM]
If the right angle bracket of the second input file specification is
missing in the command "=A.B[C,D,E],A.B[F,G]", FILCOM reports a LOOKUP
error 23 (SFD not found). Note that the PPNs are different.
[DIAGNOSIS]
Edit 50 added to code to accept a line-terminating character in lieu
of a right angle bracket to be similar to programs that use SCAN.
However, it did not catch all cases.
[CURE]
Add line-terminating checks in all cases of a check of "]" to
determine if a term is complete (there is only one other case).
********************************************************************************
EDIT 104 FOR FILCOM
[SYMPTOM]
If the right angle bracket of the second input file specification is
missing in the command "=A.B[C,D,E],A.B[F,G]", FILCOM reports a LOOKUP
error 23 (SFD not found). Note that the PPNs are different.
[DIAGNOSIS]
Edit 50 added to code to accept a line-terminating character in lieu
of a right angle bracket to be similar to programs that use SCAN.
However, it did not catch all cases.
[CURE]
Add line-terminating checks in all cases of a check of "]" to
determine if a term is complete (there is only one other case).
********************************************************************************
EDIT 105 FOR FILCOM
[SYMPTOM]
If the right angle bracket of the second input file specification is
missing in the command "=A.B[C,D,E],A.B[F,G]", FILCOM reports a LOOKUP
error 23 (SFD not found). Note that the PPNs are different.
[DIAGNOSIS]
Edit 50 added to code to accept a line-terminating character in lieu
of a right angle bracket to be similar to programs that use SCAN.
However, it did not catch all cases.
[CURE]
Add line-terminating checks in all cases of a check of "]" to
determine if a term is complete (there is only one other case).
********************************************************************************
EDIT 106 FOR FILCOM
[SYMPTOM]
If the right angle bracket of the second input file specification is
missing in the command "=A.B[C,D,E],A.B[F,G]", FILCOM reports a LOOKUP
error 23 (SFD not found). Note that the PPNs are different.
[DIAGNOSIS]
Edit 50 added to code to accept a line-terminating character in lieu
of a right angle bracket to be similar to programs that use SCAN.
However, it did not catch all cases.
[CURE]
Add line-terminating checks in all cases of a check of "]" to
determine if a term is complete (there is only one other case).
********************************************************************************
EDIT 76 FOR FILCOM
[SYMPTOM]
Filcom does not report label+offset in differences file.
[DIAGNOSIS]
Add support from ADP for /O - report label+offset in
differences file. This is useful for .MAC or .P11 files, since
it eliminates ambiguity in reporting the location of
differences.
[CURE]
Edit 76 of FILCOM fixes this problem.
********************************************************************************
EDIT 77 FOR FILCOM
[SYMPTOM]
If the right angle bracket of the second input file specification is
missing in the command "=A.B[C,D,E],A.B[F,G]", FILCOM reports a LOOKUP
error 23 (SFD not found). Note that the PPNs are different.
[DIAGNOSIS]
Edit 50 added to code to accept a line-terminating character in lieu
of a right angle bracket to be similar to programs that use SCAN.
However, it did not catch all cases.
[CURE]
Add line-terminating checks in all cases of a check of "]" to
determine if a term is complete (there is only one other case).
********************************************************************************
EDIT 324 FOR SYSTAT
[SYMPTOM]
"SYS P" REPORTS INCORRECT NUMBER OF RETIRES (UNIECT).
[DIAGNOSIS]
RETRIES FIELD BITS 15-35
[CURE]
FIXED AT UER2T2+5
********************************************************************************
EDIT 325 FOR SYSTAT
[SYMPTOM]
ILL MEM REF'S
[DIAGNOSIS]
ONE WORD GLOBALS BYTE POINTERS WHICH MICROCODE (352) CREATES
[CURE]
FIXED AT MSG:
********************************************************************************
END OF UTILITIES-10-V702