Messages BBMZS100 through BBMZS199

BBMZS100

SPCF IS ACTIVE, GROUP=groupName, MEMBER=memberName

Explanation: The Sysplex Communication Facility (SPCF) initializes successfully with the BBPlex group name of xxxx and member name of yyyy. This is an informational message.

User response: No action is required.

BBMZS110

SPCF Initialization Failed reasonText

Explanation: The Sysplex Communication Facility (SPCF) initialization failed for one of the following reasons, indicated by reasonText:

• ERROR ON FORMATTING SPLT

  An error occurred while trying to format the Sysplex Communication Facility Local Table (SPLT) during the initialization stage. SPCF fails to initialize.

  Action: Contact BMC Support with the reason text.

• BBGROUP NAME IS INVALID

  The BBGROUP name is missing due to the incorrect specification of the Coordinated Address Space System Definition Table (CASD). SPCF fails to initialize.

  Action: Contact BMC Support with the reason text.

• ERROR ON ISSUING SET_EOMEXIT

  An error occurred when the SET_EOTEXIT command was issued. SPCF fails to initialize.

  Action: Try to restart the Sysplex Communication Facility (SPCF) by entering the MVS MODIFY command of F casname,SPCF=START. If the problem persists, contact BMC Support with the reason text.

• ERROR ON ISSUING SET_EOTEXIT

  An error occurred when the SET_EOTEXIT command was issued. SPCF fails to initialize.

  Action: Try to restart the Sysplex Communication Facility (SPCF) by entering the MVS MODIFY command of F casname,SPCF=START. If the problem persists, contact BMC Support with the

• ERROR DURING XCF JOIN; RC/RS=XX/YY

  An error occurred while trying to join the Cross System Coupling Facility (XCF) to establish communication links. The indicated return code and reason code are displayed in the message text. SPCF fails to initialize.

  Action: See MVS Programming: Sysplex Services Reference regarding the indicated return code and reason code of the IXCJOIN macro and try to correct the error. If the problem persists, contact BMC Support with the Code and reason code values.

• ERROR DURING PGLOAD EXITS

  An error occurred while loading the Sysplex Communication Facility (SPCF) exits. SPCF fails to initialize.

  Action: If the problem persists, contact BMC Support with the details.

• ERROR DURING SBGET FOR ANSWER AREAS

  A Storage Block Get (SBGET) service failed to acquire storage for the answer areas. SPCF fails to initialize.

  Action: Contact BMC Customer Support with any information available in this message.

• ERROR BUILDING STORAGE POOLS

  An error occurred while trying to build storage pools due to a shortage of space in the storage area. SPCF fails to initialize.

  Action: Contact BMC Support with this message.

• ERROR BUILDING MESSAGE QUEUES

  An error occurred while trying to build message queues. SPCF fails to initialize.

  Action: Contact BMC Support with this message.

• ERROR DURING XCF QUERY; RC/RS= XX/YY

  An error occurred while issuing the Cross System Coupling Facility (XCF) Query service. The indicated return code and reason code appear in the message text. The Sysplex Communication Facility (SPCF) fails to initialize.

  Action: See MVS Programming: Sysplex Services Reference regarding the indicated return code and reason code of the IXCQUERY macro and try to correct the error. If the error persists, contact BMC Support with the r code and reason code values.

• ERROR BUILDING SYSPLEX STRUCTURE

  There was not enough storage to build the SYSPLEX structure. SPCF fails to initialize.

  Action: Contact BMC Support.

• ERROR BUILDING BBGROUP STRUCTURE

  There was not enough storage to build the BBGROUP structure. SPCF fails to initialize.

  Action: Contact BMC Support.

• DUPLICATE XCF MEMBER NAME: group/member

  A duplicate XCF member name was found when trying to initialize the Sysplex Communication Facility (SPCF). The group and member names are unique identifiers. SPCF fails to initialize.

  Action: Determine why a duplicate XCF member name exists. In most instances, you will find that SPCF has already been initialized.

User response: See the individual reasons.

BBMZS111

SPCF INITIALIZATION FAILED; XCF NOT SUPPORTED ON THIS SYSTEM

Explanation: An error occurred while trying to use the Cross Coupling Facility (XCF) service due to the operating system not supporting XCF. These services are supported on the MVS/ESA SP version 4.2.2 or higher. The Sysplex Communication Facility (SPCF) fails to initialize.

