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


Re: EOM for z hardware clarification

2021-01-18 Thread Gibney, Dave
Further off topic. CAPEX to me means the COBOL optimizer bought by CA in the 80s

> -Original Message-
> From: IBM Mainframe Discussion List  On
> Behalf Of R.S.
> Sent: Monday, January 18, 2021 6:57 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: EOM for z hardware clarification
> 
> Well said.
> However I have different observations of real world. It can be computer,
> dasd array, car, truck, airplane, etc.
> I even know cases when a leasing company is owned by leasing client.
> Sometimes bank lend money to (its own) leasing company just to lease
> something from that company.
> Of course I do not operate in US, so YMMV.
> 
> BTW: leasing, CAPEX and OPEX are slightly off-topic. ;-)
> 
> --
> Radoslaw Skorupka
> Lodz, Poland
> 
> 
> 
> 
> 
> 
> W dniu 18.01.2021 o 14:05, Joe Monk pisze:
> > "CAPEX can be converted to OPEX i.e. by using leasing services."
> >
> > The lease must be a fair market value lease, so that title does not pass.
> > Only then is it  considered OPEX.
> >
> > If it's a dollar buyout lease, then its a CAPEX lease and must  be
> > accounted for as CAPEX.
> >
> > Joe
> >
> > On Mon, Jan 18, 2021 at 6:46 AM R.S. 
> wrote:
> >
> >> W dniu 18.01.2021 o 13:28, Joe Monk pisze:
> >>> "2. EOM and EOS are important, but IMHO prices are more important. In
> >>> many cases it is cheaper to replace machine than to buy service contract
> >>> for existing (old) one. And it is rather cheaper to buy newer model even
> >>> if new and new-1 are available."
> >>>
> >>> The purchase  of hardware is CAPEX. The purchase of a service contract
> is
> >>> OPEX. OPEX is an expense and affects income, therefore you do not
> have
> >> to
> >>> pay income tax on it. CAPEX affects fixed assets and there are taxes to
> >> be
> >>> paid on it.
> >>>
> >>> There is a point where it is less expensive to replace, say a model with
> >>> one that is newer (maybe a z13 with  a z16). But in general, it is less
> >>> expensive to maintain an existing piece of equipment  than to buy a new
> >> one
> >>>(depreciation and all).
> >> CAPEX can be converted to OPEX i.e. by using leasing services. There are
> >> also other tricks.
> >> Regarding prices - I do not have to convince anyone, but ...I used to
> >> buy mainframes and I simply see IBM offerings. Depending on time
> >> perspective *usually* it is more effective (cheaper) to buy new
> >> equipment than buy service for existing one. My advice: buying new
> >> hardware is the best time to think about service for all life of it.
> >> Extending support after first year tend to be more expensive, especially
> >> when new machine is available.
> >>
> >> --
> >> Radoslaw Skorupka
> >> Lodz, Poland
> >>
> 
> 
> 
> ==
> 
> 
> Jeśli nie jesteś adresatem tej wiadomości:
> 
> - powiadom nas o tym w mailu zwrotnym (dziękujemy!),
> - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub
> zapisałeś na dysku).
> Wiadomość ta może zawierać chronione prawem informacje, które może
> wykorzystać tylko adresat. Przypominamy, że każdy, kto rozpowszechnia
> (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania,
> narusza prawo i może podlegać karze.
> 
> mBank S.A. z siedzibą w Warszawie, ul. Prosta 18, 00-850
> Warszawa,https://urldefense.com/v3/__http://www.mBank.pl__;!!JmPEgB
> Y0HMszNaDT!77ZtdvxBINfpzOfskvsvZkm9zgXEtY8PyDt7SLcDIX96yvNfdAgAby
> YXVVWmcg$ , e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy
> XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237,
> NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na
> 01.01.2020 r. wynosi 169.401.468 złotych.
> 
> Jesteśmy administratorem twoich danych osobowych, które podałeś w
> związku z prowadzoną z nami korespondencją. Przetwarzamy te dane dla
> celów, które wynikają z przedmiotu korespondencji, w tym związanych z
> prowadzoną działalnością bankową.
> Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe
> znajdziesz w Pakietach RODO (w wersji polskiej i angielskiej), które są na
> https://urldefense.com/v3/__http://www.mbank.pl/rodo__;!!JmPEgBY0H
> MszNaDT!77ZtdvxBINfpzOfskvsvZkm9zgXEtY8PyDt7SLcDIX96yvNfdAgAbyb9o
> u_WNA$
> 
> 
> If you are not the addressee of this message:
> 
> - let us know by replying to this e-mail (thank you!),
> - delete this message permanently (including all the copies which you have
> printed out or saved).
> This message may contain legally protected information, which may be used
> exclusively by the addressee.Please be reminded that anyone who
> disseminates (copies, distributes) this message or takes any similar action,
> violates the law and may be penalised.
> 
> mBank S.A. with its registered office in Warsaw, ul. Prosta 18, 00-850
> Warszawa,https://urldefense.com/v3/__http://www.mBank.pl__;!!JmPEgB
> Y0HMszNaDT!77ZtdvxBINfpzOfskvsvZkm9zgXEtY8PyDt7SLcDIX96yvNfdAgAby
> YXVVWmcg$ , e-mail: kont...@mbank.pl. District Court for the Capital City

Re: EOM for z hardware clarification

2021-01-18 Thread R.S.

Well said.
However I have different observations of real world. It can be computer, 
dasd array, car, truck, airplane, etc.
I even know cases when a leasing company is owned by leasing client. 
Sometimes bank lend money to (its own) leasing company just to lease 
something from that company.

Of course I do not operate in US, so YMMV.

BTW: leasing, CAPEX and OPEX are slightly off-topic. ;-)

