BBMXxnnn messages

This section contains window messages that are prefixed with BBMX. These messages report any errors that occur during initialization, with the security interface, or when collecting, displaying, or storing object data or screen definitions.

During normal processing, the BBMX messages appear inside windows where errors occur; however, for initialization errors or when other specific error conditions exist, these messages are written to the operator's console or to a system log.

Note:
Each message has an alphabetic character at the end, which depends upon the return code received at the time the message was issued. See Action and severity codes for more information about these values.
BBMXB003
The SIZE : size should be greater than zero and less than 16K
Explanation:

This is a diagnostic message containing error information used by IBM® support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB004
Failed to get storage for size bytes data
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB005
Failed to enlarge existing storage block
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB103
The function received size but should be greater than zero
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB104
The number of keys, number, was too small
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB105
The number of elements, number, was too small
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB106
The received ELEMENT NUMBER, number, was too big
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB107
Failed to get size bytes storage
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB108
Failed to resize storage for size bytes
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB127E
Authorization failed for starting CAS with ESMTYPE(NONE)
Explanation:

This message is issued to the operator's console. There is no authorization to initialize the coordinating address space (CAS) with the security type of ESMTYPE(NONE).

System action:

CAS initialization terminates.

User response:

Notify your security administrator.

BBMXB128E
Initialization continuing in non-privileged IVP mode
Explanation:

This message is issued to the operator's console. The coordinating address space (CAS) is initializing with no security defined and in non-privileged installation verification process (IVP) mode. When initialization is complete, there is no security checking for authorized functions.

System action:

CAS initialization continues.

User response:

If a security interface is required, you need to edit member BBMTSS00 in the BBSECURE library to specify an external security manager (ESM). In BBMTSS00, change the ESMTYPE global security parameter to a value other than NONE. The following values may be specified:

Start of change
RACF®
Resource Access Control Facility
End of change
BBMXB203
The function received size but should be greater than zero
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB204
The function received string but should be less than 16 characters
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB205
The specified block does not exist
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB206
Cannot get size bytes of storage
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB207
Cannot free the specified storage
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB208
Cannot reset the storage group object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB303
The BLOCKSIZE parameter must be greater than zero, received number
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB304
The NAME parameter cannot exceed 16 characters, name is too long
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB305
INITBLOCKS must be greater than zero, received number
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB306
The specified block does not exist, cc: code zerr: n
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB307
Cannot Create pool name, cc: code zerr: n
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB308
Cannot Get block name, cc: code zerr: n
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB403
The received source map number, number, should between 0 and 12
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB404
The pointer to an array of pointers to DataMap Instances was NULL
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB405
The action action invalid. Map status is status.
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB406
Failed to get storage for DataMap public data area
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB407
There is no matching entry in look up maps for name
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB408
The data type of name is invalid
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB409
There is no data specification for name method
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB410
There is no source map for DataMapMap method to use
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB411
The module load module does not exist
Explanation:

During initialization of a view that was requested for display, the load module module, which contains mapping information for the view's data, could not be located.

System action:

The requested view is not displayed, but the previous view is redisplayed. If no previous view existed, the window remains empty until another view is requested.

User response:

Verify that the product is installed correctly and check any SMP listings to ensure that recent service was properly applied. (All linkedits to target data sets should be RC=0. If SMP target data sets are copied to execution libraries, the copy step should be repeated, taking care to copy everything.)

Look for additional related messages that can indicate a cause for the load module not being found, such as I/O errors. See the information about any additional messages for more actions.

BBMXB413
The input for name method was invalid
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB414
Failure to allocate a StrArray object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB415
The data specification data was invalid
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB416
Failure to set a character string to a StrArray object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB417
The data spec. data was invalid for CountIf
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB418
There is no Total Map in source map list for PARTOF element
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB419
There are no Maps in source map list for look up
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB420
The name calculation of type type data is invalid
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB421
The DataMapMake method failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB422
The name element does not exist in any of the source maps
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB423
The DataMapCompile method failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB503
The received data was not a valid specification
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB504
There was no data record to add
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB505
Failed to get DataManagerStep data
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB506
Failed to allocate a DataMap instance
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB507
Failed to allocate an HArray instance
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB508
Failed to allocate a DataStore instance
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB509
Failed to get storage from DataStore Object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB510
The received name does not exist in source maps
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB511
Lack of format pattern for element in old join specification
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB603
The expected number of specifications should be greater than number
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB604
There was no DataBus Instance for building a Join Object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB605
The provided record failed to pass the evaluation by FilterEvaluate
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB606
Failed to allocate DataRecord Object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB607
Failed to allocate HArray Object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB608
Failed to allocate DummyTree Object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB609
Failed to allocate TotalMap
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB610
Failed to get storage for exception messages
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB611
Failed to allocate CompCodeMap
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB612
Failed to allocate Filter Object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB614
Error detected in selector during process
Explanation:

The data in a view was being refreshed, but an error occurred in the selector process of process while attempting to obtain data to display.

System action:

The view is not displayed and this message appears.

User response:

Read the related messages for more information about this failure. If an abend occurred, contact your IBM Support Center with the LOGREC, system dump, and related console messages.

BBMXB615
Access denied to Table Actions; Key=key
Explanation:

A command for a secured action was issued against the data in a view, but the user ID does not have the authority to issue any secured actions against this table. The key value indicates diagnostic security information of up to 24 characters.

System action:

The command is not performed and this message is displayed. When ENTER is pressed, the view reappears but the action has not occurred.

User response:

Perform the following:

  1. Obtain a screen print of this message and related messages that show the resource class and entity name information.
  2. Contact your security administrator to obtain authorization for the required resource for your user ID.

If you feel this message is in error, contact your IBM Support Center with the key value and related message information.

BBMXB703
No record was provided
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB704
There was no Join Instance for building a DummyTree Object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB705
JoinAdd Failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB803
No GroupBy specification was provided
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB804
There was no Summary Map provided
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB805
There was no Join Instance for building a Summary Object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB806
The provided specification data was bad
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB807
Failed to allocate Summary Key Map
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB808
Failed to allocate Summary HArray
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB809
Failed to allocate DataStore object for summary record
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB810
Failed to allocate DataStore object for summary reference
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB811
Failed to get storage for next Summary Reference
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB812
Failed to get storage for summary keys
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB813
DataMapMap Failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXB904E
Error reading loadlist loadlist from DD ddname
Explanation:

During CAS initialization, a CAS definition parmlib member for the local CAS could not be found.

System action:

CAS initialization continues normally using default system values.

User response:

Ensure member loadlist exists in DD ddname. See CICSPlex® System Manager Setup for more guidance.

BBMXBA03
The Load Module module was not found
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBA04
Invalid Option - option for ReplyGet
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBA05
Adding the current Arg would not leave room for a reply
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBA06
No room for a reply buffer in the Omsg
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBB03
Cannot allocate Language Object for filter specification
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBB04
The number of data records number is invalid
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBB05
The number of data records number exceeds maximum maximum
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBB06
Cannot allocate Evaluator Object for filter specification
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBB08
FilterSet did not work correctly, evaluation failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBB09
FilterSet completed with warning
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBB10
Invalid element data type for pattern matching operation
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBB11
Filter evaluation completed with exceptions
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBB13
Summary Element name: string is invalid
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBC03
The Order Specification data was bad
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBC04
Either a Join Object or a Summary Object should exist, not both
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBC05
Failed to allocate a new DataMap Object for DataOrder
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBC06
Failed to allocate a new BArray Object for DataOrder
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBC07
Failed to add a new element to DataMap
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBC08
Failed to get a block of storage for KeyRecord
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBC09
Element element does not exist
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBD03
There was no data specification provided
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBD04
There was no Join Instance for building a DataForm Object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBD05
name method may be called only once and immediately after Allocate
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBD06
The starting number number1 is too big. There are only number2 records.
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBD07
Failed to allocate a new DataMap object for DataForm object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBD08
Failed to allocate a new Summary object for DataForm object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBD09
Failed to allocate a new DataOrder object for DataForm object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBD10
Failed to allocate a new Filter object for DataForm object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBD11
Failed to get storage for Requested Data
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBD12
The DataOrderSet for name form was failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBD13
Failed to refresh the Summary object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBD14
Failed to refresh the DataOrder object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBD15
There is no data that satisfies your request
Explanation:

A view or form was requested, but there are no data records for display. This situation can occur in one of two ways:

System action:

This message is displayed in the window instead of data. When you press Enter, the data is requested again and either this message is redisplayed or data appears in the window because an exception condition was met.

User response:

This may not be an error condition. You may have qualified the view command in such a way that no data was found.

For an administration view, this message may mean that there are no definitions of the requested type for the current context. You can issue the CREATE action command to create a definition while this message is displayed.

For a monitor view, make sure that CICSPlex SM resource monitoring is turned on for the specified resource in the current context. If monitoring is not turned on, no monitor data is available.

If this message appears when you believe there should be data to display, contact your IBM Support Center with an example of the command used to request the form or view.

BBMXBD16
Failed to add a new element to form name
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBD17
Failed to make the map for form name
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBD18
Failed to update total element in Join
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBD19
There were invalid elements found in form name
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBD20
There is no DataOrder allocated for form name
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBD21
Failed to extract order BArray key structure for form name
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBD22
Failed to allocate an Array object for summary data
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBD23
number records presented by the product
Explanation:

The number value reflects the total number of records that CICSPlex SM provided to the ISPF end-user interface.

System action:

None.

User response:

None.

BBMXBD24
number records filtered by the query
Explanation:

The number value in message BBMXBD24 reflects the number of records removed from the total number of records presented by CICSPlex SM, based on user-defined query filters.

Message BBMXBD24 is always issued with message BBMXBD23 and may be issued with message BBMXBD25.

If only message BBMXBD23 is issued with message BBMXBD24, the criteria established by the user-defined query filters removed all records presented by CICSPlex SM, so no data is left to display in the view.

If both messages BBMXBD23 and BBMXBD25 are issued with message BBMXBD24, the criteria established by the user-defined query filters removed some of the records presented by CICSPlex SM and the user-defined filter conditions removed the remaining records, so no data is left to display in the view.

User-defined query filters are specified by using the PARm command or by defining keyword parameters when issuing the view command.

System action:

None.

User response:

Use the PARm command to re-establish the filter criteria for the query.

BBMXBD25
number records filtered by the form
Explanation:

The number value in message BBMXBD25 reflects the number of records removed from the total number of records presented by the query, based on the user-defined form filter conditions.

Message BBMXBD25 is always issued with message BBMXBD23 and may be issued with message BBMXBD24.

If only message BBMXBD23 is issued with message BBMXBD25, the criteria established by the user-defined form filter conditions removed all records presented by CICSPlex SM, so no data is left to display in the view.

If both messages BBMXBD23 and BBMXBD24 are issued with message BBMXBD25, the criteria established by the user-defined query filters removed some of the records presented by CICSPlex SM and the user-defined form filter conditions removed the remaining records, so no data is left to display in the view.

User-defined form filter conditions are specified by using the QPARm command.

System action:

None.

User response:

Use the QPARm command to re-establish the filter criteria for the filter conditions.

BBMXBE03
The expected DataBus Instance was absent
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBE04
There are already 20 forms
Explanation:

The limit of forms against a single query is 20. A form against the same query within a window was requested, but the query already has 20 forms. Forms are requested either by invoking a hyperlink or issuing the FORM command in the COMMAND field.

System action:

The form request is ignored and the previous form is redisplayed.

User response:

Do one of the following:

BBMXBE05
The form name does not exist
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBE06
Failed to allocate a Join Object for Query
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBE07
Failed to create name form
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBF01
The number of data records number is invalid
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBF02
The number of data records number exceeds maximum maximum
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBF03
Cannot allocate Language Object for security administration
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBF04
Syntax error in member BBMTSS00
Explanation:

During coordinating address space (CAS) initialization, the member BBMTSS00 is read from the BBSECURE DD data set to initialize the security interface. At least one syntax error was found in this member. Additional related messages are issued to indicate the exact nature of the syntax error.

System action:

The CAS does not initialize.

User response:

See related messages and perform the actions provided for those messages to correct the syntax error, then restart the CAS.

BBMXBF05
Restart interval is value1 minute(s); allowed maximum is value2 minutes
Explanation:

During coordinating address space (CAS) initialization, the member BBMTSS00 is read from the BBSECURE DD data set to initialize the security interface. The restart interval parameter value of value1 minutes defined in BBMTSS00 is too large. The maximum allowable minutes for the restart interval value is value2.

System action:

The CAS does not initialize.

User response:

Correct the RSINTERVAL parameter value on the ESM statement in member BBMTSS00 to specify a number of minutes that does not exceed value2 and restart the CAS.

BBMXBF06
Wrong integer of value entered; default of default is used
Explanation:

During coordinating address space (CAS) initialization, the member BBMTSS00 is read from the BBSECURE DD data set to initialize the security interface. An invalid value of value was entered in this member for the RSINTERVAL parameter, which specifies the restart interval value. A default value of default is used; the default value is 1440.

System action:

The CAS initializes using the default value.

User response:

Correct the invalid value on the RSINTERVAL parameter of the ESM statement in member BBMTSS00 and restart the CAS.

BBMXBF07
Error in processing security administration file
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBF08
Error allocating file: ddname
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBF09
Output not allowed to BBACTDEF
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBF10
Error reading SecAdminLang member DD: ddname Member: member
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

