Page 1 of 1

One Parmlib/Proclib to rule them all

PostPosted: Thu Sep 28, 2017 5:20 pm
by bkw88
Hey Guys,

Wanted to reach out in regards to a question concerning your sysplex configurations concerning Parmlib/proclib. As of right now, our shop currently uses one parmlib/proclib to run the entire prod,dev and test lpars with heavy use of symbolics. Recently we've had a change in leadership and the new person would like to separate the lpar specific proclib/parmlib members into their own separate libraries. Based on your own personal experience which one do you guys recommend?

Me personally I believe that with Symbolics there should be no issues with keeping everything in one location. However I still have a lot to learn.

Re: One Parmlib/Proclib to rule them all

PostPosted: Thu Sep 28, 2017 5:28 pm
by enrico-sorichetti
What we think is irrelevant , it is the decision maker opinion that counts

what bothers me in Your setup is the sentence with heavy use of symbolics

I prefer common libraries,
but what is the boundary between a reasonable use of symbolics and a heavy one :mrgreen:

Re: One Parmlib/Proclib to rule them all

PostPosted: Thu Sep 28, 2017 5:37 pm
by bkw88
Just to clarify it's not a matter of opinion to challenge. I'm just curious to know as im sure you guys have probably dealt with both setups. As for the heavy use comment, 90% of our naming conventions are symbolic now.

Re: One Parmlib/Proclib to rule them all

PostPosted: Fri Sep 29, 2017 12:59 pm
by willy jensen
The last company I worked for has one parmlib / proclib set per sysplex. One parmlib / proclib set for all seems to me to be very risky.