BMC II for z/OS reason codes

0

The function call (specified by its return code) was successful. Not an error, this code is returned for all successful function calls.

1

Gateway Library was not initialized.

2

Initialization of configuration failed.

3

Tracing configuration failed.

4

Initialization of outbound communication failed.

5

Initialization of inbound communication failed.

6

Initialization of message handling failed.

7

Initialization of persistent storage failed.

8

Initialization of connection port range failed.

9

Initialization of encryption failed.

10

Transport provider is unavailable.

11

Service endpoint could not be opened.

12

Service endpoint could not be bound.

13

Memory allocation failure occurred.

14

Invalid IP address syntax was specified.

15

Service location cannot be determine.

16

Host name lookup failed.

17

Server is already running.

18

Server is already down.

19

Invalid connection handle.

20

Invalid message type.

21

Connect failed.

22

Timed out.

23

Connection to destination failed.

24

No buffers available for destination.

25

Contact with destination failed.

26

Send failure occurred.

27

Invalid message ID.

28

Storage file read failed.

-102

The message is corrupted or includes a null parameter.

-104

No memory is available to the Basic C APIs.

-105

The integration called a function that included a malformed or null slot name.

-106

The message contains a slot with a null value or an empty string.

-107

An internal structure is corrupt.

-108

An internal structure is corrupt.

-110

The requested item (such as a slot) does not exist.

-111

The header of a BAROC string that was passed to the Basic C APIs by using the bmcii_messageSetBaroc function is malformed or missing. The string cannot be converted into a message.

-112

The class name is missing from an event or data message. The message information may be intended for a new message or as an attempt to overwrite an existing message.

-113

No more results are available in response to a request for the items in a list of values.

-114

Internal error.

-115

The integration called a function that included an invalid parameter.

-116

Fatal error occurred due to a failure to allocate memory.

-118

A BAROC string that the integration is formatting as a message is missing an END statement

-119

The name and location of the mcell.dir file are not specified in the integration_name.conf configuration file.

-120

The specified map set file (or selector set file) does not exist, or the integration does not have permission to access the specified file.

-121

The parameter specified in a configuration function call (bmcii_get_bool, bmcii_get_dir, bmcii_get_file, bmcii_get_num, or bmcii_get_,string) is missing from the integration_name.conf file, or the parameter name was specified incorrectly in the function call.

-122

The Basic C APIs are unable to create an event message.

-123

The host or port specified in one of the following functions is invalid or malformed: bmcii_connect, bmcii_setupServer, or bmcii_initQueryConnect.

-124

The cell name specified in the bmcii_connect, bmcii_serverSetup, or bmcii_queryInitConnect function is invalid.

-125

The connection to the BMC Impact Manager product instance was broken while the integration was sending a message.

-130

Internal error occurred. The Basic C APIs are unable to create a required object.

-131

Internal error occurred.

-132

The message type specified in the message is not included in the message type enumeration.

-133

(Microsoft Windows only) Sockets are not initialized because the Basic C APIs determine the socket library version. The version of Windows on the integration host is not supported.

-136

The bmcii_loadSelectorSet function specifies a null pointer or empty string for the selector set file name. This error message can also apply to map set files specified with the bmcii_loadMapSet function.

-137

The header of one or more selectors in the specified selector file is missing or malformed.

-138

The name of a selector in the specified selector file is missing or malformed.

-139

There are no more items in the list.

-140

The specified selector file contains an error.

-141

The loaded map set or selector set file specifies a Basic C APIs function not supplied by the Basic C APIs library in use.

-144

There is an error in the specified map file.

-145

There is a syntax error in a line in the specified map file.

-146

There is a syntax error in a line in the specified selector file.

-147

The header of one or more maps in the specified map file is missing or malformed.

-148

The name of a map in the specified map file is missing or malformed.

-149

The message that was passed to the Basic C APIs is invalid or corrupt.

-150

The map set (or selector set) specifies a function that includes one or more invalid parameters.

-160

Internal error occurred.

-161

The bmcii_init function has been called after the Basic C APIs have already been initialized.

-164

The bmcii_startRecvThread function failed to create a new Receive thread.

-165

The bmcii_startRecv function has been called after the Receive thread is already running.

-166

The timeout period specified in the function expired before any results were returned.

-169

An internal event is invalid.

-170

A mutex internal to the Basic C APIs is invalid.

-171

The integration did not perform any translation operation because the specified map set was disabled. This error message does not necessarily describe an error, since disabling an entire map set is supported.

-172

The $domap function is creating a loop in the map set.

-173

The $doselector function is creating a loop in the selector set.

-174

The version of the structure passed by the bmcii_getFirstDirectoryInfo or bmcii_getNextDirectoryInfo function is not supported by the Basic C APIs library in use.

-175

A slot name in the message is set with an empty string.

-177

The Basic C APIs are not initialized. All Function calls (except for bmcii_getVersion) can be performed only after bmcii_init is called.

-178

The bmcii_start RecvThread function cannot create a thread because the UseLocks parameter is missing from the configuration file or is included but set to NO or OFF.

-179

The message type that is being passed to the message is unknown. This situation can happen when setting the message type with the bmcii_setMessageType function or setting META_MSG_TYPE by using the bmcii_setMetaSlot function.

-180

The map specified in the bmcii_translate function call is disabled.

-181

Functions that must be called in a specific order were called out of order.

-182

The BAROC string that was passed to the Basic C APIs using the bmcii_messageSetBaroc function is malformed and cannot be processed.

-184

Timed out waiting for query registration

-185

Following an attempt to establish a query connection with a BMC Impact Manager product instance by using the bmcii_initQueryConnect function, the BMC Impact Manager product instance returned an error and the connection failed.

-188

A query result has not yet been returned.

-189

The Basic C APIs are unable to parse the response from the BMC Impact Manager product instance.

-190

The requested placeholder is not in the list.

-191

The BMC Impact Manager product instance returned an error.

-192

The query connection was broken during the processing of a query.

-193

The query is not supported by the loaded version of the Basic C APIs.

-194

Internal error occurred. The result buffer is corrupt.

-195

An internal list is corrupt.

-196

An internal list is corrupt.

-197

The integration called a function after the Basic C APIs were terminated.

-198

The event modification that was sent did not include an mc_ueid ID or event handle to identify the event that was to be modified. The data modification that was sent did not include an mc_udid ID or data handle to identify the data object that was to be modified.

-199

The length of an encrypted string is invalid.

-200

An illegal character was found in a hexadecimal-encoded string

-201

The list being searched is empty.

-202

The configuration file parameter of the bmcii_init function is invalid.

-203

The home directory parameter of the bmcii_init function is invalid.

-204

A required slot is missing.

-205

The address passed is not a valid IP address.

-206

The operation is not allowed in a map.

-207

The string is invalid or malformed.

-208

The memory passed is corrupt or incorrect.

-209

Query registration failed.

-210

The SelectorSet or all selectors are disabled.

-211

This operation is not supported by the connected Impact Manager.

-212

An error was received from the Impact Manager. See trace file for more information.

-213

The limit of 100 open connections has been reached.

-214

The function bmcii_getSlotValue was used on a non SLOT_TYPE_LIST slot.

-215

The function bmcii_getSlotValue was used on a non SLOT_TYPE_NORMAL slot.

-216

Modify LIST_OF slots (bmcii_modifySlotValueList) is not permitted with new events. It is only supported for MOD events.

-217

Modify LIST_OF slots (bmcii_modifySlotValueList) is not supported on Impact Managers before 7.0.

-218

The message loaded has been deleted.

-219

A buffer has reached it size limit.

-220

The end of the file has been reached; this error message applies for SM object query.

-240

The component object did not contain an mc_udid slot.

-241

Invalid query type in query result.

-242

The request query failed.

-243

Component query result is invalid.because it is not a valid count number.

-244

Invalid query parameter.

-245

Size of slot name and value do not match.

-249

The SIM is not in mcell.dir and is needed for a model query error message for ClassDef query.

-280

Invalid class definition data string.

-281

Invalid slot definition occurred.

-301

No match was found in the filter In selector set. The message was discarded. (not an error)

-302

A match was found in the filter Out selector set. The message was discarded. (not an error)