DBIOException during the apply of editing USER parameters in Settings and at DEPLOYMENT during the 'Record target library names' stage

Products

• CA Compress Data Compression for MVS
• CA Compress Data Compression for Fujitsu
• CA Datacom
• CA DATACOM - AD
• CA Mainframe Software Manager (Chorus Software Manager)
• CA MICS Resource Management
• 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:

On USER SETTINGS after changing anything or adding a new user the APPLY does not work and in the taskoutput the following error messages are shown:

IO error sending or receiving native data: ca.datacom.db.DBIOException:

ca.datacom.db.DBIOException: ca.datacom.db.DBIOException:

MSM Deploy task fails in step Record_target_library_nam with a DataAccessResourceFailureException.

The error messages are starting like this:

An exception has occurred
Message=:org.springframework.dao.DataAccessResourceFailureException: PreparedStatementCallback; SQL [insert into datasetoverride (datasetid, methodology_style_id, 
sysobjid, deploymentid, typeobj, overridemask, finalname, overridepath, finalpath, makecontainer, mountpoint, percentfree, containermask, rffustring, hash) values
(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]; IO error sending or receiving native data: ca.datacom.db.DBIOException: ca.datacom.db.DBIOException: ca.datacom.db.DBIOException: 
java.lang.ClassCastException: [B incompatible with java.lang.Stringin Jni(DBCall)in Node(DBCall)in Session(Exception executeImmediate); nested exception is 
java.sql.SQLException: IO error sending or receiving native data: ca.datacom.db.DBIOException: ca.datacom.db.DBIOException: ca.datacom.db.DBIOException: 
java.lang.ClassCastException: [B incompatible with java.lang.Stringin Jni(DBCall)in Node(DBCall)in Session(Exception executeImmediate)

Or you find the message :

MSM0050E - CA MSM database unavailable..........................................  
  Additional Diagnostic Data:................................................... 
    Database Unavailable........................................................ 
    There was a problem accessing the database. Consult the MSM logs for  further   
      Message: PreparedStatementCallback; SQL     insert into Internallogin  (logini 
      flag2, binf, userpw)values (?, ?, ?, ?, ?, ?, ?, ?)    ; IO error      sending or  
      ca.datacom.db.DBIOException: ca.datacom.db.DBIOException:    ca.datacom.db.DB   
      java.lang.ClassCastException:     B incompatible with   java.lang.Stringin Jni(  
      Session(Exception executeImmediate); nested exception is  java.sql.SQLExcep   
      native data: ca.datacom.db.DBIOException: ca.datacom.db.DBIOException: 

Solution:

These problems are fixed by an APAR for component CA Datacom Server - RO49599

with prereqs of PRE (RO11552, RO17432, RO47345, RO48169, RO48171)

After applying above fix in some cases a MSMDEPLY was necessary to resolve the problem.

1. Apply the maintenance.
2. Stop CA MSM.
3. Run the MSMDEPLY job to deploy the maintenance to the CA MSM run-time libraries and USS paths.
4. Start CA MSM.

Environment

Release:
Component: MSM