Hi Chuck.

I found this. I thought I found it for v5r4 as well. But, have not found
it >again<.


Specifically, in the notes, this is bullet 3:

Make sure that the value for the QINACTITV system value is *NONE. If the
value for QINACTITV is other than *NONE, the workstation will vary off in
the amount of time specified. If you changed the value to *NONE, write the
old value down.

John McKee

On Tue, Apr 1, 2014 at 6:04 PM, CRPence <CRPbottle@xxxxxxxxx> wrote:

On 01-Apr-2014 14:00 -0700, John McKee wrote:
<<SNIP>> If unattended need to be run from the console, somebody
could enter command during Friday and it would take off on Saturday
night. I forgot to add that the inactive time would also need to be
set to *NOMAX and restored. <<SNIP>>

What is the basis for an implication that the system value QINACTITV
"Inactive job time-out" would need to be modified in that scenario? If
the job awaits continuance in the DLYW "Delayed Wait" job status, due to
processing the Delay Job (DLYJOB) command, that does not qualify for an
"inactive" condition for an interactive job.

Regards, Chuck
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page