IMS Connect configuration examples

The following examples of IMS Connect configuration statements show how to enable various IMS Connect functions and support during IMS Connect system definition.

You can also find a sample IMS Connect configuration member, HWSCFG00, in the ADFSSMPL data set.

Important: In all the example configurations shown, you can continue parameters beyond an 80-column line by using any combination of the following techniques:
  • Inserting a comma followed by three blanks, then continuing the parameter on the next line. An example of this technique is shown in the IMS Connect Example 1 Configuration File.
  • Using all 80 columns of a line, then continuing in the next statement. You do not need to use a continuation indicator (such as an "x" in column 72).

Example of a simple IMS Connect configuration for IMS TM support

The following figure is an example of a simple IMS Connect system configuration for IMS TM support.

Figure 1. Simple IMS Connect system configuration for IMS TM support
begin figure description. Diagram of a simple system configuration as described in the surrounding text. end figure description.

In the following example of an IMS Connect configuration member:

  • The IMS Connect ID is defined as HWS. This IMS Connect is configured to include the ports defined for TCP/IP communications and the IMS OTMA group and member names for communication with IMS.
  • The TCP/IP configuration defines the HOSTNAME as MVSTCPIP, the RACFID as RACFID, the PORTID as 9999, and the EXIT as HWSSMPL0.
  • The data store configuration defines the ID as IMS, the GROUP as XCFGROUP, the MEMBER as HWSMEM, and the TMEMBER as IMSMEM.
***************************************************
* IMS Connect example configuration file
***************************************************
HWS (ID=HWS,RACF=N,XIBAREA=20)
TCPIP (HOSTNAME=MVSTCPIP,RACFID=RACFID,PORTID=(9999),MAXSOC=2000,TIMEOUT=8888,   
EXIT=(HWSSMPL0))
DATASTORE  (ID=IMS,GROUP=XCFGROUP,MEMBER=HWSMEM,TMEMBER=IMSMEM,DRU=HWSYDRU0)

Example of a complex IMS Connect configuration for IMS TM support

The following figure shows an example of a more complex IMS Connect system configuration for TM support.
Figure 2. Complex IMS Connect system configuration for IMS TM support
begin figure description. Diagram of a complex system configuration as described in the surrounding text. end figure description.

In following example of an IMS Connect configuration member:

  • Three IMS Connects are configured. Each IMS Connect has its own configuration member.
  • Each IMS Connect uses a different port number for TCP/IP communications and can belong to multiple z/OS® cross-system coupling facility (XCF) groups.
  • One or more IMS systems can belong to each XCF group.
  • When defining multiple data stores that belong to the same XCF group in a single IMS Connect configuration member, the XCF member name for that IMS Connect must be unique in each DATASTORE statement. However, if the data stores are members of different XCF groups, the XCF member names can be the same for different data stores within a single IMS Connect configuration member.
For example, observe that the XCF member name for IMS Connect in the IMSA and IMSB DATASTORE statements in the HWS2 configuration member in the configuration example, HWSMEM2, is the same for both DATASTORE statements. The IMSA and IMSB data stores are members of different XCF groups—GROUPA and GROUPB—so the XCF member names can be identical. These member names could have been made unique, for example, HWS2MEMA and HWS2MEMB, but it is not necessary to do so. However, the XCF member names for IMS Connect in the IMSB and IMSC DATASTORE statements in the HWS2 configuration member are different because the IMSB and IMSC data stores are members of the same XCF group, GROUPB. 
***************************************************
* IMS Connect example configuration member for HWS1
***************************************************
HWS (ID=HWS1,RACF=N,XIBAREA=20)
TCPIP (HOSTNAME=MVSTCPIP,RACFID=RACFID,PORTID=(9999),MAXSOC=2000,TIMEOUT=8888,
EXIT=(HWSSMPL0))
DATASTORE (ID=IMSA,GROUP=GROUPA,MEMBER=HWS1MEM,TMEMBER=IMSAMEM,DRU=HWSYDRU0)
***************************************************
 
