BBMZAnnn messages

This section lists the coordinating address space (CAS) server control messages. These messages are issued when starting or stopping the CAS.

BBMZA001I
CAS(casname) SSID(ssid) INITIALIZATION COMPLETE - Rv.r.m (modID)
Explanation:

The coordinating address space (CAS) named casname with a subsystem name of ssid has completed initialization and is ready to accept sessions with other address spaces. The version, release, and modification level of the CAS is shown as Rv.r.m. This software level is contained in the SMP function functional modification identifier (FMID) or PTF level set replacement modification identifier (RMID) shown as modID.

System action:

The CAS processes connections to address space sessions.

User response:

None

BBMZA002A
CAS(casname) SSID(ssid) OPERATOR INTERFACE IS READY
Explanation:

The operator interface for the coordinating address space (CAS) named casname with a subsystem name of ssid is ready to accept operator-entered replies. Currently, END is the only valid response, which, if entered, requests termination of the CAS.

System action:

The CAS waits for an operator reply, while continuing normal processing.

User response:

Reply END when CAS termination is desired.

BBMZA002I
CAS(casname) SSID(ssid) SHUTDOWN ECB ADDRESS = address
Explanation:

The coordinating address space (CAS) named casname with a subsystem name of ssid has initialized with a shutdown event control block (ECB). The address of the ECB is address.

System action:

None.

User response:

None

BBMZA003E
COMMAND NOT RECOGNIZED by CAS(casname) SSID(ssid)
Explanation:

An operator command issued to the coordinating address space (CAS) named casname with a subsystem name of ssid is not valid for the CAS.

System action:

The invalid command is ignored and message BBMZA002A is issued.

User response:

Verify the command syntax and reissue the command.

BBMZA010E
CAS(ssid) INVALID EXEC PARAMETER FIELD FORMAT AT OFFSET offset
Explanation:

During coordinating address space (CAS) initialization, a syntax error was detected in the parameter string passed to service module BBM9ZA00. The decimal offset relative to 0 from the beginning of the parameter string where the error was detected is shown as offset. The parameter string is located in the CAS PROC JCL, where one or more of the parameter fields contains a format error. The CAS that was attempting to initialize has a subsystem ID of ssid.

System action:

The CAS does not initialize.

User response:

Correct the CAS PROC JCL parameter string for the CAS with a subsystem ID of ssid and restart the CAS.

BBMZA011E
CAS(ssid) UNDEFINED EXEC PARM KEYWORD AT OFFSET offset
Explanation:

During coordinating address space (CAS) initialization, an invalid keyword defined in the PARM= parameter of the CAS PROC's EXEC statement was detected. The decimal offset of the error relative to 0 from the beginning of the EXEC statement is shown as offset. The CAS that was attempting to initialize has a subsystem ID of ssid.

System action:

The CAS does not initialize.

User response:

Correct the invalid EXEC statement keyword in the CAS PROC JCL for the CAS with a subsystem ID of ssid and restart the CAS.

BBMZA012E
CAS(ssid) ’keyword’ VALUE IS TOO LONG|SHORT
Explanation:

During initialization of the coordinating address space (CAS) with a subsystem ID of ssid, an invalid value defined to the keyword keyword in the CAS PROC's EXEC statement was detected. The reason the keyword value is invalid is shown in the message as one of the following:

LONG
Too many characters defined to the keyword.
SHORT
Not enough characters defined to the keyword.
System action:

The CAS does not initialize.

User response:

Correct the value defined to the EXEC statement keyword in the CAS PROC JCL for the CAS with a subsystem ID of ssid and restart the CAS.

BBMZA071E
MODULE=csect OFFSET=offset ABEND CODE=tnnnn|GSI Failure (ROUT=route)
Explanation:

This message issues with messages BBMZA072E and BBMZA073E to provide snap dump information about a failing coordinating address space (CAS) initialization function. This message also issues with message BBMZA080E. This message either displays as MODULE=csect OFFSET=offset   ABEND CODE=tnnnn or as GSI Failure (ROUT=route).

If the text displays as MODULE=csect OFFSET=offset ABEND CODE=tnnnn, the CSECT name, csect, and offset information, offset, for the failing initialization module, and abend code that was returned due to the failure are provided. The offset value is the offset from the start of the failing module where the abend occurred. If the offset cannot be determined, this value appears as ****.

The abend code is either Snnnn or Unnnn, where:

