Re: [staf-users] STAX & its JOB QUEUE

[Phil K. <pkl...@us...>]

That's kinda what I expected. So how do I work around that. I can't create 
a STAF handle for a job queue from a STAX job because the Queue service 
does not allow you to specify what queue to receive messages on. The only 
one available for a STAX job is the STAX job handles one. So... How do I 
communicate back to a STAX job that a request made to a processes queue 
has compleated? And still keep the process active. I need to be able to 
interact between the STAX job and the process. What else is available to 
me, or will I need to create somesort of new service for this. Which I can 
do, I'm just trying to use what is already available in the STAX/STAF 
world. 

Phil Klickman(pkl...@us...)  512-838-3919
-----------------------------------
"Complexity exists only in the minds of the bewildered!"
 "The more helpful you make something the less helpful it becomes." 
-----------------------------------





Sharon Lucas/Austin/IBM
02/16/2005 04:59 PM

To
sta...@li...
cc
Phil Klickman/Austin/IBM@IBMUS
Subject
Re: [staf-users] STAX & its JOB QUEUE





You cannot use the STAX job handle's queue as it currently used 
exclusively by the STAX service to continually checking each job handle's 
queue to receive messages that <process> or <stafcmd> has completed.

--------------------------------------------------------------
Sharon Lucas
IBM Austin,   lu...@us...
(512) 838-8347 or Tieline 678-8347




Phil Klickman/Austin/IBM@IBMUS 
Sent by: sta...@li...
02/16/2005 04:44 PM

To
sta...@li...
cc

Subject
[staf-users] STAX & its JOB QUEUE







I'm looking for a work around for the following problem. 

I working on a stax job that starts a process, the executable started by 
this, does a STAFregister so that it can use STAF command including 
processing requests from its QUEUE using the staf queue service. The stax 
job then using the process-action directive then send requests to the 
processes queue using the STAXProcessHandle. This part of the job is 
working correctly request made are being received. The problem come on the 
return leg. Using the information in the Queue's request comming from the 
STAX job, for machine name and requesters return handle I send a respones 
back to the STAX job's queue, but it looks like some part of the STAX job 
is processing the queue, because when I issue  a STAFcmd to the queue 
service to get the responce, it never finds it. 

an easy test for this condition is 

<?xml version="1.0" encoding="UTF-8" standalone="no"?> 
<!DOCTYPE stax SYSTEM "stax.dtd"> 
<stax> 
  <defaultcall function="Main"/> 
  <function name="Main" scope="local">   
     <sequence> 
        <message>'job queue test'</message> 
        <stafcmd> 
           <location>'local'</location> 
           <service>'queue'</service> 
           <request>'queue message test'</request> 
        </stafcmd> 
        <message>'STAFcmd RC: %s Result: %s' % (RC,STAFResult) </message> 
        <stafcmd> 
           <location>'local'</location> 
           <service>'queue'</service> 
           <request>'get wait 60000 '</request> 
        </stafcmd> 
        <message>'STAFcmd RC: %s Result: %s' % (RC,STAFResult) </message> 
     </sequence>   
  </function> 
</stax> 

This should send and return the request from the local STAX job's queue, 
but it will always timeout as something else get it first. 
I have found no refreance to this in the STAX documentation, so I need to 
find a workaround. STAF Queue commands don't let you specify what 
queue's handle to get from, It uses the current  processes handle , in the 
case of the STAX job its handles name is STAX/Job/nnn where 'nnn' is the 
STAXJobID. 

Note: that if you start sending queue service queue requests from a STAF 
command line to the STAX jobs queue handle it will eventually get one. 

Any help would be appreciated. 

Thanks 

Phil Klickman(pkl...@us...)  512-838-3919
-----------------------------------
"Complexity exists only in the minds of the bewildered!"
"The more helpful you make something the less helpful it becomes." 
-----------------------------------