***************************************************
* IMS Connect example configuration member for HWS2
***************************************************
HWS (ID=HWS2,RACF=N,XIBAREA=20)
TCPIP (HOSTNAME=MVSTCPIP,RACFID=RACFID,PORTID=(9998),MAXSOC=2000,TIMEOUT=8888,
EXIT=(HWSSMPL0))
DATASTORE (ID=IMSA,GROUP=GROUPA,MEMBER=HWS2MEM,TMEMBER=IMSAMEM,DRU=HWSYDRU0)
DATASTORE (ID=IMSB,GROUP=GROUPB,MEMBER=HWS2MEM,TMEMBER=IMSBMEM,DRU=HWSYDRU0)
DATASTORE (ID=IMSC,GROUP=GROUPB,MEMBER=HWS2MEMC,TMEMBER=IMSCMEM,DRU=HWSYDRU0)
***************************************************
 
***************************************************
* IMS Connect example configuration member for HWS3
***************************************************
HWS (ID=HWS3,RACF=Y,XIBAREA=20)
TCPIP (HOSTNAME=MVSTCPIP,RACFID=RACFID,PORTID=(9997),MAXSOC=2000,TIMEOUT=8888,
EXIT=(HWSSMPL0))
DATASTORE (ID=IMSB,GROUP=GROUPB,MEMBER=HWS3MEMB,TMEMBER=IMSBMEM,DRU=HWSYDRU0)
DATASTORE (ID=IMSC,GROUP=GROUPB,MEMBER=HWS3MEMC,TMEMBER=IMSCMEM,DRU=HWSYDRU0)
***************************************************

Example of IMS Connect support for ISC links between IMS and CICS.

The following example shows a simple configuration member for an IMS Connect instance that supports ISC parallel sessions on an ISC link between IMS and IBM® CICS® Transaction Server for z/OS.

Instead, the ISC statement defines the connection to IMS via the Structured Call Interface (SCI) of the Common Service Layer (CSL). A DATASTORE statement is not required.

The CICSPORT keyword on the TCPIP statement defines port that IMS Connect receives transactions and reply data from CICS.

HWS=(ID=HWS1,XIBAREA=100,RACF=N)
TCPIP=(HOSTNAME=TCPIP,PORTID=(9998,19998,LOCAL),RACFID=GOFISHIN,
     TIMEOUT=000,
     IPV6=Y,
     PORT=(ID=15554),
     CICSPORT=(ID=1111,KEEPAV=1000),
     CICSPORT=(ID=3333,KEEPAV=1000),
     CICSPORT=(ID=6666,KEEPAV=1000),
     CICSPORT=(ID=7777,KEEPAV=1000),
     EXIT=(HWSSMPL0,HWSSMPL1,HWSCSLO0,HWSCSLO1,HWSSOAP1))
ISC=(ID=CICSA1,NODE=LU6NDPA,
     IMSPLEX=(MEMBER=HWS1,TMEMBER=PLEX1),
     LCLIMS=IMS1,RMTCICS=CICS1,CICSAPPL=CICS1,CICSPORT=1111)
ISC=(ID=CICSA2,NODE=LU6NDPB,
     IMSPLEX=(MEMBER=HWS1,TMEMBER=PLEX1),
     LCLIMS=IMS1,RMTCICS=CICS1,CICSAPPL=CICS1,CICSPORT=3333)
ISC=(ID=CICSA5,NODE=ISCTCP1,
     IMSPLEX=(MEMBER=HWS1,TMEMBER=PLEX1),
     LCLIMS=IMS1,RMTCICS=CICS1,CICSAPPL=CICS1,CICSPORT=6666)
ISC=(ID=CICSA6,NODE=ISCTCP2,
     IMSPLEX=(MEMBER=HWS1,TMEMBER=PLEX1),
     LCLIMS=IMS1,RMTCICS=CICS1,CICSAPPL=CICS1,CICSPORT=7777)
RMTCICS=(ID=CICS1,HOSTNAME=ABC.EXAMPLE.COM,PORT=23456)

Example of IMS Connect configuration for IMS-to-IMS connections

The following sets of configuration statements provide examples of how to configure both IMS Connect instances that support an IMS-to-IMS TCP/IP connection.

The examples are shown in two sets two.

The following set of configuration statements show an example of the IMS Connect configuration statements required to support MSC.

The following two sets of example configuration statements define a connection for an MSC link between two instances of IMS Connect. One set of configuration statements is for a local IMS Connect instance, HWS1, and one set is for a remote IMS Connect instance, HWS2. Both IMS Connect instances require both a RMTIMSCON statement and an MSC statement because MSC links support message traffic in both directions.

*************************************************** 
* IMS Connect configuration statements for an MSC IMS-to-IMS connection
***************************************************

