IV92447: NEED TO EXPLAIN HOW "OVERLAP DONOTSTART" WORKS IN DETAIL

APAR status

• Closed as documentation error.

Error description

• Explanation of "OVERLAP DONOTSTART" needs to be updated to
  explain better the actual behavior
  
  According to the manual, the next instance should be cancelled
  if the previous JS were still running if DONOTSTART defined.
  http://www.ibm.com/support/knowledgecenter/SSGSPN_9.4.0/com.ibm.
  tivoli.itws.doc_9.4/distr/src_ref/awsrgonoverlap.htm
  parallel
      The next instance is started regardless, and the two
  instances run
       concurrently. This is the default behavior for the job
  stream if
       you do not use the onoverlap keyword.
  enqueue
      The next instance is not started until the previous
  instance has
       completed its run.
  donotstart
      The next instance is not started at all.
  
  
  Scenario:
  Environment:
  MDM: IWS 9.3.0 + FP0002
  
  0. Define a job stream with "ONOVERLAP DONOTSTART"
  -JS is to be launched every 2 minutes.
  -Job duration is 3 minutes.
  
  SCHEDULE MDM#JSEVRY01
  ON RUNCYCLE RULE1 "FREQ=DAILY;"
  ( AT 945 EVERY 0002 EVERYENDTIME 1010)
  ONOVERLAP DONOTSTART
  :
  MDM#JOB001
  END
  
  MDM#JOB001
   DOCOMMAND "sleep 180"
   STREAMLOGON mae93
   TASKTYPE UNIX
   RECOVERY STOP
  
  1. ResetPlan -scratch/JnextPlan to plan the js.
  
  Results:
  I expected JobStream run as followings:
  %ss
  MDM#JSEVRY01 0945 01/11 SUCC  10 09:45  00:03    1   1
  MDM#JSEVRY01 0947 01/11 CANCL 10        00:03    1   0
           [Cancelled]
  MDM#JSEVRY01 0949 01/11 SUCC  10 09:49  00:03    1   1
  MDM#JSEVRY01 0951 01/11 CANCL 10        00:03    1   0
           [Cancelled]
  MDM#JSEVRY01 0953 01/11 SUCC  10 09:53  ( 0:03)  1   1
  MDM#JSEVRY01 0955 01/11 CANCL 10        00:03    1   0
           [Cancelled]
  MDM#JSEVRY01 0957 01/11 SUCC  10 09:57  00:03    1   1
  MDM#JSEVRY01 0959 01/11 CANCL 10        ( 0:03)  1   0
           [Cancelled]
  MDM#JSEVRY01 1001 01/11 SUCC  10 10:01  00:03    1   1
  MDM#JSEVRY01 1003 01/11 CANCL 10        00:03    1   0
           [Cancelled]
  MDM#JSEVRY01 1005 01/11 SUCC  10 10:05  00:03    1   1
  MDM#JSEVRY01 1007 01/11 CANCL 10        ( 0:03)  1   0
           [Cancelled]
  MDM#JSEVRY01 1009 01/11 SUCC  10 10:09  00:03)   1   0
  
  Actual JobStream run results are as follows:
  %ss
  MDM#JSEVRY01 0945 01/11 SUCC  10 09:45  00:03    1   1
  MDM#JSEVRY01 0947 01/11 SUCC  10 09:48  00:03    1   1
  MDM#JSEVRY01 0949 01/11 SUCC  10 09:51  00:04    1   1
  MDM#JSEVRY01 0951 01/11 SUCC  10 09:54  00:03    1   1
  MDM#JSEVRY01 0953 01/11 CANCL 10        ( 0:03)  1   0
           [Cancelled]
  MDM#JSEVRY01 0955 01/11 SUCC  10 09:57  00:03    1   1
  MDM#JSEVRY01 0957 01/11 SUCC  10 10:00  00:04    1   1
  MDM#JSEVRY01 0959 01/11 CANCL 10        ( 0:03)  1   0
           [Cancelled]
  MDM#JSEVRY01 1001 01/11 SUCC  10 10:03  00:03    1   1
  MDM#JSEVRY01 1003 01/11 SUCC  10 10:06  00:03    1   1
  MDM#JSEVRY01 1005 01/11 CANCL 10        ( 0:03)  1   0
           [Cancelled]
  MDM#JSEVRY01 1007 01/11 SUCC  10 10:09  00:03    1   1
  MDM#JSEVRY01 1009 01/11 SUCC  10 10:12  00:03    1   1
  

Local fix

• n/a
  

Problem summary

•  See apar description
  

Problem conclusion

•  This apar will be documented into TWS 9.3 an
  d TWS 9.4 guide . Basically
  donotstart
       The next instance is not started at all.
  The next instance is created as:
  At planning time it is added :a new dependencies to the
  previous
  instance + ad-hoc until = (time of current instance + a fixed
  time of
  

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

Applicable component levels