Issue with Cleanup Resources Dialog

Christina Lim · Post by **Christina Lim** » Fri Oct 17, 2008 6:07 am

Hi....

I've tried search the forum but unable to find the answer i needed.

I have some jobs hang, unable to unlock or released..

I launched Cleanup resources dialog and able to see the PID #
PID # = 1073402
Context= Controller
User Name = dsadm
Last Command Processed = SH -c 'touch RT_SC287/jpfile.484B475F50445F4...' [ DSD.OshRun @ 0xC56]

Show by job Option ticked, Logout All- Yes
but the job is still there.. unable to logout. This is a mutiple instance name. and checking from LIST.READU unable to yeild any info.

bin/uv -admin -info

40646 dsadm 1073402 1 0 18:36:46 - 0:01 phantom DSD.RUN PCA_R_BXXX

I can see the process id, 1073402 matches the pid as per cleanup resources but unable to kill this job. Tried kill 1073402 from unix command and this job is unable to kill.

2nd issue:
bin/uv -admin -info
User Segments : 14 active
I found some active segments is actually not active.
As checked from Cleanup Resources/Show All, found a lot pid with below info:

PID # = 12740914
Context = Unavailable
User Name = dsadm
Last Command Processed=Unavailable

How do i kill the pid from ds? from unix this pid is no longer exists.

Appreciate your comment.

ArndW · Post by **ArndW** » Fri Oct 17, 2008 7:18 am

Due to historical reasons, DS sometimes cuts off PID numbers (back in the old PRIMOS days they didn't envision 6-digit pids). If you do a

Code: Select all

ps -ef | grep 1073402

are any processes shown?

Christina Lim · Post by **Christina Lim** » Fri Oct 17, 2008 7:33 am

Yes the processes is shown..

dsadm 1073402 1 0 18:36:46 - 0:04 phantom DSD.RUN PCA_R_BATCHcountNumRecs.HKG_PD_Commission_CSV 0/0 factTab="F_C1P1P2UA1A2" ...

However, i tried execute:
kill 1073402
This does not work, and when i Tried Kill -9 <pid>, it's killed but in cleanup resources dialog it return

PID # = <PID>
Context = Unavailable
User Name = dsadm
Last Command Processed=Unavailable

and the subsequent test run on the job failed.. job will hang like above.

ArndW · Post by **ArndW** » Fri Oct 17, 2008 7:59 am

Never use "kill -9", it will ensure that the process is gone in the OS but it will remain in DataStage and potentially block processing because it holds locks and resources.
From UNIX, in the same $DSHOME directory as before, do a

1. "bin/dssh"
2. "LIST.READU EVERY"
3. "QUIT"

does the PID show up?

mmanes · Post by **mmanes** » Thu Oct 23, 2008 10:12 am

in uv environment

LOGTO <project>
LIST.READU

UNLOCK DEVICE <device no> INODE <inode no> READULOCK

or

UNLOCK ALL USER <user no>

bye

ArndW · Post by **ArndW** » Thu Oct 23, 2008 10:30 am

mmanes - the commands are correct, but don't help much in this case. The device/inode numbers as well as the "user no" (not the pid) can be retrieved using the "LIST.READU EVERY" command and the user needs administrator rights in order to execute the commands.