II08516: HINTS AND TIPS FOR SYSTEM SETUP (CICS) ASF VERSION 3 ( 565500200 )

APAR status

• Closed as canceled.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• ASF Version 3    565500200
  APPLICATION SUPPORT FACILITY VERSION 3
  Hints and tips for system setup (CICS)
  (This is an updated version of chapter 6.12 in the
  Program Directory for IBM Application Support Facility)
  
  This APAR lists setups outside of Application Support
  Facility and the impacts they may have for your Application
  Support Facility installation:
  
  1. UCTRAN
  
     Uppercase translation caused by setting
     parameter UCTRAN=YES has the following impacts:
  
     - You cannot enter parameter names or text in
       uppercase and lowercase in Application Support
       Facility.
     - The communication between the Workstation feature
       and the host part of Application Support Facility
       does not work.
  
     The following settings are recommended:
  
     - CICS Version 2
  
       - Resource Definition Online (RDO)
  
         Set UCTRAN=NO or UCTRAN=TRANID. Do not specify
         UCTRAN=YES in the TYPETERM definitions in the
         TCT entries for the terminals you use with
         Application Support Facility.
  
       - Terminal Control Table (TCT)
  
         If you use TCT macro definitions, do not specify
         UCTRAN in FEATURE=parameter of your TCT entries for the
         terminals you use with Application Support Facility.
  
     - CICS Version 3
  
       Set UCTRAN=NO or UCTRAN=TRANID.
       Do not specify UCTRAN=YES in the TYPETERM
       definitions in the TCT entries for the terminals
       you use with Application Support Facility.
       Specify UCTRAN=NO in the profile definitions.
  
       Application Connectivity also requires UCTRAN=NO
       or UCTRAN=TRANID.
  
  2. TCTUA
  
     Application Support Facility uses 16 bytes of the
     TCTUA to support NODE ERROR situations (NEP) and
     PROGRAM ERROR situations (PEP). The use of TCTUA
     is optional, but it is a prerequisite for the
     Application Support Facility NEP and PEP handling.
  
     If you do not use TCTUA, use the reset function
    (FSNA transaction) instead.
  
    To set SESSCTL=2 is an alternate possibility.
    Refer to "Transaction family table (FSNTTXC)" in
    Chapter 16 "Customizing Application Support Facility"
    of the Administration Guide of Application Support
    Facility for further information on SESSCTL=2.
  
    Note: If you use Application Support Facility and
          OfficeVision/MVS, both products need their own
          OfficeVision/MVS, both products need their own
          16-byte TCTUA. This is supported by the use of
          parameter TCTDISP. For details see the
          description of parameter TCTDISP in the
          Program Directory.
  
    If Application Support Facility runs under CICS/ESA
    with storage protection, Application Support Facility
    not only reads but also updates its part of the TCTUA.
    To run Application Support Facility programs
     with the attribute USERKEY successfully,
     the TCTUA must be defined with the SIT
     attribute TCTUAKEY=USER. This is the CICS default.
     Setting TCTUAKEY=CICS results in a protection
     exception (ASRA) when Application Support Facility
     writes to the TCTUA.
  
  3. NODE ERROR PROGRAM (NEP)
  
     NEP provides the following functions:
  
     - It prevents an unauthorized user from
       resuming a session after reconnect of a
       terminal after a node error occurred.
     - It lets a user sign on at another terminal
       after a node error occurred.
  
       If NEP is not used, there are the following
       limitations:
  
       - If a node error occurs and the terminal reconnects,
         the terminal receives the communication area during
         the next interrupt and the session continues.
         This is a security risk because unauthorized people
         can continue working with the session of another user.
       - To sign on again is only possible after the session
         where the node error occurred has been reset by
         the administrator.
  
     Application Support Facility provides a complete sample
     NEP for both, CICS Version 2 and CICS Version 3.
     Assemble and link the sample NEP to get a running
     version supporting the Application Support Facility
     node error handling.
  
     If you already use another NEP, add the sample
     NEP code to your existing NEP.
  
     In an MRO environment the NEP must be installed
     in the terminal owning region (TOR).
  
     Note: If you use Application Support Facility and
           OfficeVision/MVS, your NEP must contain the
           NEP code for both programs.
  
  4. PROGRAM ERROR PROGRAM (PEP)
  
     The PEP code provides the following functions:
  
     - Possibility to sign on at another terminal after
       a program ABEND.
  
     - Support of ABENDs outside of Application Support Facility.
       This means if an ABEND occurs in an application that
       was called from Application Support Facility, it is
       possible to sign on at another terminal.
  
       If PEP is not used, signing on is only possible when
       the session where the ABEND occurred has been reset by
       the administrator.
  
       Application Support Facility provides a complete
       sample PEP for both, CICS Version 2 and CICS Version 3.
       Assemble the sample PEP to get a running version
       supporting the Application Support Facility
       program error handling. In an MRO environment
       PEP must be installed in each application
       owning region (AOR).
  
  5. TIMEOUT
  
     - Application Support Facility
  
       Application Support Facility provides an internal
       timeout function. The value of the Application
       Support Facility timeout is specified in field
       TIMEOUT in member FSNT000C (CICS) on library SFSNSRCE.
       Specify the value in minutes. The default is 60.
       If you specify zero, the Application Support Facility
       timeout function is switched off.
  
       If you use the Application Support Facility timeout,
       the NEP functions are also supported in case of an
       inactive Application Support Facility session.
  
     - CICS
  
       To fully support the timeout of a terminal, specify
       SIGNOFF=LOGOFF in the TCT definitions. If you specify
       SIGNOFF=LOGOFF, the terminal is logged off from CICS and
       afterwards from VTAM. The logoff from VTAM includes
       that the NEP is started. This means that the NEP
       functions are supported in case of a CICS timeout, too.
  
       If SIGNOFF=YES (CICS default) is specified, the terminal
       is only logged off from CICS and NEP is not started.
  
       For further information refer to the following manuals:
       CICS/ESA Resource Definition (Macro) 3.2.1 and
       CICS/ESA Resource Definition (Online) 3.2.1.
  
  6. Application Support Facility work data sets
     (USL, ISL, and ZSL)
  
     For a detailed description of these data sets refer
     to Chapter 1 "Overview of Application Support Facility
     administration" of the Application Support
     Facility Administration Guide.
  
     Delete and initialize the work data sets during
     CICS startup. Definitions and initializations
     are provided in the sample CICS startup
     job statements.
  
  7. Lost term exit DFHXTENF
  
     In an MRO environment with more than one AOR (Application
     Support Facility sample MRO configuration) the
     CICS terminal-not-found exit DFHXTENF must be
     implemented.
  
     To implement this, you need the following parts (all parts
     are generated during installation phase 2):
  
     - The modified CICS exit DFHXTENF
     - The CICS sample enable program FSNXTENF
     - Sample PLT table
     - PPT entry for PLT table (CICS Version 2 only).
  
  8. AFP PRINT
  
     If you want to use the remote print functions of
     Application Support Facility, do the following:
  
     - Set SPOOL=YES.
     - Set OSCOR greater than 120 000 bytes (CICS Version 2).
  
  9. PLIDUMP
  
     If you want to write a PLIDUMP to TRANSIENT DATA QUEUE,
     define this in your DCT either by specifying:
  
     CPLD    DFHDCT TYPE=EXTRA,DESTID=CPLD,DSCNAME=PLIDUMP
     PLIDUMP DFHDCT TYPE=SDSCI,DSCNAME=PLIDUMP,BLKSIZE=137,
                    RECSIZE=133,RECFORM=VARUNB,TYPEFLE=OUTPUT,
                    BUFNO=1
  
     or by specifying:
  
     CPLD    DFHDCT TYPE=INDIRECT,DESTID=CPLD,INDDEST=CPLI.
  
     To write a PLIDUMP to SYSOUT, add the following
     JCL statement to your CICS startup job:
  
     //PLIDUMP SYSOUT=*,DCB=(RECFM=V,BLKSIZE=137)
  
  10.LE/370
  
     If you run LE/370 1.2 under CICS 3.3 refer to
     LE/370 Installation and Customization, SC26-4817
     and to LE/370 Migration Guide, SC26-3118.
     You find additional information in APAR PN46894.
     LE/370 PTFs and cross product dependance PTFs must
     be installed depending on the customer's environment
     according to the LE/370 PSP-Bucket UPGRADE=LE370R120.
     CICS 3.3 APAR PN38032/PTF UN45348 is mandatory.
     Define programs as LE/370 to CICS.
  
       Use the following example to modify your Application
       Support Facility job FSNFLNK0 for final link of load
       modules. Change the library names if neccessary so that
       they fit in your system.
       Change the loadmodname marked by <======.
       //LKCIC1 EXEC PGM=HEWL,REGION=256K,
       //            PARM='LIST,XREF,RENT,AMODE=31,RMODE=ANY'
       //*
       //SYSLIB   DD DSN=SYS1.ADLE.SCEELKED,DISP=SHR
       //         DD DSN=SYS1.ADLE.SIBMMATH,DISP=SHR
       //         DD DSN=CICS330.SDFHLOAD,DISP=SHR
       //*
       //SYSLMOD  DD DSN=" FSNHLQ ".SFSNLOD0,DISP=SHR
       //*
       //SYSUT1   DD UNIT=SYSDA,SPACE=(TRK,(10,10))
       //SYSPRINT DD SYSOUT=*
       //*
       //SYSLIN DD *
       INCLUDE SYSLIB(CEESTART)
       INCLUDE SYSLIB(CEESG010)
       INCLUDE SYSLIB(DFHELII)
       REPLACE PLISTART
       CHANGE  PLIMAIN(CEEMAIN)
       INCLUDE SYSLMOD(FSNASF1)   <========  ASF loadmod
       ORDER   CEESTART
       ENTRY   CEESTART
       NAME FSNASF1(R)            <========  ASF loadmod
       /*
       .......
       .......
       .  Repeat the previous link step for each LOADMOD in your
          FSNLNK0.
          FSNLNK0.
       .......
       .......
  

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