RE: CPI2417 Job message queue for xxxxxx/xxxxxx/xxxx has been wrapped. *** Additional Information ***

More on this issue and maybe the answer.

The error on the vendor program was Message text for CPF1056 is:  Subsystem
QINTER already ending with *IMMED option. and this (the already ending deal)
was from the nightly Backup program which ends QINTER to do it's thing. So
it failed to end QINTER.

Here is what is in that CL:

ENDSBS SBS(QINTER)    OPTION(*CNTRLD) DELAY(300)
MONMSG     MSGID(CPF1054)  

So should I just change that to *IMMED and would that do the trick ?

What I had to do this morning was issues an ENDJOBABN against the job that
was "stuck"

Thanks !

Chuck   

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chuck Lewis
Sent: Wednesday, October 12, 2005 8:31 AM
To: 'Midrange Systems Technical Discussion'
Subject: CPI2417 Job message queue for xxxxxx/xxxxxx/xxxx has been wrapped.

Hi Folks,

 

Had a BIG problem during EOD processing early this morning. In a batch job
the command was issued to shut QINTER down and it hung with ONE stinking
job. This job was spitting out CPI2417 Job message queue for
xxxxxx/xxxxxx/xxxx has been wrapped. like CRAZY. So our vendor software
checks for QINTER to be down and tries to end it and for some reason that
bombed.

 

Cut to the chase here, what the heck is going on when one stinking job can
keep QINTER from ending ? This is an iSeries 810 at V5V2.

 

I have looked that the system values and their settings are as follows:

 

QJOBMSGQFL - *NOWRAP

QJOBMSGQMX  - 24

QJOBMSGQSZ  - 16

QJOBMSGQTL - 24

 

What do I do about this ?

 

Thanks in advance !

 

Chuck