Kishore:
If I understand your question correctly .... the solution is not to
hardcode the qualifier inside your stored procedure. Use QUALIFIER option in
your db2prep/db2bind command.
Manas.
> We are on NT and AIX.
> So I am looking for solution on these platforms.
>
> Kish
>
>
> >From: Myron Miller <[EMAIL PROTECTED]>
> >Reply-To: [EMAIL PROTECTED]
> >To: [EMAIL PROTECTED]
> >Subject: Re: DB2EUG: Stored procedures move
> >Date: Wed, 23 May 2001 05:43:33 -0700 (PDT)
> >
> >What DB2 are you using this for. If OS/390, have easy solution, just
> >use DSNTPSMP with edit program on source to move from one system to
> >another.
> >
> >
> >--- kishore lingamallu <[EMAIL PROTECTED]> wrote:
> > > Hi
> > >
> > > We want to move the stored procedures from one environment to other
> > > environments like Test to QA , QA to Pord we are encountering
> > > problem.
> > >
> > > The table names are completely qualified means like
> > > testschema.tablename in
> > > Test environment qaschema.tablename in QA and proschema.tablename.in
> > > Prod in
> > > the stored procedures
> > >
> > > When we want to move the SQL stored procedures from one environment
> > > to other
> > > we are facing problem because of the qualifier and we have change
> > > qualifier/code every time to make it environment fit. There is a
> > > possibility
> > > of human errors while doing that hence we want to avoid it.
> > >
> > > What are the best ways to make the Stored Procedures Qualifier
> > > independent
> > > or edit free while moving them from one environment to other?
> > >
> > > Any kind of suggestion is appreciated.
> > >
> > > Thank You.
> > >
> > > Kish
=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
