JR47074: VARIABLE ISUSER IS NOT BEING SET WHEN JOB IS SCHEDULED VIA DIRECTOR TO RUN DAILY OR TOMORROW.

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

• Customer is defining an ISUSER parameter in sequence jobs.
  Regardless of what job they run in production, if it is run
  manually, ISUSER is set to the userid of the person that was
  logged into Datastage that executed the job.  If the job is
  scheduled, ISUSER is not set in the environment variables. In
  their pre-production environments, ISUSER is set regardless of
  if it is executed manually from Director or scheduled in
  Director (i.e. the user id of the person that schedules the job
  is set in ISUSER).
  When Add to Schedule is selected and the job is scheduled to run
  "Today" at a certain time, the job is scheduled using the "AT"
  command.
  The environment is also recorded which is how the IUSUSER value
  gets set.
  Likewise, if you schedule the same job to run "Daily" or
  "Tomorrow", etc, the job is scheduled using the CRONTAB.
  In this case, the environment is not recorded, and the ISUSER
  variable is not included in the run of the job.
  

Local fix

• Executed jobs manually
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Affects all users of the scheduling activity within the director
  ****************************************************************
  PROBLEM DESCRIPTION:
  On UNIX scheduling with multi-run scheduling the ISUSER
  environment
  variable is not set but it is on single-run scheduling. The
  problem
  is evident for all runs on Windows.
  ****************************************************************
  RECOMMENDATION:
  If it is required to use the ISUSER variable then a patch should
  be applied.
  ****************************************************************
  

Problem conclusion

• The ISUSER variable is set as a psuedo job variable in the
  scheduling data for the run, from there it will be picked up and
   appliedto the environment when the job is run. THe variable
  will be the ISUser that invoked the director.
  

Temporary fix

• The temporary solution is to explicitly set the variable to some
   value as part of the job run.
  

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

• R910 PSY

     UP