Re: MVS RESMGR exit

2021-01-19 Thread Attila Fogarasi
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  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


Re: MVS RESMGR exit

2021-01-19 Thread Peter Relson
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


Re: MVS RESMGR exit

2021-01-18 Thread Binyamin Dissen
On Mon, 18 Jan 2021 15:51:51 -0500 Gary Weinhold  wrote:

:>Excuse me for asking this question here, but I can't find an IMS DC list.

:>We rely on getting control at task termination to clean up resources 
:>used by our software.  We create a PC to add an MVS RESMGR exit when our 
:>software is first accessed in an IMS MPR.  If there is a pseudo-abend, 
:>which we understand means the TCB on which transactions run will 
:>terminate, we expect our RESMGR exit to execute.  The IMS MPR control 
:>program will then attach a new TCB in the region on which to run 
:>transactions.  Our software will be reinitialized if a transaction 
:>accesses it.  This could happen many times.  However, if our RESMGR exit 
:>doesn't execute, we may deplete resources.

:>Is it possible that the IMS MPR control program bypasses or deletes our 
:>RESMGR exit on some pseudo-abends?

It has been a while, but it appears that the TCB does not always end when one
expects. 

Are you just guessing that there is a problem, or do you see evidence of a
problem? 

Are you seeing the tasks ending without your RESMGR doing its job? 

Do you need to clean up if the message region runs a new program?

--
Binyamin Dissen 
http://www.dissensoftware.com

Director, Dissen Software, Bar & Grill - Israel


Should you use the mailblocks package and expect a response from me,
you should preauthorize the dissensoftware.com domain.

I very rarely bother responding to challenge/response systems,
especially those from irresponsible companies.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: MVS RESMGR exit

2021-01-18 Thread Lizette Koehler
The List for IMS is

IMS http://imslistserv.bmc.com/scripts/wa-BMC.exe?A0=ims-l

If you have not joined - it is free to sign up

Lizette

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Gary Weinhold
Sent: Monday, January 18, 2021 1:52 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: MVS RESMGR exit

Excuse me for asking this question here, but I can't find an IMS DC list.

We rely on getting control at task termination to clean up resources used by 
our software.  We create a PC to add an MVS RESMGR exit when our software is 
first accessed in an IMS MPR.  If there is a pseudo-abend, which we understand 
means the TCB on which transactions run will terminate, we expect our RESMGR 
exit to execute.  The IMS MPR control program will then attach a new TCB in the 
region on which to run transactions.  Our software will be reinitialized if a 
transaction accesses it.  This could happen many times.  However, if our RESMGR 
exit doesn't execute, we may deplete resources.

Is it possible that the IMS MPR control program bypasses or deletes our RESMGR 
exit on some pseudo-abends?



Gary Weinhold
Senior Application Architect
DATAKINETICS | Data Performance & Optimization
Phone:+1.613.523.5500 x216
Email: weinh...@dkl.com
Visit us online at www.DKL.com
E-mail Notification: The information contained in this email and any 
attachments is confidential and may be subject to copyright or other 
intellectual property protection. If you are not the intended recipient, you 
are not authorized to use or disclose this information, and we request that you 
notify us by reply mail or telephone and delete the original message from your 
mail system. 



--
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


Re: MVS RESMGR exit

2021-01-18 Thread Seymour J Metz
First, this is definitely a legitimate list for IMS questions: you'll get more 
eyeballs but less concentrated in depth knowledge here. My advice is to post on 
both lists and to note the cross posting.

Second, unless an IMS pseudo-ABEND causes a real ABEND, only IMS rcovery code 
will run.

Third, can an IMS pseudo-ABEND cause termination of the MPR?


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Gary Weinhold [weinh...@dkl.com]
Sent: Monday, January 18, 2021 3:51 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: MVS RESMGR exit

Excuse me for asking this question here, but I can't find an IMS DC list.

We rely on getting control at task termination to clean up resources
used by our software.  We create a PC to add an MVS RESMGR exit when our
software is first accessed in an IMS MPR.  If there is a pseudo-abend,
which we understand means the TCB on which transactions run will
terminate, we expect our RESMGR exit to execute.  The IMS MPR control
program will then attach a new TCB in the region on which to run
transactions.  Our software will be reinitialized if a transaction
accesses it.  This could happen many times.  However, if our RESMGR exit
doesn't execute, we may deplete resources.

Is it possible that the IMS MPR control program bypasses or deletes our
RESMGR exit on some pseudo-abends?



