Filter
Top Products
System Action: Server operation continues. Support for the TCP/IP COMMmethod
is enabled.
User Response: None.
ANR5091E (S/390)
Unable to initialize TCP/IP driver - insufficient memory.
Explanation: The server’s TCP/IP communications driver is unable to initialize
itself due to insufficient memory (virtual storage).
System Action: Server initialization fails.
User Response: Allocate additional storage to the server virtual machine. There
are three ways to do this:
1. On VM, increase the size of the server’s virtual machine. This requires that the
default storage size be updated in the server’s CP directory entry.
2. On MVS, increase the size of the REGION parameter on the EXEC or JOB
statement of the JCL used to start the server.
3. Reduce the maximum number of client sessions permitted. To do this, edit the
server options file and reduce the value specified for the MAXSESSIONS
statement. Note that each client session causes an additional 64KB of memory to
be allocated.
4. Decrease the amount of space allocated to the server’s database buffer pool. To
do this, edit the server options file and reduce the value specified for the
BUFPOOLSIZE statement. Note that each buffer pool page causes an additional
4KB of memory to be allocated.
Note that the server must be shut down (with the HALT command) before changes
can be made to the server options file.
ANR5092E (S/390)
Unable to initialize TCP/IP driver - error creating acceptor socket.
Explanation: The server’s TCP/IP communications driver is unable to create its
critical listening socket, and so TCP/IP communications cannot be initialized.
System Action: Server initialization continues. TCP/IP communications
initialization will be retried.
User Response: Check that TCP/IP is running, and that TCPName in the options
file matches the TCP/IP subsystem name you intend to use.
640
Version 3 Release 7