JR45646: THE OSH PART OF PARALLEL JOBS REQUIRE DIFFERENT PATH/LIBPATH SETTINGS FROM BEFORE/AFTER SUBROUTINES AND JOB CONTROL CODE

IBM 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
IBM InfoSphere Information Server Enterprise Edition V11.3 for Windows

APAR status

• Closed as program error.

Error description

• The osh part of parallel jobs require different PATH/LIBPATH
  settings from before/after subroutines and job control code.
  
  Currently, the Server job contains the PX LIBPATH prefix which
  loads the incorrect version of the framework library causing a
  server job runtime failure due to a library load error.
  

Local fix

Problem summary

• Customer is using custom job control code in a parallel job to
  run a server job that uses the DB2 Connector. The server job
  fails invoking the DB2 connector component.
  The Connector framework means that the connector can run in
  three different environments.
  1. within the ASBAgent CAS Handler
  2. within a parallel job
  3. within a server job.
  In each of these environments it requires a different libfcl.so
  library so we install three different
  versions of this in
  ASBNode/lib/cpp/libfcl.so
  PXEngine/lib/libfcl.so
  DSEngine/lib/libfcl.so
  and we require different PATH and LIBPATH settings in order to
  load the correct one.
  In the customer scenario the child server job has the wrong
  LIBPATH setting and fails because of this.
  This is because the parent parallel job has already setup the
  parallel job LIBPATH before it calls
  the DSBasic job control code that starts the child server job
  and as a result the server job inherits
  the wrong LIBPATH setting.
  

Problem conclusion

• We need to change the code in DSD.RUN to defer calling
  DSD.OshInit, which sets the LIBPATH and PATH
  environment variables for parallel jobs, until just before it
  calls DSD.OshRun to start the parallel job.
  We also need to restore the original PATH and LIBPATH
  environment variable settings on return from
  DSD.OshRun.
  Just in case this change has any unintended side-effects it will
  be possible to revert to the original behavior
  by setting an environment variable DS_OLD_OSHINIT=1
  

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