Re: ENDSBS SBS(QINTER) OPTION(*IMMED) Takes 10 minutes?

Large Joblog(s)?

I have never really liked these timed solutions ( and I have used them ),
but sooner or later this happens. I thought there was a RTVxxx cmd but
don't see it, I may have used in the past something like
Loop1: ENDSBS xxxxx (withwhatever option(s) you want).
MONMSG CPF1054 GOTO CONTINUE
DLYJOB 120
GOTO Loop1
Continue: The rest of the program

As you can tell this isn't the exact syntax...but you get the idea




On Mon, Apr 29, 2013 at 1:58 PM, Sam_L <lennon_s_j@xxxxxxxxxxx> wrote:

In day end processing on Saturday and Sunday we issue ENDSBS
SBS(QINTER) OPTION(*IMMED).
Then we DLYJOB(120)
Then we do STRSBS SBSD(QINTER).
This Saturday evening it took QINTER 10 minutes to end, so the
subsequent STRSBS SBSD(QINTER) failed. Examining recent QINTER job
logs it normally ends in less than 12 seconds.
The job log for Saturday has this escape message:
MCH2401 Escape 40 04/27/13 09:05:50.414607
#iiinsen 000D4C QWTMMDSC QSYS 1577
Thread . . . . : 00000920
Message . . . . : Tried to insert
duplicate key argument in index MISREM
Disconnected jobs.
MISREM is a virtual display , type 3179.
But the job log contained nothing else, except CPF1124 (started) and
CPF1164 (ended.)
Sysval QENDJOBLMT is set to 120 and is the only other thing I've come up
with that might impact ending the subsystem.
We were working overtime on Saturday, so there probably were 5250
sessions in QINTER on Saturday evening.
Any idea why it took so long for QINTER to end?

Thanks
--
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.