Re: Ending A "Orphaned" Program

When the nightly process runs at 9 PM there are no other activities going
on. The last person leaves for the day at EXACTLY 5:30 PM. They don't hang
around. Under normal operations there are no uploads or downloads, no ODBC
jobs, no web access. Our code is almost 100% green screen. Our users, who
on average have been here 30 years, like green screen. It works for them.

Thanks for the tip on object lock API's, didn't think about that avenue.
Not sure what you mean by the *MSG statement. Can you elaborate a little?

Thanks.

On Mon, May 7, 2012 at 10:40 AM, <rob@xxxxxxxxx> wrote:

Ending qinter 'may' help. However, in this day and age are 5250 programs
the only programs accessing the data? No upload/downloads? No batch
programs stuck in MSGW? No ODBC? No web access? Perhaps checking the
library for object locks would be better. There are APIs to process
locks.

See also
WRKSYSVAL QDEVRCYACN
CHGJOBD DEVRCYACN(...)
CHGJOB DEVRCYACN(...)
If you're going to use *MSG then have the program process the *MSG
correctly.

See also
WRKSYSVAL QDSCJOBITV


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com