Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

RSTS/E problem

113 views
Skip to first unread message

vaxorcist

unread,
Dec 8, 2008, 12:08:13 PM12/8/08
to
Hi,

after installing and SYSGENing of RSTS/E V9.6 I get the following
error:

Beginning RSTS/E system startup...
88.12.07 12:10 Installing monitor overlays
88.12.07 12:10 Mounting disks
88.12.07 12:10 Assigning logical names
88.12.07 12:10 Starting error logging
?ERRINT - ?No room for user on device at Line 1265
88.12.07 12:10 Setting system characteristics
07-Dec-88 12:10 PM Installing run-time systems and libraries
07-Dec-88 12:10 PM Setting terminal characteristics
07-Dec-88 12:10 PM Defining system commands
07-Dec-88 12:10 PM Setting printer characteristics
07-Dec-88 12:10 PM Starting spoolers
?Unable to start Print/Batch Services
?No room for additional jobs

Could anyone please give me advice/hints?

Regards,

Ulli

John Santos

unread,
Dec 9, 2008, 1:13:00 AM12/9/08
to

I think you are out of disk space. IIRC, it is also possible in RSTS
to fill a directory, which would give the same error. I think cure
for a full directory is to create the directory with a larger
clustersize, (max of 7 clusters in a directory.) The V9.0 internals
manual says the maximum size of a directory is 112 blocks (7 16-block
clusters), but I think this may have changed in later V9.x releases.
A directory could have a smaller clustersize and hence a smaller
maximum size if the disk cluster size is less than 16, though.
I don't remember if it is possible to change the clustersize of a
directory while preserving its contents. Maybe running the directory
defragger program (whose name escapes me at the moment, REORDR, maybe?)
would help, but perhaps all it does is sort the allocated blockettes in
the directory into a more optimal order, and not actually free up
any space.

V9+ moved lots of stuff from [0,1] and [1,2] to other directories,
so this kind of problem should be much less likely. IIRC, ERRINT
has its own directory for error logs, etc. Used to be in [1,2].

The PBS message might mean you've hit the max job limit (before
even completing startup!) How many jobs did you sysgen for? You
might need more swap space; IIRC, the maximum job limit can't
exceed the available swap files. And if you've enabled I/D space,
you need twice as much swap space.

Is this a real PDP-11 or emulated? (If real, you'll have to
juggle real disk space, clustersizes, swap files, etc., but if it's
an emulated PDP-11, it should be no problem to create larger
directories, swapfiles, etc.)

It's been a very long time!

--
John Santos
Evans Griffiths & Hart, Inc.
781-861-0670 ext 539

Kelvin Smith

unread,
Jan 2, 2009, 2:36:07 PM1/2/09
to

Apologies for not responding sooner. My ISP decided to stop providing
Usenet groups...

I generally concur with John Santos on what's happening. By default, the
error files go into the ERROR$: account, which is [0,3], but they can be
moved to another location if needed. If you look at [1,2]START.LOG,
you'll see a complete log of your startup process, which will tell you
what directory the error log file is being stored in. Also check your
disk free status with the command SYS/D, which will list all the disks
you have and the amount of free space in each.

RSTS requires swap files large enough to hold the maximum number of jobs
you enable. In V9.6, if you've enabled I&D space, each job can be 64KW
in size, which means that the swap files need to total 256 blocks (each
disk block is 256 words) per job.

The command SYS/F will tell you your maximum number of jobs ("Jobmax").
If you log into [1,2] and give the command

$SHOW FILE/SYSTEM

you'll get a list of the swap files installed, and how many jobs they
can handle. Probably you have only a "Swap_file 1:" entry. If you have
sufficient disk space, you can create more swap files, and install them,
so that the number of jobs can be increased. To create a swap file:

$INSTALL/SWAPFILE=s/SIZE=n Dxm:

where s is the swap file number (0-3), n is the size of the new swap
file (which will overwrite any existing swap file of that number, which
is always named SWAPs.SYS in the [0,1] directory, again s meaning the
swap file number), and Dxm: is the disk on which to put the swap file.
So an example would be:

$INSTALL/SWAPFILE=0/SIZE=2560 DU0:

which will create a swap file named [0,1]SWAP0.SYS on drive DU0: that
can hold 10 64K jobs.

To install an existing swap file, simply skip the /SIZE=n switch:

$INSTALL/SWAPFILE=0 DU0:

You'll want to put these commands in the startup command file,
[0,1]START.COM, so they're automatically installed each time you start
up the system.

Note, though, that swapfiles won't increase the Jobmax that you
specified with SYSGEN. If that number is too small, you have to go
through the entire SYSGEN process all over again.

Kelvin Smith
Financial Computer Systems
(remove 1111 for email)

1tim....@gmail.com

unread,
Aug 27, 2015, 8:15:20 PM8/27/15
to
I'm finding myself in the same boat, and no matter what I do, I cannot get JOB MAX above 2.
$ sys/f

General FIP Hung
Buffers Buffers Jobs/Jobmax TTY's Errors
736 467 2/2 0 1

$ sys/d

Disk Structure:
Dsk Open Size Free Clu Err Name Level Comments
DU0 17 311200 241392 77% 8 0 RSTSV9 1.2 Pub, DLW
DU1 0 311200 311024 99% 8 0 DATA 1.2 Pub, DLW
$

$ show file/sys

Swap_file 0: DU0:[0,1]SWAP0 .SYS 16128 blocks (126 jobs at 32K Swap max)
Swap_file 1: DU0:[0,1]SWAP1 .SYS 15872 blocks (124 jobs at 32K Swap max)
Swap_file 2: DU0:[0,1]SWAP .SYS 128 blocks (1 job at 32K Swap max)
Swap_file 3: None

Overlay_file: None
Error_file: None

Network_file: None
$

from Sysgen:

The following questions deal with the
capacity and features of this RSTS/E
system provided at the system manager's
option.

Accept Software defaults ? <N >

Maximum jobs ? <25> 63

Small buffers ? <500> 640

EMT Logging ? <N >

I modified START.COM to mount my data disk and to install the swap0 file.

any help would be appreciated!

John Santos

unread,
Sep 3, 2015, 12:42:45 AM9/3/15
to
In article <2489cf0e-e149-4721...@googlegroups.com>,
1tim....@gmail.com says...
$ set logins/enable or $ set system/logins=63? (It's been a very long
time, but I think the login limit at boot time is 1 or 2 and you have
to increase it after adding the swap files.)
0 new messages