Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!brutus.cs.uiuc.edu!usc!ucsd!ucbvax!binky.UUCP!dukew
From: dukew@binky.UUCP (Wayne Duquaine)
Newsgroups: comp.protocols.ibm
Subject: Re: LU 6.2 Questions
Message-ID: <8911220224.AA10602@lilac.berkeley.edu>
Date: 21 Nov 89 22:05:34 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: Wayne Duquaine <mtxinu!sybase!binky!dukew@ucbvax.Berkeley.EDU>
Organization: The Internet
Lines: 27

(1) SYNCPT and BACKOUT were also implemented on the S/38 I believe, in
    addition to CICS.

(2) Any other vendor implemented SYNCPT and BACKOUT ? - I think
    CULLINET SOFTWARE's UCF tp monitor may have also implemented these
    as part of it LU 6.2 support.  It runs on S/370 mainframes.

(3) SYNCPT and BACKOUT were not carried forward in SAA CPIC ? - sad
    but true, and I regard this as a major screwup by IBM. I heard
    part of the problem was due to inter-product fights while CPIC
    was being designed.  I've heard rumors that an officially blessed
    version of SAA CPIC SYNCPT and BACKOUT will appear in some
    new version of the CPIC manual in the next 1-2 years.

(4) How do 2-phase commit protocols relate to SYNCPT and BACKOUT ? -
    Application (transaction) programs issue SYNCPT and BACKOUT calls.
    These calls are then translated into the required (SNA) 2-phase
    commit protocol (prepare/commit/committed/forget) over the wire.
    For more information on how these work, you may want to read
    Chapter 5.3 "Presentation Services - Sync Point Services Verbs"
    in IBM's SC31-6808 LU 6.2 Reference: Peer Protocols manual.

Hope this helps.

Wayne D.

=== Usual disclaimers apply ===