IMS terminology dates back to 1968 and abend generally means "abnormal end
of the IMS unit of work" rather than an MVS ABEND. For continuous
operation reasons IMS avoids issuing ABEND except when absolutely necessary
for data integrity. The IMS pseudo-abend is strictly an internal IMS
function with no involvement by MVS, and can result in TCB termination done
by IMS (and re-attach) but not always ... it varies by region type and
environment The OP was wondering if the normal task termination RESMGR can
be relied upon, and when the IMS pseudo-abend results in TCB termination it
can. There isn't any documentation of when pseudo-abend results in TCB
termination, my experience is that most do but some don't. IMS has a
multiple TCB task structure in the dependent region to handle most
termination conditions without losing the dependent region or unit of
work. Over the decades the number of different IMS region types and
environments has proliferated with differing workflow, making pseudo-abends
more complex or at least differentiated.
On Wed, Jan 20, 2021 at 2:17 AM Peter Relson <rel...@us.ibm.com> wrote:
> Simply put, there is no MVS or z/OS concept of a "pseudo abend" beyond
> some internal RTM processing. I can see that IMS uses this term but it has
> no meaning to z/OS itself. Within a CommServer book there is mention of
> "pseudo abend" within IMS saying "Under certain situations IMS
> applications cannot complete. When such a condition occurs, IMS abnormally
> ends the MPR with a status code (such as U0777) and reschedules it.". I
> don't know how "abnormally end...with a status code" relates to "abend".
> Within an IMS book, it does say that a pseudoabend does not result in the
> detecting module issuing an abend and some subsequent module "indicates a
> dependent-region abend" ("indicates" should not, to my mind, equate to
> "issues", but I have no idea what IMS does)
>
> Task termination resmgrs get control when the task terminates, whether
> normally or abnormally. So if "ends the MPR" or "indicates a
> dependent-region abend" results in a task termination, a resmgr for that
> task will get control.
>
> A task terminates upon an SVC D (when no recovery routine retries).
> Period. That SVC D might be issued by a user (such as the ABEND macro) or
> by the system itself (for example, as part of CALLRTM processing when
> transitioning from RTM1 (FRRs) to RTM2 (ESTAE-type) or when the last RB of
> a task returns to the system).
>
> Thus:
> a task termination resgmr will never get control if the recovery routine
> retries;
> a task termination resmgr (let alone an ESTAE-type recovery routine) will
> get control only if an SVC D occurs.
>
> Peter Relson
> z/OS Core Technology Design
>
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
