DSXchange

Hi,

How do you see structure of Datastage tables like DS_JOBS?

I am looking to a command similiar to Oracle's Describe <tablename>.


Thanks

Ketfos

Some aspects of tables like that are specifically hidden from prying eyes, or so others have said in this forum. But... you can use "LIST DICT" to list the dictionary for any given object.

Hi,
Thanks.

The reason I asked was --
I have job which I am not able to delete.

It gives error message on deleting

Cannot open execute job file RT_CONFIG740

Can I delete it from DS_JOBS using the JOBNO 740.
Is this the right way?

Thks

Ketfos

No. If you do that you end up with orphan tables (though these can, in theory, be cleaned up from DS.TOOLS menu). Worse, you get lots of orphan records in DS_JOBOBJECTS, and the DS.TOOLS utility does not (as of version 7.1) clean these up.

Better is to figure out why RT_CONFIG740 is giving problems. Or simply CLEAR.FILE RT_CONFIG740 then try deleting the job from a DataStage client.

Yes, I agree do not play with the RT_ files. I would assure there are no orphaned locks and all PIDs are killed. After that I would DS.REINDEX ALL. The I would try deleting.

Reindexing will not help if one of the hashed files has become corrupted. Indeed, the reindexing will fail to complete successfully in this case.

That said, RT_CONFIGnnn is one of the least likely (smallest) hashed files in the repostory to become corrupted. It's only updated at compile time.

More to the point, RT_CONFIGnnn files are not indexed, so reindexing would not be any help at all in this case.

CLEAR.FILE wipes out all internal content, including any corruption, so is the quickest way to get a corrupted file prepared for deletion.

ketfos ran out of disk space on the project filesystem, so there's a lot of bits and pieces that could be a mess. When this happens, sometimes it's easiest to export all your jobs (and verify) then delete the project and recreate it. Then import your jobs again and continue.

Don't run out of disk space!!!! Bad things happen.

Hi Ray and Ken,

This happens when I try to run
CLEAR.FILE RT_CONFIG740; ======= COMMAND IN Administrator

Unable to clear file RT_CONFIG740;.

CLEAR.FILE RT_CONFIG740 ======= COMMAND IN Administrator (no semicolon)

Cannot open file "RT_CONFIG740"
***Processing cannot continue. ***

Ketfos

You ran out of disk space, you have orphaned pieces and parts of a hash file. Export this job and re-import it.

Yes, RT_CONFIG740 is so badly damaged - it was probably being written to when the disk full condition occurred - that even CLEAR.FILE won't work. This suggests that it's header block has become corrupted.

Export the job (which doesn't use RT_CONFIG740) and import it (which will generate a new set of repository files and a new job number). And make sure you don't run out of disk space!

Hi Ray and Ken,

I exported another job (which doesnot use RT_CONFIG740) and imported it sucessfully.

But when I try to open the job / or delete the job / rename the job with RT_CONFIG740, I still get the same message

"Cannot open executable job file RT_CONFIG740"

Ketfos

The job you have to export is the one currently numbered 740, not "another job". Then import that one.

My point was that the export does not use RT_CONFIGnnn, rather than suggesting that you should export a different job. Sorry about the confusion.

Hi,

Thks for clarification.

1. I could export in question the job using Manager.

2. When I try to import it, I get the same error message

Cannot open execute job file RT_CONFIG740

3. Also when i view Director, the job is not listed.

4. When I view Designer / Manager the Job is listed.

Ketfos

Take another RT_CONFIG file/directory in your unix project and copy it to the errant/missing name. This will at least allow you to import the job or delete it. As I keep telling everyone, it's BAD to run out of disk space on your project.

kcbland wrote:Take another RT_CONFIG file/directory in your unix project and copy it to the errant/missing name. This will at least allow you to import the job or delete it. As I keep telling everyone, it's BAD to run out of disk space on your project.

I am having a similar problem. I copied an existing RT_CONFIG file and copied it to the missing file name. I am still unable to delete the job or import the job.