JR31617: SCHEDULED JOB DOES NOT START.

APAR status

• Closed as program error.

Error description

• Scheduled jobs do not start intermittently and randomly.
  This is not cron problem. Customer defined queuedef to permit
  2000 cron jobs. And cron log shows that the scheduled jobs were
  called normally but fail.
  

Local fix

• This fix is included in 8.0.1 fixpack 3
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Problem seen when multiple jobs are started at the same time
  with cron on AIX
  ****************************************************************
  PROBLEM DESCRIPTION:
  When multiple jobs are scheduled with cron to start at the same
  hh:mm, one may fail to start. The Director job will show one
  line with DS.SCHED: Started at... but nothing more.  The cron
  log will show that a particular pid failed. This problem has
  thepotential of happening on any UNIX platform but has only been
    reported against AIX at this point.
  ****************************************************************
  RECOMMENDATION:
  5.2 is available.
  This change is included in 8.1 Fix Pack 1.
  ****************************************************************
  

Problem conclusion

• The customer's problem is caused by the attempt to use the same
  shared memory segment to start each scheduled job.  Setting the
  environment variable DSE_PID_SIGNATURE in $DSHOME/dsenv to 1
  will result in generating a more unique shared memory segment
  key.
  

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:

Modules/Macros

• SERVER
  

Fix information

• Fixed component name

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R752 PSY

     UP