TPXL5130 / TPXL5131 Reason Code 0C1C0825

Products

• TPX - Session Management

Issue/Introduction

 

When users sign on to TPX we see the following TPXL5130 and TPXL5131 messages in the log.

TPXL0101 07/21/25.202 01:19:17.13 LOGON   TERMINAL: XXXXXXXX XXXXXXXX                                   
TPXL5131 07/21/25.202 01:19:23.84 CA-TPX CMPL EXIT DRIVEN, RC=00000008, RSN=0C1C0825                    
TPXL5130 07/21/25.202 01:19:23.84  CF-REQ: Func=0000, Rc=00000008, Rsn=0C1C0825, Lst#=0000, Enty=X*******
TPXL5131 07/21/25.202 01:19:23.86 CA-TPX CMPL EXIT DRIVEN, RC=00000008, RSN=0C1C0825                    
TPXL5130 07/21/25.202 01:19:23.86  CF-REQ: Func=0000, Rc=00000008, Rsn=0C1C0825, Lst#=0000, Enty=X*******
TPXL5131 07/21/25.202 01:19:23.86 CA-TPX CMPL EXIT DRIVEN, RC=00000000, RSN=00000000                    
TPXL5130 07/21/25.202 01:19:23.86  CF-REQ: Func=0004, Rc=00000000, Rsn=00000000, Lst#=0001, Enty=X*******
TPXL0010 07/21/25.202 01:19:23.86 SIGNON  TERMINAL: SECZ0041 2E8FB7C0 USER: X*******  2D148270           

We do have a generic resource configured and these coupling facility requests seem to always give RC 8 and RSN Code 0C1C0825 on 2 consecutive CF requests with Func 0000 and then the third CF requests for Func 0004 comes back clean.

Looking for some assistance as to what these 3 CF requests are trying to accomplish? What does the Function code and the RC 8, RSN code 0C1C0825 return codes mean? 

Environment

TPX 5.4

Resolution

Return and reason codes can be referenced from MVS Programming Sysplex Service Reference. Below is the link for the pdf

MVS Programming Sysplex Service Reference

Below are the most frequently seen functions in the TPX LOG. 

CF-REQ 0000 - READ
CF-REQ 0004 - WRITE
CF-REQ 0012 - DELETE

When the user tries to sign in, TPX reads the list to make sure the user is already logged in in any of the GR regions. If the user is, they are switched to that particular session. If not, read fails with RC=00000008 and RSN=0C1C0825, meaning TPX was not able to find the user in any of the list entries.

Most of these messages are just informational.

Since TPX did not find the user already in the list, it does the routing of the user to the appropriate TPX region based on the workload balancing algorithm used in the site, and will update the appropriate list entry as below.

TPXL5130 07/21/25.202 01:19:23.86  CF-REQ: Func=0004, Rc=00000000, Rsn=00000000, Lst#=0001, Enty=X*******
TPXL0010 07/21/25.202 01:19:23.86 SIGNON  TERMINAL: XXXXXXXX XXXXXXXX USER: X*******  2D148270           

When the user logs off from TPX, another function kicks in to delete the user from the list. 
TPXL5130 07/24/25.205 19:01:56.43  CF-REQ: Func=0012, Rc=00000000, Rsn=00000000, Lst#=0001, Enty=X*******........   
TPXL0010 07/24/25.205 19:01:56.43 SIGNOFF TERMINAL: XXXXXXXX XXXXXXXX USER: X******* 58EE4000                        

To check what routing algorithm those GR TPX regions are using, use the two commands against your GR ID

D NET,E,ID=XXXXXXXX (Check what the status of WLM)  <<<<<< Where XXXXXXXX is your Generic Resource Name. >>>>>>>>

D NET,GRAFFIN,GNAME=XXXXXXXX  (6th bytes under attributes column will tell you whether it is WLM managed or default ISTGENERIC)