Db2 12 z/OS, LOCKPART vs. LOCKSIZE

Ruediger Kurtz

Db2 12 z/OS, LOCKPART vs. LOCKSIZE
Hi,

just something that struck me as being odd.

Knowledge Centre says that LOCKPART YES and LOCKSIZE TABLESPACE are mutually exclusive, whereas Db2 itself seems to allow the use of both.

<snip>

CREATE
TABLESPACE <tablespace>
IN <database>
NUMPARTS 40
(
PART 1
<. . .>
PART 40
)
<. . .>
LOCKSIZE TABLESPACE
LOCKPART YES
;

</snip>

We’re not having any problems with this combination, apart from understanding why it’s got implemented when apparently it shouldn’t have been.

Could anyone shed some light?

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.
________________________________

Joe Geller

RE: Db2 12 z/OS, LOCKPART vs. LOCKSIZE
(in response to Ruediger Kurtz)

Ruediger,

The wording in the manual changed between V10 and V11.  They both say:

You can specify the LOCKPART clause, but it has no effect. DB2 treats
all table spaces as if they were defined as LOCKPART YES. LOCKPART
YES specifies the use of selective partition locking.

In V10 it says:

If you specify LOCKSIZE TABLESPACE, the table space must be defined with
LOCKPART NO. LOCKSIZE TABLESPACE and LOCKPART YES are mutually
exclusive.

In V11 it only says:

LOCKSIZE TABLESPACE and LOCKPART YES are mutually exclusive

None of this wording makes logical sense and may be left over from earlier versions. In V10, if all tablespaces are treated as LOCKPART YES, then why would you be required to specify LOCKPART NO?

Joe



In Reply to Ruediger Kurtz:

Hi,

just something that struck me as being odd.

Knowledge Centre says that LOCKPART YES and LOCKSIZE TABLESPACE are mutually exclusive, whereas Db2 itself seems to allow the use of both.



CREATE
TABLESPACE
IN
NUMPARTS 40
(
PART 1

PART 40
)

LOCKSIZE TABLESPACE
LOCKPART YES
;



We’re not having any problems with this combination, apart from understanding why it’s got implemented when apparently it shouldn’t have been.

Could anyone shed some light?

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.
________________________________

Ruediger Kurtz

AW: Db2 12 z/OS, LOCKPART vs. LOCKSIZE
(in response to Joe Geller)
Hello Joe,

here’s the quote from Db2 12 (we’re on V12):

<quote>
You can specify the LOCKPART clause, but it has no effect. DB2 treats all table spaces as if they were defined as LOCKPART YES. LOCKPART YES specifies the use of selective partition locking. When all the conditions for selective partition locking are met, DB2 locks only the partitions that are accessed. When the conditions for selective partition locking are not met, DB2 locks every partition of the table space.
LOCKSIZE TABLESPACE and LOCKPART YES are mutually exclusive.
<unquote>

We do understand that it really makes no sense to specify LOCKPART YES (implicitly or explicitly) when actually you want a LOCKSIZE TABLESPACE. But why Db2 really allows the combined use is a mystery to me. I’d suspect that locksize wins over lockpart, but who knows.

I just altered a PBR to LOCKPART YES and afterwards I also altered its LOCKSIZE to TABLESPACE, our favourite catalog browser shows both changes:

BUFFERPOOL BP9
LOCKSIZE TABLESPACE
LOCKMAX 0
CLOSE YES
LOCKPART YES

Curiouser and curiouser. But again, we’re not facing any problems, it’s just an oddity I stumbled across.

