Messages BBVT500 through BBVT599
This group includes messages for the
BMC AMI Ops Infrastructure
product.
Number | Description | ||||||
|---|---|---|---|---|---|---|---|
BBVT511E | Unable to allocate an ATB slot, no available entries Explanation: During TAS initialization, BBV determined that the ATB control block is full. TAS initialization fails. User response: Contact your MVS Systems Programmer to find out why there are no slots in the ATB. | ||||||
BBVT517E | EXCP failed for UCB=ucb, local or remote command code=command Explanation: This message follows message BBVT417E. During an EXCP session, BBV attempted to read data from or write data to the terminal with a UCB value of ucb, but failed. The local or remote command code that was issued when the error occurred was command. The TAS for the EXCP session fails. User response: See the IBM manual 3270 Information Display Systems Data Stream Programmer's Reference for a description of command codes for more information about the command value. If you cannot determine and correct the problem, contact BMC Support with the JES listings for the TAS started task. | ||||||
BBVT532E | INVALID USER ID, TERMINATION IN PROGRESS Explanation: During TAS initialization, BBV determined that the specified user ID is not a valid user ID. TAS initialization terminates. User response: Contact your Security Administrator to determine if the user ID is defined to your site external security manager (ESM) or use a different user ID. | ||||||
BBVT533E | User not authorized to use MainView Alternate Access Explanation: The ESM data base did not allow the user to access BBV. Logon is terminated. User response: See your security administrator for more information. | ||||||
BBVT534E | User not authorized for BBV logon from terminal, terminal Explanation: The ESM denied BBV logon from the specified terminal. Logon is terminated. User response: Ensure that the ESM data base does not restrict terminal terminal logon access. See your security administrator for more information. | ||||||
BBVT535E | User not authorized for BBV logon from this terminal Explanation: The ESM denied BBV logon from the terminal to which the message is issued. Logon is terminated. User response: See your security administrator for more information. | ||||||
BBVT536I | RACF security environment exists Explanation: During TAS initialization, BBV determined that the RACF external security manager is active on the system. TAS initialization continues. User response: Wait for TAS initialization to complete. | ||||||
BBVT537I | TOP SECRET security environment exists Explanation: During TAS initialization, BBV determined that the TOP SECRET external security manager is active on the system. TAS initialization continues. User response: Wait for TAS initialization to complete. | ||||||
BBVT538I | ACF2 security environment exists Explanation: During TAS initialization, BBV determined that the ACF2 external security manager is active on the system. TAS initialization continues. User response: Wait for TAS initialization to complete. | ||||||
BBVT539I | RACF, ACF2, or TOP SECRET environment does not exist Explanation: During TAS initialization, BBV could not locate an active RACF, TOP SECRET, or ACF2 external security manager on the system. TAS initialization continues without security. User response: None, unless your site requires security for all TASs. If your site requires TAS security, contact BMC Support. | ||||||
BBVT540E | Error on update attempt for an invalid ATBX block Explanation: During TAS initialization of an EXCP session, the TAS attempted to update the ATBX with a new session entry, but the ATBX is not a valid control block. TAS initialization fails and any current EXCP sessions are terminated. User response: Obtain the console log, the LOGREC record, and, if current sessions were terminated, an SDUMP containing system common area information for SQA values, and contact BMC Support. | ||||||
BBVT540I | SAF security environment exists Explanation: During TAS initialization, BBV has determined that the external security manager (ESM) is other than CA-ACF2, RACF, or CA-TOP SECRET. This message is issued for informational purposes to indicate that another type of ESM was detected. TAS initialization continues normally. User response: No action is required. | ||||||
BBVT541E | No available ATBXE block to use, terminating Explanation: During TAS initialization of an EXCP session, the TAS determined that no ATBXE is available for a new EXCP session because 32 EXCP sessions already are active. The 32 session limit is an artificial limit in BBV that can be increased. TAS initialization fails. User response: Start the TAS after other EXCP sessions become inactive or contact BMC Support to increase the concurrent EXCP session limit. | ||||||
BBVT541I | RACF is inactive Explanation: This message occurs only if RACF is the external security manager (ESM) current on the system. If issued, this message follows message BBVT536I. RACF was detected as the installed ESM, but BBV found that RACF is not active at this time. TAS initialization continues normally. User response: No action is required. | ||||||
BBVT542E | Required user ID not found, terminating Explanation: During TAS initialization, the DATA( ) was not defined with a user ID value, either in the START command or in the BBVTASxx parmlib member for the session. TAS initialization fails. User response: Check the START command string and add a DATA( ) parameter specifying a user ID. Restart the TAS. If the START command points to a BBVTASxx member, check this parmlib member to ensure that it contains a DATA( ) parameter with a user ID value. Correct the parmlib member and restart the TAS. | ||||||
BBVT543E | ATBX block is full, no available ATBXE Explanation: During TAS initialization of an EXCP session, the TAS determined that no ATBXE is available for a new EXCP session because 32 EXCP sessions already are active. The 32 session limit is an artificial limit in BBV that can be increased. TAS initialization fails. User response: Start the TAS after other EXCP sessions become inactive or contact BMC Support to increase the concurrent EXCP session limit. | ||||||
BBVT544I | REPLY 'U' TO USE CURRENT EXCP HANDLER, 'R' TO REPLACE CURRENT EXCP HANDLER, 'C' TO TERMINATE TAS SESSION Explanation: This WTO message follows message BBVT435I. During TAS initialization of an EXCP session, the attention handler being used was found to be different from the attention handlers used for currently active EXCP sessions. This message indicates that an operator response is required for the WTOR message BBVT580A, which follows. Message BBVT580A is issued. User response: See information for message BBVT580A. | ||||||
BBVT545E | Logon failure for user=userid during verify create Explanation: During TAS initialization, the TAS issued a verify create to TOP SECRET for the user ID named userid, but TOP SECRET rejected the verify create request. TAS initialization fails. User response: Contact your Security Administrator about userid or try a different user ID. | ||||||
BBVT546E | LOGON FAILED BY SECURITY, TERMINATING Explanation: During TAS initialization, the external security manager (ESM) denied access for the session. This message is issued to the terminal where the session was to be established. TAS initialization terminates. User response: Contact your Security Administrator to determine if your user ID is valid or use a different user ID. | ||||||
BBVT547E | User UserID not authorized for CLASS APPL, ENTITY=entity Explanation: During logon, the user is denied access to the resource entity, entity. Logon is terminated. User response: See your security administrator for more information. | ||||||
BBVT549I | USERID NOT PROVIDED, TERMINATION IN PROGRESS Explanation: During TAS initialization for an AutoLogon terminal, no user ID value was provided in the DATA ( ) parameter. A user ID value is required for TAS initialization, so the initializing session is terminated. This message does not appear on the MVS operator's console; it appears on the terminal defined for AutoLogon. The TAS terminates. User response: Verify that the START command being invoked or the BBVTASxx member being pointed to at session startup contains a DATA( ) parameter with a valid user ID value. If not, define the DATA( ) parameter with a user ID value permanently to the BBVTASxx member and restart the TAS, or use the P= parameter of the START command to specify the DATA( ) subparameter when restarting the TAS. | ||||||
BBVT555E | Terminating in TAS LOSTERM exit Explanation: During a VTAM session, VTAM invoked the BBV LOSTERM exit due to a terminal disconnect. The TAS for the session is terminated immediately with an S622 abend. User response: Look for VTAM console messages indicating the cause of the terminal disconnect. Contact BMC Support, if necessary. | ||||||
BBVT556I | CLSDST negative response from VTAM Explanation: This message is issued with message BBVT555E. VTAM invoked the BBV LOSTERM exit so the LOSTERM exit issued the CLSDST macro to VTAM to release the terminal for the session. In this case, VTAM was no longer communicating with the TAS session, so the CLSDST response was negative. The TAS for the session is terminated immediately with an S622 abend. User response: Look for VTAM console messages indicating the cause of the terminal disconnect. Contact BMC Support, if necessary. | ||||||
BBVT560E | FREEMAIN for ESM extracted result area failed Explanation: As part of the process of verifying the user ID and password through the external security manager (ESM), an extracted result area is established for extracting additional user ID information, such as account number, prefix, region size, or group name. When the extract function was complete, an attempt was made to free the extracted result area but the attempt failed. Session initialization continues. User response: None, unless the problem persists. If the problem persists, contact BMC Support. | ||||||
BBVT566I | STOP operator command issued for TAS user=userid Explanation: A STOP command was issued for the TAS session with a user ID value of userid. This is an informational message indicating that the STOP command has been acknowledged and termination processing is beginning. The TAS is terminated. User response: No action is required. | ||||||
BBVT580A | REPLY 'USE', 'REPLACE', OR 'CANCEL' Explanation: This WTOR message is issued because the attention handler being used for a currently initializing EXCP session was found to be different from the attention handlers used for currently active EXCP sessions. A response is required for TAS initialization continues. BBV waits for a USE, REPLACE, or CANCEL response. User response: Respond with one of the following values:
|