IBM SC30-3865-04 - Manual (Page 71)

To enable collection implicitly, set create intermediate session records to yes.
This setting will override the setting of collect intermediate session information.
2. Configuration changes to the APPN accounting parameters made using the talk
6 interface will not take effect until the router or the APPN function on the router
is restarted. You can make changes interactively, however, by issuing SNMP set
commands to modify the APPN MIB variables associated with the configuration
parameters. Refer to the
Software User’s Guide for a list of these MIB variables.
3. Data on intermediate session RSCVs is obtained by examining the BIND
request used to activate a session between two LUs. RSCV data is not
collected for sessions that have already been established because the BIND
information for those sessions is not available.
4. Intermediate session data is not collected for HPR sessions since intermediate
sessions are not part of HPR. If the router contains an ISR/HPR boundary,
intermediate session data is collected when it flows across that boundary.
DLUR Retry Algorithm
If communication between DLUR and DLUS is broken, the following algorithm is
used to reestablish communication:
If Perform retries to restore disrupted pipe is No:
v If DLUR receives a non-disruptive UNBIND (sense code of X’08A0 000A’), DLUR
waits indefinitely for a DLUS to reestablish the broken pipe.
v If the pipe fails for any other reason than a non-disruptive UNBIND, DLUR
attempts to reach the primary DLUS once. If this is unsuccessful, DLUR attempts
to reach the backup DLUS. If DLUR is unable to reach the backup DLUS, it waits
indefinitely for a DLUS to reestablish the broken pipe.
If Perform retries to restore disrupted pipe is Yes, DLUR will attempt to reestablish
the pipe based on the following configuration parameters:
v Delay before initiating retries
v Perform short retries to restore disrupted pipe
v Short retry timer
v Short retry count
v Perform long retries to restore disrupted pipe
v Long retry timer
There are two cases that determine the retry algorithm:
v For the case of receiving a non-disruptive UNBIND:
1. Wait for the amount of time specified by the Delay before initiating retries
parameter. This delay allows time for an SSCP takeover, where the pipe
would be reestablished by a new DLUS without action on the DLUR’s part.
2. Attempt to reach the primary DLUS.
3. If unsuccessful, attempt to reach the backup DLUS.
4. If the attempt to reach the backup DLUS is unsuccessful, DLUR will retry as
described in steps 5 - 7 as long as the DSPU is requesting ACTPU.
5. Wait for the amount of time specified by the Long retry timer.
Note: If Perform long retries to restore disrupted pipe is No, no further retries
will be attempted.
6. Attempt to reach the primary DLUS.
APPN
Chapter 1. APPN 41