Gary Weinhold
Senior Application Architect
DATAKINETICS | Data Performance & Optimization
Phone:+1.613.523.5500 x216
Email: weinh...@dkl.com
Visit us online at 
http://secure-web.cisco.com/1ThLsaDk3Jxh0BTYv7hVr821No7D2wZwKcoMywmPoU28jK4_nnpcbx4i89M237BBsFJiEBhWBJDo6maWWdfwNoodMBhFTveWAuOXC9gRNgoWtxtF2tfRjuyyghOFOKddWjg4Ne4S-BmcNgA4V-0DuAny7_emT2DEFa3s2g15xEhp0P6x-PcX3f12oQjGOu5B95COqigd9IvD436I1U0fitFZNv3c9I0E4zftKRdAIx5gQeX8EGP1ceVZvasotI74TfP36LWatlTGP1_oZT57RnJUKZc17XpotktCTItkmbvKE1GUDJfWpE6I6AQtIPvRax0hHIcRlHdubU_47yXehHxUSngVgY3dXEqiHaarxXLd13MXHox9bvuY2LXjRx3Ef8tUYRXCh9bMOPL8E1h5qKrpNv1opeQZlIVDyn-8HFgjOpcMO1N6PxqMMhGecXggr/http%3A%2F%2Fwww.DKL.com
E-mail Notification: The information contained in this email and any 
attachments is confidential and may be subject to copyright or other 
intellectual property protection. If you are not the intended recipient, you 
are not authorized to use or disclose this information, and we request that you 
notify us by reply mail or telephone and delete the original message from your 
mail system.



--
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


Re: MVS RESMGR exit

2021-01-18 Thread Attila Fogarasi
Perhaps some pseudo-abends in IMS do not result in TCB termination and
re-attach.  The IMS dependent region has a multi-level TCB structure
(originally to handle application programs issuing the EXIT SVC, such as
Cobol STOP RUN, as well as abnormal conditions).  The primary purpose of a
pseudo-abend (as opposed to a real abend issued by IMS) was to gather
diagnostic info (e.g. 67FF log records) and continue normal application
execution (including requeue of the affected transaction for many cases).
Ending the TCB and re-attach occurs when cleanup is needed.  This is often,
but I don't know if it is for every pseudo-abend condition and could even
vary by region type and environment.  Your best bet is a GTF trace to see
what conditions your testcase is encountering.  There are a lot of possible
permutations and support for Java etc. has complicated the
environment considerably.

On Tue, Jan 19, 2021 at 7:52 AM Gary Weinhold  wrote:

> Excuse me for asking this question here, but I can't find an IMS DC list.
>
> We rely on getting control at task termination to clean up resources
> used by our software.  We create a PC to add an MVS RESMGR exit when our
> software is first accessed in an IMS MPR.  If there is a pseudo-abend,
> which we understand means the TCB on which transactions run will
> terminate, we expect our RESMGR exit to execute.  The IMS MPR control
> program will then attach a new TCB in the region on which to run
> transactions.  Our software will be reinitialized if a transaction
> accesses it.  This could happen many times.  However, if our RESMGR exit
> doesn't execute, we may deplete resources.
>
> Is it possible that the IMS MPR control program bypasses or deletes our
> RESMGR exit on some pseudo-abends?
>
>
>
> Gary Weinhold
> Senior Application Architect
> DATAKINETICS | Data Performance & Optimization
> Phone:+1.613.523.5500 x216
> Email: weinh...@dkl.com
> Visit us online at www.DKL.com
> E-mail Notification: The information contained in this email and any
> attachments is confidential and may be subject to copyright or other
> intellectual property protection. If you are not the intended recipient,
> you are not authorized to use or disclose this information, and we request
> that you notify us by reply mail or telephone and delete the original
> message from your mail system.
>
>
>
> --
> 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


MVS RESMGR exit

2021-01-18 Thread Gary Weinhold

Excuse me for asking this question here, but I can't find an IMS DC list.

We rely on getting control at task termination to clean up resources
used by our software.  We create a PC to add an MVS RESMGR exit when our
software is first accessed in an IMS MPR.  If there is a pseudo-abend,
which we understand means the TCB on which transactions run will
terminate, we expect our RESMGR exit to execute.  The IMS MPR control
program will then attach a new TCB in the region on which to run
transactions.  Our software will be reinitialized if a transaction
accesses it.  This could happen many times.  However, if our RESMGR exit
doesn't execute, we may deplete resources.

Is it possible that the IMS MPR control program bypasses or deletes our
RESMGR exit on some pseudo-abends?



Gary Weinhold
Senior Application Architect
DATAKINETICS | Data Performance & Optimization
Phone:+1.613.523.5500 x216
Email: weinh...@dkl.com
Visit us online at www.DKL.com
E-mail Notification: The information contained in this email and any 
attachments is confidential and may be subject to copyright or other 
intellectual property protection. If you are not the intended recipient, you 
are not authorized to use or disclose this information, and we request that you 
notify us by reply mail or telephone and delete the original message from your 
mail system.



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN