Receiving the CAS9899E errors trying to start CCITCP after upgrading to CCS version 14

book

Article ID: 49879

calendar_today

Updated On:

Products

CA 1 Tape Management CA 1 Tape Management - Copycat Utility CA 1 Tape Management - Add-On Options CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu CA Datacom CA DATACOM - AD CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Datacom/AD

Issue/Introduction

Description:

The following errors were generated trying to start CCITCP or CCITCPGW after upgrading to CCI v14 eventhough SSL is not desired.

CAS9899E Error: SSL function gsk_environment_init
CAS9899E Error: SSL function rc = 201 ->
CAS9899E Error: No key database password supplied
CAS9899E Error: SSL ErrNo = 129 ->
CAS9899E Error: EDC5129I No such file or directory.

Discovered that this can be prevented by adding the UNSECON=ONLY to the parm.

Is this a change for version 14? This parm was not necessary under the previous versions.

Solution:

With previous versions of CA Common Services, CAICCI delivered separate programs for SSL and non-SSL requirements. Beginning with CCI v14. Only the SSL capable program is being delivered. Therefore if you do not require an SSL connection you specify UNSECON=ONLY. In the CAW0PROC library we deliver two separate procs for host-to-PC connectivity and for peer-to-peer connectivity. The procs for non-SSL are delivered with a PARM statement that specifies UNSECON=ONLY.

host-to-PC connections
CCITCP -> non-SSL , PROTOCOL(TCPIP)    
CCISSL -> SSL , PROTOCOL(TCPSSL)
peer-to-peer connections
CCITCPGW -> non-SSL , PROTOCOL(TCPIPGW)    
CCISSLGW -> SSL , PROTOCOL(TCPSSLGW)

Separate procs were delivered so existing customers would not be required to modify existing CCIPARMS. The only requirement would be to copy the appropriate proc from CAW0PROC to your existing procedure library to replace what was being used previously.

Environment

Release:
Component: CCIMVS