- Detailed and accurent version number (OS, product, patch level)  == PEL732 SP2-P2
- Product problem description == frequent abends S106-0C for modules PELGETKY and PELPSRCE in Monitor task.

The analysis shows that an extremely high number of transfer attempts occuring in the prior 30 minutes and continuing to the point abends started happening. The IEW4000I message indicates the their was a Short on Storage condition.

IEW4000I FETCH FOR MODULE PELGETKY FROM DDNAME STEPLIB  FAILED BECAUSE INSUFFICIENT STORAGE WAS AVAILABLE.

The Short On Storage condition was due to lower memory (below line) being exhausted. Each InterPel transfer request loads 2 modules into lower memory and allocates 2 TCB's. These TCB's require 254 bytes of storage each and this does not include the storage required by each module (varies based on protocol)

The first abend occurs at 3.46.30 when trying to load in PELGETKY, each abend has consistently same PSW at point of abend (PSW AT TIME OF ERROR  470C1000   8155BBE0) and the same Data at PSW (DATA AT PSW  0155BBDA - 8400181E  0A0D18FB  180C181D).

There are a couple of possible solutions and the customer must decide which one to implement. The first is to limit the number of available active sessions at the protocol or site level. This can be set on the GENLIGN macro by using the MSESSOU parameter. The monitor will only run the max number of connection and queue the rest.

MSESSOU={nn|10}
nn: Maximum number of simultaneous outgoing connections requested by
Inter.Pel for terminals defined in the GENTER macro-instructions
associated with this GENLIGN definition. It is used only for DYN, STAT or
LU62 type GENLIGN definitions.
Default: 10.

The MAXCON can be set on the GENSITE when the LINGRP is used.
MAXCON={n|1}
Used when the LINGRP parameter is set. Maximum number of
simultaneous outgoing connections (must be set to 1 in the NPSI PCNE
mode).
NOTE: if the maximum number of connections is reached, Inter.Pel creates
an additional connection when a 0 priority transfer request is
submitted.
Default: 1.

There is also the possibility of creating another Transfer Monitor. In this case the new monitor would run in its own address space with its own lower memory pool.

We have had customers use all three approaches, once they have reconfigured and throttled the transfers this problem has never occured again.