Author: Robert Sample
Posted: Tue May 23, 2017 2:30 am (GMT 5.5)
I think you've got your answer -- if you redefine SYS1.PROCLIB, there are things to consider BEFORE embarking on the task. JES uses SYS1.PROCLIB and hence keeps it open; changing the data set without considering JES implications could lead to an unstable JES system at best, repeated IPLs at worst.
You didn't provide much information for us to help you, but depending upon why you want to redefine SYS1.PROCLIB, whether you're using JES2 or JES3, how many LPARs are sharing the SYSRES volume SYS1.PROCLIB is on, and whether or not SYS1.PROCLIB is indirectly cataloged -- you could potentially have an easy time redefining it or a very difficult time redefining it.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth
Posted: Tue May 23, 2017 2:30 am (GMT 5.5)
| Quote: |
| Do i need to consider about something before do it ? |
You didn't provide much information for us to help you, but depending upon why you want to redefine SYS1.PROCLIB, whether you're using JES2 or JES3, how many LPARs are sharing the SYSRES volume SYS1.PROCLIB is on, and whether or not SYS1.PROCLIB is indirectly cataloged -- you could potentially have an easy time redefining it or a very difficult time redefining it.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth