Chapter 18. End-to-end scheduling troubleshooting 625
assumes the characteristics defined in BPX.DEFAULT.USER and needs these
three variables set in a valid manner so that the user can work as needed for
In addition, APARs such as PK01415 have tightened security while giving better
messages to help diagnose security issues.
18.3 End-to-end scheduling PORTNUMBER and
There are two different parameters named PORTNUMBER: one in the
SERVOPTS that is used for the JSC and OPC connector, and one in the
TOPOLOGY parameters that is used by the E2E Server to communicate with the
distributed FTAs. The two PORTNUMBER parameters must have different
values. The localopts for the FTA has a parameter named nm port, which is the
port on which netman listens. The nm port value must match the CPUREC
CPUTCPIP value for each FTA. There is no requirement that CPUTCPIP must
match the TOPOLOGY PORTNUMBER. The value of the TOPOLOGY
PORTNUMBER and the HOSTNAME value are imbedded in the Symphony file,
which allows the FTA to know how to communicate back to OPCMASTER. The
next sections illustrate different ways in which incorrectly setting the values for
PORTNUMBER and CPUTCPIP can cause problems in the end-to-end
18.3.1 CPUTCPIP not same as nm port
The value for CPUTCPIP in the CPUREC parameter for an FTA should always be
set to the same port that the FTA has defined as nm port in localopts.
We ran tests to see what errors occur if the wrong value is used for CPUTCPIP.
In the first test, nm port for the domain manager (DM) HR82 was 31111, but
CPUTCPIP was set to 31122, a value that was not used by any FTA on our
network. The current plan (CP) was extended to distribute a Symphony file with
the wrong CPUTCPIP in place. The domain manager failed to link, and the
messages in Example 18-29 were seen in the USS stdlist TWSMERGE log.
Example 18-29 Excerpt from TWSMERGE log
MAILMAN:+ AWSBCV082I Cpu HR82, Message: AWSDEB003I Writing socket:
EDC8128I Connection refused.
MAILMAN:+ AWSBCV035W WARNING: Linking to HR82 failed, will write to