Alfredo writes after Jeff on the problem of forking, and the 3000 sometimes
having a problem in this area...

> > > vi: cannot fork: Resource busy, try again
> > > vi: Internal error: j_close: no processes
> > >
> > > what corrective action should we take?
> >
> >Defrag your system volume set, this is a long-standing issue/problem
> >with fork().  You must have "lots" of contiguous free space
> available to
> >transient space on each and every system volume.
>
> Good point.  Now, could CSY please make the error message(s) more
> precise so we can know WHICH particular resource is "busy" and how we
> can "liberate" it?  (See Jeff's note above for a specific solution
> for this specific case.)
>
> Or is this type of generic message a generic Unix/Posix thing that
> admits no gentle HP3000-like treatment right at the source of the
> problem?

Once in the shell, you're in POSIX-land (Unix-land?).  We wanted "open-ness" -
this is the price of entry (unfortunately) - you gotta know the commands, and
the error messages are meant strictly for engineers - thus it is written in the
Book of Unix (Chapter 1, verse 23) :)

Later,
Joe