Hi All,
We are moving to DataStage 6 and we are planning
to use version control in DS6. While playing with VC,
I am surprised to see one single repository project
for multiple projects. Then we are going to have
serious problem - though job names are same on two
different projects, but jobs are completly different
because metadata, logic etc are different in two
profit centers.
How can we handle this problem?
One way is to use view by Initialize Batch and promote
by batch number.
Any more suggestions? Is this changed on higher
versions?
with regards,
Bruce
__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
Version Control - multiple projects
Version Control - multiple projects
<b>PLEASE READ</b>
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Version Control - multiple projects
I'm pretty sure that Version 7 supports multiple VC projects for precisely
this reason.
What we've done for 6 is impement the same thing - multiple projects - by
taking advantage of something. When you launch VC and fill in the connection
values... lie. My Custom menu has a hook to VC which deliberately uses the
wrong password. After you acknowledge the error, you will get the *standard*
connection dialogue which includes which project to connect to. We've got a
VERSION-AAA, VERSION-BBB, etc - one for each 'subject area'.
You have to be careful when connecting that you get into the 'right one' but
it is working for us and (from what I understand) will be easier to manage
under 7.
-craig
-----Original Message-----
From: Bruce William [mailto:bwilliam_ds@yahoo.com]
Sent: Tuesday, January 13, 2004 6:34 AM
To: DataStage
Subject: Version Control - multiple projects
Hi All,
We are moving to DataStage 6 and we are planning
to use version control in DS6. While playing with VC,
I am surprised to see one single repository project
for multiple projects. Then we are going to have
serious problem - though job names are same on two
different projects, but jobs are completly different
because metadata, logic etc are different in two
profit centers.
How can we handle this problem?
One way is to use view by Initialize Batch and promote
by batch number.
Any more suggestions? Is this changed on higher
versions?
with regards,
Bruce
__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
this reason.
What we've done for 6 is impement the same thing - multiple projects - by
taking advantage of something. When you launch VC and fill in the connection
values... lie. My Custom menu has a hook to VC which deliberately uses the
wrong password. After you acknowledge the error, you will get the *standard*
connection dialogue which includes which project to connect to. We've got a
VERSION-AAA, VERSION-BBB, etc - one for each 'subject area'.
You have to be careful when connecting that you get into the 'right one' but
it is working for us and (from what I understand) will be easier to manage
under 7.
-craig
-----Original Message-----
From: Bruce William [mailto:bwilliam_ds@yahoo.com]
Sent: Tuesday, January 13, 2004 6:34 AM
To: DataStage
Subject: Version Control - multiple projects
Hi All,
We are moving to DataStage 6 and we are planning
to use version control in DS6. While playing with VC,
I am surprised to see one single repository project
for multiple projects. Then we are going to have
serious problem - though job names are same on two
different projects, but jobs are completly different
because metadata, logic etc are different in two
profit centers.
How can we handle this problem?
One way is to use view by Initialize Batch and promote
by batch number.
Any more suggestions? Is this changed on higher
versions?
with regards,
Bruce
__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
<b>PLEASE READ</b>
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Version Control - multiple projects
We have used multiple VC projects since DS 4.2. The Version tool expects a
project named VERSION, but if it does not exist, it prompts the user for the
correct project. Once a different project named is used, that becomes the new
default. In fact, if a user needs to access more than one VC project (like me,
the DS Administrator), I need to enter either a bad logon or password in order
to be prompted for a specific project. I used VC project names like
VERSION_PROJ1.
-Doug
-----Original Message-----
From: Bruce William [mailto:bwilliam_ds@yahoo.com]
Sent: Tuesday, January 13, 2004 7:34 AM
To: DataStage
Subject: Version Control - multiple projects
Hi All,
We are moving to DataStage 6 and we are planning
to use version control in DS6. While playing with VC,
I am surprised to see one single repository project
for multiple projects. Then we are going to have
serious problem - though job names are same on two
different projects, but jobs are completly different
because metadata, logic etc are different in two
profit centers.
How can we handle this problem?
One way is to use view by Initialize Batch and promote
by batch number.
Any more suggestions? Is this changed on higher
versions?
with regards,
Bruce
__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
project named VERSION, but if it does not exist, it prompts the user for the
correct project. Once a different project named is used, that becomes the new
default. In fact, if a user needs to access more than one VC project (like me,
the DS Administrator), I need to enter either a bad logon or password in order
to be prompted for a specific project. I used VC project names like
VERSION_PROJ1.
-Doug
-----Original Message-----
From: Bruce William [mailto:bwilliam_ds@yahoo.com]
Sent: Tuesday, January 13, 2004 7:34 AM
To: DataStage
Subject: Version Control - multiple projects
Hi All,
We are moving to DataStage 6 and we are planning
to use version control in DS6. While playing with VC,
I am surprised to see one single repository project
for multiple projects. Then we are going to have
serious problem - though job names are same on two
different projects, but jobs are completly different
because metadata, logic etc are different in two
profit centers.
How can we handle this problem?
One way is to use view by Initialize Batch and promote
by batch number.
Any more suggestions? Is this changed on higher
versions?
with regards,
Bruce
__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
<b>PLEASE READ</b>
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Version Control - multiple projects
Thanks Craig and Doug.
Its a nice workaround!
but still I have a doubt ..
whether VC 6 is designed to support multiple
repositories?
Also had you faced any problems like loosing design or
jobs getting corrupted in VC.
with regards,
Bruce
--- "Hall, Doug" wrote:
>
> We have used multiple VC projects since DS 4.2. The
> Version tool expects a
> project named VERSION, but if it does not exist, it
> prompts the user for the
> correct project. Once a different project named is
> used, that becomes the new
> default. In fact, if a user needs to access more
> than one VC project (like me,
> the DS Administrator), I need to enter either a bad
> logon or password in order
> to be prompted for a specific project. I used VC
> project names like
> VERSION_PROJ1.
>
> -Doug
>
> -----Original Message-----
> From: Bruce William [mailto:bwilliam_ds@yahoo.com]
> Sent: Tuesday, January 13, 2004 7:34 AM
> To: DataStage
> Subject: Version Control - multiple projects
>
>
> Hi All,
> We are moving to DataStage 6 and we are
> planning
> to use version control in DS6. While playing with
> VC,
> I am surprised to see one single repository project
> for multiple projects. Then we are going to have
> serious problem - though job names are same on two
> different projects, but jobs are completly different
> because metadata, logic etc are different in two
> profit centers.
> How can we handle this problem?
> One way is to use view by Initialize Batch and
> promote
> by batch number.
> Any more suggestions? Is this changed on higher
> versions?
>
> with regards,
> Bruce
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Hotjobs: Enter the "Signing Bonus"
> Sweepstakes
> http://hotjobs.sweepstakes.yahoo.com/signingbonus
__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
Its a nice workaround!
but still I have a doubt ..
whether VC 6 is designed to support multiple
repositories?
Also had you faced any problems like loosing design or
jobs getting corrupted in VC.
with regards,
Bruce
--- "Hall, Doug" wrote:
>
> We have used multiple VC projects since DS 4.2. The
> Version tool expects a
> project named VERSION, but if it does not exist, it
> prompts the user for the
> correct project. Once a different project named is
> used, that becomes the new
> default. In fact, if a user needs to access more
> than one VC project (like me,
> the DS Administrator), I need to enter either a bad
> logon or password in order
> to be prompted for a specific project. I used VC
> project names like
> VERSION_PROJ1.
>
> -Doug
>
> -----Original Message-----
> From: Bruce William [mailto:bwilliam_ds@yahoo.com]
> Sent: Tuesday, January 13, 2004 7:34 AM
> To: DataStage
> Subject: Version Control - multiple projects
>
>
> Hi All,
> We are moving to DataStage 6 and we are
> planning
> to use version control in DS6. While playing with
> VC,
> I am surprised to see one single repository project
> for multiple projects. Then we are going to have
> serious problem - though job names are same on two
> different projects, but jobs are completly different
> because metadata, logic etc are different in two
> profit centers.
> How can we handle this problem?
> One way is to use view by Initialize Batch and
> promote
> by batch number.
> Any more suggestions? Is this changed on higher
> versions?
>
> with regards,
> Bruce
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Hotjobs: Enter the "Signing Bonus"
> Sweepstakes
> http://hotjobs.sweepstakes.yahoo.com/signingbonus
__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
<b>PLEASE READ</b>
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Version Control - multiple projects
On the issue of 'designed to support', I think technically your answer is
'no'. However, it *does* work fine and the only change in v7 (that I am
aware of) to add that support is removing the need to fail the first logon
to get the project selector.
And, no, I've never had it lose or corrupt anything. As with any collection
of projects, make sure you have ample room whereever DataStage is installed.
Running out of disk space is a *guarenteed* way to corrupt jobs.
-craig
-----Original Message-----
From: Bruce William [mailto:bwilliam_ds@yahoo.com]
Sent: Tuesday, January 13, 2004 9:05 PM
To: datastage-users@oliver.com
Subject: RE: Version Control - multiple projects
Thanks Craig and Doug.
Its a nice workaround!
but still I have a doubt ..
whether VC 6 is designed to support multiple
repositories?
Also had you faced any problems like loosing design or
jobs getting corrupted in VC.
with regards,
Bruce
--- "Hall, Doug" wrote:
>
> We have used multiple VC projects since DS 4.2. The
> Version tool expects a
> project named VERSION, but if it does not exist, it
> prompts the user for the
> correct project. Once a different project named is
> used, that becomes the new
> default. In fact, if a user needs to access more
> than one VC project (like me,
> the DS Administrator), I need to enter either a bad
> logon or password in order
> to be prompted for a specific project. I used VC
> project names like
> VERSION_PROJ1.
>
> -Doug
>
> -----Original Message-----
> From: Bruce William [mailto:bwilliam_ds@yahoo.com]
> Sent: Tuesday, January 13, 2004 7:34 AM
> To: DataStage
> Subject: Version Control - multiple projects
>
>
> Hi All,
> We are moving to DataStage 6 and we are
> planning
> to use version control in DS6. While playing with
> VC,
> I am surprised to see one single repository project
> for multiple projects. Then we are going to have
> serious problem - though job names are same on two
> different projects, but jobs are completly different
> because metadata, logic etc are different in two
> profit centers.
> How can we handle this problem?
> One way is to use view by Initialize Batch and
> promote
> by batch number.
> Any more suggestions? Is this changed on higher
> versions?
>
> with regards,
> Bruce
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Hotjobs: Enter the "Signing Bonus"
> Sweepstakes
> http://hotjobs.sweepstakes.yahoo.com/signingbonus
__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
'no'. However, it *does* work fine and the only change in v7 (that I am
aware of) to add that support is removing the need to fail the first logon
to get the project selector.
And, no, I've never had it lose or corrupt anything. As with any collection
of projects, make sure you have ample room whereever DataStage is installed.
Running out of disk space is a *guarenteed* way to corrupt jobs.
-craig
-----Original Message-----
From: Bruce William [mailto:bwilliam_ds@yahoo.com]
Sent: Tuesday, January 13, 2004 9:05 PM
To: datastage-users@oliver.com
Subject: RE: Version Control - multiple projects
Thanks Craig and Doug.
Its a nice workaround!
but still I have a doubt ..
whether VC 6 is designed to support multiple
repositories?
Also had you faced any problems like loosing design or
jobs getting corrupted in VC.
with regards,
Bruce
--- "Hall, Doug" wrote:
>
> We have used multiple VC projects since DS 4.2. The
> Version tool expects a
> project named VERSION, but if it does not exist, it
> prompts the user for the
> correct project. Once a different project named is
> used, that becomes the new
> default. In fact, if a user needs to access more
> than one VC project (like me,
> the DS Administrator), I need to enter either a bad
> logon or password in order
> to be prompted for a specific project. I used VC
> project names like
> VERSION_PROJ1.
>
> -Doug
>
> -----Original Message-----
> From: Bruce William [mailto:bwilliam_ds@yahoo.com]
> Sent: Tuesday, January 13, 2004 7:34 AM
> To: DataStage
> Subject: Version Control - multiple projects
>
>
> Hi All,
> We are moving to DataStage 6 and we are
> planning
> to use version control in DS6. While playing with
> VC,
> I am surprised to see one single repository project
> for multiple projects. Then we are going to have
> serious problem - though job names are same on two
> different projects, but jobs are completly different
> because metadata, logic etc are different in two
> profit centers.
> How can we handle this problem?
> One way is to use view by Initialize Batch and
> promote
> by batch number.
> Any more suggestions? Is this changed on higher
> versions?
>
> with regards,
> Bruce
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Hotjobs: Enter the "Signing Bonus"
> Sweepstakes
> http://hotjobs.sweepstakes.yahoo.com/signingbonus
__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
<b>PLEASE READ</b>
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.