Configuring IMS Connect

IMS Connect supports communication between one or more TCP/IP clients and IMS systems. You can configure multiple IMS systems on multiple z/OS® images within a single sysplex and distribute the client request to the IMS systems (data stores).

1. Authorize the Authorized Program Facility (APF).
   1. Create and run a JCL job that authorizes IMS.SDFSRESL library to the APF.
   2. Issue the z/OS command SETPROG APF,ADD,DSNAME=IMS.SDFSRESL,VOLUME=IMS001.
2. Update the z/OS Program Properties Table (PPT). Updating the PPT allows IMS Connect to run in authorized supervisor state and in key 7.
   1. Edit the SCHEDxx member of the SYS1.PARMLIB data set.
   2. Add the required entries to the z/OS PPT.
      For TCP/IP communications only, add the following entry in the z/OS PPT:

      PPT PGMNAME(HWSHWS00)     /* PROGRAM NAME = HWSHWS00           */
               CANCEL           /* PROGRAM CAN BE CANCELED           */
               KEY(7)           /* PROTECT KEY ASSIGNED IS 7         */
               SWAP             /* PROGRAM IS SWAPPABLE              */
               NOPRIV           /* PROGRAM IS NOT PRIVILEGED         */
               DSI              /* REQUIRES DATA SET INTEGRITY       */
               PASS             /* CANNOT BYPASS PASSWORD PROTECTION */
               SYST             /* PROGRAM IS A SYSTEM TASK          */
               AFF(NONE)        /* NO CPU AFFINITY                   */

   3. IPL the z/OS system again or issue the z/OS SET SCH= command to make the changes effective.
3. Enable Internet Protocol Version 6 (IPV6) for IMS Connect.
   1. Ensure that IMS Connect is running.
   2. Customize the BPXPRMxx member, as follows:

      FILESYSTYPE Type(INET) Entrypoint(EZBPFINI)
      NETWORK DOMAINNAME(AF_INET)
      DOMAINNUMBER(2)
        MAXSOCKETS(2000)
        TYPE(INET)
      
      NETWORK DOMAINNAME(AF_INET6)
      DOMAINNUMBER(19)
        MAXSOCKETS(3000)
        TYPE(INET)

   3. Recycle the TCP/IP stack. For more information about customizing this member, see z/OS UNIX System Services Planning.
   4. Customize the IMS Connect configuration member using the IPV6 parameter.
   5. For each of the READ subroutines shown below that you use, determine whether the EXPREA_IPV6 bit is turned on in the EXPREA_FLAG2 field of the READ subroutine. If it is turned on, IPV6 is enabled.
      • HWSJAVA0
      • HWSSMPL0
      • HWSSMPL1
   6. Map EXPREA_SOCKET6 to the AF_INET6 socket address structure. See READ subroutine in IMS Version 15.5 Exit Routines for more information.
   The IP address format when IPV6 is enabled is described in VIEWHWS command in IMS Version 15.5 Commands, Volume 3: IMS Component and z/OS Commands.
4. Create an IMS Connect configuration member in IMS.PROCLIB data set to hold the configuration statements that IMS Connect uses during initialization.
   You can specify the following configuration statements for IMS Connect to use:

   • ADAPTER
   • DATASTORE
   • HWS
   • IMSPLEX
   • ISC
   • MSC
   • ODACCESS
   • RMTCICS
   • RMTIMSCON
   • TCPIP

   In addition, you can dynamically create, update, and delete certain IMS Connect resources by using IMS type-2 commands.