Migrating Databases among Platforms(Re: DSN1COPY -- for replication)

Philip Sevetson

Migrating Databases among Platforms(Re: DSN1COPY -- for replication)
Two years ago, we migrated our Peoplesoft implementation from Oracle/Unix
to DB2/OS390; we're migrating another large set of databases from multiple
Sybase/AIX servers to a DB2 Data Sharing Group, again on OS390. Our Data
Warehouse application is on OS390.

Don't lose heart, Max.

--Phil Sevetson
Database Administration
Wakefern Food Corporation CISD
mailto:[login to unmask email]






[login to unmask email]
Sent by: DB2 Data Base Discussion List <[login to unmask email]>
12/12/2003 11:15 AM
Please respond to DB2 Database Discussion list at IDUG


To: [login to unmask email]
cc:
Subject: Re: DSN1COPY -- for replication


We had a miserable failure with client-server and have since move all of
it
back to
the mainframe.
We're looking at moving the server farms to mainframe/linx.
So its not all bad news.
cliff:-)

-----Original Message-----
From: [login to unmask email] [mailto:[login to unmask email]
Sent: Thursday, December 11, 2003 11:55 PM
To: [login to unmask email]
Subject: Re: DSN1COPY -- for replication


I'd like to know how they think it's more productive to move to cheaper
machine like WIN2000 or SQL SERVER

Here 2 sysprogs manage a mainframe and a lot of data and other things with
minimal outage while in the same time time 2 sysprogs plus some
programmers
are unable to tune only 1 (one) application in a decent manner on SQL
Server, with a lot and prolonged outages. And licence fees are NOT so
cheap for only 1 server.

Neverthless I receive a lot of mail clearly showing the disappearing of
mainframe as production platform. Mah

Max Scarpa

----------------------------------------------------------------------------
-----
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". If you will be out of the office, send the SET
DB2-L NO MAIL command to [login to unmask email] 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". If you will be out of
the office, send the SET DB2-L NO MAIL command to
[login to unmask email] 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". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] 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

Nam Wu

Re: DSN1COPY -- for replication
(in response to Philip Sevetson)
Hi Duane,

I really appreciate your help in this matter! I would love to see the
script you had written to handle the DSN1COPY. You can send it to either
the DB2-L distribution list or to me personally. Thanks, once again.

Nam


PS, I sent you an email offline. . .







"Duane Lee - EGOVX" <[login to unmask email]>
Sent by: "DB2 Data Base Discussion List" <[login to unmask email]>
12/10/2003 05:00 PM
Please respond to "DB2 Database Discussion list at IDUG"


To: [login to unmask email]
cc:
Subject: Re: DSN1COPY -- for replication



I built some SQL and REXX to build the DSN1COPY JCL for me. I use one SQL
routine too extract the source information, one SQL routine to extract the
target information and a REXX routine to read the extracted data and build
the DSN1COPY JCL. If you have multiple tables per tablespace this won't
work without modification on your part. If you are interested let me know
and I'll send what I have to you and you can do with it what you will. It
sets up one step per table. The table names must be the same in the
target environment as they are in the source. I'm, unfortunately, still
running on v5 with no prospects of moving to a new release so if you're on
a later release you may need to modify the routines.

By the way if you have any job openings for a DB2 DBA/Systems Programmer
please let me know because all of us on the mainframe are being phased out
because our CIO has chosen to move to Microsoft 2000 and MS SQL Server
2003 and not train any of us that work on the mainframe. My job search so
far has produced very few interviews and no job offers. The jobless
recovery sure sucks.

Duane
-----Original Message-----
From: [login to unmask email] [mailto:[login to unmask email]
Sent: Wednesday, December 10, 2003 5:35 PM
To: [login to unmask email]
Subject: DSN1COPY -- for replication


Hello,

I am a 390 newbie and I need some help with the DSN1COPY utility. What I
want to do is to replicate the objects and data from one database into
several other databases. Does anybody out there have a manual they can
share, or a link that they can direct me to, or share about the problems
you ran into?

I just want to know where to start: do I need to select the OBIDs first?
how do I account for the 500 OBIDs limit? do I need to find all the
datasets that correlate to the tablespaces that I want to move first? how
do I know which dataset I need? Or if you have a completely different
approach, I'll welcome any suggestions you have. (I'm eager to learn.)

Thanks in advance!!!

Nam
---------------------------------------------------------------------------------
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". If you will be out of
the office, send the SET DB2-L NO MAIL command to
[login to unmask email] 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". If you will be out of
the office, send the SET DB2-L NO MAIL command to
[login to unmask email] 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". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] 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

Max Scarpa

Re: Migrating Databases among Platforms(Re: DSN1COPY -- for replication)
(in response to Nam Wu)
Phil, Maurice

Thank you for your reply and pardon my 'vent' even if it's based on real
data and real co$t$ I see (almost) every day, not on marketing people's
tall stories. Your experiences are rays of sun in a dark sky.

The problem is (at least from what I saw) that many managers now came from
this cheap machine experience and for them mainframe is an obsolete and
dying machine, even if in many cases it's tested that you have savings in
many area (other than $$$$). And I don't understand why some prefere a SUN
mainframe (for instance) with respect to real mainframe.

The only thing I'm losing are my hair.....for now.

Regards
Max Scarpa

---------------------------------------------------------------------------------
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". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] 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

S. Kumar

Re: DSN1COPY -- for replication
(in response to Max Scarpa)
[login to unmask email]
.COM To: [login to unmask email]
Sent by: "DB2 cc:
Data Base Subject: Re: DSN1COPY -- for replication
Discussion List"
<[login to unmask email]
ORG>


12/12/2003 10:49
PM
Please respond to
"DB2 Database
Discussion list
at IDUG"











Hi Duane,

I really appreciate your help in this matter! I would love to see the
script you had written to handle the DSN1COPY. You can send it to either
the DB2-L distribution list or to me personally. Thanks, once again.

Nam


PS, I sent you an email offline. . .





"Duane Lee - EGOVX"
<[login to unmask email]> To:
Sent by: "DB2 Data Base Discussion List" [login to unmask email]
<[login to unmask email]> cc:
Subject: Re:
DSN1COPY -- for replication
12/10/2003 05:00 PM
Please respond to "DB2 Database
Discussion list at IDUG"







I built some SQL and REXX to build the DSN1COPY JCL for me. I use one SQL
routine too extract the source information, one SQL routine to extract the
target information and a REXX routine to read the extracted data and build
the DSN1COPY JCL. If you have multiple tables per tablespace this won't
work without modification on your part. If you are interested let me know
and I'll send what I have to you and you can do with it what you will. It
sets up one step per table. The table names must be the same in the target
environment as they are in the source. I'm, unfortunately, still running
on v5 with no prospects of moving to a new release so if you're on a later
release you may need to modify the routines.

By the way if you have any job openings for a DB2 DBA/Systems Programmer
please let me know because all of us on the mainframe are being phased out
because our CIO has chosen to move to Microsoft 2000 and MS SQL Server 2003
and not train any of us that work on the mainframe. My job search so far
has produced very few interviews and no job offers. The jobless recovery
sure sucks.

Duane
-----Original Message-----
From: [login to unmask email] [mailto:[login to unmask email]
Sent: Wednesday, December 10, 2003 5:35 PM
To: [login to unmask email]
Subject: DSN1COPY -- for replication


Hello,

I am a 390 newbie and I need some help with the DSN1COPY utility. What I
want to do is to replicate the objects and data from one database into
several other databases. Does anybody out there have a manual they can
share, or a link that they can direct me to, or share about the problems
you ran into?

I just want to know where to start: do I need to select the OBIDs first?
how do I account for the 500 OBIDs limit? do I need to find all the
datasets that correlate to the tablespaces that I want to move first? how
do I know which dataset I need? Or if you have a completely different
approach, I'll welcome any suggestions you have. (I'm eager to learn.)

Thanks in advance!!!

Nam
---------------------------------------------------------------------------------

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". If you will be out of the office, send the SET
DB2-L NO MAIL command to [login to unmask email] 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". If you will be out of the office, send the SET
DB2-L NO MAIL command to [login to unmask email] 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". If you will be out of the office, send the SET
DB2-L NO MAIL command to [login to unmask email] 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". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] 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

Isaac Yassin

Re: DSN1COPY -- for replication
(in response to S. Kumar)
Hi,

Around April 2000 I've posted a REXX to handle DSN1COPY to the documents list.
I hope it is still there :-)

Isaac Yassin
IBM Certified solution expert
DB2 V7 for OS/390 & Z/OS

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On Behalf Of S.
Kumar
Sent: Monday, December 15, 2003 9:40 AM
To: [login to unmask email]
Subject: Re: DSN1COPY -- for replication

[login to unmask email]
.COM To: [login to unmask email]
Sent by: "DB2 cc:
Data Base Subject: Re: DSN1COPY -- for
replication
Discussion List"
<[login to unmask email]
ORG>


12/12/2003 10:49
PM
Please respond to
"DB2 Database
Discussion list
at IDUG"











Hi Duane,

I really appreciate your help in this matter! I would love to see the
script you had written to handle the DSN1COPY. You can send it to either
the DB2-L distribution list or to me personally. Thanks, once again.

Nam


PS, I sent you an email offline. . .





"Duane Lee - EGOVX"
<[login to unmask email]> To:
Sent by: "DB2 Data Base Discussion List" [login to unmask email]
<[login to unmask email]> cc:
Subject: Re:
DSN1COPY -- for replication
12/10/2003 05:00 PM
Please respond to "DB2 Database
Discussion list at IDUG"







I built some SQL and REXX to build the DSN1COPY JCL for me. I use one SQL
routine too extract the source information, one SQL routine to extract the
target information and a REXX routine to read the extracted data and build
the DSN1COPY JCL. If you have multiple tables per tablespace this won't
work without modification on your part. If you are interested let me know
and I'll send what I have to you and you can do with it what you will. It
sets up one step per table. The table names must be the same in the target
environment as they are in the source. I'm, unfortunately, still running
on v5 with no prospects of moving to a new release so if you're on a later
release you may need to modify the routines.

By the way if you have any job openings for a DB2 DBA/Systems Programmer
please let me know because all of us on the mainframe are being phased out
because our CIO has chosen to move to Microsoft 2000 and MS SQL Server 2003
and not train any of us that work on the mainframe. My job search so far
has produced very few interviews and no job offers. The jobless recovery
sure sucks.

Duane
-----Original Message-----
From: [login to unmask email] [mailto:[login to unmask email]
Sent: Wednesday, December 10, 2003 5:35 PM
To: [login to unmask email]
Subject: DSN1COPY -- for replication


Hello,

I am a 390 newbie and I need some help with the DSN1COPY utility. What I
want to do is to replicate the objects and data from one database into
several other databases. Does anybody out there have a manual they can
share, or a link that they can direct me to, or share about the problems
you ran into?

I just want to know where to start: do I need to select the OBIDs first?
how do I account for the 500 OBIDs limit? do I need to find all the
datasets that correlate to the tablespaces that I want to move first? how
do I know which dataset I need? Or if you have a completely different
approach, I'll welcome any suggestions you have. (I'm eager to learn.)

Thanks in advance!!!

Nam
--------------------------------------------------------------------------------
-

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". If you will be out of the office, send the SET
DB2-L NO MAIL command to [login to unmask email] 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". If you will be out of the office, send the SET
DB2-L NO MAIL command to [login to unmask email] 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". If you will be out of the office, send the SET
DB2-L NO MAIL command to [login to unmask email] 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". If you will be out of the office, send the SET DB2-L NO MAIL
command to [login to unmask email] 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". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] 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

Horacio Villa

Re: DSN1COPY -- for replication
(in response to Isaac Yassin)
Isaac,

I was looking for it, but can't find the documents list.

Horacio Villa

---------------------------------------------------------------------------------
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". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] 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