CA MSMCPROC Initialization Fails User Completion code=U1015, Reason code=00000002

Products

• Mainframe Software Manager (Chorus Software Manager)

Issue/Introduction

Problem:

When I attempt to start the SCS started task (MSMCPROC) it abends. What could be the problem? 

MSMC0001I SCS initialization in progress

MSMC0032I SVC dump for task MSMCJTSK suppressed by DAE 

MSMC0036I Symptom dump output for task MSMCJTSK 548 

User Completion code=U1015, Reason code=00000002 

Time=14:31:31, Seq=02249, CPU=0000, ASID=0108 

PSW at time of error=078C1000 A391172A, ILC=2, INTC=0D 

PSW load module name=MSMCJINI, address=23911000, offset=0000072A 

PSW section name=MSMCJINI, address=23911000, offset=0000072A 

Data at PSW 23911724 - 00181610 0A0D5810 A0405E10

 

Environment:

CA CSM - Any supported release

CA Common Services (CCS) for z/OS release 14.1 S1401

 

Cause:

This specific abend can result from a couple of factors, such as:

1. Attempting to start MSMCPROC on a system where MSMTC was not running.

2. Attempting to start MSMCPROC with an assigned user-id that is missing the required security privileges.

 

Resolution:

1.  If the MSMTC task is not currently running, start it after ensuring the MSMMUF and MSMDBSRV tasks are active.

2.  Set up security for SCS address space, MSMCPROC.

• MSMCPROC user ID must have an OMVS segment defined.
• MSMCPROC user ID must have read access to the CCS CAW0LOAD and CAW0PLD data sets.
• MSMCPROC user ID must have read access to the CA CSM CAAXLOAD and CUSLIB data sets.
• MSMCPROC user ID does not need OMVS UID(0) or Super User privileges.

Refer to your security product documentation for specifics on how to define an OMVS segment. In general, a valid OMVS segment requires each of the following items:

UID, HOME directory, OMVSPGM, GROUP, and DFLTGRP 

Environment

Release:
Component: MSMSCS