DB2 v.8 z/OS DR Question

Robert Tilkes

DB2 v.8 z/OS DR Question
At DR the Archlog datasets and the Vsam backing files are in the same user
catalog. When I recover user catalog DB2.CATALOG in order to have access
to all of my archive log datasets. I will now have catalog entries for
the archlog DS as well as the DB2 VSAM backing files. I know I can issue
an IDCAM DELETE with the NOSCRATCH option to remove the catalog entries
prior to running my recover process. Does anyone know of a easy way to
either generate the DELETE statements? Maybe possible there is a better
way to handle this isssue? Any Ideas would be useful. Our old process
was the ARCHLOG were in a different user catalog and we would recover the
user cat with the archlog entries and rebuild the other one. That work
great. Both the Archive logs, active logs, bsds, DSNDB01, DSNDB06, and
APP DB are in the same user cat. Also all DS from the following Archive
logs, active logs, bsds, DSNDB01, and DSNDB06 have the same first node
qualifier. I am looking for a quick solution, please help?

Thank you in Advance for your help

Bob

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

Carol Broyles

Re: DB2 v.8 z/OS DR Question
(in response to Robert Tilkes)
Bob,

I've cleaned up ICF catalogs using a series of ISPF commands like the following.

First, save a 3.4 listing of your datasets with a command like "SAVE DB2". A dataset called "<your-profile-prefix>.DB2.DATASETS will be created. Edit this dataset and issue the following commands:

X ALL
F DSNDBC ALL
DEL ALL X
RESET
BNDS 45 *

Issue the following block command:

)) <This is on the first line of your dataset names.>
))100 <This is on the last line of your dataset names.>

This should leave the dataset name only on the line. Now issue command BNDS to reset your boundaries. Issue another block command to move the entries over 10 characters:

)) <This is on the first line of your dataset names.>
))10 <This is on the last line of your dataset names.>

Insert the following line before line 1 of the file:

DELETE ' ' NOSCRATCH

Then move this line and overlay all your dataset names with the following block commands:

M <This is the delete line you just inserted.>
OO <This is on the first line of your dataset names.>
OO <This is on the last line of your dataset names.>

Make sure you've included enough spaces in the "DELETE" line so you don't overlay any of the characters in the dataset names. Then issue the following command to get rid of all the spaces between the end of the dataset name and the apostrophe:

C " ' NOSCRATCH" "' NOSCRATCH" ALL

Continue to RETRIEVE and repeat this command until all the spaces between the end of the dataset name and the apostrophe are gone.

Save the dataset and include it in a batch IDCAMS job in the SYSIN DD.

HTH,

Carol

----- Original Message ----
From: Robert Tilkes <[login to unmask email]>
To: [login to unmask email]
Sent: Friday, January 12, 2007 4:00:28 PM
Subject: [DB2-L] DB2 v.8 z/OS DR Question


At DR the Archlog datasets and the Vsam backing files are in the same user
catalog. When I recover user catalog DB2.CATALOG in order to have access
to all of my archive log datasets. I will now have catalog entries for
the archlog DS as well as the DB2 VSAM backing files. I know I can issue
an IDCAM DELETE with the NOSCRATCH option to remove the catalog entries
prior to running my recover process. Does anyone know of a easy way to
either generate the DELETE statements? Maybe possible there is a better
way to handle this isssue? Any Ideas would be useful. Our old process
was the ARCHLOG were in a different user catalog and we would recover the
user cat with the archlog entries and rebuild the other one. That work
great. Both the Archive logs, active logs, bsds, DSNDB01, DSNDB06, and
APP DB are in the same user cat. Also all DS from the following Archive
logs, active logs, bsds, DSNDB01, and DSNDB06 have the same first node
qualifier. I am looking for a quick solution, please help?

Thank you in Advance for your help

Bob

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



____________________________________________________________________________________
Be a PS3 game guru.
Get your game face on with the latest PS3 news and previews at Yahoo! Games.
http://videogames.yahoo.com/platform?platform=120121

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

Walter Trovijo Jr (UOL)

Re: DB2 v.8 z/OS DR Question
(in response to Carol Broyles)
The simple rexx below does generate idcams delete and rename commands on datasets selected by mask using
a modified version of iggcsirx from sys1.samplib. Just modify iggcsirx to return result in stack instead of displaying it, or modify code below to trap iggcsirx display. Resulting idcams comands are written in sysut2 data which in turn can be passed to a idcams step sysin dd.

/* rexx */
;
arg parm
parse value parm with func msk1 msk2'('opt .
;
select
when func='ALTER' then cmd='ALTER'
when func='DELETE' then cmd='DELETE'
otherwise EXIT 8
end
;
parse value msk2 with hlqo'.'restoo
;
'DROPBUF'
rc= iggcsirx(msk1)
;
i=0
do queued()
pull dsni
if pos('NONVSAM',dsni) = 0 &,
pos('CLUSTER',dsni) = 0 then ITERATE
if cmd='ALTER' & pos('MIGRAT',dsni) > 0 then ITERATE
parse value dsni with type dsn .
parse value dsn with hlqi'.'restoi
if cmd='ALTER' then ,
do
i=i+1
cm.i=' 'cmd' 'dsn' -'
i=i+1
cm.i=' NEWNM('overlay(hlqo,dsn,1)')'
end
if cmd='DELETE' then ,
do
i=i+1
cm.i=' 'cmd' 'dsn' 'opt
/*cm.i=' 'cmd' 'dsn' 'type' 'opt*/
end
end
;
i=i+1
cm.i=' SET MAXCC=0'
i.0=i
;
'EXECIO * DISKW SYSUT2 (STEM CM.'

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