CA CSM Startup Failed

Article Id: 108588

Status: Published

Updated On: 31-01-2019 07:03

Products:

CA Mainframe Software Manager (Chorus Software Manager)

Issue/Introduction:

CA CSM Startup failed with messages:
---------------------------------------------------------------
MSM0010E CA CSM STARTUP FAILED
---------------------------------------------------------------
MMS0001E - Insufficient privileges: server requires FACILITY:BPX.SERVER(READ).
(mvsutil/mvsutil.c:535): mvsutil_setuid: setuid(0) failed: errno=139 EDC5139I Operation
not permitted.
---------------------------------------------------------------

Cause:

The message indicates (READ) privileges have been granted, but the ACID (UserID=SWMGRQA) that the Tomcat Server
runs under needs (UPDATE) access to the facility BPX.SERVER.

Environment:

Release:
Component: MSM

Resolution:

Your security administrator must configure the following access:
– BPX.SERVER (UPDATE authority)

Also permission to access the following FACILITY class profiles that are related UNIX:
– BPX.FILEATTR.APF (READ authority)
– BPX.FILEATTR.PROGCTL (READ authority)
– BPX.FILEATTR.SHARELIB (READ authority)
– BPX.SERVER (UPDATE authority)
– BPX.CONSOLE (READ authority)

Additional Information:

https://docops.ca.com/ca-chorus-software-manager/6-1/en/preparing-for-installation/set-up-security-for-ca-csm-with-ca-acf2-for-z-os