OA40740: NETSERV STARTS ON WRONG SYSTEM

APAR status

• Closed as documentation error.

Error description

• External symptoms:
  Customer's NETSERV does not start on the system it is
  designated to start on based on SYSTEM= parm
  Impact to customer:
    Minimal
  Analysis:
    Customer modified NETSERV statement adding SYSTEM= while the
  NETSERV is active.  The JES3 Initialization and Tuning Reference
  states
  
  ...
  An active Netserv cannot be deleted or
   modified except to change the JTRACE, VTRACE,
   or ITRACE parameter.
  ...
  
  The modification of SYSTEM= gets updated in the intermediate
  text, but not in the active NETSERV's control blocks.
  The intermediate text is only read during a JES3 restart;
  subsequent cancel and starts of the NETSERV read checkpointed
  information, which reflect the previous status
  
  The projected closing code for this APAR is DOC.
  

Local fix

• stop NETSERV, hotstart/refresh
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of HJS7780.                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A user defined a Netserv without a SYSTEM= parameter on the
  NETSERV initialization statement.  This means the Netserv
  should run on the global system.  After starting the Netserv
  on the global (SYA), SYSTEM=SYA was added to the NETSERV
  initialization statement.  After performing a DSI (Dynamic
  System Interchange) to SYB, the Netserv was restarted.  Instead
  of starting on SYA, it started on SYB, which was interpreted as
  an error.
  
  The checkpointed Netserv state is maintained for all Netservs
  on a hot start and active Netservs on a hot start with refresh.
  During a DSI, the new global is hot started.  Therefore, when
  the Netserv was restarted, its checkpointed state was used.
  Since that state indicated the Netserv should run on the
  global, the Netserv was started on SYB.
  

Problem conclusion

• In this case, JES3 is working as designed, so no code changes
  are required.  However, changes to documentation will be made
  to clarify Netserv behavior.
  
  The information in the following manuals should appear as
  indicated below.  Updates will only be made to the manuals
  in future releases.
  
  SA22-7550-xx
  JES3 Initialization and Tuning Reference
  Chapter 2. Initialization Statement
  NETSERV section
  
  Replace the existing Rules subsection with the following:
  
  The state of a Netserv after a JES3 start depends on the
  type of start requested:
  
  o  Cold start -- The initialization statements are read and
     used as the source of the Netserv state.  The starting
     state is checkpointed.
  o  Warm start -- The initialization statements are read and
     used as the source of the Netserv state.  The starting
     state is checkpointed, replacing checkpointed information
     from previous starts.
  o  Hot start -- The checkpointed information is the source
     for all Netservs.  Since checkpoint includes the state
     and modifications from previous JES3 starts, that state
     is preserved across the hot start.
  o  Hot start with refresh -- The initialization statements
     are read and used as the source for inactive Netservs.
     Checkpointed information is used for active Netservs.
     The checkpoint includes state and modifications from
     previous JES3 starts, and that state is preserved
     across the start.
  
  These rules, when applied to a specific situation, predict
  the outcome.  For example, if an initialization statement
  is changed and the system is hot started, we know that the
  change will not be applied because a hot start does not read
  the initialization statements and preserves the checkpointed
  state.  How would you apply such a change?  The NETSERV state-
  ments must be read, so that means a cold, warm, or hot start
  with refresh.  Choosing hot start with refresh also means the
  changed Netserv must be inactive across the restart.  Another
  example.  If an inactive Netserv is modified by command and
  it remains inactive, the change will be lost across a hot start
  with refresh because this restart preserves changes only for
  active Netservs.
  
  
  SA22-7540-xx
  JES3 Commands
  Chapter 15. JES3 Command Reference Section
  The "Modifying a TCP/IP/NJE Network Server *MODIFY,NETSERV="
  section should be replaced with the following:
  
  Rules
    o HOSTNAME= can be abbreviated to HOST=.
    o Active Netservs cannot be modified, except for ITRACE,
     JTRACE, and VTRACE.
  
  The following information applies to all *MODIFY,NETSERV
  command variants:
  
  The state of a Netserv after a JES3 start depends on the
  type of start requested:
  
  o  Cold start -- The initialization statements are read and
     used as the source of the Netserv state.  The starting
     state is checkpointed.
  o  Warm start -- The initialization statements are read and
     used as the source of the Netserv state.  The starting
     state is checkpointed, replacing checkpointed information
     from previous starts.
  o  Hot start -- The checkpointed information is the source
     for all Netservs.  Since checkpoint includes the state
     and modifications from previous JES3 starts, that state
     is preserved across the hot start.
  o  Hot start with refresh -- The initialization statements
     are read and used as the source for inactive Netservs.
     Checkpointed information is used for active Netservs.
     The checkpoint includes state and modifications from
     previous JES3 starts, and that state is preserved
     across the start.
  
  These rules, when applied to a specific situation, predict
  the outcome.  For example, if an initialization statement
  is changed and the system is hot started, we know that the
  change will not be applied because a hot start does not read
  the initialization statements and preserves the checkpointed
  state.  How would you apply such a change?  The NETSERV state-
  ments must be read, so that means a cold, warm, or hot start
  with refresh.  Choosing hot start with refresh also means the
  changed Netserv must be inactive across the restart.  Another
  example.  If an inactive Netserv is modified by command and
  it remains inactive, the change will be lost across a hot start
  with refresh because this restart preserves changes only for
  active Netservs.
  
  
  The "Adding a TCP/IP/NJE Network Server *MODIFY,NETSERV,ADD="
  section should be modified (changes marked with "|"):
  
  Rules
    o The Netserv to be added must be a valid name for an
      address space.
    o It is the responsibility of the installation to provide
      security definitions for the added Netserv. See z/OS
      JES3 Initialization and Tuning Guide for information
      about defining Netservs.
  | o See the Rules section for "Modifying a TCP/IP/NJE
  |   Network Server *MODIFY,NETSERV=" for more information
  
  
  The "Deleting a TCP/IP/NJE Network Server *MODIFY,NETSERV,
  DELETE=' section should be modified (changes marked with
  "|"):
  
  Rules
    o DELETE= can be abbreviated to DEL=.
    o Active Netservs cannot be deleted.
  | o See the Rules section for "Modifying a TCP/IP/NJE
  |   Network Server *MODIFY,NETSERV=" for more information
  

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