--
Radoslaw Skorupka
Lodz, Poland






W dniu 18.01.2021 o 14:05, Joe Monk pisze:

"CAPEX can be converted to OPEX i.e. by using leasing services."

The lease must be a fair market value lease, so that title does not pass.
Only then is it  considered OPEX.

If it's a dollar buyout lease, then its a CAPEX lease and must  be
accounted for as CAPEX.

Joe

On Mon, Jan 18, 2021 at 6:46 AM R.S.  wrote:


W dniu 18.01.2021 o 13:28, Joe Monk pisze:

"2. EOM and EOS are important, but IMHO prices are more important. In
many cases it is cheaper to replace machine than to buy service contract
for existing (old) one. And it is rather cheaper to buy newer model even
if new and new-1 are available."

The purchase  of hardware is CAPEX. The purchase of a service contract is
OPEX. OPEX is an expense and affects income, therefore you do not  have

to

pay income tax on it. CAPEX affects fixed assets and there are taxes to

be

paid on it.

There is a point where it is less expensive to replace, say a model with
one that is newer (maybe a z13 with  a z16). But in general, it is less
expensive to maintain an existing piece of equipment  than to buy a new

one

   (depreciation and all).

CAPEX can be converted to OPEX i.e. by using leasing services. There are
also other tricks.
Regarding prices - I do not have to convince anyone, but ...I used to
buy mainframes and I simply see IBM offerings. Depending on time
perspective *usually* it is more effective (cheaper) to buy new
equipment than buy service for existing one. My advice: buying new
hardware is the best time to think about service for all life of it.
Extending support after first year tend to be more expensive, especially
when new machine is available.

--
Radoslaw Skorupka
Lodz, Poland





==

Jeśli nie jesteś adresatem tej wiadomości:

