Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.
Moderators: chulett , rschirm , roy
Hema.k
Participant
Posts: 43 Joined: Wed Dec 30, 2009 3:28 am
Post
by Hema.k » Wed Apr 04, 2012 1:17 am
Hi All,
We are facing the error code -14 frequently.
When I checked in the forum, i understood that it is due to DS server overloaded.
Is there any way to check the no of process running on the DS at a particular time when the job got aborted.
Thanks in advance,
Regards,
Hema K
arvind_ds
Participant
Posts: 428 Joined: Thu Aug 16, 2007 11:38 pm
Location: Manali
Post
by arvind_ds » Wed Apr 04, 2012 3:39 am
use the below command to check the number of processes running on a unix server.
ps -ef
ps -ef | grep DSD.RUN
ps -ef | grep <user name may be dsadm>
topas
Arvind
chulett
Charter Member
Posts: 43085 Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO
Post
by chulett » Wed Apr 04, 2012 8:19 am
Your SysAdmin(s) should have logs that track that kind of information. Not that particular measure but process / usage stats certainly.
-craig
"You can never have too many knives" -- Logan Nine Fingers
PaulVL
Premium Member
Posts: 1315 Joined: Fri Dec 17, 2010 4:36 pm
Post
by PaulVL » Wed Apr 04, 2012 12:01 pm
A job abort causes a lot of processes to terminate so you won't actually catch the exact count.
ray.wurlod
Participant
Posts: 54607 Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:
Post
by ray.wurlod » Wed Apr 04, 2012 3:21 pm
One...
Two...
Many...
LOTS!!!
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.