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
end-to-end scheduling.
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
scheduling environment.
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
626 IBM Tivoli Workload Scheduler for z/OS Best Practices
Therefore, if the DM will not link, and the messages shown in Example 18-29 are
seen in TWSMERGE, the nm port value should be checked and compared to the
CPUTCPIP value. In this case, correcting the CPUTCPIP value and running a
Symphony Renew job eliminated the problem.
We did another test with the same domain manager, this time setting CPUTCPIP
to 31113.
Example 18-30 Setting CPUTCPIP to 31113
The TOPOLOGY PORTNUMBER was also set to its normal value of 31113:
After cycling the E2E Server and running a CP EXTEND, the domain manager
and all of the FTAs were linked and active, which is not what was expected.
Example 18-31 Messages showing DM and all the FTAs are LINKED and ACTIVE
Enter the row command S to select a work station for modification, or
I to browse system information for the destination.
Row Work station L S T R Completed Active Remaining
cmd name text oper dur. oper oper dur.
' HR82 PDM on HORRIBLE L A C A 4 0.00 0 13 0.05
' OP82 MVS XAGENT on HORRIBLE L A C A 0 0.00 0 0 0.00
' R3X1 SAP XAGENT on HORRIBLE L A C A 0 0.00 0 0 0
How could the DM be active if the CPUTCPIP value was intentionally set to the
wrong value? We found that there was an FTA in the network that was set up with
nm port=31113. It was actually a master domain manager (MDM) for a Tivoli
Workload Scheduler V8.1 Distributed only (not E2E) environment. So our V8.2
end-to-end scheduling environment connected to the V8.1 master domain
manager as though it were HR82. This illustrates that extreme care must be
taken to code the CPUTCPIP values correctly, especially if there are multiple
Tivoli Workload Scheduler environments present (for example, a test system and
a production system).

Get IBM Tivoli Workload Scheduler for z/OS Best Practices: End-to-end and mainframe scheduling, 2nd Edition now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.