*************************************************** 
* Local HWS1 configuration statements
***************************************************
HWS=(ID=HWS1,XIBAREA=20,RACF=Y)                                       
TCPIP=(HOSTNAME=TCPIP,PORTID=(9999),                                   
       MAXSOC=50,RACFID=RACFID,TIMEOUT=5000)            
RMTIMSCON=(ID=ICON2,HOSTNAME=ICON2.IBM.COM,PORT=5555,       
           IDLETO=0,AUTOCONN=N,PERSISTENT=Y,                           
           RESVSOC=10,USERID=USER01,APPL=APPL01)                       
MSC=(LCLPLKID=MSC12,RMTPLKID=MSC21,                                    
     IMSPLEX=(MEMBER=HWS1,TMEMBER=PLEX1),                              
     LCLIMS=(IMS1),RMTIMS=IMS2,RMTIMSCON=ICON2)                        
*************************************************** 

*************************************************** 
* Remote HWS2 configuration statements
***************************************************
HWS=(ID=HWS2,XIBAREA=20,RACF=Y)                                       
TCPIP=(HOSTNAME=TCPIP,PORTID=(5555),                                   
       MAXSOC=50,RACFID=RACFID,TIMEOUT=5000)            
RMTIMSCON=(ID=ICON1,HOSTNAME=ICON1.IBM.COM,PORT=9999,       
           IDLETO=0,AUTOCONN=N,PERSISTENT=Y,                           
           RESVSOC=10,USERID=USER02,APPL=APPL02)                       
MSC=(LCLPLKID=MSC21,RMTPLKID=MSC12,                                    
     IMSPLEX=(MEMBER=HWS2,TMEMBER=PLEX2),                              
     LCLIMS=(IMS2),RMTIMS=IMS1,RMTIMSCON=ICON1)                        
***************************************************

The following two sets of example configuration statements define a one-way OTMA connection between two instance of IMS Connect. One set of configuration statements is for a local IMS Connect instance, HWS1, that sends OTMA messages, and one set is for a remote IMS Connect instance, HWS2, that receives the OTMA messages.

*************************************************** 
* IMS Connect configuration statements for an OTMA IMS-to-IMS connection
***************************************************

*************************************************** 
* Local HWS1 configuration statements
***************************************************
HWS=(ID=HWS1,XIBAREA=20,RACF=N)                                       
TCPIP=(HOSTNAME=TCPIP,PORTID=(9999),                                   
       MAXSOC=50,RACFID=RACFID,TIMEOUT=5000)            
DATASTORE=(ID=IMS1,GROUP=XCFGRP1,MEMBER=HWS1,TMEMBER=IMS1,DRU=HWSYDRU0,
           APPL=APPLID1)                                               
RMTIMSCON=(ID=ICON2,HOSTNAME=ICON2.IBM.COM,PORT=5555,      
           IDLETO=3000,AUTOCONN=N,PERSISTENT=Y,                        
           RESVSOC=10,USERID=USER01,APPL=APPL01)                        
*************************************************** 

*************************************************** 
* Remote HWS2 configuration statements
***************************************************
HWS=(ID=HWS2,XIBAREA=20,RACF=Y)                                       
TCPIP=(HOSTNAME=TCPIP,PORTID=(9999,5555),                              
       MAXSOC=50,RACFID=RACFID,TIMEOUT=6000)            
DATASTORE=(ID=IMS2,GROUP=XCFGRP2,MEMBER=HWS2,TMEMBER=IMS2,DRU=HWSYDRU0,
           APPL=APPLID1)                                               
***************************************************

IMS Connect configuration statement for IMS DB support

The following example shows a simple configuration member for an IMS Connect instance that supports clients that connect to IMS DB in a DBCTL system.

When configuring IMS Connect to support only a DBCTL system, a DATASTORE statement is not required. Instead, the ODACCESS statement defines the connection to IMS via the Open Database Manager (ODBM) of the Common Service Layer (CSL). For IMS Connect to communicate with ODBM, you must code an IMSPLEX substatement in the IMS Connect configuration member. You do not identify ODBM or IMS in the configuration member. The communication and connection between IMS Connect and ODBM is managed automatically by IMS Connect and ODBM through the Structured Call Interface (SCI) component of CSL.

When ODBMAUTOCONN=Y is specified, as shown in the example, IMS Connect automatically connects to all active ODBM instances in the IMSplex that is specified on the TMEMBER parameter of the IMSPLEX substatement. Communications with the IMS systems that are defined to the ODBM instances is also automatically enabled.

If ODBMAUTOCONN=N, IMS Connect does not connect to ODBM during startup. Communication can then be enabled for ODBM instances and IMS systems individually by issuing the STARTIA command.

Although the values of ID on the HWS statement and MEMBER on the IMSPLEX substatement are the same in the example, the values do not need to match.

*************************************************** 
* IMS Connect example for IMS Universal drivers and DRDA client support
***************************************************
HWS (ID=HWS1,RACF=N,XIBAREA=20)
TCPIP (HOSTNAME=MVSTCPIP,RACFID=RACFID,MAXSOC=2000)
ODACCESS (DRDAPORT=(ID=1111,KEEPAV=5,PORTTMOT=50),
IMSPLEX=(MEMBER=HWS1,TMEMBER=PLEX1),
ODBMAUTOCONN=Y)
***************************************************
The following figure illustrates the configuration defined in the preceding example.
Figure 3. Simple IMS Connect system configuration for IMS DB support
begin figure description. Diagram of a simple IMS Connect configuration in which an IMS Connect client, like the IMS Universal drivers, connects to IMS Connect over TCP/IP. IMS Connect communicates to ODBM through SCI, and ODBM communicates directly to IMS. end figure description.

Additional IMS Connect configuration statement examples

The following series of IMS Connect configuration statements are examples of how to configure IMS Connect to support various functions, including:

  • OM command clients, such as IBM Management Console for IMS and Db2 for z/OS
  • Internet Protocol version 6 (IPV6)
  • RACF® PassTicket
  • Secure Sockets Layer (SSL)
  • XML conversion with the XML adapter
  • IMS Universal drivers and DRDA clien
Note: AT-TLS is the recommended method to enable SSL for IMS Connect.
***************************************************
* IMS Connect example of including the support for OM command clients
***************************************************
HWS (ID=HWS4,RACF=Y,XIBAREA=20)
TCPIP (HOSTNAME=MVSTCPIP,RACFID=RACFID,PORTID=(9999,LOCAL),MAXSOC=2000,
TIMEOUT=8800,
EXIT=(HWSCSLO0,HWSCSLO1,HWSSMPL1))
IMSPLEX (MEMBER=HWS4,TMEMBER=PLEX1)
***************************************************

***************************************************
* IMS Connect example of including the support for OM command clients and IPV6
***************************************************
HWS (ID=HWS4,RACF=Y,XIBAREA=20)
TCPIP (HOSTNAME=MVSTCPIP,RACFID=RACFID,PORTID=(9999),MAXSOC=2000,TIMEOUT=8800,
EXIT=(HWSCSLO0,HWSCSLO1,HWSSMPL1),IPV6=Y)
IMSPLEX (MEMBER=HWS4,TMEMBER=PLEX1)
***************************************************

***************************************************
* IMS Connect example of including the APPL name for passticket support
***************************************************
HWS (ID=HWS5,RACF=Y,XIBAREA=20)
TCPIP (HOSTNAME=MVSTCPIP,RACFID=RACFID,PORTID=(9999),MAXSOC=2000,TIMEOUT=8800,
EXIT=(HWSSMPL0)
DATASTORE (ID=IMS,GROUP=XCFGROUP,MEMBER=HWSMEM,TMEMBER=IMSMEM,DRU=HWSYDRU0,
APPL=APPLID1)
***************************************************

***************************************************
* IMS Connect example of including the support for SSL
***************************************************
HWS (ID=HWSG7,RACF=N,XIBAREA=20))
TCPIP (HOSTNAME=TCIPI,PORTID=(9998),
EXIT=(HWSSMPLO))
DATASTORE (ID=SOCKEYE,MEMBER=COHO,TMEMBER=CHINOOK,GROUP=SALMON)
***************************************************

***************************************************
* IMS Connect example of including XML adapter support
***************************************************
HWS (ID=HWS8,RACF=Y,XIBAREA=20)
TCPIP (HOSTNAME=MVSTCPIP,RACFID=RACFID,
PORTID=(9999,LOCAL,MAXSOC=2000,TIMEOUT=8800,
EXIT=(HWSSMPL1,HWSSOAP1))
ADAPTER (XML=Y,MAXCVRT=200)
***************************************************