Unable to end the Process DSD.OshMonitor MSEVENTS.FALSE

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

Post Reply
kagliwal.a
Participant
Posts: 2
Joined: Tue Jan 10, 2017 12:01 am

Unable to end the Process DSD.OshMonitor MSEVENTS.FALSE

Post by kagliwal.a »

Hello Experts,

We are facing some strange issue in our job.
Job is getting completed but taking more than 1-2 hours to return its status to the head node.
Below is the output from the logs:

Item #: 111
Event ID: 4151752
Timestamp: 2017-07-25 02:58:36
Type: Info
User Name: test
Message Id: IIS-DSTAGE-RUN-I-0124
Message: Parallel job reports successful completion
Item #: 112
Event ID: 4152177
Timestamp: 2017-07-25 03:58:34
Type: Control
User Name: test
Message Id: IIS-DSTAGE-RUN-I-0077
Message: Finished Job <jobname>


Also we have check from our end that the load and other parameters are normal.
While checking from backend we found that there is still process running even after the job has been successfully completed.
Below is the output of command after job has been finished.

ps -ef | grep -i <Jobname>
test 10144 1 99 Jul24 ? 1-02:20:41 phantom DSD.OshMonitor <jobname> 9411 MSEVENTS.FALSE
root 13692 9540 0 05:19 pts/0 00:00:00 grep --color=auto -i <jobname>

Thanks in advance :)
priyadarshikunal
Premium Member
Premium Member
Posts: 1735
Joined: Thu Mar 01, 2007 5:44 am
Location: Troy, MI

Post by priyadarshikunal »

Did you check if you have any after job subroutine in that job?
Priyadarshi Kunal

Genius may have its limitations, but stupidity is not thus handicapped. :wink:
kagliwal.a
Participant
Posts: 2
Joined: Tue Jan 10, 2017 12:01 am

Post by kagliwal.a »

Yes I checked, there is no job sub routine after that job.
Earlier it used to take just 12 min to finish the job but from the last 2 days it is taking more than 1 hrs as job is getting stuck at a particular point.
Also we have find the process from background:
test 10144 1 99 Jul24 ? 1-02:20:41 phantom DSD.OshMonitor <jobname> 9411 MSEVENTS.FALSE
root 13692 9540 0 05:19 pts/0 00:00:00 grep --color=auto -i <jobname>
from that day only.
priyadarshikunal
Premium Member
Premium Member
Posts: 1735
Joined: Thu Mar 01, 2007 5:44 am
Location: Troy, MI

Post by priyadarshikunal »

you can try setting APT_NO_JOB_MON = 'True' just to check if its the job monitor which is causing the problem.

Above enviornment variable changes will disable the monitoring and the statistics will not be visible in director.
Priyadarshi Kunal

Genius may have its limitations, but stupidity is not thus handicapped. :wink:
Post Reply