If your macro completes and you restart it from the THE command line, then
yes, the next time you invoke it the current queue will the be SESSION
queue. That is a new Rexx program invocation and it defaults to SESSION.
Rick
On Sun, Jul 6, 2014 at 1:48 PM, Les Koehler <vmr...@tampabay.rr.com> wrote:
> Ok, but that's what DOSTACK.THE does, as I showed earlier:
>
> Test for THE queue and if not set then set it and examine all the lines
> in it. THE commands or macros get executed, other lines get restacked.
>
> SET Session queue and do the same as above.
>
> SET THE queue as the default and exit.
>
> When I run my macro, the default has been reset back to SESSION! If this
> is what is supposed to happen, that means that I can't centrally manage
> queues, right? Instead, each and every macro must SET THE in order to
> stack data for another macro, and that macro must do the same thing in
> order to read the stacked data. Have I got it right?
>
> Les
>
> On 7/6/2014 6:07 AM, Rick McGuire wrote:
> > No, the named queue persists. The the only thing that resets is the
> > SESSION queue and which queue the program reads and writes to when it
> > starts up. That is always the session queue. If you wish to access the
> > data in the THE queue, you just need to issue an RXQUEUE SET operation to
> > to switch the location. Or alternatively, use an Rexxqueue object to
> work
> > with that queue.
> >
> > Rick
> >
> >
> > On Sun, Jul 6, 2014 at 12:54 AM, Les Koehler <vmr...@tampabay.rr.com>
> wrote:
> >
> >> I think I'm missing something! When my THESTACK.REX launches THE, does
> >> it immediately get control back and run to termination, thus destroying
> >> the named THE rxqueue?
> >>
> >> If that is true, then how can this statement from the doc be true?:
> >>
> >> ---- clip ----
> >>
> >> "Named queues prevent different Rexx programs that are running in a
> >> single session from interfering with each other. They allow Rexx
> >> programs running in different sessions to synchronize execution and pass
> >> data."
> >>
> >> ---- eclip -----
> >>
> >> So how am I supposed to do this if the THE queue doesn't persist so I
> >> can keep it data separate from some other arbitrary process that might
> >> use SESSION?
> >>
> >> Les
> >>
> >> On 7/5/2014 7:13 PM, Rick McGuire wrote:
> >>> The queue set lasts as long as the top Rexx program in the execution
> >> chain
> >>> is active. So once you return to the THE command line, the next macro
> >> you
> >>> run starts off with the default queue. Note that the queue you create,
> >> as
> >>> well as the data within the queue, will persist. If you set back to
> that
> >>> queue name you will find the lines. This does not apply for the
> SESSION
> >>> queue, which is created anew each time a Rexx environment is created.
> >>>
> >>> Rick
> >>>
> >>>
> >>> On Sat, Jul 5, 2014 at 6:33 PM, Les Koehler <vmr...@tampabay.rr.com>
> >> wrote:
> >>>
> >>>> My thestack.rex is executed by linesize.rex from the command window
> and
> >>>> does:
> >>>> --- clip ---
> >>>> x=rxqueue('Delete','THE')
> >>>> the=rxqueue('CREATE','THE')
> >>>> old=rxqueue('SET','THE')
> >>>> call directory 'C:\MyTHEstuff'
> >>>> parse arg file
> >>>> If pos(';',file)>0 then do
> >>>> parse arg file ';' remainder
> >>>> do while pos(';',remainder)>0
> >>>> parse var remainder more ';' remainder
> >>>> queue more
> >>>> End
> >>>> if remainder\='' then queue remainder
> >>>> End
> >>>> "C:\THE\THEc.exe -a stack_active" , /* Set the DOSTACK? eDITV flag */
> >>>> "-p c:\mythestuff\profile.the" file
> >>>> --- eclip ---
> >>>>
> >>>> to get THE started with a stack. The last thing done by profile.the is
> >>>> DOSTACK.THE, the pertinent part is:
> >>>>
> >>>> ---clip---
> >>>> oldq=rxqueue('Get')
> >>>> 'msg On entry, the qname is:' oldq
> >>>> If oldq\='THE' Then Do
> >>>> Call rxqueue 'SET','THE'
> >>>> 'msg So it has been set to: THE'
> >>>> End
> >>>> 'msg Anything there?'
> >>>> Call doq 'THE'
> >>>> Call rxqueue 'SET','SESSION'
> >>>> 'msg How about in' rxqueue('Get')
> >>>> Call doq 'SESSION'
> >>>> Call rxqueue 'SET','THE'
> >>>> 'msg qname set back to:' rxqueue('Get')
> >>>> ---eclip---
> >>>>
> >>>> and the stacked commands get executed by *dostack* from the THE qname
> as
> >>>> intended. However, further stack testing from the THE command line
> >>>> indicates that the THE queuename has been set back to SESSION!
> >>>> Is this working as designed? The documentation doesn't give any hint
> of
> >>>> this behavior :-(
> >>>>
> >>>> Les
> >>>>
> >>>>
> >>>>
> >>
> ------------------------------------------------------------------------------
> >>>> Open source business process management suite built on Java and
> Eclipse
> >>>> Turn processes into business applications with Bonita BPM Community
> >> Edition
> >>>> Quickly connect people, data, and systems into organized workflows
> >>>> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> >>>> http://p.sf.net/sfu/Bonitasoft
> >>>> _______________________________________________
> >>>> Oorexx-users mailing list
> >>>> Oorexx-users@lists.sourceforge.net
> >>>> https://lists.sourceforge.net/lists/listinfo/oorexx-users
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>
> ------------------------------------------------------------------------------
> >>> Open source business process management suite built on Java and Eclipse
> >>> Turn processes into business applications with Bonita BPM Community
> >> Edition
> >>> Quickly connect people, data, and systems into organized workflows
> >>> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> >>> http://p.sf.net/sfu/Bonitasoft
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Oorexx-users mailing list
> >>> Oorexx-users@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/oorexx-users
> >>>
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> Open source business process management suite built on Java and Eclipse
> >> Turn processes into business applications with Bonita BPM Community
> Edition
> >> Quickly connect people, data, and systems into organized workflows
> >> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> >> http://p.sf.net/sfu/Bonitasoft
> >> _______________________________________________
> >> Oorexx-users mailing list
> >> Oorexx-users@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/oorexx-users
> >>
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > Open source business process management suite built on Java and Eclipse
> > Turn processes into business applications with Bonita BPM Community
> Edition
> > Quickly connect people, data, and systems into organized workflows
> > Winner of BOSSIE, CODIE, OW2 and Gartner awards
> > http://p.sf.net/sfu/Bonitasoft
> >
> >
> >
> > _______________________________________________
> > Oorexx-users mailing list
> > Oorexx-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/oorexx-users
> >
>
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> Oorexx-users mailing list
> Oorexx-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-users
>
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
