How to avoid the messages TPXL5130 and TPXL5131 being written into the TPXLOG?
When using TPX as a Generic Resource then you will find messages TPXL5130 and TPXL5131 logging on in the TPX Log for every User:
TPXL5131 <day> <time> CA-TPX CMPL EXIT DRIVEN, RC=00000000, RSN=00000000
TPXL5130 <day> <time> CF-REQ: Func=0000, Rc=00000008, Rsn=0C1C0825, Lst#=0000, Enty=xxxx
TPXL5131 <day> <time> CA-TPX CMPL EXIT DRIVEN, RC=00000008, RSN=0C1C0825
TPXL5130 <day> <time> CF-REQ: Func=0000, Rc=00000008, Rsn=0C1C0825, Lst#=0000, Enty=xxxx
These messages protocol a request to the Coupling Facility. They are informational if the logon request is successful and are helpful in case a problem occurs.
The Return and Reason Codes are documented in the IBM manual "z/OS MVS Programming: Sysplex Services Reference". Click on the Download link on the right hand corner to download the manual.
(NOTE: As it is an IBM manual Broadcom does not take any responsibility for the information provided in it)
Use the Log Writer User Exit if those messages are not required to be written to the TPX Log.
This exit receives control any time TPX is about to write a message to the TPX Log.
The default Exit provided in dataset 'hlq.CB0VSRC(TPXULOGW)' does check for these two messages and discards them instead of writing them into the log.
It is required to link this exit without any change with the name TPXULOGW in order to remove messages TPXL5130 and TPXL5131 from the TPX Log.