How to modify a DI job?

[sfffdg]

Hi ,

I am bit new to the sas DI Studio.

In our company ,We develop code in sas DI Studio then , we promote the code to the MainFrames.

I have to change a job , which is developed some years ago.

When I opened the job in sas di studio, the job is completely messed up and not at all reliable. ( as the job is not locked and some body has messed it up )

then I  copied the job from Mainframes .( I have the actual  code with me now)

Based on the Production code, I developed the new job again.

But the problem with this is , the code is not matching.

how can I correct my job ?

[r_behata]

The most efficient way to restore a DI job is through the metadata restore. See if you have a backup of the Metadata.

Often times the underlying Metadata tables might be deleted/ renamed / moved in the Non-Production environment, it does not necessarily mean that the Job is corrupted.

If the Job metadata was never backed up originally, you may try taking the backup of the current job and try to restore it in the same environment. While restoring, the process would prompt you to map the table metadata if it is unable to find the tables in the default locations.

[sfffdg]

Hi behata,

Thanks for the reply, definitely will try to take the back up of the job and restore in the same environment as there is no back up for the job.
But In case if I want to develop from the scratch,is it possible?if possible please guide me through the challenges with it..

Thanks a lot!!

[Patrick]

This question is closely related to another one here.

[ChrisNZ]

Changed title from "Help needed in understanding some challenges in the job developed" to "How to modify a DI job?"

[LinusH]

So your mainframe code works, but the code from the messed up DI Studio job doesn't?

If you sreuggke to reproduce the job, I would start of using the Code Importer. That won't be as pretty as job crafted by a decent DI developer. Either you're fine with that, or use that as a reference when rebuilding the job by hand.
Regardless you need to do thorough testing so you get the same/expected result.