- powiadom nas o tym w mailu zwrotnym (dziękujemy!),
- usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś 
na dysku).
Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać 
tylko adresat. Przypominamy, że każdy, kto rozpowszechnia (kopiuje, 
rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może 
podlegać karze.

mBank S.A. z siedzibą w Warszawie, ul. Prosta 18, 00-850 Warszawa,www.mBank.pl, 
e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział 
Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. 
Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2020 r. wynosi 
169.401.468 złotych.

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

- let us know by replying to this e-mail (thank you!),
- delete this message permanently (including all the copies which you have 
printed out or saved).
This message may contain legally protected information, which may be used 
exclusively by the addressee.Please be reminded that anyone who disseminates 
(copies, distributes) this message or takes any similar action, violates the 
law and may be penalised.

mBank S.A. with its registered office in Warsaw, ul. Prosta 18, 00-850 
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital 
City of Warsaw, 12th Commercial Division of the National Court Register, KRS 
025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 
169.401.468 as at 1 January 2020.

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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


Re: EOM for z hardware clarification

2021-01-18 Thread Joe Monk
"CAPEX can be converted to OPEX i.e. by using leasing services."

The lease must be a fair market value lease, so that title does not pass.
Only then is it  considered OPEX.

If it's a dollar buyout lease, then its a CAPEX lease and must  be
accounted for as CAPEX.

Joe

On Mon, Jan 18, 2021 at 6:46 AM R.S.  wrote:

> W dniu 18.01.2021 o 13:28, Joe Monk pisze:
> > "2. EOM and EOS are important, but IMHO prices are more important. In
> > many cases it is cheaper to replace machine than to buy service contract
> > for existing (old) one. And it is rather cheaper to buy newer model even
> > if new and new-1 are available."
> >
> > The purchase  of hardware is CAPEX. The purchase of a service contract is
> > OPEX. OPEX is an expense and affects income, therefore you do not  have
> to
> > pay income tax on it. CAPEX affects fixed assets and there are taxes to
> be
> > paid on it.
> >
> > There is a point where it is less expensive to replace, say a model with
> > one that is newer (maybe a z13 with  a z16). But in general, it is less
> > expensive to maintain an existing piece of equipment  than to buy a new
> one
> >   (depreciation and all).
>
> CAPEX can be converted to OPEX i.e. by using leasing services. There are
> also other tricks.
> Regarding prices - I do not have to convince anyone, but ...I used to
> buy mainframes and I simply see IBM offerings. Depending on time
> perspective *usually* it is more effective (cheaper) to buy new
> equipment than buy service for existing one. My advice: buying new
> hardware is the best time to think about service for all life of it.
> Extending support after first year tend to be more expensive, especially
> when new machine is available.
>
> --
> Radoslaw Skorupka
> Lodz, Poland
>
>
>
>
>
> ==
>
> Jeśli nie jesteś adresatem tej wiadomości:
>
> - powiadom nas o tym w mailu zwrotnym (dziękujemy!),
> - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub
> zapisałeś na dysku).
> Wiadomość ta może zawierać chronione prawem informacje, które może
> wykorzystać tylko adresat. Przypominamy, że każdy, kto rozpowszechnia
> (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania,
> narusza prawo i może podlegać karze.
>
> mBank S.A. z siedzibą w Warszawie, ul. Prosta 18, 00-850 Warszawa,
> www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy
> XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP:
> 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na
> 01.01.2020 r. wynosi 169.401.468 złotych.
>
> Jesteśmy administratorem twoich danych osobowych, które podałeś w związku
> z prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które
> wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną
> działalnością bankową.
> Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe
> znajdziesz w Pakietach RODO (w wersji polskiej i angielskiej), które są na
> www.mbank.pl/rodo
>
>
> If you are not the addressee of this message:
>
> - let us know by replying to this e-mail (thank you!),
> - delete this message permanently (including all the copies which you have
> printed out or saved).
> This message may contain legally protected information, which may be used
> exclusively by the addressee.Please be reminded that anyone who
> disseminates (copies, distributes) this message or takes any similar
> action, violates the law and may be penalised.
>
> mBank S.A. with its registered office in Warsaw, ul. Prosta 18, 00-850
> Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the
> Capital City of Warsaw, 12th Commercial Division of the National Court
> Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital
> amounting to PLN 169.401.468 as at 1 January 2020.
>
> We are the controller of your personal data, which you provided in
> connection with correspondence with us. We process your data for purposes
> resulting from the subject of correspondence, including those related to
> the banking services.
> More information on how we protect and process personal data can be found
> in the GDPR Packages (in English and Polish), which are on
> www.mbank.pl/rodo.
>
> --
> 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: EOM for z hardware clarification

2021-01-18 Thread R.S.

W dniu 18.01.2021 o 13:28, Joe Monk pisze:

"2. EOM and EOS are important, but IMHO prices are more important. In
many cases it is cheaper to replace machine than to buy service contract
for existing (old) one. And it is rather cheaper to buy newer model even
if new and new-1 are available."

The purchase  of hardware is CAPEX. The purchase of a service contract is
OPEX. OPEX is an expense and affects income, therefore you do not  have to
pay income tax on it. CAPEX affects fixed assets and there are taxes to be
paid on it.

There is a point where it is less expensive to replace, say a model with
one that is newer (maybe a z13 with  a z16). But in general, it is less
expensive to maintain an existing piece of equipment  than to buy a new one
  (depreciation and all).


CAPEX can be converted to OPEX i.e. by using leasing services. There are 
also other tricks.
Regarding prices - I do not have to convince anyone, but ...I used to 
buy mainframes and I simply see IBM offerings. Depending on time 
perspective *usually* it is more effective (cheaper) to buy new 
equipment than buy service for existing one. My advice: buying new 
hardware is the best time to think about service for all life of it. 
Extending support after first year tend to be more expensive, especially 
when new machine is available.


--
Radoslaw Skorupka
Lodz, Poland





==

Jeśli nie jesteś adresatem tej wiadomości:

- powiadom nas o tym w mailu zwrotnym (dziękujemy!),
- usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś 
na dysku).
Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać 
tylko adresat. Przypominamy, że każdy, kto rozpowszechnia (kopiuje, 
rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może 
podlegać karze.

mBank S.A. z siedzibą w Warszawie, ul. Prosta 18, 00-850 Warszawa,www.mBank.pl, 
e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział 
Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. 
Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2020 r. wynosi 
169.401.468 złotych.

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

- let us know by replying to this e-mail (thank you!),
- delete this message permanently (including all the copies which you have 
printed out or saved).
This message may contain legally protected information, which may be used 
exclusively by the addressee.Please be reminded that anyone who disseminates 
(copies, distributes) this message or takes any similar action, violates the 
law and may be penalised.

mBank S.A. with its registered office in Warsaw, ul. Prosta 18, 00-850 
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital 
City of Warsaw, 12th Commercial Division of the National Court Register, KRS 
025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 
169.401.468 as at 1 January 2020.

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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


Re: EOM for z hardware clarification

2021-01-18 Thread Joe Monk
"2. EOM and EOS are important, but IMHO prices are more important. In
many cases it is cheaper to replace machine than to buy service contract
for existing (old) one. And it is rather cheaper to buy newer model even
if new and new-1 are available."

The purchase  of hardware is CAPEX. The purchase of a service contract is
OPEX. OPEX is an expense and affects income, therefore you do not  have to
pay income tax on it. CAPEX affects fixed assets and there are taxes to be
paid on it.

There is a point where it is less expensive to replace, say a model with
one that is newer (maybe a z13 with  a z16). But in general, it is less
expensive to maintain an existing piece of equipment  than to buy a new one
 (depreciation and all).

Joe

On Mon, Jan 18, 2021 at 4:46 AM R.S.  wrote:

> W dniu 18.01.2021 o 10:55, Peter pisze:
> > Hello All,
> >
> > Just curious to understand what is the minimum duration for the z
> hardware
> > to be from withdrawn from marketing ?
> >
> > Are there any specific factor IBM follows ?
>
> There is excellent paper describing all the dates (GA, EOM, EOS).
> I found the link:
>
> https://www.ibm.com/support/pages/system/files/inline-files/IBM_Mainframe_Life_Cycle_History_V2.6_-_Oct_13_2020.pdf
>
> Few remarks
> 1. There is no long term comitment saying, let's say z16 will be
> available for minimum 5 years. Everytime this is decision of IBM.
> 2. EOM and EOS are important, but IMHO prices are more important. In
> many cases it is cheaper to replace machine than to buy service contract
> for existing (old) one. And it is rather cheaper to buy newer model even
> if new and new-1 are available.
> 3. There are other issues, like upgrade availability. Usually IBM first
> close "physical" upgrades, that means new hardware elements (cards,
> DRAWERs, etc.) Later IBM close microcode upgrades - this is reasonable,
> since they do not deliver anything physically.
> 4. There are independent service providers.
>
> --
> Radoslaw Skorupka
> Lodz, Poland
>
>
>
>
>
> ==
>
> Jeśli nie jesteś adresatem tej wiadomości:
>
> - powiadom nas o tym w mailu zwrotnym (dziękujemy!),
> - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub
> zapisałeś na dysku).
> Wiadomość ta może zawierać chronione prawem informacje, które może
> wykorzystać tylko adresat. Przypominamy, że każdy, kto rozpowszechnia
> (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania,
> narusza prawo i może podlegać karze.
>
> mBank S.A. z siedzibą w Warszawie, ul. Prosta 18, 00-850 Warszawa,
> www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy
> XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP:
> 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na
> 01.01.2020 r. wynosi 169.401.468 złotych.
>
> Jesteśmy administratorem twoich danych osobowych, które podałeś w związku
> z prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które
> wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną
> działalnością bankową.
> Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe
> znajdziesz w Pakietach RODO (w wersji polskiej i angielskiej), które są na
> www.mbank.pl/rodo
>
>
> If you are not the addressee of this message:
>
> - let us know by replying to this e-mail (thank you!),
> - delete this message permanently (including all the copies which you have
> printed out or saved).
> This message may contain legally protected information, which may be used
> exclusively by the addressee.Please be reminded that anyone who
> disseminates (copies, distributes) this message or takes any similar
> action, violates the law and may be penalised.
>
> mBank S.A. with its registered office in Warsaw, ul. Prosta 18, 00-850
> Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the
> Capital City of Warsaw, 12th Commercial Division of the National Court
> Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital
> amounting to PLN 169.401.468 as at 1 January 2020.
>
> We are the controller of your personal data, which you provided in
> connection with correspondence with us. We process your data for purposes
> resulting from the subject of correspondence, including those related to
> the banking services.
> More information on how we protect and process personal data can be found
> in the GDPR Packages (in English and Polish), which are on
> www.mbank.pl/rodo.
>
> --
> 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: EOM for z hardware clarification

2021-01-18 Thread R.S.

W dniu 18.01.2021 o 10:55, Peter pisze:

Hello All,

Just curious to understand what is the minimum duration for the z hardware
to be from withdrawn from marketing ?

Are there any specific factor IBM follows ?


There is excellent paper describing all the dates (GA, EOM, EOS).
I found the link:
https://www.ibm.com/support/pages/system/files/inline-files/IBM_Mainframe_Life_Cycle_History_V2.6_-_Oct_13_2020.pdf

Few remarks
1. There is no long term comitment saying, let's say z16 will be 
available for minimum 5 years. Everytime this is decision of IBM.
2. EOM and EOS are important, but IMHO prices are more important. In 
many cases it is cheaper to replace machine than to buy service contract 
for existing (old) one. And it is rather cheaper to buy newer model even 
if new and new-1 are available.
3. There are other issues, like upgrade availability. Usually IBM first 
close "physical" upgrades, that means new hardware elements (cards, 
DRAWERs, etc.) Later IBM close microcode upgrades - this is reasonable, 
since they do not deliver anything physically.

4. There are independent service providers.

--
Radoslaw Skorupka
Lodz, Poland





==

Jeśli nie jesteś adresatem tej wiadomości:

- powiadom nas o tym w mailu zwrotnym (dziękujemy!),
- usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś 
na dysku).
Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać 
tylko adresat. Przypominamy, że każdy, kto rozpowszechnia (kopiuje, 
rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może 
podlegać karze.

mBank S.A. z siedzibą w Warszawie, ul. Prosta 18, 00-850 Warszawa,www.mBank.pl, 
e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział 
Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. 
Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2020 r. wynosi 
169.401.468 złotych.

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

- let us know by replying to this e-mail (thank you!),
- delete this message permanently (including all the copies which you have 
printed out or saved).
This message may contain legally protected information, which may be used 
exclusively by the addressee.Please be reminded that anyone who disseminates 
(copies, distributes) this message or takes any similar action, violates the 
law and may be penalised.

mBank S.A. with its registered office in Warsaw, ul. Prosta 18, 00-850 
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital 
City of Warsaw, 12th Commercial Division of the National Court Register, KRS 
025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 
169.401.468 as at 1 January 2020.

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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


EOM for z hardware clarification

2021-01-18 Thread Peter
Hello All,

Just curious to understand what is the minimum duration for the z hardware
to be from withdrawn from marketing ?

Are there any specific factor IBM follows ?

Peter

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