Start of change
BBMXBF11
Invalid External Security Manager name: value
Explanation:

During coordinating address space (CAS) initialization, the member BBMTSS00 is read from the BBSECURE DD data set to initialize the security interface. An invalid value was entered in this member for the ESMTYPE parameter, which specifies whether RACF is to be used as the external security manager or if CAS security is to be bypassed.

System action:

The CAS does not initialize.

User response:

Correct the ESMTYPE parameter value in member BBMTSS00. Specify ESMTYPE(RACF) to use a system authorization facility (SAF) compliant security manager or ESMTYPE(NONE) to bypass CAS security, and restart the CAS.

End of change
BBMXBG03
There was no data specification provided
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBG04
A Filter Instance did not exist before setting filter parms
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBG05
There was no form name provided
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBG06
There was no Action Table name provided
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBG07
There was no Action name provided
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBG08
There was no Token provided
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBG09
There was no Element Name provided
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBG10
The FormOrder should be sent before the first FormRequest
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBG11
The form name does not exist
Explanation:

A request has been made for a form called name, but the form does not exist. Up to 20 forms can be defined to each view and they are named internally as FORM00 through FORM19. The name value appears as one of these internal form names. If the name value is FORM00, then a new view was requested.

This message also can occur when commands are stacked in the COMMAND field. When commands are stacked, they are separated from each other by semicolons. As many commands can be stacked as can fit in the COMMAND field. Therefore, if an error occurs in a command specified early in the stack, other errors may result from command processing of commands that are specified later in the stack. In the case of this message, an earlier error would have caused a failure in creating the form, so the form would be unknown.

System action:

This message is displayed and the request for the new view or form is ignored. Other related messages also can appear that describe why the form was not created. If this message appears during the initialization of a new view, the previous view is redisplayed when you press Enter.

User response:

See related messages for more information.

If this message appears without related messages or if the problem cannot be corrected from related message information, contact your IBM Support Center with an example of the command that was issued when the error occurred and any of the other information that is available from the list shown in Diagnostic information for BB messages.

BBMXBG12
Failed to allocate Query object for QueryForms object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBG13
type error in filter for name
Explanation:

An error with a type of type occurred during the processing of a filter for a query named name. Allowable error types are:

Length
The length of the filter for the query is greater than 512 characters.
Set
An error occurred while attempting to set the filter. Other related error messages are displayed that describe the exact nature of the failure.
System action:

The filter is ignored. This may result in more data than was anticipated.

User response:

If the error type is Length, an internal error has occurred. Obtain a screen print of the messages and contact your IBM Support Center.

If the error type is Set, this message is accompanied by related messages that describe why the filter was not set. See those messages for problem resolution.

BBMXBG14
Refresh error
Explanation:

When a view is displayed and Enter is pressed, a request is made to refresh the data in the window. During the process of gathering this new data, an error occurred which caused no data to be gathered. The most common cause of this type of failure is an abend in the selector program module. The selector program gathers data for a view.

System action:

The data is not refreshed. When Enter is pressed again, another attempt is made to refresh the data.

User response:

Read the related messages for more information about this failure. If an abend occurred, contact your IBM Support Center with the LOGREC, system dump, and related console messages.

BBMXBG15
DataFormOrderSet failed while setting data order for name
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBG16
Query select failed
Explanation:

When a view is requested, a query is initialized that collects and holds the data for the view. An error occurred during the process of initializing the query. The most common cause of this type of failure is an abend in the selector program module. The selector program controls the function of gathering data for a query.

System action:

The view is not initialized and this message is displayed. When Enter is pressed, the previous view is redisplayed in the window.

User response:

Read the related messages for more information about this failure. If an abend occurred, contact your IBM Support Center with the LOGREC, system dump, and related console messages.

BBMXBG17
Failed to reset join object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBG18
Failed to create a new form
Explanation:

When a new view or form name is requested, a form is initialized that selects specific data to be displayed in a window. Requests are made by issuing the VIEW or FORM command in the COMMAND field, or by invoking a hyperlink. An error occurred during the process of setting up the form for the requested view or form name.

System action:

The form is not initialized and this message is displayed. When Enter is pressed, the previous form is redisplayed in the window, or, if this problem occurred during the initialization of a new view, the previous view is redisplayed in the window.

User response:

Read the related messages for more information about this failure. If an abend occurred, contact your IBM Support Center with the LOGREC, system dump, and related console messages.

BBMXBG19
Failed to create a summary form
Explanation:

The FORM command was issued, or a hyperlink was invoked that requested a summary form to be displayed in a window. An error occurred during the process of setting up the summary form.

System action:

The summary form is not initialized and this message is displayed. When Enter is pressed, the previous form is redisplayed in the window.

User response:

Read the related messages for more information about this failure. If an abend occurred, contact your IBM Support Center with the LOGREC, system dump, and related console messages.

BBMXBG20
Failed to set filter for name
Explanation:

When a new view or form name is requested, a form is initialized that selects specific data to be displayed in a window. An error occurred during the process of establishing the filter for the form named name. Up to 20 forms can be defined to each view and they are named internally as FORM00 through FORM19. The name value appears as one of these internal form names.

The most common reason for this failure is that the filter specification contains invalid syntax.

System action:

The form is not initialized and this message is displayed. When Enter is pressed, the previous form is redisplayed in the window, or, if this problem occurred during the initialization of a new view, the previous view is redisplayed in the window.

User response:

Read the related messages for more information about this failure.

BBMXBG21
Failed to set filter parameters for name
Explanation:

When a new view or form name is requested, a form is initialized that selects specific data to be displayed in a window. An error occurred during the process of setting up the parameters for the filter on the form named name. Up to 20 forms can be defined to each view and they are named internally as FORM00 through FORM19. The name value appears as one of these internal form names.

The most common reason for failure is that the filter specification contains invalid syntax.

System action:

The form is not initialized and this message is displayed. When Enter is pressed, the previous form is redisplayed in the window, or, if this problem occurred during the initialization of a new view, the previous view is redisplayed in the window.

User response:

Read the related messages for more information about this failure.

BBMXBG22
Form request failed to get data for name
Explanation:

When Enter is pressed, or a new form is selected by issuing the FORM command or invoking a hyperlink, data is requested from the query. An error occurred in attempting to get data to return to the window for form name. Up to 20 forms can be defined to each view and they are named internally as FORM00 through FORM19. The name value appears as one of these internal form names.

System action:

When Enter is pressed, the query data is updated and the form request is attempted again.

User response:

Read the related messages for more information about this failure. If an abend occurred, contact your IBM Support Center with the LOGREC, system dump, and related console messages.

BBMXBG23
Failed to add a new element to name form
Explanation:

An attempt to add a new element to a form named name has failed. Up to 20 forms can be defined to each view and they are named internally as FORM00 through FORM19. The name value appears as one of these internal form names. The error occurred while using the SUM command to add the element.

System action:

The element is not added to the form and this message is displayed. All other fields in the form are displayed.

User response:

Read the related messages for more information about this failure. If an abend occurred, contact your IBM Support Center with the LOGREC, system dump, and related console messages.

BBMXBG24
Failed to get data map data specifications for form name
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBG25
No HelpFetch Instance existed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBH01
DictionaryAllocate Failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBH02
Storage Group Allocate Failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBI01
DataMap allocation failed at LuManager initialization time
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBI02
SecAdminLang allocation for LuManager failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBI04
Open failed for parmlib ddname
Explanation:

During initialization of the security interface, an attempt to open the parameter library data set defined by ddname failed. The most likely cause of this error is a failure to allocate ddname to the coordinating address space (CAS).

System action:

The security interface is initialized using the default security parameters. The default security parameters are:

ESM ESMTYPE(NONE) RELEASE(1.9) APPL(JOBNAME) SUBSYS(SSID)

User response:

No action is required unless a security interface is required. If a security interface is required, perform the following:

  1. Modify the CAS started task JCL to allocate the parameter library named ddname.
  2. If additional messages indicate an error in the data set, perform the corrective action for these messages.
  3. Restart the CAS.
BBMXBI05
Read failed for member member in parmlib DSNname
Explanation:

During initialization of the security interface, an attempt to read member member from the parameter library data set named DSNname failed. The most likely cause of this error is that member is not in the data set named DSNname.

System action:

If the member value is BBMTSS00, the security interface initializes with the default security parameters. The default security parameters are:

ESM ESMTYPE(NONE) RELEASE(1.9) APPL(JOBNAME) SUBSYS(SSID)

If the member value is BBMTSP, the security interface is not initialized and coordinating address space (CAS) initialization terminates.

If the member value is BBMTSP00, the security interface initializes, but no customer-specified Resource Class Name Transformations can be processed. This may be unacceptable for CA-TOP SECRET and CA-ACF2 installations.

User response:

No action is required if the system response is acceptable.

If the system response is not acceptable, ensure that member member resides in the data set named DSNname and restart the CAS.

BBMXBI06
Processing failed for parmlib ddname member member
Explanation:

During initialization of the security interface, an attempt to interpret member member from the parameter library data set named ddname resulted in at least one error. The most likely cause of this error is that member in data set ddname contains syntax errors. However, the error may be severe enough to cause the security interface to fail to initialize.

System action:

If the member value is BBMTSP00, the system attempts to continue initialization using default values, if necessary. Defaults are substituted for parameters invalidated by syntax errors; additional messages are issued which indicate which parameters are ignored or substituted.

If the member value is other than BBMTSP00, the security interface may fail to initialize and additional messages are issued to indicate the exact nature of the error.

User response:

If the member value is BBMTSP00 and the default substitutions are acceptable, no action is required.

If additional messages indicate syntax errors, correct these errors and restart the CAS.

BBMXBI07
PLEXMGR service point attach failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBI08
DataMapMake failed at LuManager initialization time
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBI09
Unable to allocate Security Object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBI10
Wait Failed cc: code
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBI11
Post Failed cc: code
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBI12
Security Timer Allocation failed, restarts not allowed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBI13
Security subcomponent is terminating
Explanation:

The security interface has encountered an abnormal error and is terminating. Additional related messages indicate the exact nature of the failure.

System action:

The security interface is terminating, therefore the coordinating address space (CAS) is terminating.

User response:

See the related messages to determine the cause of the failure and perform any corrective action for these messages. If the error is an abend, obtain as much of the available information shown in Diagnostic information for BB messages and contact your IBM Support Center.

BBMXBI14
No maximum restarts specified for the security subtask
Explanation:

This is an informational message that is issued during initialization of the security interface to indicate that the BBSECURE DD data set member BBMTSS00 does not have a maximum number of restarts specified. The restarts limit is defined by the RSLIMIT parameter on the ESM statement in member BBMTSS00. The restart limit is a whole number indicating the number of times the security subtask can fail during the specified restart interval before the WTOR message BBMXBI23A is issued to the operator.

The security subtask fails because the security subtask abends, or an unusual condition in the external security manager (ESM) causes the security subtask to abend. Each time there is a failure in the security subtask, the subtask counts the number of failures that occurred during the number of minutes defined to the restart interval. If the number of failures equals or exceeds the restart limit, the WTOR message BBMXBI23A is issued.

System action:

The system proceeds with initialization, but if the security subtask abends during normal operation, the subtask continually attempts recovery and may not request a restart.

User response:

If this is acceptable, no action is required.

If a maximum number of restarts is required, update the RSLIMIT parameter value in the BBMTSS00 member and restart the coordinating address space (CAS).

BBMXBI15
No restart time limit for security subtask
Explanation:

This is an informational message that is issued during initialization of the security interface to indicate that the BBSECURE DD data set member BBMTSS00 did not specify a restart time limit. The restart time limit is defined by the RSINTERVAL parameter on the ESM statement in member BBMTSS00. The restart time is a whole number indicating the number of minutes in the restart interval.

The security subtask fails because the security subtask abends, or an unusual condition in the external security manager (ESM) causes the security subtask to abend. Each time there is a failure in the security subtask, the subtask counts the number of failures that occurred during the number of minutes defined to the restart interval. If the number of failures equals or exceeds the restart limit, the WTOR message BBMXBI23A is issued.

System action:

The system proceeds with initialization, but if the security subtask abends during normal operation, the subtask continually attempts recovery and may not request a restart.

User response:

If this is acceptable, no action is required.

If a restart time limit is required, update the RSINTERVAL parameter value in the BBMTSS00 member and restart the coordinating address space (CAS).

BBMXBI16
No time interface for security subtask
Explanation:

This is an informational message that is issued during initialization of the security interface to indicate that the time object for the security subtask was not available, so no time interface could be established. A time interface is required to provide a reference point for the restart interval. Without a time interface, the restart interval and restart limit parameters cannot be processed.

System action:

The system proceeds with initialization, but if the security subtask abends during normal operation, the subtask continually attempts recovery and may not request a restart.

User response:

If this is acceptable, no action is required.

If a time interface is required, restart the coordinating address space (CAS).

If the problem persists, obtain as much of the information that is available from the list shown in Diagnostic information for BB messages and contact your IBM Support Center.

BBMXBI17
Default security parameters used
Explanation:

This is an informational message that is issued during initialization of the security interface to indicate that the BBSECURE DD data set member BBMTSP00 either could not be read or was not available. Default security parameters are used to initialize the security interface. The default security parameters are:

ESM ESMTYPE(NONE) RELEASE(1.9) APPL(JOBNAME) SUBSYS(SSID)

