I'm shutting down D3 which has been running for 88 days and I'm getting
these messages:
Wrapping up process on line 126
Wrapping up process on line 127
Wrapping up process on line 128
Wrapping up process on line 129
Process is releasing overflow (0)
Process is releasing overflow (0)
Process is releasing overflow (0)
Process is releasing overflow (0)
Process is releasing overflow (0)
Process is releasing overflow (2964)
Process is releasing overflow (-1)
Process is releasing overflow (0)
Process is releasing overflow (0)
Process is releasing overflow (0)
Process is releasing overflow (7312)
Process is releasing overflow (7204)
Process is releasing overflow (5288)
Process is releasing overflow (0)
Process is releasing overflow (-1)
Process is releasing overflow (0)
<snip, many more follow this>

Should I be concerned?
This is on D3 Linux.


Thanks,
Danny

what was running on line 130? Something has grabbed a lot of overflow and
is holding it in "known" storage registers.
The progess won't "die" and so the logoff processor escalates to trying to
kill the process and release all it's overflow.

Make sure there's nothing locked (list-locks (gi)) and if there is clear
them. When's the last time you saved? If this is an NT and you've got all
your data in FSI, don't worry, just turn the computer off. Worst case,
restore the (more or less) unused VME and reboot.

If this is AIX, Linux, Unix or Pro/Plus, do a WHERE and see who's doing what
in those high pibs and make sure the system isn't waiting for something to
happen.

I'm suprised you waited 8 hours, let alone 88 days. I'd say something
wasn't quite right.

Mark Brown


"ddspell-m3" <ddspell (AT) yahoo (DOT) com> wrote

Mark Brown wrote:
It was a phantom process.


We save every night.

I was doing a shutdown and did not have any other sessions whereby I
could have done anything.

I let it run since it appeared to be doing something. It finally
finished with line 129, then it started doing the same thing with line
130. Before shutdown, I had lines through 139, so based on what
happened with line 129, I thought I had about more than 7 hours
remaining for shutdown.

As it turned out, the shutdown finished successfully at 8:35 PM. So it
took 2 hours and 35 minutes to shutdown a D3 Linux system.

Did the reboot, but then the startup script failed. For now the system
is "working" although I can't launch any phantom processes. I working
with my VAR to get this resolved. Back in July we requested a stupid
mod that the VAR delivered. I was reluctant to install it because the
request was so stupid (the users wanted the system to uppercase all the
data). The VAR wrote a routine that added a CALLX to each dictionary
of the files we wanted uppercased. We ran some tests and it worked,
but I was still reluctant to install it. Well, a couple of weeks ago
in a company meeting, I was embarrassed by one of the employees that
asked if this had been done and I said it hadn't. The COO directed me
to install it. I did, but I hadn't rebooted since I installed it (and
as you know, we hadn't rebooted for 88 days). So when the system
started up, it tried to run the case conversion routine for some reason
in the startup process. It couldn't find the routine (since I hadn't
installed it in the DM account -- I didn't think it was warranted
there), so it crashed the startup. I couldn't determine where it was
bombing, so I executed each command of the SYSTEM-COLDSTART macro and
documented where it failed. Some things worked fine. Some did not.
I've passed this onto the VAR and I await their response.

In the meantime, the system is up, but I'm unable to run any phantoms.

I imagine after the VAR cleans this up, we'll reboot again and all will
be good once more. Stupid mod. Stupid users. Oh well...


Regards,
Danny

Thanks for the response.

Found out what was causing the error in the startup. The mod got
applied to the JOBS database because of a Q-pointer from the data
account. Altered the case control procedure and now the JOBS is
updated properly.

However, I still can't launch phantoms. I'm thinking a reboot my clear
the problem from memory.


Regards,
Danny

Do you have any phantoms available? Use BACKGROUND-STATUS to check.


"ddspell-m3" <ddspell (AT) yahoo (DOT) com> wrote

And you guys get offended when I beat up on VARs to take care of their
end-users... *sigh*

Well, OK, if we can't discourage people from applying untried patches
to end-user systems, then we might as well sit back and enjoy the
resulting disasters.

T