--
Peter Hunkeler
>SLIP gets control in 4 environments:
>-- PER
>-- RTM1 (think "FRR")
>-- RTM2 (think "ESTAE")
>-- MEMTERM
How about SLIPs with keyword MSGID=. We've been asked by IBM support in
response to a PMR to set a such SLIP to get a dump when a specific message was
issues. This is how I learned about the MSGID= type SLIP.
Seems to be neither error nor PER type of SLIP. The manual describes SLIP being
called as part of WTO procesing.
>Completion code applies to the last 3. As to the question, in practice, it
>is typically only for some sort of 0C4 (whether PIC 10, PIC 11, PIC 38,
>etc) that routines convert that program check to something else, such as
>"I tried to access storage identified by the caller, but failed, so
>provide a nicer completion code for the user to deal with than the generic
>0C4". It could be any program check, it just happens not to be.
>
>SLIP gets control before recovery routines, so any completion code set by
>the recovery routine is not matchable by a SLIP trap.
Stupid me. I completely misinterpreted the text in the manual.
>I know nothing about SmartRestart, but even LE recommends not using its
>ESPIE path (and wisely so, in general). ESPIE is so restrictive that there
>is no "surely" here.
Are you recommending to run with TRAP(ON,NOSPIE)? The LE Programming Reference
manual still says "IBM highly recommends running with TRAP(ON,SPIE) in all
environments".
--
Peter Hunkeler
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
