IJ00338: JOBSTREAM IS PLANNED UNEXPECTEDLY ON EXCEPT CALENDAR DATE

9.4.0-IBM-IWS-AIX_BATCH_REPORTS-FP0003
9.4.0-IBM-IWS-HPIA64_BATCH_REPORTS-FP0003
9.4.0-IBM-IWS-LNX_PPC_BATCH_REPORTS-FP0003
9.4.0-IBM-IWS-LNX_S390_BATCH_REPORTS-FP0003
9.4.0-IBM-IWS-LNX_X86_64_BATCH_REPORTS-FP0003
9.4.0-IBM-IWS-SOL_I386_BATCH_REPORTS-FP0003
9.4.0-IBM-IWS-WIN_X86_64_BATCH_REPORTS-FP0003
9.4.0-IBM-IWS-LINUX_X86_64_WORKBENCH-FP0003
9.4.0-IBM-IWS-WINDOWS_X86_64_WORKBENCH-FP0003
9.4.0-IBM-IWS-AIX_AGENT-FP0003
9.4.0-IBM-IWS-AIX_ZOS_AGENT-FP0003
9.4.0-IBM-IWS-HPIA64_AGENT-FP0003
9.4.0-IBM-IWS-HPIA64_ZOS_AGENT-FP0003
9.4.0-IBM-IWS-IBM_I_AGENT-FP0003
9.4.0-IBM-IWS-IBM_I_ZOS_AGENT-FP0003
9.4.0-IBM-IWS-LINUXPPC_LE_AGENT-FP0003
9.4.0-IBM-IWS-LINUXPPC_LE_ZOS_AGENT-FP0003
9.4.0-IBM-IWS-LNX_PPC_AGENT-FP0003
9.4.0-IBM-IWS-LNX_PPC_ZOS_AGENT-FP0003
9.4.0-IBM-IWS-LNX_S390_AGENT-FP0003
9.4.0-IBM-IWS-LNX_S390_ZOS_AGENT-FP0003
9.4.0-IBM-IWS-LNX_X86_64_AGENT-FP0003
9.4.0-IBM-IWS-LNX_X86_64_ZOS_AGENT-FP0003
9.4.0-IBM-IWS-SOL_I386_AGENT-FP0003
9.4.0-IBM-IWS-SOL_I386_ZOS_AGENT-FP0003
9.4.0-IBM-IWS-WIN_X86_64_AGENT-FP0003
9.4.0-IBM-IWS-WIN_X86_64_ZOS_AGENT-FP0003
9.4.0-IBM-IWS-AIX-FP0003
9.4.0-IBM-IWS-HPIA64-FP0003
9.4.0-IBM-IWS-LINUX_X86_64-FP0003
9.4.0-IBM-IWS-LINUX390-FP0003
9.4.0-IBM-IWS-LINUXPPC-FP0003
9.4.0-IBM-IWS-SOLARIS_I386-FP0003
9.4.0-IBM-IWS-WINDOWS_X86_64-FP0003
9.2.0-TIV-DWC_FP0003_AIX
9.2.0-TIV-DWC_FP0003_LINUX_X86_64
9.2.0-TIV-DWC_FP0003_LINUX390
9.2.0-TIV-DWC_FP0003_WINDOWS_X86_64

APAR status

• Closed as program error.

Error description

• Environment:
  MDM: IWS 9.2.0 + FP0002 on RHEL 5.5
  DWC: DWC 9.2.0 + FP0002 on RHEL 5.5
  
  Problem Description:
  Jobstream FTA#JSEXCEPT has EXCEPT RUNCYCLE "CAL03" defined.
  
  Calendar Definitions:
  CAL01
    "CAL01"
    04/02/2017 04/03/2017 04/04/2017 04/30/2017 05/01/2017
  05/02/2017 05/03/2017 05/04/2017
    05/05/2017 05/06/2017 05/07/2017 05/31/2017 06/01/2017
  06/02/2017 06/03/2017 06/04/2017
    06/05/2017 06/06/2017 06/07/2017 06/30/2017 07/01/2017
  07/02/2017 07/03/2017 07/04/2017
    07/05/2017 07/06/2017 07/07/2017 07/08/2017 07/09/2017
  07/10/2017 07/31/2017 08/01/2017
  
  CAL02
    "CAL02"
    01/01/2016
  
  CAL03
    "End of Monthly"
    01/31/2016 02/28/2017 03/31/2017 04/30/2017 05/31/2017
  06/30/2017
  07/31/2017 08/31/2017
    09/30/2017 10/31/2017 11/30/2017 12/31/2017
  
  Jobstream FTA#JSEXCEPT is planned on April 30, May 31, June 30
  and so on, where these days are defined in EXCEPT calendar
  "CAL03".
  
  SCHEDULE FTA#JSEXCEPT
  FREEDAYS YIMMHLDY -SA -SU
  ON RUNCYCLE CAL01 CAL01 FDIGNORE
  ON RUNCYCLE CAL02 CAL02 FDIGNORE
  EXCEPT RUNCYCLE EXCEPTEMONTH CAL03 FDIGNORE
  :
  FTA#JOB001
  END
  
  -Forecast plan for these days have FTA#JSEXCEPT planned.
   planman crtfc forecast0430 -from 04/30/17 -days 1
   planman crtfc forecast0531 -from 05/31/17 -days 1
   planman crtfc forecast0630 -from 06/30/17 -days 1
  
  
  -On DWC, "Run Cycle Preview" -> "All Run Cycles"  shows these
  EXCEPT days are not selected.
  

Local fix

• To prevent the issue to occur:
  Edit the runcycles for the same jobstream using only one
  interface, composer or DWC.
  To fix the issue:
  Force the save of the runcycles definitions from the same user
  interface,
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Tivoli Workload Scheduler users having      *
  *                  jobstreams with exclude runcycles and       *
  *                  editing jobstreams from composer and DWC    *
  ****************************************************************
  * PROBLEM DESCRIPTION: If runcycles in the same jobstream are  *
  *                      or modified using mixed user interface  *
  *                      DWC and composer) it is possible that   *
  *                      the some runcycles are ignored          *
  ****************************************************************
  * RECOMMENDATION: Edit runcycles in the same jobstream from a  *
  *                 single user interface                        *
  ****************************************************************
  The problem is due to the different default value DWC and
  composer use for the runcycle subset value.
  Even if no runcycle groups have been specified, the code manages
  simple runcycles as part of a default subset in a default group.
  Because of the different subset default value the two interfaces
  assign to the runcycles, if a jobstream contains runcycles
  defined from both the interfaces, some of them will be ignored.
  The code has been changed to have the same default vales for
  both the user interfaces.
  

Problem conclusion

• This apar will be fixed in 9.4-TIV-TWS-FP0003,
  9.3-TIV-TWS-FP0004, 9.2-TIV-TWS-FP0003 and 9.1-TIV-TWS-FP0003
  

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

  TIV DYN WKLD CN

• Fixed component ID

  TIVOWEBUI

Applicable component levels