System action:

The system proceeds normally with initialization.

User response:

If the default security parameters are acceptable, no action is required.

If the default security parameters are not acceptable, ensure that the BBMTSP00 member is available to the coordinating address space (CAS). If additional messages indicate a syntax error with member BBMTSP00, correct these errors and restart the CAS.

BBMXBI18
Resource Name Transformation module (module) load failed cc: code
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBI19
Unable to allocate ResPrt Object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBI20
Processing failed for DD ddname member member
Explanation:

During initialization of the security interface, an attempt to interpret member member from the DD ddname resulted in at least one error. The most likely cause of this error is that member contains syntax errors. Additional related messages indicate the exact nature of the failure.

System action:

The coordinating address space (CAS) continues to initialize, but may be unable to perform resource transformations. Additional messages are displayed if resource transformations cannot be performed. This may not be acceptable for CA-TOP SECRET or CA-ACF2 installations.

User response:

Correct the errors indicated in related messages and restart the CAS.

BBMXBI21
Resource property table runtime structure not built
Explanation:

During initialization of the security interface, errors were encountered in the definitions of the resource property table. The errors were severe enough that the procedure to build the runtime structure for resource translation was abandoned.

System action:

The coordinating address space (CAS) continues to initialize, but the system is unable to perform resource transformations.

User response:

Correct the errors indicated in related messages and restart the CAS.

BBMXBI22
Security server task abended number times in the past minutes minutes
Explanation:

While attempting to recover from a failure, the security subtask detected that it already had abended number number of times during the restart interval of minutes minutes. The number value meets or exceeds the specified restart limit for the security interface.

System action:

Recovery processing terminates and message BBMXBI23A is issued to the operator's console.

User response:

See the user response for message BBMXBI23A.

BBMXBI23A
Reply 'Y' to restart security server or 'N' to terminate
Explanation:

This message is a WTOR message issued to the operator's console that always follows message BBMXBI22. The security subtask has failed enough times during the restart interval to meet or exceed the restart limit specified for the security interface.

System action:

All processing halts until the operator responds to this message.

User response:

Respond N to terminate the security subtask.

Respond Y to reinitialize the security subtask.

BBMXBI24
LuManager allocate failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBI25
Resource Definition Build failed for global resources
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBI26
Default security resource properties used
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBI27
Authorization failed for starting CAS with ESMTYPE(NONE)
Explanation:

The appropriate profile for allowing a coordinating address space (CAS) to initialize with security disabled is not defined in your external security manager's data base.

System action:

CAS initialization terminates.

User response:

If you need to initialize a CAS with security disabled, contact your security administrator. Otherwise, specify RACF for the ESMTYPE parameter of the Global Security Parameter member BBMTSS00 used by the desired CAS.

BBMXBI28
Initialization continuing in non-privileged IVP mode
Explanation:

This is an informational message.

System action:

CAS initialization continues in non-privileged IVP mode.

User response:

None

BBMXBI29
type member member not found in PARMLIB ddname
Explanation:

Either the customized Global Security Parameter member (BBMTSS00) or the customized Global Resource Class Property Table member (BBMTSP00) could not be located in the Security parameter library, ddname BBSECURE.

System action:

CAS initialization terminates.

User response:

Make sure that the correct BBMTSS00 or BBMTSP00 for the specified CAS is defined in the BBSECURE parameter library.

BBMXBI30
type member member in ddname used
Explanation:

Either the customized Global Security Parameter member (BBMTSS00) or the customized Global Resource Class Property Table member (BBMTSP00) could not be located in the Security parameter library, ddname BBSECURE. The member specified in this message was substituted.

System action:

CAS initialization continues with the security parameters defined in member.

User response:

None

BBMXBJ01
Invalid message request parameter header - reason code: code
Explanation:

During the process of writing a message to the operator console, an error was encountered in the message request parameter header. The procedure returned a reason code of code. Allowable code values and the corresponding reasons are:

1
The request header contained a nonzero reserved field.
2
The request header contained an unsupported version identifier.
System action:

The original message is not written to the console; instead, this message is written.

User response:

Contact your IBM Support Center with any of the available information shown in Diagnostic information for BB messages.

BBMXBJ02
Invalid parameter was encountered - reason code: code
Explanation:

During the process of writing a message to the operator console, an invalid parameter was detected in the operator message request. The invalid parameter caused an error with a reason code of code. Allowable code values and the corresponding invalid parameters are:

1
Nonzero reserved field
2
Invalid message ID
3
Invalid product ID
4
Invalid component ID
5
Invalid message text unit (MTU) count; an MTU represents the variable text portion of the message
6
Invalid MTU array address
7
Fetch protected MTU
8
Nonzero reserved field in the MTU
9
Invalid MTU type
10
Invalid MTU length
11
Too many MTUs
12
Fetch protected message request parameter list (MRPL)
13
Fetch protected data
System action:

The original message is not written to the console; instead, this message is written.

User response:

Contact your IBM Support Center with any of the available information shown in Diagnostic information for BB messages.

BBMXBJ03
Message work environment failure - reason code: code
Explanation:

During the process of writing a message to the operator console, the message work environment failed with a reason code of code. Allowable code values and the corresponding reasons are:

1
LDISP failure
2
System work cell size was less than the minimum size allowed
3
Work cell could not be obtained
4
Coordinating address space (CAS) control structure address (CSCA) could not be located
System action:

The original message is not written to the console; instead, this message is written.

User response:

Contact your IBM Support Center with any of the available information shown in Diagnostic information for BB messages.

BBMXBJ04
Message send failed - reason code: code
Explanation:

During the process of writing a message to the operator console, the message send function failed with a reason code of code. The code value is an MVS™ system completion code.

System action:

The original message is not written to the console; instead, this message is written.

User response:

See the IBM/ESA System Codes manual for information about correcting the error associated with the code value. If the error cannot be corrected from this information, contact your IBM Support Center with any of the available information shown in Diagnostic information for BB messages.

BBMXBK01
Unable to allocate size bytes for Security Environment
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBK02
No environment was presented to Inherit
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBK03
Security GSI failed where function is function, cc=code, and ZERR=n
Explanation:

The function function was attempted against a secured resource, but failed with a completion code of code and an internal trace error code of n. This message appears for all failure types other than access failures.

The code value is a two-digit value indicating and internal completion code. The n value describes the internal load failure that occurred. This is an 8-character value comprised of:

System action:

The function function fails.

User response:

Contact your security administrator to obtain proper authority for the function function.

BBMXBK04
A missing or null Security Token was passed to function
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBK05
The intent was invalid on an auth call: intent
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBK06
Access to resource denied
Explanation:

A user attempted to access a secured resource, but access was denied. Additional messages BBMXBK07 through BBMXBK11 are displayed that provide more information about the resource and the access intent.

System action:

Access to the secured resource is denied.

User response:

Contact your security administrator to obtain proper authority to access the resource.

BBMXBK07
Resource Class: class
Explanation:

This message is issued with message to BBMXBK06. Message BBMXBK07 identifies class as the name of the resource class of the secured resource for which access was denied.

System action:

See message BBMXBK06.

User response:

See message BBMXBK06.

BBMXBK08
Entity: entity
Explanation:

This message is issued with message to BBMXBK06. Message BBMXBK08 identifies entity as the entity name of the secured resource for which access was denied.

System action:

See message BBMXBK06.

User response:

See message BBMXBK06.

BBMXBK09
Volume Serial: volser
Explanation:

This message is issued with message to BBMXBK06. Message BBMXBK09 identifies volser as the name of the volume serial for the secured resource for which access was denied.

System action:

See message BBMXBK06.

User response:

See message BBMXBK06.

BBMXBK10
Access Intent: intent
Explanation:

This message is issued with message to BBMXBK06. Message BBMXBK10 identifies intent as the reason for access to the secured resource for which access was denied.

System action:

See message BBMXBK06.

User response:

See message BBMXBK06.

BBMXBK11
Reason: reason
Explanation:

This message is issued with message to BBMXBK06. Message BBMXBK11 identifies reason as the reason for which access was denied to the secured resource.

System action:

See message BBMXBK06.

User response:

See message BBMXBK06.

BBMXBK12
Security Service Failure for function sspb.ssrc = ssrc
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBK13
field : reason
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBK14
Unable to Allocate StringLang Object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBK15
Error creating entity name
Explanation:

An error occurred while processing an instruction set to construct an entity name. The incorrect instruction set resides in a resource definition file that is used to construct the entity name.

System action:

Access to the resource is denied and this message is displayed, along with additional messages that provide more information about the error.

User response:

If the security dialog was used to redefine the resource definition file, correct the problem.

If this is a default resource definition file, contact your IBM Support Center with a screen print of this message and any related messages.

BBMXBK16
type : value
Explanation:

This is a related message that provides additional information about an error, where:

type
Is one of the following values:
  • Function
  • Action Name
  • Internal Action
  • Action Table
  • Internal Table
  • External Table
  • Entity Name
value
Is the value of type in the context of the error.
System action:

Depends on the type of error that is further defined by other messages that are issued with this message.

User response:

See other messages and perform those actions. If the problem persists, contact your IBM Support Center with a screen print of this message and any related messages.

BBMXBK17
Parameter name requested; no parameters available
Explanation:

An internal error occurred in a default resource definition file. A parameter named name was defined to be available for use in the construction of an entity name, but no parameter was provided.

System action:

Access to the resource is denied. Other messages are issued with this message.

User response:

Contact your IBM Support Center with a screen print of this message and any related messages.

BBMXBK18
Data element name was not found
Explanation:

A resource definition file requested a data element named name to be used in the construction of an entity name. The data element name is not defined, so an error results.

System action:

Access to the resource is denied. Other messages are issued with this message.

User response:

If the security dialog was used to modify the resource definition file that is identified in related messages, correct the error to include the data element name.

If the security dialog was not used, then there is an error with the default resource definition file. Contact your IBM Support Center with a screen print of this message and any related messages.

BBMXBK19
Data element name is not a character string
Explanation:

A resource definition file requested a data element named name to be used in the construction of an entity name. The data element name is defined, but is not a character value. Only character values can be assigned as valid data elements, otherwise an error results.

System action:

Access to the resource is denied. Other messages are issued with this message.

User response:

If the security dialog was used to modify the resource definition file that is identified in related messages, correct the error to define a character value to the data element name.

If the security dialog was not used, then there is an error with the default resource definition file. Contact your IBM Support Center with a screen print of this message and any related messages.

BBMXBK20
Data element name is not allowed in an entity name
Explanation:

A resource definition file requested a data element named name to be used in the construction of an entity name. The data element name is defined, but it is a calculated field. A calculated field cannot be assigned as a valid data element, otherwise, an error results.

System action:

Access to the resource is denied. Other messages are issued with this message.

User response:

If the security dialog was used to modify the resource definition file that is identified in related messages, correct the error to define a data element that is not a calculated field.

If the security dialog was not used, then there is an error with the default resource definition file. Contact your IBM Support Center with a screen print of this message and any related messages.

BBMXBK21
Data element name would cause literal pool overflow
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBK22
Action parameter name not available
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBK23
Data element name requested; no data available
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBK24
Internal Error - Code code not recognized for name
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBK25
External security manager messages are present
Explanation:

When the external security manager issues messages, they must be passed to the user. This message indicates that messages from the external security manager follow.

System action:

If an external security manager message does not have a recognizable number, message BBMXBK26 is used to present the message text.

User response:

Take appropriate action for the external security manager messages that follow.

BBMXBK26
message text
Explanation:

This message contains the message number and text, shown as message text, of a message issued by the external security manager. This message appears when the external security manager message does not have a recognizable message number.

System action:

Additional messages may be issued.

User response:

Take appropriate action for the external security manager message shown as message text.

BBMXBK27
Invalid identify option character ID
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBK28
No access to any secured actions for this table, key=key
Explanation:

A command for a secured action was issued against the data in a view, but the user ID does not have the authority to issue any secured actions against this table. The key value indicates diagnostic security information of up to 24 characters.

System action:

The command is not performed and this message is displayed. When ENTER is pressed, the view reappears but the action has not occurred.

User response:

Perform the following:

  1. Obtain a screen print of this message and related messages that show the resource class and entity name information.
  2. Contact your security administrator to obtain authorization for the required resource for your user ID.

If you feel this message is in error, contact your IBM Support Center with the key value and related message information.

BBMXBK29
No access to any secured actions, key=key
Explanation:

A command for a secured action was issued, but the user ID does not have the authority to issue any secured actions. The key value indicates diagnostic security information of up to 24 characters.

System action:

The command is not performed and this message is displayed. When ENTER is pressed, the view reappears but the action has not occurred.

User response:

Perform the following:

  1. Obtain a screen print of this message and related messages.
  2. Contact your security administrator to obtain authorization for the required resource for your user ID.

If you feel this message is in error, contact your IBM Support Center with the key value and related message information.

BBMXBK31
Security Extended Trace, key=key
Explanation:

Security Extended Trace messages are enabled. A Resource Manager constructed a key value of key to represent a requested operation against a resource. This key value is used to create a request for the external security manager (ESM) to find out if the user is authorized to perform the operation.

System action:

This message is issued and a request containing the key value is issued to the ESM.

User response:

None

BBMXBP01
ResPrt Language module allocate failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBP02
ResPrt PCell allocation failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBP03
Open failed for resource property file ddname
Explanation:

