× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



The problem is most of these occur in the middle of the night, when user
access is already restricted...so it definitely has to be another batch
job.....the problem is, I have like 300,000 jobs that will run over the
course of the nightjob.





From:
"sjl" <sjl_abc@xxxxxxxxxxx>
To:
midrange-l@xxxxxxxxxxxx
Date:
06/26/2008 01:44 PM
Subject:
Re: Finding a locked file



Doug -

I'm not sure this will help in your situation, but one of my clients had a

problem with interactive users forgetting to sign off from their
interactive
green-screen JDE sessions. Although JDE has a facility for killing
interactive jobs after x minutes of inactivity, they weren't using this
feature.

Quite often one of the purchasing guys would be in the middle of
maintaining
data in the item master or other master files and walk away from his
terminal at the end of the day, or an order-entry clerk would be in the
middle of changing a sales order and leave for the day without saving
it...

These 'orphaned' interactive jobs would occasionally have *record* locks
that interfered with the nightly batch jobs, so I wrote a CL program that
runs on the JDE job scheduler approximately 15 minutes before the batch
processing window starts each night.

1) It does an ENDSBS SBS(QINTER) OPTION(*CNTRLD) to prevent any new
interactive jobs from starting.
2) It then sends a break message to all workstations jobs indicating that
the batch processing jobs are about to start, requesting that they sign
off - then delays for 5 minutes.
3) It sends the same break message again, with another 5-minute delay.
4) It then performs an ENDSBS(QINTER) OPTION(*IMMED) DELAY(0) to kill all
remaining interactive jobs.
5) The nightly batch jobs could then (for the most part) run uninterrupted

without any record-locking problems.

6) At the end of the nightly backup job, the QINTER subsystem was
re-started.


This strategy took care of the majority of record-locking problems that
were
being encountered by the nightly batch jobs.

- sjl




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.