CA Datacom Server DSV00119E - TCP/IP startup time limit exceeded
Article ID: 32076
Updated On:
Products
Issue/Introduction
CA Datacom Server mainframe startup (PGM=SVDBSPR) fails with errors:
DSV00119E - TCP/IP startup time limit exceeded
SER: Only 39 threads created - quit 408
DSV00120E - TCP/IP startup failed see DSV00119E for cause 409
Environment
Release:
Component: CA Datacom Server
z/OS
Protocol TCP/IP
Cause
The CA Datacom Server startup option TCPIP_CONNECT_QUEUE to specify the number of TCP/IP threads was too large and the REGION=n was too small to handle the maximum number of threads.
Resolution
Decrease the TCPIP_CONNECT_QUEUE value appropriate to the number of DBUSERS or allow it to default and increase REGION (REGION=0M suggested).
When allowed to default, CA Datacom Server computes the TCPIP_CONNECT_QUEUE to 2 times the number of the DBUSERS specified in the startup.
CA Datacom Server sets the maximum to 150 even if the value is specified higher (with no error or warning) or if DBUSERS is greater than 75.
Also, the REGION must be large enough to handle the number of TCP/IP threads requested.
In the case noted, TCP_CONNECT_QUEUE was set to 250 with REGION=6M. The problem was resolved once the value was set more appropriate to the number of desired DBUSERS as well as setting REGION=0M.
Additional Information
Refer to the CA Datacom Tools Version 15.1 section on "Using CA Datacom Server"
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-mainframe-software/database-management/ca-datacom-tools/15-1/working-with-ca-datacom-server-15-0/using-ca-datacom-server.html
Refer to the CA Datacom Messages for DBSV00119I and DBSV00120I
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-mainframe-software/database-management/ca-datacom-tools/15-1/ca-datacom-messages/ca-datacom-server-messages/mainframe-messages/dsv00119i.html
Feedback
