I have a released job that I need to make changes to. I dont have the original unreleased job. Is there any way to make a copy of the released job?
Thanks,
Kenny
Released Jobs
Theres no legal way to do this. Thats the whole point - youve released it into production.
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.
You may be able to view the job design (it will be read only) depending on what version of DataStage you are using, and create it afresh - manually - in a second Designer window.
-----Original Message-----
From: Salstrom, Kenneth [mailto:Kenneth.Salstrom@msnyuhealth.org]
Sent: Thursday, 10 May 2001 04:47
To: DataStage List (E-mail)
Subject: Released Jobs
I have a released job that I need to make changes to. I dont have the original unreleased job. Is there any way to make a copy of the released job?
Thanks,
Kenny
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.
You may be able to view the job design (it will be read only) depending on what version of DataStage you are using, and create it afresh - manually - in a second Designer window.
-----Original Message-----
From: Salstrom, Kenneth [mailto:Kenneth.Salstrom@msnyuhealth.org]
Sent: Thursday, 10 May 2001 04:47
To: DataStage List (E-mail)
Subject: Released Jobs
I have a released job that I need to make changes to. I dont have the original unreleased job. Is there any way to make a copy of the released job?
Thanks,
Kenny
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.
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.
My guess is "would not", since its not working with the documented behaviour of the product. Nothing to stop you asking of course!
Its a very painstaking and time-consuming process to built the missing repository objects from a released design. They (Ascential) *may* be prepared to do it in exchange for consulting fees, but I suspect there are very few Ascential consultants with the necessary expertise. The technique is not documented, even in-house at Ascential AFAIK. So "would not" even becomes "could not".
-----Original Message-----
From: Moderator [mailto:moderator@oliver.com]
Sent: Thursday, 10 May 2001 08:31
To: informix-datastage@oliver.com
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.
Its a very painstaking and time-consuming process to built the missing repository objects from a released design. They (Ascential) *may* be prepared to do it in exchange for consulting fees, but I suspect there are very few Ascential consultants with the necessary expertise. The technique is not documented, even in-house at Ascential AFAIK. So "would not" even becomes "could not".
-----Original Message-----
From: Moderator [mailto:moderator@oliver.com]
Sent: Thursday, 10 May 2001 08:31
To: informix-datastage@oliver.com
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.
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.
>
>
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.
>
>
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.
> >
> >
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.
> >
> >
Hello.
I am Jung-Hee, Jang. I am working for LEXKEN in KOREA.
You cannot change a released job because the jobs readonly column is not "NRO". If you want to change a released job(or save as ...), change the jobss readonly column to "NRO". For example, UPDATE DS_JOB123 SET READONLY = NRO; And Open the job, Save as job.
If you dont know job number(eg. 123), do following SQL statement. SELECT * FROM DS_JOBS WHERE NAME = job name; job name is a released job name.
Good lock to you.
Jung-Hee, Jang
Support Engineer
Email : jhjang@lexken.co.kr
-----Original Message-----
From: Salstrom, Kenneth [mailto:Kenneth.Salstrom@msnyuhealth.org]
Sent: Thursday, May 10, 2001 3:47 AM
To: DataStage List (E-mail)
Subject: Released Jobs
I have a released job that I need to make changes to. I dont have the original unreleased job. Is there any way to make a copy of the released job?
Thanks,
Kenny
I am Jung-Hee, Jang. I am working for LEXKEN in KOREA.
You cannot change a released job because the jobs readonly column is not "NRO". If you want to change a released job(or save as ...), change the jobss readonly column to "NRO". For example, UPDATE DS_JOB123 SET READONLY = NRO; And Open the job, Save as job.
If you dont know job number(eg. 123), do following SQL statement. SELECT * FROM DS_JOBS WHERE NAME = job name; job name is a released job name.
Good lock to you.
Jung-Hee, Jang
Support Engineer
Email : jhjang@lexken.co.kr
-----Original Message-----
From: Salstrom, Kenneth [mailto:Kenneth.Salstrom@msnyuhealth.org]
Sent: Thursday, May 10, 2001 3:47 AM
To: DataStage List (E-mail)
Subject: Released Jobs
I have a released job that I need to make changes to. I dont have the original unreleased job. Is there any way to make a copy of the released job?
Thanks,
Kenny
Tried this, it works. Wonderfully simple solution.
Thanks, Jung-Hee.
-----Original Message-----
From: Jang,JungHee [mailto:jhjang@lexken.co.kr]
Sent: Thursday, 10 May 2001 10:50
To: Kenneth.Salstrom@msnyuhealth.org
Cc: informix-datastage@oliver.com
Subject: RE: Released Jobs
Hello.
I am Jung-Hee, Jang. I am working for LEXKEN in KOREA.
You cannot change a released job because the jobs readonly column is not "NRO". If you want to change a released job(or save as ...), change the jobss readonly column to "NRO". For example, UPDATE DS_JOB123 SET READONLY = NRO; And Open the job, Save as job.
If you dont know job number(eg. 123), do following SQL statement. SELECT * FROM DS_JOBS WHERE NAME = job name; job name is a released job name.
Good lock to you.
Jung-Hee, Jang
Support Engineer
Email : jhjang@lexken.co.kr
-----Original Message-----
From: Salstrom, Kenneth [mailto:Kenneth.Salstrom@msnyuhealth.org]
Sent: Thursday, May 10, 2001 3:47 AM
To: DataStage List (E-mail)
Subject: Released Jobs
I have a released job that I need to make changes to. I dont have the original unreleased job. Is there any way to make a copy of the released job?
Thanks,
Kenny
Thanks, Jung-Hee.
-----Original Message-----
From: Jang,JungHee [mailto:jhjang@lexken.co.kr]
Sent: Thursday, 10 May 2001 10:50
To: Kenneth.Salstrom@msnyuhealth.org
Cc: informix-datastage@oliver.com
Subject: RE: Released Jobs
Hello.
I am Jung-Hee, Jang. I am working for LEXKEN in KOREA.
You cannot change a released job because the jobs readonly column is not "NRO". If you want to change a released job(or save as ...), change the jobss readonly column to "NRO". For example, UPDATE DS_JOB123 SET READONLY = NRO; And Open the job, Save as job.
If you dont know job number(eg. 123), do following SQL statement. SELECT * FROM DS_JOBS WHERE NAME = job name; job name is a released job name.
Good lock to you.
Jung-Hee, Jang
Support Engineer
Email : jhjang@lexken.co.kr
-----Original Message-----
From: Salstrom, Kenneth [mailto:Kenneth.Salstrom@msnyuhealth.org]
Sent: Thursday, May 10, 2001 3:47 AM
To: DataStage List (E-mail)
Subject: Released Jobs
I have a released job that I need to make changes to. I dont have the original unreleased job. Is there any way to make a copy of the released job?
Thanks,
Kenny
Allen,
Exporting, editing the file and reimporting worked and its easy.
Thanks.
Kenny
-----Original Message-----
From: Allen Spayth - wwc [mailto:daspayth@wwc.com]
Sent: Wednesday, May 09, 2001 7:11 PM
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.
>
>
Exporting, editing the file and reimporting worked and its easy.
Thanks.
Kenny
-----Original Message-----
From: Allen Spayth - wwc [mailto:daspayth@wwc.com]
Sent: Wednesday, May 09, 2001 7:11 PM
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.
>
>