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

.;15-MAR-77-GR
\\
.LM0;.RM70;.F;.J;.FLAG CAP;.SP1;.TS5
<OPSER.DOC -- ^CHANGES FROM ^V5^B(73) TO ^V5^C(105)
.BR
^MARCH 1977
.FG30
^COPYRIGHT (^C) 1975,1976,1977
.BR
^DIGITAL ^EQUIPMENT ^CORPORATION, ^MAYNARD, ^MASS.
.B 2
^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.
.B 1
^THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE WITHOUT
NOTICE AND SHOULD NOT BE CONSTRUED AS A COMMITMENT BY ^DIGITAL
^EQUIPMENT ^CORPORATION.
.B 1
<DEC ASSUMES NO RESPONSIBILITY FOR THE USE OR RELIABILITY OF ITS
SOFTWARE ON EQUIPMENT WHICH IS NOT SUPPLIED BY <DEC.
.T <OPR5C.DOC
.PG
<OPSER.DOC -- ^CHANGES FROM ^V5^B(73) TO ^V5^C(105)
.BR
^MARCH 1977
.B3
1.0	<SUMMARY
.B1
^^OPSER\\ VERSION 5^C(105) IS A MAINTAINANCE RELEASE OF ^^OPSER\\S 5(26), 5^A(67), AND 5^B(73).
^IT INCLUDES ALL PUBLISHED PATCHES AS OF THE ^FEBRUARY 1977 ISSUE OF THE ^BULLETIN/^DISPATCH.
.B1
^^OPSER\\ VERSION 5^C(105) RUNS ON ALL SUPPORTED MONITORS.
^IT HAS BEEN EXPLICITLY TESTED UNDER 6.02, 6.02^A, AND 6.03 MONITORS.
.B1
^^OPSER\\ IS DOCUMENTED IN THE ^SOFTWARE ^NOTEBOOKS UNDER:
.B1.I5
1.##^NOTEBOOK 11#-#^^OPSER PROGRAMMING SPECIFICATION\\
.B1.I5
2.##^NOTEBOOK 13#-#^^OPERATOR_'S GUIDE\\
.B1.I5
3.##^NOTEBOOK 3#-#^^MPB OPERATION PROCEDURES\\ (IMPLICIT)
.B3
2.0	<INTERNAL <CHANGES
.B1
^THE LOGIC USED BY ^^OPSER\\ IN ^^INIT\\ING A ^^PTY\\ FOR A SUBJOB HAS BEEN RE-WORKED TO GAIN SPEED ON SYSTEMS THAT HAVE MANY ACTIVE ^^PTY\\S.
^THE OLD METHOD ALSO HAD A BUG IN THAT ^^PTY\\S GREATER THAN ^^PTY77\\ COULD NOT BE ACCESSED BY ^^OPSER\\.
.B1
^IN PREVIOUS VERSIONS OF ^^OPSER\\, THE SYSTEM PROGRAMS ^^DAEMON\\ AND ^^SAVER\\ WERE SPECIAL CASED SO THEY WERE NOT DISTURBED BY ^^KSYS\\.
^HOWEVER, SEVERAL INSTALLATIONS RUN ^^QUASAR\\ DETACHED AND 6.03 ADDED ^^FILDAE\\ TO THIS LIST.
^TO ELIMINATE MORE SPECIAL CHECKS, ^^OPSER\\ WILL NOT DISTURB ANY ^^[OPR]\\ JOB AT ^^KSYS\\.
.B1
^THE COMMAND SCANNER OF <OPSER HAD SEVERAL ERRORS AND WAS ESPECIALLY
SENSITIVE TO BLANKS IN STRANGE PLACES (I.E., ":KSYS_<SP>_<CR>_<LF>").
^THESE HAVE BEEN CORRECTED BY EDITS 101, 103, 104, 105.
.PG
3.0	<KNOWN <BUGS <AND <DEFICIENCIES
.B1
^THERE ARE LIMITATIONS ON THE TYPES (OR CHARACTERISTICS) OF JOBS THAT MAY RECEIVE COMMANDS THROUGH ^^AUTO\\ FILES.
^THESE JOBS ^^MUST\\ USE CONVENTIONS SIMILAR TO THE ONES USED BY ^^BATCON, LPTSPL,\\ OR OTHER SUPPORTED PROGRAMS THAT ARE DESIGNED TO RUN AS SUBJOBS OF ^^OPSER\\.
^THAT IS, THEY MUST ^^HIBER\\NATE ON ^^TTY\\ INPUT OR GO QUICKLY INTO ^^TTY\\ INPUT WAIT.
^^DOC\\ FILES THAT ACCOMPANIED ^^OPSER\\S 5^A(67) AND 5^B(73) EXPLAINED
THE HISTORY AND NATURE OF THE TIMING PROBLEMS THAT CAN ARISE, BUT IT IS
SUFFICIENT TO SAY THAT, ALTHOUGH THE PROBABILITY IS SMALL, IT IS POSSIBLE
THAT LINES READ FROM AN ^^AUTO\\ FILE DIRECTED TO A SUBJOB THAT DOES NOT
FOLLOW THOSE CONVENTIONS, COULD BE LOST.
.B3
4.0	<INSTALLATION <INSTRUCTIONS
.B1
^THERE ARE NO CHANGES TO THE INSTALLATION PROCEDURES FOR ^^OPSER\\ 5^C(105).
.B3
5.0	<INTERNAL <CHANGES
.B1
^THERE ARE NO CHANGES TO <OPSER 5^C(105).
.B3
6.0	<SUGGESTIONS
.B1
^NONE.
.B3
[^END OF <OPR5C.DOC]
.B1
[<OPR5B.DOC IS APPENDED AS AN INTEGRAL PART OF <OPR5C.DOC]
.T <OPR5B.DOC
.PG
<OPSER.DOC -- ^CHANGES FROM 5^A(67) TO ^V5^B(73)
.BR
^JUNE 1975
.B3
1.0	<SUMMARY
.B1
^^OPSER\\ VERSION 5^B(73) IS A MAINTAINANCE RELEASE OF ^^OPSER\\ 5(26) AND 5^A(67).
^IT INCLUDES ALL PUBLISHED PATCHES AS OF THE ^JUNE 15, 1975 ISSUE OF THE ^BULLETIN/^DISPATCH.
.B1
^^OPSER\\ VERSION 5^B(73) RUNS ON ALL SUPPORTED MONITORS.
^IT HAS BEEN EXPLICITLY TESTED UNDER 5.07, 6.01, AND 6.02 MONITORS.
^THIS VERSION FULLY SUPPORTS THE ^^DATE75\\ PROJECT.
.B1
^^OPSER\\ IS DOCUMENTED IN THE ^SOFTWARE ^NOTEBOOKS UNDER:
.B1.I5
1.##^NOTEBOOK 11#-#^^OPSER PROGRAMMING SPECIFICATION\\
.B1.I5
2.##^NOTEBOOK 13#-#^^OPERATOR_'S GUIDE\\
.B1.I5
3.##^NOTEBOOK 3#-#^^MPB OPERATION PROCEDURES\\ (IMPLICIT)
.B3
2.0	<EXTERNAL <CHANGES
.B1
^NONE.
.B3
3.0	<KNOWN <BUGS <AND <DEFICIENCIES
.B1
^AS NOTED BELOW, A CHANGE WAS MADE TO CORRECT A TIMING PROBLEM IN AUTO FILES.
^INITIALLY, THE PROBLEM WAS THAT IF AN AUTO FILE CONTAINED MANY COMMANDS DESTINED FOR A SUBJOB, ^^OPSER\\ WOULD SEND THESE MORE RAPIDLY THAT THE JOB COULD ACCEPT THEM (ESPECIALLY DURING SYSTEM STARTUP OR ON A BUSY SYSTEM).
^BECAUSE THESE COMMANDS ARE "TYPE-AHEAD" ON THE ^^PTY\\, EXCEEDING THE MONITOR ^^PTY\\ BUFFERS CAUSED DATA TO BE DISCARDED AND LOST COMMANDS.
^TO CORRECT THIS, ^^OPSER\\ WOULD WAIT FOR THE SUBJOB TO RETURN TO INPUT WAIT BEFORE SENDING THE NEXT COMMAND FROM THE AUTO FILE.
^WHILE THIS IS A CORRECT SOLUTION, A NEW PROBLEM OCCURRED WHEN A COMMAND IN THE AUTO FILE IS ISSUED FOR A SUBJOB THAT IS NOT WAITING FOR INPUT.
^AN EXAMPLE OF THIS IS:
.B1
^^	L0-MLIMIT 1000
.B1
^AS THE ONLY COMMAND IN THE AUTO FILE.
^ASSUMING ^^L0\\ IS ^^LPTSPL\\, IF IT HAS ALREADY BEEN ^^START\\ED, ^^LPTSPL\\ IS EITHER RUNNING A JOB, OR ^^HIBERNATING\\, BUT IN ANY CASE IS ^^NOT\\ IN INPUT WAIT.
^^OPSER\\ WOULD WAIT FOR THE JOB TO RETURN TO INPUT WAIT WHICH, IN THIS CASE, WOULD NEVER HAPPEN.
^THE FIX TO THIS PROBLEM WAS TO HAVE ^^OPSER\\ CHECK THE JOB'S HIBERNATE ENABLE BITS TO SEE IF THE JOB CAN BE AWOKEN FOR TTY LINE OR CHARACTER INPUT.
^IF SO, AS IN THE CASE OF ^^BATCON, SPRINT, OMOUNT, \\AND ANY OF THE OUTPUT SPOOLERS, SEND THE LINE ON THE THEORY THAT THE JOB WILL ^^SKPINL\\ TO CHECK THE AVAILABLITY OF INPUT.
^HOWEVER, AN ^^AUTO\\ FILE OF THE TYPE:
.BLANK 1
^^	:SLOG
.BREAK
	:DEF X=
.BREAK
	X-GET PROG
.BREAK
	X-CSTART
.BREAK
	X-DETACH\\
.BLANK 1
WOULD NOT BEHAVE PROPERLY IF "^^PROG\\" DID NOT DO THE ^^HIBER\\NATE AS DESCRIBED.
^THE CHANGE MADE IN VERSION 5^B(73) IS TO PLACE A MAXIMUM RETRY COUNT ON THE LENGTH OF TIME ^^OPSER\\ WILL WAIT FOR THE MENTIONED CONDITIONS TO OCCUR.
^IF THIS COUNT EXPIRES, ^^OPSER\\ WILL ATTEMPT TO SEND THE LINE ANYWAY.
^THE NET AFFECT OF THESE CHANGES IS THAT FOR THOSE USES OF ^^AUTO\\ FILES THAT RUN PROGRAMS THAT FUNCTION SIMILARLY TO THE MENTIONED SYSTEM PROGRAMS, ^^OPSER\\ WILL OPERATE CORRECTLY.
^IN THOSE THAT DO NOT, THE ORIGINAL PROBLEM DESCRIBED COULD STILL OCCUR BUT THE "WINDOW" DURING WHICH IT COULD HAPPEN HAS BEEN REDUCED TO A SMALL PROBABILITY.
^THESE CIRCUMSTANCES SHOULD BE KEPT IN MIND WHEN CREATING ^^AUTO\\ FILES AT THE INSTALLATION AND WILL REMAIN A KNOWN RESTRICTION IN THE USAGE OF ^^OPSER\\.
.B3
4.0	<INSTALLATION <INSTRUCTIONS
.B1
^THERE ARE NO CHANGES TO THE INSTALLATION PROCEDURES FOR ^^OPSER\\ 5^B(73).
.B3
5.0	<INTERNAL <CHANGES
.B1
^THE PRIMARY REASON FOR THIS RELEASE IS TO PROVIDE THE ONE NECESSARY CHANGE TO ^^OPSER\\ FOR SUPPORT OF THE ^^GALAXY-10\\ VERSION OF ^^LOGOUT\\.
^THIS CHANGE IS IN THE SYNTAX OF THE ^^KJOB\\ COMMAND STRING AND THE PROPER STRING IS CHOSEN BY CONDITIONAL EXECUTION OF ^^OPSER\\, BASED ON WHETHER THE SYSTEM IS ^^GALAXY-10\\ OR ^^MPB\\.
.B1
^ONE OTHER CHANGE HAS BEEN PROMPTED BY AN ^^SPR\\ AND CONCERNS A TIMING PROBLEM DURING ^^AUTO\\ FILE PROCESSING.
^THIS PROBLEM EXISTED IN VERSION 5(26) AND WAS PARTIALLY CORRECTED BY VERSION 5^A(67).
^PLEASE READ SECTION 3.0 OF THIS DOCUMENT FOR MORE INFORMATION.
.B3
[^END OF <OPR5B.DOC]