During the initialization of the security interface, a failure occurred when attempting to open the resource property file named ddname. The most likely cause for this error is that ddname is not allocated to the coordinating address space (CAS).

System action:

The CAS continues to initialize, but the security interface cannot perform resource transformations. This may not be acceptable for CA-TOP SECRET or CA-ACF2 systems.

User response:

Perform the following:

  1. Modify the CAS started task JCL to allocate the DD named ddname.
  2. If additional messages indicate an error in the data set, perform the corrective action for these messages.
  3. Restart the CAS.
BBMXBP04
Read failed for resource property DD ddname member member
Explanation:

During the initialization of the security interface, a failure occurred when attempting to read the resource property table in member member from the DD ddname. The most likely cause for this error is either that member is not in the data set defined by the DD ddname or member member is corrupted.

System action:

The coordinating address space (CAS) continues to initialize, but the security interface cannot perform resource transformations. This may not be acceptable for CA-TOP SECRET or CA-ACF2 systems.

User response:

Ensure that member member exists in the data set defined by ddname and restart the CAS.

If the problem persists, obtain as much of the information that is available from the list shown in Diagnostic information for BB messages and contact your IBM Support Center.

BBMXBP05
Parsing failed due to error for resource property file member
Explanation:

During the initialization of the security interface, a failure occurred when parsing the table in the resource property file named member. The most likely cause of the failure is syntax errors in the file. Additional messages explain the exact nature of the failure.

System action:

The coordinating address space (CAS) continues to initialize, but the security interface cannot perform resource transformations. This may not be acceptable for CA-TOP SECRET or CA-ACF2 systems.

User response:

See the additional messages and perform the corrective actions provided, then restart the CAS.

BBMXBP06
Parsing finished with warning for resource property file member
Explanation:

During the initialization of the security interface, an error was encountered when parsing the table in the resource property file named member. The error was not severe enough to cause the parsing function to fail. The failure is not so severe that it prevents resource transformations, but some defaults may be substituted as security parameters. Additional messages explain what specific defaults are taken. The most likely cause of the failure is syntax errors in the file. Additional messages explain the exact nature of the failure.

System action:

The coordinating address space (CAS) continues to initialize and the security interface performs most resource transformations. This may not be acceptable for CA-TOP SECRET or CA-ACF2 systems. Additional messages about this failure are issued.

User response:

See the additional messages and perform the corrective actions provided, then restart the CAS.

BBMXBP07
Unique FILEDATE statement required for resource property definition file
Explanation:

This message is issued with other messages. Message BBMXBP07 indicates that an error was caused by a duplicate FILEDATE statement in a resource property definition file. There can be only one FILEDATE statement in each definition file.

System action:

The coordinating address space (CAS) continues to initialize.

User response:

Remove one of the FILEDATE statements by updating the resource property definition file through the security administrator interface, so that this error does not occur again. Other messages should indicate the name of the definition file containing duplicate FILEDATE statements.

BBMXBP08
date is not in valid UPDDATE format; ddMMMyyyy expected
Explanation:

This message is issued with other messages. Message BBMXBP08 indicates that an error was caused by an invalid date format of date in the UPDDATE statement of the resource property definition file. The correct date format for the UPDDATE statement is ddMMMyyyy, where:

dd
A 2-digit number from 01 to 31 that represents the day of the month.
MMM
A 3-character value that represents the month. Allowable values are:
JAN    APR    JUL    OCT
FEB    MAY    AUG    NOV
MAR    JUN    SEP    DEC
yyyy
A 4-digit number that represents the year.
System action:

The coordinating address space (CAS) continues to initialize.

User response:

Correct the date format in the UPDDATE statement by updating the resource property definition file through the security administrator interface, so that this error does not occur again.

BBMXBP09
time is not in valid UPDTIME format; HH:mm expected
Explanation:

This message is issued with other messages. Message BBMXBP09 indicates that an error was caused by an invalid time format of time in the UPDTIME statement of the resource property definition file. The correct time format for the UPDTIME statement is HH:mm, where:

HH
A 2-digit number from 00 to 23 that represents the hour of the day.
mm
A 2-digit value from 00 to 59 that represents the minute of the hour.

This is a related message that explains a specific error in the resource property table. This error indicates that the UPDTIME statement has an invalid time format.

System action:

The coordinating address space (CAS) continues to initialize.

User response:

Correct the date format in the UPDTIME statement by updating the resource property definition file through the security administrator interface, so that this error does not occur again.

BBMXBP10
Cannot Get Resource Property storage, cc: code zerr: n
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBQ01
Specification for keyword with value of value truncated in service point name
Explanation:

During coordinating address space (CAS) initialization, member BBMTXP00 is read from the BBIPARM DD to define the expected service points and their security definition tables. The security definition table for service point name contains a keyword keyword with a value of value that is too long, so value was truncated. This message shows value as the entire operand defined to keyword keyword. Any value for keyword cannot exceed 8 characters in length.

System action:

The CAS continues to initialize using the truncated value of value for keyword keyword.

User response:

Update the BBIPARM DD member BBMTXP00 to shorten the value value, so that it does not exceed 8 characters in length and restart the CAS.

BBMXBQ02
Error Allocating PCell to Process Service Point Definitions
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBQ03
Error interpreting service point definition parmlib member BBMTXP00
Explanation:

During coordinating address space (CAS) initialization, member BBMTXP00 is read from the BBIPARM DD to define the expected service points and their security definition tables. The BBMTXP00 member contains at least one error, so the CAS cannot initialize. Additional related messages identify the exact nature of the error(s).

System action:

CAS initialization terminates.

User response:

See the additional related messages and perform the corrective actions in member BBMTXP00, then restart the CAS.

BBMXBQ04
keyword value missing in service point definition for name
Explanation:

During coordinating address space (CAS) initialization, member BBMTXP00 is read from the BBIPARM DD to define the expected service points and their security definition tables. A value is not defined for the keyword keyword for the service point name.

System action:

CAS initialization terminates.

User response:

Define a value for keyword in the service point definition for name in PARMLIB DD member BBMTXP00, then restart the CAS.

BBMXBQ05
Error adding service point definition for name
Explanation:

During coordinating address space (CAS) initialization, member BBMTXP00 is read from the BBIPARM DD to define the expected service points and their security definition tables. An error occurred during the process of adding the service point named name to the system. Additional related messages identify the exact nature of the error.

System action:

The CAS continues initialization and adds all other valid service point definitions contained in BBIPARM DD member BBMTXP00. The service point name is not added, so does not appear on the PLEX view.

User response:

If the service point name is required, read the additional related messages and perform the corrective actions provided to fix the error(s), then, restart the CAS.

BBMXBQ06
Error in update month or year: date for name
Explanation:

During coordinating address space (CAS) initialization, member BBMTXP00 is read from the BBIPARM DD to define the expected service points and their security definition tables. The update month or year of date is incorrectly specified for the service point name.

System action:

CAS initialization terminates.

User response:

Correct the update month or year value specified in member BBMTXP00 for the service point name. The update month value can be a 3-character value that represents the month. Allowable values are:

JAN    APR    JUL    OCT
FEB    MAY    AUG    NOV
MAR    JUN    SEP    DEC

The update year value can be a 4-digit number that represents the year. When the update month and year values are correct, restart the CAS.

BBMXBQ07
Error in update time: hour:minutes for name
Explanation:

During coordinating address space (CAS) initialization, member BBMTXP00 is read from the BBIPARM DD to define the expected service points and their security definition tables. The update time of hour:minutes is incorrectly specified for the service point name.

System action:

CAS initialization terminates.

User response:

Correct either the update time hour or update time minutes value specified in member BBMTXP00 for the service point name. The hour value can be a 2-digit number from 00 to 23 that represents the hour of the day; the minutes value can be a 2-digit value from 00 to 59 that represents the minute of the hour. When the update time value is correct, restart the CAS.

BBMXBQ08
Error in update day: day for name
Explanation:

During coordinating address space (CAS) initialization, member BBMTXP00 is read from the BBIPARM DD to define the expected service points and their security definition tables. The update day of day is incorrectly specified for the service point name.

System action:

CAS initialization terminates.

User response:

Correct the update day value specified in member BBMTXP00 for the service point name. The day value can be a 2-digit number from 01 to 31 that represents the day of the month. When the update day value is correct, restart the CAS.

BBMXBQ09
Error in update month: month for name
Explanation:

During coordinating address space (CAS) initialization, member BBMTXP00 is read from the BBIPARM DD to define the expected service points and their security definition tables. The update month of month is incorrectly specified for the service point name.

System action:

CAS initialization terminates.

User response:

Correct the update month value specified in member BBMTXP00 for the service point name by updating the resource property definition file through the security administrator interface. The update month value can be a 3-character value that represents the month. Allowable values are:

JAN    APR    JUL    OCT
FEB    MAY    AUG    NOV
MAR    JUN    SEP    DEC

When the update month value is correct, restart the CAS.

BBMXBQ10
Error in update year: year for name
Explanation:

During coordinating address space (CAS) initialization, member BBMTXP00 is read from the BBIPARM DD to define the expected service points and their security definition tables. The update year of year is incorrectly specified for the service point name.

System action:

CAS initialization terminates.

User response:

Correct the update year value specified in member BBMTXP00 for the service point name by updating the resource property definition file through the security administrator interface. The update year value can be a 4-digit number that represents the year. When the update year value is correct, restart the CAS.

BBMXBQ11
Parameter parameter occurs twice for name
Explanation:

During coordinating address space (CAS) initialization, member BBMTXP00 is read from the BBIPARM DD to define the expected service points and their security definition tables. The parameter parameter is specified twice for the service point name.

System action:

The duplicate parameter is ignored and the CAS continues to initialize.

User response:

Remove one of the parameter values from member BBMTXP00 for the service point name and restart the CAS.

BBMXBQ12
Service point name name truncated
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBQ13
Unable to allocate Language object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBS01
SubTask Object Failed. FN: function CC: code ZERR: n.
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBS02
SubTask ReAttach failed for function CC: code ZERR: n
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBS03
SubTask ReAttach failed: Previous Subtask not terminated
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBV03
The Size was Invalid
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBV04
The Variable ID was not found
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBV05
The Variable ID already exists
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBX01
The CELLSIZE parameter must be greater than zero, received size
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBX02
The INITNUM must be greater than zero, received number
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBX03
The NAME parameter cannot exceed 23 characters, name is too long
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBX04
PCell cannot allocate Storage Pool
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBX05
Cannot add a PCell for userid: name
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBX06
Input cell size size1 is wrong, correct PCell size is size2
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBX07
The specified PCell (Addr: address) does not exist
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBX08
PCell operation method not allowed for cell state flag flag
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBX09
PCell operation method not allowed for unmatched time stamp
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBX10
The cell being added already exists Key = key
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBZ03
The function received size should be greater than zero
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBZ04
The number of keys, number, was too small
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBZ05
The number of elements, number, was too small
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBZ06
The received element number number was too big
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBZ07
Failed to get size bytes storage
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBZ08
Failed to resize storage for size bytes
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBZ09
Delete not allowed in HArray
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXBZ10
KeyDelete not allowed in HArray
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC002
Free Instance Related Storage failed in Object Storage Free
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC003
Free Instance Related Storage failed because not a slot
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC004
Deallocate failed in Object Instance Deallocate
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC005
Free public data area failed in Object Instance Deallocate
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC006
Free private data area failed in Object Instance Deallocate
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC007
Free error data failed in Object Instance Deallocate
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC008
Free Csrb data failed in Object Instance Deallocate
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC009
Free instance failed in Object Instance Deallocate
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC010
Class class not found in Object Instance Allocate
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC011
Slot not available in Object Instance Allocate
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC012
Get failed public data size bytes in Object Instance Alloc
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC013
Get failed private data size bytes in Object Instance Alloc
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC014
Get failed error data size bytes in Object Instance Alloc
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC015
Get failed Csrb slot size bytes in Object Instance Alloc
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC016
Error allocating classname; RC: code
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC017
Get failed owner storage number slots in Object Slot Get
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC018
Expand Owner failed for number slots in Object Slot Get
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC019
Max expands reached in Object Slot Get
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC020
Storage overlay detected in constructExceptionString
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC021
Severe Invalid parameter or number of parameters
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC022
No exception storage available
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC023
NULL related instance pointer
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC024
A condition was encountered that should never occur
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC025
Program Exception function Classname - class type code
Explanation:

During normal processing, an abend occurred in the function named function having the classname of Classname. The abend was recoverable and had an object class of class, with an abend type of type and abend code of code.

System action:

This message appears in the window. Since a program check caused the abend, a snap dump appears on the console, a LOGREC record is cut, and a system dump is requested.

User response:

Contact your IBM Support Center with the snap dump, LOGREC record, system dump, and a description of the command that was entered or the user action being taken when the error occurred.

BBMXC026
The FVT was not built
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC027
Text: text
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC102
Could not allocate number slots of storage for new owner
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC103
Could not deallocate because not an owner object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC104
Duplicate class class in owner class add
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC105
Load error for class classname, module module
Explanation:

A new object type was requested to be initialized. During this process, the load failed for the load module named module for the class of object named classname.

The most probable cause of this message is a problem with the installation.

System action:

The object is not initialized or allocated. Console messages are issued that indicate the extent of the failure.

If this happens during initialization of the ISPF end-user interface, the Information Display panel is not available.

If this happens during initialization of a window, the window opens, but it fails to initialize a view and remains empty.

User response:

Verify that the product is installed correctly and check any SMP listings to ensure that recent service was properly applied. (All linkedits to target data sets should be RC=0. If SMP target data sets are copied to execution libraries, the copy step should be repeated, taking care to copy everything.)

Look for additional related messages that can indicate a cause for the load module not being found, such as I/O errors. See the information about any additional messages for more actions.

If the problem persists, contact your IBM Support Center with any of the information available from the list shown in Diagnostic information for BB messages.

BBMXC106
Class instance error in owner class add for class class
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC107
Class slot error for size bytes for class class
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC108
Bind fail error in owner class add for class class
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC109
Super Class missing in owner class add for class class
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC110
ClassNameMismatch class : bind (bind and class add)
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC203
The Size was Invalid
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC303
The Variable for this Attribute is missing
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC304
The Size was Invalid
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC305
The Variable for this Attribute is not Allocated
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC403
The Conversation is not Allocated - must already be allocated
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC404
A Variable is required to Send or Receive Data
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC405
The variable has no CSRB
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC406
The Conversation has no CSRB
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC407
Error Resizing Public variable to size bytes
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC408
Error during logon userid:applid
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC409
Invalid Locater on Allocate
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC410
A StorageGroup is required to Receive Data
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC411
Error Receiving on ConversationReceiveAndWait
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC412
Error Receiving on ConversationObjectReceive
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC413
Error Getting size bytes storage through Storage Group
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC503
Request for nn bytes of storage failed
Explanation:

A request for nn bytes of virtual storage could not be satisfied.

System action:

Depends on which component requested the storage. Additional messages are issued indicating system responses.

User response:

If there is a storage shortage in the TSO address space, log off the user session and increase the region size of the TSO address space, then log on again.

If the problem persists, contact your IBM Support Center with any of the information available from the list shown in Diagnostic information for BB messages.

BBMXC603
The Symbol Name length was invalid
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC604
The Type Parameter was invalid
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC605
The Listener was already set
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC606
The Symbol (symbol) was not found
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC607
Expand Failed Adding Symbol - symbol
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC608
Storager request failed for dictionary
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC703
DictionaryAllocate failed during DataBus Allocate
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC704
Action Manager Allocate failed during DataBus Allocate
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC705
Message Queue(StrArray) Allocate failed during DataBus Allocate
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC706
Product access is denied; authorization required
Explanation:

Access to a product was attempted, but the user ID does not have authority to access the requested product.

System action:

Access to the product is denied and this message is displayed along with other messages. When ENTER is pressed, the previous panel or product is displayed, if applicable.

User response:

Perform the following:

  1. Obtain a screen print of this message and related messages.
  2. Contact your security administrator to obtain authorization for your user ID to the required resource that enables access to this product.
BBMXC708
ActionQ Allocate failed during DataBus Allocate
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC709
ActionMgr Allocate failed during DataBus Allocate
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC710
No Local File was allocated
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC711
Currently, only Local View Definitions are allowed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC712
Read failed for type - name
Explanation:

A Read operation has failed for the named name of type type. This message can occur for both views and actions.

Allowable type values are:

ActionTable
The action table named name was not found in the BBACTDEF DD associated with the coordinating address space (CAS). The most probable cause for an action table not being found is that the product is not installed correctly.
ViewDefinition
The view definition named name was not found in the BBVDEF DD associated with the CAS. The most probable causes for a view definition not being found are that the view name was incorrectly entered or the view definition exists in another service point.
System action:

If the type is ActionTable and the action table is required for the system to function, the ISPF end-user interface is unable to initialize and terminates. If the action table is for view or product actions, the view may be displayed, but no actions can be processed.

If the type is ViewDefinition and the view definition is not found, the view does not display.

User response:

If the type is ActionTable, verify that the product is installed correctly and check any SMP listings to ensure that recent service was properly applied. (All linkedits to target data sets should be RC=0. If SMP target data sets are copied to execution libraries, the copy step should be repeated, taking care to copy everything.)

Look for additional related messages that can indicate a cause for the load module not being found, such as I/O errors. See the information about any additional messages for more actions.

If the type is ViewDefinition, verify that the correct view name has been entered. The VIEWS view contains a list of all the views that are available to the service point in the window.

If the problem persists, contact your IBM Support Center with any of the information available from the list shown in Diagnostic information for BB messages.

BBMXC713
ViewDescAllocate failed during DataBus Allocate
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC714
ViewDescMake Failed for view - name
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC715
Function function Not Implemented
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC716
Conversation allocation failed
Explanation:

An attempt to communicate with a CICSPlex SM address space (CMAS) or coordinating address space (CAS) has failed. The presence of this error message indicates that a problem was encountered while attempting to establish communication. Additional messages, if any, may indicate a specific VTAM® error code.

System action:

The view is not displayed and this message appears in the window. Each time Enter is pressed, an attempt is made to reestablish communication.

User response:

Display the PLEX view by typing CONTEXT * PLEXMGR;PLEX in the COMMAND field and pressing Enter. The PLEX view lists all available service points and the current status for each. The status indicates if the requested CMAS is down, the CAS is down, or there are possible VTAM problems. Correct the problem, if possible, and reattempt access.

If the problem persists, contact your IBM Support Center with a screen print of the PLEX view and any of the other information that is available from the list shown in Diagnostic information for BB messages.

BBMXC717
Variable Allocate failed during DataBus Allocate
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC718
Definition File Allocate for DD ddname Failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC719
ActionTable Allocate Failed for name
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC720
Error Listening to local Dictionary
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC721
Error sending data on conversation
Explanation:

The user address space has lost communication with a CICSPlex SM address space (CMAS) or coordinating address space (CAS). The presence of this error message indicates that a problem was encountered while attempting to send data to the service point. Additional messages, if any, may indicate a specific VTAM error code.

System action:

The view is not displayed and this message appears in the window. Each time Enter is pressed, an attempt is made to reestablish communication with the service point.

User response:

Display the PLEX view by typing CONTEXT * PLEXMGR;PLEX in the COMMAND field and pressing Enter. The PLEX view lists all available service points and the current status for each. The status indicates if the requested CMAS is down, the CAS is down, or there are possible VTAM problems. Correct the problem, if possible, and reattempt access.

If the problem persists, contact your IBM Support Center with a screen print of the PLEX view and any of the other information that is available from the list shown in Diagnostic information for BB messages.

BBMXC722
Conversation in state state1 Expecting state2
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC723
Error receiving on conversation
Explanation:

The user address space has lost communication with a CICSPlex SM address space (CMAS) or coordinating address space (CAS). The presence of this error message indicates that a problem was encountered while attempting to receive data from the service point. Additional messages, if any, may indicate a specific VTAM error code.

System action:

The view is not displayed and this message appears in the window. Each time Enter is pressed, an attempt is made to reestablish communication with the service point.

User response:

Display the PLEX view by typing CONTEXT * PLEXMGR;PLEX in the COMMAND field and pressing Enter. The PLEX view lists all available service points and the current status for each. The status indicates if the requested CMAS is down, the CAS is down, or there are possible VTAM problems. Correct the problem, if possible, and reattempt access.

If the problem persists, contact your IBM Support Center with a screen print of the PLEX view and any of the other information that is available from the list shown in Diagnostic information for BB messages.

BBMXC724
Could not find object object to send
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC725
The type for symbol symbol must be T or I
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC726
Error Adding Action to Action Queue
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC727
Error Allocating Data Manager
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC728
Error Allocating Subset Map
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC729
Internal Length error text
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC730
Error Allocating SelectorDefinitions
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC731
Error Processing: action
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC732
ActionNotRecognized: action
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC733
Failed to open Definition DD ddname
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC734
No Application has been chosen
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC735
Unable to locate service point
Explanation:

The user address space was unable to locate the requested product and context. The presence of this error message indicates that a problem was encountered because the requested Service Point is not defined.

System action:

The view is not displayed and this message appears in the window. Each time Enter is pressed, an attempt is made to reestablish communication with the service point.

User response:

Display the PLEX view by typing CONTEXT * PLEXMGR;PLEX in the COMMAND field and pressing Enter. The PLEX view lists all available service points and the current status for each. The status indicates if the requested CICSPlex SM address space (CMAS) is down, the coordinating address space (CAS) is down, or there are possible VTAM problems. If the service point is not defined in the view, start the appropriate CMAS or CAS.

If the problem persists, contact your IBM Support Center with a screen print of the PLEX view and any of the other information that is available from the list shown in Diagnostic information for BB messages.

BBMXC736
Read failed for view - view
Explanation:

The system could not read the view definition named name from the BBVDEF DD associated with the coordinating address space (CAS).

System action:

The view is not displayed and this message is issued. When Enter is pressed, the previous view in the window is redisplayed.

User response:

Verify that the correct view name has been entered. The VIEWS view contains a list of all views that are available to the service point in the window.

Verify that the product is installed correctly and check any SMP listings to ensure that recent service was properly applied. (All linkedits to target data sets should be RC=0. If SMP target data sets are copied to execution libraries, the copy step should be repeated, taking care to copy everything.)

Look for additional related messages that can indicate a cause for the load module not being found, such as I/O errors. See the information about any additional messages for more actions.

If the problem persists, contact your IBM Support Center with any of the information available from the list shown in Diagnostic information for BB messages.

BBMXC737
Deallocate failed for symbol of class class
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC738
Read clear failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC739
View name not found
Explanation:

The view named name was not found in the BBVDEF DD associated with the coordinating address space (CAS).

System action:

The view is not displayed and this message is issued. When Enter is pressed, the previous view in the window is redisplayed.

User response:

Verify that the correct view name has been entered. The VIEWS view contains a list of all views that are available to the service point in the window.

Verify that the product is installed correctly and check any SMP listings to ensure that recent service was properly applied. (All linkedits to target data sets should be RC=0. If SMP target data sets are copied to execution libraries, the copy step should be repeated, taking care to copy everything.)

Look for additional related messages that can indicate a cause for the load module not being found, such as I/O errors. See the information about any additional messages for more actions.

If the problem persists, contact your IBM Support Center with any of the information available from the list shown in Diagnostic information for BB messages.

BBMXC740
Service point not available: status
Explanation:

The requested service point is not in an active status. Allowable status values are:

Detached
One of the CMASs defined to a service point that consists of multiple CMASs has become disconnected from the CAS. The service point can still be accessed, if it is connected to the CAS by another CMAS.
Inactive
The service point has become disconnected from the CAS. To activate the service point, restart the CMAS for that service point.
LateResponse
The service point did not respond within 30 seconds. The associated system may be experiencing distress.
LostContact
The system cannot be accessed. A system outage may have occurred or the system's CAS is not active. Contact is attempted every 2 minutes until communication is reestablished.
NeverActive
The remote service point is defined but has never been active since the last CAS initialization, or the CMAS is in the process of initializing but has not yet connected to the CAS.
Undefined
The service point was active at one time but is no longer defined, or a remote CAS has been activated but the associated CMAS has not.
System action:

The service point is not connected and this message is issued. When Enter is pressed, the previous service point in the window is reconnected.

User response:

Verify that a valid and active service point was requested.

Attempt to correct the problem associated with the status value. If the CMAS is not active for the requested service point, start the address space and attempt to reconnect.

If the problem persists, contact your IBM Support Center with a screen print of the PLEX view and any of the other information that is available from the list shown in Diagnostic information for BB messages.

BBMXC741
The string Array array is invalid
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC742
Error Adding String
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC743
String Extends beyond the end of the action
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC744
Unable to allocate text access object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC745
Test Selector Action Entered
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC746
Test Dialog Action Entered
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC747
View Definition Read not supported for this level databus
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC748
SendNotify Process Type invalid: type
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC749
Unable to allocate StorageGroup for DataBus
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC750
Unable to allocate Storage for ID from type
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC751
Invalid StorageObject for ID
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC752
Error Adding TextBlock for ID
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC753
Test of Action cc: code
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC754
Lost contact with Product Address Space
Explanation:

Communications with a CICSPlex SM address space (CMAS) have failed. This message is followed by message BBMXC758, which provides complete product service point data.

System action:

Each time Enter is pressed on the terminal, an attempt is made to reestablish communication with the product server. Communications resume when the product service point is active.

User response:

Change the context of the window by typing CONTEXT * PLEXMGR;PLEX in the COMMAND field to get a display of all the defined service points and the status of each. If the CMAS is not active for a service point, start the CMAS and then reconnect to the service point.

BBMXC755
No view has been specified
Explanation:

A context was specified for the window, but no view was specified.

System action:

This message is displayed in the window and the system waits for a view name to be entered.

User response:

Enter the name of a view name. If you do not know the name of a view, type VIEWS in the COMMAND field and press Enter. The VIEWS view is displayed, which contains a list of the valid views for the context of the window.

BBMXC756
Could not connect to target system
Explanation:

The required security environment for the user address space could not be established in the target coordinating address space (CAS) or CICSPlex SM address space (CMAS). Since the appropriate security environment could not be established, the user address space is not permitted to connect to the CAS or CMAS.

System action:

Communication with the target address space is terminated. Other messages are issued that explain the reason the security environment could not be established.

User response:

See the user responses for the other messages; contact your security administrator.

BBMXC757
Unable to allocate variable for stoken
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC758
Context: context Product: applid Server: server System: sysid
Explanation:

This message issues with other messages to identify the specific context context, product applid, server server, and system sysid where an error has occurred. The server and sysid values are reserved for future product functions and always appear blank. The context value is the SMF ID of the system on which the error occurred. The applid value is the name of the application or product that was being used when the error occurred.

System action:

The system action depends on the type of error that occurred.

User response:

See the user responses for the other messages.

BBMXC759
No valid context
Explanation:

An invalid context was previously specified for this window and no new context has been specified. The context for a window is specified using the SET or CONTEXT commands, or by invoking a hyperlink.

System action:

The invalid context continues to be ignored and this message is displayed. The system waits for a valid context to be specified.

User response:

Specify a valid context for the window using the SET or CONTEXT commands. If you do not know what the valid context values are, display the PLEX view by typing CONTEXT * PLEXMGR;PLEX in the COMMAND field and pressing Enter. The PLEX view shows a list of the available service points and the current status for each. The service points are valid context values and the status indicates if the requested context value is active. If a specific service point is not active, start the proper coordinating address space (CAS) or CICSPlex SM address space (CMAS) to activate the service point; then use the SET or CONTEXT commands to establish the context for a window.

If the problem persists, contact your IBM Support Center with a screen print of the PLEX view and any of the other information that is available from the list shown in Diagnostic information for BB messages.

BBMXC760
Unable to allocate LuManager object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC803
The Number of Elements is invalid - number
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXC804
The Size of Elements is invalid - size
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA03
Invalid Intent on Put 'intent' Expecting 'wt'
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA04
Unable to open Temporary File name
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA05
Output error on name
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA06
...Writing Record record
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA07
Attempting to close unopened file
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA08
Closing name without a Stow
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA09
Missing Member Name on find or stow
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA10
Access Denied on file
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA11
Output Left in file
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA12
Close Failed on file
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA13
Rename Failed for file
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA14
Required Parm String array pointer missing
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA15
Cannot Write an Empty StrArray
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA16
String in StrArray Too Long size bytes (truncated)
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA17
StringArrayWrite Failed for name
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA18
Get failed for buffer size Bytes
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA19
Path Name Too Long: path
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA20
Open Failed: path
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA21
Get Attempted on unopened file
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA22
Array Allocation Failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA23
Array Get Slot Failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA24
Invalid Dsorg: Dsorg
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA25
MaxLineNegative: maximum
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA26
InvalidIntent: intent
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA27
Text Intents only - Invalid Intent: intent
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA28
String Array Allocation Failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA29
File not found: file
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCA30
FunctionNotImplemented: function
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB02
No Action Table entry found for line command - command
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB03
No Action Table entry found for command - command
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB04
Id: 'ID' is too long
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB05
The input string is empty
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB06
Prefix: 'prefix' is greater than eight characters
Explanation:

A period in the command string is immediately preceded by a prefix of more than eight characters. The prefix is indicated by prefix.

System action:

Additional messages are issued.

User response:

If you are using the window prefix (Wx.), separate it from the related command by a semicolon (;),

If you are using a period with a character string, place the entire string, including the period, inside the quote marks; for example, 'This string ends with a period.'

BBMXCB07
No blank after Quoted string at position position
Explanation:

A blank must separate a quoted string from the command or parameter after which it follows. The position in the COMMAND field where the blank was omitted is indicated by position.

System action:

Additional messages are issued.

User response:

Insert a blank space between the quoted string and the command or parameter that follows it.

BBMXCB08
Quote in token at position Not preceded by blank
Explanation:

A quoted string cannot contain quote marks as part of the quoted text. The position in the COMMAND field where the individual quote marks occur is indicated by position.

System action:

Additional messages are issued.

User response:

Remove the quote marks from the quoted string.

BBMXCB09
Too many tokens in command
Explanation:

A command was issued from the COMMAND field that contains more than 8 tokens, but only 1 to 8 tokens are supported for a single command. A token is a specific value in a view or form that the command action is performed against, so when the command is specified, the values that the command should function against also are specified. Each token in a command is delimited either by a blank character or a comma that is not contained within a single quoted string.

System action:

The command is redisplayed for correction and this message appears in the window.

User response:

If multiple commands were stacked in the COMMAND field, check the command syntax for a missing semicolon, which is used to delimit commands. If more than 8 tokens were specified with a single command, remove token values until no more than 8 are specified.

To get the online help for the command and its syntax, press the HELP key. The long ISPF message is displayed. Press the HELP key again to obtain online help for the command.

BBMXCB10
The Location on Allocate location must be Selector or Dialog
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB11
Command ended without closing quotes
Explanation:

A command was issued from the COMMAND field that contains an opening quote but no ending quote.

System action:

The command is redisplayed for correction and this message appears in the window.

User response:

Either eliminate the opening quote or add an ending quote and press Enter to reissue the command.

BBMXCB12
The Input Command is too long (Greater than 250 characters)
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB13
Could not find Action : action in Table: table
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB14
Could not find Line Action : action
Explanation:

The ISPF end-user interface does not recognize a line command entered in the line command field. The action is the unrecognized line command.

System action:

Additional messages are issued.

User response:

Issue the HELP ACTIONS command to list the line commands that are valid for the view with which you are working.

BBMXCB15
Could not find Action : action
Explanation:

The ISPF end-user interface does not recognize an action entered in the COMMAND field. The action is the unrecognized command.

System action:

Additional messages are issued.

User response:

Issue the HELP ACTIONS command to list the valid actions for the view with which you are working.

BBMXCB17
Request for size bytes of private storage failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB18
ActionTable Make Failed for position position
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB19
Load Failed for Action Load Module Named module
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB20
The table position position was Greater than maximum
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB21
An Object Directed Action action was entered without a target
Explanation:

The action command action requires that an object be defined at the time the command is entered. The object identifies the value in a view against which the command should be executed. The action command named action was issued to a view in a window, but no object was specified with the command.

System action:

The action is not executed and this message is displayed.

User response:

Correct the command syntax and press Enter again.

If the correct command syntax is not known, do one of the following to get online help for the action command:

If the problem persists, contact your IBM Support Center with an example of the command and a screen print of this message and any other messages that are displayed when you press Enter.

BBMXCB22
Action cannot be Processed: No Successful Recognize
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB23
Error Sending Action: action
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB24
Positional parameter after keyword in position position
Explanation:

A command containing a mixture of both positional and keyword parameters was issued from the COMMAND field, but a positional parameter in command parameter position position was specified after a keyword parameter. Both types of parameters in the same command are supported as long as any positional parameters are specified first. In this case, not all of the positional parameters were specified before the keyword parameters. The position value is a number that shows the location of the positional parameter occurring after a keyword parameter, when reading the command syntax from left to right.

System action:

The command is redisplayed for correction and this message appears in the window.

User response:

Correct the command syntax so that all positional parameters are specified first, or remove any keyword parameters.

If the correct command syntax is not known, do one of the following to get online help for the command:

If the problem persists, contact your IBM Support Center with an example of the command and a screen print of this message and any other messages that are displayed when you press Enter.

BBMXCB25
Keyword keyword not recognized
Explanation:

A command containing the keyword keyword was issued from the COMMAND field, but the keyword is not a valid parameter.

System action:

The command is redisplayed for correction and this message appears in the window.

User response:

Correct the command syntax.

If the correct command syntax is not known, do one of the following to get online help for the command:

If the problem persists, contact your IBM Support Center with an example of the command and a screen print of this message and any other messages that are displayed when you press Enter.

BBMXCB26
The required FVT was missing: action
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB27
Invalid Size for Opaque Action: action
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB28
Storage not available for opaque action
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB29
Action action not allowed in history
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB30
Error Allocating Opaque Action Storage Group
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB31
Invalid Object Index: name
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB32
Invalid form name of name
Explanation:

A view or form was requested, but the view or form does not exist. Up to 20 forms can be defined to each view and they are named internally as FORM00 through FORM19. The name value appears as one of these internal form names. If the name value is FORM00, a new view was requested.

This message also can occur when commands are stacked in the COMMAND field. When commands are stacked, they are separated from each other by semicolons. As many commands can be stacked as can fit in the COMMAND field. Therefore, if an error occurs in a command specified early in the stack, other errors may result from command processing of commands that are specified later in the stack. In the case of this message, an earlier error would have caused a failure in creating the form, so the form would be unknown.

System action:

This message is displayed and the request for the new view or form is ignored. Other related messages also can appear that describe why the form was not created. If this message appears during the initialization of a new view, the previous view is redisplayed when Enter is pressed.

User response:

See related messages for more information.

If this message appears without related messages or if the problem cannot be corrected from related message information, contact your IBM Support Center with an example of the command that was issued when the error occurred and any of the other information that is available from the list shown in Diagnostic information for BB messages.

BBMXCB33
Unable to find Query Object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB34
action is not allowed against summarized objects
Explanation:

A line command named action was issued against a data object in a summarized form, but the command is not allowed for summarized objects.

System action:

The line command is ignored and this message is displayed.

User response:

Invoke the hyperlink on the first column in the summarized form to display a tabular form from which the line command can be issued.

If the problem persists, contact your IBM Support Center with an example of the command and a screen print of this message and any other messages that are displayed when you press Enter.

BBMXCB35
For: name
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB36
Action action completed with return code: code
Explanation:

An action command named action was issued against the data within a window and the action completed with a return code of code. This may or may not represent an error condition. Additional messages can indicate the scope and exact nature of the reason for the return code.

System action:

This message is displayed and other valid action commands are processed normally.

User response:

See other messages to determine the cause for the return code and perform the actions required to resolve the error.

BBMXCB37
At: time on date
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB38
FrontEnd Object Directed Command Line actions are not allowed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB39
Error Allocating object pattern filter
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB40
The objident tag is missing for action action
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB41
Unable to determine target for action action
Explanation:

An action command named action was issued against the view in a window, but the action processor could not determine a data object for the action. The object identifies the value in a view against which the command should be executed.

System action:

The action is not executed and this message is displayed.

User response:

Correct the command syntax and press Enter again.

If the correct command syntax is not known, do one of the following to get online help for the action command:

If the problem persists, contact your IBM Support Center with a screen print of the Information Display panel with the action in the command line, then press Enter and a screen print of the resulting messages.

BBMXCB42
This action (action) is not allowed on a summary form
Explanation:

An action command named action was issued against a summarized form, but the action cannot execute against summarized data.

System action:

The line command is ignored and this message is displayed.

User response:

Invoke the hyperlink on the first column in the summarized form to display a tabular form from which the line command can be issued.

To get online help for action commands, do one of the following:

If the problem persists, contact your IBM Support Center with an example of the command and a screen print of this message and any other messages that are displayed when you press Enter.

BBMXCB43
There are no records in this form
Explanation:

An action command was issued against a form that is not displaying any data. Data must be present for an action to be performed. There may be no data present because there may be no data in the query that meets the filter criteria established for the form.

System action:

The action is ignored and this message is displayed.

User response:

None.

BBMXCB44
Action action scheduled
Explanation:

An action command named action was issued and requires asynchronous processing. This processing has been scheduled.

Most actions process synchronously, where the action is scheduled and the system waits for the response. An asynchronous action does not wait for a system response. Instead, these actions are scheduled to be performed, while other actions can be requested immediately.

System action:

This message is displayed and normal processing continues.

User response:

None.

BBMXCB45
Status Report failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB46
Nothing matched the target for action: action
Explanation:

An action command named action that specified a target was issued for the view or form, but no data in the view or form matches the specified target.

The target is a specific data object in a view or form that the command action is performed against. If a data object in a view or form cannot be seen, even by scrolling the view or form, then the action cannot be performed against that data object. Actions can be performed only against the data objects that appear in a view or form.

System action:

The action is not executed and this message is displayed.

User response:

Correct the target value and press Enter again.

To get online help for action commands, do one of the following:

If the problem persists, contact your IBM Support Center with an example of the command and a screen print of this message and any other messages that are displayed when you press Enter.

BBMXCB47
Action Filter: filter
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCB48
Access to action action denied; key=key
Explanation:

A command for a secured action named action was issued against the data in a view, but the user ID does not have the authority to issue the action command. The key value indicates diagnostic security information of up to 24 characters.

System action:

The command is not performed and this message is displayed. When ENTER is pressed, the view reappears but the action has not occurred.

User response:

Perform the following:

  1. Obtain a screen print of this message and related messages that show the resource class and entity name information.
  2. Contact your security administrator to obtain authorization to the required resource for your user ID.

If you feel this message is in error, contact your IBM Support Center with the key value and related message information.

BBMXCB50
Action action
Explanation:

This message is used for diagnostic purposes only and produced after message BBMXCB22 to indicate the exact text of the action that could not be processed.

System action:

The action is not executed and may produce unpredictable results in the request for data.

User response:

Perform the following:

  1. Obtain a screen print of this message and related messages.
  2. Obtain an explanation of the user's actions that produced this result.
  3. Contact your IBM Support Center.

The user may need to clear the window and reissue the commands.

BBMXCD03
The Number of Elements is invalid - number
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCD04
The Index is out of Range
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCD05
The Index is a negative number
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCE03
The Load of the module module failed
Explanation:

A load module named module was requested but could not be loaded. During normal processing, load modules are loaded as needed for execution.

The most probable cause of this message is a problem with installation. Additional messages may indicate the specific cause of the failure to load the module.

System action:

The specific system action depends on the processing that was occurring when the load module failure occurred.

User response:

