XCOM SMF record layout and SSL data

Products

• XCOM Data Transport - z/OS
• XCOM Data Transport

Issue/Introduction

Looking at the XCOM SMF records and want to understand the data. Is there a published layout with content descriptions?
Trying to locate the cipher spec, TLS version, and key length if possible.

What is the meaning of  SSL_VERSION = S, SECURE_SOCKET = Y, XCOM_CONFIG_SSL is blank ?

Also, are these records compatible with using SAS reporting?

Resolution

1. For SMF records the SMFDSECT macro (XCOM library CBXGMAC) contains the SMF record layout: SMF Record and History File
Here are some relevant sections in SMFDSECT for the parameters asked about:
===
SMFSECSF DS    CL1                     SECURE_SOCKET Y OR N   #R32 #116
SMFSSCFG DS    CL256                   XCOM_CONFIG_SSL             #116
...
SMFSSLT  DS    CL1             SSL Version                        #SSSL
SMFCIPHN DS    CL50            SSL Cipher Name                    #SSSL
===
Currently, there is no column available for TLS version or key length and only the above SMFCIPHN ("SSL Cipher Name") for the cipher is available.
For adding those values in the future, a new Idea can be created on the Ideas Community with Category = "XCOM Data Transport".

2.
"SSL_VERSION = S": That refers to the XCOM SSL_VERSION parameter and 'S' would mean IBM System SSL (the older and previously deprecated OpenSSL in XCOM 12.0 is now actually removed completely after PTF LU07625).
"SECURE_SOCKET = Y": The SECURE_SOCKET parameter (also see General Parameters, R-Z) always needs to be set for an SSL type transfer.
"XCOM_CONFIG_SSL is blank": The XCOM_CONFIG_SSL parameter is the configuration file used for SSL transfers which is normally a CONFIG parameter. Currently, it will show as blank unless it is set in the SYSIN01 parameters (The Batch Interface > SYSIN01 Parameters > General Parameters, R-Z).
XCOM Engineering decided this would be changed with a new fix so that XCOM_CONFIG_SSL is always displayed irrespective of where it is set. See newly released PTFs LU13140 ("XCOM_CONFIG_SSL NOT CONSISTENTLY IN XCOM HISTORY RECORD") and LU13186 ("S0C4 ABENDS POSSIBLE AFTER APPLYING LU13140 AND WRITING SMF")
  
3. The XCOM SMF records should be compatible with SAS.