S
Indicates an MVS™ component issued the abend code.
U
Indicates a user or vendor process could not continue so the product or user code invoked its own ABEND macro.
nnnn
Is the abend code value.

If the text displays as GSI Failure (ROUT=route), the abend occurred during a general services interface (GSI) call function, and the route value is an 8-digit routing code that identifies the following information about where the GSI call was being directed when it failed:

System action:

CAS initialization is terminated and additional messages are issued by the CAS.

User response:

See messages BBMZA072E and BBMZA073E, which contain further snap dump information.

BBMZA072E
PSW=PSword WHERE IC=code/IL=il
Explanation:

This message issues with messages BBMZA071E and BBMZA073E to provide snap dump information about a failing coordinating address space (CAS) initialization function. This message also issues with message BBMZA080E. This message provides information related to storage when the initialization failure occurred.

The program status word (PSW) is the area in storage containing the order in which program instructions were processing when the failure occurred. The active PSW area for the initialization function is PSword. The length, in decimal, of the instruction that failed is il. The hexadecimal interrupt code at completion of the last instruction executed before the abend condition was signaled is code.

System action:

CAS initialization is terminated and additional messages are issued by the CAS.

User response:

See messages BBMZA071E and BBMZA073E, which contain further snap dump information.

BBMZA073E
ERR|RB REGS nn-nn: reg1 reg2 reg3 reg4
Explanation:

This message issues with messages BBMZA071E and BBMZA072E to provide snap dump information about a failing coordinating address space (CAS) initialization function. This message also issues with message BBMZA080E. The ERR registers are always displayed; the RB registers are displayed only if they are different from the ERR register contents.

The nn-nn values are the starting and ending register numbers and are always:

The reg1 through reg4 values are the 8-digit hexadecimal general registers.

System action:

CAS initialization is terminated.

User response:

See messages BBMZA071E and BBMZA072E, which contain further snap dump information and contact your IBM® Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBMZA080E
SYSTEM CONTROL TASK INITIALIZATION ESTAE EXIT ENTERED
Explanation:

The coordinating address space (CAS) initialization controller ESTAE exit has been entered to recover an abend condition encountered during CAS initialization.

System action:

The CAS establishes an ESTAE and terminates initialization.

User response:

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

BBMZA082E
SYSTEM CONTROL TASK RECOVERY COMPLETE (retry action)
Explanation:

This message is a continuation of message BBMZA080E. The coordinating address space (CAS) initialization controller ESTAE exit has completed its problem analysis and one of the following retry action values indicates the action that was taken:

SCHEDULED
The controller ESTAE exit schedules a special termination procedure to recover any global resources prior to terminating the CAS.
PROHIBITED
The controller ESTAE exit could not schedule its special termination procedure because it is prohibited from doing so by the MVS Recovery/Termination Manager. This is usually the result of issuing an MVS CANCEL operator command to cancel the CAS prior to completion of CAS initialization. Depending on the location of the error, some global storage resources may be lost until the next system IPL. It may be necessary to specify COLD=Y on a subsequent CAS restart.
NO RETRY
The controller ESTAE exit did not attempt to schedule its special termination procedure. The controller has determined that its execution environment has been corrupted and it is therefore unsafe to attempt a normal termination. Depending on the location of the error, some global storage resources may be lost until the next system IPL. It may be necessary to specify COLD=Y on a subsequent CAS restart.
System action:

CAS initialization is terminated.

User response:

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

BBMZA083E
CAS(ssid) SBGET FAILED (Block=block, ZERR=n)
Explanation:

A storage block get (SBGET) function failed when attempting to secure storage for a block named block. The n value is an 8-character code that identifies the following information from the system storage manager, which rejected the SBGET request:

System action:

CAS initialization fails.

User response:

Increase the CAS region size and ensure that the active IEASYSxx SYS1.PARMLIB member specifies a large enough CSA and/or extended CSA area, then restart the CAS. If the problem persists, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBMZA084E
CAS(ssid) PGLOAD failed (ZERR=n PSBNAME=module)
Explanation:

An attempt to load a server control program module named module failed during initialization of the coordinating address space (CAS) with a subsystem name of ssid. The n value is an 8-character code that identifies the following information from the PGLOAD function, which rejected the SBGET request:

System action:

CAS initialization fails.

User response:

Increase the CAS region size and ensure that the active IEASYSxx SYS1.PARMLIB member specifies a large enough CSA and/or extended CSA area, then restart the CAS. If the problem persists, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

