MVSFORUMS.com

videlord · Beginner Joined: 09 Dec 2004 Posts: 147 Topics: 19

REORG job faile in RELOAD phase due to DATA SET full (reason code 00E40318)
SYSREC data set kept

then Term the utility, run sql:
Alter tablespace ts1 alter parition 1 priqty xxx secqty xxx compress yes

then use load utility to load the SYSREC generated in REORG UNLOAD PHASE
LOAD DATA REPLACE LOG NO NOCOPYPEND FORMAT UNLOAD

but all records discraded, 0 in, why?

schintala · Posted: Wed Jul 06, 2005 10:19 am Post subject:

Looks like you don't have enough cylinders in store group volumes in creating shadow datasets during reorg reload phase. Did you see in the DB2MSTR for the exact error message. It gives you right direction. If it is space problem I would allocate more volume to the stogroup. BTW, how your table space allocation made? As per DB2 V7 in z/os LDS can not have more than 2GB data. If it exceeds more than it allocates another DS, and henc you should be cautious in allocating primary and secondary quantities would match with 2GB.

videlord · Beginner Joined: 09 Dec 2004 Posts: 147 Topics: 19

schintala, thx for your reply.
But the now it is not the space problem, after ALTER SQL, space is OK.
The question is the SYSREC which kept from REORG UNLOAD phase can't be LOADed back to the same tablespace. All records discarded.
It's strange.

schintala · Posted: Wed Jul 06, 2005 12:40 pm Post subject:

How your load card defined? Doesit matches with unload file.

videlord · Beginner Joined: 09 Dec 2004 Posts: 147 Topics: 19

Hi schintala
I have decribed it in the first post,

LOAD DATA LOG NO NOCOPYPEND FORMAT UNLOAD INTO xxx

REORG UNLOAD is internal format

videlord · Beginner Joined: 09 Dec 2004 Posts: 147 Topics: 19

It seems than SYSREC of REORG is not same as REORG UNLOAD ONLY in DB2 V8 for z/OS.
The 6 bytes head of each reacord are not same.
Do anyone know the meaning of the 6 bytes head of the unloaded record by REORG?