Anyone:
The sysut3 and sysut4 restriction from the fine manual I believe syas
there should be a specific allocation. IT seems reasonable to me that
indeed if there is a restriction it at the minimum should be
documented in the CURRENT manual and *IF* these are dynamically
allocated should be done as per the fine manual.
Anyone up to a doc apar and a TSO APAR ?
Ed
On Mar 25, 2013, at 3:41 AM, Elardus Engelbrecht wrote:
Shmuel Metz (Seymour J.) wrote:
TSO is supposed to allocate SYSUT3 and SYSUT4,
There's nothing special about SYSUT3 and SYSUT4. TSO allocates
whatever is in the logon proc.
Very True! Before issueing 'Z' in =3.4 or 'C' in =3.1, you can use
ISRDDN to see if you have SYSUT3/4 allocated or not. If it is
indeed pre-allocated in TSO logon proc, they will be used.
If not pre-allocated, the background services (PDF interface
utility) will allocate them.
In my case, SYSUT3/4 are not pre-allocated in my TSO logon proc,
but are allocated, used during compress and then freed.
To the OP:
I see an interesting sample which can be useful to prevent gray
hairs :-D during a compress:
ISP.SISPSAMP(ISRCMPEX) - This sample will prevent compressing any
SYS1. datasets.
I also see you can use COMPRESS_UTILITY_PROGRAM_EXIT or
COMPRESS_UTILITY_CLIST_EXIT.
With them you can write something to do a backup automagically
before continue to do a compress. Or you can selectively prevent
compress at all.
Thanks Shmuel for your kind post.
Groete / Greetings
Elardus Engelbrecht
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
