/WINDOW=RECEIVE=n
       /WINDOW=NORECEIVE

    Sets a management-specified upper bound on the receive window
    size (that is, the number of out-of-order packets this VC holds
    in its resequencing cache while awaiting the next in-order packet
    or packets).

    You can use this qualifier to override the automatically
    calculated receive window size. This ensures that the VC has
    enough buffering to receive the expected maximum number of out-
    of-order packets.

    Usage notes:

    o  The window size value n must be an exact power of 2.

       Never use settings that cause the receive window of a VC to
       be smaller than the transmit window of the partner node.
       Otherwise, the partner can send packets that cannot be
       cached when a packet is lost. This results in unnecessary
       retransmissions, and might cause channels not to be used
       because they become "lossy." This leads to the remaining
       restrictions listed.

    o  Always decrease the receive window size of a VC's partner node
       before decreasing a VC's receive window size.

       HP recommends using SYSMAN to decrease both the local and the
       remote VC transmit window sizes before increasing the local
       and remote receive window sizes (as shown in the example).

    o  Always increase the receive window size of a VC's partner node
       before increasing a VC's transmit window size.

       HP recommends using SYSMAN to increase both the local and the
       remote VC receive window sizes before increasing the local and
       remote transmit window sizes.

    o  Whenever you enter the SET VC/WINDOW=RECEIVE command, the
       following sequence of events occurs:

       1. The VC's current resequencing cache is emptied.

       2. The VC partner node automatically retransmits any discarded
          packets.

       3. As a result of 2, the VC and channel retransmit counts
          increase.

       4. A few messages similar to the following might be displayed,
          indicating that one or more channels has temporarily become
          "lossy":

              %PEA0, Excessive packet losses on LAN Path from EWA to EWC
                     on REMOTE NODE STAR

       5. The partner node recovers automatically within a few
          seconds.

    o  You can use the SCACP> CALCULATE WINDOW_SIZE command to assist
       you in selecting the size to use for transmit and receive
       windows.