BPXP013I THREAD threadid, IN PROCESS pid, WAS TERMINATED BY SIGNAL signal, DUE TO CPU TIME OUT.
search cancel

BPXP013I THREAD threadid, IN PROCESS pid, WAS TERMINATED BY SIGNAL signal, DUE TO CPU TIME OUT.

book

Article ID: 45432

calendar_today

Updated On:

Products

Mainframe Software Manager (Chorus Software Manager)

Issue/Introduction

CA MSMTC abends during install with GIM43201t PROGRAM GIMSMP FAILED WITH A SYSTEM ABEND CODE OF 0EC6 followed by BPXP013I THREAD 0DFCC0000000000, IN PROCESS 33554925, WAS TERMINATED BY SIGNAL SIGKILL, DUE TO CPU TIME OUT.

Cause

Task terminates due to a CPU time out signal.  

Resolution

Verify that TIME=1440 is coded on the EXEC statement in the startup JCL. Also refer to SYS1.PARMLIB(BPXPRMxx) member for the MAXCPUTIME value or the OMVS segment CPUTIMEMAX value.
The OMVS segment is defined in RACF, ACF2 or Top Secret.

Please see z/OS UNIX System Services Planning for more information about System limits and process limits.
 
Increase your system setting for MAXCPUTIME to 7200, if your current setting is lower, using the following steps:
Display your current setting by issuing the following command from the console. These should be the same as what is coded in SYS1.PARMLIB(BPXPRMxx). There can be multiple BPXPRM members and the last two characters xx represents the one that is being used by the LPAR:
DISPLAY OMVS,MAXCPUTIME
Change MAXCPUTIME to the suggested limit temporarily by issuing the following command:
SETOMVS MAXCPUTIME=7200
Change MAXCPUTIME to no CPU limit using the following command:
SETOMVS MAXCPUTIME=86400
Change MAXCPUTIME to the suggested limit permanently by updating the following member with MAXCPUTIME(7200):
BPXPRMxx  

 

Additional Information:

z/OS UNIX System Services Planning Guide, CSM installation guide