APT_PM_CONDUCTOR_TIMEOUT and APT_PM_NODE_TIMEOUT

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
just4geeks
Premium Member
Premium Member
Posts: 644
Joined: Sat Aug 26, 2006 3:59 pm
Location: Mclean, VA

APT_PM_CONDUCTOR_TIMEOUT and APT_PM_NODE_TIMEOUT

Post by just4geeks »

Hi All,

Can you please guide me what is the difference between APT_PM_CONDUCTOR_TIMEOUT and APT_PM_NODE_TIMEOUT and how they impact performance/execution of the job?

I see from a previous post:
APT_PM_CONDUCTOR_TIMEOUT controls the number of seconds a section leader will wait for a response from the conductor before aborting.

APT_PM_NODE_TIMEOUT controls the number of seconds that the conductor will wait for a section leader to start up and load a score before assuming something has failed. The default for starting a section leader process is 30. The default for loading a score is 12
0.

Can you please confirm if this is correct as name created some confusion in my mind.

In Parallel Advance developer guide only APT_PM_NODE_TIMEOUT is described.

Thanks for all your help!
Attitude is everything....
PaulVL
Premium Member
Premium Member
Posts: 1315
Joined: Fri Dec 17, 2010 4:36 pm

Post by PaulVL »

What symptom are you trying to cure?
just4geeks
Premium Member
Premium Member
Posts: 644
Joined: Sat Aug 26, 2006 3:59 pm
Location: Mclean, VA

Post by just4geeks »

I am just trying to understand both of them because one of the developers asked us to set both to same value ( 480) without providing any reason. So I would like to know what each variable means and its impact on execution of the job.
Attitude is everything....
JPalatianos
Premium Member
Premium Member
Posts: 306
Joined: Wed Jun 21, 2006 11:41 am

Post by JPalatianos »

What you have posted is corrcet. We have just implemented the two in our shop as it seems the start up of the parallel processes is being affected by our Virus Software (Windows).

FYI...Windows has another parmeter which is similar to those mentioned in your post.

APT_PM_PLAYER_CONNECT_TIMEOUT
This controls the number of seconds that the section
leader will wait for exec'd player processes to connect
before giving up and aborting. Default is 60 seconds.
This environment variable is specific to Windows.

- - John
just4geeks
Premium Member
Premium Member
Posts: 644
Joined: Sat Aug 26, 2006 3:59 pm
Location: Mclean, VA

Post by just4geeks »

Thanks John for the help!
Attitude is everything....
just4geeks
Premium Member
Premium Member
Posts: 644
Joined: Sat Aug 26, 2006 3:59 pm
Location: Mclean, VA

Post by just4geeks »

Thanks John and Paul for the help!
Attitude is everything....
sezerman
Participant
Posts: 17
Joined: Fri Nov 14, 2008 9:57 am

Post by sezerman »

Hi ,

I have a similar problem. I need to know if APT_PM_CONDUCTOR_TIMEOUT has any disadvantages ? Thanks for helping,
igorlp
Participant
Posts: 10
Joined: Thu Mar 09, 2006 2:13 am

Post by igorlp »

JPalatianos wrote:APT_PM_PLAYER_CONNECT_TIMEOUT
Hi, how i can add this parameter? i have not them in parallel parameters list.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

As a general rule anything with an all upper-case name is an environment variable. Project environment variables are maintained using the Administrator client. You can add environment variables to those supplied "out of the box".
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply