To determine the cause of the SEC6 within XCOM you may want to do the following:
1. Check your xcomlog for the following messages:
XCOMM0053E #SUBTASK ABEND SEC6 REASON XXXXXXXX IN MODULE(*********),
OFFSET(+XXXXXXXX)
XCOMM0054I PSW at entry to ABEND: XXXXXXXX XXXXXXXX
XCOMM0054I Data near PSW: XXXXXXXX XXXXXXXX XXXXXXXX
XCOMM0054I Abending Instr ---------*
XCOMM0054I Registers at entry to ABEND:
XCOMM0054I 0-3: XXXXXXXX XXXXXXXX XXXX009C XXXX0012
XCOMM0054I 4-7: XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
XCOMM0054I 8-B: XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
XCOMM0054I C-F: XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
Note: if you don't find it in your xcomlog check the other logs.
2. Check the contents of Register 2 and Register 3. In the above sample you will see that Reg 2 has a hex 'XXXX009C' Unix Return Code and Reg 3 has a hex 'XXXX0012' Unix Reason Code.
3. Search for the meaning of the Unix Reason Code in this IBM document: IBM Knowledge Center
Reason Code x'0012' indicates:
JRMaxChild
The maximum number of processes for this user ID has been exceeded.
Action: Ask the system programmer or system administrator to increase the MAXPROCUSER parameter of the
BPXPRMxx parmlib member.
4. In this case your System Programmer will need to increase the value of MAXPROCUSER to prevent this specific SEC6 abend.