Filter
Top Products
ANR5128E (S/390)
Unable to allocate session number for LU LU ID.
Explanation: The server is unable to assign a session number to the incoming
session.
System Action: Server operation continues. The server rejects the incoming
session.
User Response: If the MAXSESSIONS statement in the server options file has
been set correctly, the end-user (client) must wait until there is a free session before
retrying to connect with the server. If the MAXSESSIONS statement is in error,
shut down the server, correct the MAXSESSIONS statement, restart the server, and
have the client retry to connect with the server.
ANR5129W (S/390)
VTAM APPC (LU62) conversation terminated - server HALT in progress.
Explanation: The server’s APPC communications driver rejects a conversation
because the HALT command has been entered.
System Action: The server rejects the conversation and proceeds with HALT
command processing.
User Response: None.
ANR5130W (S/390)
VTAM APPC (LU62) conversation (conversation ID) with LU LU ID terminated
- insufficient memory.
Explanation: An APPC conversation has been terminated by the server’s APPC
communications driver because sufficient memory is not available to support this
conversation.
System Action: Server operation continues. The conversation is deallocated.
User Response: Allocate additional storage to the server virtual machine. There
are three ways to do this:
1. Increase the size of the REGION parameter on the JOB or EXEC statement of
the JCL used to start the server.
2. 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.
651
Tivoli Storage Manager Messages
3. Common and Platform
Specfic Messages