Enter your search terms Submit search form
	Web pdp-10.trailing-edge.com

.TITLE	^^DSKRAT BEWARE FILE
.SPACING 1
.BLANK 3
.CENTER
^^DSKRAT BEWARE FILE
.BLANK 3
I.##\\^REQUIREMENTS FOR ^LOST ^BLOCK ^RECOVERY ^ROUTINE
.LEFT MARGIN 4
.PARAGRAPH 0
\\^IN ORDER FOR THE ^LOST ^BLOCK ^RECOVERY CODE TO BE CALLED THE FOLLOWING
CONDITIONS MUST BE MET.
.LEFT MARGIN 12
.PARAGRAPH -4
1)##\\^BIT 35 OF WORD 17 OF TABLE 11 (^MONITOR ^CONFIGURATION
^TABLE) MUST BE SET. ^IN OTHER WORDS, A "^^SET SCHED 1,3,\\ OR 7
MUST BE IN EFFECT.
.PARAGRAPH -4
2)##^YOU MUST BE THE ONLY JOB RUNNING.
.PARAGRAPH 0
\\^THE FOLLOWING TWO MESSAGES WILL BE OUTPUT ON THE ^^TTY\\ IN EVENT OF
A FAILURE.
.PARAGRAPH 0
% ^^LOST BLOCK RECOVERY WILL NOT BE DONE
.BREAK
% LOST BLOCK RECOVERY PHASE ABORTED
.PARAGRAPH 0
\\FOLLOWED BY ONE OR MORE OF THE FOLLOWING MESSAGES
.NOFILL
.RIGHT MARGIN 100
.SKIP 1
1)##^^GETTAB UUO FAILURE
2)##MORE THAN ONE JOB LOGGED IN
3)##SET SCHEDULING FOR NO MORE LOGINS
4)##YOU ARE NOT A PRIVILEGED JOB
5)##ANOTHER JOB IS RUNNING
6)##CURRENT SCHEDULING MAY ALLOW ANOTHER JOB TO LOG IN
.RIGHT MARGIN 65

.FILL
.LEFT MARGIN 10
.PARAGRAPH 0
\\^THE LAST TWO LINES ARE OUTPUT WHEN THE ^LOST ^BLOCK ^RECOVERY
ROUTINE IS FINALLY CALLED AND A SECOND CHECK IS MADE ON THE SYSTEM
STATUS.
.PARAGRAPH 0
\\^THE FOLLOWING MESSAGES WILL BE OUTPUT UPON INTERNAL ERROR CONDITIONS
IN THE ^^LBR\\ ROUTINE.
.LEFT MARGIN 16
.PARAGRAPH -4
1)##? ^^OPEN FAILURE FOR DEVICE STR
.BREAK
DSKRAT \\COULDN'T ^^OPEN\\ THE DEVICE FOR OUTPUT
.INDENT -4
2)##? ^^ENTER FAILURE FOR DEVICE STR
.BREAK
DSKRAT \\COULDN'T ^^ENTER\\ ONE OF ITS ^^LSTBLK\\ FILES
.INDENT -4
3)##?^^ INPUT FAILURE FOR DEVICE STR
.BREAK
DSKRAT \\COULDN'T READ THE ^^RIB\\ OF THE ^^LSTBLK\\ FILE
IT HAS JUST CREATED.
.INDENT -4
4)##? ^^ERROR IN OUTPUTTING TO LOST BLOCK FILE
.BREAK
DSKRAT \\ ENCOUNTERED AN ERROR WHILE DOING A ^^SUPER USETO\\ TO
ONE OF ITS ^^LSTBLK\\ FILES.
.INDENT -4
5)##? ^^ERROR IN CLOSING LSTBLK FILE
.BREAK
DSKRAT \\COULDN'T ^^CLOSE\\ A ^^LSTBLK\\ FILE.
.TEST PAGE 6
.LEFT MARGIN 4
.PARAGRAPH -4
^^II##PRECAUTIONS AND RECOVERY PROCEDURES
.PARAGRAPH 0
\\^UPON SUCCESSFUL COMPLETION OF ^^DSKRAT\\ AND THE ^^LBR\\
^ROUTINE THE USER SHOULD RUN ^^DSKRAT\\ AGAIN, PREFERABLY BY-PASSING THE
^^LBR\\ CODE. ^THIS MAY BE ACCOMPLISHED BY EITHER RUNNING THE ^^FIELD
IMAGE \\VERSION OF ^^DSKRAT\\ WHICH CURRENTLY DOES NOT HAVE THE ^^LBR\\ ROUTINE OR BY FAILING TO MEET THE ^^LBR\\ REQUIREMENTS FOR
^^LBR \\ENTRY,IE. ^SET SCHEDULING TO 0 OR LOG IN ANOTHER JOB.
\\^BOTH LISTINGS SHOULD THEN BE COMPARED TO DETERMINE IF RECOVERY WAS
TRULY SUCCESSFUL.

.PARAGRAPH 0
\\^SUCCESSFUL RECOVERY WOULD BE INDICATED BY THE FOLLOWING CONDITIONS.
.LEFT MARGIN 16
.PARAGRAPH -4
1)##\\^THERE ARE NO ^LOST ^BLOCKS REMAINING.
.INDENT -4
2)##\\^THERE ARE NO MORE ^MULTIPLY DEFINED CLUSTERS THAN THERE WERE BEFORE.
.INDENT -4
3)##\\^THERE ARE NO MORE ^FREE CLUSTERS THAN THERE WERE BEFORE.
.LEFT MARGIN 12
.PARAGRAPH 0
\\^IF THE ABOVE IS TRUE THE OPERATOR MAY SIMPLY DELETE ^^LSTBLK.*\\.
.PARAGRAPH 0
\\^IN THE EVENT THAT THE ABOVE IS NOT TRUE AN ^^SPR\\ SHOULD
BE SUBMITTED STATING THE PARTICULARS OF THE FAILURE ALONG WITH THE
FOLLOWING:
.NOFILL
.BLANK 1
1)##\\^ANY AVAILABLE ^^TTY\\ OUTPUT.
2)##^BOTH ^^DSKRAT\\ LISTINGS.
3)##^A ^^DEC\\TAPE WITH ANY GENERATED ^^LSTBLK\\ FILES.
.BLANK 3
.CENTER
*****************^^WARNING****************
.SKIP 1
.FILL
\\^IF SEVERE ERRORS ARE INDICATED THE DELETION OF THE ^^LSTBLK\\ FILES
MAY RESULT IN A ^^CRASH\\ AND/OR NECESSITY FOR REFRESHING THE STRUCTURE
INVOLVED.
.BLANK 2
\\^TO "GRACEFULLY" RECOVER OR TO UNDO WHAT HAS BEEN DONE THE
OPERATOR MUST DELETE THE ^^LSTBLK\\ FILES VIA A ^^SUPER-USETO.
\\^IT IS SUGGESTED THAT THE PROGRAM ^^DELFIL\\ BE USED WITH THE FOLLOWING
COMMAND LINE:
.BREAK
^^*STR:LSTBLK.EXT/S