Start of change
BBMZA085W
CAS(ssid) PREVIOUS CAS FAILED TO TERMINATE CORRECTLY AUTOMATIC COLD START SELECTED
Explanation:

The previous Coordinating Address Space (CAS) instance terminated abnormally before initializing the Global Recovery Manager. The new CAS instance is automatically forced to perform a COLD start to ensure that the Global Recovery Man- ager is initialized properly.

System action:

CAS initialization continues. Some common storage may be orphaned until the next IPL. The amount depends upon how far initialization has proceeded when the previous CAS instance terminated.

User response:

None. If initialization of the CAS continues to terminate abnormally, contact your IBM Support Center with any of the diagnostic information that is available from the list shown in Diagnostic information for BB messages.

End of change
BBMZA089U
SYSTEM CONTROL TASK RECOVERY COMPLETE (NO SDWA - RETRY IMPOSSIBLE)
Explanation:

The coordinating address space (CAS) initialization controller ESTAE exit is in control and has determined that a retry is not possible because the MVS Recovery/Termination Manager (RTM) did not provide a System Diagnostic Work Area (SDWA).

System action:

Recovery is not attempted and CAS initialization fails.

User response:

Increase the address space's region size to prevent this situation from occurring in the future. Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBMZA090E
CAS(ssid) SSID VERIFICATION FAILED (IEFSSREQ RC=X’xxxx’)
Explanation:

During initialization, the coordinating address space (CAS), with a subsystem ID of ssid, issued an IEFSSREQ (VS) call to the MSTR subsystem to determine if the CAS was previously defined to the system. The MSTR subsystem rejected the IEFSSREQ call with a hexadecimal subsystem router return code of X'xxxx'. The problem is in either the MSTR subsystem or in the IEFSSREQ macro that issues the IEFSSREQ (VS) call.

System action:

CAS initialization fails.

User response:

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

BBMZA091E
CAS(ssid) SSID ALREADY IN USE (SSCT=address, SSCTSUSE=field)
Explanation:

Another subsystem or application already is using the name ssid and the coordinating address space (CAS) attempted to initialize using this name. The address of the subsystem control vector table (SSCT) for the subsystem or application using the name ssid is address. The field value shows the contents of the SSCTSUSE field, which is a field in the SSCT that is used by the subsystem or application to point to another area in the system, such as a major control block.

System action:

CAS initialization fails.

User response:

Update the CAS JCL set EXEC PARM information to specify a subsystem name which is not being used by any IBM, vendor, or installation-developed subsystem and restart the CAS. If the problem persists, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBMZA092E
CAS(ssid) SSID CONTENTION DETECTED (SSCT=address, SSCTSUSE=field)
Explanation:

During a warm start initialization, the coordinating address space (CAS) with a subsystem ID of ssid looks for an subsystem control vector table (SSCT) by the name of ssid. The CAS found an SSCT by the name of ssid located at address and determined that another address space updated the contents of the SSCTSUSE field, which is field. (The SSCTSUSE is a field in the SSCT that is used by a subsystem or application to point to another area in the system, such as a major control block.)

A warm start initialization for the CAS is the default. This situation can occur if the START command is issued twice in a row for a single CAS--the CAS initialization processing for the second command would find the SSCT contents already updated because of the initialization processing from the first command.

System action:

CAS initialization fails (for the second command, if the START command was entered twice).

User response:

Ensure that the CAS was not accidentally started more than once. If so, no further action is require. If not, use the MVS DUMP operator command to take a dump of the MASTER address space (ASID=0001) and contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBMZA093E
CAS(ssid) SUBSYSTEM NOT DORMANT (CSCA=address, CSCAFLGS=field)
Explanation:

During initialization, the coordinating address space (CAS) determined that the subsystem ID of ssid is currently or was previously being used by another CAS. The active or formerly active CAS has a main CAS control structure (CSCA) address of address. The field value shows the contents of the CSCAFLGS field in the CSCA.

Note:
This error can occur if COLD=Y is specified in the START command. COLD=Y should be specified only at the request of IBM customer support personnel.
System action:

If COLD=Y was specified in the START command, this message is immediately followed by message BBMZA094A; otherwise, CAS initialization is terminated.

User response:

If the active CAS can be identified, do one of the following:

If the active CAS cannot be identified, restart the CAS specifying COLD=Y in the START command and respond Y to message BBMZA094A.

BBMZA094A
CAS(ssid) REPLY ’Y’ TO CONFIRM COLD START OR ’N’ TO TERMINATE
Explanation:

During cold start initialization, the coordinating address space (CAS) determined that the subsystem ID of ssid was currently or previously used by another CAS.

Note:
Cold start initialization should be used only at the request of IBM customer support personnel.
System action:

CAS initialization waits for an operator response.

User response:

Reply N to terminate CAS initialization; reply Y to refresh the subsystem and continue initialization.

Note:
Common storage space may be lost until the next system IPL if initialization is allowed to continue.
BBMZA094E
CAS(ssid) INVALID REPLY
Explanation:

A reply other than Y or N was received in response to message BBMZA094A. The ssid is the subsystem name of the coordinating address space (CAS).

System action:

CAS initialization waits for a valid operator response.

User response:

Reply either Y or N.

BBMZA095E
CAS(userid)USER AUTHORIZATION TO INITIALIZE FAILED
Explanation:

This message is issued to the operator's console. The coordinating address space (CAS) user authorization for the specified user ID failed. The user ID is not authorized to start the task, where:

userid
Is the LOGONID, ACID, or USERID associated with the task in the external security manager (ESM).
System action:

CAS initialization terminates.

User response:

Notify your security administrator.

BBMZA096E
CAS(ssid) CURRENT CAS RELEASE AND CONNECTING RELEASE DO NOT MATCH
Explanation:

The CICSPlex® SM product release level executing in the coordinating address space (CAS) does not match the product release level executing in the connecting address space. This message is always accompanied by BBMZA096I and BBMZA097E or BBMZA098E.

System action:

If the message is issued during CAS initialization, message BBMZA098I is also issued and the CAS is cold started.

If the message issued during connect processing, message BBMZA097E is also issued.

User response:

Make sure the CICSPlex SM libraries being allocated by the connecting address space are the same as those being allocated by the CAS address space. Refer to accompanying messages for additional actions.

BBMZA096I
CAS(ssid) LAST STARTED FROM bbbnnnn LEVEL
Explanation:

A component detected that the maintenance level of the coordinating address space (CAS) libraries has changed since the last time the CAS was last executed.

System action:

Refer to accompanying messages to determine the system's response.

User response:

Make sure the CICSPlex SM libraries being allocated by the connecting address space are the same as those being allocated by the CAS address space. Refer to accompanying messages for additional actions.

BBMZA096W
CAS(ssid) NEW MAINTENANCE LEVEL xxxyyy DETECTED
Explanation:

A component detected that the maintenance level of the coordinating address space (CAS) libraries has been changed in a way that necessitates a cold start for correct operation (for example, a new release or a major functional change). PTF xxxyyy introduced this change. This message is always accompanied by BBMZA097E or BBMZA098I.

System action:

If the message is issued during CAS initialization, message BBMZA098I is issued and initialization continues.

If the message is issued during connect processing, either during CMAS initialization or while connecting to the CAS from a TSO session, message BBMZA097E is issued and the connect request is rejected.

User response:

Refer to the message description for either message BBMZA097E or message BBMZA098I.

BBMZA097E
CAS(ssid) MUST BE RESTARTED BEFORE IT CAN ACCEPT NEW CONNECT REQUESTS
Explanation:

This message is always preceded by BBMZA096W and is issued by the connect function when it detects that the maintenance level of the coordinating address space (CAS) has been changed in a way that necessitates a cold start for correct operation.

System action:

The connect request is rejected.

User response:

Stop and then restart the CAS. During the restart process, the CAS will detect the new maintenance level indicated by message BBMZA096W and will perform a cold start automatically.

The CMAS should also be stopped and restarted to ensure correct operation. Failure to restart the CMAS may result in errors in the CMAS, the TSO session, or the CAS that may require that the CAS be recycled again to restore normal operation.

BBMZA098E
MVS SYSTEM IS BELOW REQUIRED RELEASE LEVEL. THE CAS CANNOT BE INITIALIZED.
Explanation:

For successful initialization of a coordinating address space (CAS), the MVS system must be at the required release level of MVS.

System action:

The CAS terminates.

User response:

Refer to the CICSPlex SM Program Directory for the MVS release level requirements.

BBMZA098I
CAS(ssid) AUTOMATIC COLD START IN PROGRESS for xxxyyy
Explanation:

This message is always preceded by BBMZA096W and is issued during coordinating address space (CAS) initialization when the CAS detects that the maintenance level of its libraries has been changed in a way that necessitates a cold start for correct operation.

System action:

The system automatically performs a cold start.

User response:

None.

BBMZA099E
CAS SUBSYSTEM DEFINITION FAILED
Explanation:

During initialization, the coordinating address space (CAS) initialization controller failed when it attempted to dynamically define the CAS subsystem. The initialization controller failed because the coordinating address space (CAS) subsystem is not defined in the active IEFSSNxx member of SYS1.PARMLIB.

System action:

CAS initialization fails.

User response:

Review the system log (SYSLOG) for previously issued messages providing the reason for the subsystem definition failure. Correct the problem(s) by following the action instructions for the issued error messages and restart the CAS. If the problem persists, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBMZA100I
CONVXCF=Y REQUIRES SPCF=Y; CONVXCF=Y IGNORED BECAUSE SPCF=N WAS SPECIFIED.
Explanation:

The CAS startup parameters specified or defaulted to CONVXCF=Y and SPCF=N. If CONVXCF=Y is specified, SPCF=Y must also be specified.

System action:

The CAS continues to initialize as if CONVXCF=N had been specified. XCF conversations will not be allocated for CAS-to-CAS connections.

User response:

None required. To avoid this message, specify compatible values for the CONVXCF and SPCF parameters. If XCF conversations are desired between CASes, specify CONVXCF=Y and SPCF=Y.

BBMZA800W
CAS(ssid) CONNECT INTERFACE DISABLED (IVP MODE REQUESTED)
Explanation:

The coordinating address space (CAS) with a subsystem ID of ssid has been initiated as a non-APF authorized task. The EXEC statement in the CAS PROC contains the parameter IVP=Y. This parameter causes the CAS to be started only to verify proper product installation. Other address spaces cannot request a session with the CAS when the IVP=Y parameter is defined at initialization.

System action:

The CAS initializes, but no address spaces can connect to it.

User response:

If you wanted only to validate proper installation, check the CAS job log for any error messages.

If you want other address spaces to connect to the CAS, remove the IVP=Y parameter from the CAS PROC JCL and restart the CAS.

BBMZA900I
CAS(casname) SSID(ssid) SHUTDOWN IN PROGRESS
Explanation:

The coordinating address space (CAS) named casname with a subsystem ID of ssid is terminating in response to either an MVS operator STOP (P) command directed to the CAS or a CAS WTOR END command specified in response to message BBMZA002A.

System action:

Normal termination processing continues.

User response:

None

BBMZA993W
CAS(ssid) ERROR OCCURRED IN DISCONNECTING USER userid, TERMINATION CONTINUES
Explanation:

The coordinating address space (CAS) with a subsystem ID of ssid was in the process of shutting down due to an operator-issued MVS STOP or CANCEL command. While shutting down, an unknown error occurred when the CAS was disconnecting the user session with a user ID of userid.

System action:

The CAS continues terminating and the user session may hang or encounter other unexpected error conditions.

User response:

None.

BBMZA994W
CAS(ssid) WAITING FOR SESSION DISCONNECT(S)
Explanation:

coordinating address space (CAS) termination has been requested for the CAS with a subsystem ID of ssid. One or more sessions connected to the CAS are currently active. The CAS is in the process of disconnecting the active sessions; this operation may require up to one minute to complete. If all sessions are not disconnected within one minute, message BBMZA995A is issued.

System action:

Message BBMZA996I is issued.

User response:

Look for additional messages.

BBMZA995A
CAS(ssid) REPLY ’U’ TO WAIT OR ’C’ TO CONTINUE TERMINATION
Explanation:

During termination, the coordinating address space (CAS) with a subsystem ID of ssid has waited one minute for disconnect processing of all remaining sessions to complete, but one or more sessions still remain connected to the CAS.

System action:

CAS termination waits for an operator response before continuing.

User response:

Do one of the following:

Reply U
Disconnect processing occurs again for an additional one-minute period.
Note:
You can reply U repeatedly until this message is no longer issued and normal disconnect processing has occurred for all sessions. You should reply U for this message as many times as necessary.
Reply C
If immediate CAS termination is required; all remaining sessions are instantly cancelled without normal disconnect processing.
Note:
If C is replied in response to this message, existing sessions might experience subsequent S0C4 or S202 abends or other unpredictable errors.
BBMZA996I
CAS(ssid) ACTIVE SESSIONS WITH session1...sessionx
Explanation:

This message is always issued with message BBMZA994W. This message supplies additional information about the remaining sessions connected to the coordinating address space (CAS).

During termination processing for the CAS with a subsystem of ssid, one or more sessions connected to the CAS are still active. The address spaces for the active sessions are listed as values session1 through sessionx in the message. One address is listed for each active session.

System action:

The CAS is in the process of disconnecting the active sessions and continues this function for one minute.

User response:

None.

BBMZA998U
CAS(ssid) INITIALIZATION FAILED (reason text)
Explanation:

Initialization has failed for the coordinating address space (CAS) with a subsystem ID of ssid. The reason text value indicates a reason for the initialization failure and is one of the following:

CONTROL TASK NOT APF AUTHORIZED
Indicates that the CAS was initiated as a non-APF authorized task, but IVP=Y is not defined to the CAS PROC JCL.

System Action: The CAS does not initialize.

User Response: Do one of the following:

  • Update the CAS PROC JCL EXEC statement to include the parameter IVP=Y and restart the CAS.
  • Execute the CAS initialization program BBM9ZA00 out of an APF-authorized library.
BBLINK NOT APF AUTHORIZED
Indicates that the CAS server task library (BBLINK) was allocated to a non-APF authorized library, but the CAS was initiated as an APF-authorized task.

System Action: The CAS does not initialize.

User Response: Do one of the following:

  • Update the appropriate IEAAPFxx SYS1.PARMLIB member to authorize the BBILINK specified server task libraries.
  • Remove the BBILINK DD statement from the CAS PROC JCL and ensure that all required server programs reside in an APF-authorized JOBLIB or STEPLIB, or system linklist library.
IVP MODE ERROR - AUTHORIZED TASK
Indicates that the CAS was initiated as an APF-authorized task, but IVP=Y is defined to the CAS PROC JCL.

System Action: The CAS does not initialize.

User Response: Do one of the following:

  • Execute the CAS initialization program BBM9ZA00 out of a non-APF authorized library.
  • Remove the IVP=Y parameter from the CAS PROC JCL EXEC statement and restart the CAS.
IVP MODE ERROR - AUTHORIZED BBLINK
Indicates that the CAS PROC JCL specifies the IVP=Y parameter, but it also contains a BBILINK DD statement that allocates an APF-authorized server program library.

System Action: The CAS does not initialize.

User Response: Do one of the following:

  • Remove the BBILINK DD statement from the CAS PROC JCL and restart the CAS.
  • Remove the BBILINK data set(s) from the appropriate SYS1.PARMLIB IEAAPFxx member and restart the CAS.
  • Add a non-APF authorized library to the BBILINK library concatenation.
BBMZA998W
CAS(ssid) EMERGENCY SHUTDOWN IN PROGRESS, NOW NOTIFYING CONNECTED ADDRESS SPACES
Explanation:

The coordinating address space (CAS) is terminating abnormally and it has one or more address spaces connected to it.

System action:

The CAS attempts to notify the connected address spaces to disconnect. Additional related messages may be issued during emergency shutdown. See messages BBMZA999W and BBMZA99EA for additional information.

User response:

None.

BBMZA999I
CAS(ssid) SHUTDOWN COMPLETE - CC=nn
Explanation:

The coordinating address space (CAS) with a subsystem ID of ssid has terminated with a completion code of nn. The completion code is a decimal value returned by the terminated CAS. See Completion code values for information about the code value.

System action:

None.

User response:

None.

BBMZA999W
CAS(ssid) SEVERE ERRORS MAY OCCUR IF SESSIONS ARE NOT GIVEN TIME TO DISCONNECT
Explanation:

The coordinating address space (CAS) is terminating and it has one or more address spaces connected to it. This message indicates to the system operator that the CAS is in the process of disconnecting connected address spaces.

Severe errors (abends) may occur in the CAS or in the connected address spaces if the CAS is cancelled or forced before active address space connections are terminated. Abends may occur subsequently in the connected address spaces, even after the CAS has terminated.

System action:

The CAS notifies connected address spaces that they must disconnect from the CAS. Additional messages may be issued in conjunction with this message.

User response:

Allow time for address space connections to be terminated.

[[ Contents Previous Page | Next Page Index ]]