Re:Re: [IDMSVENDOR-L] cics to idms lu62 connectivity failure on

Discussion created by ca.portal.admin on Nov 13, 2008
CICS startup

Steve, et al,

Doesn't this apply to ""Two-Phase Commit Support"" only, rather LU6.2

Gary Bryson

The information contained in this e-mail message and any attachments is
confidential and intended only for the addressee(s). If you are not an
addressee, you may not copy or disclose the information, or act upon it,
and you should delete it entirely from your e-mail system. Please notify
the sender that you received this e-mail in error.
-----Original Message-----
From: IDMS Public Discussion Forum [mailTo:IDMS-L@LISTSERV.IUASSN.COM]
On Behalf Of Harmeson, Steve (Newport News)
Sent: Thursday, November 13, 2008 5:34 AM
Subject: Re: [IDMSVENDOR-L] cics to idms lu62 connectivity failure on
CICS startup

Sorry I didn't get back to you sooner but in the CA-IDMS System
Operations manual section 14.4.8 CICS Resynchronization Task Execution
is were you will find all you care to about resync program, I believe it
came out in 15.0 or earlier 16.0. Do a search on IDMSCSYN to find it
quickly. Short description below:

Resynchronization between a CICS interface and an Advantage CA-IDMS

central version is done through execution of a resynchronization

transaction defined to CICS. The Advantage CA-IDMS installation default

name for this transaction is RSYN. The resynchronization transaction is

associated with a resynchronization program whose installation default

name is IDMSCSYN. A separate resynchronization transaction and program

must be created for each CICS interface module (IDMSINTC) that is used

within a CICS system and the name of the transaction must be specified
in =20
the RSYNTXN parameter of the interface's CICSOPT macro. Failure to
define the CICS resynchronization transaction causes any task attempting
open =20
a database session for which AUTOCMT is enabled to fail with an abend
code of K209. =20

Steve Harmeson