Verify that the product is installed correctly and check any SMP listings to ensure that recent service was properly applied. (All linkedits to target data sets should be RC=0. If SMP target data sets are copied to execution libraries, the copy step should be repeated, taking care to copy everything.)

Look for additional related messages that can indicate a cause for the load module not being found, such as I/O errors. See the information about any additional messages for more actions.

If the problem persists, obtain as much of the information that is available from the list shown in Diagnostic information for BB messages and contact your IBM Support Center.

BBMXCE04
The Delete of the Module Failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCE05
Module name is not a Help Module
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCE06
Help section section was not found in module module
Explanation:

Help information for a view, element, or the tutorial was requested but not found. The specific internal help section name is section and the system expected to find this section in load module module.

System action:

This message is displayed and the specific help request is not executed.

User response:

The most likely reason for this message is missing help modules. Contact your IBM Support Center after first obtaining a screen print of the Information Display panel both before and after the help request was made.

BBMXCE07
Help Section section was not found in module module
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCF03
Unable to get size bytes of storage for Map
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCF04
Invalid type type in element element
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCG03
Path Name Too Long: path
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCG04
Read Failed: Path: path Member: member
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCG05
File Allocate Failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCG06
No Blank after end quote
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCG07
No Blank before beginning quote
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCG08
Too Many Tokens in text
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCG09
No End Quotes
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCG10
Tag tag is not in allowed in state State
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCG11
Line is too long: line
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCG12
Tag is missing: line
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCG13
Tag Not Found: line
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCG14
Tag Incomplete: line
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCG15
Definition File ended prematurely
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCH03
Invalid DispType: type
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCH04
A field value was too long in Tag: tag, value
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCH05
The following required tag was Missing: tag
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCH06
Tag tag is not allowed in state state
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCJ03
Invalid DispType: type
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCJ04
A field value was too long in Tag: tag, value
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCJ05
The following required tag was Missing: tag
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCJ06
Tag tag is not allowed in state state
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCJ07
Error getting size bytes for an Action Table
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCJ08
Error in Element ID:value in Tag: tag
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCJ09
Parse failed for action table
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCK03
The Number of Elements is invalid - number
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCK04
The Index is out of Range
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCK05
The Index is a negative number
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCK06
No room to add class class
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL03
View view not found
Explanation:

A view named view was requested by typing the view name in the COMMAND field and pressing Enter or by invoking a hyperlink. A view by this name was not found in the BBVDEF data set for the context in the window.

System action:

This message is displayed in the window. When Enter is pressed, the previous view is redisplayed.

User response:

The most probable cause for this error is that a view named view is not defined for the context in the window. To see a list of the valid view names for the current context, display the VIEWS view by typing VIEWS in the COMMAND field and pressing Enter.

If this problem occurred when a hyperlink was invoked, obtain a screen print of any error messages and contact your IBM Support Center.

BBMXCL04
Invalid View List Entry for view
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL05
Selector selector Not Found
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL06
Invalid Selector List Entry for selector
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL07
Communication variable for LuManager not allocated
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL08
WaitList for LuManager not allocated
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL09
Work conversation for LuManager not allocated
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL10
Timer for LuManager not allocated
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL11
LuManager allocation failed at initialization time
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL12
OpMessage for LuManager initialization not allocated
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL13
DataMap allocation failed at LuManager initialization time
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL14
SecAdminLang allocation for LuManager failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL15
Initialization Error: reason text
Explanation:

During coordinating address space (CAS) initialization or termination, an internal error occurred because of reason text, which can be one of the following:

Subtask Allocate Failed
During CAS initialization, an error occurred which resulted in a failure to create a critical subtask. The subtask is necessary for successful initialization.
Wait for Start Failed
During CAS initialization, a subtask was successfully created but did not start. An error occurred when the program timed out waiting for the subtask to start.
EOT Before Start Posted
During CAS initialization, a subtask was successfully created but the subtask posted an end-of-task (EOT) before it could be successfully started.
Wait for Shutdown Failed
During CAS termination, a subtask was scheduled for shutdown, but an error occurred when the program timed out waiting for the subtask to shut down.
Premature End of LuManager Task
During CAS initialization or termination, the LuManager task ended abnormally, causing the CAS to terminate abnormally.
System action:

CAS initialization fails or termination ends abnormally.

User response:

Look for related messages providing additional information about the internal error and perform the corrective actions associated with those messages. Restart the CAS.

If the problem persists or you cannot correct the error, contact your IBM Support Center with as much as possible of the information listed in Diagnostic information for BB messages.

BBMXCL16
Open failed for parmlib ddname
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL17
Read failed for parmlib ddname member member
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL18
Processing failed for parmlib ddname member member
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL19
PLEXMGR service point attach failed
Explanation:

When the coordinating address space (CAS) initializes, it issues a service point attach for the LU Manager and establishes a service point. This message indicates that the LU Manager could not initialize correctly, so the service point was not established. This CAS service point keeps track of any CICSPlex SM address space (CMAS) service points as they initialize and monitors the availability of cross-system communications.

The most probable cause of this message is a problem with installation. Additional messages may indicate the specific cause of the failure to initialize.

System action:

The CAS does not initialize properly, so the ISPF end-user interface cannot be used.

User response:

Verify that the product is installed correctly and check any SMP listings to ensure that recent service was properly applied. (All linkedits to target data sets should be RC=0. If SMP target data sets are copied to execution libraries, the copy step should be repeated, taking care to copy everything.)

Look for additional related messages that can indicate a cause for the load module not being found, such as I/O errors. See the information about any additional messages for more actions.

If the problem persists, obtain as much of the information that is available from the list shown in Diagnostic information for BB messages and contact your IBM Support Center.

BBMXCL20
GSI LU Query service action failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL21
LuManager failed to find the index for index from table table
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL22
There is no index in the index matched entry in table table
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL23
DataMap Make failed at LuManager initialization time
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL24
Allocate failed in location for object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL25
Service Point Manager Processing Error for object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL27
Error establishing default security environment
Explanation:

A request to construct the default security environment failed.

System action:

Access is denied and this message is displayed along with other related messages.

User response:

See the user responses for the related messages.

BBMXCL28
Access to CAS denied; authorization required
Explanation:

Access to the coordinating address space (CAS) was attempted, but the user ID does not have authority to access the CAS. This message is issued as a TSO message and also is issued to the console.

System action:

Access to the window environment is denied and this message is displayed along with other messages.

User response:

Contact your security administrator to obtain authorization to the required resource for your user ID.

BBMXCL29
Unable to allocate security object
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL30
Resource definition build failed for parmlib ddname member member
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL31
A recoverable error occurred processing parmlib ddname member member
Explanation:

A problem was encountered processing member member in the parmlib data set named ddname. The system did not consider the error to be serious; however, other problems may occur later due to this error.

System action:

Processing continues normally as if the error did not occur and this message is displayed along with related messages.

User response:

Press ENTER to return to the active session from this message display.

Look for related messages that indicate the nature of the problem and correct it.

BBMXCL32
Resource definition language allocate failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL33
Authorization failed attaching service point product context server
Explanation:

A product named product on a system named context with a step name of server was started, but the associated security ID does not have the authority to attach a service point to the coordinating address space (CAS). The security ID used to start a product must be authorized to attach a service point to the CAS or an error results. This prevents unauthorized users from starting and using products.

This message is issued to the console.

System action:

The service point for product is not attached to the CAS and no window access is provided.

User response:

If you believe this message is in error, contact your security administrator to verify authorization to the required resource for your user ID.

BBMXCL34
Product name product is invalid
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL35
Resource definition parse failed for parmlib ddname member member
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL36
Default resource definition used for product resources
Explanation:

There are no customized resource definition files for the product named product. The default resource definition files shipped with the product are used.

System action:

Processing continues normally using the default resource definition files.

User response:

None

BBMXCL37
Authorizing function; key=key
Explanation:

During the process of authorizing the function set named function, an error occurred. The value function can be either Common Actions or Product Actions. The key value indicates diagnostic security information of up to 24 characters.

System action:

Depends on the type of error that occurred, which is further defined by other messages that are issued with this message. The related message indicate whether or not access is denied.

User response:

Perform the following:

  1. Obtain a screen print of this message and related messages that show the resource class and entity name information.
  2. Contact your security administrator to obtain authorization to the required resource named function for your user ID.

If you feel this message is in error, contact your IBM Support Center with the key value and related message information.

BBMXCL39
Target CPSM attach failed, reason
Explanation:

CICSPlex SM cannot attach to a coordinating address space for the reason specified. The reason may be that the BBACTDEF (action) and/or the BBVDEF (view) definitions are missing for the address space associated with CICSPlex SM.

System action:

CICSPlex SM is not attached.

User response:

Check the started task procedure for CICSPlex SM to ensure that both a BBACTDEF DD and a BBVDEF DD are defined properly. Restart the address space to attempt to attach CICSPlex SM.

BBMXCL40
Type member member not found in ddname
Explanation:

This message occurs when member member is not defined in the parmlib specified by the DD statement.

System action:

Processing continues using the default.

User response:

None.

Note:
CICSPlex SM does not use the SSI feature. The message is included for informational purposes only.
BBMXCL41
Default system values used for the target definition
Explanation:

During coordinating address space (CAS) initialization, a target definition parmlib member for the local CAS was not located.

System action:

CAS initialization continues normally using default values.

User response:

None.

BBMXCL53
Fail to get size bytes of storage for SysMonActionSetUp
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL54
Fail to allocate DataMap object for SysMonActionMapGet
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL55
The DataMapMake function call failed in SysMonActionMapGet
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCL56
Status data not received from CAS cccccccc
Explanation:

This message indicates the local CAS was able to establish communications to a remote CAS, but service point status information which was requested from the remote CAS named cccccccc was not returned. Instead of status information, informational, warning or error messages were returned from the remote CAS, explaining why the requested status information was not returned. These messages are usually displayed immediately prior to this message.

System action:

The local CAS's service point table is not updated to include new service points or current status infor mation of a service point, which is directly attached to the CAS named cccccccc.

User response:

This message is usually indicative of an incorrect CAS definition of a remote CAS in the local CAS. To locate and correct the incorrect CAS definition, perform the following steps:

  1. Sign on to the PLEXMGR application on the local CAS.
  2. Enter CASDEF on the command line to cause the list of local CAS definition entries to be displayed.
  3. Enter EDIT on the command line to place the view into update mode.
  4. Locate entry cccccccc. This is the incorrect CAS definition. Place a ‘c’ in the command column next to the entry name. This will cause the entry to be displayed in update mode.
  5. Note the values set for the following fields:
    • CAS System Name
    • MVS System Name
    • VTAM Appl Name
  6. Go to the remote CAS executing on the MVS system identified in the above ‘MVS System Name’ and sign on to the PLEXMGR application on that CAS. Repeat steps 2, 3, and 4 on this CAS. However, instead of locating and displaying entry cccccccc, locate and display the definition for this remote CAS.
  7. Compare values of ‘CAS System Name’ and ‘VTAM Appl Name’ fields. These values must be identical in both CAS definitions. The values specified in the local CAS's entry must be the same as those in the remote CAS's entry. If they are not, change the fields in the local CAS's entry to match those in the remote CAS's entry. Then stop and restart the local CAS address space.
  8. If the messages continue, contact your IBM Support Center.
BBMXCM03
The number of rows, number, must be positive and less than 255
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCM04
The number of columns, number, must be positive and less than 255
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCM05
Allocate failed for dynamic area of size characters
Explanation:

In the TSO address space, an attempt to obtain virtual storage failed. Virtual storage was being requested during the initialization of a window. Typically, this message is issued because the region size in the TSO address space is too small to accommodate the new window that was attempted to be opened. This message is displayed only when opening a new window; a different message is displayed if there is not enough virtual storage for a screen definition request.

System action:

The window in which the failure occurred terminates, but it still appears on the screen with a T (terminated) status. All other windows continue processing normally.

User response:

Do one of the following:

If a larger region size is used and the problem persists, contact your IBM Support Center after gathering the following information:

BBMXCM06
Invalid Top Row: row
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCM07
Invalid LeftCol: column
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCM08
Invalid Visible Columns: number
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCM09
Invalid Visible Rows: number
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCN03
Invalid position option: option
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCN04
Tree was not open when process was attempted
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCN05
Invalid Search option: option
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCN06
SetOrder failed resetting tree (what:code zerr:n)
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCN07
Tree Open Failed (what:code zerr:n)
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCN08
Tree Allocate Failed (what:code zerr:n)
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCN09
Tree Add Failed (what:code zerr:n)
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCN10
Tree Delete record Failed (what:code zerr:n)
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCN11
Tree Position Failed (what:code zerr:n)
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCN12
Tree Scan Failed (what:code zerr:n)
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCN13
Tree Search Failed (what:code zerr:n)
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCN14
Tree Close Failed (what:code zerr:n)
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCN15
Tree Reset Failed (what:code zerr:n)
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCN16
Too Many Required elements
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCN17
Mapped Add Failed (what:code zerr:n)
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCN18
Unable to allocate buffer storage
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCN19
Mapping Failed for table
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCN20
Id Field column Not in baseMap - table
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCP03
Load failed for selector module: module
Explanation:

A view was requested by typing the view name in the COMMAND field and pressing Enter or by invoking a hyperlink. During the initialization of the view, the load module named module that contains the selector code for the view could not be loaded. During view initialization, the selector code obtains the data requested in the view.

