DB2v10.1 for Z/OS. REORG failed with 00E40800. Utility remain in STOP state.

Oleg Dayneko

DB2v10.1 for Z/OS. REORG failed with 00E40800. Utility remain in STOP state.

Hi! I have a programm, that run reorg for tablespace every week.

In one day reorg ended with reason code=00E40800 and utility state changed to STOP. But this tablespace was in middle of list tablespaces for reorg. And all remain tablespacess in the list ended with message:

...

DSNU180I - 301 16:14:15.98 DSNUGUCC - UTILITY IS NOT COMPATIBLE WITH THE REORG TABLESPACE UTILITY

...

For example, I usage syntax of reorg:

TEMPLATE COPYTPL UNIT SYSDA DATACLAS DB2COPY DISP(NEW,DELETE,DELETE) SPACE(30000,30000) TRK DSN ('SORTSAP3.&DB..&SN..&UQ.')

TEMPLATE UNLDTPL UNIT SYSDA DATACLAS DB2COPY DISP(NEW,DELETE,DELETE) SPACE(30000,30000) TRK DSN ('SORTSAP3.&DB..&SN..&UQ.')

REORG TABLESPACE A140X998.COEP SHRLEVEL CHANGE MAPPINGTABLE SAPE03.REPUTMAPNC1 COPYDDN(COPYTPL) RECOVERYDDN(COPYTPL)

UNLDDN(UNLDTPL) SORTDEVT SYSDA DRAIN_WAIT 15 DRAIN ALL MAXRO 240 DELAY 900

LONGLOG CONTINUE TIMEOUT TERM RETRY 40 RETRY_DELAY 300 DEADLINE NONE

...

Is it possible to set up a reorg so that after a crash it never stays in the state of a stop?
 Maybe I can manage this REORG params "CONTINUE TIMEOUT TERM RETRY 40 RETRY_DELAY 300 DEADLINE NONE" ?

Chris Tee

DB2v10.1 for Z/OS. REORG failed with 00E40800. Utility remain in STOP state.
(in response to Oleg Dayneko)
Oleg


Are there any additional messages about sort work dataset allocation problems? Unfortunately, with this type of error, the utility is going to be put in a stopped state. Are the subsequent reorgs trying to use the same mapping table?


regards


Chris


________________________________
From: Oleg Dayneko <[login to unmask email]>
Sent: 31 October 2017 05:16
To: [login to unmask email]
Subject: [DB2-L] - DB2v10.1 for Z/OS. REORG failed with 00E40800. Utility remain in STOP state.


Hi! I have a programm, that run reorg for tablespace every week.

In one day reorg ended with reason code=00E40800 and utility state changed to STOP. But this tablespace was in middle of list tablespaces for reorg. And all remain tablespacess in the list ended with message:

...

DSNU180I - 301 16:14:15.98 DSNUGUCC - UTILITY IS NOT COMPATIBLE WITH THE REORG TABLESPACE UTILITY

...

For example, I usage syntax of reorg:

TEMPLATE COPYTPL UNIT SYSDA DATACLAS DB2COPY DISP(NEW,DELETE,DELETE) SPACE(30000,30000) TRK DSN ('SORTSAP3.&DB..&SN..&UQ.')

TEMPLATE UNLDTPL UNIT SYSDA DATACLAS DB2COPY DISP(NEW,DELETE,DELETE) SPACE(30000,30000) TRK DSN ('SORTSAP3.&DB..&SN..&UQ.')

REORG TABLESPACE A140X998.COEP SHRLEVEL CHANGE MAPPINGTABLE SAPE03.REPUTMAPNC1 COPYDDN(COPYTPL) RECOVERYDDN(COPYTPL)

UNLDDN(UNLDTPL) SORTDEVT SYSDA DRAIN_WAIT 15 DRAIN ALL MAXRO 240 DELAY 900

LONGLOG CONTINUE TIMEOUT TERM RETRY 40 RETRY_DELAY 300 DEADLINE NONE

