Rules

The state of a Netserv after a JES3 start depends on the type of start that was requested:

Cold start: The initialization statements are read and used as the source of the Netserv state. The starting state is checkpointed.
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.
Hot start: The checkpointed information is the source for all Netservs. Because checkpoint includes the state and modifications from previous JES3 starts, that state is preserved across the hot start.
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 dictate the outcome of each specific JES3 start situation. For example, if an initialization statement is changed and the system is hot started, the change will not be applied because a hot start does not read the initialization statements and preserves the checkpointed state. To apply such a change, The NETSERV statements must be read, which requires a cold, warm or hot start with refresh. Choosing hot start with refresh also means that the changed Netserv must be inactive across the restart. Likewise, 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.