JR52879: DSJOB WITH -WAIT OPTION GETTING CLIENT/SERVER TIMEOUT EXCEEDED MAY NOT ALWAYS RETURN CORRECTLY

IBM InfoSphere Information Server, Version 11.3.1.2 (Fix Pack 2)

APAR status

• Closed as program error.

Error description

• When a job run exceeds the client/server timeout and dsjob is
  used with the -wait option then dsjob does not always return
  correctly.
  Specifically, "dsjob" command hangs while exiting to return to
  calling Shell script.
  

Local fix

• No longer use the "-wait", or combined "-wait -userstatus"
  options of the "dsjob" command, but use a waiting loop in the
  calling script instead.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This problem only impacts users where a client/server
  connectivity timeout has been specified and the dsjob
  command is used to run and wait for jobs which run for longer
  then the timeout.
  ****************************************************************
  PROBLEM DESCRIPTION:
  The problem is that after the session has disconnected and
  the connection is closed the code continues to use the
  connection.
  ****************************************************************
  RECOMMENDATION:
  Apply the patch for JR52879
  ****************************************************************
  

Problem conclusion

• Modified the code to not use the connection if the last error
  was a connection broken error. Also stopped the termination code
   from making inappropriate calls if for example domain login had
   not been used.
  

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

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R910 PSY

     UP

• R912 PSY

     UP