Unable to logon to TPX with the generic applid (generic resource) setup.
This LPAR was recently upgraded to z/os 1.12.
Check your TPXLOG for message TPXL5501:
TPXL5501 11/28/11.332 15:03:12.85 XCF Connect - Group=TPXTEST Member=DCCTPX Rc=00000016 Rsn=00000031
TPX is talking with Coupling Facility via a module called 'LXCFMAIN'.
This is a module which is part of Common Services (CCS390/CA90s) and it is residing in either LPA or a linklist library.
The Reason 'Rsn=00000031' on the message indicates that TPX cannot access this module.
Please check that this module is available for TPX. As a test, put it in your TPX STEPLIB.
Sample TPX messages:
TPX JESMSGLG:
15.03.13 STC06548 IXL014I IXLCONN REQUEST FOR STRUCTURE TPXGENRCTPXTEST 670 670 WAS SUCCESSFUL. JOBNAME: TPXC ASID: 0050 670 CONNECTOR NAME: DCCTPX CFNAME: CF01ASC 15.03.13 STC06548 IXL015I STRUCTURE ALLOCATION INFORMATION FOR 671 671 STRUCTURE TPXGENRCTPXTEST, CONNECTOR NAME DCCTPX 671 CFNAME ALLOCATION STATUS/FAILURE REASON 671 -------- ---------------------------------------- 671 CF01ASC STRUCTURE ALLOCATED AC007800 671 CF02ASC PREFERRED CF ALREADY SELECTED AC007800 15.03.13 STC06548 TPX5556 CA-TPX SYSPLEX SERVICES FOR NODE(DCCTPX ) are disabled 15.03.17 STC06548 TPX001 TERMINAL PRODUCTIVITY EXECUTIVE ACCEPTING LOGONS
TPX LOG messages:
TPXL5101 11/28/11.332 15:03:12.85 CF Connect - Str=TPXGENRCTPXTEST Conn=DCCTPX Rc=00000000 Rsn=00000000 Disp=NEW APPROXIMATE NUMBER OF USERS SUPPORTED = 00012572 TPXL5102 11/28/11.332 15:03:12.85 Allocating Master Entry in List 0 TPXL5130 11/28/11.332 15:03:12.85 CF-REQ: Func=0004, Rc=00000000, Rsn=00000000, Lst#=0000, Enty=TPXGENRCTPXTEST TPXL5116 11/28/11.332 15:03:12.85 Adding application entry for listnum(0001) TPXL5130 11/28/11.332 15:03:12.85 CF-REQ: Func=0048, Rc=00000000, Rsn=00000000, Lst#=0001, Enty=................ TPXL5130 11/28/11.332 15:03:12.85 CF-REQ: Func=0004, Rc=00000000, Rsn=00000000, Lst#=0000, Enty=DCCTPX TPXL5130 11/28/11.332 15:03:12.85 CF-REQ: Func=0048, Rc=00000000, Rsn=00000000, Lst#=0001, Enty=................ TPXL5501 11/28/11.332 15:03:12.85 XCF Connect - Group=TPXTEST Member=DCCTPX Rc=00000016 Rsn=00000031 TPXL5130 11/28/11.332 15:03:12.85 CF-REQ: Func=0036, Rc=00000004, Rsn=0C080409, Lst#=0001, Enty=................ TPXL5130 11/28/11.332 15:03:12.85 CF-REQ: Func=0036, Rc=00000000, Rsn=00000000, Lst#=0001, Enty=................ TPXL5130 11/28/11.332 15:03:12.85 CF-REQ: Func=0048, Rc=00000008, Rsn=0C1C0848, Lst#=0001, Enty=................ TPXL5158 11/28/11.332 15:03:12.85 Unlock failed - Recovery abandoned TPXL5130 11/28/11.332 15:03:13.02 CF-REQ: Func=0000, Rc=00000000, Rsn=00000000, Lst#=0000, Enty=................ TPXL5131 11/28/11.332 15:03:13.02 CF Disconnect/Normal - Rc=00000000 Rsn=00000000 TPXL5503 11/28/11.332 15:03:13.02 XCF Disconnect - Group=TPXTEST Member=DCCTPX TPX001 11/28/11.332 15:03:16.52 TERMINAL PRODUCTIVITY EXECUTIVE ACCEPTING LOGONS TPXL0500 11/28/11.332 16:59:59.19 30 Recipients had 192 Message locators on file TPXL0501 11/28/11.332 16:59:59.19 0 Message locators and 0 Messages deleted TPX9900 11/29/11.333 00:00:00.72 UNICENTER CA-TPX IS CHECKING AUTHORIZATION TPX9905 11/29/11.333 00:00:00.72 CPU SERIAL NO = 0B2E36 , MODEL = 2817 , DATE = 29NOV11 TPX9915 11/29/11.333 00:00:00.72 UNICENTER CA-TPX IS AUTHORIZED TPX200I 11/29/11.333 09:57:21.39 OK TPX030 11/29/11.333 09:57:21.69 TERMINATION REQUEST ACCEPTED TPXL5152 11/29/11.333 09:57:21.71 CA-TPX CF MANAGER TASK SHUTDOWN IS NOW IN PROGRESS TPXL5153 11/29/11.333 09:57:21.71 CA-TPX CF MANAGER TASK IS ENDING x