II11643: INSTALL STEPS FOR THE CICS WEB INTERFACE FOR V520

APAR status

• Closed as canceled.

Error description

• ****************************************************************
  It is crucial to understand that ALL products involved MUST be
  configured properly in order for the CICS TS 1.2 Web Interface
  (aka CWI) to work!! This document will cover the items necessary
  for setting up to run the CWI. Configuration parameters for
  CICS, TCPIP, LE/370, OpenEdition (OMVS), RACF, and other known
  products which DIRECTLY affect the CWI will be covered. Please
  refer to the product documentation for each respective product
  for more complete information.
  ****************************************************************
  **NOTE--This document is currently written ONLY from the
  **      perspective of running CICS TS 1.2 on the OS/390 2.5 or
  **      OS/390 2.6 platform. We intend to update this in the
  **      future with appropriate information where there are subt
  **      differences relating to configuring different combinatio
  **      of earlier releases of CICS and MVS and/or OS/390.
  ****************************************************************
  Minimum Prerequisites:
  1) TCP/IP R3.2.0 or higher (MUST be OpenEdition capable).
  2) LE/370 1.5 or higher (preferably the one delivered with your
     operating system)
  3) MVS OpenEdition
  ****************************************************************
  +-------------------------------------------------------------+
  |For CICS:                                                    |
  +-------------------------------------------------------------+
  The INSTRUCTIONS in Chapter 18 in the CICS Internet and
  External Interface Guide  (SC33-1944-00) provide complete
  information for setting up the CICS Web Interface. Although
  covered in the manual, the following are common oversights.
   1) Change the WEB= setting from NO to YES, the default is NO.
   2) Create and compile DFHCNV for the CWI.
  *
  If a DFHCNV already exists in the CICS system which will
  incorporate the CWI, the following statements will serve
  as a sample for what needs to be added.   If a DFHCNV does
  not already exist, use the following sample to define the
  entries needed for the CWI.
  Refer to CICS Family: Communicating from CICS on System/390,
  which explains the process of creating a DFHCNV.
  *
  ***ENTRIES FOR CICS WEB INTERFACE
  *!!!NOTE that this example is NOT properly aligned, it has !!!
  *!!!been shifted to the left to fit within this document.  !!!
  *!!!Normally the "DFHCNV" would begin in column 10, with   !!!
  *!!!continuation character (in this case "*") in column 72,!!!
  *!!!with the continued line beginning in column 16,        !!!
  *!!!following standard Assembler conventions.              !!!
  *     -----------------------------------------------
  DFHCNV TYPE=ENTRY,RTYPE=PC,RNAME=DFHWBHH,USREXIT=NO,          *
        SRVERCP=037,CLINTCP=437
  DFHCNV TYPE=SELECT,OPTION=DEFAULT
  DFHCNV TYPE=FIELD,OFFSET=0,DATATYP=CHARACTER,DATALEN=32767,   *
        LAST=YES
  DFHCNV TYPE=ENTRY,RTYPE=PC,RNAME=DFHWBUD,USREXIT=NO,          *
        SRVERCP=037,CLINTCP=437
  DFHCNV TYPE=SELECT,OPTION=DEFAULT
  DFHCNV TYPE=FIELD,OFFSET=0,DATATYP=CHARACTER,DATALEN=32767,   *
        LAST=YES
  DFHCNV TYPE=FINAL
  *
   3) Ensure the TCPIP PORT in use has been reserved for the CWI.
      There is no requirement to assign a port to the CWI, but
      you must use one that NO other products or applications are,
      or will be using.
   4) Define an OMVS segment for the CICS region, authorizing CICS
      to the OMVS libraries.
   5) A SYSTCPD DD statement must be added to the CICS startup
      JCL.
   6) If using the basic authentication sample security programs,
      mentioned on page 129 of the Internet and External
      Interfaces Guide (SC33-1944), they are labeled incorrectly.
      DFH$WBAU is labeled as the analyzer and it is actually the
      converter program. DFH$WBSB is labeled as the converter but
      is actually the analyzer program. If you inadvertently use
      DFH$WBAU as your analyzer instead of DFH$WBSB, you will get
      DFHWB0523 with a response 8 and reason code of 0.
  +-------------------------------------------------------------+
  |For TCPIP from IBM                                           |
  +-------------------------------------------------------------+
   1) Be certain you have added a SYSTCPD DD statement in the
      CICS Startup JCL, which points to the CORRECT TCPIP.DATA
      dataset.
   2) Be certain you are using a unique PORT number, dedicated
      to the CWI. Although it is not required, it is advisable
      to assign a PORT for use by the CWI. Port definitions are
      specified in the TCPIP.PROFILE dataset.
   3) You should run the HOMETEST utility from a TSO command
      line. This utility will test the TCPIP configuration. If it
      fails you will need to recheck your TCPIP.DATA and
      TCPIP.PROFILE configuration files. Make sure this utility
      runs successfully BEFORE trying to use the CWI.
   4) In some cases, customers may find they are running
      without a Domain Name Server or DNS. Although the CICS
      manual states that you must have specified a DNS in the
      TCPIP.DATA file on the NSINTERADDR statement, you can
      get around this by creating a HOST.LOCAL. The procedures
      for doing this are documented in the TCPIP Administration
      guide (the title of the manual will depend on the release
      of TCPIP in use).
   5) If you are running with multiple TCPIP stacks, be certain
      you have defined the entries in the OE BPXPRMxx file to
      point to the correct DEFAULT stack.
   6) If you are running with multiple TCPIP stacks, be certain
      each stack has its own separate, unique IP address.
  +-------------------------------------------------------------+
  |For TCPIP from Interlink                                     |
  +-------------------------------------------------------------+
  The following information was generously provided by the folks
  at Interlink. If you have any questions or problems in this
  area you should contact the Interlink support group.
  Interlink IUCV Sockets:
  ----------------------
  TCPaccess 4.1 users should consult Technical Note
  TN02 -- IUCV Sockets.
  TCPaccess 5.2 users should consult the System Management Guide,
  Chapter 6, IUCV Sockets.
   1) Ensure the 'trgindex.LINK'  library is in the CICS STEPLIB
      and DFHRPL concatenations; this allows the ICS version of
      IUCVMULT to be loaded.
   2) Use the SYSTCPD DD statement to override the default
      TCPIPJOBNAME and set the correct DNS NSINTERADDR for the
      configuration.  This is not documented clearly and the
      default is assumed.
   3) Since TCPaccess 4.1 has only a Domain Name Resolver, the
      Domain Name Server (see #2 above) must reference an
      external name server and port.  For consistency, DNR should
      also be setup for GLOBAL resolution; this allows the DNRGET
      command to be used to validate the requests being presented.
   4) The Domain Name Server *must* be configured to perform both
      direct (byname = host name to IP address) and reverse
      (byvalues = IP address to host name) resolution.  Often the
      reverse database is not fully populated. This latter is also
      referred to as the "in-addr.arpa" lookup.
   5) All maintenance specified for the CICS Web Server, LE/370,
      and TCPaccess must be applied at least to these levels:
        OS/390 v1.3 (SP 6.0.2) at 9709
        LE/370 at v1.5 (for above OS/390)
        TCPaccess v4.1 at 9706 (or later)
        CICS v4.1 at 9709, using the TCP 3.1 C-Socket resident
               library, configured for LE/370 support
        CICS Web Server at current maintenance
   7) All supplementary and prerequisite fixes as noted in
      SC33-1892 section 2.1.2
  Interlink Asynchronous OE Sockets in TCPaccess 5.2:
  --------------------------------------------------
    1) The minimum recommended maintenance level for TCPaccess
       5.2 is CUM9812.
    2) Consult the TCPaccess 5.2 Planning Guide, Chapter 4,
       OpenEdition (UNIX System Services) Support.
    3) The Interlink PFSLOAD must be in the OMVS PROC STEPLIB to
       reference Interlink's T010PFSA module.
    4) The BPXPRMxx entries for Interlink will look like the
       following:
         FILESYSTYPE TYPE(CINET)
                     ENTRYPOINT(BPXTCINT)
         SUBFILESYSTYPE NAME(TCPIP)
                        DEFAULT
                        TYPE(CINET)
                        ENTRYPOINT(EZBPFINI)
         SUBFILESYSTYPE NAME(SNSTCP52)
                        PARM('SYSID(ACSS)')
                        TYPE(CINET)
                        ENTRYPOINT(T010PFSA)
         NETWORK DOMAINNAME(AF_INET)
                 DOMAINNUMBER(2)
                 INADDRANYPORT(10000)
                 INADDRANYCOUNT(1000)
                 MAXSOCKETS(60000)
                 TYPE(CINET)
  +-------------------------------------------------------------+
  |For LE/370:                                                  |
  +-------------------------------------------------------------+
     1) Be certain your LE/370 is current on service as listed
        in INFO APAR II11025.
  +-------------------------------------------------------------+
  |For OpenEdition:                                             |
  +-------------------------------------------------------------+
    1) It is highly recommended you read through the following
       OpenEdition reference manuals:
       a) OpenEdition Planning guide (SC28-1890)
       b) The latest Installation and Customization "Redbook"
       *
       **Note that beginning with OS/390 2.6, OpenEdition will
       **be called UNIX System Services or USS. You may need to
       **keep that in mind when searching for reference manuals.
       *
    2) OpenEdition should be configured to run in "full function"
       mode as opposed to "sockets only" mode.
    3) Ensure the entries within SYS1.PARMLIB(BPXPRMxx) have
       correctly defined.
       *********************************************************
       ** The following is needed for a SINGLE stack TCPIP 3.4**
       *********************************************************
       FILESYSTYPE TYPE(INET) ENTRYPOINT(EZBPFINI)
       NETWORK DOMAINNAME(AF_INET)
               DOMAINNUMBER(2)
               MAXSOCKETS(35000)
               TYPE(INET)
    4) If MULTIPLE TCPIP stacks are in use, be certain the
       entries in the BPXPRMxx member point to the correct
       DEFAULT stack.
       *********************************************************
       ** The following is an EXAMPLE of a multiple TCPIP     **
       ** stack set up. It identifies three TCPIP 3.4 stacks. **
       ** Note that in this example, SUBFILESYSTYPE TCPSMTA1  **
       ** is the "default". If a DEFAULT is not defined, then **
       ** the first TCPIP that starts and connects to OMVS    **
       ** will be the default, which may not necessarily be   **
       ** the TCPIP that CICS was configured for. From a CICS **
       ** perspective, you MUST define the DEFAULT to be the  **
       ** TCPIP that is in the TCPIP.DATA pointed to by the   **
       ** SYSTCPD DD statement in the CICS startup JCL.       **
       *********************************************************
       FILESYSTYPE TYPE(CINET) ENTRYPOINT(BPXTCINT) /*common inet
       NETWORK DOMAINNAME(AF_INET)
               DOMAINNUMBER(2)
               MAXSOCKETS(35000)
               TYPE(CINET)
       SUBFILESYSTYPE NAME(TCP)                     /*tcpip 3.4
               TYPE(CINET)
               ENTRYPOINT(EZBPFINI)
       SUBFILESYSTYPE NAME(TCPSMTA1)                /*tcpip 3.4
               TYPE(CINET)                          /*default
               ENTRYPOINT(EZBPFINI)
               DEFAULT
       SUBFILESYSTYPE NAME(TCPSMTA2)                /*tcpip 3.4
               TYPE(CINET)
               ENTRYPOINT(EZBPFINI)
    5) Define an OMVS segment for the CICS region,
       authorizing CICS to the OMVS libraries.
    6) The OpenEdition installation verification program or IVP
       named OESVP, must run successfully BEFORE attempting to
       use the CICS Web Interface. The utility may be downloaded
       from one of the following websites:
       A) www.s390.ibm.com/products/oe/index.html
          Once at the website click on "Tools and Toys", then
          click on "OS/390 Unix Tools", and now scroll down
          until you see the entry for OESVP then follow the
          instructions.
       B) www.s390.ibm.com/unix/bpxa1svp.html
          Once at the website follow the instructions.
  +-------------------------------------------------------------+
  |For RACF:                                                    |
  +-------------------------------------------------------------+
  You should have already defined your CICS region to RACF, and
  as such you should only need to do what is described in this
  excerpt from the CICS TS 1.2 Migration Guide (GC33-1571-01),
  under the topic "Authorizing CICS region userid to OpenEdition
  MVS":
   "The CICS Web Interface now uses the OpenEdition sockets API,
    in preference to the TCP/IP sockets library. This change means
    that CICS regions using the Web Interface must be authorized
    to access the OpenEdition sockets libraries to ensure the Web
    Interface can resolve OpenEdition sockets API calls.
    Authorize your CICS regions by including an OpenEdition MVS
    (OMVS) segment in the CICS region's user profile, specifying
    the UID parameter. In the OMVS segment, UID specifies the
    numeric user identifier.
  
    For example:   ALTUSER CICSHAA1 OMVS( UID(4127) )
  
    where CICSHAA1 is the CICS region userid of a CICS AOR that
    is initialized with Web Interface support, and 4127 is the
    OpenEdition numeric user identifier assigned for this CICS
    AOR.
    For information about defining OMVS segment parameters in a
    user profile, see the OS/390 Security Server (RACF) Command
    Language Reference SC28-1919. For information about changing
    the access permissions, or modes, of OpenEdition files (modes
    determine who can read, write, or execute a file), see the
    chmod command in the OS/390 OpenEdition Command  Reference
    SC28-1892."
  +-------------------------------------------------------------+
  |For ACF2:                                                    |
  +-------------------------------------------------------------+
  The following information was generously provided by the folks
  at Computer Associates. If you have any questions or problems in
  this area you should contact the ACF2 support group.
   1) Authorize CICS to OMVS
      A) A ONE TIME definition of the following is needed:
         DEFINE GROUP GROUPNAME(omvscics)
                    GROUPID(50)
      B) Userid needs to be setup: (ACF2)
          From TSO, use the ACF command as follows:
            SET LID
            CH cicsxxxx GROUP(omvscics)
            SET PROFILE(USER) DIV(OMVS)
            INSERT cicsxxxx UID(nnn)
            SET PROFILE(GROUP) DIV(OMVS)
            INSERT omvscics GID(nnn)
          Then from the console:
            F ACF2,REBUILD(USR),CLASS(P)
            F ACF2,REBUILD(GRP),CLASS(P)
            F ACF2,OMVS
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• Closing and Pinning APAR
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels