A user may get the following message from CA XCOM Data Transport:
XCOMM0780E Txpi 308:TxpiInitSSL Failed msg = <error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number> value = 429496
Release: CA XCOM Data Transport for z/OS
Component: xcmvs
This message is issued because either the parameter SECURE_SOCKET=YES has been specified either in the default table, the DEST member, or in the SYSIN01 file and the partner system does not support SSL.
To override the SECURE_SOCKET parameter specify SECURE_SOCKET=NO in the SYSIN01.
or
Configure the partner XCOM to support SSL.
According to IBM documentation, signal SIGXCPU gets raised when the CPU usage limit is exceeded. Please increase the permitted CPU time allowed for the OMVS segment associated with the ID being used to run the scripts to generate the self-signed (sample...) certificates.
This is not normally an error we have seen during this process. You should delete any files created by the scripts up to the point of failure. Then you can restart the process from the beginning.