RE: Cancelling a program in a program stack

Mello Simon. (isn't that how it goes)

I've dumped the PASA and all related structures but it doesn't appear
that the invocation pointers are materializable. What's curious is that
many MI instructions take a jobs' invocation pointer as a parameter but
I can't find any way to get access to an invocation stacks' pointer
list. Perhaps I do need to get a more updated Function Ref Manual but my
need for this utility has dissipated - it was resurrected as an
interesting (futile) exercise when the topic arose.

Thanks again
Tim 

> -----Original Message-----
> From: Simon Coulter [SMTP:shc@flybynight.com.au]
> Sent: Tuesday, April 27, 1999 3:53 AM
> To:   MIDRANGE-L@midrange.com
> Subject:      RE: Cancelling a program in a program stack
> 
> 
> Hello Tim,
> 
> Firstly get a current copy of the Functional Reference Manual.  There
> have been some new 
> instructions added to support ILE progams and these can return more
> information.
> 
> Some information from my archives you may find useful:
> 
>       MATACTAT                Materialize Activation Attributes
>       MATINV            Materialize Invocation
>       MATINVAT          Materialize Invocation Attributes
>       MATINVE           Materialize Invocation Entry
>       MATINVS           Materialize Invocation Stack
> 
> I don't know the entire history, but:
>       MATINV came first (on S/38), but was slow for some uses
>       MATINVE came later, but is only supported in OPM programs
>       MATINVS came around the time of MATINVE, when S/38 added the
> option to not update
>               PASA stack headers
>       MATINVAT was added for ILE support
> 
> I think the instruction you need is MATINVAT but I don't have any
> readily available 
> documentation to verify that.
> 
> Also check the ILE C/C++ MI Library Reference.  It has information for
> the MATACTAT and 
> MATINVAT instructions.  The templates should be found in QSYSINC.
> 
> Since the invocation stack is part of the PASA you may be able to use
> MATPRATR with option 
> X'1D' to get a pointer to the PASA and then explore the structure.
> 
> Sorry I can't provide more information.
> 
> Regards,
> Simon Coulter.
> 
> «»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
> «» FlyByNight Software         AS/400 Technical Specialists       «»
> «» Eclipse the competition - run your business on an IBM AS/400.  «»
> «»                                                                «»
> «» Phone: +61 3 9419 0175      Mobile: +61 0411 091 400           «»
> «» Fax:   +61 3 9419 0175      mailto: shc@flybynight.com.au      «»
> «»                                                                «»
> «» Windoze should not be open at Warp speed.                      «»
> «»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
> //--- forwarded letter
> -------------------------------------------------------
> > X-Mailer: Internet Mail Service (5.5.1960.3)
> > Date: Thu, 15 Apr 99 18:44:32 -0400
> > From: "Tim McCarthy" <TimM@softwarejungle.com>
> > To: "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>
> > Reply-To: MIDRANGE-L@midrange.com
> > Subject: RE: Cancelling a program in a program stack
> 
> > 
> > This topic raised a question I had a while back and perhaps an MI
> hacker
> > out there could help. I'd like to be able to signal an exception to
> > another process (thus the topic) but SIGEXCP requires the invocation
> > pointer for the process. I've tried to get access to the invocation
> > level pointers on a job's stack but they're well hidden (I've looked
> > really hard). According to my (old) MI manual (V2R3) the relevant
> > materialize instruction (MATINVS) doesn't provide this info. Has
> this by
> > any chance been added in a later version?  
> > 
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---