User response: No action is required.

BBMZS112

Create Sppi on channel channelNumber for name

Explanation: This XDM message indicates the creation of a pipe instance. A pipe instance has the indicated channel number associated with it. The number will be negative if this half-session is the originator of the conversation. The other side of the conversation will have the same number only positive. The corresponding Sppi may be on another CAS. The name field is used to identify the pipe.

User response: No action is required.

BBMZS113

Create Sppi failed, RC=returnCode for name

Explanation: This XDM message indicates the failure to create a pipe instance. The reason code is an SPCF internal process return code. The name of the pipe is also documented.

User response: No action is required.

BBMZS114

Create Spnp on system for name

Explanation: This XDM message indicates the creation of a new pipe. The pipe is located on the indicated system as indicated and has the indicated name.

User response: No action is required.

BBMZS115

Create Spnp failed RC=returnCode for name

Explanation: This XDM message indicates the failure of a pipe creation. The reason code is documented in the process return codes. The name of the failed pipe is also included.

User response: No action is required.

BBMZS116

Destroy Spnp on system for name

Explanation: This XDM message indicates the destruction of a pipe. The name of the system where the pipe existed and the pipe name are indicated.

User response: No action is required.

BBMZS117

Create Spnp name

Explanation: This XDM message indicates the successful request to create a named pipe.

User response: No action is required.

BBMZS118

Create Spnp failed, RC=returnCode for name

Explanation: This XDM message indicates the unsuccessful request to create a named pipe. The reason code for the failure is a process return code.

User response: No action is required.

BBMZS119

Create Sppi failed, RC=returnCode for name

Explanation: This XDM message indicates the unsuccessful request to create a pipe instance. The reason code for the failure is a process return code.

User response: No action is required.

BBMZS120

SPCF server encountered an invalid SPCE header

Explanation: An internal control block did not have the proper format. The request is discarded.

User response: Watch for additional errors that may result as a consequence of this failure. Users may experience hang situations or views may not update because sessions to the other system should have started or stopped. Gather the CAS log and the SYSLOG that were current when the failure occurred and provide this information to BMC Support.

BBMZS121

SPCF server error-no SPBE entry found for the SPCE event

Explanation: A request to deactivate a group member failed because the member could not be found. The deactivation request is ignored. Additional errors might accompany this failure. Users may experience hang situations or views may fail to update because the sessions to the failing system should have been terminated.

User response: Gather the CAS log and the SYSLOG that were current when the failure occurred and provide this information to BMC Support.

BBMZS122

SPCF server error-SPBE is already inactive for the SPCE event

Explanation: A request to deactivate a group member failed because the member was already inactive. The inactivation request is ignored. Additional errors might accompany this failure. Users may experience hang situations or views may fail to update because the sessions to the failing system should have been terminated.

User response: Gather the CAS log and the SYSLOG that were current when the failure occurred and provide this information to BMC Support.

BBMZS123

SPCF server error-Maximum SPBE is reached

Explanation: A request to add a group member failed because the group member table is full. The activation request is ignored.

User response: Gather the CAS log and the SYSLOG that were current when the failure occurred and provide this information to BMC Support.

BBMZS124

SPCF server error-SPSE entry not found

Explanation: A request to remove an MVS system from the SYSPLEX failed because an entry could not be found that corresponds to the MVS system. This is an extended diagnostic mode (XDM) message. The request to remove the system that cannot be found is ignored.

User response: Gather the CAS log and the SYSLOG that were current when the failure occurred and provide this information to BMC Support.

BBMZS125

SPCF server error-Invalid SYSTEM name for SPCE

Explanation: A request to remove an MVS system from the SYSPLEX failed because the entry that describes the MVS system has a different system name in the internal table. The request to remove the system is ignored.

User response: Gather the CAS log and the SYSLOG that were current when the failure occurred and provide this information to BMC Support.

BBMZS126

SPCF server error-Maximum SPSE is reached

Explanation: A request to add an MVS system to the SYSPLEX failed because the internal table is full. This is an extended diagnostic mode (XDM) message. The request to add the MVS system is ignored.

User response: Gather the CAS log and the SYSLOG that were current when the failure occurred and provide this information to BMC Support.

BBMZS127