The most probable cause of this message is a problem with installation. Additional messages may indicate the specific cause of the failure to initialize.

System action:

The view request is not processed and this message is displayed. Unless another view is requested, the previous view is redisplayed on the next Enter. If no previous view existed, the window remains empty until a new view is selected.

User response:

Verify that the product is installed correctly and check any SMP listings to ensure that recent service was properly applied. (All linkedits to target data sets should be RC=0. If SMP target data sets are copied to execution libraries, the copy step should be repeated, taking care to copy everything.)

Look for additional related messages that can indicate a cause for the load module not being found, such as I/O errors. See the information about any additional messages for more actions.

If the problem persists, obtain as much of the information that is available from the list shown in Diagnostic information for BB messages and contact your IBM Support Center.

BBMXCP04
Table table Not Found in Selector Dictionary
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCP05
Unable to add Module: module as class: ProductSelector
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCP06
Failure allocatingProductSelector Object for module
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCP07
Failure loading map: module
Explanation:

A view was requested by typing the view name in the COMMAND field and pressing Enter or by invoking a hyperlink. During the initialization of the view, the load module named module that contains the mapping information for the view data could not be loaded. The mapping information is used to specify what data should appear in which fields in a view.

The most probable cause of this message is a problem with installation. Additional messages may indicate the specific cause of the failure to initialize.

System action:

The view request is not processed and this message is displayed. Unless another view is requested, the previous view is redisplayed on the next Enter. If no previous view existed, the window remains empty until a new view is selected.

User response:

Verify that the product is installed correctly and check any SMP listings to ensure that recent service was properly applied. (All linkedits to target data sets should be RC=0. If SMP target data sets are copied to execution libraries, the copy step should be repeated, taking care to copy everything.)

Look for additional related messages that can indicate a cause for the load module not being found, such as I/O errors. See the information about any additional messages for more actions.

If the problem persists, obtain as much of the information that is available from the list shown in Diagnostic information for BB messages and contact your IBM Support Center.

BBMXCP08
Access denied to table; key=key
Explanation:

A view was requested for display, but the user ID does not have the authority to look at the table associated with the view. The key value indicates diagnostic security information of up to 24 characters.

System action:

The view is not displayed, but this message appears. When ENTER is pressed, the previous view is redisplayed.

User response:

Perform the following:

  1. Obtain a screen print of this message and related messages.
  2. Contact your security administrator to obtain authorization for the required resource for your user ID.

If you feel this message is in error, contact your IBM Support Center with the key value and related message information.

BBMXCQ03
The requested table table was not found
Explanation:

The selector table named table was not found in the BBACTDEF DD associated with the coordinating address space (CAS) or CICSPlex SM address space (CMAS) that was attempting to initialize. A selector table is a parameter of a service point attach that lists the load modules that are required to be loaded and executed to produce the data for each view. When the CAS or CMAS initialize, they issue a service point attach to establish a service point and identify what other service points are available for processing.

The most probable cause of this message is a problem with installation. Additional messages may indicate the specific cause of the failure to initialize.

System action:

The specific service point that failed is not attached and is not available for processing.

User response:

Verify that the product is installed correctly and check any SMP listings to ensure that recent service was properly applied. (All linkedits to target data sets should be RC=0. If SMP target data sets are copied to execution libraries, the copy step should be repeated, taking care to copy everything.)

Look for additional related messages that can indicate a cause for the load module not being found, such as I/O errors. See the information about any additional messages for more actions.

If the problem persists, contact your IBM Support Center with a copy of the started task JCL for the CAS or CMAS, a member list for the BBACTDEF DD data sets in the CAS or CMAS, and as much of the other information that is available from the list shown in Diagnostic information for BB messages.

BBMXCQ04
Error adding to tree: table
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCR03
Lengths did not match in copying text
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCR04
Error loading map: module
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCR05
Error Allocating selector: module
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCR06
Error During Refresh: function
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCR07
Error During Request: function
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCR08
Unable to obtain storage for data size Bytes
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCR09
Set Order Failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCR10
Request for Data Failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCR11
There is no data which satisfies your request
Explanation:

A view command could not display data because no data matched the filter conditions. The command or action executed successfully, but there is no data to display.

System action:

Additional messages are issued.

User response:

None.

BBMXCR12
Wrong State For Data: state
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCR13
View Initialization Failed
Explanation:

The BBVDEF DD statement in the coordinating address space (CAS) and CICSPlex SM address space (CMAS) started task procedures must point to the library distributed by IBM. In one of the procedures, either the DD statement is pointing to a user library or a user library is concatenated to the DD statement.

Another reason for this error could be that the SEYUVDEF library had members copied into it using the ISPF copy utility. During the copy process, the SPECIFY PACK OPTION FOR 'TO' DATASET option was defined as Y for YES. The SEYUVDEF library cannot be packed.

System action:

If the CAS BBVDEF DD was modified, no PlexManager views are available; if the CMAS BBVDEF DD was modified, no CICSPlex SM views are available.

If the SEYUVDEF library was packed during a copy procedure, no views of any type are available.

User response:

If the BBVDEF DD statement was modified, change the statement in the CAS and CMAS started task procedures to point to the distributed view definition library and remove any concatenated user libraries.

If the SEYUVDEF library was packed during a copy procedure, use the ISPF copy utility to unpack the data set.

BBMXCR14
View Refresh Failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCR15
Tree Set Order Failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCR17
Tree OperationFailed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCR18
No view to initialize
Explanation:

This message appears after an error in a window has occurred and the system attempts to return to the previous view for the window, but no view existed. For example, a new window is opened and then an invalid view name is entered. Error messages about the invalid view name are displayed and when Enter is pressed, this message appears to indicate that this window did not contain a valid view.

System action:

This message is displayed until a valid view is requested for the window.

User response:

Type a valid view name in the COMMAND field and press Enter.

To see a list of the valid view names for the window, type VIEWS in the COMMAND field and press Enter. The VIEWS view is displayed, which lists all of the valid views for the context in the window.

BBMXCR19
Program Exception in function - class type code
Explanation:

During normal processing, an abend occurred in the function named function. The abend was recoverable and had an object class of class, with an abend type of type and abend code of code.

Selectors are the programs that produce the specific type of data that is requested by a view. If a selector was the object where the abend occurred, the abend is recorded only once, even if exception condition occurs more than once.

System action:

This message appears in the window. When Enter is pressed, another attempt to obtain data is made. Since a program check caused the abend, a snap dump appears on the console, a LOGREC record is cut, and a system dump is requested.

User response:

Contact your IBM Support Center with the snap dump, LOGREC record, system dump, and a description of the command entered or the user action being taken when the error occurred.

BBMXCR20
Unable to Allocate Help Dictionary
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCR21
Help Member not found member.table.section
Explanation:

No help is available for the item where the cursor is, or for the topic specified with the HELP command.

System action:

Additional messages are issued.

User response:

From the COMMAND field of a help pop-up window, do one of the following:

BBMXCR22
Table table is not defined
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCR23
Help Not Found - table.element
Explanation:

Online help was requested for the named element, but no help text for an element of that name could be found, where:

table
is the name of the internal help table that was searched.
element
is the name of the element for which help was requested.

Either the named element does not exist, or help for that element is not available from your current position in the window interface.

System action:

This message appears in a help pop-up window in place of help text.

User response:

Issue the END command to exit from the help pop-up window.

If you issued the HELP command with a parameter, make sure the parameter was specified correctly. When issued from the COMMAND field of an Information Display panel, the HELP command accepts the following parameters:

HELP
For information about the help facility.
cmdname
For information about the specified display command.
viewname
For information about the specified view.
ACTIONS
For information about the action commands available for the view displayed in the current window.

If you expected to receive help based on the position of your cursor, make note of the cursor position and the text of this message and contact your IBM Support Center.

BBMXCR24
Unable to allocate storage Group
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCS03
Error adding to tree
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCT03
Error Resizing Private variable to size bytes
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCT04
Cannot have multiple not-posted waits for the same conversation
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCT05
No CSRB slot
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCT06
CSRB slot exists but has not been Allocated
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCT07
Get failed for size bytes
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCT08
Wait requested with no conversations now on waiting list
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCU03
Timer Conversation Allocate Failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCU04
Timer Variable Allocate Failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCV03
Invite for new conversation failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCV04
Max DataManager Subtasks exceeded
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCV05
Transaction Allocate Failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCY01
Invalid Option to ScrnSyncRequest option
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCY02
The Global Variable !SSY could not be allocated
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCY03
WaitList Allocate Failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCY04
Allocate Conversation failed for The Stax Conversation
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCY05
Could not allocate a conversation for waiting
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCY06
The Screen is not Available on an Immediate Request
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXCY07
The user pressed attention
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXNS01
ConversationAllocate failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXNS02
MZS_CREATE_NPIPE failed, RC=RC: Zerr=Zerr
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXNS03
MZS_DESTROY_NPIPE failed, RC=RC: Zerr=Zerr
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXNS04
Invalid work element request code: WE=We REQ=Req
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXNS05
MZS_SET_PSTATE failed, RC=RC: Zerr=Zerr
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXNS06
Work SubTaskAllocate failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXNS07
MSS_SECR_DELETE failed, RC=RC: Zerr=Zerr
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXNS08
BsamFileAllocate failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXNS09
BsamFileMemberStrArrayRead failed
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXNS10
Too many properties to fit into 61K pipe state data
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXNS11
Property value longer than 255 for Cat.Ident.Type
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXNS12
MZS_HALT_PINSTANCE failed, RC=RC: Zerr=Zerr
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXNS13
MSE_EPOST failed, RC=RC: Zerr=Zerr
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXNS14
TargetSvcWorkElement MFS_SBPOOL CREATE failed, RC=RC: Zerr=Zerr
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXNS15
TargetSvcWorkElement MFS_SBPOOL DELETE failed, RC=RC: Zerr=Zerr
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXNS16
TargetSvcWorkElement MFS_SBGET failed, RC=RC: Zerr=Zerr
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXNS17
TargetSvcWorkElement MFS_SBFREE failed, RC=RC: Zerr=Zerr
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXSS01
Error getting size bytes of storage
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXSS02
Error from TraceStatus Service rc: code acs1: acs1 acs2: acs2
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXSS03
Error adding record to Tree
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXSS04
Invalid length for Task Token
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXSS05
Error Performing function: function on target
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXSS06
Function: function is not defined for target
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXSS07
Invalid Task Index: index
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXY003
The Language Load Module module is not loaded
Explanation:

The load of the Language Load Module named module has failed. Language Load Modules define the execution algorithms for processing filter expressions and must be loaded to execute. The most probable cause of this message is a problem with the installation.

System action:

The filter is not executed and this message is displayed. Additional messages also may appear. When Enter is pressed, the view is displayed but may contain more data than requested.

User response:

Verify that the product is installed correctly and check any SMP listings to ensure that recent service was properly applied. (All linkedits to target data sets should be RC=0. If SMP target data sets are copied to execution libraries, the copy step should be repeated, taking care to copy everything.)

Look for additional related messages that can indicate a cause for the load module not being found, such as I/O errors. See the information about any additional messages for more actions.

If the problem persists, contact your IBM Support Center with an example of the command and a screen print of this message and any other messages that are displayed when you press Enter.

BBMXY004
The Language Scanner Table module is not loaded
Explanation:

The load of the Language Scanner Table named module has failed. Language Scanner Tables define the syntax for filter expressions and must be loaded to execute. The most probable cause of this message is a problem with the installation.

System action:

The filter is not executed and this message is displayed. Additional messages also may appear. When Enter is pressed, the view is displayed but may contain more data than requested.

User response:

Verify that the product is installed correctly and check any SMP listings to ensure that recent service was properly applied. (All linkedits to target data sets should be RC=0. If SMP target data sets are copied to execution libraries, the copy step should be repeated, taking care to copy everything.)

Look for additional related messages that can indicate a cause for the load module not being found, such as I/O errors. See the information about any additional messages for more actions.

BBMXY005
Positional parameter value was not specified
Explanation:

This message is issued with other messages when a syntax error is encountered during action command processing. The action command definition requires a positional parameter named value that was not specified with the command in the COMMAND field.

System action:

The command is ignored and this message is displayed with other messages.

If commands were stacked in the COMMAND field or hyperlink definition, other valid commands are processed normally.

User response:

Correct the command syntax and press Enter to reissue the command.

If the correct command syntax is not known, do one of the following to get online help for the command:

If the command was issued by invoking a hyperlink, contact your IBM Support Center.

BBMXY006
Language processor detected syntax error
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXY007
Statement number statement
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXY008
Invalid token number=token, value=value
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXY009
Invalid token number=1, value=End-Of-File
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXY010
Invalid version of Keyword table; table=tblversion driver=prsversion
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Language processing ignored.

User response:

Contact your IBM Support Center.

BBMXY103
Invalid number of records entered : number
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXY104
Requested data type result is invalid, type
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXY106
Pattern segment exceeds maximum length length
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXY107
Too many pattern segments, maximum is maximum
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXY202
The number of data records number is invalid
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXY203
The number of sub languages number is invalid
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXY205
Sublanguage statement exceeds maximum length length
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

BBMXY207
Sublanguage statement name is not supported
Explanation:

This is a diagnostic message containing error information used by IBM support to resolve the error condition.

System action:

Additional messages are issued.

User response:

See related messages and perform the actions provided.

[[ Contents Previous Page | Next Page Index ]]