Messages BBVJ000 through BBVJ099
This group includes messages for the
BMC AMI Ops Infrastructure
product.
Number | Description | ||||||
|---|---|---|---|---|---|---|---|
BBVJ002E | Identify failed for BBVJSETP, RC=X'returnCode' Explanation: During initialization, the BBVJSETP module is attached by the MVS module IKJEFT01 to provide support for TSO services. This attach function failed with the indicated return code because BBVJSETP could not be identified externally to TSO. The return code is a hexadecimal value. TAS initialization fails and the session is not started. User response: See information about the IDENTIFY macro in the IBM manual MVS Assembler Programming Reference for the return code value. If you cannot correct the problem, contact BMC Support with the return code value in this message. | ||||||
BBVJ003E | Non zero return code from IKJEFT01, RC=returnCode Explanation: During TAS initialization, the TMP (Terminal Monitor Program) named IKJEFT01 did not initialize and issued the indicated hexadecimal return code. TAS initialization terminates. User response: The TSO/E messages indicating the exact nature of the TAS initialization failure are written to SYSTSPRT. To obtain a listing of these messages to determine the nature of the session initialization error, perform the following:
If you cannot determine the problem your session is having, contact BMC Support with the TSO/E messages and any related messages. | ||||||
BBVJ010 | IDENTIFY failed for module, RC=X'returnCode' Explanation: During initialization, BBVJSETP Identifies certain entry points so they can be located by IBM routines. The IDENTIFY for module failed with the indicated return code. TAS initialization fails and the session is not started. User response: See information about the IDENTIFY macro in the IBM manual MVS Assembler Programming Reference for the return code value. If you cannot correct the problem, contact BMC Support with the return code value in this message. | ||||||
BBVJ011 | CSVQUERY failed for module, RC=X'returnCode' Explanation: During initialization, BBVJSETP modifies certain load modules. To determine what method to use, it issues a CSVQUERY. The request failed as indicated. TAS initialization fails and the session is not started. User response: See information about the CSVQUERY macro in the IBM manual MVS Assembler Programming Reference for the return code value. If you cannot correct the problem, contact BMC Support with the return code value in this message. | ||||||
BBVJ012 | MODNAMET not found in IRXTSPRM Explanation: During initialization, BBVJSETP modifies certain load modules. In examining IRXTSPRM, the pointer to MODNAMET was found to be zero. Alternate Access is unable to modify IRXTSPRM to provide an attention exit that is appropriate. This might result in problems if ATTN (or PA1) is used to stop a REXX EXEC. User response: The distributed version of IRXTSPRM has a MODNAMET. Determine why this information has been removed. | ||||||
BBVJ022I | IKJSCAN RC=X'returnCode' Explanation: The IBM IKJSCAN routine checks the command buffer built by BBV during initialization. The command buffer is not correct, so IKJSCAN issues a hexadecimal return code of X'nn'. TAS initialization fails and the session is not started. User response: See information about the IKJSCAN routine in the IBM manual MVS Assembler Programming Reference for the return code value. If you cannot correct the problem, contact BMC Support with the return code value in this message. | ||||||
BBVJ031E | EXEC RC=X'returnCode' Explanation: The IBM EXEC routine takes a command from the command buffer built by BBV during initialization and places the command on the command stack. An error resulted during this function, so EXEC issues the indicated hexadecimal return code. TAS initialization fails and the session is not started. User response: See information about the EXEC routine in the IBM manual TSO/E Programming Services for the return code value. If you cannot correct the problem, contact BMC Support with the return code value in this message. | ||||||
BBVJ032E | GETLINE RC=X'returnCode' Explanation: The IBM GETLINE routine encountered an error while attempting to read an element in the command stack. Typically, an element cannot be read due to an installation or environmental compatibility issue. The GETLINE routine issues the indicated hexadecimal return code. TAS initialization fails and the session is not started. User response: Verify the BBV installation and correct the problem, if possible. Restart the LAS. See information about the GETLINE routine in the IBM manual TSO/E Programming Services for the return code value and correct the problem, if possible. If the problem persists, contact BMC Support with the return code value in this message. | ||||||
BBVJ034E | Syntax error in the following statement: Explanation: This message is always issued with message BBVJ035E. A syntax error was found in a command line statement in the BBVINIT REXX EXEC. Message BBVJ035E is issued. User response: See message BBVJ035E for additional information. | ||||||
BBVJ035E | variable text Explanation: This message is always issued with message BBVJ034E. The variable text value is the command line in BBVINIT containing invalid syntax. TAS initialization fails and the session is not started. User response: Correct the syntax error and restart the TAS. If the problem persists, contact BMC Support. | ||||||
BBVJ036E | Non-zero return code from BBVJCMDP, RC=X'returnCode' Explanation: The BBV command processor BBVJCMDP encountered an error and issued the indicated hexadecimal return code. The BBVJCMDP command processor is used for non-TSO commands that interface with TSO. Valid return code values are:
TAS initialization fails and the session is not started. User response: Contact BMC Support with the return code in this message. | ||||||
BBVJ050E | Environment create failed, RC=X'returnCode' Explanation: The IBM STACK macro encountered an error while attempting to create an environment for a command. The STACK macro issues the indicated hexadecimal return code. This message may issue with message BBVJ051E. TAS initialization fails and the session is not started. User response: See information about the STACK macro in the IBM manual TS0/E Programming Services for the return code value. If you cannot correct the problem, contact BMC Support with the return code in this message. | ||||||
BBVJ051E | Environment create did not return a new ECT Explanation: The IBM STACK macro encountered an error because an ECT (environment control table) could not be initialized. This error is more likely to occur in older versions of TSO. TAS initialization fails and the session is not started. User response: Contact BMC Support with the text of this message and the return code in message BBVJ050E. | ||||||
BBVJ052E | Barrier element create failed, RC=X'returnCode' Explanation: The IBM STACK macro created an environment for a command, but an error occurred during the process of establishing a boundary for command execution. TAS initialization fails and the session is not started. User response: See information about the STACK macro in the IBM manual TSO/E Programming Services for the return code value. If you cannot correct the problem, contact BMC Support with the return code in this message. | ||||||
BBVJ053E | REXX environment initialization failed, Reason=X'reasonCode' Explanation: The BBVINIT REXX EXEC failed for the TAS. The reason for the failure is indicated by the indicated hexadecimal reason code. TAS initialization fails and the session is not started. User response: See information in the IBM manual TSO Procedures Language MVS/REXX Reference for the reason code value. If you cannot correct the problem, contact BMC Support with the reason code in this message. | ||||||
BBVJ054E | TSO Services Facility failed, RC=X'returnCode' Reason=X'reasonCode' Explanation: BBV was calling a function through the TSO Services Facility, but the request failed. The TSO Services Facility issued the indicated hexadecimal return code and hexadecimal reason code. TAS initialization fails and the session is not started. User response: See information in the IBM manual TSO Programming Services for the return code and reason code values. If you cannot correct the problem, contact BMC Support with the reason code in this message. | ||||||
BBVJ055E | Barrier element delete failed, RC=X'returnCode' Explanation: During termination of a TAS, the boundaries for a command processing environment could not be deleted properly. The indicated return code value was issued by the IBM STACK macro, which created the environment during TAS initialization. TAS termination continues. User response: See information about the STACK macro in the IBM manual TSO/E Programming Services for the return code value. If you cannot correct the problem, contact BMC Support with the return code in this message. | ||||||
BBVJ056E | Requested function function was not found Explanation: BBV was calling the function function through the TSO Services Facility, but the request failed because the function could not be located. This error is most likely to occur when default values were changed during BBV customization. This message always issues with message BBVJ054E. TAS initialization fails and the session is not started. User response: See information in the IBM manual TSO Programming Services for the return code and reason code values shown in message BBVJ054E. If you cannot correct the problem, contact BMC Support with the reason code in this message. | ||||||
BBVJ072W | Timeout from command scheduling Explanation: During a session, a command was scheduled and attached, but the command did not complete execution for some reason so the timeout value for the command expired. The command is not fully executed. User response: Check for other messages that indicate a possible reason why the command did not execute. Obtain a copy of the job log and any system dumps that may have resulted from an error, and contact BMC Support. | ||||||
BBVJ090E | Value of variable exceeds maximum length of 255 Explanation: During command processing, a variable of variable was being passed, but the variable value exceeded 255 bytes. Only variable values of up to 255 bytes can be passed properly. The value variable is truncated at 255 bytes and passed; command processing continues. User response: No action is required, if normal processing continues. If other errors result, obtain any related messages and the job log, and contact BMC Support. |