ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

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

book

Article ID: 49200

calendar_today

Updated On:

Products

Compress Data Compression for MVS Compress Data Compression for Fujitsu Datacom DATACOM - AD Mainframe Software Manager (Chorus Software Manager) MICS Resource Management CIS COMMON SERVICES FOR Z/OS 90S SERVICES DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS COMMON PRODUCT SERVICES COMPONENT Common Services CA ecoMeter Server Component FOC EASYTRIEVE REPORT GENERATOR FOR COMMON SERVICES INFOCAI MAINTENANCE IPC UNICENTER JCLCHECK COMMON COMPONENT Mainframe VM Product Manager CHORUS SOFTWARE MANAGER CA On Demand Portal CA Service Desk Manager - Unified Self Service PAM CLIENT FOR LINUX ON MAINFRAME MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME GRAPHICAL MANAGEMENT INTERFACE WEB ADMINISTRATOR FOR TOP SECRET Xpertware 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