62 Implementing and Managing APPC Protected Conversations
other is in the same state of the last contact. If it is, you can see the message shown in
Example 4-10.
Example 4-10 Syslog for a successful exchange log name between two APPC LUs
ATB207I EXCHANGE LOG NAME PROCESSING HAS COMPLETED SUCCESSFULLY
BETWEEN LOCAL LU USIBMSC.SCSIM8HA AND PARTNER LU
USIBMSC.SCSIM8I$.
LOCAL LOG: ATR.BA04D30D06ADBE08.IBM
PARTNER LOG: ATR.BA04D30D06ADBE08.IBM
ATB207I EXCHANGE LOG NAME PROCESSING HAS COMPLETED SUCCESSFULLY
BETWEEN LOCAL LU USIBMSC.SCSIM8I$ AND PARTNER LU
USIBMSC.SCSIM8HA.
LOCAL LOG: ATR.BA04D30D06ADBE08.IBM
PARTNER LOG: ATR.BA04D30D06ADBE08.IBM
There’s a message for each system owning the LU. If there is a failure, depending on the
reason, you can have one or more of the messages shown in Example 4-11.
Example 4-11 Syslog for unsuccessful exchange log name between APPC LUs
ATB227I LOCAL LU USIBMSC.SCSIM8IA IS WARM STARTING AS A RESOURCE
MANAGER WITH RRS/MVS.
LOCAL LOG: ATR.BA04D30D06ADBE08.IBM
ATB225I LOGICAL UNIT SCSIM8IA IS ACTIVE, BUT WILL REJECT ALL 507
PROTECTED CONVERSATIONS BECAUSE OF A FAILURE RETURN CODE FROM THE
ATRIBRS SERVICE. RETURN CODE IS 00000FFF.
ATB225I LOGICAL UNIT SCSIM8IA IS ACTIVE, BUT WILL REJECT ALL 558
PROTECTED CONVERSATIONS BECAUSE OF A FAILURE RETURN CODE FROM THE
ATRIBRS SERVICE. RETURN CODE IS 00000FFF.
+ATB70042I APPC/MVS cannot schedule allocate request. LU SCSIM8IA
can not process syncpt conversations.
In Example 4-11, the ATB225I message shows an APPC problem encountered during an
RRS call, while ATB70042I is a message that APPC sends only to the TP program. Basically
you can have three level of problems, shown in increasing level of severity:
򐂰 Unit of recovery problems, single or multiple
򐂰 LUs warm/cold or name mismatch problems
򐂰 RRS or Logger problems
4.2.1 Solving unit of recovery problems
This is the lowest severity problem. Some information is available in RRS's logs because of a
missed or failed resynch process after a UOR failure. You have to remove the interest of
APPC for this UOR using the RRS panels. Example 4-12 shows a sample of RRS UORs.
Chapter 4. How to operate in an APPC/MVS Protected Conversations environment 63
Example 4-12 Sample RRS UOR list for an APPC LU and a detail
RRS Unit of Recovery List Row 1 to 3 of 3
Command ===> Scroll ===> CSR
Commands: v-View Details c-Commit b-Backout r-Remove Interest f-View UR Family
S UR Identifier System Logging Group
State Type Comments
BC0AC5E07E6CC00000000006010E0000 SC62 WTSCPLX1
InFlight Prot
BC0AC5E07E6CC37400000008010E0000 SC62 WTSCPLX1
InFlight Prot
BC0AC5E07E6CC6E800000006010E0000 SC62 WTSCPLX1
InFlight Prot
--------------------------------------------------------------------------------
RRS Unit of Recovery Details Row 1 to 2 of 2
Command ===> Scroll ===> CSR
Commands r-Remove Interest v-View URI Details
UR identifier : BC0AC5E07E6CC00000000006010E0000
Create time : 2004/10/29 20:41:28.243319 Comments :
UR state : InFlight UR type : Prot
System : SC62 Logging Group : WTSCPLX1
SURID : N/A
Work Manager Name : IMS.IMSI____V081.STL.SANJOSE.IBM
Display Work IDs / Display IDs formatted
Luwid . : Present
Eid . . : Not Present
Xid . . : Present
Expressions of Interest:
S RM Name Type Role
ATB.USIBMSC.SCSIM8I$.IBM Prot Participant
IMS.IMSI____V081.STL.SANJOSE.IBM Prot Participant
--------------------------------------------------------------------------------
RRS Unit of Recovery Work IDs
UR identifier : BC0AC5E07E6CC00000000006010E0000
More: +
Logical Unit of Work Identifier (LUWID):
USIBMSC.SCSIM8HA C5E06397CB05 0001
NetID.LuName : USIBMSC.SCSIM8HA
TP Instance : C5E06397CB05
SeqNum . . . : 0001
Enterprise Identifier (EID)
TID : (decimal)
GTID :
X/Open Transactions Identifier (XID)
Format ID : 003654612722 (decimal)
D9D4F6F2 (hexadecimal)
GTRID : 00-0F F0F0F2F0 F6F4F1C3 F7C9C2D4 F0F2F0F0 |0020641C7IBM0200|
10-1F F0F0F0F0 F0F1F0C5 C3C210E4 E2C9C2D4 |0000010ECB.USIBM|
20-2F E2C34BE2 C3E2C9D4 F8C8C1C5 E06397CB |SC.SCSIM8HAE\.p.|
30-33 05000100 |.... |
BQUAL : 00-0F E4E2C9C2 D4E2C34B E2C3E2C9 D4F8C8C1 |USIBMSC.SCSIM8HA|
10-1F 00E4E2C9 C2D4E2C3 4BE2C3E2 C9D4F8C9 |.USIBMSC.SCSIM8I|
20-21 5B00 |$. |

Get Implementing and Managing APPC Protected Conversations now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.