 
| Subject: | |
| From: | |
| Reply To: | |
| Date: | Fri, 22 Sep 1995 03:03:37 EDT |
| Content-Type: | text/plain |
| Parts/Attachments: |
|
|
>I've been subscribed to this list for a while now and appreciate
>the informal discussions. I decided to pose a question regarding
>aborting sessions prior to backups.
>We are running a Series 967 with two a manufacturing application
>written in Fortran and a Financial app in RPG. Bot hare
>maintained by a company called Computer Financial Services in
>Washington state.
>My problem, for at least the past 7 years, has been to come up
>with a guaranteed way to make sure sessions are aborted prior to
>our nightly production backups. In the old days there were
>operators to take care of sessions prior to backing up, but since
>we now have only the 5:00am - 4:00pm coverage, I have to rely on
>a logoff job using MPEX and attempting ABORTJOB's and ABORIO's.
>It does not always get rid of the sessions I want. They either
>end up as ghost sessions or the HP has determined that the
>process state is critical enough not to abort it.
Why do you not configure a CI time-out, so that after a given
inactivity time, the users are logged off?
We have this feature and and an job doing abortjobs/abortio's, and it
does not create problems (except sometimes ghosts sessions, but for the
backup purpose, this is not important as they do not access any files).
[log in to unmask]
Extra X400 information begins:
Originator
Name: MICHEL BUYSE
Org Units: HPDESK
: BXLDSI
: 00
Organisation: XLX400HP
Domain: BE/RTT/SOLVAY
Node.Userid: IBMX400.170254
Message Id: 9526508500802 PXLDSI1.HP.SOLVAY
Importance: Normal
Sent by
Name: MICHEL BUYSE
Org Units: HPDESK
: BXLDSI
: 00
Organisation: XLX400HP
Domain: BE/RTT/SOLVAY
Node.Userid: IBMX400.170254
Recipients
Name: INTERNET INTERNET
Domain: GB/IBMX400/IBMMAIL
Node.Userid: IBMMAIL.INTERNET
|
|
|
