DCI0999E: WRITE_XML,WRITEFILE: ( 0/10) DCI0999E: FILE: /USR/LOCAL/DCI/XML/POLICY-STATUS.XML, ERRNO: , ERRNOJR: DCI1351I: POLICY AND CAPACITY CHECK CYCLE COMPLETED. DCI0999E: WRITE_XML,WRITEFILE: ( 0/8) DCI0999E: FILE: /USR/LOCAL/DCI/XML/CNTL.XML, ERRNO: , ERRNOJR: DCI1353E: ERROR -256 GETTING USS DISK INFO DCI1005E: MAX RESTARTS OF TEST TASK REACHED DCI1004I: STOP COMMAND FORCED BY ZDC DCI1308I: CONTROLLER MAIN TASK SHUTDOWN IN PROGRESS DCI1328I: CONTROLLER IP TASK SHUTDOWN IN PROGRESS DCI1329I: CONTROLLER IP TASK SHUTDOWN COMPLETED DCI1318I: RULE TASK SHUTDOWN IN PROGRESS DCI0999E: WRITE_XML,WRITEFILE: ( 0/8) DCI0999E: FILE: /USR/LOCAL/DCI/XML/CNTL.XML, ERRNO: , ERRNOJR: DCI1319I: RULE TASK SHUTDOWN COMPLETED DCI1338I: CONTROLLER DB TASK SHUTDOWN IN PROGRESS DCI1339I: CONTROLLER DB TASK SHUTDOWN COMPLETED DCI1348I: REPORT TASK SHUTDOWN IN PROGRESS DCI1349I: REPORT TASK SHUTDOWN COMPLETED DCI1368I: CONTROLLER SERVICE TASK SHUTDOWN IN PROGRESS DCI1369I: CONTROLLER SERVICE TASK SHUTDOWN COMPLETED DCI1358I: CONTROLLER MOI TASK SHUTDOWN IN PROGRESS DCI1359I: CONTROLLER MOI TASK SHUTDOWN COMPLETED DCI1309I: CONTROLLER MAIN TASK SHUTDOWN COMPLETEDThen the step gets an RC 12.
Release : 2.0
Component : CA DYNAMIC CAPACITY INTELLIGENCE
Spawn error: err=70x rsn=B0F0028x
Spawn error: err=70x rsn=B0F0028x
Spawn error: err=70x rsn=B0F0028x
Spawn error: err=70x rsn=B0F0028x
5286 +++ call merrorx 'write_xml','writefile',rc,retval,dst_file
5131 +++ call write_xml p_nr
1407 +++ call put_xml g.status
245 +++ call write_status
124 +++ call schedule_policy_calculation
79 +++ call req_testpol
IRX0043I Error running ?, line 5286: Routine not found
1 +++ CALL DCIC0010
IRX0040I Error running DCIC0007, line 1: Incorrect call to routine
1 +++ CALL DCIC0010
IRX0043I Error running DCIC0007, line 1: Routine not found
1 +++ CALL DCIC0010
IRX0043I Error running DCIC0007, line 1: Routine not found
Spawn error: err=70x rsn=B0F0028x
| 112 | 0070 | EAGAIN | The resource is temporarily unavailable. |
rsn=B0F0028x (z/OS UNIX reason codes)
| 0028 | JRMaxProc
The maximum number of processes was exceeded. Action: Retry after some processes have ended, or change the maximum number of processes allowed. |
So the problem is actually due to the maximum number of processes that can be active at the same time on USS.