With all respect, I think there was enough time to move RYO tools to
RACF segment.
Proclib - ITYM logon procedue - I see no problem with that. More
important: I see no problem to authorize users to all procedures, since
it is method of customization, not resource access control
Not to mention I have never understood the purpose of account numbers
nowadays.
Benefits of move to UADS? Very little *now*.
But in general it is really good idea to migrate from old solutions
before IBM announce Enf Of Life for them. Time pressure or upgrade
stopper is really pain in the a...
Regards
--
Radoslaw Skorupka
Lodz, Poland
W dniu 2016-01-30 o 18:11, Skip Robinson pisze:
Ah, UADS. A prime example of archaic mechanism. Defensible technically?
Probably not, although a security administrator who needs to know which
account numbers or which proclibs a user is authorized to use might tell a
different story. With UADS, a simple list command tells the story. With TSOE
segment, it's a data mining operation. This difference alone has inhibited
conversion in some shops.
Consider a bigger problem. A shop has been in business for decades. In-house
RYO tools have been developed over the years to enable clerical security
personnel to manage addition, modification, and deletion of userids. All
based on UADS. IBM certainly supports the conversion process, but switching
to TSOE segment would require rewriting all of these in-house tools from the
ground up. Benefit? 'Modernization'. For the vast majority of users, there
is no perceivable difference. Who will fund this change and why? The
business units (clients) who must pony up the funds will not see any
demonstrable benefits. A tough sell. So UADS lives on.
I don't believe that native ISAM is even supported anymore. Back then the
ISAM application I referred to was economical to run because it was old, did
what was needed, and best of all did not require any updating. IIP allowed a
few *external* changes to deliver a major performance boost. An easy
business case to sell.
As I said earlier, I'm not arguing against moving forward with COBOL. Just
seeking some forbearance towards shops that see issues on the horizon.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
[email protected]
--
Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku
przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie
jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem
niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania
adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie
lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by
karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie
zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo
wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku.
This e-mail may contain legally privileged information of the Bank and is
intended solely for business use of the addressee. This e-mail may only be
received by the addressee and may not be disclosed to any third parties. If you
are not the intended addressee of this e-mail or the employee authorized to
forward it to the addressee, be advised that any dissemination, copying,
distribution or any other similar activity is legally prohibited and may be
punishable. If you received this e-mail by mistake please advise the sender
immediately by using the reply facility in your e-mail software and delete
permanently this e-mail including any copies of it either printed or saved to
hard drive.
mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa,
www.mBank.pl, e-mail: [email protected]
Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru
Sdowego, nr rejestru przedsibiorców KRS 0000025237, NIP: 526-021-50-88.
Wedug stanu na dzie 01.01.2016 r. kapita zakadowy mBanku S.A. (w caoci
wpacony) wynosi 168.955.696 zotych.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
