![[z/OS]](../images/ngzos.svg)
Monitoring transactions imported from WebSphere Application Server to CICS
About this task
When a request is made from a WebSphere® Application Server component that is running in a global transaction to a CICS® link server that is started with the TXN=Y parameter, the global transaction is propagated to CICS.
A new branch of the transaction is created by CICS, with WebSphere acting as the coordinator and CICS as the subordinate. The overall representation of the transaction branch is defined by CICS as a unit of work (UOW) and representation of the coordinator is defined by CICS as a unit of work link (UOWLINK).
The CICS link server marks the UOWLINK so that it can be distinguished from other UOWLINKS on the system and traced back to the originating WebSphere server, and the optimized local adapter registration that is used to create the branch.
The following fields are set in the UOWLINK:
- Role
Set to coordinator since WebSphere is coordinating the outcome of the overall UOW.
- Type
Set to IIOP. The IIOP coordinator and resource model best represent the relationship between the WebSphere coordinator and the CICS subordinate.
- HostSet to a string that describes the coordinating WebSphere server. The string syntax is as follows:
where DGN is daemon group name, NDN is node short name, and SVN is the server short name of the WebSphere Application Server that is coordinating the transaction. RGN is the register name of the link server that is used to create the transaction branch.WOLA:<DGN>/<NDN>/<SVN>:<RGN>In the following example, a value of:
indicates that the WebSphere server, BBOS001, in node SY1 and daemon group SY1, initiated the transaction and was imported into CICS using the link server, MYLINKSERVER.WOLA:SY1/SY1/BBOS001:MYLINKSERVER
You can monitor the status of these CICS subordinate branches using the EXEC CICS INQUIRE UOW and EXEC CICS INQUIRE UOWLINK APIs from within a CICS program.
The CICS-supplied CEMT transaction uses these APIs to display the UOWs that are currently known
to CICS. You can inquire about a particular UOW if an error
has occurred during sync point processing. An example of this situation is if the task running the
CICS UOW abends while the global transaction is
in-doubt or between phase 1 and 2 of the two-phase commit. An example output of the CEMT
INQUIRE UOW transaction is as
follows:
| INQUIRE UOW |
| STATUS: RESULTS - OVERTYPE TO MODIFY |
| Uow(C5B2837D664B4D25) Inf Act Tra(CSOL) Tas(0000003) |
| Age(00000373) Use(CICSUSER) |
| Uow(C5B2837DCB24B56B) Inf Act Tra(CSSY) Tas(0000005) |
| Age(00000373) Use(CICSUSER) |
| Uow(C5B2837DCB2B046B) Inf Act Tra(CSSY) Tas(0000006) |
| Age(00000373) Use(CICSUSER) |
| Uow(C5B2837DDE3D9C96) Inf Act Tra(CSTP) Tas(0000008) |
| Age(00000373) Use(CICSUSER) |
| Uow(C5B28380EF477F93) Inf Act Tra(CSHQ) Tas(0000020) |
| Age(00000370) Use(CICSUSER) |
| Uow(C5B2839DD76D01D5) Inf Act Tra(CSNE) Tas(0000021) |
| Age(00000339) Use(CICSUSER) |
| Uow(C5B284C7C4C9535B) Inf Act Tra(OLAT) Tas(0000043) |
| Age(00000027) Ter(L320) Netn(L320 ) Use(CICSUSER) |
| Uow(C5B284C7C81DB991) Inf Act Tra(BBO$) Tas(0000044) |
| Age(00000027) Use(CICSUSER) |
|+ Uow(C5B284C82EAF3BE0) Ind Shu Tra(BBO#) Tas(0000047) |
| Age(00000026) Use(CICSUSER) |
| |
| SYSID=CICS APPLID=CICSHTH3 |
| RESPONSE: NORMAL TIME: 14.13.08 DATE: 03.18.10 |
|PF 1 HELP 3 END 5 VAR 7 SBH 8 SFH 9 MSG 10 SB 11 SF| INQUIRE UOW |
| RESULT - OVERTYPE TO MODIFY |
| Uow(C5B284C82EAF3BE0) |
| Uowstate( Indoubt ) |
| Waitstate(Shunted) |
| Transid(BBO#) |
| Taskid(0000047) |
| Age(00000047) |
| Termid() |
| Netname() |
| Userid(CICSUSER) |
| Waitcause() |
| Link() |
| Sysid() |
| Netuowid(..MCLNT2L.CICSHTH3.dH......) |
| Otstid(.......O.b...... .Ep6E3.S....m.............O.b...... .Ep6E3.S....) |
| Otstid(m..........................) |
| |
| |
| |
| |
| SYSID=CICS APPLID=CICSHTH3 |
| TIME: 14.13.28 DATE: 03.18.10 |
|PF 1 HELP 2 HEX 3 END 5 VAR 7 SBH 8 SFH 10 SB 11 SF Attention: The Transid is BBO#, which is the default transaction ID for the CICS link task. To determine why the UOW remains in-doubt, you can
examine the UOWLINK objects for this UOW to see if a coordinator is present. The following example
is the output for CEMT INQUIRE
UOWLINK:
For
UOW C5B284C82EAF3BE0, there is one UOWLINK. It is an IIOP type link that is represented by the
abbreviation "Iio", and it is an OTS Coordinator link that is represented by the abbreviation "Coo
Ots". Place the cursor over the UOWLINK and click enter to show details for this UOWLINK as
follows:| INQUIRE UOWLINK |
| STATUS: RESULTS - OVERTYPE TO MODIFY |
| Uowl(01020001) Uow(C5B284C7C4C9535B) Rmi Lin(BBOATRUE) |
| Unk Net(..MCLNT2L.L320.dGDI........) |
| Uowl(01030001) Uow(C5B284C7C81DB991) Rmi Lin(BBOATRUE) |
| Unk Net(..MCLNT2L.CICSHTH3.dGH.....) |
| Uowl(01010003) Uow(C5B284C82EAF3BE0) Rmi Lin(BBOATRUE) |
| Sub Net(..MCLNT2L.CICSHTH3.dH......) |
| Uowl(01040001) Uow(C5B284C82EAF3BE0) Iio |
| Coo Ots Net(..MCLNT2L.CICSHTH3.dH......) |
| Uowl(01000002) Uow(C5B284E2AEAA9951) Rmi Lin(BBOATRUE) |
| Unk Net(..MCLNT2L.CICSHTH3.dS..r...) |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| SYSID=CICS APPLID=CICSHTH3 |
| RESPONSE: NORMAL TIME: 14.13.38 DATE: 03.18.10 |
|PF 1 HELP 3 END 5 VAR 7 SBH 8 SFH 9 MSG 10 SB 11 SF ||
| INQUIRE UOWLINK |
| RESULT - OVERTYPE TO MODIFY NOT FOUND |
| Uowlink(01040001) |
| Uow(C3F5C2F2F8F4C3F8) |
| Type(Iiop) |
| Link() |
| Action( ) |
| Role(Coordinator) |
| Protocol(Ots) |
| Resyncstatus() |
| Sysid() |
| Rmiqfy() |
| Netuowid(..MCLNT2L.CICSHTH3.dH......) |
| Urid() |
| Host(WOLA:PLEX1/SY1/BBOS001:OLASERVER) |
| |
| |
| |
| |
| |
| |
| SYSID=CICS APPLID=CICSHTH3 |
| TIME: 14.13.46 DATE: 03.18.10 |
|PF 1 HELP 2 HEX 3 END 5 VAR 7 SBH 8 SFH 10 SB 11 SF |Attention: On this screen, the Uow() field has been converted from EBCDIC text to its
hexadecimal representation, so it does not match the previous screen, for exaample, C3=C, F5=5, and
C2=B. The host representing the coordinator is WOLA:PLEX1/SY1/BBOS001:OLASERVER. This indicates that
the coordinator is WOLA, or WebSphere Optimized Local
Adapters. The server we are connected to is BBOS001, in node SY1 of daemon group PLEX1. The name of
the registration used to create this transaction branch is OLASERVER. This UOW must wait for server
BBOS001 to deliver the outcome for this UOW.
For more information on the CEMT transaction,
see the topic, CEMT INQUIRE commands, in the CICS Transaction
Server for z/OS®, Version 4.1 documentation. For more
information about the EXEC CICS INQUIRE UOW and EXEC CICS
INQUIRE UOWLINK API commands, see the topic, System Commands, in the CICS Transaction Server for z/OS,
Version 4.1 documentation