PH46450: ZD&T 13.X EE: EMULATOR NOT ALWAYS STARTING AFTER MULTIPLE STOP/START API REQUESTS

APAR status

• Closed as unreproducible.

Error description

• ZD&T 13.X EE
  
  After a successful deployment, a series of Stop/Start API
  requests are issued approximately 3-4 minutes apart.
  Half of the Start API requests fail.
  
  The logs indicate duplicate IPL Handling scripts running on the
  target Linux host resulting in a z/OS Wait state which occurs
  when the oprmsg 'v cn(*),activate" command is issued prior to
  IEE389I.
  

Local fix

• 1. After any Start API request, wait at least 15 minutes prior
  to executing any subsequent Start API request. This wait time is
  
  regardless of a successful connection to z/OS. Note that 15
  minutes is an estimate, as there are handling threads running on
  both the target Linux host and the ZD&T Tools server. One may
  have to adjust the wait time upward if errors still persist. It
  is also completely possible to require less time between
  multiple Start API requests, as this is highly dependent on what
  
  z/OS subsystems are starting and the time it takes for ZD&T
  tools to complete any post IPL processing. Generally speaking,
  if the zdt_ipl_handle_log.sh and zdt_ipl.sh processes on the
  target Linux host are complete (i.e. none are running), then it
  is safe to do a new Start API request. Again, there could still
  be a timing issue here if the threads on the ZD&T Tools server
  haven't terminated yet.
  
  2. It may be also be possible to prevent the error without
  waiting so long by killing any zdt_ipl_handle_log.sh and
  zdt_ipl.sh processes running on the target Linux host after any
  Stop API Request and before any subsequent Start API Request.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ZD&T users                                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * ZD&T 13.X EE: Emulator not always starting after multiple    *
  * stop/start requests                                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

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