Installing AVZ interface for ACI

This section provides the installation requirements and installation steps for the AVZ interface for ACI when used with Software AG’s Natural via CICS and Batch.

1. Install the AVZ server. See Installing and configuring the server.
2. Modify the AVZ initialization EXEC.
   Use the MODIFY PARM command to set following parameters located in the AVZ initialization EXEC, xVZyIN00:

   “MODIFY PARM NAME(ACIPREALLOC VALUE(100)”
   “MODIFY PARM NAME(ACIDEFAULTCONNNAME) VALUE(EXCS)”
   “MODIFY PARM NAME(ACIPERSISTTIMEOUT) VALUE(CLIENT)”
   “MODIFY PARM NAME(ACICONNPW) VALUE(NO)”
   “MODIFY PARM NAME(ACISRVRCONNINT) VALUE(25)”
   “MODIFY PARM NAME(ACISETSRVRINTTIME) VALUE(YES)”
   “MODIFY PARM NAME(ACICICSGENERIC) VALUE(ACICSRV)”
   “MODIFY PARM NAME(ACIBATCHGENERIC) VALUE(ACIBSRV)”
   “MODIFY PARM NAME(ACITRACE) VALUE(YES)”
   

3. Assemble the ACI translation/migration table.

   You must assign a default DV Server subsystem to route all service application ACI requests. You can do this with the ACI translation/migration table (AVZRTX table) provided with the AVZ interface for ACI. The AVZRTX table is initially loaded by AVZCTRUI (the ACI Task Related User Exit Initialization program), and is viewed by AVZCITRU (the ACI Task Related User Exit).

   The minimal assembled module must contain the TYPE=INITIAL card with a default defined AVZ subsystem and a TYPE=FINAL card to set the default subsystem.

   Note: The default AVZ server subsystem can be overridden by using the ”#ETBCB-ACI-ID” field in the REGISTER function to specify a AVZ server subsystem.

   If you are using Natural via CICS, the AVZRTX table can also be used by AVZCINAT, the Natural “front end” program, to obtain information to start the Natural session. AVZCIFEN is a CICS module that allows the passing of the COMMAREA to the invoked ACI server, if the CICS transaction is associated with the AVZCIFEN program. If you associate the transaction name with the program AVZCIFEN when defining the transaction to CICS, you can pass Natural startup parameters to the transaction using the COMMAREA. In turn, AVZCIFEN transfers control (EXEC CICS XCTL) to a program of your choice. If AVZCINAT is used as the program to which AVZCIFEN transfers control, the COMMAREA must be formatted with the Natural nucleus program name (eight bytes, space padded if necessary), followed by a comma, followed by the CICS transaction ID for Natural (four bytes, space padded if necessary), followed by a comma, followed by the Natural startup parameters.

   Note: If the AVZCIFEN program is used to specify the Natural startup parameters, as a minimum, the AVZRTX table must be assembled with the TYPE=INITIAL card with a default AVZ subsystem defined and a TYPE=FINAL card to set the default subsystem.

   To assemble the AVZRTX table:

   1. Use data set member AVZACJBH, located in HLQ.SAVZSAMP. This member contains the source that needs to be assembled for the ACI translation/migration table.
   2. Install the ACI translation/migration table into a load library that is concatenated to the DFHRPL DD statement for CICS which may include the SAVZCLOD dataset or for batch include the AVZRTX table within the STEPLIB of the batch application.

      The following example shows an example AVZRTX entry with the required minimum:

      ACI TYPE=INITIAL,SUBS=xVZy DEFINITION START / DEFAULT
      ACI TYPE=FINAL DEFINITION END
      

4. Link the stubs:
   1. Link the AVZCICIS stub into your Natural CICS nucleus, using the following example:

      //AVZLIB DD DSN=HLQ.SAVZCLOD,DISP=SHR
      .
      .
      CHANGE BROKER(AVZACI) <--CHANGING THE DEFAULT NAME
      INCLUDE AVZLIB(AVZCICIS) FOR AVZ ACI STUB
      INCLUDE NATLIB(NATLAST) FINAL INCLUDE

      You must add AVZACI as a CSTATIC parameter, as shown in the following example:

      CSTATIC=(CMMSG,AVZACI)

   2. Link the AVZRBIS stub into your Natural Batch nucleus, using the following example:

      //AVZLIB DD DSN=HLQ.SAVZLOAD,DISP=SHR
      .
      .
      CHANGE BROKER(AVZACI) <--CHANGING THE DEFAULT NAME
      INCLUDE AVZLIB(AVZRBIS) FOR AVZ ACI STUB
      INCLUDE NATLIB(NATLAST) FINAL INCLUDE
      

      You must add AVZACI as a CSTATIC parameter, as shown in the following example:

      CSTATIC=(CMMSG,AVZACI)

5. Create CICS resource definitions.

   The AVZ interface for ACI requires several resources that include programs, a transaction, and an intrapartition transient data queue (TDQ) to be defined in all CICS regions that will be using this component.

   Note: These resources should have been defined during the installation of the AVZ interface for CICS/TS, a prerequisite for this component. AVZCICSD (in HLQ.SAVZCNTL library) is the name of the member used to define these resources. This member defines AVZCTRUI and AVZCITRU to CICS for the loading and viewing of the AVZRTX table (see Step 3).
6. Assemble CICS PLTPI for ACI task related user exit.
   1. Add the following entry to the program list table/program initialized (PLTPI) table.

      DFHPLT TYPE=ENTRY, PROGRAM=AVZCTRUI

      This entry should follow the first of the following statements to ensure that the AVZCTRUI will be executed in phase 2 of the CICS PLTI process:

      DFHPLT TYPE=ENTRY, PROGRAM=DFHDELIM

   2. Code the appropriate parameter in CICS startup.

      PLTPI=xx

      where xx is the suffix value given to the DFHPLTI table.

7. In order to associate the data set modules with CICS, add HLQ.SAVZCLOD data set to the CICS DFHRPL data set concatenation.
8. Restart the CICS region.
   Because the CICS installation for the AVZ interface for ACI requires use of a CICS task related user exit, you should restart your CICS region. The following message appears on the console if the CICS Task Related User Exit correctly installs and is enabled:

   AVZ0364I AVZCITRU is started and enabled.

9. Add Natural source distribution.

   Customize and submit AVZACNLD, located in HLQ.SAVZCNTL. This is a Natural Systems utility that will load the Natural environment objects into the AVZ Natural library. These objects include Natural samples and ACI Server programs.

   Note: If you are using Natural security, you must create the AVZ Natural Library before performing this step. If you are not using Natural Security, the library is created automatically.