Is this same third party product which creates a version project?
Do you know what is costs?
Phil.
> -----Original Message-----
> From: Allen Spayth - wwc [SMTP:
daspayth@wwc.com]
> Sent: Thursday, May 10, 2001 11:11 AM
> To:
informix-datastage@oliver.com
> Subject: Re: Released Jobs
>
> Actually there is a trivial resolution should it be required. First
> export the released job(s) then edit the export file.
> Do a global replace of: Readonly "1" with Readonly "0"
>
> Then re-import the dsx file. You should then be able to modify/rename
> etc the job(s). Remember that this could be dangerous and I would not
> expect this to be a "supported feature" by any means of the
> imagination but it certainly could get you out of a bad situation
> should you loose your original source code.
>
> Speaking of source code Ascential is now selling a pretty good
> Version Control software addon for DataStage which is significantly
> more advanced than the "release-jobs" concept of version control.
> This in-expensive add-on supports full rollback, compile, read-only,
> check-in/check-out and more. The concept is to have a VERSION project
> that you can import from development projects and then publish to
> test/production. It supports sub-versions of objects such that a
> routine may be at version 1.2 and the
> job(s) may be at version 3.1 and the whole "release" may be at 4.0. You
> can also have it create the hash files for you when it publishes to the
> production project/server. I recommend that everyone take a quick look at
> this productivity enhancer.
>
> Regards,
>
> Allen
>
>
>
> ----- Original Message -----
> From: "Moderator"
> To:
> Sent: Wednesday, May 09, 2001 3:30 PM
> Subject: Re: Released Jobs
>
>
> > Now I would think that might be something Support could help with,
> > could it not? (Or would it not?)
> >
> > Regards,
> >
> > Clif
> >
> >
> > Wednesday, May 09, 2001, 4:35:06 PM, you wrote:
> >
> > > It can be done through the "back door" so to speak, but this ought
> > > not
> to be
> > > undertaken without a thorough knowledge of the underlying
> > > DataStage repository structures.
> >
> >