CICS server connection definition

CICS® Transaction Server includes sample EXCI connection and session definitions (EXCG and EXCS). These are in the sample group DFH$EXCI.

You can use the supplied definitions without modification, you can copy and modify the supplied definitions, or you can create completely new definitions.

Here are two examples of a connection definition:

Figure 1. Connection definition - screen 1

VIEW GROUP(MYEXCI) CONNECTION(CTGS)
 OBJECT CHARACTERISTICS                                    CICS RELEASE = 0690
  CEDA  View Connection( CTGS )
   Connection     : CTGS
   Group          : MYEXCI
   DEScription    : Sample EXCI Specific connection
  CONNECTION IDENTIFIERS
   Netname        : CICSTG01
   INDsys         :
  REMOTE ATTRIBUTES
   REMOTESYSTem   :
   REMOTEName     :
   REMOTESYSNet   :
  CONNECTION PROPERTIES
   ACcessmethod   : IRc                Vtam | IRc | INdirect | Xm
   PRotocol       : Exci               Appc | Lu61 | Exci
   Conntype       : Specific           Generic | Specific
   SInglesess     : No                 No | Yes
   DAtastream     : User               User | 3270 | SCs | STrfield | Lms
+  RECordformat   : U                  U | Vb

                                                     SYSID=SYSA APPLID=IY2GTG99

PF 1 HELP 2 COM 3 END             6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL

Figure 2. Connection definition - screen 2

VIEW GROUP(MYEXCI) CONNECTION(CTGS)
 OBJECT CHARACTERISTICS                                    CICS RELEASE = 0690
  CEDA  View CONnection( CTGS )
   Queuelimit     : No                 No | 0-9999
   Maxqtime       : No                 No | 0-9999
  OPERATIONAL PROPERTIES
   AUtoconnect    : No                 No | Yes | All
   INService      : Yes                Yes | No
  SECURITY
   SEcurityname   :
   ATtachsec      : Identify           Local | Identify | Verify | Persistent | Mixidpe
   BINDPassword   :                    PASSWORD NOT SPECIFIED
   BINDSecurity   : No                 No | Yes
   Usedfltuser    : No                 No | Yes
  RECOVERY
   PSrecovery     :                    Sysdefault | None
   Xlnaction      : Keep               Keep | Force
  DEFINITION SIGNATURE 
+  DEFinetime     : 04/15/14 15:49:10


                                                     SYSID=SYSA APPLID=IY2GTG99

PF 1 HELP 2 COM 3 END             6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL

Figure 3. Connection definition - screen 3

VIEW GROUP(MYEXCI) CONNECTION(CTGS)
 OBJECT CHARACTERISTICS                                    CICS RELEASE = 0690
  CEDA  View CONnection( CTGS )
+  CHANGETime     : 04/15/14 15:52:19
   CHANGEUsrid    : CICSUSER 
   CHANGEAGEnt    : CSDApi             CSDApi | CSDBatch
   CHANGEAGRel    : 0690














                                                     SYSID=SYSA APPLID=IY2GTG99

PF 1 HELP 2 COM 3 END             6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL

The key parameters are shown in bold in the examples, these are:

Parameter	Setting
Netname	If you enter a Netname, the connection uses a specific pipe. If you leave it blank, the EXCI connection uses a generic pipe. You should ideally use a specific pipe because this helps to manage multiple connections, and to identify problems. If you use specific pipes, set Netname to be the same as the pipe specified in the EXCI client program. You specify this on the user_name parameter of an Initialize_User EXCI call. Set the DFHJVPIPE environment variable to allow CICS Transaction Gateway to pass this value to the EXCI. For more information see Setting environment variablesSetting environment variables. If you use the sample DFH$EXCI, set the DFHJVPIPE environment variable to BATCHCLI to use the specific pipe. If CICS Transaction Gateway is configured to connect to more than one CICS server, use the same Netname for all EXCI connections.
ACcessmethod	Specify IRC (interregion communication).
PRotocol	Specify EXCI.
Conntype	This defines the type of EXCI connection used for jobs that are not CICS to communicate with a CICS server on IBM® z/OS®. This is a type of multiregion operation (MRO) request and can be either Generic or Specific. Generic: An MRO link with multiple sessions to be shared by multiple EXCI users. Only one generic EXCI connection can be installed in each server. Specify Generic if you left the Netname attribute blank. Specific: An MRO link with one or more sessions dedicated to a single user in a client program. Specify Specific if you completed the Netname attribute.
ATtachsec	This determines whether a check is to be made against the flowed user ID. Specify Local or Identify. Local: CICS Transaction Gateway does not flow a user identifier; just the link user ID (if specified) is used. If no link user ID is supplied, all requests are run under the CICS default user ID as specified in the DFLTUSER SIT parameter. Identify: A user ID is flowed on every request, but a password is not expected, because CICS trusts the user ID as having been already authenticated. For security reasons, consider enabling user ID and password verification within CICS Transaction Gateway, before the EXCI request is made. The user ID is either the user named in the ECIRequest object (if null), or the user ID of the thread under which the ECI request runs.

For more information on how to create CICS server connection definitions see the CICS Transaction Server for IBM z/OS External Interfaces GuideCICS Transaction Server for IBM z/OS External Interfaces Guide.