CSM gives message : 500 Internal Server Error The call failed on the server; see server log for details
search cancel

CSM gives message : 500 Internal Server Error The call failed on the server; see server log for details

book

Article ID: 4306

calendar_today

Updated On:

Products

Mainframe Software Manager (Chorus Software Manager)

Issue/Introduction

During startup of the CSM Tomcat server you see the error message :

 SEVERE: Exception while dispatching incoming RPC call com.google.gwt.user.server.rpc.UnexpectedException: Service method 'public abstract com.ca.mf20.ui.foundation.client.tasks.TaskInfo com.ca.mf20.ui.msm.settings.client.rpc.SettingsSrvc.startImmediateCarsUpdate()' threw an unexpected exception: com.ca.mf20.errors.SystemError: SystemError has occurred. The cause is ExecutionFailedException.
  Attached Diagnostic Text:
    An unexpected error has occurred while creating temporary space for mountpoint /msm/mpm/tmproot, dataset name OMVS.MSM50.T248, primary tracks 1000, secondary tracks 1000 in the security context of the server.
..
Caused by: com.ca.mf20.zos.api.process.errors.UssProcessTerminatedError: MME0260S - Process 0x300010F terminated by signal 0x12.
 Attached Internal Log:                                                                                                        
   MME0260S - Process 0x300010F terminated by signal 0x12.      
..

Environment

z/OS

Cause

The SYS1.SIEALNKE needs to be APF authorized.

Resolution

Specify the SYS1.SIEALNKE dataset in the APF list.

Additional Information

If it's APF authorized, and you still have the same failure within the CSM Tomcat server, check the volser it's defined on in the APFLSTnn member, and if it's really on that volser.