Messages XS4100 through XS4199

This group includes messages for the BMC AMI Ops Infrastructure product.

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

NumberDescription
XS4111I

BBI/XS RESTARTING


Explanation: After XSSTAE was entered for an error in XSDRVR, the retry routine gives control back to XSDRVR. BBI multiple-system support continues.

User response: No action is required.

XS4114W

BBI/XS WAITING FOR RESPONSE FROM xxxxxxxx'


Explanation: BBI has been waiting for a response from 'xxxxxxxx' for 10 minutes. The message will be reissued every 10 minutes until the response is received or the link is stopped. Message XS4115I will be issued if a response is subsequently received. BBI continues processing but other requests that require a response from 'xxxxxxxx' will be delayed until the outstanding response is received.

User response: You may choose to wait and see if the condition eventually resolves itself. If not, issue .P LINK xxxxxxxx to cancel all outstanding requests against the node. Then issue .S LINK xxxxxxxx to reestablish communication.

XS4114E

MAX BBI TS SESSIONS EXCEEDED - CONNECT REJECTED


Explanation: The maximum users, as specified in BBIXSP00 in BBI.PARMLIB was reached. The connection with the SS is not established.

User response: Check the value specified in BBIXSP00 for MAXUSER= and increase it if neccessary.

XS4115I

BBI/XS RESPONSE RECEIVED FROM xxxxxxxx'


Explanation: BBI issues this message if a response is subsequently received from 'xxxxxxxx' after the XS4114I message is issued. BBI continues normal processing.

User response: No action is required.

XS4116E

XSSUSR: MAX NUMBER OF ENTRIES IN XUSR TABLE


Explanation: 600 sessions are active. No further sessions can be established until some currently active sessions are terminated. These sessions are either active VTAM Links (use .D L to display) or active user sessions (use .D U to display). The attempted connection cannot complete.

User response: If you believe this message was issued erroneously, take a console dump of the BBI-SS PAS and contact BMC Support. In addition use .D L and .D U and provide BMC Support with the output. When using the DUMP command, reply to the WTOR as follows:

R xx,J=jobname,SDATA=(CSA,RGN,TRT,GRSQ)

XS4116W

XSSUSR: NEARING THE MAX NUMBER OF CONNECTIONS


Explanation: More than 500 sessions are active. These sessions either represent active VTAM Links, or users connected to the PAS. The maximum allowed is 600, but at 500 the PAS will start to issue a warning message. At this point the PAS may be using most of the storage below the line and other features may failure for storage related problems. A warning message is issued for each additional connection over 500. After 600 connections, the PAS will stop accepting new connections. The task for the connection is established and processing continues.

User response: The user may want to consider the number of active VTAM links and redesign BBINOD00 in such a way that a single PAS directly connects to fewer PASes. It is recommended to stay well below 500 active links. A BBIJNT00 and BBINOD00 configuration can be used to establish reasonable clusters of PASes that can communicate with each other through the VTAM link. Use .D L ALL to display VTAM Links. Use .D U to display users.

XS4117W

Setting DONTKILLME option, RC=XXXXXXXX, RSN=XXXXXXXX, TCB=XXXX


Explanation: The BBI-3 DONTKILLME option was set for a BBI-2 task, unless the return code and reason code are non zero. The purpose of the DONTKILLME option is to prevent task from being terminated when the CAS is forced down or ABENDs. This message is only issued if DEBUG=YES is specified in the parameter library member BBISSP00. If RC and RSN are non zero this BBI-2 task may be terminated in the event that the CAS is forced down or ABENDs. This may prevent the PAS from functioning normally.

User response: Contact BMC Software Customer Support. Save the joblog for diagnostic purposes.

XS4119E

XSSUSR: TPEND, NEW USER TASKS NOT ALLOWED


Explanation: The TPEND exit has been driven by VTAM, no new user tasks/sessions may be established until the Network is reactivated. The user task/connection is not established.

User response: Ensure that VTAM on this host is active.

Was this page helpful? Yes No Submitting... Thank you

Comments