Active log dataset rename

Raymond Bell

Active log dataset rename
Colleagues,

A brain teaser before I sod off for NY (that's New Years', not New York.
Chance would be a fine thing...) to do with renaming active log datasets.

Ours are named badly and inconsistently. One or the other I can - almost -
live with, but both is unacceptable. Net result is that for some of our
subsystems I'm going to be adding a completely new set of archive log
datasets and completely removing the existing ones.

I think I've got a problem with removing the old names. I'm going to define
and format the new logs, stop DB2, update the BSDS to stick them in and
remove the old names, then start DB2 and test it out. But thinking about
it, I don't think I can't remove the entry for the old active log that's in
use until DB2 has stepped off it onto one of my new active log datasets. I
was going to see if I couldn't do it in one bounce of DB2 but I think I need
two, the first to add all the new log names and the 2nd to remove the old
ones once DB2 is using one of my new log datasets. Does this sound right?

I'd really like to do it in one bounce so I can make use of one of our
regularly scheduled bounces but I don't think I can get away with it. Any
suggestions (apart from not using the word 'bounce' quite so often)?


Raymond Bell
Database Administrator
PS. Oh, and I know about adding them in the BSDS in the reverse order to
which you'd like them used.


This e-mail (and any attachments) may contain privileged and/or confidential information. If you are not the intended recipient please do not disclose, copy, distribute, disseminate or take any action in reliance on it. If you have received this message in error please reply and tell us and then delete it. Should you wish to communicate with us by e-mail we cannot guarantee the security of any data outside our own computer systems. For the protection of Legal & General's systems and staff, incoming emails will be automatically scanned.

Any information contained in this message may be subject to applicable terms and conditions and must not be construed as giving investment advice within or outside the United Kingdom.

Legal & General Group PLC, Temple Court, 11 Queen Victoria Street, London, EC4N 4TP.
Registered in England no: 1417162

Legal & General Group Plc is a holding company, subsidiary undertakings of which are fully authorised as appropriate under the Financial Services and Markets Act in respect of their investment activities in the UK.

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Michael Ebert

Re: Active log dataset rename
(in response to Raymond Bell)
Stop DB2, print BSDS contents, rename VSAM files for the active logs (or
repro REUSE [or ADRDSSU COPY without DEL] to predefined logs with the
proper name in case you want to be able to fall back - do not pre-format,
that's useful only for adding new empty logs), delete old logs from BSDS,
define new logs with the proper start/end-RBAs, print BSDS again for
verification, start DB2.
Maybe write a REXX to create the proper control statements; that's more
reliable.
Where did you get that "trick" from? I once deleted/defined logs so that
they'd be used in the order in which they were named, but I'm sure I did it
forward...

Happy New Year, don't burn your fingers!

Dr. Michael Ebert
DB2 Database Administrator
aMaDEUS Data Processing
Erding / Munich, Germany




From: "Bell, Raymond" <[login to unmask email]>@IDUGDB2-L.ORG on
31-12-2004 14:58 GMT

Please respond to DB2 Database Discussion list at IDUG
<[login to unmask email]>

Sent by: DB2 Data Base Discussion List <[login to unmask email]>



To: [login to unmask email]


cc:






Subjec [DB2-L] Active log dataset rename
t:








Colleagues,

A brain teaser before I sod off for NY (that's New Years', not New York.
Chance would be a fine thing...) to do with renaming active log datasets.

Ours are named badly and inconsistently. One or the other I can - almost -
live with, but both is unacceptable. Net result is that for some of our
subsystems I'm going to be adding a completely new set of archive log
datasets and completely removing the existing ones.

I think I've got a problem with removing the old names. I'm going to
define
and format the new logs, stop DB2, update the BSDS to stick them in and
remove the old names, then start DB2 and test it out. But thinking about
it, I don't think I can't remove the entry for the old active log that's in
use until DB2 has stepped off it onto one of my new active log datasets. I
was going to see if I couldn't do it in one bounce of DB2 but I think I
need
two, the first to add all the new log names and the 2nd to remove the old
ones once DB2 is using one of my new log datasets. Does this sound right?

I'd really like to do it in one bounce so I can make use of one of our
regularly scheduled bounces but I don't think I can get away with it. Any
suggestions (apart from not using the word 'bounce' quite so often)?


Raymond Bell
Database Administrator
PS. Oh, and I know about adding them in the BSDS in the reverse order to
which you'd like them used.


This e-mail (and any attachments) may contain privileged and/or
confidential information. If you are not the intended recipient please do
not disclose, copy, distribute, disseminate or take any action in reliance
on it. If you have received this message in error please reply and tell us
and then delete it. Should you wish to communicate with us by e-mail we
cannot guarantee the security of any data outside our own computer systems.
For the protection of Legal & General's systems and staff, incoming emails
will be automatically scanned.

Any information contained in this message may be subject to applicable
terms and conditions and must not be construed as giving investment advice
within or outside the United Kingdom.

Legal & General Group PLC, Temple Court, 11 Queen Victoria Street, London,
EC4N 4TP.
Registered in England no: 1417162

Legal & General Group Plc is a holding company, subsidiary undertakings of
which are fully authorised as appropriate under the Financial Services and
Markets Act in respect of their investment activities in the UK.

---------------------------------------------------------------------------------

Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org
. The IDUG List Admins can be reached at [login to unmask email]
Find out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Raymond Bell

Re: Active log dataset rename
(in response to Michael Ebert)
Hey Michael,

You know, I didn't even think about renaming the logs. That's a much better
idea, as long as I get the RBA ranges right. Which I will, of course...

That 'trick' I worked out while trying to get a subsystem to grind to a halt
awhile ago by removing active log datasets from the BSDS. Basically I
wanted the archive offload to fail. When putting the logs back I noticed
DB2 switches to the log that's at the 'top' of the queue, as listed by
DSNJU004. So to get them used in the 'right' order you have to treat each
NEWLOG command as if it's going on a stack, rather than a queue, and put the
first one you want switched to on the stack last. See, after 18 years as a
DB2 DBA I have picked up a trick or two, despite what Gary/Vitor may say.
;o)

Prosit Neujahr!


Raymond Bell
Database Administrator

-----Original Message-----
From: Michael Ebert [mailto:[login to unmask email]
Sent: 31 December 2004 15:12
To: [login to unmask email]
Subject: Re: [DB2-L] Active log dataset rename


Stop DB2, print BSDS contents, rename VSAM files for the active logs (or
repro REUSE [or ADRDSSU COPY without DEL] to predefined logs with the
proper name in case you want to be able to fall back - do not pre-format,
that's useful only for adding new empty logs), delete old logs from BSDS,
define new logs with the proper start/end-RBAs, print BSDS again for
verification, start DB2.
Maybe write a REXX to create the proper control statements; that's more
reliable.
Where did you get that "trick" from? I once deleted/defined logs so that
they'd be used in the order in which they were named, but I'm sure I did it
forward...

Happy New Year, don't burn your fingers!

Dr. Michael Ebert
DB2 Database Administrator
aMaDEUS Data Processing
Erding / Munich, Germany




From: "Bell, Raymond" <[login to unmask email]>@IDUGDB2-L.ORG on
31-12-2004 14:58 GMT

Please respond to DB2 Database Discussion list at IDUG
<[login to unmask email]>

Sent by: DB2 Data Base Discussion List <[login to unmask email]>



To: [login to unmask email]


cc:






Subjec [DB2-L] Active log dataset rename
t:








Colleagues,

A brain teaser before I sod off for NY (that's New Years', not New York.
Chance would be a fine thing...) to do with renaming active log datasets.

Ours are named badly and inconsistently. One or the other I can - almost -
live with, but both is unacceptable. Net result is that for some of our
subsystems I'm going to be adding a completely new set of archive log
datasets and completely removing the existing ones.

I think I've got a problem with removing the old names. I'm going to
define
and format the new logs, stop DB2, update the BSDS to stick them in and
remove the old names, then start DB2 and test it out. But thinking about
it, I don't think I can't remove the entry for the old active log that's in
use until DB2 has stepped off it onto one of my new active log datasets. I
was going to see if I couldn't do it in one bounce of DB2 but I think I
need
two, the first to add all the new log names and the 2nd to remove the old
ones once DB2 is using one of my new log datasets. Does this sound right?

I'd really like to do it in one bounce so I can make use of one of our
regularly scheduled bounces but I don't think I can get away with it. Any
suggestions (apart from not using the word 'bounce' quite so often)?


Raymond Bell
Database Administrator
PS. Oh, and I know about adding them in the BSDS in the reverse order to
which you'd like them used.


This e-mail (and any attachments) may contain privileged and/or
confidential information. If you are not the intended recipient please do
not disclose, copy, distribute, disseminate or take any action in reliance
on it. If you have received this message in error please reply and tell us
and then delete it. Should you wish to communicate with us by e-mail we
cannot guarantee the security of any data outside our own computer systems.
For the protection of Legal & General's systems and staff, incoming emails
will be automatically scanned.

Any information contained in this message may be subject to applicable
terms and conditions and must not be construed as giving investment advice
within or outside the United Kingdom.

Legal & General Group PLC, Temple Court, 11 Queen Victoria Street, London,
EC4N 4TP.
Registered in England no: 1417162

Legal & General Group Plc is a holding company, subsidiary undertakings of
which are fully authorised as appropriate under the Financial Services and
Markets Act in respect of their investment activities in the UK.

----------------------------------------------------------------------------
-----

Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org
. The IDUG List Admins can be reached at [login to unmask email]
Find out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm

----------------------------------------------------------------------------
-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org.
The IDUG List Admins can be reached at [login to unmask email] Find
out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm