SLOT 12 BELOW THE LINE OVERFLOW on startup

book

Article ID: 76480

calendar_today

Updated On:

Products

CA TPX - Session Management TPX- PACKAGE CA Vman Session Management for z/OS TPX SESSION MANAGEMENT

Issue/Introduction

SLOT 12 BELOW THE LINE OVERFLOW
Reviewed TPXOPER display command D STOR. Shows 0% Current Use and 0% Max Use with 3 Failed.  How is that possible?

From TPXOPER D STOR:
Slot   Size  * Count  =  Bytes     Curr.Use   Max.Use   Failed      Requests 
  01    00008   6656      53248       000 %     000 %    0           0        
  02    00016   4096      65536       000 %     000 %    0           1        
  ... 
  11    08192   16        131072      000 %     006 %    0           5 
  12    10240   0         0           000 %     000 %    3           0 
******************************** BOTTOM OF DATA ******************************


 

Cause

TPX started task is using REGION=5000K.  We recommend REGION=0M.

5000K did not allow enough storage available to define slot 12 once TPX modules and other required items like the SMRT, SACBs, etc., were loaded.  This is evident in the TPXOPER display above with the zero value for slot 12 Count and Bytes.

In this situation, TPX managed by using Dynamic Storage Area (DSA) when otherwise slot 12 below the line would have been used.

Environment

Release: NVINAM00200-5.4-TPX-Session Management-Access Management package
Component:

Resolution

Change REGION=5000K to REGION=0M and restart TPX.

Additional Information

TPX 5.4 - Adjust Storage Parameter ...this explains how TPX manages storage

Why does CA recommend the region size for the TPX proc be set to 0M?  Document ID : KB000032062