We have performed all of the installation requirements for the new ESM Micro-service , but upon starting the task ZMSSTART it ends RC=0100.

Products

• Compress Data Compression for MVS
• Compress Data Compression for Fujitsu
• SYSVIEW Performance Management
• NXBRIDGE - SYSVIEW/ENDEVOR
• OPS/MVS Event Management & Automation

Issue/Introduction

After installing and deploying the Common Service component the Message Service the ZSMSSTART PROC does not come up.

The task ends RC=0100 and the following is observed in the job log :

JVMJZBL2008E Could not find or load class: com.ca.messagingservice.engine.MessagingServiceApplication 

 

Environment

Any supported release of z/OS.

Cause

This is basically equivalent to an MVS abend S806 module not found. This indicates that either a file system is not mounted, the STC / ACID assigned to the task does not have permissions to access the path, or the path does not exist. 

In this case the file system was not mounted due to an IPL of the system but the BPXPRMXX member had not been updated to mount the ESM USS files at IPL time.

 

 

Resolution

The user redeployed the target file system and verified it's contents. Afterwards the ZSMSTART STC came up without error.  

This is basically equivalent to an MVS abend S806 module not found. This indicates that either a file system is not mounted, the STC / ACID assigned to the task does not have permissions to access the path, or the path does not exist. 

In this case the file system was not mounted due to an IPL of the system but the BPXPRMXX member had not been updated to mount the ESM USS files at IPL time.

 

Update the BPXPRMXX member and all is resolved.

Additional Information

None