What to do Upon Receiving an EBCXST32 Message
Article ID: 29821
Updated On:
Products
Issue/Introduction
The XMS (cross-memory services) message EBCXST32 appears as:
EBCXST32 DATABASE INDEX NAME NOT FOUND FOR TRANSACTION - SESSION ENDED
TRAN="xxxx"
its appearance indicates that an entry for the transaction specified, located in an EBCXMCTR table, does not point to a valid CA View database.
An EBCXMCTR table sample entry is:
EBCXMTRN TYPE=xxx,TRANID=xxxx,INDEX=db_hlq
where: TYPE is SAR for a View database, EXP for a Deliver database
TRANID is a 4-character transaction ID
db_hlq is the corresponding database high-level qualifier
Generalities on setting up the EBCXMCTR table:
. The ExxXMCTR table should be properly updated/assembled for each release.
. The library containing the table should either be in the Linklist or be STEPLIBed to.
Specifics if doing an upgrade:
. Ensure that the name of the XMS program to be executed is in line with the new release:
//XMS EXEC PGM=EC0DRV View/Deliver 12.0
//XMS EXEC PGM=EC1DRV View/Deliver 12.1
//XMS EXEC PGM=EC2DRV View/Deliver 12.2
. Each release has its own SUBSYS value:
SUBSYS=XMC0 View/Deliver 12.0
SUBSYS=XMC1 View/Deliver 12.1
SUBSYS=XMC2 View/Deliver 12.2
Situations:
- If preceded by message EBCDBL01:
EBCDBL01 SAR DATABASE SAR.SYSTEM1 RESET 00 AVAILABLE
where a generic database name is specified, the XMS task does not include the proper database HLQ.
To resolve the problem:
. Adjust the libraries and definitions, so that proper databases are being referenced.
- If accompanied by message EBCXMC03:
EBCXMC03 ExxXSTSK NOT ACTIVE
The ExxXSTSK program is not executing. ExxXMCIC requires the ExxXSTSK to work, so ExxXMCIC ends indicating the task is not active.
ExxCINIT, which starts the subtask, was not executing, or the subtask was stopped.
To resolve the problem:
. Have the CICS staff check to see if the CICS RPL definitions are properly updated to point to the new View libraries.
If the CICS definitions need updated, please recycle CICS to enact the change.
- If accompanied by message EBCXMC90:
EBCXMC90 RELEASE DEPENDENT PROGRAM NOT FOUND
The ExxXMCIC application program has abended.
To resolve the problem:
. Configure and assemble the EBCXMCTR table.
. Put a STEPLIB in the corresponding XMS task.
. Refresh LLA
. Recycle CICS
- If accompanied by informational message EBCCIN06:
EBCCIN06 EBCXSTSK ALREADY ACTIVE, CONTROL TABLE (ExxXMCTR) RELOADED
The subtask is active when ExxCINIT was executed. The control table was reloaded and no other changes were made. Some XMS initialization options
(MAXUSER, MSGLVL) are ignored.
- The EBCXST32 message can appear because the wrong execution library is being accessed:
Below are other possible solutions:
. The CICS region could be picking up an older CA View execution library (CAILIB or CVDELOAD) from the Linklist.
To solve the problem:
. STEPLIB to the correct View library, which contains the assembled EBCXMCTR table.
Add the proper CA View library to the CICS task.
. There could be a CA Deliver execution library (CAILIB or CVDELOAD), located in the Linklist ahead of a CA View execution library (CAILIB or
CVDELOAD), that contains a default EBCXMCTR table which would contain generic TRANsaction IDs and database references.
To solve the problem:
. Move the CA View library ahead of the Deliver library.
. Though the View execution library (CAILIB or CVDELOAD) is in the Linklist, there could be another library residing higher in the Linklist that
contains a different copy of an assembled the EBCXMCTR.
To solve the problem:
. Move the proper CA View library ahead of the library with the other EBCXMCTR.
Environment
Component:
Feedback
