Author: Willy Jensen
Posted: Tue May 23, 2017 9:29 pm (GMT 5.5)
Something like this:
- make a copy of SYS1.PROCLIB with a new name and bigger space,
- keep your TSO logon active !!!
- stop as much work on the system as you can.
- stop JES2 using command $PJES2,ABEND.
- rename SYS1.PROCLIB.
- rename new dataset to SYS1.PROCLIB.
- start JES2 normally.
I don't think this is documented, but I have done it in the distant past and I know others have too.
You might also want to check the JES2 procedure to see if there are other proclibs where you could move procedures to. You should probably compress SYS1.PROCLIB afterwards. And do a backup beforehand.
And as said earlier see if the JES2 procedure have volser as variables. Some JES2 procedures even have the datasetname as symbolic, which means that you can copy SYS1.PROCLIB and start JES2 using the new name. Then you have a fallback if something goes wong.
_________________
WJ
Posted: Tue May 23, 2017 9:29 pm (GMT 5.5)
Something like this:
- make a copy of SYS1.PROCLIB with a new name and bigger space,
- keep your TSO logon active !!!
- stop as much work on the system as you can.
- stop JES2 using command $PJES2,ABEND.
- rename SYS1.PROCLIB.
- rename new dataset to SYS1.PROCLIB.
- start JES2 normally.
I don't think this is documented, but I have done it in the distant past and I know others have too.
You might also want to check the JES2 procedure to see if there are other proclibs where you could move procedures to. You should probably compress SYS1.PROCLIB afterwards. And do a backup beforehand.
And as said earlier see if the JES2 procedure have volser as variables. Some JES2 procedures even have the datasetname as symbolic, which means that you can copy SYS1.PROCLIB and start JES2 using the new name. Then you have a fallback if something goes wong.
_________________
WJ