PersistentFilesystemMisMountedException: DSN does not match during CSM startup
Article ID: 228878
Updated On:
Products
Issue/Introduction
During CSM/MSM startup PersistentFilesystemMisMountedException occurred.
ERROR (localhost-startStop-1) 2021-11-03 11:19:03,858 (MountPointManagerImpl.java:1067): Error has occurred while checking Managed product filesystem (ID: 2195) SYS2.CAAPM.R105.C7C4A50.ZFS mountpoint /usr/lpp/cai/apm/C7C4A50 for CSI: SYS2.CAAPM.R105.CSI options: mount=aggrgrow;added=1507825390072;csi=SYS2.CAAPM.R105.CSI
com.ca.mf20.mpm.errors.PersistentFilesystemMisMountedException: DSN does not match
There is no diagnostic data attached.
Environment
Release : 6.0
Component : Chorus Software Manager
Cause
The name of the file system dataset that CSM is expecting to be mounted at the specified mountpoint is not mounted there. In this example the mountpoint is /usr/lpp/cai/apm/C7C4A50 and the name of the file system dataset name is SYS2.CAAPM.R105.C7C4A50.ZFS. These are stored in the CSM database MOUNTPOINT table.
Resolution
The df -v /usr/lpp/cai/apm/C7C4A50 shows that currently OMVS.CAAPM.R105.C7C4A50.ZFS it mounted to /usr/lpp/cai/apm/C7C4A50 and not SYS2.CAAPM.R105.C7C4A50.ZFS. This explains the exception.
This is stored on CSM database. Run this DBSQLPR to list all the mountpoints on the database and identify the specific one by comparing the mountpoint and file system name to those in the exception. For this example this is that mountpoint
row/record:
MOUNTPOINTID, <2195>, INT NOT NULL
MP_PATH, < /usr/lpp/cai/apm/C7C4A50>, VARCHAR(24/240)
MP_DATASET, < SYS2.CAAPM.R105.C7C4A50.ZFS>, VARCHAR(27/45)
MP_TYPE, < PRODUCT>, VARCHAR(7/20)
MP_OPTIONS, < mount=aggrgrow;added=1507825390072;csi=SYS2.CAAPM.R105.CSI>, VARCHAR(58/2000)
SYS2.CAAPM.R105.C7C4A50.ZFS should be changed to OMVS.CAAPM.R105.C7C4A50.ZFS. To list the MOUNTPOINT's run this DBSQLPR JCL.
//STEP05A EXEC PGM=DBSQLPR,
// PARM='PRTWIDTH=1500,INPUTWIDTH=72,ROWLIMIT=7000'
//* The STEPLIB below should be the same as the MSMMUFS startup
//* The CXX below should have the same HLQ as the PXX in the
//* MSMMUFS startup except that the DDNAME is CXX and that last
//* qualifer is also CXX in this JCL.
//*
//*
//STEPLIB DD DSN=hlq.CUSLIB,
// DISP=SHR
// DD DSN=hlq.CAAXLOAD,
// DISP=SHR
//CXX DD DSN=hlq.CXX,
// DISP=SHR
//SYSUDUMP DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//STDERR DD SYSOUT=*
//STDOUT DD SYSOUT=*
//OPTIONS DD *
AUTHID=CASWMGT
/*
//SYSIN DD *
//SYSIN DD *
SELECT * FROM MOUNTPOINT;
/* Run the DBSQLPR JCL with this input to correct it:
//SYSIN DD *
UPDATE MOUNTPOINT SET MP_DATASET='OMVS.CAAPM.R105.C7C4A50.ZFS'
WHERE MOUNTPOINTID=2195 ;
/*
Note that this is just an example. The MOUNTPOINTID, the mountpoint/directory and file system name will be different for each exception. The MOUNTPOINTID for the identified row/record must be the same in the SQL UPDATE statement.
Feedback
