Anyone using batch queue in superlayer functions ?
If so, have you ever experienced with functions running in batch queue always exitting to the previous calling function regardless of what is set in the exit link ?
Here is what I 've got in my function:
|------------------------- Revision Control Numbers -------------------------|
|SuperLayer Revision: 4.000000 Release: 22.000 Function Revision: 6.42000 |
| |
|------------------------------ Link Functions ------------------------------|
|Exit Link < SELPIMPS Error Link< SELPIMPS |
|Security Link< Level : |
| |
|------------------------------ Batch Options -------------------------------|
|Queue ID: y Priority: 1 Release Terminal?: |
+----------------------------------------------------------------------------+
The function never exits to 'SELPIMPS' screen.
Thanks in advance.
Hat

Batch Queue
Started by hath, Dec 03 2004 02:00 AM
8 replies to this topic
#4
Posted 03 December 2004 - 05:56 PM
hath,
Try making the last line of logic in the function an explicit setting of @LFUNCT = SELPIMPS
This will isolate for any potential of @LFUNCT being overwritten. You may also want to prove to yourself that the problem is not the SELIMPS - for some reason - is immediately exitting back to the prior function...
hth,
Joseph
Try making the last line of logic in the function an explicit setting of @LFUNCT = SELPIMPS
This will isolate for any potential of @LFUNCT being overwritten. You may also want to prove to yourself that the problem is not the SELIMPS - for some reason - is immediately exitting back to the prior function...
hth,
Joseph
#5
Posted 04 December 2004 - 01:09 AM
G'Day Hath,
When executing a function that is set to Batch, control is returned to the calling function. Therefore you will need to set @PFUNCT = 'SELPIMPS' to "trick" PRO-IV - memory fails me, but I believe this needs to be done in logic in of the called batch function.
I've got to ask, with a function name like SELPIMPS (Select Pimps ?) is this a brothel management system ?
Regards
Shaun
When executing a function that is set to Batch, control is returned to the calling function. Therefore you will need to set @PFUNCT = 'SELPIMPS' to "trick" PRO-IV - memory fails me, but I believe this needs to be done in logic in of the called batch function.
I've got to ask, with a function name like SELPIMPS (Select Pimps ?) is this a brothel management system ?
Regards
Shaun
PRO-IV free for 385 Days

#6
Posted 05 December 2004 - 11:37 PM
Hi Donald, Queue id can be A-Z, a-z, or 1-9. We heavily use batch queue functions here and almost use up A-Z.
Hi Chris, you 're right. Batch queue function must be an update which is my function.
Hi Joseph, it did try @LFUNCT to reset the next function to execute, but unfortunately it was ignored.
Hi Shaun, similar to your work-out idea. I put a logic in the calling function to check if @PFUNCT is the batch queue function then @LFUNCT to SELPIMPS which is a 'Select Premium Brothel management system'. No, it 's nothing like that Shaun, it 's to do with Super.
Thanks all.
Hath.
Hi Chris, you 're right. Batch queue function must be an update which is my function.
Hi Joseph, it did try @LFUNCT to reset the next function to execute, but unfortunately it was ignored.
Hi Shaun, similar to your work-out idea. I put a logic in the calling function to check if @PFUNCT is the batch queue function then @LFUNCT to SELPIMPS which is a 'Select Premium Brothel management system'. No, it 's nothing like that Shaun, it 's to do with Super.
Thanks all.
Hath.
#7
Posted 06 December 2004 - 01:39 AM
G'Day Hath,
If you're heavily using batch queue functions, can I ask whether you have examples that do work ? If so, is it possible to compare the PRO-IV code generated, and potentially highlight any differences. The current system that I am working on is written via Superlayer and utilises Batch Queue Processing within the application; all of which runs sweetly. I don't mention this out of smugness, merely that we have had no problems with Superlayer creating any "spurious linkage or code" that would affect the performance of Batch Queue Processing.
Excuse me if I'm a little slow on the uptake, but just to clarify to one point, are you talking about linking to SELPIMPS when you queue the function (i.e. after an attempt to execute it), or after the function has been executed in background.
Regards
Shaun
If you're heavily using batch queue functions, can I ask whether you have examples that do work ? If so, is it possible to compare the PRO-IV code generated, and potentially highlight any differences. The current system that I am working on is written via Superlayer and utilises Batch Queue Processing within the application; all of which runs sweetly. I don't mention this out of smugness, merely that we have had no problems with Superlayer creating any "spurious linkage or code" that would affect the performance of Batch Queue Processing.
Excuse me if I'm a little slow on the uptake, but just to clarify to one point, are you talking about linking to SELPIMPS when you queue the function (i.e. after an attempt to execute it), or after the function has been executed in background.
Regards
Shaun
PRO-IV free for 385 Days

#8
Posted 06 December 2004 - 02:37 AM
Hi Shaun,
There is no problem with creating or launching a batch queue function in the background. It 's just that once the batch queue function is completed, the next function to be executed is automatically its calling function, regardless of what is set in the EXIT LINK or ERROR LINK of the batch queue function. It even ignores what is explicitly set in @LFUNCT.
It must be some ProIV system variable which stores the calling function and the batch queue function just links to it once it is completed.
Cherio
Hath.
There is no problem with creating or launching a batch queue function in the background. It 's just that once the batch queue function is completed, the next function to be executed is automatically its calling function, regardless of what is set in the EXIT LINK or ERROR LINK of the batch queue function. It even ignores what is explicitly set in @LFUNCT.
It must be some ProIV system variable which stores the calling function and the batch queue function just links to it once it is completed.
Cherio
Hath.
#9
Posted 06 December 2004 - 04:03 AM
A couple of questions:
What function is the batch queue function going back to?
Are you talking about the initiation of the Batch Queue function, where the parameters get written to the BATCHQUE file, or are you talking about after processing the function?
What function is the batch queue function going back to?
Are you talking about the initiation of the Batch Queue function, where the parameters get written to the BATCHQUE file, or are you talking about after processing the function?
Reply to this topic

0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users