JR47068: Intermittent dsjob failures with rc of -1010 or 80011

Download ISF roll-up 1 for InfoSphere Information Server Version 9.1.2
InfoSphere Information Server, Version 11.3 for Microsoft Windows
InfoSphere Information Server, Version 11.3 for AIX
InfoSphere Information Server, Version 11.3 for Linux
Download ISF roll-up 2 for InfoSphere Information Server Version 8.5.0.3
Download ISF roll-up 2 for InfoSphere Information Server Version 9.1.2
IBM InfoSphere Information Server Enterprise Edition V11.3 for Windows
Download ISF roll-up 3 for InfoSphere Information Server Version 9.1.2
Download ISF roll-up 4 for InfoSphere Information Server Version 9.1.2
Download ISF roll-up 5 for InfoSphere Information Server Version 9.1.2
Download ISF roll-up 7 for InfoSphere Information Server Version 9.1.2
Download ISF roll-up 8 for InfoSphere Information Server Version 9.1.2
Download ISF roll-up 2 for InfoSphere Information Server Version 8.7.0.2
Download ISF roll-up 4 for InfoSphere Information Server Version 8.5.0.3
Download ISF roll-up 11 for InfoSphere Information Server Version 9.1.2
Download ISF roll-up 4 for InfoSphere Information Server Version 8.7.0.2
Download ISF roll-up 12 for InfoSphere Information Server Version 9.1.2
Download ISF roll-up 1 for InfoSphere Information Server Version 8.7.0.2
Download ISF roll-up 3 for InfoSphere Information Server Version 8.7.0.2
Download ISF roll-up 10 for InfoSphere Information Server Version 9.1.2

APAR status

• Closed as program error.

Error description

• dsjob command with '-domain host:port' returns 'Status Code =
  -1010 (DSJE_DOMAINLOGTOFAILED)' or 'Status Code = 80011
  (Incorrect system name or invalid user name or password
  provided)' once in a while.
  

Local fix

• use -domain NONE
  

Problem summary

• The Java method to generate a UUID is not always generating a
  unique value when called from multiple process (different JVMs)
  concurrently. This can result in concurrent LOGIN requests from
  different client processes getting the same SessionID. If these
  LOGIN requests that get the same SessionID are from different
  userids, the LOGIN fails. If from the same userid, the LOGIN
  succeeds but will cause issues for the remaining session once
  the first one destroys the session via a LOGOUT. Depending on
  what the remaining client process is doing, you could get
  different errors. This issue can potentally occur with more than
  just dsjob commands.
  

Problem conclusion

• The code was modified to seen the random number generation to
  better assure a unique SessionID from different processes
  calling it concurrently.
  

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

• R850 PSY

     UP

• R870 PSY

     UP