Trailing-Edge
-
PDP-10 Archives
-
BB-L665B-BM
-
documentation/mountr.edt
There is 1 other file named mountr.edt in the archive. Click here to see a list.
PCO Log Report
*********************
*PCO #:20-MONITO-248*
*********************
[PCO Write-up]
**********
[SYMPTOM]
Attempts to use labeled tape return garbage error number.
**********
[DIAGNOSIS]
Code not written.
**********
[CURE]
Adjust labeled tape filename size checking code to return a new
error code to indicate that tape label filename specification exceeds
17 characters; and add the error code and description to the MONSYM
file.
[FILCOM]
@! PATCH TO RELEASE 4 SYSTEMS TO CORRECT GARBAGE ERROR CODES
@! RETURNED ON USE OF TOO-LONG FILENAMES FOR LABELED TAPES.
@! NEEDS ASSOCIATED EDIT TO MONSYM TO DEFINE GJFX53 STRING.
@
@ENABLE (CAPABILITIES)
$
$GET SYSTEM:MONITR
$START 140
DDT
TAPE$:
FFF/ 0 YYY: MOVEI T1,602461
FFF+1/ 0 RET
FFF+2/ 0 FFF:
MTNML+17/ RET JRST YYY
MTEXL+21/ RET JRST YYY
MTEXL+30/ RET JRST YYY
MTEXL+33/ RET JRST YYY
^Z
$SAVE SYSTEM:MONITR
<SYSTEM>MONITR.EXE.2 Saved
$
And the MONSYM edit:
File 1) AU4:MONSYM.MAB[4,43] created: 1258 11-Jun-1980
File 2) AU4:MONSYM.MAC[4,43] created: 1213 23-Sep-1980
1)59 > ;END OF .ERCOD DEFINITION
****
2)59 ;**;[1785] Add one line before end of .ERCOD definition JGZ
23-SEP-80
2) .ERR (2461,GJFX53,<Tape label filename specification exceeds 17
characters>)
2) > ;END OF .ERCOD DEFINITION
**************
Submit MONSYM.CTL to rebuild the MONSYM files and ERRMES.BIN.
[End PCO Write-up]
*********************
*PCO #:20-MONITO-245*
*********************
[PCO Write-up]
**********
[SYMPTOM]
Error Message IOX22 'Invalid HDR1 Sequence Number' when setting data
mode or attempting to read from some EBCDIC labeled tapes.
**********
[DIAGNOSIS]
When TOPS-20 checks the Form Control Byte in the HDR2 Label in the
routine GETFC0, it enforces that the Form Control Byte (CP 37) conform
to DEC standard (A, M, X, or space). ANSI standard X3.27-1969 clearly
states that CP 16-50 of the HDR2 Label are system defined and should
be ignored in interchange mode. TOPS-20 does not ignore this byte and
as a result may disagree with the contents of this character position
and return the IOX22 error message.
**********
[CURE]
At the check in the GETFC0 routine for an EBCDIC labled tape, return
the code for an undefined form control rather than checking for
consistency of this byte with DEC standard.
[FILCOM]
@! Patch to Version 4 of TOPS-20 to ignore form control in HDR2 Label
@! for EBCDIC labeled tapes.
@!
@GET SYSTEM:MONITR.EXE
@ST 140
DDT
TAPE$:
GETFC0+2/ JRST GETFC2 JRST FFF
FFF/ 0 MOVEI T1,.TPFNC
FFF2+1/ 0 JRST RSKP
FFF2+2/ 0 FFF:
^Z
@SAVE PS:<SYSTEM>MONITR.EXE
@!
*********************
*PCO #:20-MONITO-243*
*********************
[PCO Write-up]
**********
[SYMPTOM]
Accounting is being done on nonregulated structures.
**********
[DIAGNOSIS]
Edit 67 to MOUNTR corrected part of the problem by testing the correct
bit. The monitor did not set up the status bits correctly before
sending a message to MOUNTR.
**********
[CURE]
At SNDUSG+24 move status bits from left half of T4 into the right half
of MSTIPC+2. Edit 67 in answer to SPR 20-14215 is also required.
[FILCOM]
@GET SYSTEM:MONITR.EXE
@ST 140
DDT
SNDUSG+24/ HRRM T4,T4(P6) HLRM T4,T4(P6)
^Z
@SAVE SYSTEM:MONITR.EXE
*********************
*PCO #:20-MONITO-217*
*********************
[PCO Write-up]
**********
[SYMPTOM]
Values returned for .MOIRD, .MOIWT, .MOIRF, .MOIWF entries of
the .MOINF function of the MTOPR JSYS are wrong.
**********
[DIAGNOSIS]
Frame count and operation count entries are reversed.
**********
[CURE]
Change the MTINFT XCT table to do things correctly.
[FILCOM]
@! PATCH TO RELEASE 4 TOPS-20 MONITORS TO CORRECT THE .MOINF
@! FUNCTION OF THE MTOPR JSYS WHICH REVERSED THE ENTRIES
@! FOR THE .MOIRD AND .MOIRF AND THE .MOIWT AND .MOIWF VALUES.
@
@ENABLE (CAPABILITIES)
$GET SYSTEM:MONITR
$START 140
DDT
MEXEC$:
MTINFT+.MOIRD-1/ MOVE T1,CX(FX) MOVE T1,UDBRCT(Q3)
MTINFT+.MOIWT-1/ MOVE T1,P(FX) MOVE T1,UDBWCT(Q3)
MTINFT+.MOIRF-1/ MOVE T1,20(FX) MOVE T1,UDBRED(Q3)
MTINFT+.MOIWF-1/ MOVE T1,21(FX) MOVE T1,UDBWRT(Q3)
^Z
$SAVE SYSTEM:MONITR
<SYSTEM>MONITR.EXE.2 Saved
$
*********************
*PCO #:20-MONITO-199*
*********************
[PCO Write-up]
**********
[SYMPTOM]
Volume Valid is not cleared for labeled tapes under restart
conditions, leading the system to believe false information.
**********
[DIAGNOSIS]
The bits start clear, which handles the initial startup case;
the AC field is missing in the AOBJN loop to clear the bits.
**********
[CURE]
Fill in the proper AC in the AOBJN.
[FILCOM]
@! PATCH TO RELEASE 4 SYSTEMS TO CORRECT FAILURE TO CLEAR
@! LABELED TAPE VOLUME VALID ON RESTART CONDITIONS.
@
@ENABLE (CAPABILITIES)
$GET SYSTEM:MONITR
$START 140
DDT
TAPE$:
MTCLV1+2/ AOBJN MTCLV1 AOBJN U,MTCLV1
^Z
$SAVE SYSTEM:MONITR
<SYSTEM>:MONITR.EXE.2 Saved
$
*********************
*PCO #:20-MONITO-187*
*********************
[PCO Write-up]
**********
[SYMPTOM]
Problems when clearing volid valid for a tape.
**********
[DIAGNOSIS]
AOBJN loop in MTCLVL routine should be using T3 in loop, but is
using AC U instead.
**********
[CURE]
Use the right AC to AOBJN on.
[FILCOM]
@! PATCH TO RELEASE 4 SYSTEMS TO CORRECT LABELED TAPE
@! PROBLEMS DUE TO USE OF WRONG AC IN LOOP.
@
@ENABLE (CAPABILITIES)
$GET SYSTEM:MONITR
$START 140
DDT
TAPE$:
MTCLA2+3/ AOBJN U,MTCLA2 AOBJN T3,MTCLA2
^Z
$SAVE SYSTEM:MONITR
<SYSTEM>MONITR.EXE.2 Saved
$
*********************
*PCO #:20-MONITO-178*
*********************
[PCO Write-up]
**********
[SYMPTOM]
COBOL programs receive errors such as "Read an EOF instead of a
label" or record sequence errors while reading magtapes.
**********
[DIAGNOSIS]
Tape read-ahead is handled incorrectly, allowing a race condition
in the tape status code concerning a bit used both at program level
and at PHYSIO interrupt level.
**********
[CURE]
Prevent the race by doing a call to the routine used to achieve
proper status synchronization. Separate patches for 3A and 4 are
given.
[FILCOM]
@
@! PATCH TO 3A SYSTEMS TO CORRECT PROBLEMS WITH MAGTAPE READ-AHEAD
@
@ENABLE (CAPABILITIES)
$GET SYSTEM:MONITR
$ST 140
DDT
MAGTAP$:
MTSTS+4/ HLRZ U,DEV FFF$$<
FFF/ HLRZ U,DEV
FFF2+1/ 0 CALL MTACLW
FFF2+2/ 0 RET$>
FFF2+3/ JUMPA A,MTSTS+5
FFF2+4/ JUMPA B,MTSTS+6
MTSTS+4/ JUMPA FFF2
^Z
$SAVE SYSTEM:MONITR
<SYSTEM>MONITR.EXE.2 Saved
$
@
@! PATCH FOR RELEASE 4 SYSTEMS TO CORRECT PROBLEMS WITH MAGTAPE READ-AHE
AD
@
@ENABLE (CAPABILITIES)
$GET SYSTEM:MONITR
$ST 140
DDT
MAGTAP$:
MTSTS+5/ CALL UPDSTS CALL UPDSTA
^Z
$SAVE SYSTEM:MONITR
<SYSTEM>MONITR.EXE.2 Saved
$
*********************
*PCO #:20-MONITO-160*
*********************
[PCO Write-up]
**********
[SYMPTOM]
COBOL programs that write multi-reel EBCDIC tape files will
not write tape marks on the end of any of the reels except
the last one.
**********
[DIAGNOSIS]
This is because, when the physical end of tape is
encountered, PA1050 resets the data mode and then closes the
tape file. Resetting the data mode causes all buffers to be
written to tape and the buffers are then released. The
CLOSF JSYS decides whether to write tape marks on whether
there are buffers allocated for that Magnetic Tape Unit.
The JSYS assumes that if there are no buffers allocated then
no output could have been performed on that unit.
Therefore, there is no need to write the tape marks. This
is a false assumption.
**********
[CURE]
Remove the test at MTACLZ+12, which checks whether buffers
are allocated and replace it with a SKIPA.
[FILCOM]
@ENABLE (CAPABILITIES)
$GET SYSTEM:MONITR.EXE
$ST 140
DDT
MAGTAP$:
MTACLZ+12/ TLNN IOS,110000 SKIPA
^Z
$SAVE (ON FILE) SYSTEM:MONITR.EXE
$DISABLE (CAPABILITIES)
@
*********************
*PCO #:20-MONITO-110*
*********************
[PCO Write-up]
**********
[SYMPTOM]
Illegal read error when .MSRNU function of the MSTR JSYS is
used and the argument block length is less than six words.
**********
[DIAGNOSIS]
Routine uses word 4 (.msrsn) and word 5 (.msrsa) of the
argument block as pointers regardless of whether the
argument block has been specified as that long.
**********
[CURE]
Check to see if argument block is long enough to contain
these words before using them as pointers.
[FILCOM]
@ENABLE]
$GET SYSTEM:MONITR
$ST 140
DDT
MSTR$:
FFF/ 0 ARGSIZ: HLRZ 1,1
FFF2+1/ 0 FFF:
MSTRS4+33/ MOVE A,C(B) FFF$<
FFF/ 0 XCTU ARGSIZ
FFF+1/ 0 CAIGE 1,5
FFF+2/ 0 JRST MSTRS4+42
$>
FFF+3/ MOVE A,C(B)
FFF+4/ JUMPA A,MSTRS4+34
FFF+5/ JUMPA B,MSTRS4+35
MSTRS4+33/ JUMPA FFF2+1
MSTRS5+22/ HRRZ A,-4(P) FFF$<
FFF/ 0 XCTU ARGSIZ
FFF+1/ 0 CAIGE 1,6
FFF+2/ 0 JRST MSTRS6
$>
FFF+3/ HRRZ A,-4(P)
FFF+4/ JUMPA A,MSTRS5+23
FFF+5/ JUMPA A,MSTRS5+24
MSTRS5+22/ JUMPA FFF2+7
^Z
*********************
*PCO #:20-MONITO-257*
*********************
[PCO Write-up]
**********
[SYMPTOM]
When switching volumes on labelled tape the record size is reset
to job defaults.
**********
[DIAGNOSIS]
The volume switch code does not check record size after a volume
switch.
**********
[CURE]
Check record size during volume switch.
WARNING: This patch may cause problems since tapes written by
the unpatched monitor will have different record sizes on all but the
first volume if a non-default record size was specified for the first
volume. If this patch is not installed the problem can be
circumvented by using the SETJB JSYS or the EXEC command SET TAPE
RECORD-LENGTH (TO) to set the job default record size.
[FILCOM]
@! PATCH TO ALLOW A VOLUME SWITCH AND PRESERVE
@! RECORD SIZE.
@!
@! MAY CAUSE MULTI VOLUME TAPES WRITTEN BEFORE
@! THIS PATCH TO BE UNREADABLE IF A NON DEFAULT
@! RECORD SIZE WAS SPECIFIED FOR THE FIRST VOLUME
@
@ENABLE (CAPABILITIES)
$GET SYSTEM:MONITR.EXE
$START (PROGRAM) 140
DDT
VVBLOK+2/ T1,,T1 2,,2
VVBLK1+1/ LDB T1,662663 LDB T2,$Q
VVBLK1#+2/ HRRM T1,-2(P) HRRM T2,-2(P)
VVBLK1#+3/ CALL CLRVV JRST FFF
FFF/ 0 HRRZ T2,MTANR1(T1)
FFF+1/ 0 MOVEM T2,-3(P)
FFF+2/ 0 CALL CLRVV
FFF+3/ 0 JRST VVBLK1+4
FFF+4/ 0 FFF:
VVBLK4+1/ HRRZ T2,-2(P) HRRZ T2,-3(P)
VVBLK4#+2/ LDB CX,662671 HRRM T2,MTANR1(T1)
VVBLK4#+3/ CAMN T2,CX HRRZ T2,-2(P)
VVBLK4#+4/ JRST RSKP JFCL
^Z
$SAVE SYSTEM:MONITR.EXE
<SYSTEM>MONITR.EXE.2 Saved
*********************
*PCO #:20-MONITO-298*
*********************
[PCO Write-up]
**********
[SYMPTOM]
Structures are always marked domestic in usage accounting records.
**********
[DIAGNOSIS]
The structure status bits are not sent to MOUNTR correctly and the
primary public structure never has bit MS%DOM marked.
**********
[CURE]
Send bits correctly. To achieve the desired results also install
MOUNTR edit 116 to version 4 of MOUNTR.
Digital Equipment Corporation 12-JUN-81 Page 3
PCO Log Report
[EDIT]
@! CORRECTLY SEND STRUCTURE STATUS TO MOUNTR
@! REQUIRES EDIT 116 TO VERSION 4 OF MOUNTR
@
@ENABLE (CAPABILITIES)
$GET SYSTEM:MONITR.EXE
$START (PROGRAM) 140
DDT
SNDUSG+21/ HLRZ T4,T3(T1) MOVE T4,SDBSTS(T1)
SNDUSG+23/ TLO T4,444000 TLO T4,544000
^Z
$SAVE SYSTEM:MONITR.EXE