IV63672: EXECUTION OF JNEXTPLAN HANGS BECAUSE OF DEFINITION OF RUNCYCLE GROUPS

9.2.0-TIV-TDWC-TWS-FP0001
9.2.0-TIV-TWS-AIX_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS-AIX_AGENT-FP0001
9.2.0-TIV-TWS-HPIA64_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS-HPIA64_AGENT-FP0001
9.2.0-TIV-TWS-IBM_I_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS-IBM_I_AGENT-FP0001
9.2.0-TIV-TWS-LNX_I386_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS-LNX_I386_AGENT-FP0001
9.2.0-TIV-TWS-LNX_PPC_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS-LNX_PPC_AGENT-FP0001
9.2.0-TIV-TWS-LNX_S390_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS-LNX_S390_AGENT-FP0001
9.2.0-TIV-TWS-LNX_X86_64_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS--LNX_X86_64_AGENT-FP0001
9.2.0-TIV-TWS-SOLARIS_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS-SOLARIS_AGENT-FP0001
9.2.0-TIV-TWS-SOLARIS_I386_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS-SOLARIS_I386_AGENT-FP0001
9.2.0-TIV-TWS-AIX-FP0001
9.2.0-TIV-TWS-HPIA64-FP0001
9.2.0-TIV-TWS-LINUX_X86_64-FP0001
9.2.0-TIV-TWS-LINUX390-FP0001
9.2.0-TIV-TWS-LINUXPPC-FP0001
9.2.0-TIV-TWS-SOLARIS_I386-FP0001
9.2.0-TIV-TWS-SOLARIS-FP0001
9.2.0-TIV-TWS-WINDOWS_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS-WINDOWS_AGENT-FP0001
9.2.0-TIV-TWS-WINDOWS_X86_64_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS-WINDOWS_X86_64_AGENT-FP0001
9.2.0-TIV-TWS-WINDOWS_X86_64-FP0001

APAR status

• Closed as program error.

Error description

• 1. Create the following RunCycle Group"RCG_ERR2A" definition and
  register it into MDM.
     RunCycle "RC1" and "RC2" is the same except for a difference
  between
  "ON RUNCYCLE" and "EXCEPT RUNCYCLE".
  
  ============
  RUNCYCLEGROUP RCG_ERR2A ON RUNCYCLE RC1
  "FREQ=WEEKLY;INTERVAL=1;BYDAY=MO,TU,WE,TH,FR,SA,SU" SUBSET
  SUBSET1 OR
  ( AT 1500 )
  EXCEPT RUNCYCLE RC2
  "FREQ=WEEKLY;INTERVAL=1;BYDAY=MO,TU,WE,TH,FR,SA,SU"
  SUBSET SUBSET1 OR
  ( AT 1500 )
  END
  ============
  
  2. Create the following Job and JobStream definition and
  register them
  into MDM.
     The Job "RCG_ERR2A_JOB01" is scheduled base on the RunCycle
  Group"RCG_ERR2A".
  
  (Job)
  ============
  $JOBS
  TWS91MDMAIX#RCG_ERR2A_JOB01
   DOCOMMAND "echo `date` >> /ISEL/RCG_ERR2A_JOB.log"
   STREAMLOGON twsusr1
   TASKTYPE UNIX
   RECOVERY STOP
  ============
  
  (JobStream)
  ============
  SCHEDULE TWS91MDMAIX#RCG_ERR2A_JS01
  ON RUNCYCLE RCG_ERR2A_RC1 $RCG RCG_ERR2A
  :
  TWS91MDMAIX#RCG_ERR2A_JOB01
  END
  ============
  
  3. Run "ResetPlan -scratch".
  
  twsusr1@tws91mdmaix1:/ISEL/New_Function/RCGroup# echo Y |
  ResetPlan
  -scratch
  
  4. Run "JnextPlan"
  
     The command never  completes and the following error is
  repeated into
  TSMerge.log:
  
  00:24:17 14.08.2014|CONNECTR:INFO:ERROR reading the header in
  the
  symphony file.
  00:24:17 14.08.2014|CONNECTR:INFO:ERROR closing the symphony
  file.
  00:24:17 14.08.2014|CONNECTR:INFO:ERROR opening the symphony
  file.
  
  5. Also, we have noticed that Makeplan hangs when the following
  runcycle group is used
  
  
  RUNCYCLEGROUP SRIRUNC2 ON RUNCYCLE RC1 "FREQ=DAILY;INTERVAL=1"
  SUBSET
  RC1 AND
  ( AT 1820 )
  ON RUNCYCLE RC2 "FREQ=DAILY;INTERVAL=1" SUBSET RC1 AND
  ( AT 1830 )
  ON RUNCYCLE RC3 "FREQ=DAILY;INTERVAL=1" SUBSET RC1 AND
  ( AT 1840 )
  END
  
  Once we changed the AND to OR the issue went away, so it seems
  to be caused by by the AND clause.
  

Local fix

• n/a
  

Problem summary

• See apar description.
  

Problem conclusion

• This apar will be fixed into
  9.1 FP2 and 9.2 FP1.
  

Temporary fix

• see apar description
  

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 WKLD SCHDL

• Fixed component ID

  5698WKB91

Applicable component levels

• R9A1 PSY

     UP