SYSUT1 with REORG TABLESPACE needed in DB2 V8?

Kapil Mathur

SYSUT1 with REORG TABLESPACE needed in DB2 V8?
Hello Listers,

I am at DB2 V8 NFM on z/OS shop and we have BMC tools for DB2.
I was seeking a clarification from BMC Support when their response confused
me. Could someone please help me out with this ... thanks in advance.

Do we ever need to allocate a SYSUT1 dataset when we run a REORG
TABLESPACE utility?

From the online DB2 v8 Utility Guide and Reference (dated Sept 2008)
at IBM website in the chapter on Reorg Tablespace it says:-

Beginning with Version 8, the SORTKEYS option is the default .. Therefore the
REORG TABLESPACE utility does not require the SYSUT1 and SORTOUT
datasets.

However, later on in the same chapter, in the "Sample Reorg Tablespace
Control Statements" in Example 17 / Figure 90 the manual does show a
SYSUT1 DD being allocated & used for reorganizing:-
REORG TABLESPACE DBKQAA01.TPKQAA01 SCOPE PENDING PART 2:10

The DB2 V9 Utility Guide and Reference on the IBM website in the chapter on
Reorg Tablespace has the same SYSUT1 DD in the same example

Based on the above documentation, BMC Customer Support says that IBM
Reorg-Tablespace utility needs to allocate a SYSUT1 DD (even in DB2 v8)
when anyone does a TS partition-level reorg - Is this correct?
The entire Reorg Tablespace JCL in question is being automatically generated
by BMC Dasd Manager utility

______________________________________________________________________

* IDUG 2009 Denver, CO, USA * May 11-15, 2009 * http://IDUG.ORG/Events *
______________________________________________________________________




IDUG.org was recently updated requiring members to use a new password. You should have gotten an e-mail with the temporary password assigned to your account. Please log in and update your member profile. If you are not already an IDUG.org member, please register at http://www.idug.org/component/juser/register.html

Mark McCormack

SYSUT1 with REORG TABLESPACE needed in DB2 V8?
(in response to Kapil Mathur)
Kapil,

I notice that you have received no replies to your post. Let me give it
a try.

We have long since changed most of our reorgs to online reorg (which
does not use sysut1). We still have some standalone reorg jobs,
however, many of which (by coincidence) process partition ranges (but
without SCOPE PENDING as in example 17). These reorg jobs were
originally set up upder DB2v7 with SORTKEYS on the reorg stmt and no
sysut1 in the jcl. These continue to run since we converted to DB2v8 in
2006. I can't remember the last time I ran the reorg tablespace utility
with a sysut1 dd stmt.

I suspect that the presence of a sysut1 dd stmt in example 17 / figure
90 is an oversight. It may have been in the example prior to DB2v8, and
its continued presence may be a proofreading error.

Mark



______________________________________________________________________

* IDUG 2009 Melbourne, Australia * 18-20 March * http://IDUG.ORG/Events *
______________________________________________________________________




IDUG.org was recently updated requiring members to use a new password. You should have gotten an e-mail with the temporary password assigned to your account. Please log in and update your member profile. If you are not already an IDUG.org member, please register at http://www.idug.org/component/juser/register.html