Messages BBVL700 through BBVL799
This group includes messages for the
BMC AMI Ops Infrastructure
product.
Number | Description |
|---|---|
BBVL701I | Logon in progress for userid at hh:mm:ss on dd:mmm:yyyy Explanation: This is an informational message indicating that a user has issued the LOGON command or abbreviated logon command from a VTAM terminal and has specified a user ID of userid. The LAS has established communications with the terminal and has issued a START command to create a TAS for userid at the time (hh:mm:ss) and date (dd:mmm:yyyy) indicated. NOTE: For XA systems, the yyyy value is a 2-digit value only. The LAS starts a TAS for userid. If the userid value is a valid user ID, the password panel is displayed by the TAS, or a menu is displayed if userid does not a require clear text password. User response: Wait for TAS initialization. |
BBVL702E | Logon terminating Explanation: A user issued the LOGON or abbreviated logon command from a VTAM terminal, but the LAS encountered a condition which caused termination of the requested logon. The type of condition encountered could be an invalid user ID was specified, a TAS could not be initialized before the timeout value expired, or another reason. Other messages are issued. User response: Look for other messages that indicate the reason for the logon termination and perform the actions associated with those messages. |
BBVL704E | LAS logon failed for userid Explanation: The LAS started a TAS for userid, but the TAS encountered a condition which caused termination of the requested logon. The type of condition could be that userid is an invalid user ID or another reason. Other messages are issued. User response: Look for other messages that indicate the reason for the logon termination and perform the actions associated with those messages. |
BBVL705I | Logon terminated Explanation: This is an information message indicating that a minor condition was encountered which caused termination of the requested logon. Typically, this message is issued if the END key is pressed during logon processing. Logon processing is terminated. User response: Re-enter the LOGON or abbreviated logon command. If the problem persists, look for other messages which may indicate the problem and attempt to correct it. Contact BMC Support if necessary. |
BBVL708E | Maximum user limit exceeded - try again later Explanation: The LOGON or abbreviated logon command was issued from a VTAM terminal and the LAS issued a START command for a TAS. However, all VTAM minor nodes are either inactivated or are currently being used, so a new TAS session cannot be supported. Logon processing is terminated. User response: Try logging on at a later time when a minor node is available, ensure all minor nodes are active, or define additional minor nodes to the VTAM application major node definition and reactivate the major node User Guide for more information). |
BBVL709E | TAS could not open ACB Explanation: The LOGON or abbreviated logon command was issued from a VTAM terminal and the LAS issued a START command for a TAS. However, the ACB for the VTAM minor node the TAS was attempting to connect to malfunctioned or all minor nodes are currently being used. Logon processing is terminated. Other messages are issued if an ACB malfunctioned. User response: Try logging on at a later time if all minor nodes are currently in use. If an ACB malfunctioned, look for other messages that indicate the problem and correct it. Contact BMC Support if necessary. |
BBVL715I | Press ENTER to continue Explanation: This is an informational message that is issued to the terminal session with a wait function, so you have time to read other messages that indicate the condition that has occurred. When ENTER is pressed, control of the terminal is returned to VTAM. The terminal session waits until ENTER is pressed. User response: Press ENTER. |
BBVL717E | SEND failed to logicalUnit, code=rcfb Explanation: During the initial logon processing, a failure was detected while attempting to send the initial logon-in-progress screen, where logicalUnit is the logical unit name and rcfb is the VTAM reason and feed back code. The logon request is terminated. User response: See IBM publication IP and SNA Codes for an explanation of the RPL RTNCD and FDB2 return codes. |
BBVL718W | MGCR Failed, RC=XXXXXXXX Explanation: While attempting to start a TAS address space, a non-zero return code was received from MGCR. Some of the possible reasons are:
Processing continues assuming that Auto Operator has interfered and the request was actually honored. User response: If the system actually denied the request, you will have to log on at another time. |
BBVL719E | Invalid ASID returned by MGCR, ASID=XXXXXXXX Explanation: The ASID returned by MGCR does not appear to be valid. Either the value did not conform to the conventions for a valid ASID, the ASID was invalid or the address space for this ASID does not appear to be a BBVTAS address space. This error can be caused because the PROC used to start the TAS address space contained a JCL error or simply does not exist. Possibly Auto Operator has intercepted the START command in order to validate it. Unfortunately, Auto Operator does not include the token that Alternate Access passes to MGCR. As a result, the BBVTAS might start but it will not find the token and assume that a UCB or TERMID is required. Processing continues assuming that Auto Operator has interfered and the request was actually honored. If the TAS does not start in the indicated ASID within a few minutes, the terminal is released. User response: If Auto Operator intercepted the START command, see the FAQ for Auto Operator on how to modify your rules so that Alternate Access will not be intercepted. Check the system LOG to make sure the procedure that was started did, if fact, start. Correct any JCL errors that may cause the procedure to fail. Check for messages from the procedure that may indicate a reason for a premature termination. |