SPCF server error-SBGET RFPQ failed

Explanation: While adding another system to the group, a failure occurred trying to obtain storage. This is an extended diagnostic mode (XDM) message. This system is unable to inform the new member of the group of all its named pipes. The new member will either be unaware of these connections or its attempts to make connections will fail.

User response: Gather the CAS log and the SYSLOG that were current when the failure occurred and provide this information to BMC Support.

BBMZS128

SPCF bypass post in shutdown SPRE=xxxxxxxx

Explanation: This XDM message indicates that during shutdown of the CAS, the SPCF server bypassed posting the ECB associated with a server request element (SPRE). During shutdown, tasks that own the ECB storage might terminate before SPCF can process the SPRE, thus causing a failure in the post. These messages are informational. CAS termination proceeds normally.

User response: No action is required.

BBMZS129

SPCF server error-SPCE process abended

Explanation: An unexpected error has occurred. The current request is discarded.

User response: Gather the CAS log and the SYSLOG that were current when the failure occurred and provide this information to BMC Support. There will also be a dump created of this failure and it too may be required.

BBMZS131

SPCF server error-Invalid SPRE reserved field

Explanation: An internal control block has an invalid function code Issue this message and then ABEND S0C1. The ABEND is taken in order to obtain a dump. The system will recover and discard the invalid control block. This is an extended diagnostic mode (XDM) message.

User response: Contact BMC Support and provide the CAS log and the dump that follows. Note that because this control block is ignored, other problems may occur.

BBMZS132

SPCF server error-SPRE POST error. code=errorCode

Explanation: An error occurred attempting to POST the user's side of a request. The SPRE is discarded without notifying the requestor.

User response: Contact BMC Support and provide the CAS log and SYSTEM log from around the time of the failure. Because a request did not complete, users might be reporting additional symptoms such as hangs.

BBMZS133

IXCMSGO macro error, RC=returnCode, RS=reasonCode, attempting retry

Explanation: An error occurred while trying to run the IXCMSGO macro with the indicated return code and reason code. The return and reasons codes are documented in the IBM manual MVS Sysplex Services Reference. The most common retriable errors are as follows:

There are many other retriable errors listed in the manual. Retry occurs. Either message BBMZS134E or BBMZS135I will be issued depending on the success of the retries.User response: A buffer shortage condition can often be caused by a sudden request for a large amount of data. Specifying a MAXMSG value of 4096 will significantly reduce the possibility of this condition. The IBM default is 750 and is much too small for many configurations.

BBMZS134

IXCMSGO macro error, RC=returnCode, RS=reasonCode, total retries=number

Explanation: An error occurred while attempting to retrying this macro, where the indicated return code and reason code. This message shows the total number of retry attempts. The return and reasons codes are documented in the IBM manual MVS Sysplex Services Reference. The most common non-retriable error is RC, 08, Reason, 00000008 - Token invalid. This error often occurs because a CAS is leaving the XCF group and the associate token is invalidate asynchronously. The Sysplex Communication Facility (SPCF) process continues. The conversation associated with this request will be terminated.

User response: This is error could not be corrected. This may not be a problem if there are other messages indicating that another CAS has left the group (BBMZS152). Because sends are processed asynchronously, this error may be reported under these circumstances and can be ignored.

BBMZS135

IXCMSGO macro retry successful, total retries=number

Explanation: This message states the retry attempt was successful and shows the total number of retry attempts. The Sysplex Communication Facility (SPCF) process continues. This is an informational message.

User response: If retry attempts occur frequently during a 24-hour period, contact BMC Support even though the retries ucce are s. Otherwise, no action is required.

BBMZS136

Free SPPI on channel channel for reason reason

Explanation: This XDM message documents the deletion of a pipe instance. The channel number was assigned when the instance was created. The possible reasons are as follows:

User response: No action is required.

BBMZS137

Free storage RC=returnCode for address address

Explanation: The indicated storage could not be automatically freed when the associated SPRE terminated. The storage is not freed.

User response: Take a console dump with SDATA=(RGN,CSA) and provide the dump and CAS log to BMC Support.

BBMZS139

SPCF server error-SPRE process abended

Explanation: An unexpected error has occurred. The request is completed with an error indication.

User response: Provide the dump and CAS log to BMC Customer Support.

BBMZS140

SPCF message router error, RC=returnCode

Explanation: The message router returned a non-zero return code. The internal messages are not processed.

User response: Gather any available documentation and contact BMC Support.

BBMZS141

SPCF group exit error, GERR=groupExitError GEB=groupExitBuffer

Explanation: An error occurred while trying to run the group user exit routine with the indicated Group Exit Error (GERR) and the indicated Group Exit Buffer (GEB). The Sysplex Communication Facility (SPCF) process continues.

User response: Contact BMC Support with the message text.

BBMZS142

SPCF message exit error, MERR=messageExitError MEB=messageExitBuffer

Explanation: An error occurred while trying to run the message user exit routine with the indicated Message Exit Error (MERR) and the indicated Message Exit Buffer (MEB). The Sysplex Communication Facility (SPCF) process continues.

User response: Contact BMC Support with the message text.

BBMZS143

SPCF server - NPWA SBGET ZERR=number

Explanation: An error occurred while trying to use a storage block get (SBGET) service to acquire storage for the Notify Parameter Work Area (NPWA). The ZERR=number value describes the internal failure error that occurred. The number value is an 8-character code that identifies the following information about the rejected request:

• Component
• Module
• Function in process at the time of the failure
• Return code or reason the request was rejected

The Sysplex Communication Facility (SPCF) process continues.User response: Contact BMC Support with the ZERR value.

BBMZS144

SPCF server - XMDISP XDPLACS=error

Explanation: The Sysplex Communication Facility (SPCF) issues a Cross Memory Dispatcher Service (XMDISP) call but the indicated error occurred. SPCF processing continues.

User response: Contact BMC Support with the message text.

BBMZS145

SPCF server status exit error, RC=returnCode, Routcode=routeCode, ExitRC=exitReturnCode, ZERR=number

Explanation: The Sysplex Communication Facility (SPCF) invokes status exits that define SPCF applications. During this process, an error occurred with the indicated return code, the indicated ROUTCODE, and the indicated ZERR number in the message text. The ZERR=number value describes the internal failure error that occurred. The indicated 8-digit routing code that identifies the following information about where the service request was being directed when it failed.

• Product
• Server space
• Component
• Function

The indicated 8-character code identifies the following information about the rejected request:

• Component
• Module
• Function in process at the time of the failure
• Return code or reason the request was rejected

SPCF processing continues.

User response: Contact BMC Support with the message text.

BBMZS146

SPCF server status exit error, RC=returnCode, ExitRC=exitReturnCode

Explanation: The Sysplex Communication Facility (SPCF) invokes status exits that are defined by SPCF applications. During this process, an error occurred with the indicated return code and the indicated exit return code (EXITRC). SPCF processing continues.

User response: Contact BMC Support with the message text.

BBMZS150

A CAS is active in the XCF group; SYSTEM=MVSsystem, JOB=jobName, SSID=ssid, MEMBER=XCFName

Explanation: This is an informational message indicating that a new Coordinating Address Space (CAS) has joined an XCF group and has detected that another CAS is already a member. The existing CAS group member has the indicated XCF member name and the indicated subsystem ID, and resides on the MVS system with the started task name of jobName.

User response: No action is required.

BBMZS151

A CAS has joined the XCF group; SYSTEM=system, JOB=jobName, SSID=ssid, MEMBER=XCFName

Explanation: This is an informational message indicating that the local Coordinating Address Space (CAS), which is already a member of an XCF group, has detected that a new CAS has joined the XCF group. The new CAS group member has the indicated XCF member name and the indicated subsystem ID, and resides on the indicated MVS system with the started task name of jobName.

User response: No action is required.

BBMZS152

A CAS has left the XCF group; SYSTEM=system, JOB=jobName, SSID=ssid, MEMBER=XCFName

Explanation: This is an informational message indicating that a Coordinating Address Space (CAS) has left the XCF group for some reason, such as the system has gone down or the CAS has become inactive. The departing CAS had the indicated XCF group member name and the indicated subsystem ID, and was running on the indicated MVS system with the started task name of jobName.

User response: No action is required.

BBMZS153

SPCF server is disconnecting ASID=XXXX, TCB=TTTTTTTT

Explanation: A task is terminating and all of its SPCF resources are being released. The ASID and TCB are indicated. The TCB address will be all if the address space is terminating or disconnecting.

