[Db2 12 for z/OS] Check Data

Ruediger Kurtz

[Db2 12 for z/OS] Check Data
Hi all,

maybe I’m already in the end-of-year-mode and can’t see the wood for the trees, but something concerning CHECK DATA today struck me as seemingly odd.

Here’s what I did: I ….

… Changed RI between 2 tables to ENFORCE NO
… Inserted 3 rows in the child-table that have no parent
… Changed the RI back to ENFORCE
… didn’t run CHECK DATA , but started the TS ACCESS(FORCE)
… ran CHECK DATA, SHRLEVEL REFERENCE DELETE NO SCOPE ALL (according to the documentation the tablespace should now be in CHKP)
… checked the utility-output (3 keys have no parent, as expected)
… checked the TS-State, the TS remained in RW-Mode, no CHKP (not as expected)

Am I missing the obvious? What am I doing wrong?

best regards

Rüdiger

Rüdiger Kurtz
Abteilung Informatik – Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon: 09561 96-44148
Telefax: 09561 96-44104
E-Mail: [login to unmask email]
Internet: www.huk.de
________________________________
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas (stv.).
________________________________
Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in this information is strictly forbidden.
________________________________

Michael Hannan

RE: [Db2 12 for z/OS] Check Data
(in response to Ruediger Kurtz)

Ruediger,

I did not know the answer but found this brief caveat almost hidden in the Db2 12 Utilities Reference under heading Output (for Check Data):

"If the utility finds any violation of constraints, the table space that is checked is not

put into the CHECK-pending status."

Mick Hannan

 In Reply to Ruediger Kurtz:

Hi all,

maybe I’m already in the end-of-year-mode and can’t see the wood for the trees, but something concerning CHECK DATA today struck me as seemingly odd.

Here’s what I did: I ….

… Changed RI between 2 tables to ENFORCE NO
… Inserted 3 rows in the child-table that have no parent
… Changed the RI back to ENFORCE
… didn’t run CHECK DATA , but started the TS ACCESS(FORCE)
… ran CHECK DATA, SHRLEVEL REFERENCE DELETE NO SCOPE ALL (according to the documentation the tablespace should now be in CHKP)
… checked the utility-output (3 keys have no parent, as expected)
… checked the TS-State, the TS remained in RW-Mode, no CHKP (not as expected)

Am I missing the obvious? What am I doing wrong?

best regards

Rüdiger

Rüdiger Kurtz
Abteilung Informatik – Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon: 09561 96-44148
Telefax: 09561 96-44104
E-Mail: [login to unmask email]
Internet: www.huk.de
________________________________
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas (stv.).
________________________________
Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in this information is strictly forbidden.
________________________________



Michael Hannan,
DB2 Application Performance Specialist
CPT Global Ltd

Ruediger Kurtz

AW: [Db2 12 for z/OS] Check Data
(in response to Michael Hannan)
Michael,

Thanks, but in the same documentation I find …

<snip>

DELETE
Indicates whether rows that are in violation of referential or table check constraints are to be deleted from the table space. You can specify DELETE only if you specify the FOR EXCEPTION clause.
NO Indicates that error rows are to remain in the table space. Primary errors in dependent tables are copied to exception tables.
If DELETE NO and SHRLEVEL REFERENCE are specified, and constraint violations are detected, CHECK DATA places the table space in the CHECK-pending status.

</snip>

Cf. https://www.ibm.com/support/knowledgecenter/SSEPEK_12.0.0/ugref/src/tpc/db2z_checkdatasyntax.html?cp=SS9UP7_2.2.0

And here’s the utility as it ran:

CHECK DATA TABLESPACE <database>.<tabspace>
FOR EXCEPTION
IN <creator>.<table> USE <excreator>.<extable>
DELETE NO SHRLEVEL REFERENCE SCOPE ALL

The violating rows are copied to the exception-table alright, but the tablespace is NOT put into CHECK PENDING.

This is the behavior documented, as you rightly say, under OUTPUT, but as soon as DELETE comes into play the documentation chose a different route.

Rüdiger


