Author: Robert Sample
Posted: Mon May 22, 2017 11:42 pm (GMT 5.5)
How many LPARs share the SYS1.PROCLIB data set? Is SYS1.PROCLIB indirectly cataloged? Are you planning on bringing JES2 / JES3 down before redefining SYS1.PROCLIB? If not, how will you prevent JES problems? From APAR II04595:
If the lack of space (which is what I assume you meant by "kack of space" in your post) is no secondary allocation, you can override the secondary allocation in a job and let it go into secondary extents. If the lack of space is no directory space, and you have PDS86 installed at your site, use that to add directory space to the data set. If you feel you have no choice but to move SYS1.PROCLIB to another volume to give it more space, be aware that you could have problems from doing so and I would HIGHLY recommend an IPL immediately after SYS1.PROCLIB has been moved.
_________________
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: Mon May 22, 2017 11:42 pm (GMT 5.5)
| Quote: |
| Do i need to consider about something before do it ? |
| Quote: |
| THE CUSTOMER'S PROBLEM STARTS WHEN HE PREPARES FOR THE IPL BY BRINGING JES2 DOWN GRACEFULLY. THE CLOSE FUNCTION PERFORMED AT END OF JOB WILL CAUSE INDIRECTLY CATALOGED NONVSAM DATASETS (PROCLIB) TO BE RECATALOGED. WHEN THE DATASET WAS OPENED, NO TTR WAS PASSED TO OPEN, SO A FULL VTOC SEARCH WAS DONE AND THE TTR OF THE FORMAT 1 DSCB (FORMAT1) WAS SAVED IN THE JFCB. IN ADDITION, AN INDICATOR WAS TURNED ON IN THE JFCB TO TELL TERMINATION TO RECATALOG THE DATASET. TERMINATION DOES A CAMLST RECATALOG WHICH GETS TRANSLATED TO A VSAM/ICF CATALOG PARMLIST ALTER NEWNAME WITH THE NEW AND OLD NAME THE SAME, BUT USING THE TTR PASSED IN THE VOLUME LIST. SO THE CATALOG-DIRECT WHICH WAS DONE EARLIER IS UNDONE AND THE DATASET IS NOW CATALOGED DIRECTLY TO THE VOLUME WHERE IT ORIGINALLY RESIDED. WHEN JES2 IS RESTARTED, THE OPEN FAILURE OCCURS TRYING TOP OPEN THE MOVED DATASET. |
If the lack of space (which is what I assume you meant by "kack of space" in your post) is no secondary allocation, you can override the secondary allocation in a job and let it go into secondary extents. If the lack of space is no directory space, and you have PDS86 installed at your site, use that to add directory space to the data set. If you feel you have no choice but to move SYS1.PROCLIB to another volume to give it more space, be aware that you could have problems from doing so and I would HIGHLY recommend an IPL immediately after SYS1.PROCLIB has been moved.
_________________
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