Trailing-Edge
-
PDP-10 Archives
-
bb-d868c-bm_tops20_v4_2020_distr
-
4-documentation/sysjob.tco
There are 21 other files named sysjob.tco in the archive. Click here to see a list.
TOPS20 Change Order Number 4.2120
Written by: DBELL 13-Dec-78 11:22:14
Edit checked: NO Document: NO
TCO Tested: NO Maintenance Release: NO
Hardware-related: NO
Program: SYSJOB
Related TCO's:
Related SPR's: 12134
Problem:
When SYSJOB is running a job on a PTY, and that job logs out, SYSJOB
creates another job on that PTY for free. If logins are not possible
for some reason (full, no logins allowed) then SYSJOB will complain
forever every 1/2 second.
Diagnosis:
Code is stupid.
Solution:
Make code smarter. Change the CHKPIN routine to check for null input
before creating a job, and replace PTYPRM with the new routine PTYINI
which will only try to create a new job occasionally.
TOPS20 Change Order Number 4.2180
Written by: KIRSCHEN 1-Feb-79 12:07:40
Edit checked: NO Document: YES
TCO Tested: NO Maintenance Release: NO
Hardware-related: NO
Program: SYSJOB
Related TCO's:
Related SPR's:
Problem:
There is no way to kill one of several SYSJOB forks all
of which have the same name, e.g. one of several LPTSPLs.
Diagnosis:
The name is not unique to the fork; several forks may have
the same name. A unique handle on the fork is needed.
Solution:
Add the PURGE command. It accepts a fork number as an
argument and will kill that fork. The fork number may
be obtained from the printout from the STATUS command
(it is the first number output for each fork). Thus,
PURGE 4
will kill fork 4.
TOPS20 Change Order Number 4.2502
Written by: R.ACE 1-Oct-79 07:20:12
Edit checked: NO Document: NO
TCO Tested: NO Maintenance Release: NO
Hardware-related: NO
Program: SYSJOB
Related TCO's:
Related SPR's:
Problem: SYSJOB CAN GO INTO A LOOP IF AN INFERIOR FORK DIES, TYPING
"UNEXPECTED INTERRUPT CHANNEL 15, PC=..."
Diagnosis: MISSING ERJMP AFTER JFNS JSYS
Solution: ADD ERJMP TO RECOVER FROM BAD JFNS JSYS