...

Is it possible to set up a reorg so that after a crash it never stays in the state of a stop?
Maybe I can manage this REORG params "CONTINUE TIMEOUT TERM RETRY 40 RETRY_DELAY 300 DEADLINE NONE" ?

-----End Original Message-----

Oleg Dayneko

RE: DB2v10.1 for Z/OS. REORG failed with 00E40800. Utility remain in STOP state.
(in response to Chris Tee)

"Are the subsequent reorgs trying to use the same mapping table"

Yes. All reorg usage 1 mapping table. Maybe I must create 10 mapping table and mixed in reorg statement from 1 to 10?

I add volumes into sort group and reinitialize old volumes. Then repeat utility. The utility completed successfully.

I see, that after each reorg check utility state. If stopped, then term utility. But it was a program corrects.

Horacio Villa

DB2v10.1 for Z/OS. REORG failed with 00E40800. Utility remain in STOP state.
(in response to Oleg Dayneko)
I wonder why you delete the COPYs.Horacio Villa ----- Original message -----
From: Oleg Dayneko <[login to unmask email]>
To: [login to unmask email]
Cc:
Subject: [DB2-L] - DB2v10.1 for Z/OS. REORG failed with 00E40800. Utility remain in STOP state.
Date: Tue, Oct 31, 2017 2:16 AM

Hi! I have a programm, that run reorg for tablespace every week.
In one day reorg ended with reason code=00E40800 and utility state changed to STOP. But this tablespace was in middle of list tablespaces for reorg. And all remain tablespacess in the list ended with message:
...
DSNU180I - 301 16:14:15.98 DSNUGUCC - UTILITY IS NOT COMPATIBLE WITH THE REORG TABLESPACE UTILITY
...
For example, I usage syntax of reorg:
TEMPLATE COPYTPL UNIT SYSDA DATACLAS DB2COPY DISP(NEW,DELETE,DELETE) SPACE(30000,30000) TRK DSN ('SORTSAP3.&DB..&SN..&UQ.')
TEMPLATE UNLDTPL UNIT SYSDA DATACLAS DB2COPY DISP(NEW,DELETE,DELETE) SPACE(30000,30000) TRK DSN ('SORTSAP3.&DB..&SN..&UQ.')
REORG TABLESPACE A140X998.COEP SHRLEVEL CHANGE MAPPINGTABLE SAPE03.REPUTMAPNC1 COPYDDN(COPYTPL) RECOVERYDDN(COPYTPL)
UNLDDN(UNLDTPL) SORTDEVT SYSDA DRAIN_WAIT 15 DRAIN ALL MAXRO 240 DELAY 900
LONGLOG CONTINUE TIMEOUT TERM RETRY 40 RETRY_DELAY 300 DEADLINE NONE
...
Is it possible to set up a reorg so that after a crash it never stays in the state of a stop?
 Maybe I can manage this REORG params "CONTINUE TIMEOUT TERM RETRY 40 RETRY_DELAY 300 DEADLINE NONE" ? Site Links: View post online   View mailing list online   Start new thread via email   Unsubscribe from this mailing list   Manage your subscription  

This email has been sent to: [login to unmask email]
Setup a data refresh task in less time than it takes to make a cup of coffee + save up to 90% in CPU
ESAi's BCV5 & XDM fast data refresh & Test Data Mgmt products will make you a hero to users. See
http://www.ESAIGroup.com/idug

Use of this email content is governed by the terms of service at:
http://www.idug.org/p/cm/ld/fid=2

Oleg Dayneko

RE: DB2v10.1 for Z/OS. REORG failed with 00E40800. Utility remain in STOP state.
(in response to Horacio Villa)

I delete 2 copies when reorg each tablespace. I submit BACKUP SYSTEM utility every week. Therefore, I don't see the need to save copies for local and remote side. If crash occured, I restore Subsystem from FLASHCopy volumes.