Re: can't kill a dataq program -- MIDRANGE-L

Mike

Be careful about the recommendation to use ENDJOBABN - this has a direct effect on the next IPL - check the help text, maybe.

Since this is in development, you could maybe delete the program object for now. If you were to create a changed version, the original might still be in use, because of how replaced objects work.

Deleting the program - or even the DTAQ - would cause the job to end in error - no problem in this case, maybe.

HTH
Vern

On 3/7/2012 11:40 AM, Smith, Mike wrote:

The only reason I was ending the job manually, is because I'm just getting this written and trying to determine if my basic process works.
I hadn't coded a STOP entry process yet, so I tried to end manually.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jorge Merino
Sent: Wednesday, March 07, 2012 12:06 PM
To: Midrange Systems Technical Discussion
Subject: RE: can't kill a dataq program

If the program has not ended in 10 minutes, you can use ENDJOBABN

But, I was wondering why you do 'end job' manually.

If you are already using DataQueues and QRCVDTAQ API, wouldn't it be easier to create another program to send a '*STOP' entry to the DataQ and have your program to finalize upon reading the DataQ entry? That would have a cleaner program end.

jmerinoh

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Smith, Mike
Sent: Wednesday, March 07, 2012 9:06 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: can't kill a dataq program

4 with *immed.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jorge Merino
Sent: Wednesday, March 07, 2012 11:04 AM
To: Midrange Systems Technical Discussion
Subject: RE: can't kill a dataq program

How are you performing the 'end job' ?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Smith, Mike
Sent: Wednesday, March 07, 2012 8:51 AM
To: 'Midrange Systems Technical Discussion'
Subject: can't kill a dataq program

This might be more appropriate in the rpg list, but since I can't seem to kill my job I'll start here.

I'm trying to test some rpg programs that send and receive from a dataq.

The premise of the program(Program_A) is that when the dataq receives an entry it calls another program(Program_B).
This program(Program_B) checks to see if the order has printed. If it has, then return to Program_A.
If it hasn't printed then check elapsed time. If it hasn't met the threshold, then wait 15 seconds and put the order back in the dataq and return to Program_A
If it has reached the threshold, then send emails to appropriate people and return to Program_A.

Program_A is submitted to QBATCH and has a wait time of -1 on the QRCVDTAQ API.

I have a interactive program that sends entries to the dataq.

So testing,

I submit the receiving program. I perform a end job and the program ends. ( I have not sent anything to the dataq at this point)

I submit the receiving program again. Then I execute the interactive program to send data to the dataq.

It seems to being doing what I want so far(in limited testing).

Now I perform a end job but the program won't end.
I have repeated this scenario a couple of times and have to perform an IPL to get rid of this job.
NOTICE: This message, including any attachment, is intended as a confidential and privileged communication. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this message.
--
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 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.

NOTICE: This message, including any attachment, is intended as a confidential and privileged communication. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this message.
--
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 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.

NOTICE: This message, including any attachment, is intended as a confidential and privileged communication. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this message.