Trailing-Edge
-
PDP-10 Archives
-
BB-5255D-BM
-
4-documentation/mountr.tco
There are 7 other files named mountr.tco in the archive. Click here to see a list.
TOPS20 Change Order Number 4.2324
Written by: R.ACE 13-Jul-79 06:18:26
Edit checked: NO Document: NO
TCO Tested: NO Maintenance Release: NO
Hardware-related: YES
Program: MOUNTR
Related TCO's:
Related SPR's:
Problem: WHEN A DUMPER TAPE WITH A LARGE BLOCKING FACTOR IS LOADED ON
A DRIVE AND MOUNTR TRIES TO READ ITS LABEL, MANY ERROR RETRIES OCCUR.
THIS CAUSES A LONG WAIT, AND POSSIBLY MOUNTR-LEVEL I/O JSYS TIMEOUTS.
Diagnosis: A FEW REASONS:
1. DUMPER WRITES LONGER RECORDS THAN MOUNTR CAN CURRENTLY READ BECAUSE
DUMPER WRITES IN CORE-DUMP MODE, WHILE MOUNTR READS IN INDUSTRY-
COMPATIBLE MODE.
2. WHEN A TAPE DRIVE REPORTS THAT IT HAS FAILED TO READ A TAPE RECORD
BECAUSE IT WAS TOO LONG FOR THE SPECIFIED BUFFER, PHYSIO RETRIES
THE READ OPERATION AS IF IT WERE AN ORDINARY PARITY ERROR.
Solution: MAKE MOUNTR READ THE FIRST RECORD OF THE TAPE IN CORE-DUMP
MODE, CHECK FOR VOL1, AND IF SO, GO BACK AND READ IT IN INDUSTRY-
COMPATIBLE MODE.
TOPS20 Change Order Number 4.2343
Written by: R.ACE 24-Jul-79 16:39:33
Edit checked: NO Document: YES
TCO Tested: NO Maintenance Release: NO
Hardware-related: NO
Program: MOUNTR
Related TCO's:
Related SPR's:
Problem: MOUNTR MESSAGE DOESN'T CONFORM TO OPR COMMAND
Diagnosis: MOUNTR MESSAGE,
"%USE THE UNLOAD COMMAND TO UNLOAD TAPE DRIVES"
SHOULD READ
"%USE THE DISMOUNT TAPE COMMAND TO UNLOAD TAPE DRIVES"
Solution: CHANGE TEXT STRING IN MOUNTR
TOPS20 Change Order Number 4.2346
Written by: R.ACE 26-Jul-79 06:48:14
Edit checked: NO Document: NO
TCO Tested: NO Maintenance Release: NO
Hardware-related: NO
Program: MOUNTR
Related TCO's:
Related SPR's:
Problem: BUGS RELATED TO VOLUME-PROTECTION IN TOPS-20 VOL2 LABEL:
1) PROTECTION SUPPLIED ON MOUNT TAPE COMMAND NOT GETTING PUT INTO
VOL2 LABEL; GARBAGE PUT THERE INSTEAD
2) OWNER DENIED OVERWRITE ACCESS IF <PROTECTION>&<10> = 0
Diagnosis: CODING ERRORS
Solution: FIX ERRORS
TOPS20 Change Order Number 4.2353
Written by: R.ACE 27-Jul-79 13:30:14
Edit checked: NO Document: NO
TCO Tested: NO Maintenance Release: NO
Hardware-related: NO
Program: MOUNTR
Related TCO's:
Related SPR's:
Problem: MOUNTR USES PS:<SYSTEM>DEVICE-STATUS.BIN INSTEAD OF
SYSTEM:DEVICE-STATUS.BIN
Diagnosis: PROGRAMMER ERROR
Solution: CHANGE IT TO SYSTEM:DEVICE-STATUS.BIN
TOPS20 Change Order Number 4.2432
Written by: R.ACE 30-Aug-79 14:40:37
Edit checked: NO Document: NO
TCO Tested: NO Maintenance Release: NO
Hardware-related: NO
Program: MOUNTR
Related TCO's:
Related SPR's:
Problem: BROKEN TAPE HARDWARE CAN YIELD THE FOLLOWING:
AFTER SETTING A TAPE DRIVE UNAVAILABLE, MOUNTR ACKNOWLEDGES THIS,
BUT SUBSEQUENT "SHOW STATUS" COMMANDS SHOW THE DRIVE IS STILL
UNDER MOUNTR'S CONTROL.
Diagnosis: SICK TU45 CAN RETURN BOTH "REWINDING" AND "UNLOADED",
BOTH OF WHICH ARE DUTIFULLY PASSED BY THE MONITOR TO MOUNTR,
CAUSING A BIT OF CONFUSION.
Solution: FIX MOUNTR GMTADS ROUTINE TO CLEAR SJ%REW IF IT SJ%OFS IS SET
TOPS20 Change Order Number 4.2460
Written by: KONEN 12-Sep-79 13:08:43
Edit checked: NO Document: NO
TCO Tested: NO Maintenance Release: NO
Hardware-related: NO
Program: MOUNTR
Related TCO's:
Related SPR's:
Problem: 1. After operator corrects write-locked situation, mount of structure
will not proceed.
2. Drives and channels coming on-line needs more reworking.
Diagnosis: 1. MOUNTR doesn't notice change in status of drive from write-
protected to write-enabled.
2. Channels and drives appearing or disappearing between existing
drives overwrite valid drive information.
Solution: 1. Check for change in status of write-lock bit.
2. Rewrite code to include moving drive information around to fit in
new drives or delete old drives.
TOPS20 Change Order Number 4.2501
Written by: R.ACE 28-Sep-79 17:11:53
Edit checked: NO Document: NO
TCO Tested: NO Maintenance Release: NO
Hardware-related: NO
Program: MOUNTR
Related TCO's:
Related SPR's:
Problem: IF A SCRATCH TAPE WITH VOLID "FOO" IS MOUNTED ON A DRIVE AND
2 MOUNT REQUESTS EXIST, ONE FOR A SCRATCH TAPE AND THE OTHER FOR VOLUME
"FOO", MOUNTR MAY ASSOCIATE THE TAPE WITH THE FORMER REQUEST. IT IS
DESIRABLE THAT MOUNTR GIVE PRIORITY TO REQUESTS FOR SPECIFIC VOLUMES
OVER REQUESTS FOR SCRATCH VOLUMES.
Diagnosis: MOUNTR DOESN'T ENFORCE SUCH A PRIORITY. IT JUST SCANS THE
REQUESTS IN THE ORDER THAT THEY APPEAR IN THE QUEUE.
Solution: IMPLEMENT PRIORITY SCHEME FOR ASSOCIATING SCRATCH VOLUMES
WITH USER REQUESTS.
TOPS20 Change Order Number 4.2505
Written by: R.ACE 2-Oct-79 09:30:00
Edit checked: NO Document: NO
TCO Tested: YES Maintenance Release: NO
Hardware-related: NO
Program: MOUNTR
Related TCO's:
Related SPR's:
Problem: MOUNTR DOESN'T ALWAYS GET THE INSTALLATION NAME OUT OF
SYSTEM:INSTNM.TXT
Diagnosis: MOUNTR GETS A JFN ON SYSTEM:INSTNM.TXT WITHOUT GJ%OLD,
WHICH CAUSES THE FIRST DIRECTORY IN THE LOGICAL NAME DEFINITION
TO BE USED. IF THE FILE IS IN ONE OF THE OTHER DIRECTORIES IN
THE LOGICAL NAME DEF, THE OPENF AFTER THE GTJFN IN GTINAM WILL FAIL.
Solution: USE GJ%OLD WHEN GETTING JFN ON SYSTEM:INSTNM.TXT.
TOPS20 Change Order Number 4.2508
Written by: R.ACE 3-Oct-79 07:25:00
Edit checked: NO Document: NO
TCO Tested: NO Maintenance Release: NO
Hardware-related: NO
Program: MOUNTR
Related TCO's:
Related SPR's:
Problem: MOUNTR CODE SHOULD BE WRITE-PROTECTED
Diagnosis: IT ISN'T
Solution: ADD WRTP ROUTINE TO WRITE-PROTECT MOUNTR'S CODE AT STARTUP
TOPS20 Change Order Number 4.2526
Written by: R.ACE 16-Oct-79 07:04:21
Edit checked: NO Document: YES
TCO Tested: NO Maintenance Release: NO
Hardware-related: NO
Program: MOUNTR
Related TCO's:
Related SPR's:
Problem: "INSUFFICIENT SYSTEM RESOURCES" MESSAGE FROM MOUNTR IS NOT
SUFFICIENTLY SPECIFIC TO LEAD THE RECEIVER TO CONCLUDE THAT THE
PROBLEM ORIGINATED IN MOUNTR (AS OPPOSED TO THE MONITOR).
Diagnosis: NEW ERROR CODE SHOULD HAVE BEEN CREATED FOR THIS PURPOSE.
Solution: CREATE NEW ERROR CODE MREQ31, "INSUFFICIENT MOUNTR RESOURCES",
AND USE IT INSTEAD OF MONX01, "INSUFFICIENT SYSTEM RESOURCES".
TOPS20 Change Order Number 4.2539
Written by: R.ACE 20-Oct-79 14:25:37
Edit checked: NO Document: YES
TCO Tested: NO Maintenance Release: NO
Hardware-related: NO
Program: MOUNTR
Related TCO's:
Related SPR's:
Problem: BY GIVING THE IDENTIFY KEYIN, AN OPERATOR CAN CAUSE A TOPS-20
TAPE THAT IS OWNED BY A USER TO BE TREATED AS A SCRATCH TAPE. IT IS
FELT THAT IT SHOULDN'T BE SO EASY TO DO THIS (I.E., THE OPERATOR SHOULD
HAVE TO GIVE THE SET TAPE INITIALIZE COMMAND TO OPR TO DECLARE A TOPS-20
TAPE TO BE A SCRATCH TAPE).
Diagnosis: MOUNTR WAS DESIGNED AND CODED THAT WAY.
Solution: Change MOUNTR to reject the following cases of the IDENTIFY
command:
1) An attempt to associate a user request for a scratch tape with a
TOPS-20 labeled tape that is owned by a user other than the requestor
2) IDENTIFY MTAn: SCRATCH when MTAn: contains a TOPS-20 tape that is
owned by any user
The error message given by MOUNTR in these cases has the form:
--- Cannot Scratch MTA3: ---
Volume FOO owned by user R.ACE
TOPS20 Change Order Number 4.2560
Written by: R.ACE 1-Nov-79 08:30:20
Edit checked: NO Document: NO
TCO Tested: NO Maintenance Release: NO
Hardware-related: NO
Program: MOUNTR
Related TCO's:
Related SPR's:
Problem: MOUNTR CAN HANG IF A TAPE DRIVE GOES SOUTH.
Diagnosis: ELOGON/ELOGOF ROUTINES DON'T DEFEND AGAINST THE POSSIBILITY
OF THE MTOPR BLOCKING FOR A LONG TIME. THIS CAN HAPPEN IF THE TAPE
DRIVE EXPERIENCES A "PROBLEM ON DEVICE" CONDITION.
Solution: ADD JSYS-TIMER CODE TO ELOGON/ELOGOF ROUTINES.
TOPS20 Change Order Number 4.2578
Written by: KONEN 26-Nov-79 10:15:12
Edit checked: NO Document: NO
TCO Tested: NO Maintenance Release: NO
Hardware-related: NO
Program: MOUNTR
Related TCO's:
Related SPR's:
Problem: MOUNTR grabs bad address sometimes during dismount code
Diagnosis: MOUNTR gets confused on whether or not a stucture is online
Solution: Return to user immediately when structure not found
TOPS20 Change Order Number 4.2587
Written by: R.ACE 3-Dec-79 06:44:07
Edit checked: NO Document: YES
TCO Tested: NO Maintenance Release: NO
Hardware-related: NO
Program: MOUNTR
Routines Affected: AVR
Related TCO's:
Related SPR's:
Problem: MOUNTR AND THE MONITOR DON'T AGREE ON WHAT CONSTITUTES A
LABELED TAPE, FORCING SOME TAPES TO BE READABLE ONLY IN BYPASS MODE.
Diagnosis: MOUNTR CLASSIFIES AS LABELED ANY TAPE WITH A VALID VOL1
LABEL. IF THE TAPE HAS NO HDR1, HOWEVER, THE MONITOR WON'T LET YOU
READ IT AS A LABELED TAPE.
Solution: CHANGE MOUNTR TO MAKE HAVING A HDR1 LABEL A NECESSARY
CONDITION FOR CLASSIFYING A TAPE AS LABELED.
TOPS20 Change Order Number 4.2595
Written by: KONEN 4-Jan-80 09:08:08
Edit checked: NO Document: NO
TCO Tested: NO Maintenance Release: NO
Hardware-related: NO
Program: MOUNTR
Related TCO's:
Related SPR's:
Problem: MOUNTR DIES
Diagnosis: MSTR JSYS failed
Solution: Add ERCAL after JSYS
TOPS20 Change Order Number 4.2605
Written by: KONEN 19-Feb-80 16:02:48
Edit checked: NO Document: NO
TCO Tested: NO Maintenance Release: NO
Hardware-related: NO
Program: MOUNTR
Related TCO's:
Related SPR's:
Problem: Receive "Can't Increment Mount Count" while trying to mount structure
Diagnosis: MOUNTR thinks the structure is already mounted.
Solution: If there is no structure or disk activity in MOUNTR from the time it
is mounted, dismounted by a program other than MOUNTR, and then remounted;
tables are only half set up. This fix sets up all the tables immediately in
MOUNTR when a structure is mounted in MOUNTR.