Using XCOM for z/OS with AT-TLS and see this message after attempted secure transfer on port 8045
11:19:11 ##.##.#.# 095882 JOBNAME1 XCOMM0811I STARTING SECURE TCP/IP CONNECTION TO PORT=08045, IP=##.##.#.# 11:19:11 ##.##.#.# 095882 JOBNAME1 XCOMM0813I SECURE TCP/IP CONNECTION REQUESTED WITH DEST=**NONE**, PORT=08045, IP=##.##.#.# 11:19:11 ##.##.#.# 095882 JOBNAME1 XCOMM0780E Txpi 411: TxpiSystemSSLConfig Mandatory item missing Element nb: 0 Section = <KEYRING_FILE> Parameter = <INITIATE_SIDE> Value = 11:19:12 ##.##.#.# 095882 JOBNAME1 XCOMM0093E ERROR ACTIVATING SESSION - SESSION NOT ESTABLISHED
XCOM Data Transport® for z/OS
The SECURE_SOCKET parameter had been set to YES instead of NO.
Therefore XCOM was trying to looking for SYSTEM SSL configuration parameters like KEYRING_FILE in the XCOM_CONFIG_SSL file and not finding them.
SECURE_SOCKET must be set to NO for AT-TLS per this article: Enabling encryption for XCOM for z/OS transfers using AT-TLS
i.e.
a. To initiate secure transfers using AT-TLS, you must not specify SECURE_SOCKET=YES in the XCOM parameters. The idea is that XCOM starts an unsecure transfer. AT-TLS makes it secure, XCOM notices the fact and issues messages informing that the connection is protected by AT-TLS. The transfers must be addressed to the SSL port at the partner.