IT06516: MAX RUN TASK FORWARDING TIMEOUT PARAMETER NOT BEING HONORED.

APAR status

• Closed as program error.

Error description

• When delivering a file and then executing a script on a remote
  CD Server Node, if that script takes longer than x seconds
  then we want the Run Task to time-out. The Max Run Task
  Forwarding Timeout prarmeter is not being honored.
  
  This would require adding a new parameter coded in the
  Connect:Direct run task service, for instance, MaxTimeToWait
  (in seconds), to specify how long to wait for the remote node
  to complete task execution and respond before timing out.
  

Local fix

• STRRTC - #449773
  GM / GM
  Circumvention: No workaround available.
  

Problem summary

• Users Affected:
  All
  
  Problem Description:
  The time in which the Connect Direct Run Task Service will wait
  on a task running on the remote CD SNODE is determined by the
  Connect Direct Server Adapter's "Socket Read Timeout"
  parameter.  This imposes a minimum timeout of 90 seconds and
  changing this affects all sessions using this adapter, whether
  or not they use the Connect Direct Run Task Service.
  
  Platforms affected:
  All
  

Problem conclusion

• Resolution Summary:
  A new Connect Direct Run Task Service parameter has been
  introduced called 'MaxTimeToWait' to override the behavior of
  the Connect Direct Server Adapter's Read Socket Timeout
  parameter.  The new parameter's purpose is to provide a maximum
  period of time (in seconds) in which the Connect Direct Run
  Task Service is willing wait for the task executing on the
  remote CD SNODE to complete. If the parameter is not
  specified, a default value of 90 seconds is used.
  
  Delivered In:
  5020500_3
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  STR B2B INTEGRA

• Fixed component ID

  5725D0600

Applicable component levels

• R525 PSY

     UP