Rüdiger Kurtz
Abteilung Informatik – Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon: 09561 96-44148
Telefax: 09561 96-44104
E-Mail: [login to unmask email]
Internet: www.huk.de
________________________________
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas (stv.).
________________________________
Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in this information is strictly forbidden.
________________________________
Von: Michael Hannan [mailto:[login to unmask email]
Gesendet: Dienstag, 19. Dezember 2017 03:22
An: [login to unmask email]
Betreff: [DB2-L] - RE: [Db2 12 for z/OS] Check Data


Ruediger,

I did not know the answer but found this brief caveat almost hidden in the Db2 12 Utilities Reference under heading Output (for Check Data):

"If the utility finds any violation of constraints, the table space that is checked is not

put into the CHECK-pending status."

Mick Hannan

In Reply to Ruediger Kurtz:
Hi all,

maybe I’m already in the end-of-year-mode and can’t see the wood for the trees, but something concerning CHECK DATA today struck me as seemingly odd.

Here’s what I did: I ….

… Changed RI between 2 tables to ENFORCE NO
… Inserted 3 rows in the child-table that have no parent
… Changed the RI back to ENFORCE
… didn’t run CHECK DATA , but started the TS ACCESS(FORCE)
… ran CHECK DATA, SHRLEVEL REFERENCE DELETE NO SCOPE ALL (according to the documentation the tablespace should now be in CHKP)
… checked the utility-output (3 keys have no parent, as expected)
… checked the TS-State, the TS remained in RW-Mode, no CHKP (not as expected)

Am I missing the obvious? What am I doing wrong?

best regards

Rüdiger

Rüdiger Kurtz
Abteilung Informatik – Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon: 09561 96-44148
Telefax: 09561 96-44104
E-Mail: [login to unmask email]<mailto:[login to unmask email]>
Internet: www.huk.de http://www.huk.de
________________________________
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas (stv.).
________________________________
Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in this information is strictly forbidden.
________________________________



Michael Hannan,
DB2 Application Performance Specialist
CPT Global Ltd

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

Michael Hannan

RE: AW: [Db2 12 for z/OS] Check Data
(in response to Ruediger Kurtz)

Ruediger,

Documentation has been known to be misleading and even sometimes apparently contradictory. Could raise it with IBM. Documentation is done by documentation writers, that are not always completely expert. They rely on the experts to check it though.

Like you, I like to test out things to see how they actually function and see if the doco agrees with the experience. 

Michael Hannan,
DB2 Application Performance Specialist
CPT Global Ltd

Ruediger Kurtz

AW: AW: [Db2 12 for z/OS] Check Data
(in response to Michael Hannan)
Michael,

that’s just one way of looking at it – I personally feel inclined to consider this to be a bug within DB2 itself.

For what it’s worth: We copied a *a lot* of tablespaces over the weekend without stopping the source tablespaces, being aware that we will have to check the target-tablespaces afterwards.
Now we run loads of checks only to have to check each and every output to find those tables that actually have RI-violations? John McEnroe might have said “You cannot be serious”.
Can you guess how much easier things would’ve been had the check-utility told us all that by working the way it is documented?

Ah well ….

And by the way, one more issue:

The V11-doco reads as follows:

<snip>

If the utility finds any violation of constraints, the table space that is checked is not put into the CHECK-pending status. You can force the prior behavior, that a table space is put into CHECK-pending status when violations or constraints are detected, by specifying CHECK_SETCHKP=Y on the CHECK_SETCHKP system parameter.

</snip>

Now let us read this carefully: In prior version, CHECK DATA would have put the tablespace in Check Pending as soon as RI-violations were found.
One could force this pre-V11-behaviour by setting the ZPARM accordingly.
Alas, in V12 this ZPARM seems to have vanished, so CHECK DATA does NOT put a tablespace in CHECK-pending.
One could readily debate this behavior as suitable or not, but I do have a suspicion that coding DELETE NO SHRLEVEL REFERENCE was IBM’s replacement for that ZPARM.

Thanks all the same, I guess we will ask IBM …

Rüdiger


Rüdiger Kurtz
Abteilung Informatik – Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon: 09561 96-44148
Telefax: 09561 96-44104
E-Mail: [login to unmask email]
Internet: www.huk.de
________________________________
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas (stv.).
________________________________
Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in this information is strictly forbidden.
________________________________
Von: Michael Hannan [mailto:[login to unmask email]
Gesendet: Dienstag, 19. Dezember 2017 09:15
An: [login to unmask email]
Betreff: [DB2-L] - RE: AW: [Db2 12 for z/OS] Check Data


Ruediger,

Documentation has been known to be misleading and even sometimes apparently contradictory. Could raise it with IBM. Documentation is done by documentation writers, that are not always completely expert. They rely on the experts to check it though.

Like you, I like to test out things to see how they actually function and see if the doco agrees with the experience.

Michael Hannan,
DB2 Application Performance Specialist
CPT Global Ltd

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

Roy Boxwell

AW: [Db2 12 for z/OS] Check Data
(in response to Ruediger Kurtz)
Looks like IBM forgot to update the DELETE NO part of the docu. It never sets a CHKP anymore...mind you it is a bit strange that they only mention this en passant...

Roy Boxwell

SOFTWARE ENGINEERING GMBH and SEGUS Inc.
-Product Development-

Heinrichstrasse 83-85
40239 Duesseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]<mailto:[login to unmask email]>
http://www.seg.de http://www.seg.de

Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert

From: Kurtz, Rüdiger [mailto:[login to unmask email]
Sent: Tuesday, December 19, 2017 9:39 AM
To: '[login to unmask email]' <[login to unmask email]>
Subject: [DB2-L] - AW: AW: [Db2 12 for z/OS] Check Data

Michael,

that’s just one way of looking at it – I personally feel inclined to consider this to be a bug within DB2 itself.

For what it’s worth: We copied a *a lot* of tablespaces over the weekend without stopping the source tablespaces, being aware that we will have to check the target-tablespaces afterwards.
Now we run loads of checks only to have to check each and every output to find those tables that actually have RI-violations? John McEnroe might have said “You cannot be serious”.
Can you guess how much easier things would’ve been had the check-utility told us all that by working the way it is documented?

Ah well ….

And by the way, one more issue:

The V11-doco reads as follows:

<snip>

If the utility finds any violation of constraints, the table space that is checked is not put into the CHECK-pending status. You can force the prior behavior, that a table space is put into CHECK-pending status when violations or constraints are detected, by specifying CHECK_SETCHKP=Y on the CHECK_SETCHKP system parameter.

</snip>

Now let us read this carefully: In prior version, CHECK DATA would have put the tablespace in Check Pending as soon as RI-violations were found.
One could force this pre-V11-behaviour by setting the ZPARM accordingly.
Alas, in V12 this ZPARM seems to have vanished, so CHECK DATA does NOT put a tablespace in CHECK-pending.
One could readily debate this behavior as suitable or not, but I do have a suspicion that coding DELETE NO SHRLEVEL REFERENCE was IBM’s replacement for that ZPARM.

Thanks all the same, I guess we will ask IBM …

Rüdiger


Rüdiger Kurtz
Abteilung Informatik – Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon:

09561 96-44148

Telefax:

09561 96-44104

E-Mail:

[login to unmask email]<mailto:[login to unmask email]>

Internet:

www.huk.de http://www.huk.de

________________________________
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas (stv.).
________________________________
Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in this information is strictly forbidden.
________________________________
Von: Michael Hannan [mailto:[login to unmask email]
Gesendet: Dienstag, 19. Dezember 2017 09:15
An: [login to unmask email]<mailto:[login to unmask email]>
Betreff: [DB2-L] - RE: AW: [Db2 12 for z/OS] Check Data


Ruediger,

Documentation has been known to be misleading and even sometimes apparently contradictory. Could raise it with IBM. Documentation is done by documentation writers, that are not always completely expert. They rely on the experts to check it though.

Like you, I like to test out things to see how they actually function and see if the doco agrees with the experience.

Michael Hannan,
DB2 Application Performance Specialist
CPT Global Ltd

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

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

Ruediger Kurtz

AW: AW: [Db2 12 for z/OS] Check Data
(in response to Roy Boxwell)
Hi Roy,

well, I’d rather have DB2 tell me something’s wrong in the first place without me having to look for it myself … never mind, that’s just the way it is (Thanks, Bruce Hornsby).

Regards

Rüdiger


Rüdiger Kurtz
Abteilung Informatik – Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon: 09561 96-44148
Telefax: 09561 96-44104
E-Mail: [login to unmask email]
Internet: www.huk.de
________________________________
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas (stv.).
________________________________
Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in this information is strictly forbidden.
________________________________
Von: Boxwell, Roy [mailto:[login to unmask email]
Gesendet: Dienstag, 19. Dezember 2017 10:16
An: [login to unmask email]
Betreff: [DB2-L] - RE: AW: [Db2 12 for z/OS] Check Data

Looks like IBM forgot to update the DELETE NO part of the docu. It never sets a CHKP anymore...mind you it is a bit strange that they only mention this en passant...

Roy Boxwell

SOFTWARE ENGINEERING GMBH and SEGUS Inc.
-Product Development-

Heinrichstrasse 83-85
40239 Duesseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]<mailto:[login to unmask email]>
http://www.seg.de http://www.seg.de

Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert

From: Kurtz, Rüdiger [mailto:[login to unmask email]
Sent: Tuesday, December 19, 2017 9:39 AM
To: '[login to unmask email]' <[login to unmask email]<mailto:[login to unmask email]>>
Subject: [DB2-L] - AW: AW: [Db2 12 for z/OS] Check Data

Michael,

that’s just one way of looking at it – I personally feel inclined to consider this to be a bug within DB2 itself.

For what it’s worth: We copied a *a lot* of tablespaces over the weekend without stopping the source tablespaces, being aware that we will have to check the target-tablespaces afterwards.
Now we run loads of checks only to have to check each and every output to find those tables that actually have RI-violations? John McEnroe might have said “You cannot be serious”.
Can you guess how much easier things would’ve been had the check-utility told us all that by working the way it is documented?

Ah well ….

And by the way, one more issue:

The V11-doco reads as follows:

<snip>

If the utility finds any violation of constraints, the table space that is checked is not put into the CHECK-pending status. You can force the prior behavior, that a table space is put into CHECK-pending status when violations or constraints are detected, by specifying CHECK_SETCHKP=Y on the CHECK_SETCHKP system parameter.

</snip>

Now let us read this carefully: In prior version, CHECK DATA would have put the tablespace in Check Pending as soon as RI-violations were found.
One could force this pre-V11-behaviour by setting the ZPARM accordingly.
Alas, in V12 this ZPARM seems to have vanished, so CHECK DATA does NOT put a tablespace in CHECK-pending.
One could readily debate this behavior as suitable or not, but I do have a suspicion that coding DELETE NO SHRLEVEL REFERENCE was IBM’s replacement for that ZPARM.

Thanks all the same, I guess we will ask IBM …

Rüdiger


Rüdiger Kurtz
Abteilung Informatik – Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon:

09561 96-44148

Telefax:

09561 96-44104

E-Mail:

[login to unmask email]<mailto:[login to unmask email]>

Internet:

www.huk.de http://www.huk.de

________________________________
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas (stv.).
________________________________
Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in this information is strictly forbidden.
________________________________
Von: Michael Hannan [mailto:[login to unmask email]
Gesendet: Dienstag, 19. Dezember 2017 09:15
An: [login to unmask email]<mailto:[login to unmask email]>
Betreff: [DB2-L] - RE: AW: [Db2 12 for z/OS] Check Data


Ruediger,

Documentation has been known to be misleading and even sometimes apparently contradictory. Could raise it with IBM. Documentation is done by documentation writers, that are not always completely expert. They rely on the experts to check it though.

Like you, I like to test out things to see how they actually function and see if the doco agrees with the experience.

Michael Hannan,
DB2 Application Performance Specialist
CPT Global Ltd

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

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

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