PDP-10 Archive: gal2.rnd from AP-D483B-SB

Trailing-Edge - PDP-10 Archives - AP-D483B-SB_1978 - gal2.rnd
There are no other files named gal2.rnd in the archive.
.FLAG CAP
.LM 0;.RM70;.F;.J;.SP1;.TS5
^^GALAXY.DOC\\ -- ^CHANGES ^FROM ^^V1\\ TO ^^V2\\
.BR
^APRIL 1977
.FG30
^COPYRIGHT (^C) 1977
.BR
^DIGITAL ^EQUIPMENT ^CORPORATION, ^MAYNARD, ^MASS.
.B2
^THIS SOFTWARE IS FURNISHED UNDER A LICENSE FOR USE ONLY ON A SINGLE
COMPUTER SYSTEM AND MAY BE COPIED ONLY WITH THE INCLUSION OF THE ABOVE
COPYRIGHT NOTICE. ^THIS SOFTWARE, OR ANY OTHER COPIES THEREOF, MAY NOT
BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY OTHER PERSON EXCEPT FOR
USE ON SUCH SYSTEM AND TO ONE WHO AGREES TO THESE LICENSE TERMS.
^TITLE TO AND OWNERSHIP OF THE SOFTWARE SHALL AT ALL TIMES REMAIN IN
^^DEC\\.
.B1
^THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE WITHOUT NOTICE
AND SHOULD NOT BE CONSTRUED AS A COMMITMENT BY ^DIGITAL ^EQUIPMENT
^CORPORATION.
.B1
^^DEC\\ ASSUMES NO RESPONSIBILITY FOR THE USE OR RELIABILITY OF ITS
SOFTWARE ON EQUIPMENT WHICH IS NOT SUPPLIED BY ^^DEC\\.
.T <GAL2.DOC
.PG
<GALAXY.DOC -- ^CHANGES FROM <V1 TO <V2
.BR
^APRIL 1977
.B3.LM0
1.0##<SUMMARY
.B1
<GALAXY IS THE ^BATCH AND ^SPOOLING SUBSYSTEM FOR THE <DEC<SYSTEM-10 AND <DECSYSTEM-20.  <GALAXY COMPRISES
ALL THE SOFTWARE (EXCLUDING OPERATING SYSTEMS SOFTWARE) NECESSARY TO DO BATCH PROCESSING AND INPUT
AND OUTPUT SPOOLING AND ALL QUEUE MANAGEMENT AND TASK SCHEDULING REQUIRED FOR THOSE FUNCTIONS.
.B1
<GALAXY RELASE 2 CONSISTS OF THE FOLLOWING PROGRAMS:
.B1.LM0.TS13,25
^PROGRAM	^VERSION	^WHAT IT DOES
.BR
-------	-------	------------
.B1.LM23.TS15,23.I-23
<QUASAR	#2	^CENTRAL QUEUE MANAGER, TASK SCHEDULER, AND <GALAXY SYSTEM CONTROLLER.
.B1.I-23
<BATCON	102	^BATCH JOB PROCESSOR.
.B1.I-23
<LPTSPL	102	^LINEPRINTER OUTPUT SPOOLER (UNSPOOLER).
.B1.I-23
<SPRINT	102	^CARD READER INPUT STACKER/SPOOLER.
.B1.I-23
<QUENCH	#2	^TIMESHARING USERS' INTERFACE TO THE <GALAXY SYSTEM.
.B1.I-23
<SPROUT	#2	^OUTPUT SPOOLER (UNSPOOLER) FOR PAPERTAPE, CARDS, AND PLOTTER (<DEC<SYSTEM-10 ONLY).
.B1.I-23
<LOGOUT	102	<DEC<SYSTEM-10 <LOGOUT PROGRAM.  (^THIS PART OF <GALAXY NOW BUT MAY BE SEPARATED IN THE FUTURE.)
.B1.I-23
<QMANGR	102	^INTERFACE MODULE FOR <FOROTS, <BASIC, ETC.
.B1.LM0
^THE PRIMARY THRUST OF RELEASE 2 WAS TO SUPPORT MOUNTABLE STRUCTURES ON THE <DECSYSTEM-20.  ^THIS
IN ITSELF DID NOT CREATE ANY SUBSTANTIAL EXTERNAL CHANGES BUT A LARGE NUMBER
OF OTHER MINOR CHANGES WERE MADE (MOSTLY COSMETIC) WHICH
ARE DESCRIBED IN THIS DOCUMENT.
.B2.LM0
1.1##^MONITOR ^DEPENDENCE
.B1
^RELEASE 2 OF <GALAXY WILL RUN UNDER THE FOLLOWING MONITORS:
.B1.LM9.I-4
1.##<TOPS10 RELEASE 6.03 AND LATER
.B1.I-4
2.##<TOPS20 RELEASE 2 AND LATER
.PG.B1.LM0
^RELEASE 1 OF <GALAXY WILL CONTINUE TO RUN UNDER <TOPS10 6.03 WITH TWO
PATCHES AS DESCRIBED IN THE 6.03 ^BEWARE (<BWR) FILE.
.B1
^RELEASE 2 OF <TOPS20 REQUIRES RELEASE 2 OF <GALAXY.  ^RELEASE 1, <1A, AND <1B OF <GALAXY WILL NOT RUN UNDER RELEASE 2 OF <TOPS20.
.B3.LM0
2.0##<EXTERNAL <CHANGES
.B1
^THIS SECTION LISTS THE EXTERNAL CHANGES IN <GALAXY RELEASE 2.  ^THE SECTION IS BROKEN
UP INTO 4 SECTIONS - OPERATOR CHANGES, USER CHANGES, OTHER CHANGES,
AND A DESCRIPTION OF SIGNIFICANT CHANGES IN MORE DETAIL.  ^THIS LAST SECTION
IS REFERENCED BY THE RELEVANT ITEMS IN THE FOLLOWING LISTS.  ^THE
FOLLOWING INDICATIONS ARE NOTED WITH EACH CHANGE:
.B1.LM9.I-4
1.##(10)#-#<DEC<SYSTEM-10 ONLY
.B1.I-4
2.##(20)#-#<DECSYSTEM-20 ONLY
.B1.I-4
3.##(<1B)#-#^THE CHANGE WAS IN RELEASE <1A OR <1B NEITHER OF WHICH WERE RELEASED
ON THE <DEC<SYSTEM-10 AND HENCE THE CHANGE IS NEW ON THE 10 BUT ALREADY FIELD-IMAGE ON THE 20.
.B1.LM0
^IF NONE OF THE ABOVE INDICATORS APPEARS THEN THE FEATURE/CHANGE IS NEW ON BOTH
THE 10 AND THE 20 WITH RELEASE 2 OF <GALAXY.
.B2.LM0
2.1##^OPERATOR ^CHANGES
.B1
^THE FOLLOWING CHANGES WILL PRIMARILY AFFECT THE SYSTEM OPERATOR.  ^CHANGES WHICH
AFFECT TIMESHARING AND BATCH USERS ARE IN THE NEXT SUB-SECTION.  ^NOTE THAT
THOSE CHANGES MIGHT ALSO AFFECT THE OPERATOR SINCE HE IS A TIMESHARING USER.
.B1.LM9.I-4
1.##^A NEW COMMAND, <ROUTE, HAS BEEN ADDED TO <BATCON TO ALLOW ALL OUTPUT FOR A GIVEN
STATION TO BE SENT TO A DIFFERENT STATION.  ^SEE SECTION 2.4 FOR DETAILS (10).
.B1.I-4
2.##<LPFORM.INI IS READ WHEN <LPTSPL IS STARTED AND NOT AGAIN, SO CHANGES TO THE
<LPFORM FILE WILL NOT BE NOTICED BY AN <LPTSPL<S WHICH ARE ALREADY RUNNING (<1B).
.B1.I-4
3.##^GIVING THE <FORMS COMMAND WILL FORCE <LPTSPL TO RE-READ <LPFORM.INI.
.B1.I-4
4.##^THE COMMAND <MONITOR HAS BEEN ADDED TO <LPTSPL.  ^THIS
COMMAND CAUSES <LPTSPL TO EXIT IMMEDIATELY REGARDLESS OF WHETHER IT IS IN
THE MIDDLE OF A JOB OR NOT.  ^USING THIS COMMAND IS PREFERABLE TO MERELY
CONTROL-C'INT OUT OF <LPTSPL SINCE IT CAUSES <LPTSPL TO RELEASE ITS INTERLOCK ON THE CURRENT REQUEST
BEFORE EXITING.  ^THIS COMMAND "MUST" BE COMPLETELY SPELLED OUT!
.PG.B1.I-4
5.##^TWO NEW SWITCHES HAVE BEEN ADDED TO <LPFORM.INI, </ALSLP<:NN AND </ALCNT<:NN.  ^THESE
SWITCHES SPECIFY HOW LONG TO SLEEP BETWEEN EACH PRINTING OF THE <ALIGN FILE AND HOW
MANY TIMES TO PRINT THE <ALIGN FILE RESPECTIVELY (10).
.B1.I-4
6.##^A NEW SWITCH HAS BEEN ADDED TO <LPFORM.INI, </VFU, WHICH IS EQUIVALENT TO </TAPE (<1B).
.B1.I-4
7.##^THE <DAVFU IN THE <LP05 PRINTER IS SUPPORTED IN RELEASE 2.  ^SEE SECTION 2.4 FOR DETAILS (<1B).
.B1.I-4
8.##^THE SYNTAX OF THE <SUPPRESS COMMAND IN <LPTSPL HAS CHANGED.  ^THE ARGUMENTS
<JOB AND <FILE ARE NOW KEYWORDS RATHER THAN SWITCHES, SO THE COMMANDS ARE NOW OF THE
FORM "<SUPPRESS <JOB" RATHER THAN "<SUPPRESS </JOB".
.B1.I-4
9.##^THE </C SWITCH TO THE <LPTSPL <REQUEUE COMMAND HAS BEEN REMOVED SINCE </C (CURRENT) IS THE DEFAULT.
.B1.I-5
10.##^LINE SEQUENCE NUMBERS ARE NOW ALLOWED IN <LPFORM.INI.
.B1.I-5
11.##^THE <FORMS COMMAND IN <LPTSPL HAS CHANGED.  ^SEE SECTION 2.4 FOR FURTHER DETAILS.
.B1.I-5
12.##^THE DEVICE OFF-LINE MESSAGE IS NO LONGER TYPED IF THE <LPT GOES OFF-LINE WHILE IDLE (20).
.B1.I-5
13.##^THE <LPTSPL <MSGLVL COMMAND HAS BEEN REMOVED AND REPLACED BY
THE <MESSAGE COMMAND.  ^SEE SECTION 2.4 FOR DETAILS.
.B1.I-5
14.##^THE <SPROUT <MSGLVL COMMAND HAS ALSO BEEN REMOVED.  ^SEE SECTION 2.4 FOR DETAILS (10).
.B1.I-5
15.##<LPTSPL AND <SPROUT DO NOT RELEASE THEIR OUTPUT DEVICES ONCE THEY ARE STARTED (10).
.B1.I-5
16.##^THE FORMAT FOR OPERATOR MESSAGES FROM <BATCON HAS BEEN IMPROVED.  ^SEE SECTION 2.4 FOR DETAILS.
.B2.LM0
2.2##^USER ^CHANGES
.B1.LM9.I-4
1.##^A NEW MESSAGE IS PRINTED OUT ON THE TERMINAL WHEN A QUEUE ENTRY IS CREATED (<1B).
^IT IS OF THE FORM:
.B1.I5
[<LPT:JOB=/SEQ:3/LIMIT:150, 1 ^FILE]
.I7
[<INP:JOB=/SEQ:5/TIME:00:05:00]
.B1.I-4
2.##^THE DEFAULT LIMITS SET ON <LPT JOBS ARE DIFFERENT (SMALLER IN MOST CASES).
.B1.I-4
3.##</PRIO:0 WHICH PREVIOUSLY WAS USED TO PUT A JOB AT THE END OF THE QUEUE,
NOW CAUSES THE JOB TO GET THE DEFAULT PRIORITY.  </PRIO:1 NOW DOES WHAT </PRIO:0 USED TO.
.PG.B1.I-4
4.##^THE </OUTPUT SWITCH ON THE <SUBMIT COMMAND AND THE $<JOB CARD NO LONGER TAKES A
DECIMAL NUMBER AS AN ARGUMENT BUT RATHER ONE OF THE KEYWORD <LOG, <NOLOG, OR <ERROR.  ^SEE
SECTION 2.4 FOR DETAILS (<1B).
.B1.I-4
5.##ALL QUEUE REQUESTS ARE INTERLOCKED ON A PARTICULAR FILE-STRUCTURE.  ^SEE SECTION 2.4 FOR DETAILS (20).
.B1.I-4
6.##^ALL QUEUE REQUESTS ARE SPLIT UP BY FILE-STRUCTURE.  ^SEE SECTION 2.4 FOR MORE DETAILS (20).
.B1.I-4
7.##<LPTSPL NOW PRINTS A "LOG FILE" ON THE TRAILER PAGES SHOWING ALL MAJOR ACTION
TAKEN BY <LPTSPL DURING THE COURSE OF A JOB. (<1B).
.B1.I-4
8.##^THE FORMAT OF THE BANNER PAGES HAVE CHANGED.
.B1.I-4
9.##^THE PAPER-TAPE HEADERS AND TRAILERS HAVE BEEN CLEANED-UP QUITE A BIT IN <SPROUT (10).
.B1.I-5
10.##^A NEW <$JOB CARD SWITCH </JOBNAM:<XXX HAS BEEN ADDED TO <SPRINT.  ^THIS SWITCH
IS EQUIVALENT TO SPECIFYING A JOBNAME (ON THE 10) (<1B).
.B1.I-5
11.##^A BUG WHICH CAUSED <SPRINT TO APPLY THE BATCH JOB'S <AFTER PARAMETER TO
THE <LOG FILE (IF <SPRINT QUEUED UP THE <LOG FILE DUE TO AN ERROR) HAS BEEN FIXED.
.B1.I-5
12.##<SPRINT NOW FLUSHES NULTIPLE <$EOJ CARDS WITHOUT GENERATING AN ERROR.
.B1.I-5
13.##^END-OF-FILE CARDS AGAIN WORK ON REMOTE CARD-READERS (10).
.B1.I-5
14.##^IF A BATCH JOB IS SUBMITTED VIA THE <SUBMIT COMMAND, THE SUBMITTING JOB'S
ACCOUNT STRING IS USED TO LOG THE BATCH JOB IN (20).
.B1.I-5
15.##^CONTROL FILE <TAG<S CAN NOW BE SIX CHARACTERS LONG IN ALL CASES.
^SPECIFICALLY "<CHKPNT 6CHARS" AND "</TAG:6<CHARS" BOTH WORK.
.B1.I-5
16.##^THE </PAPER SWITCH HAS BEEN REMOVED IN <QUENCH (<QUEUE) (10).
I.
.B1.I-5
17.##^THE </PRESERVE SWITCH HAS BEEN ADDED TO <QUENCH.  ^THIS SWITCH IS THE SAME AS
</DISPOSE:PRESERVE.  ^NOW THAT </PRESERVE AND </DELETE EXIST WHICH CORRESPOND TO
THE </DISPOSE SWITCHES, USERS SHOULD BE DISCOURAGED FROM USING THE </DISPOSE SWITCH.
.B1.I-5
18.##^THE FORMAT OF THE QUEUE LISTINGS HAS BEEN CLEANED-UP.
.B1.I-5
19.##</AFTER IS NO LONGER AN HOUR OFF ON THE 20.
.PG.B1.I-5
20.##^THE DEFAULT FILE TYPES (EXTENSIONS) <.LPT AND <.LST HAVE BEEN REMOVED FROM
<QUENCH.  ^SO, <PRINT <FOO WILL NO LONGER FIND <FOO.LST.
.B1.I-5
21.##<.BLI HAS BEEN ADDED TO THE TABLE OF IMPORTANT EXTENSIONS IN <LOGOUT<'S </BATCH ALGORITHM (10).
.B1.I-5
22.##<LOGOUT NOW DELETES NNN???.<TMP WHERE NN IS THE JOB NUMBER (10).
.B1.I-5
23.##^THE <LOG FILE IS "ALWAYS" LOOKED FOR IN THE USERS PATH "ONLY" BY <QUENCH, AND NEVER IN <LIB (10).
.B2.LM0
2.3##^OTHER ^CHANGES
.B1.LM9.I-4
1.##^SIGNIFICANT PERFORMANCE IMPROVEMENT HAS BEEN MADE TO <LPTSPL ON THE 10 BY SIGNIFICANTLY INCREASING
THE SIZE OF ITS LINEPRINTER BUFFERS.  <LPTSPL (10) NOW USES 2 400 (OCTAL) WORD BUFFERS TO
DRIVE THE LINEPRINTER REDUCING BY A FACTOR OF APPROXIMATELY 8 THE NUMBER OF <OUTPUT
<UUO<S DONE.  ^THIS REDUCES <LPTSPL<S <CPU TIME BY 15-30% (DEPENDING INVERSELY WITH SYSTEM LOAD).
.B1.I-4
2.##^RELEASE 2 REQUIRES <FTSFD TO BE ON THE <TOPS10 IN ORDER TO RUN <SPRINT.  ^IF AN
INSTALLATION DOES NOT WANT TO <SFD<S, <LIMLVL CAN BE SET TO 0, BUT
<SPRINT REQUIRES CERTAIN <PATH FEATURES (10).
.B1.I-4
3.##^RELEASE 2 OF <GALAXY DOES NOT REQUIRE <SYSTEM[INFO].
.B1.I-4
4.##^ON THE 10, THE <QUEUE PROGRAM HAS BEEN RENAMED TO <QUENCH.  ^THE SOURCE FILE
IS <QUENCH.MAC.  ^HOWEVER, WHEN THE PROGRAM IS PUT ON THE SYSTEM IT MUST BE CALLED <QUEUE.EXE
SINCE THIS IS WHAT THE MONITOR LOOKS FOR ON THE <PRINT, <SUBMIT, ETC. COMMANDS.
^THE <GALAXY CONTROL FILE WILL CREATE <QUEUE.EXE.
.B2.LM0
2.4##^DETAILS OF ^IMPORTANT ^CHANGES
.B1.LM9.I-4
1.##<BATCON <ROUTE ^COMMAND (10).  ^A COMMAND OF THE FORM:
.B1.I15
<ROUTE STN1 <TO STN2
.B1
HAS BEEN ADDED TO <BATCON.  ^THIS COMMAND CAUSES ALL OUTPUT QUEUED UP FOR STATION
"STN1" TO BE SENT TO "STN2".  ^THE PRIMARY USE OF THIS IS FOR INSTALLATIONS
WITH <DN87<S.  ^SINCE BY DEFAULT ALL USERS WHICH LOG IN OVER A <DN87 ARE LOCATED AT THAT NODE, ALL THEIR
OUTPUT WILL BE QUEUED UP FOR THE <DN87<'S PRINTER (WHICH DOESN'T EXIST).  ^IF
THE <DN87 IS STATION 2 AND THE CENTRAL SITE IS STATION 1,
.B1.I18
<ROUTE 2 <TO 1
.B1
WILL HAVE THE DESIRED EFFECT.
.PG.B1.I-4
2.##^DIRECT ^ACCESS ^VERTICAL ^FORMS ^UNIT (<1B).  ^THE <DAVFU ON THE <LP05 PRINTER
(^DATAPRODUCTS 2270) IS SUPPORTED BY <LPTSPL ON <LP20 AND <LP100 CONTROLLERS.  ^PARTICULAR
<VFU<S ARE ASSOCIATED WITH PARTICULAR FORMS VIA THE </TAPE (OR </VFU) SWITCHES IN <LPFORM.INI.  ^THE
SPECIFICATION OF </VFU:<XXXXXX FOR A FORM WILL CAUSE <LPTSPL TO LOAD <SYS:<XXXXXX<.VFU
INTO THE <DAVFU WHEN THE FORMS ARE MOUNTED.  ^IF NO </VFU SWITCH EXISTS, THE DEFAULT (SAME AS
THE NAME OF STANDARD FORMS) WILL BE USED.  ^THIS IS USUALLY <SYS:NORMAL.VFU.  ^A
PROGRAM CALLED <MAKVFU WILL BE RELEASED TO CREATE <VFU FILES.
.B1.I-4
3.##<LPTSPL <FORMS ^COMMAND.  ^IN PREVIOUS VERSIONS OF <LPTSPL, TYPING "<FORMS <NARROW" TOLD
<LPTSPL THAT <NARROW FORMS WERE IN THE LINEPRINTER.  ^THIS HAD A NUMBER OF RACE
CONDITIONS AND INCONSISTENCIES IN THAT THE COMMAND COULD NOT BE GIVEN WHILE
A JOB WAS BEING PROCESSED AND IF <LPTSPL WAS IDLE, <QUASAR MIGHT VERY WELL HAVE SENT IT A JOB
JUST BEFORE THE OPERATOR TYPED THE COMMAND.  ^TO CLEAR UP THESE PROBLEMS, THE MEANING OF THE FORMS
COMMAND HAS CHANGED.  ^THE COMMAND "<FORMS <NARROW" NOW MERELY HAS <LPTSPL TELL <QUASAR TO SCHEDULE
<NARROW FORMS IF POSSIBLE NEXT TIME A JOB IS SCHEDULED.  ^THE COMMAND DOES NOT
CAUSE ANY CHANGES WHATSOEVER TO <LPTSPL ITSELF.  ^IF A JOB WITH <NARROW FORMS
IS ACTUALLY SCHEDULED, THE "^PLEASE MOUNT" MESSAGE WILL BE TYPED.  ^IF THE NEXT JOB SCHEDULED IS NOT ON
<NARROW FORMS, THE <FORMS COMMAND IS CANCELLED.  ^A NULL ARGUMENT TO THIS COMMAND MEANS <FORMS <NORMAL.
.B1.I-4
4.##<LPTSPL <MESSAGE ^COMMAND.  ^THE <MSGLVL COMMAND HAS BEEN REMOVED AND REPLACED
BY A SOMEWHAT CLEANER MECHANISM, THE <MESSAGE COMMAND.  ^THE <MESSAGE COMMAND HAS A NUMBER OF KEYWORD ARGUMENTS:
<JOB, <FILE, <ERROR, <ALL, <NONE.  ^THE <JOB KEYWORD CAUSES A MESSAGE
TO BE PRINTED AT THE START AND FINISH OF EACH JOB.  ^THE <FILE KEYWORD CAUSES A MESSAGE TO
BE PRINTED AT THE BEGINNING OF EACH FILE, AND THE <ERROR KEYWORD CAUSES ALL FATAL
USER ERRORS TO BE TYPED OUT.  ^SAMPLE <MESSAGE COMMANDS ARE:
.B1.I15
<MESSAGE <JOB
.I15
<MESSAGE <JOB,ERR
.I15
<MESSAGE <NONE
.B1.I-4
5.##<SPROUT <MESSAGE ^COMMAND.  ^THE <MESSAGE COMMAND HAS ALSO BEEN IMPLEMENTED IN <SPROUT.
^HOWEVER, THE <JOB KEYWORD DOESN'T EXIST, JUST <FILE, <ERROR, <ALL, <NONE.
.B1.I-4
6.##^NEW FORMAT FOR <BATCON ^OPERATOR ^MESSAGES.  ^THE FORMAT FOR <BATCON ^OPERATOR MESSAGES
HAS BEEN CLEANED UP SOME.  ^FIRST OF ALL, ALL SUBJOB REQUESTS NOW INCLUDE THE JOB SEQUENCE NUMBER.
.PG.B1
^THE "<BL-$" PROMPT FOR ALL OPERATOR INTERACTION HAS BEEN REMOVED AND MADE MORE UNDERSTANDABLE.
^IN PLACE OF THE "^L" THE ACTUAL SUBJOB NUMBER IS TYPED, AND IN PLACE OF THE ESCAPE ($),
THE WORD "<GO" IS USED.  ^FOR EXAMPLE:
.B1.LM30.NF.NJ
<FOO[10,20] ^SEQ _#3554 ^SUBJOB _#1 ^JOB _#33
<PLEASE <DO <SOMETHING
<OPR--R<ESPOND <B1-GO (OR <KILL)
^WAITING...
.B1.LM9
AND ON THE 20:
.B1.LM30.NF.NJ
<FOO ^USER:<SMITH ^SEQ _#4567 ^SUBJOB _#2 ^JOB _#4
<PLEASE <DO <SOMETHING
<OPR--R<ESPOND <B-2-GO (OR <KILL)
^WAITING...
.B1.LM9.F.J.I-4
7.##</OUTPUT ^SWITCH ON <SUBMIT COMMAND AND <$JOB CARD (<1B).  ^THE </OUTPUT
SWITCH ON THE <SUBMIT COMMAND AND THE <$JOB CARD NOW TAKES ONE OF THE FOLLOWING KEYWORDS AS AN ARGUMENT:
.B1.LM20
<LOG###-#^ALWAYS PRINT THE <LOG FILE (DEFAULT
.BR
<NOLOG#-#^NEVER PRINT THE <LOG FILE
.BR
<ERROR#-#^PRINT THE <LOG IF THE BATCH JOB TERMINATED
.BR
########WITH AN ERROR
.B1.LM9.I-4
8.##^INTERLOCKING OF QUEUE REQUESTS BY STRUCTURE (20).  ^EACH QUEUE REQUEST HAS A DEFAULT
FILE STRUCTURE WITH WHICH IT IS ASSOCIATED.  ^THIS FILE STRUCTURE IS THE FILE-STRUCTURE
CONTAINING THE FIRST FILE IN THE REQUEST.  ^THE REQUEST WILL NOT BE SCHEDULED FOR PROCESSING UNTIL ITS
FILE-STRUCTURE IS MOUNTED.  ^SO, IF A REQUEST IS CREATED TO PRINT <STR:_<SMITH>FILE.TYP, AND STRUCTURE <STR
IS DISMOUNTED BEFORE THE REQUEST IS PROCESSED, THE REQUEST WILL SIT IN THE QUEUE AND WAIT FOR <STR
TO BE REMOUNTED.  ^BATCH JOBS WHICH ARE WAITING FOR A FILE STRUCTURE WILL BE INDICATED IN A QUEUE LISTING
BY THE WORD <STR IN THE <STATUS COLUMN.  ^LINEPRINTER REQUESTS WILL HAVE
A NUMBER SIGN (_#) FOLLOWING THE DEVICE NAME AND THE LISTING WILL HAVE THE FOOTNOTE "_# ^WAITING
FOR FILE-STR TO BE MOUNTED".  ^IF THE </LIST:ALL OPTION IS USED (I.E., <PRINT/LIST:ALL OR <SUBMIT/LIST:ALL) THE STRUCTURE
ASSOCIATED WITH EACH REQUEST WILL BE PRINTED.
.B1.I-4
9.##^SPLITTING QUEUE REQUESTS BY STRUCTURE (20).
.B1.LM15.RM55.C
<NOTE
.B1
^THIS IS AN OPTION THAT CAN BE SELECTED BY REBUILDING THE <GALAXY SYSTEM
AND ANSWERING THE APPROPRIATE <GALGEN QUESTION.
.PG.B1.LM9.RM70
^WHEN A <PRINT REQUEST IS MADE, THE FILES IN THE REQUEST ARE SEGREGATED BY FILE-STRUCTURE,
AND A SEPARATE REQUEST IS MADE FOR EACH FILE-STRUCTURE.  ^THIS FEATURE ARGUMENTS THE INTERLOCK
DESCRIBED IN THE PREVIOUS SECTION.  ^SINCE ALL FILES IN A REQUEST ARE ON THE SAME
STRUCTURE, THE SITUATION WHERE THE FILE-STRUCTURE OF THE FIRST FILE IN THE REQUEST
IS MOUNTED BUT NOT THE FILE-STRUCTURE OF THE SECOND FILE IS AVOIDED.
.B3.LM0
3.0##^^KNOWN BUGS AND DEFICIENCIES\\
.B1.LM9.I-4
1.##</DISPOSE:RENAME (SIMILAR TO THE <MPB FEATURE) DOES NOT EXIST.
.B1.I-4
2.##^THERE IS NO MECHANISM FOR PLACING PARAMETERS ON SPOOLED FILES.
.B1.I-4
3.##^JOBS WITH <AFTER PARAMETERS ARE PRINTED FIRST IN A QUEUE LISTING.
.B3.LM0
4.0##<INSTALLATION <INSTRUCTIONS
.B1
^THE SIMPLEST WAY OF BUILDING A <GALAXY SYSTEM IS TO PLACE ALL NECESSARY FILES ON AN
EMPTY DISK AREA, RUN THE <GALGEN PROGRAM, AND SUBMIT <GALAXY.CTL.  ^THERE ARE A NUMBER
OF UNIVERSAL FILES WHICH ARE DEPENDED UPON BY THE VARIOUS PROGRAMS, AND
THEREFORE ATTEMPTING TO BUILD INDIVIDUAL PROGRAMS MAY BE DIFFICULT.
.B1
^THE ^SYSTEM ^MANAGERS ^GUIDE ON THE 20 AND THE <GALAXY ^OPPERATIONS AND ^SYSTEM
^PROGRAMMING ^PROCEDURES ^MANUAL ON THE 10 (NOTEBOOK _#3) HAVE MORE INFORMATION ON BUILDING <GALAXY.
.B1
^RELEASE 1 OF <GALAXY ON THE 10 DID NOT INCLUDE ANY <.EXE FILES.  ^RELEASE 2
INCLUDES DEFAULT <.EXE FILES FOR ALL <GALAXY COMPONENTS.  ^THESE WERE
CREATED BY TAKING ALL <GALGEN DEFAULTS.  ^THE ONLY DANGER IN USING THESE ARE THAT
THE FILE-STRUCTURE FOR THE MASTER QUEUE FILES IS SPECIFIED TO BE <DSK THEREFORE IF THESE <.EXE
FILES ARE RUN AND THEN A "CUSTOM" BUILD <GALAXY IS RUN, THE PREVIOUS
MASTER QUEUE FILES MAY NOT BE FOUND.
.B1
^BOTH RELEASE 1 AND 2 ON THE 20 INCLUDED <.EXE FILES.
.PG.B3
5.0##<INTERNAL <CHANGES
.B1
^RELEASE 2 OF <GALAXY CONSISTED OF A VERY LARGE NUMBER OF INTERNAL CHANGES.  ^THESE
CHANGES INCLUDE CHANGES TO THE FORMAT OF VARIOUS MESSAGES, SO THAT ANY SOFTWARE WRITTEN
TO COMMUNICATE WITH <QUASAR MIGHT HAVE TO BE MODIFIED.
.B3
6.0##<SUGGESTIONS
.B1
^NONE.
.B3
[^END OF <GAL2.DOC]