Two TPX tasks (TPX01 and TPX02) have been defined to use the generic resource configuration.
When the first task (TPX01) is brought up, it is able to connect to the generic resource structure and the log shows the following messages:-
IXL014I IXLCONN REQUEST FOR STRUCTURE TPXAABBBCCCDVTAM WAS SUCCESSFUL.
JOBNAME: TPX01 ASID: _____
CONNECTOR NAME: TPX01 CFNAME: CFP1
TPX5555 CA-TPX SYSPLEX SERVICES FOR NODE(TPX01 ) are enabled
TPX001 TERMINAL PRODUCTIVITY EXECUTIVE ACCEPTING LOGONS
However, when the second task (TPX02) is started, it is terminated from the structure due to the following message - IXL016I
IXL014I IXLCONN REQUEST FOR STRUCTURE TPXAABBBCCCDVTAM WAS SUCCESSFUL.
JOBNAME: TPX02 ASID: ____
CONNECTOR NAME: TPX02 CFNAME: CFP1
IXL016I CONNECTOR TPX02 TO STRUCTURE TPXAABBBCCCDVTAM TERMINATING: JOB TPX02 ASID ____ REQUESTED DISCONNECT REASON=FAILURE.
TPX5556 CA-TPX SYSPLEX SERVICES FOR NODE(TPX02 ) are disabled
TPX001 TERMINAL PRODUCTIVITY EXECUTIVE ACCEPTING LOGONS
The most likely cause is that the TPX's in the Generic Resource structure have start-up proc's that do not have matching TPX VSAM database names.
( ADMIN1 / ADMIN2 / MAIL / NOTES & VIEW )
There is a mis-match in how TPX is setup to function in a Generic Resource / Coupling facility structure environment.
It was observed that the ADMIN1 and ADMIN2 files in TPX01 and TPX02 had same names, as required however,
the VIEW, NOTES and MAIL files had different and unique names.
Since this is a TPX GR/CF environment, use same name in both the TPX images for all 5 TPX VSAM databases and restart both TPX's.
Look for following messages in the TPX LOG for explanation.
TPXL5113
Snapping contents of CF Master Entry:
Reason:
Following is the contents of the Master List Entry in the Coupling Facility
structure. This message is followed by message TPXL5115 showing the
details.
Action:
See message TPXL5111 for an explanation of why this occurred and action to be taken.
TPXL5115
SMRTxxxx=dddd
Reason:
This message identifies the information being compared for all instances of
the product running with the same generic resource name and connected to this
structure. The information must be the same for all instances of the product.
xxxx identifies the variable being displayed:
o CSRT -- Identifies the SMRT name
o CACT -- Identifies the ACT name
o CPRT -- Identifies the Print Destination Table name
o CTRM -- Identifies the Terminal Options Table name
o VFL1 -- Identifies the ADMIN1 data set name
o VFL2 -- Identifies the ADMIN2 data set name
o VFL3 -- Identifies the MAIL data set name
o VFL4 -- Identifies the NOTES data set name
o VFL5 -- Identifies the VIEW data set name
dddd indicates the value for specific variable. Action:
Review the explanation of messages TPXL5113 TPXL5114 and TPXL5111. Correct any
discrepancies and restart this instance of the product.
TPXL5114
Snapping contents of local Master Entry:
Reason:
Following is the contents of the Master List Entry as expected by this
instance. This message is followed by message TPXL5115 showing the details.
Action:
See message TPXL5111 for an explanation of why this occurred and action to
be taken.
TPXL5115
SMRTxxxx=dddd
Reason:
This message identifies the information being compared for all instances of
the product running with the same generic resource name and connected to this
structure. The information must be the same for all instances of the product.
xxxx identifies the variable being displayed:
o CSRT -- Identifies the SMRT name
o CACT -- Identifies the ACT name
o CPRT -- Identifies the Print Destination Table name
o CTRM -- Identifies the Terminal Options Table name
o VFL1 -- Identifies the ADMIN1 data set name
o VFL2 -- Identifies the ADMIN2 data set name
o VFL3 -- Identifies the MAIL data set name
o VFL4 -- Identifies the NOTES data set name
o VFL5 -- Identifies the VIEW data set name
dddd indicates the value for specific variable. Action:
Review the explanation of messages TPXL5113 TPXL5114 and TPXL5111. Correct any
discrepancies and restart this instance of the product.
TPXL5111
Master Entry verification failed - Disconnecting
Reason:
One or more items (such as the Mail Data set) are not the same for all
instances of the product operating with this generic resource name.
Action:
Review the explanations associated with messages TPXL5113, TPXL5114, and
TPXL5115. Correct the discrepancies and restart this instance of the product.