rtp disconnect time for outbound links from AIX end node

[t***@jasi.com]

I can resolve this situation under commserver for z/OS but can find no
solution under AIX.

When an HPR/RTP pipe is established from AIX to z/OS for LU-LU
traffic, the disconnect time is too short. In other words, I need
the pipe to stay open for longer than 10-20 seconds after the last LU-
LU session has closed. On the z/OS side, this is controlled by the
DISCNT=(DELAY,,seconds) parameter on the dynamic PU model for
enterprise extender (EE) RTP pipes.

Coding it on z/OS does not help because the disconnect time is
controlled by the originator of the pipe (AIX). Does anyone know how
(or if) this value can be specified on the AIX side of the pipe??

[l***@us.ibm.com]

Subject: rtp disconnect time for outbound links from AIX end node
Date: 12 Feb 2007 07:29:32 -0800
Organization: http://groups.google.com
I can resolve this situation under commserver for z/OS but
can find no solution under AIX.
When an HPR/RTP pipe is established from AIX to z/OS for LU-LU
traffic, the disconnect time is too short. In other words, I need
the pipe to stay open for longer than 10-20 seconds after the last LU-
LU session has closed. On the z/OS side, this is controlled by the
DISCNT=(DELAY,,seconds) parameter on the dynamic PU model for
enterprise extender (EE) RTP pipes.
Coding it on z/OS does not help because the disconnect time is
controlled by the originator of the pipe (AIX). Does anyone know how
(or if) this value can be specified on the AIX side of the pipe??

Postings made to the ibm.software.commserver.aix newgroup
through google are not forwarded to the NNTP server which
hosts that newsgroup (news.software.ibm.com) so your posting
will not be seen by all who might reply unless you use the
nntp interface to that news server. Please use the NNTP URL:
news://news.software.ibm.com/ibm.software.commserver.aix


You didn't say whether these are explicit links defined on CS/AIX
or dynamic links created using a VRN/ConnectionNetwork. For the
former, look at the limited_resource= parameter on the define_ip_ls
definition and for the latter look at the implicit_limited_resource=
on the define_ip_port definition. The CS/AIX v6.3 Admin Command
Reference book says this about limited_resource:

limited_resource
Specifies whether this link station is a limited resource and is
automatically deactivated when there are no sessions using the link.
Possible values are:
NO The link is not a limited resource and is not automatically
deactivated.
NO_SESSIONS The link is a limited resource and is automatically
deactivated when no active sessions are using it.
INACTIVITY The link is a limited resource and is automatically
deactivated when no active sessions are using it, or when no data
has flowed on the link for the time period specified by the
link_deact_timer parameter.

and here is what it says about link_deact_timer:

link_deact_timer
Limited resource link deactivation timer, in seconds. A limited
resource link is automatically deactivated if no data flows over the
link for the time specified by this parameter. This parameter is not
used if limited_resource is set to any value other than INACTIVITY.
The minimum value is 5; values in the range 1–4 will be interpreted as
5. The value 0 (zero) indicates that the default deactivation timer
value of 30 is used.

Have you tried limited_resource=INACTIVITY and link_deact_timer=60
(implicit_limited_resource and implicit_deact_timer for dynamic links)?
The CS/AIX manuals are online at:
http://www.ibm.com/software/network/commserver/library

Paul Landay

[t***@jasi.com]

Post by l***@us.ibm.com
Have you tried limited_resource=INACTIVITY and link_deact_timer=60
(implicit_limited_resource and implicit_deact_timer for dynamic links)?

Pardon my ignorance, but I can not see those values anywhere other
than in the manuals. How are these values set? Are they
configurable via the GUI or via SMIT?

In answer to your other questions, all I can say is that there is an
APPC Lu6.2 application in the AIX box that allocating and deallocating
conversations to CICS all day long. An HPR pipe is established as
needed for the conversation allocation. The lifetime of the pipe
varies from short (seconds) to long(Minutes). This establish/takedown
happens thousands of times a day.
We do not have a VRN connection. The two Nodes involved share a local
IP segment, but it is not formally a VRN. The z/OS box is a NNode and
the AIX is an ENode. The CP-CP related sessions (CPSVCMG and
SNASVCMG) do not cycle like the pipe established for the Lu6.2
traffic.

(also pardon me for not having a usable newsgroup reader configured at
work -- maybe next time)

[l***@us.ibm.com]

Subject: Re: rtp disconnect time for outbound links from AIX end node
Date: 13 Feb 2007 12:32:48 -0800

Post by l***@us.ibm.com
Have you tried limited_resource=INACTIVITY and link_deact_timer=60

Pardon my ignorance, but I can not see those values anywhere other
than in the manuals. How are these values set? Are they
configurable via the GUI or via SMIT?

In this case, neither. Both xsnaadmin and smit only display the
most commonly used fields. You need to use the 'snaadmin' command
line to display/modify less commonly used fields.

The CS/AIX v6.3 Admin Command Reference says:
CS/AIX administration commands are accessible through the snaadmin
program. The snaadmin program is a command-line administration program
that can be used to configure and manage the CS/AIX node. The
Communications Server for AIX Administration Guide describes how to
configure and manage the CS/AIX node using specific administration
commands.

The CS/AIX Admin Guide says (in the section describing xsnaadmin):
The other CS/AIX administration tools, including command-line
configuration, and NOF application programs, provide access to a wider
range of configuration parameters and options than those shown in the
Motif administration program. In most cases, however, you can perform
all needed configuration from the Motif administration program,
because it exposes the key fields you need to configure and hides the
fields that most users should not need to modify. The default values
supplied by command-line configuration may differ from those supplied
by the Motif administration program or SMIT, because the Motif program
can choose values more intelligently based on the context of the
configuration task you are performing.

You would use commands like:
snaadmin -d -h
snaadmin -d -h define_ip_ls
snaadmin -c define_ip_ls, ls_name=..., limited_resource=..., ...

In answer to your other questions, all I can say is that there is an
APPC Lu6.2 application in the AIX box that allocating and deallocating
conversations to CICS all day long. An HPR pipe is established as
needed for the conversation allocation. The lifetime of the pipe
varies from short (seconds) to long(Minutes). This establish/takedown
happens thousands of times a day.

I misread your original question, you are asking about RTP pipes,
not the linkstations over which the pipe runs. My answer would
help to keep a linkstation active, but may not help with keeping a
pipe up when there are no sessions using the pipe. Are you using
session_timeout to end the sessions:
snaadmin -d query_session | grep timeout
snaadmin query_lu62_timeout

Paul Landay

[t***@jasi.com]

I am the middle man here and do not have access to the AIX system in
question. the administrator has forwarded me portions of the raw
config dataset. The link station is behaving normally
(limited_resource=NO - the default) I guess what we are trying to
"fix" is an lu6.2 session level issue.

Thanks for your help so far. I will try to find out more about the
session level definitions from the AIX administrator before he goes on
vacation for a week.

Post by l***@us.ibm.com

Post by t***@jasi.com
In answer to your other questions, all I can say is that there is an
APPC Lu6.2 application in the AIX box that allocating and deallocating
conversations to CICS all day long. An HPR pipe is established as
needed for the conversation allocation. The lifetime of the pipe
varies from short (seconds) to long(Minutes). This establish/takedown
happens thousands of times a day.

I misread your original question, you are asking about RTP pipes,
not the linkstations over which the pipe runs. My answer would
help to keep a linkstation active, but may not help with keeping a
pipe up when there are no sessions using the pipe. Are you using
snaadmin -d query_session | grep timeout
snaadmin query_lu62_timeout
Paul Landay