User response: No action is required.

BBMZS154

XCF status exit ADDR=XXXXXXXX was called by SPCF in JOB=jobName

Explanation: A notify exit was called, where XXXXXXXX is the exit address and jobName is the job name. If a GSI interface was specified, ADDR=XXXXXXXX is replaced by GSI=XXXXXXXX, where XXXXXXXX is the GSI service code.

User response: See message BBMZS155I.

BBMZS155

XCF status exit failed, TCB=TCBaddress, RC=returnCode, RSN=reasonCode

Explanation: The notify exit returned a non-zero return code.

User response: Gather the CAS log and contact BMC Support.

BBMZS157

Create Sppi on channel name for NAME

Explanation: This XDM message indicates the creation of a pipe instance from the user side of the SPCF interface.

User response: No action is required.

BBMZS158

Destroy Spnp on SYSTEM for NAME

Explanation: The named pipe on the user's side of the SPCF interface is destroyed on the indicated system. The name of the pipe is also provided.

User response: No action is required.

BBMZS159

Destroy Spnp failed, Rc=returnCode for NAME

Explanation: The deletion of the named pipe failed where the indicated return code is the return code from the user side of the SPCF interface.

User response: No action is required.

BBMZS160

Destroy Spue in SYSTEM for NAME

Explanation: This XDM message that documents the deletion of a SPCF user. The user was on SYSTEM and running under NAME.

User response: No action is required.

BBMZS161

Destroy Spue failed, Rc=returnCode for SYSTEM

Explanation: This XDM message that documents the failed deletion of a SPCF user on the indicated system.

User response: No action is required.

BBMZS162

Create Spue in ',%1,' for ',%2)

Explanation: This XDM message that documents the creation of a SPCF user on SYSTEM running under NAME.

User response: No action is required.

BBMZS163

Create Spue failed, Rc=',%1, for ',%2

Explanation: This XDM message that documents the failure to delete a SPCF user on SYSTEM.

User response: No action is required.

BBMZS164

MSB_TIMER failed with RC=returnCode and ZERR=ZZZZZZZZ

Explanation: A failure has occurred while attempting to retry an error. The return code and failure reason for MSB_TIMER are given. The retry attempts are bypassed.

User response: Gather the CAS log and contact BMC Support.

BBMZS165

MZZ_WAIT failed with RC=returnCode and ACS=ZZZZZZZZ

Explanation: A failure has occurred while attempting to retry an error. The return code and failure reason for MZZ_WAIT are given. The retry attempts are bypassed.

User response: Gather the CAS log and contact BMC Support.

BBMZS168

IXCSETUS failed with error code=ccccssss

Explanation: An XCF IXCSETUS macro issued to update CAS's user data is failed with return code of cccc and reason code of ssss The user data of this CAS is not updated.

User response: Gather the CAS log and contact BMC Support.

BBMZS169

A CAS's user data is changed; SYSTEM=system, JOB=jobName, SSID=ssid, MEMBER=XCFName

Explanation: This XDM message indicates that a Coordinating Address Space (CAS), which is already a member of an XCF group, has updated its user data. This user data contains the current state information of the CAS.

User response: No action is required.

BBMZS170

CONVXCF=Y/N is in effect now.

Explanation: User has changed the CONVXCF parameter value to Y or N.

• CONVXCF=Y means that XCF path is used for the communications between CASes or address spaces.
• CONVXCF=N means that VTAM is used for the communications between CASes or address spaces.

User response: No action is required.

BBMZS190

SPCF SERVER TERMINATES

Explanation: The Sysplex Communication Facility (SPCF) server stops processing. The SPCF server terminates.

User response: No action is required.

BBMZS191

MVS SYSTEM IS REMOVED FROM SYSPLEX AND SPCF SERVER TERMINATES

Explanation: The Sysplex Communication Facility (SPCF) runs in the current MVS system. After it is removed from the Sysplex Network System, SPCF terminates. The SPCF server terminates.

User response: No action is required.

BBMZS192

SPCF SERVER IS TERMINATED UNEXPECTEDLY

Explanation: An error occurred that caused the Sysplex Communication Facility (SPCF) to terminate. The reason for termination is explained in previous messages. SPCF terminates.

User response: Refer to the previous messages for the reason for termination.