OPS/MVS OPS3441S Process Block Depletion OPS3441O

book

Article ID: 187919

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

We reloaded an LPAR this weekend and whilst it was coming down, OPSMVS issued message

OPS3441S POSSIBLE PROCESS BLOCK DEPLETION, CODE=B (25 0 0 ) 

The manual says this message should have an O suffix not an S

Also, we have 3 variables in the brackets, whereas the manual only shows 2.

Cause

The Process Block Depletion problem was determined to be caused by stopping a large number of initiators at the same time. 

Environment

Release : 13.0 and prior   

Component : OPS/MVS

Resolution

For release 13.0, we recommend a more controlled procedure for stopping the initiators.  This can be achieved by replacing the $PI command with a series of commands to stop ranges of initiators, with OPSWAITs between each command.

The section of STOPJES2 that stops the initiators is:
    Call WARNMSG(" - Stopping JES2 initiators, lines, and printers") 
    Call ISSUE_COMMAND cmdchar||"P I"                                

The last command should be replaced with code similar to:
   Call ISSUE_COMMAND cmdchar||"PI(1-20)"        
    t = OPSWAIT(2)
   Call ISSUE_COMMAND cmdchar||"PI(21-40)"        
    t = OPSWAIT(2)
...
And so on until all the initiators are stopped.