ClearPath OS 2200 Series Release 13.2 Software Planning and ...

Open Programming Environment (OPE)
OPE and CPComm Functionality Notes
• OPE’s local address cache may contain loopback addresses. CPComm must be
configured for loopback and OPE. A local loopback address must be chosen for OPE.
This address is not user visible to OPE user programs or commands.
• Possible candidates for the local address are 127.0.0.2, 127.0.0.3, and so forth.
• Each OPE system must have a unique local loopback address configured in
CPComm, which is not used by any other product in the CPComm configuration file.
• If you had three modes of OPE, called sxtsaa, sxtsab, and sxtsac, add the following
to the CPComm configuration file:
ip,internal link,loopback ip-address,127.0.0.1 ; **this default must now
be expressly defined**
ip-address,127.0.0.2,sxtsaa ; **because of the addition of
ip-address,127.0.0.3,sxtsab ;
ip-address,127.0.0.4,sxtsac .
these local addresses**
sxtsaa, sxtsab, and sxtsac are the TSAM_NAME parameters in the ope KRNL-CONFIG
file.
Note: The loopback lb localhost entry in your /etc/hosts file should not reflect the
changes in the CPComm configuration; it should remain 127.0.0.1.
OPE Daylight Savings time Considerations for the USA and CANADA
Because of amendments to the Uniform Time Act of 1966, starting March 11, 2007,
OPE systems observing daylight savings time will no longer have the correct local time
during the periods between: the second Sunday of March and the first Sunday of April
AND the last Sunday of October and the first Sunday of November
Elements written by the U-Driver, and files within OPE will have their timestamps set
one hour slow. Events triggered by CRON will happen one hour late. This problem will
go away once the former time that was the start of daylight time has passed, and will
appear once again in the fall when the former end of daylight time is reached.
Kernel
The TCPMAP value default was increased from 500 to 700.and in /etc/inet/inetd.conf).
The new recommended value is 700. The maximum is now 52400. This corresponds to
the total number of TCP connections plus the total number of possible queued
connections.
For inetd, the total number of possible queued connections is the number of TCP
services * 50. If the number of TCPMAP structures is inadequate, the connection or
service will not be established, and a notice will be logged in the ALTPRT file: TCPMAP
full. Consider increasing the TCPMAP kernel configuration
5–36 7831 0349–043