SSI PROBLEM: NF7Y10 FOLLOWED BY NF7Y11 AND NS2101

book

Article ID: 130201

calendar_today

Updated On:

Products

CA CMDB for z/OS CA NetSpy Network Performance CA NetMaster Network Automation CA SOLVE CA NetMaster Network Management for SNA CA NetMaster Network Management for TCP/IP CA NetMaster File Transfer Management

Issue/Introduction

Cust reported an SSI problem occurring after he enabled type 119 SMF
records in NetMaster.

Environment

OS: z/OS.

'SOLVESSI' and 'NetMaster user' regions run separately.

Resolution

These messages appeared on the SSI output:

*NF5Z01 DB/DS: DYNAMIC/DDB STORAGE IS AT 80%
*NF5Z01 DB/DS: DYNAMIC/DDB STORAGE IS AT 83%
*NF5Z01 DB/DS: DYNAMIC/DDB STORAGE IS AT 87%
*NF5Z01 DB/DS: DYNAMIC/DDB STORAGE IS AT 91%
*NF5Z01 DB/DS: DYNAMIC/DDB STORAGE IS AT 95%
*NF5Z01 DB/DS: DYNAMIC/DDB STORAGE IS AT 96%
NF7Y10 PA DATABASE/DATASPACE DYNAMIC/DDB AT LIMIT, AUTO
SHUTDOWN PROCESSING COMMENCED
NF7Y10 PA DATABASE/DATASPACE DYNAMIC/DDB AT LIMIT, AUTO
SHUTDOWN PROCESSING COMMENCED
NF7Y11 AUTO SHUTDOWN PROCESSING  COMPLETED
NF7Y11 AUTO SHUTDOWN PROCESSING  COMPLETED
NS2101 NMSSI SHUTDOWN IN PROGRESS. SSID: NETM

 
L2 Support requested command output from these--that  can be
issued on NetMaster Command Entry:

 
$$syspro nmipdiag
onetstat -f
ssis sh paddbstg level=4
 
L2 Support commented based on the command output analysis:
 
As seen in the SSISTATS cust are keeping HISTORY for  many
of their connections.

NF8O27 TCN 392486 -A 15289 -H 377197

Please change all Expiry Periods for connections to '0'. 

To do that do:

/IPAPPL



The best practice is to have all application definitions set to 'Expiry
Period ............. 0' .


Cust made these changes and SSI database   stopped increasing.

Additional Information

Additional information from L2 Support:
 
Expiry Period greater than 0 (on /IPAPPL applications) is primarily used
for troubleshooting application problems where history for specific
applications is kept and then turned back off
when finished.

Easy to prove that the change resolved the problem: Do SSIS SH
PADDBSTG LEVEL=4 and one should notice
that
DDB utilization stays stagnant.

Changes to /IPAPPL are dynamic--one doesn't need to restart the
SOLVESSI in order to make these changes.