Our favourite change management tool, by the way, disallows the combined use, which is what I’d have expected right from the start.

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.
________________________________
Von: Joe Geller [mailto:[login to unmask email]
Gesendet: Mittwoch, 11. Oktober 2017 17:18
An: [login to unmask email]
Betreff: [DB2-L] - RE: Db2 12 z/OS, LOCKPART vs. LOCKSIZE


Ruediger,

The wording in the manual changed between V10 and V11. They both say:

You can specify the LOCKPART clause, but it has no effect. DB2 treats
all table spaces as if they were defined as LOCKPART YES. LOCKPART
YES specifies the use of selective partition locking.

In V10 it says:

If you specify LOCKSIZE TABLESPACE, the table space must be defined with
LOCKPART NO. LOCKSIZE TABLESPACE and LOCKPART YES are mutually
exclusive.

In V11 it only says:

LOCKSIZE TABLESPACE and LOCKPART YES are mutually exclusive

None of this wording makes logical sense and may be left over from earlier versions. In V10, if all tablespaces are treated as LOCKPART YES, then why would you be required to specify LOCKPART NO?

Joe


In Reply to Ruediger Kurtz:
Hi,

just something that struck me as being odd.

Knowledge Centre says that LOCKPART YES and LOCKSIZE TABLESPACE are mutually exclusive, whereas Db2 itself seems to allow the use of both.



CREATE
TABLESPACE
IN
NUMPARTS 40
(
PART 1

PART 40
)

LOCKSIZE TABLESPACE
LOCKPART YES
;



We’re not having any problems with this combination, apart from understanding why it’s got implemented when apparently it shouldn’t have been.

Could anyone shed some light?

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.
________________________________

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

Walter Jani&#223;en

AW: Db2 12 z/OS, LOCKPART vs. LOCKSIZE
(in response to Ruediger Kurtz)
Hi

I can remember the days, where a lock was always only acquired for the last partition of a partitioned tablespace. And then they changed it to locking only the partition you access. I think that is what IBM called selective partition locking. At the same time the locking protocol in the coupling facility also changed.

Kind regards
Walter Janißen [standard_IBM+Champ+7+Yr+Analytics]

ITERGO Informationstechnologie GmbH
Anwendungsentwicklung
Technische Anwendungsarchitektur
Victoriaplatz 2
D-40198 Düsseldorf
[login to unmask email]<mailto:[login to unmask email]>

ITERGO Informationstechnologie GmbH
Vorsitzender des Aufsichtsrats: Christian Diedrich
Geschäftsführung: Dr. Bettina Anders (Vorsitzende),
Lothar Engelke, Ina Kirchhof, Dr. Michael Regauer
Sitz: Düsseldorf, Handelsregister: Amtsgericht Düsseldorf HRB 37996

Von: Kurtz, Rüdiger [mailto:[login to unmask email]
Gesendet: Donnerstag, 12. Oktober 2017 07:39
An: '[login to unmask email]'
Betreff: [DB2-L] - AW: Db2 12 z/OS, LOCKPART vs. LOCKSIZE

Hello Joe,

here’s the quote from Db2 12 (we’re on V12):

<quote>
You can specify the LOCKPART clause, but it has no effect. DB2 treats all table spaces as if they were defined as LOCKPART YES. LOCKPART YES specifies the use of selective partition locking. When all the conditions for selective partition locking are met, DB2 locks only the partitions that are accessed. When the conditions for selective partition locking are not met, DB2 locks every partition of the table space.
LOCKSIZE TABLESPACE and LOCKPART YES are mutually exclusive.
<unquote>

We do understand that it really makes no sense to specify LOCKPART YES (implicitly or explicitly) when actually you want a LOCKSIZE TABLESPACE. But why Db2 really allows the combined use is a mystery to me. I’d suspect that locksize wins over lockpart, but who knows.

I just altered a PBR to LOCKPART YES and afterwards I also altered its LOCKSIZE to TABLESPACE, our favourite catalog browser shows both changes:

BUFFERPOOL BP9
LOCKSIZE TABLESPACE
LOCKMAX 0
CLOSE YES
LOCKPART YES

Curiouser and curiouser. But again, we’re not facing any problems, it’s just an oddity I stumbled across.

Our favourite change management tool, by the way, disallows the combined use, which is what I’d have expected right from the start.

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.
________________________________
Von: Joe Geller [mailto:[login to unmask email]
Gesendet: Mittwoch, 11. Oktober 2017 17:18
An: [login to unmask email]<mailto:[login to unmask email]>
Betreff: [DB2-L] - RE: Db2 12 z/OS, LOCKPART vs. LOCKSIZE


Ruediger,

The wording in the manual changed between V10 and V11. They both say:

You can specify the LOCKPART clause, but it has no effect. DB2 treats
all table spaces as if they were defined as LOCKPART YES. LOCKPART
YES specifies the use of selective partition locking.

In V10 it says:

If you specify LOCKSIZE TABLESPACE, the table space must be defined with
LOCKPART NO. LOCKSIZE TABLESPACE and LOCKPART YES are mutually
exclusive.

In V11 it only says:

LOCKSIZE TABLESPACE and LOCKPART YES are mutually exclusive

None of this wording makes logical sense and may be left over from earlier versions. In V10, if all tablespaces are treated as LOCKPART YES, then why would you be required to specify LOCKPART NO?

Joe


In Reply to Ruediger Kurtz:
Hi,

just something that struck me as being odd.

Knowledge Centre says that LOCKPART YES and LOCKSIZE TABLESPACE are mutually exclusive, whereas Db2 itself seems to allow the use of both.



CREATE
TABLESPACE
IN
NUMPARTS 40
(
PART 1

PART 40
)

LOCKSIZE TABLESPACE
LOCKPART YES
;



We’re not having any problems with this combination, apart from understanding why it’s got implemented when apparently it shouldn’t have been.

Could anyone shed some light?

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.
________________________________

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

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

  • image001.png (2.6k)

Ruediger Kurtz

AW: Db2 12 z/OS, LOCKPART vs. LOCKSIZE
(in response to Walter Janißen)
Hi Walter,

long time no see.
Yes, those were the days ☺

And, if I remember correctly, the lock on the last partition meant there was an interest in the whole tablespace, not just the last partition.

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.
________________________________
Von: Walter Janißen [mailto:[login to unmask email]
Gesendet: Donnerstag, 12. Oktober 2017 08:04
An: [login to unmask email]
Betreff: [DB2-L] - AW: Db2 12 z/OS, LOCKPART vs. LOCKSIZE

Hi

I can remember the days, where a lock was always only acquired for the last partition of a partitioned tablespace. And then they changed it to locking only the partition you access. I think that is what IBM called selective partition locking. At the same time the locking protocol in the coupling facility also changed.

Kind regards
Walter Janißen [standard_IBM+Champ+7+Yr+Analytics]

ITERGO Informationstechnologie GmbH
Anwendungsentwicklung
Technische Anwendungsarchitektur
Victoriaplatz 2
D-40198 Düsseldorf
[login to unmask email]<mailto:[login to unmask email]>

ITERGO Informationstechnologie GmbH
Vorsitzender des Aufsichtsrats: Christian Diedrich
Geschäftsführung: Dr. Bettina Anders (Vorsitzende),
Lothar Engelke, Ina Kirchhof, Dr. Michael Regauer
Sitz: Düsseldorf, Handelsregister: Amtsgericht Düsseldorf HRB 37996

Von: Kurtz, Rüdiger [mailto:[login to unmask email]
Gesendet: Donnerstag, 12. Oktober 2017 07:39
An: '[login to unmask email]'
Betreff: [DB2-L] - AW: Db2 12 z/OS, LOCKPART vs. LOCKSIZE

Hello Joe,

here’s the quote from Db2 12 (we’re on V12):

<quote>
You can specify the LOCKPART clause, but it has no effect. DB2 treats all table spaces as if they were defined as LOCKPART YES. LOCKPART YES specifies the use of selective partition locking. When all the conditions for selective partition locking are met, DB2 locks only the partitions that are accessed. When the conditions for selective partition locking are not met, DB2 locks every partition of the table space.
LOCKSIZE TABLESPACE and LOCKPART YES are mutually exclusive.
<unquote>

We do understand that it really makes no sense to specify LOCKPART YES (implicitly or explicitly) when actually you want a LOCKSIZE TABLESPACE. But why Db2 really allows the combined use is a mystery to me. I’d suspect that locksize wins over lockpart, but who knows.

I just altered a PBR to LOCKPART YES and afterwards I also altered its LOCKSIZE to TABLESPACE, our favourite catalog browser shows both changes:

BUFFERPOOL BP9
LOCKSIZE TABLESPACE
LOCKMAX 0
CLOSE YES
LOCKPART YES

Curiouser and curiouser. But again, we’re not facing any problems, it’s just an oddity I stumbled across.

Our favourite change management tool, by the way, disallows the combined use, which is what I’d have expected right from the start.

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.
________________________________
Von: Joe Geller [mailto:[login to unmask email]
Gesendet: Mittwoch, 11. Oktober 2017 17:18
An: [login to unmask email]<mailto:[login to unmask email]>
Betreff: [DB2-L] - RE: Db2 12 z/OS, LOCKPART vs. LOCKSIZE


Ruediger,

The wording in the manual changed between V10 and V11. They both say:

You can specify the LOCKPART clause, but it has no effect. DB2 treats
all table spaces as if they were defined as LOCKPART YES. LOCKPART
YES specifies the use of selective partition locking.

In V10 it says:

If you specify LOCKSIZE TABLESPACE, the table space must be defined with
LOCKPART NO. LOCKSIZE TABLESPACE and LOCKPART YES are mutually
exclusive.

In V11 it only says:

LOCKSIZE TABLESPACE and LOCKPART YES are mutually exclusive

None of this wording makes logical sense and may be left over from earlier versions. In V10, if all tablespaces are treated as LOCKPART YES, then why would you be required to specify LOCKPART NO?

Joe


In Reply to Ruediger Kurtz:
Hi,

just something that struck me as being odd.

Knowledge Centre says that LOCKPART YES and LOCKSIZE TABLESPACE are mutually exclusive, whereas Db2 itself seems to allow the use of both.



CREATE
TABLESPACE
IN
NUMPARTS 40
(
PART 1

PART 40
)

LOCKSIZE TABLESPACE
LOCKPART YES
;



We’re not having any problems with this combination, apart from understanding why it’s got implemented when apparently it shouldn’t have been.

Could anyone shed some light?

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.
________________________________

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

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

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

Walter Jani&#223;en

AW: Db2 12 z/OS, LOCKPART vs. LOCKSIZE
(in response to Ruediger Kurtz)
Hi Rüdiger

That’s true. Hope I meet you at BMC Round Table in Cologne.

I am not sure, what you are saying, but I think, it was an interest at some partition.

Mit freundlichen Grüßen
Walter Janißen

ITERGO Informationstechnologie GmbH
Spezialisten
Technische Anwendungsarchitektur
Victoriaplatz 2
40477 Düsseldorf

Tel 0211 477-2928
Fax 0211 477-7146
[login to unmask email]

Vorsitzender des Aufsichtsrats: Dr. Markus Rieß
Geschäftsführung: Tomasz Smaczny (Vorsitzender),
Gary Robert Dashwood, Lothar Engelke, Joachim Fensch, Oliver Gasmus,
Bernd Jung, Paul Spiteri
Sitz: Düsseldorf, Handelsregister: Amtsgericht Düsseldorf, HRB 37996
Von: Kurtz, Rüdiger [mailto:[login to unmask email]
Gesendet: Donnerstag, 12. Oktober 2017 08:13
An: '[login to unmask email]'
Betreff: [DB2-L] - AW: Db2 12 z/OS, LOCKPART vs. LOCKSIZE

Hi Walter,

long time no see.
Yes, those were the days ☺

And, if I remember correctly, the lock on the last partition meant there was an interest in the whole tablespace, not just the last partition.

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.
________________________________
Von: Walter Janißen [mailto:[login to unmask email]
Gesendet: Donnerstag, 12. Oktober 2017 08:04
An: [login to unmask email]<mailto:[login to unmask email]>
Betreff: [DB2-L] - AW: Db2 12 z/OS, LOCKPART vs. LOCKSIZE

Hi

I can remember the days, where a lock was always only acquired for the last partition of a partitioned tablespace. And then they changed it to locking only the partition you access. I think that is what IBM called selective partition locking. At the same time the locking protocol in the coupling facility also changed.

Kind regards
Walter Janißen [standard_IBM+Champ+7+Yr+Analytics]

ITERGO Informationstechnologie GmbH
Anwendungsentwicklung
Technische Anwendungsarchitektur
Victoriaplatz 2
D-40198 Düsseldorf
[login to unmask email]<mailto:[login to unmask email]>

ITERGO Informationstechnologie GmbH
Vorsitzender des Aufsichtsrats: Christian Diedrich
Geschäftsführung: Dr. Bettina Anders (Vorsitzende),
Lothar Engelke, Ina Kirchhof, Dr. Michael Regauer
Sitz: Düsseldorf, Handelsregister: Amtsgericht Düsseldorf HRB 37996

Von: Kurtz, Rüdiger [mailto:[login to unmask email]
Gesendet: Donnerstag, 12. Oktober 2017 07:39
An: '[login to unmask email]'
Betreff: [DB2-L] - AW: Db2 12 z/OS, LOCKPART vs. LOCKSIZE

Hello Joe,

here’s the quote from Db2 12 (we’re on V12):

<quote>
You can specify the LOCKPART clause, but it has no effect. DB2 treats all table spaces as if they were defined as LOCKPART YES. LOCKPART YES specifies the use of selective partition locking. When all the conditions for selective partition locking are met, DB2 locks only the partitions that are accessed. When the conditions for selective partition locking are not met, DB2 locks every partition of the table space.
LOCKSIZE TABLESPACE and LOCKPART YES are mutually exclusive.
<unquote>

We do understand that it really makes no sense to specify LOCKPART YES (implicitly or explicitly) when actually you want a LOCKSIZE TABLESPACE. But why Db2 really allows the combined use is a mystery to me. I’d suspect that locksize wins over lockpart, but who knows.

I just altered a PBR to LOCKPART YES and afterwards I also altered its LOCKSIZE to TABLESPACE, our favourite catalog browser shows both changes:

BUFFERPOOL BP9
LOCKSIZE TABLESPACE
LOCKMAX 0
CLOSE YES
LOCKPART YES

Curiouser and curiouser. But again, we’re not facing any problems, it’s just an oddity I stumbled across.

Our favourite change management tool, by the way, disallows the combined use, which is what I’d have expected right from the start.

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.
________________________________
Von: Joe Geller [mailto:[login to unmask email]
Gesendet: Mittwoch, 11. Oktober 2017 17:18
An: [login to unmask email]<mailto:[login to unmask email]>
Betreff: [DB2-L] - RE: Db2 12 z/OS, LOCKPART vs. LOCKSIZE


Ruediger,

The wording in the manual changed between V10 and V11. They both say:

You can specify the LOCKPART clause, but it has no effect. DB2 treats
all table spaces as if they were defined as LOCKPART YES. LOCKPART
YES specifies the use of selective partition locking.

In V10 it says:

If you specify LOCKSIZE TABLESPACE, the table space must be defined with
LOCKPART NO. LOCKSIZE TABLESPACE and LOCKPART YES are mutually
exclusive.

In V11 it only says:

LOCKSIZE TABLESPACE and LOCKPART YES are mutually exclusive

None of this wording makes logical sense and may be left over from earlier versions. In V10, if all tablespaces are treated as LOCKPART YES, then why would you be required to specify LOCKPART NO?

Joe


In Reply to Ruediger Kurtz:
Hi,

just something that struck me as being odd.

Knowledge Centre says that LOCKPART YES and LOCKSIZE TABLESPACE are mutually exclusive, whereas Db2 itself seems to allow the use of both.



CREATE
TABLESPACE
IN
NUMPARTS 40
(
PART 1

PART 40
)

LOCKSIZE TABLESPACE
LOCKPART YES
;



We’re not having any problems with this combination, apart from understanding why it’s got implemented when apparently it shouldn’t have been.

Could anyone shed some light?

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.
________________________________

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

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

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

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

Ruediger Kurtz

AW: Db2 12 z/OS, LOCKPART vs. LOCKSIZE
(in response to Walter Janißen)
Walter,

bad luck, I won’t be in Cologne this year.

What I’m saying is best described by what Mike Turner said eons (10 years and DB2 v7?) ago:

“Make sure that the tablespace is defined with LOCKPART YES. If not the
entire tablespace is locked logically, but in fact the lock is taken on
the last partition.”

In V8 that behavior changed, LOCKPART became more or less meaningless, but it’s still around somehow ☺

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.
________________________________
Von: Walter Janißen [mailto:[login to unmask email]
Gesendet: Donnerstag, 12. Oktober 2017 08:23
An: [login to unmask email]
Betreff: [DB2-L] - AW: Db2 12 z/OS, LOCKPART vs. LOCKSIZE

Hi Rüdiger

That’s true. Hope I meet you at BMC Round Table in Cologne.

I am not sure, what you are saying, but I think, it was an interest at some partition.

Mit freundlichen Grüßen
Walter Janißen

ITERGO Informationstechnologie GmbH
Spezialisten
Technische Anwendungsarchitektur
Victoriaplatz 2
40477 Düsseldorf

Tel 0211 477-2928
Fax 0211 477-7146
[login to unmask email]<mailto:[login to unmask email]>

Vorsitzender des Aufsichtsrats: Dr. Markus Rieß
Geschäftsführung: Tomasz Smaczny (Vorsitzender),
Gary Robert Dashwood, Lothar Engelke, Joachim Fensch, Oliver Gasmus,
Bernd Jung, Paul Spiteri
Sitz: Düsseldorf, Handelsregister: Amtsgericht Düsseldorf, HRB 37996
Von: Kurtz, Rüdiger [mailto:[login to unmask email]
Gesendet: Donnerstag, 12. Oktober 2017 08:13
An: '[login to unmask email]'
Betreff: [DB2-L] - AW: Db2 12 z/OS, LOCKPART vs. LOCKSIZE

Hi Walter,

long time no see.
Yes, those were the days ☺

And, if I remember correctly, the lock on the last partition meant there was an interest in the whole tablespace, not just the last partition.

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.
________________________________
Von: Walter Janißen [mailto:[login to unmask email]
Gesendet: Donnerstag, 12. Oktober 2017 08:04
An: [login to unmask email]<mailto:[login to unmask email]>
Betreff: [DB2-L] - AW: Db2 12 z/OS, LOCKPART vs. LOCKSIZE

Hi

I can remember the days, where a lock was always only acquired for the last partition of a partitioned tablespace. And then they changed it to locking only the partition you access. I think that is what IBM called selective partition locking. At the same time the locking protocol in the coupling facility also changed.

Kind regards
Walter Janißen [standard_IBM+Champ+7+Yr+Analytics]

ITERGO Informationstechnologie GmbH
Anwendungsentwicklung
Technische Anwendungsarchitektur
Victoriaplatz 2
D-40198 Düsseldorf
[login to unmask email]<mailto:[login to unmask email]>

ITERGO Informationstechnologie GmbH
Vorsitzender des Aufsichtsrats: Christian Diedrich
Geschäftsführung: Dr. Bettina Anders (Vorsitzende),
Lothar Engelke, Ina Kirchhof, Dr. Michael Regauer
Sitz: Düsseldorf, Handelsregister: Amtsgericht Düsseldorf HRB 37996

Von: Kurtz, Rüdiger [mailto:[login to unmask email]
Gesendet: Donnerstag, 12. Oktober 2017 07:39
An: '[login to unmask email]'
Betreff: [DB2-L] - AW: Db2 12 z/OS, LOCKPART vs. LOCKSIZE

Hello Joe,

here’s the quote from Db2 12 (we’re on V12):

<quote>
You can specify the LOCKPART clause, but it has no effect. DB2 treats all table spaces as if they were defined as LOCKPART YES. LOCKPART YES specifies the use of selective partition locking. When all the conditions for selective partition locking are met, DB2 locks only the partitions that are accessed. When the conditions for selective partition locking are not met, DB2 locks every partition of the table space.
LOCKSIZE TABLESPACE and LOCKPART YES are mutually exclusive.
<unquote>

We do understand that it really makes no sense to specify LOCKPART YES (implicitly or explicitly) when actually you want a LOCKSIZE TABLESPACE. But why Db2 really allows the combined use is a mystery to me. I’d suspect that locksize wins over lockpart, but who knows.

I just altered a PBR to LOCKPART YES and afterwards I also altered its LOCKSIZE to TABLESPACE, our favourite catalog browser shows both changes:

BUFFERPOOL BP9
LOCKSIZE TABLESPACE
LOCKMAX 0
CLOSE YES
LOCKPART YES

Curiouser and curiouser. But again, we’re not facing any problems, it’s just an oddity I stumbled across.

Our favourite change management tool, by the way, disallows the combined use, which is what I’d have expected right from the start.

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.
________________________________
Von: Joe Geller [mailto:[login to unmask email]
Gesendet: Mittwoch, 11. Oktober 2017 17:18
An: [login to unmask email]<mailto:[login to unmask email]>
Betreff: [DB2-L] - RE: Db2 12 z/OS, LOCKPART vs. LOCKSIZE


Ruediger,

The wording in the manual changed between V10 and V11. They both say:

You can specify the LOCKPART clause, but it has no effect. DB2 treats
all table spaces as if they were defined as LOCKPART YES. LOCKPART
YES specifies the use of selective partition locking.

In V10 it says:

If you specify LOCKSIZE TABLESPACE, the table space must be defined with
LOCKPART NO. LOCKSIZE TABLESPACE and LOCKPART YES are mutually
exclusive.

In V11 it only says:

LOCKSIZE TABLESPACE and LOCKPART YES are mutually exclusive

None of this wording makes logical sense and may be left over from earlier versions. In V10, if all tablespaces are treated as LOCKPART YES, then why would you be required to specify LOCKPART NO?

Joe


In Reply to Ruediger Kurtz:
Hi,

just something that struck me as being odd.

Knowledge Centre says that LOCKPART YES and LOCKSIZE TABLESPACE are mutually exclusive, whereas Db2 itself seems to allow the use of both.



CREATE
TABLESPACE
IN
NUMPARTS 40
(
PART 1

PART 40
)

LOCKSIZE TABLESPACE
LOCKPART YES
;



We’re not having any problems with this combination, apart from understanding why it’s got implemented when apparently it shouldn’t have been.

Could anyone shed some light?

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.
________________________________

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

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

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

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

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