Ahh, I see now. If you look closely a the toleration PTFs you will see that
they are specific issues which do not apply to the vast majority of migrations
and normally not to non-sysplex migrations at all, (excluding hardware
toleration PTFs which didn't apply to the OP's question, but could
I understand, I'll try to do better. I normally forget to click the little
quote thing at the bottom until it's too late.
Brian
On Sun, 8 Sep 2019 17:34:00 +, Jesse 1 Robinson
wrote:
>Brian, you seem to have a habit of replying to notes with very specific
>allusions but *no* quoted
> I don't know what you are basing the historical accuracy of this on.
I'm basing them on toleration PTFs that IBM has issued in the past and on IBM
documentation of various migrations.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From:
Brian, you seem to have a habit of replying to notes with very specific
allusions but *no* quoted text at all. This is just one example.
-- Who is 'you'?
-- What is 'this'?
Not everyone is happy with everyone else's style of reply, but your posts
frequently leave me wondering what you're
Adding to Kirk Wolf's reply, IBM provides its LDAP server for z/OS as part
of the *base* z/OS license, so you should be all set there.
Timothy Sipples
IT Architect Executive, Industry
We have been asked to move our mainframe from green zone ( multiple OSA 10GBs
connecting to routed Layer 3 Switch) where zOS Stack / OSPF doing load
balancing, error recovery to behind Firewall and may be with F5 (or IBM Data
power). we are on Z14 / zOS 2.3 and parallel Sysplex with same box.
Thanks everyone.
We have Managed to create $SYSNAME using ish to map it to $SYSNAME/ but only
after changing my OMVS home to sysplex root.
Just a follow up question, is there a way we can protect users to default to
System Root rather than SYSPLEX Root...e.e a user doing cd / should go to
