Trailing-Edge
-
PDP-10 Archives
-
bb-bt99e-bb
-
mndany.f05
There are 11 other files named mndany.f05 in the archive. Click here to see a list.
;VERSION 5A COMMENT
;
; THIS WAS EDIT 434 FOR DBMS VERSION 5.
; CHANGES FOR VERSION 5A ARE FLAGGED WITH [V5A] IN THE MARGINAL
; COMMENTS OF THE MAKLIB TEXT.
;
;SYMPTOM:
;
; DBMEND APPEARS TO HAVE DIFFICULTY RECOGNIZING THE BEGINNING
; OF A DISK JOURNAL WHEN THE COMMAND /POSITION 1 IS GIVEN.
;
;DIAGNOSIS:
;
; PAGE 1 OF A DISK JOURNAL IS THE JOURNAL LABEL PAGE AND
; ALSO CONTAINS THE TERMINAL FRAGMENT OF THE LAST JOURNAL
; PAGE AND THEREFORE SHOULD NOT BE REFERENCED BY THE /POS
; COMMAND WITH AN ABSOLUTE ARGUMENT.
;
;CURE:
;
; INSTALL EDIT 532 TO GIVE AN ERROR MESSAGE WHEN THE COMMAND
; /POS 1 HAS BEEN GIVEN FOR A DISK JOURNAL. THE ERROR
; MESSAGE WHICH WE HAVE SELECTED IS "?MNDJPI JOURNAL
; POSITIONED INCORRECTLY AFTER PROCESSING LAST-RELATIVE
; BOUNDARY." THIS MESSAGE IS NOT EXACTLY APPROPRIATE TO
; THE PROBLEM, BUT IT IS NOT POSSIBLE TO INSTALL NEW ERROR
; MESSAGES INTO THE DBMEND REL FILES.
;
;NOTE ***** THIS EDIT APPLIES TO DBMS10 + DBMS20 VERSION 5A
;THE RECOMMENDED FILENAME FOR THIS EDIT IS 532.FIX. THE LINES
;.EDIT THRU .ENDE SHOULD BE TYPED INTO THAT FILE
;
; APPLY THIS EDIT TO MNDANY.REL
;
;THE EDIT CAN BE INSERTED USING THE FOLLOWING COMMANDS:
;
; DBMS-10:
; .R MAKLIB
; *MNDANY.REL=MNDANY.REL,532.FIX/F
;
; .R LINK
; *@DBMEN1
;
; .SAVE DBMEND
;
; DBMS-20:
; @R MAKLIB
; *MNDANY.REL=MNDANY.REL,532.FIX/F
;
; @R LINK
; *@DBMEN2
;
; @SAVE DBMEND
;
.EDIT 532
.NAME JSM
.MODULE DBMEND
.INSERT POSABS+1,REPLACE:1,<JRST DTA.SU+1057> ;[V5A]
;TWO DBMEND COMMANDS PASS THRU THIS PIECE OF CODE
; THEY ARE /POSITION AND /COMPLETE -- BOTH FOR
; ABSOLUTE ARGUMENTS. BEFORE SCAN GIVES CONTROL
; TO THE DBMEND COMMAND IT PUTS THE COMMAND INDEX
; INTO R5, WHICH IS SUPPOSED TO REMAIN UNCHANGED
; THROUGH THE ENTIRE RUN OF THE COMMAND. THE CODE
; AT LOCATION POSABS TESTS WHETHER THE JOURNAL IS
; ON MAGTAPE OR DISK AND GOES TO POSABS+1 ONLY
; FOR DISK JOURNALS.
JRST [CAIE R5,15 ;DOING POSITION COMMAND?
JRST DTA.SU+1057 ;[V5A] NO, LET USER DO /COMPLETE 1 IF
; HE WANTS
HRRZ R1,TMPIDX ;GET CURRENT REQUESTED POSITION
CAIN R1,1 ;IS IT 1?
JRST EL.JPI ; YES -- ERROR
JRST DTA.SU+1057] ;[V5A] NO, OK -- OTHER ERRORS WILL BE
; CAUGHT LATER
.ENDI
.ENDE
;VERSION 5A COMMENT
;
; THIS WAS EDIT 441 IN VERSION 5.
; CHANGES IN THE MAKLIB TEXT OF THE EDIT FOR VERSION 5A WILL
; BE FLAGGED IN THE MARGINAL COMMENTS.
;
;SYMPTOM:
;
; DBMEND WILL PRODUCE THE ERROR MESSAGE "?I/O TO UNASSIGNED
; CHANNEL AT USER PC NNNNNN" WHEN THE /UNLOAD COMMAND IS
; GIVEN WITHOUT PREVIOUSLY SPECIFYING A JOURNAL.
;
;DIAGNOSIS:
;
; DBMEND'S /UNLOAD COMMAND BLYTHELY ASSUMED THAT A JOURNAL
; HAD ALREADY BEEN SPECIFIED.
;
;CURE:
;
; INSTALL DBMS EDIT 533 TO MAKE IT CHECK FOR A JOURNAL. IF
; A JOURNAL HAS NOT BEEN PREVIOUSLY SPECIFIED, /UNLOAD WILL
; ISSUE THE MESSAGE "?MNDJNI JOURNAL NOT YET IDENTIFIED".
;
;NOTE ***** THIS EDIT APPLIES TO DBMS10 + DBMS20 VERSION 5A
;THE RECOMMENDED FILENAME FOR THIS EDIT IS 533.FIX. THE LINES
;.EDIT THRU .ENDE SHOULD BE TYPED INTO THAT FILE
;
; APPLY THIS EDIT TO MNDANY.REL
;
;THE EDIT CAN BE INSERTED USING THE FOLLOWING COMMANDS:
;
;FOR DBMS-10:
;
; .R MAKLIB
; *MNDANY.REL=MNDANY.REL,533.FIX/FIX
;
; .R LINK
; *@DBMEN1
;
; .SAVE DBMEND
;
;FOR DBMS-20:
;
; @R MAKLIB
; *MNDANY.REL=MNDANY.REL,533.FIX/FIX
;
; @R LINK
; *@DBMEN2
;
; @SAVE DBMEND
;
;
;***************************************************************
.EDIT 533
.MODULE DBMEND
.NAME JSM
.INSERT $UNLOAD,AFTER,<PUSHJ P,SC%SAV>
TRNN STATUS,$JR.BIT ;HAS JOURNAL ALREADY BEEN SPECIFIED?
JRST DTA.SU+55 ;NO -- GIVE ?MNDJNI MESSAGE
.ENDI
.ENDE
;VERSION 5A COMMENT
;
; THIS WAS EDIT 442 IN VERSION 5. THE PROBLEM OF EDIT 347 WAS
; RESOLVED IN VERSION 5A, AND SO THERE IS NO NEED TO ACCOMODATE
; THAT EDIT HERE. THIS IS WHY THREE LINES OF CODE HAVE BEEN
; COMMENTED OUT BELOW.
;
;SYMPTOM:
;
; AFTER DOING A /MERGE OPERATION IN DBMEND-10 TO REMOVE AN
; INCOMPLETE TRANSACTION THEN UNLOADING THE JOURNAL WITH THE
; /UNLOAD COMMAND, ANY SUBSEQUENT RUN-UNIT UNDER DBCS TRYING
; TO RE-USE THE JOURNAL WOULD SOMETIMES FAIL ON AN OPEN WITH
; AN ERROR-STATUS CODE OF 0962.
;
;DIAGNOSIS:
;
; THE 0962 ERROR-STATUS CODE WAS REPORTED IF DBMS-10'S
; JOURNAL-IN-UNDEFINED-STATUS WORD WAS SET IN THE JOURNAL
; LABEL PAGE OF A DISK JOURNAL. THIS WORD WAS SET BY /MERGE
; IN ORDER TO SIGNIFY THAT IT WAS CURRENTLY WORKING WITH THE
; JOURNAL IN ORDER TO RECOVER THE DATA BASE. IT SHOULD BE
; CLEARED BY /UNLOAD ON THE COMPLETION OF A SUCCESSFUL MERGE
; IN ORDER TO INDICATE THAT THIS JOURNAL IS NO LONGER ACTIVELY
; INVOLVED IN RESTORING THE DATA BASE AND IS NOW AVAILABLE
; FOR FURTHER WORK UNDER RUN-UNITS USING DBCS.
; THIS SYMPTOM IS ESPECIALLY TROUBLESOME IN CASES WHERE
; SIMULTANEOUS USERS WISH TO SHARE A PRE-ALLOCATED AND
; TRUNCATED JOURNAL AFTER IT HAS BEEN USED BY DBMEND-10 IN
; ORDER TO BACK OUT A PREVIOUS INCOMPLETE TRANSACTION.
; DBMEND-20 HANDLES THIS PROCEDURE DIFFERENTLY.
;
;CURE:
;
; INSTALL EDIT 534 TO CAUSE DBMEND-10 /UNLOAD TO CLEAR THE
; JOURNAL-IN-UNDEFINED-STATE WORD IN THE EVENT OF A SUCCESS-
; FUL /MERGE. THIS EDIT USES BIT 0 IN THE RIGHT HALF OF
; DBMEND'S STATUS REGISTER IN ORDER TO CONVEY INFORMATION
; ABOUT THE JOURNAL STATE FROM /MERGE TO /UNLOAD. IF THIS
; BIT IS SET COMING INTO THE THE EXECUTION OF /UNLOAD, IT
; WILL CLEAR IT AND GIVE THE MESSAGE "?MNDPIF JOURNAL'S
; LABEL PAGE HAS IMPROPER FORMAT". THIS BIT IS NOT OTHER-
; WISE USED BY DBMEND-10 AND IS NOT DEFINED TO IT. A SUB-
; SEQUENT /UNLOAD WILL UNLOAD THE DISK JOURNAL, CLEARING
; THE JOURNAL-IN-UNDEFINED-STATE WORD. IN THIS WAY THE USER
; WILL BE RELIEVED OF THE DISTRESSING PROBLEM OF HAVING HIS
; JOURNAL LABEL IN AN UNDEFINED STATE WHEN HE EXITS FROM
; DBMEND-10.
;
;NOTE ***** THIS EDIT APPLIES TO DBMS10 VERSION 5A ONLY
;THE RECOMMENDED FILENAME FOR THIS EDIT IS 534.FIX. THE LINES
;.EDIT THRU .ENDE SHOULD BE TYPED INTO THAT FILE
;
; APPLY THIS EDIT TO MNDANY.REL
;
;THE EDIT CAN BE INSERTED USING THE FOLLOWING COMMANDS:
;
;FOR DBMS-10:
;
; .R MAKLIB
; *MNDANY.REL=MNDANY.REL,534.FIX/FIX
;
; .R LINK
; *@DBMEN1
;
; .SAVE DBMEND
;
;***************************************************************
.EDIT 534
.MODULE DBMEND
.NAME JSM
.INSERT $MERGE+20,AFTER,<POP P,R1> ;[V5A]
;[REMOVED FOR V5A] PUSH P,R1
;[REMOVED FOR V5A] PUSHJ P,SKECHK
;[REMOVED FOR V5A] POP P,R1
TRO STATUS,400000 ; SET MERGE-IN-PROGRESS BIT
.ENDI
.INSERT MR.EX,BEFORE,<JRST %POPJ1>
TRZ STATUS,400000 ; CLEAR MERGE-IN-PROGRESS BIT
;UPON SUCCESSFUL COMPLETION OF /MERGE
.ENDI
.INSERT DTA.SU+715,AFTER,<SETOM JR.BUF+21>
TRZE STATUS,400000 ; MERGE-IN-PROGRESS BIT STILL SET?
; IF SO, TURN IT OFF IN ANY EVENT
JRST DTA.SU+1006 ; YES -- GIVE ?MNDPIF MESSAGE
SETZM JR.BUF+30 ; NO -- CLEAR JRN-IN-UNDEF-STATE
; WORD BEFORE REWRITING JRN
; LABEL PAGE
.ENDI
.ENDE
;VERSION 5A COMMENT
;
; THIS WAS EDIT 450 IN VERSION 5.
;
;SYMPTOM:
;
; IN CASES WHERE THE /schema COMMAND IS NOT PRECEDED BY /journal,
; DBMEND-10 DOES NOT UNDERSTAND /schema schnam , BUT IT WILL
; UNDERSTAND /schema SCHNAM.
;
;DIAGNOSIS:
;
; FOR THE MODIFIER AFTER THE VERB, DBMEND WASN'T CONVERTING
; LOWER CASE TO UPPER CASE PROPERLY CAUSING COMPARISIONS TO FAIL.
;
;CURE:
;
; APPLY EDIT 535 TO DBMEND-10. EDIT 535 WILL CAUSE LOWER CASE TO
; BE COMPARED PROPERLY TO THE CORRESPONDING UPPER CASE ALPHABETICS
; FOR THIS COMMAND. NOTE, THE SCHEMA NAME WILL BE OUTPUT IN UPPER
; CASE ON YOUR DBMEND LISTINGS.
;
;NOTE ***** THIS EDIT APPLIES TO DBMS-10 VERSION 5A ONLY
;THE RECOMMENDED FILENAME FOR THIS EDIT IS 535.FIX. THE LINES
;.EDIT THRU .ENDE SHOULD BE TYPED INTO THAT FILE
;
; APPLY THIS EDIT TO MNDANY.REL
;
;THE EDIT CAN BE INSERTED USING THE FOLLOWING COMMANDS:
;
; FOR A DBMS-10 SYSTEM...
;
; R MAKLIB
; *MNDANY.REL=MNDANY.REL,DIS535.FIX/F
;
; R LINK
; *@DBMEN1
;
; .SAVE DBMEND
;
;
.EDIT 535
.MODULE DBMEND
.NAME JSM
.INSERT DBMEND+1,REPLACE:1,<MOVE P,DTA.SU+3>
MOVE P,[-STKSIZ+10,,STACK+10] ;GRAB 10 LOCS OFF STACK FOR
; WORK AREA.
.ENDI
.INSERT DTA.SU+701,AFTER,<MOVEM R0,LB.SCL>
MOVEM R1,1016 ;GRAB 2 AC'S TO WORK WITH; STICK THEIR
MOVEM 2,1017 ; CONTENTS IN OPEN LOCS ON STACK.
; ALSO, CAN USE AC0.
MOVNM R0,2 ;USE SCHEMA NAME LENGTH TO MAKE NEGATIVE POINTER
HRLZ R1,2 ; FOR BYTE PROCESSING BELOW.
MOVE 2,[POINT 7,LB.BLK] ;BYTE POINTER FOR SCHEMA NAME
ILDB R0,2 ;GET A BYTE
CAIGE R0,"a" ;IS IT IN RANGE OF a THRU z?
JRST .+5 ; NO -- TOO LOW
CAILE R0,"z"
JRST .+3 ; NO -- TOO HIGH
SUBI R0,40 ; YES -- MAKE IT UPPER CASE.
DPB R0,2 ;PUT IT BACK INTO SCHEMA NAME
AOBJN R1,.-7 ;FINISHED WITH BYTE STRING?
MOVE 2,1017 ;RESTORE AC'S 0 THU 2
MOVE R1,1016
MOVE R0,LB.SCL
.ENDI
.ENDE
;VERSION 5A COMMENT
;
; THIS WAS EDIT 453 IN VERSION 5.
; CHANGES IN THE MAKLIB TEXT OF THE EDIT FOR VERSION 5A WILL
; BE FLAGGED IN THE MARGINAL COMMENTS.
;
;SYMPTOM:
;
; THE DBMEND COMMAND /JOURNAL J*.* GIVES THE ERROR MESSAGE
; "?MNDWCP WILDCARDING IS PROHIBITED", IMMEDIATELY FOLLOWED BY
; THE MESSAGE "?PA1050 ILLEGAL INSTRUCTION AT USER PC 0".
;
;DIAGNOSIS:
;
; AFTER THE ?MNDWCP MESSAGE IS DISPLAYED, THE ERROR-HANDLING
; PROCEDURE DOES A JRST 0 INSTEAD OF A JRST ABORT TO ENTER
; DBMEND'S RECYCLING PROCEDURE AFTER AN ERRONEOUS COMMAND.
;
;CURE:
;
; INSTALL EDIT 536 TO MAKE THE /JOURNAL COMMAND RECYCLE THROUGH
; THE REGULAR RECYCLE ROUTINE AFTER A ?MNDWCP ERROR.
;
;NOTE ***** THIS EDIT APPLIES TO DBMS10 + DBMS20 VERSION 5A
;THE RECOMMENDED FILENAME FOR THIS EDIT IS 536.FIX. THE LINES
;.EDIT THRU .ENDE SHOULD BE TYPED INTO THAT FILE
;
; APPLY THIS EDIT TO MNDANY.REL
;
;THE EDIT CAN BE INSERTED USING THE FOLLOWING COMMANDS:
;
;FOR DBMS-10:
;
; .R MAKLIB
; *MNDANY.REL=MNDANY.REL,536.FIX/FIX
;
; .R LINK
; *@DBMEN1
;
; .SAVE DBMEND
;
;FOR DBMS-20:
;
; @R MAKLIB
; *MNDANY.REL=MNDANY.REL,536.FIX/FIX
;
; @R LINK
; *@DBMEN2
;
; @SAVE DBMEND
;
;
;***************************************************************
.EDIT 536
.MODULE DBMEND
.NAME JSM
.INSERT DTA.SU+725,REPLACE:1,<JRST 0> ;[V5A]
JRST ABORT ;AFTER TYPOUT, GO TO REGULAR ABORT ROUTINE TO
; RECYCLE FOR NEXT COMMAND.
.ENDI
.ENDE
;VERSION 5A COMMENT
;
; THIS WAS EDIT 454 IN VERSION 5.
;
;SYMPTOM:
;
; IF THE DBMEND COMMAND /MERGE IS ISSUED WITHOUT A "BEFORE" OR
; "AFTER" ARGUMENT, THE RESULTING ?SCNSVR MESSAGE HAS GARBAGE
; AT THE END.
;
;DIAGNOSIS:
;
; THE /MERGE ERROR HANDLING PROCEDURE IS NOT PROVIDING A VALID
; ARGUMENT TO SCAN'S ERROR MESSAGE PROCESSOR.
;
;CURE:
;
; INSTALL EDIT 537.
;
;NOTE ***** THIS EDIT APPLIES TO DBMS10 + DBMS20 VERSION 5A
;THE RECOMMENDED FILENAME FOR THIS EDIT IS 537.FIX. THE LINES
;.EDIT THRU .ENDE SHOULD BE TYPED INTO THAT FILE
;
; APPLY THIS EDIT TO MNDANY.REL
;
;THE EDIT CAN BE INSERTED USING THE FOLLOWING COMMANDS:
;
;FOR DBMS-10:
;
; .R MAKLIB
; *MNDANY.REL=MNDANY.REL,537.FIX/FIX
;
; .R LINK
; *@DBMEN1
;
; .SAVE DBMEND
;
;FOR DBMS-20:
;
; @R MAKLIB
; *MNDANY.REL=MNDANY.REL,537.FIX/FIX
;
; @R LINK
; *@DBMEN2
;
; @SAVE DBMEND
;
;
;***************************************************************
.EDIT 537
.NAME JSM
.MODULE DBMEND
.INSERT $MERGE+6,REPLACE:1,<JUMPLE C,E.SVR##>
JUMPG C,.+3 ;ENCOUNTERED THIS ERROR? NO -- GO ON IN MERGE
MOVEI R0,DBHIGH+13 ;YES -- PROVIDE *MERGE PARM ADDRESS
JRST E.SVR## ;AND GO TO SCAN'S ERROR MESSAGE PROCESSOR
.ENDI
.ENDE
;SYMPTOM:
;
; AN ABSTRACT OF A JOURNAL WITH TEXT ENTRIES DOES NOT CORRECTLY PRINT
; ANY TEXT ENTRY WHICH IS LONGER THAN 80 ASCII CHARACTERS.
;
;DIAGNOSIS:
;
; THE ROUTINE WHICH PRODUCES THE MESSAGES FOR SUCCEEDING BLOCKS OF THE
; SAME TEXT ENTRY FORGETS THAT THE RUN-UNIT-ID, WHICH IS NOT PRINTED
; FOR BLOCKS OTHER THAN THE FIRST BLOCK IN THE TEXT, IS PASSED ALONG
; WITH THE TEXT, AND ATTEMTPS TO USE IT INSTEAD OF THE TEXT.
;
;CURE:
;
; INSTALL EDIT 457. THIS WILL CAUSE TEXT BLOCKS OVER 80 ASCII CHARACTERS
; TO BE PRINTED AS MULTIPLE TEXT BLOCKS AND IS A TEMPORARY SOLUTION TO
; THIS PROBLEM.
;
;THE RECOMMENDED FILENAME FOR THIS EDIT IS 552.FIX. THE LINES
;.EDIT THRU .ENDE SHOULD BE TYPED INTO THAT FILE
;
; APPLY THIS EDIT TO MNDANY.REL
;
;THE EDIT CAN BE INSERTED USING THE FOLLOWING COMMANDS:
;
;FOR DBMS-10:
;
; .R MAKLIB
; *MNDANY.REL=MNDANY.REL,552.FIX/FIX
;
; .R LINK
; *@DBMEN1
;
; .SAVE DBMEND
;
;FOR DBMS-20:
;
; @R MAKLIB
; *MNDANY.REL=MNDANY.REL,552.FIX/FIX
;
; @R LINK
; *@DBMEN2
;
; @SAVE DBMEND
;
;
;***************************************************************
.EDIT 552
.NAME CLH
.MODULE DBMEND
.INSERT DTA.SU+262,REPLACE:8,<TLNN 1,340000>
MOVE R0,MNDTEX## ;[552] ASSUME SINGLE BLOCK FOR NOW
.ENDI
.ENDE
;SYMPTOM:
;
; IF THE DBMEND COMMANDS /ABSTRACT, /BUILD, /EXCLUDE, /FORCE
; /JOURNAL, /OPEN, OR /SCHEMA ARE ISSUED WITHOUT AN
; ARGUMENT, THE RESULTING ?SCNSVR MESSAGE HAS GARBAGE
; AT THE END.
;
;DIAGNOSIS:
;
; THE COMMAND ERROR HANDLING PROCEDURES ARE NOT PROVIDING A VALID
; ARGUMENT TO SCAN'S ERROR MESSAGE PROCESSOR.
;
;CURE:
;
; INSTALL EDIT 553.
;
;NOTE ***** THIS EDIT APPLIES TO DBMS10 + DBMS20 VERSION 5
;THE RECOMMENDED FILENAME FOR THIS EDIT IS 553.FIX. THE LINES
;.EDIT THRU .ENDE SHOULD BE TYPED INTO THAT FILE
;
; APPLY THIS EDIT TO MNDANY.REL
;
;THE EDIT CAN BE INSERTED USING THE FOLLOWING COMMANDS:
;
;FOR DBMS-10:
;
; .R MAKLIB
; *MNDANY.REL=MNDANY.REL,553.FIX/FIX
;
; .R LINK
; *@DBMEN1
;
; .SAVE DBMEND
;
;FOR DBMS-20:
;
; @R MAKLIB
; *MNDANY.REL=MNDANY.REL,553.FIX/FIX
;
; @R LINK
; *@DBMEN2
;
; @SAVE DBMEND
;
;
;***************************************************************
.EDIT 553
.NAME CLH
.MODULE DBMEND
.INSERT $ABSTRACT+1,REPLACE:1,<JUMPLE C,E.SVR##>
JUMPG C,.+3 ;[553] NO PARAMETER GIVEN?
MOVEI R0,DBHIGH ;[553] YES, GET ERROR PARAMETER
JRST E.SVR## ;[553] LET SCAN PRINT MESSAGE
.ENDI
.INSERT $BUILD+1,REPLACE:1,<JUMPLE C,E.SVR##>
JUMPG C,.+3 ;[553] NO PARAMETER GIVEN?
MOVEI R0,DBHIGH+1 ;[553] YES, GET ERROR PARAMETER
JRST E.SVR## ;[553] LET SCAN PRINT MESSAGE
.ENDI
.INSERT $CLOSE+1,REPLACE:1,<JUMPLE C,E.SVR##>
JUMPG C,.+3 ;[553] NO PARAMETER GIVEN?
MOVEI R0,DBHIGH+2 ;[553] YES, GET ERROR PARAMETER
JRST E.SVR## ;[553] LET SCAN PRINT MESSAGE
.ENDI
.INSERT $EXCLUDE,AFTER,<PUSHJ 17,SC%SAV>
MOVEI R0,DBHIGH+7 ;[553] GET ERROR PARAMETER, JUST IN CASE
.ENDI
.INSERT $FORCE,AFTER,<PUSHJ 17,SC%SAV>
MOVEI R0,DBHIGH+10 ;[553] GET ERROR PARAMETER, JUST IN CASE
.ENDI
.INSERT $JOURNAL,AFTER,<PUSHJ 17,SC%SAV>
MOVEI R0,DBHIGH+11 ;[553] GET ERROR PARAMETER, JUST IN CASE
.ENDI
.INSERT $OPEN,AFTER,<PUSHJ 17,SC%SAV>
MOVEI R0,DBHIGH+14 ;[553] GET ERROR PARAMETER, JUST IN CASE
.ENDI
.INSERT $SCHEMA+1,REPLACE:1,<JUMPLE C,E.SVR##>
JUMPG C,.+3 ;[553] NO PARAMETER GIVEN?
MOVEI R0,DBHIGH+20 ;[553] YES, GET ERROR PARAMETER
JRST E.SVR## ;[553] LET SCAN PRINT ERROR MESSAGE
.ENDI
.ENDE
;VERSION 5A COMMENT
;
; THIS WAS EDIT 462 IN DBMS-10/20 VERSION 5.
;
;SYMPTOM:
;
; IN DBMEND-10,
; WHEN JOURNALLING IS DONE BE COMMAND, THE DBMEND /START AND /END
; COMMANDS DO NOT ALLOW THE USER TO EFFECTIVELY SPECIFY A PARAMETER
; FOR RUN-UNIT ID.
;
;DIAGNOSIS:
;
; FOR COMMAND JOURNALLING, THE BOUNDARY-CHECKING ROUTINE WAS BY-
; PASSING THE CHECK FOR RUN-UNIT ID. HOWEVER, IN THE CASES WHERE
; THESE COMMANDS ARE GIVEN IN THE FORM "/START LAST" OR "/END LAST"
; THE USER SHOULD NOT BE ALLOWED TO SUPPLY A RUN-UNIT ID, ACCORDING
; TO THE DBMS-10/20 ADMINISTRATORS MANUALS.
;
;CURE:
;
; INSTALL EDIT 555 IN ORDER TO DO THE APPROPRIATE CHECKING.
; DBMS-10 TRANSACTION RECOVERY IS UNAFFECTED BY THIS EDIT.
;
;NOTE ***** THIS EDIT APPLIES TO DBMS10 VERSION 5A ONLY.
;THE CORRESPONDING EDIT FOR DBMS-20 IS NUMBER 554.
;THE RECOMMENDED FILENAME FOR THIS EDIT IS 555.FIX. THE LINES
;.EDIT THRU .ENDE SHOULD BE TYPED INTO THAT FILE
;
; APPLY THIS EDIT TO MNDANY.REL
;
;THE EDIT CAN BE INSERTED USING THE FOLLOWING COMMANDS:
;
;FOR DBMS-10:
;
; .R MAKLIB
; *MNDANY.REL=MNDANY.REL,555.FIX/FIX
;
; .R LINK
; *@DBMEN1
;
; .SAVE DBMEND
;
;***************************************************************
.EDIT 555
.NAME JSM
.MODULE DBMEND
.INSERT DETBOUND+10,REPLACE:1,<JRST DO.RUN>
JRST DO.CID ;GO DO RUN-UNIT ID CHECKING
.ENDI
.INSERT DTA.SU+1637,AFTER,<MOVEM R0,BNDUBR(BND)> ;[V5A]
SKIPGE R0,BNDUBM(BND) ;DOING COMMAND MODE? (IF YES, FLAG = -1)
SKIPL R0,BNDUBX(BND) ;HAVE USER-DEFINED BOUNDARY INDEX?
; (IF NO, FLAG = -1)
JRST .+3 ;BYPASS
SKIPL R0,BNDUBR(BND) ;HAVE USER-DEFINED RUN-UNIT ID?
; (IF NO, FLAG = -1)
JRST DTA.SU+1627 ;[V5A]IF WE GET HERE, THE USER HAS PASSED
;A COMMAND OF THE FORM "/START LAST(N)".
;GIVE ERROR MESSAGE ?MNDIFB
.ENDI
.ENDE