HP3000-L Archives

December 2000, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Willy Schriemer <[log in to unmask]>
Reply To:
Willy Schriemer <[log in to unmask]>
Date:
Thu, 14 Dec 2000 10:25:36 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines)
Hello HP3K experts,

Yesterday we've had an hanging user session on one of our machines. This
session was consuming as much CPU it could get. In Glance/XL we could see
that the prio was 0 and the CPU always greater than 95%. There was no
locking situation on the databases.

The ABORTJOB didn't work. An ALTPROC said that the PIN coudn't be altered.
In glance we saw that JSMAIN wat the only running program for that session.
The session was connected with JINETD and Reflection under Win/NT. The user
killed Reflection with the taskmanager. At this point the looping user was
created.

I've three questions for the HP3K list :


-1- Is there a way to abort a looping session.

-2- Could we prevent this problem with using DTC's and not JINETD.

-3- Is there a way to prevent a looping situation ?

Best regards,

Willy Schriemer
Philips Semiconductors
Nijmegen
The Netherlands

Phone: +31 24 353 2991

ATOM RSS1 RSS2