After applying TLS maintenance, the Common Services for z/OS r14.1 procs CCISSL and/or CCISSLGW may fail with a JCL error
Article ID: 114986
CISCOMMON SERVICES FOR Z/OS90S SERVICESDATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OSCOMMON PRODUCT SERVICES COMPONENTCommon ServicesDatacom/ADCA ECOMETER SERVER COMPONENT FOCEasytrieve Report Generator for Common ServicesINFOCAI MAINTENANCEIPCUNICENTER JCLCHECK COMMON COMPONENTMainframe VM Product ManagerCHORUS SOFTWARE MANAGERCA ON DEMAND PORTALCA Service Desk Manager - Unified Self ServicePAM CLIENT FOR LINUX ON MAINFRAMEMAINFRAME CONNECTOR FOR LINUX ON MAINFRAMEGRAPHICAL MANAGEMENT INTERFACEWEB ADMINISTRATOR FOR TOP SECRETXpertwareCompress Data Compression for MVSCompress Data Compression for Fujitsu
I've just rolled out maintenance to Common Services r14.1 for TLS compatibility. The maintenance changed the CCISSL and CCISSLGW procs and added a new parm FIPS=YES/NO . Now when CCISSLGW tries to start, I receive a JCL error "excessive parameter length in the parm field".
CA Common Services for z/OS r14.1 executing the CCISSL and/or CCISSLGW procs using TLS 1.1 or 1.2.
A new parm was added to the procs for TLS, FIPS=YES/NO. When used in conjunction with other parm values, it may exceed the IBM mandated 100 character limit for parms causing a JCL error..
Use the NETPARM DD statement introduced for TLS 1.2 support by PTF RO94761
The NETPARM DD statement was added to both the CCISSL and CCISSLGW procs
The NETPARM DD points to a new member CAW4NETP included in the CAW0OPTN dataset
CAW4NETP includes the parms formerly included only on ithe parm statement itself
Prevents the JCL errors that may result by exceeding the IBM mandated 100 character limit on a parm statement
No limit to the number of characters if included in the CAW4NETP member