DSXchange

Chulett, Thanks for replying promptly.

The job finishes successfully from the command line with following messages

Error 81002 waiting for job
status code 141

How do we determine and settle this warning.


Thanks

What if the session is timed out, and we get a broken connection error 81002, despite the fact the job completed successfully.

What if the session is timed out, and we get a broken connection error 81002, despite the fact the job completed successfully.

If a dsjob command is used from command line with nohup.
what would be the impact if the unix session timesout?
Would it still run without a broken connection (81002).


Thanks

Yes. Simply take a copy of it. Copy the permissions as well. cp -irp hashedfiledir /otherdir/hashedfiledir ... Ray, Which hashed file are we talking about here? Any directory starting with D or DS is a hashed file directory containing three files (DATA.30, OVER.30 and .Type30). Can you please guide...

Ray,

For the backup, are you refering to the dynamic hashed file directory which has three files DATA.30, OVER.30 and .Type30.

Thanks for your help.

Gentlemen, Tell me how to fix the ds_jobobjects using fixtool, i never used it, well after we deleted the corrupted project and imported a fresh one, we still faced some issues while doing an export by category, it threw the DataStage DSR_SELECT action=7 (30107) Error....was resolved after we did a ...

Hi kcbland, We have opened up a ticket with IBM support. here are the steps we will take: Delete this project Import this project from test server I just checked for other projects, did a count ds_jobobjects, it returned records..I guess DS_jobobjectes file is working fine for other projects. since ...

After getting weird error messages e.g Record \J\3185\VO on file DS_JOBOBJECTS cannot be wriiten.. I did count ds_jobobjects and count ds_jobs ( it gave me record counts) but count ds_jobobjects gave me this internal data error File ' dsadm/Ascential/DataStage/Projects/myproject//DS_JOBOBJECTS/OVER....

Thanks for the prompt reply. I already tried to run the dsdlockd -p but it gave a message which I somehow forgot ( no share memory segment , or process not found) Well, the server reboot did work and hanging connections got cleaned up. next time would logout a process from ds.tools instead of a kill...

trying to do a reboot of datastage all processes are killed, because we had hanging processes.. but after doing bin/uv -admin -info ... i still seee Autostart link(s) : /etc/ds.rc Startup script : /dsadm/Ascential/DataStage/DSEngine/sample/ds.rc Cache Segments : 0 active User Segments : 39 active 39...

Thanks Ray...excellent info

Ray, The jobs which are supposedly hanging and not closed properly can be handled by dsdlockd -p , right? Instead of a kill ..... If the jobs are locked and then released from ds.tools or unlock command, would the dsdlockd.log still show the cleanup status. How different is dsdlockd -p than using ds...

ray.wurlod wrote:Do you have the DataStage deadock daemon (dsdlockd) running? ...

Ray the deadlock deamon is not running..

What are the user segments when you do a -admin -info...
I can see 100 active user segments, 74 printer segments abandoned and 26 phantom printer segments!

any clue whats causing this?

uv -admin -info returned this

46570 Zombi: No active process found!

I did a select and it returned 0 records.

>SELECT NAME FROM DS_JOBS WHERE JOBNO='46570';

0 records listed.

Any clues whats going on?


Thanks