II08342: CHANGES TO AD/CYCLE LE/370 INSTALLATION AND CUSTOMIZATION GUIDE,SC26-4817-03, NOT IN THE RELEASE 3 GA MANUAL

APAR status

• INTRAN

Error description

• This APAR documents changes to the "IBM SAA AD/Cycle
  Language Environment/370 Installation and Customization Guide"
  which were not included in the Release 3 (fourth) edition.
                * SC26481703 * 568819801 * R310
                  Last changed :  January 10, 1996
  ================================================================
  Change Record: PN56000
  Change Description: New change information.
  Page Number: vii
  Old Text: -none-
  New Text: This book updates LE/370 Release 1.3 documentation.
         Technical changes from this release are indicated by a
         plus (+) sign in the left margin. Included are changes
         from:
           o APAR PN54638 with the related PTFs:
             - UN60632 (for FMID HMWL310)
             - UN60633 (for FMID JMWL31B)
             - UN60634 (for FMID JMWL31D)
           o APAR PN53485 with the related PTFs:
             - UN58467 (for FMID HMWL31F)
             - UN58468 (for FMID JMWL35D)
             - UN58557 (for FMID JMWL350)
           o APAR PN56000
           o APAR PN55785
  ================================================================
  Change Record: PN56000
  Change Description: New entries to "Major Changes in Release 3"
  Page Number: xi
  Old Text: -none-
  New Text: o The TRACE run-time option is new. The TRACE run-time
              option activates and controls the LE/370 run-time
              library trace.
            o Multithread dumps are now supported by the CEE3DMP
              callable service.
            o The _CEE_RUNOPTS environment variable is new. You
              can use _CEE_RUNOPTS to specify run-time options
              for C/370 applications invoked by one of the exec
              family of functions.
  ================================================================
  Change Record: PN56000
  Change Description: Change item 3 in run-time options precedence
  Page Number: 12 and 82
  Old Text: Options specified on invocation.
  New Text: Options specified on invocation (or in the case of an
            application invoked by one of the exec family of
            functions, options specified in the environment
            variable _CEE_RUNOPTS). See LE/370 Programming Guide
            for more information about _CEE_RUNOPTS.
  ================================================================
  Change Record: PN56000
  Change Description: New entry in figure 3 and 14
  Page Number: 14 and 83
  Old Text: -none-                                    col.72--v
  New Text: TRACE=((OFF,4K,DUMP,LE=0),OVR)                    X
  ================================================================
  Change Record: PN56000
  Change Description: Changes to Table 8 and new note.
  Page Number: 17
  Old Text:         Space Needed..(dec)   Space Needed..(hex)
   LE/370 base      1,266,000             881,000
  New Text:
   LE/370 base      1,188,000             959,000
  ______________________________________________________________
   Note: These requirements reflect the amount of storage needed
   if you include all eligible modules from the listed components
   in your LPA or ELPA. For a list of each module's storage
   requirements and the modules recommended for inclusion in the
   LPA or ELPA, see Appendix B, "Modules Eligible for the Link
   Pack Area" on page 185.
  ================================================================
  Change Record: PN56000
  Change Description: Correct zone names in text for CEEWDDDF.
  Page Number: 29
  Old Text: If you have changed the default names (CEETGT3 and
            CEEDLB3) for the ..
  New Text: If you have changed the default names (CEETGT4 and
            CEEDLB4) for the ..
  ================================================================
  Change Record: PN56000
  Change Description: New pages documenting CEEEXTAN and CEE*DATX
                      Abnormal Termination Exits
  Page Number: after page 66
  Old Text: -none-
  New Text: CEEEXTAN is a CSECT explicitly linked with the LE/370
     condition handling routines, and it is the CSECT that you
     create by coding the CEEXAHD, CEEXART, and CEEXAST macros.
     Specifically, CEEEXTAN is linked with the LIBPACKs CEEBINIT,
     CEECCICS, CEEPIPI, and CEEPICI. The CSECT is created through
     the use of the following LE/370-provided assembler macros:
     CEEXAHD   Defines the header of the table
     CEEXART   Identifies the name of the abnormal termination
                exit to be invoked
     CEEXAST   Identifies the end of the list of abnormal term-
                ination exits
     LE/370 validates the format of the abnormal termination exit
     CSECT and issues a load of the names as identified in the
     table. The LOAD is attempted only for terminations due to
     unhandled conditions of severity 2 or greater. If the LOAD is
     successful, a abnormal termination exit is invoked according
     to the interface described below. If the LOAD fails (the
     routine cannot be found, or there is not enough storage for
     the routine, for example), no error indication is delivered
     and either the next name in CEEEXTAN is chosen or termination
     continues (if the names have been exhausted). This allows a
     STEPLIB to either contain or omit the load names.
     CEEXAHD Macro
     CEEXAHD generates the CSECT statement and any header infor-
     mation required. It has no operands.
     CEEXART Macro
     CEEXART generates one entry for an abnormal termination exit.
     It has only one keyword parameter, TERMXIT=, which is the
     load name for the abnormal termination exit. There is a
     limit of 8 characters for the load name, and no validation
     of the name is performed by the macro. More than one
     invocation of CEEXART can appear in the CEEEXTAN CSECT,
     thus allowing multiple abnormal termination exits to be
     registered. When more than one name is specified, the
     abnormal termination exits are honored in the order found in
     the CEEEXTAN CSECT.
     CEEXAST Macro
     CEEXAST generates the trailer for the CEEEXTAN CSECT. It has
     no parameters.
     Installation Jobs to Generate and Modify CEEEXTAN CSECT
     You can use two source files to generate CEEEXTAN CSECT, one
     for CICS and one for non-CICS. The following source files
     are provided in the SCEESAMP data set:
      CEECXTAN  Source to generate CEEEXTAN CSECT for CICS
      CEEEXTAN  Source to generate CEEEXTAN CSECT for non-CICS
     You can use the following two jobs to modify CEEEXTAN CSECT:
      CEEWCEXT  Replaces CEEEXTAN CSECT for CICS
      CEEWDEXT  Replaces CEEEXTAN CSECT for non-CICS
     The IBM supplied CEEEXTAN does not specify any abnormal
     termination exits.
     Sample Abnormal Termination Exits
     LE/370 provides source for sample abnormal termination exits
     for both CICS and non-CICS environments. These exits can
     provide system abend dumps or, under CICS, transaction dumps
     to help you diagnose problems. The sample batch abnormal
     termination exit is CEEBDATX. The sample CICS abnormal
     termination exit is CEECDATX. You can find both sample exits
     in the CEESAMP data set.  (The code for CEEBDATX and
     CEECDATX was shipped with APAR PN54638.)
  
     You can edit these sample exits to change or add to the
     functions performed, then assemble and link-edit them into a
     library that LE/370 can access at run-time. You must also
     code a CEEEXTAN CSECT that contains a CEEXART macro that in
     turn nominates your routine as a abnormal termination exit.
     Finally, you must replace CEEXTAN in LE/370, as described in
     "Installation Jobs to Generate and Modify CEEEXTAN CSECT".
  ================================================================
  Change Record: PN56000
  Change Description: New text in first paragraph
  Page Number: 85
  Old Text: You can run the customization EXEC, C5688198, to
          update the assembler user exit CEEBXITB, which is
          contained in the CEEBXITA ORIGINAL. The EXEC places you
          into an XEDIT session where you can modify the exit.
  New Text: You can customize the assembler user exit by invoking
          the C5688198 (customization) EXEC and selecting option
          2, which puts you into an XEDIT session of CEEBXITB
          ASSEMBLE. After you complete your changes and file them,
          C5688198 assembles the file and, if no errors occur,
          issues a prompt to rebuild the required module.
  ================================================================
  Change Record: PN56000
  Change Description: Changes to NSS eligible module lists.
  Page Number: 85
  Old Text: ..only in NSSs below 16M:
  (remove)    EDCZ24
            .......in NSSs above 16M:
              EDCNINSP
  New Text: ..only in NSSs below 16M:
  (add)       IBMRPTLA
            .......in NSSs above 16M:
              CEEMJPN5
              EDCNSS01
              EDCNSS02
              EDCNSS03
  ================================================================
  Change Record: PN63666
  Change Description: New chapter for LE/370 library routine
                      retention
  Page Number: 174
  Old Text: -none-
  New Text:
  
   USING LE/370 LIBRARY ROUTINE RETENTION TO IMPROVE PERFORMANCE
   ON IMS/DC
  
   If you are running programs in an IMS/DC dependent region (such
   as an IMS message processing region) that require LE/370, you
   can get an improvement in performance if you use LE/370 library
   routine retention along with the existing PREINIT feature
   of IMS/DC.
  
   When library routine retention is used, LE/370 keeps certain
   LE/370 resources in memory when an application program ends.
   By keeping certain resources in memory, subsequent invocations
   of programs that use LE/370 is much faster since the LE/370
   resources left in memory are reused.
  
   When library routine retention is used, the resources that
   LE/370 keeps in memory includes the following:
   o   LE/370 run time load modules
   o   LE/370 storage associated with the management of the run
       time load modules
   o   LE/370 storage for start-up control blocks
  
   In order to use LE/370 library routine retention in an IMS
   dependent region, you must do the following:
   o   In your JCL or procedure used to bring up IMS dependent
       regions, specify that you want IMS to invoke dependent
       region preinitialization routines.  This is done by
       specifying a suffix on the PREINIT keyword of the IMS
       dependent region procedure.
   o   In the DFSINTxx member of IMS.PROCLIB (where xx is a suffix
       specified by the PREINIT keyword), include the name
       CEELRRIN.
  
   When the module CEELRRIN is invoked by IMS, LE/370 library
   routine retention is initialized.
  
   NOTE:  The source for module CEELRRIN is available in the
   SCEESAMP library in member CEELRRIN.  If this source does not
   meet the needs of your shop, you can create your own assembler
   program to initialize LE/370 library routine retention. If you
   create your own load module to initialize LE/370 library
   routine retention, you will need to put the name of the module
   in the DFSINTxx member.
  
   NOTE:  LE/370 also provides a routine called CEELRRTR to
   terminate library routine retention.  However, this routine
   does not need to be used when running on IMS/DC.  If library
   routine retention is initialized, and the IMS Program Control
   Task is terminated (for example, due to an ABEND), the
   operating system will free the LE/370 resources as part of task
   termination.
  
   Then when the IMS Program Control Task is reattached, the
   preinitialization routines get control before IMS scheduling is
   attempted.
  
   For more information about specifying IMS dependent region
   preinitialization routines, see the IMS/ESA CUSTOMIZATION
   GUIDE: SYSTEM.
  
   For more information about LE/370 library routine retention,
   see the LE/370 PROGRAMMING GUIDE update in information APAR
   II08343.
  ================================================================
  Book Title: LE/370 Installation and Customization Guide
  Version: Release 3                         SC26-4817-03
  Pages: 36, 39
  -
  Change Description for Information APAR II08342: When
  installing LE/370, expect MsgIEW0461.
  -
  Replace the paragraph beginning "You receive ..." with:
  "If you are installing one of these components, expect to see
  a condition code of 04. Unresolved external references may
  occur as follows.
   -
  If installing   then for load    unresolved references to these
  product ...     module ...       external names may occur ...
  ---------------------------------------------------------------
  COBOL           ILBOxxxx        ILBOxxxx, IEDxxxx
                  IGZxxxx         CEExxxx, IGZxxxx
  -
  PL/I            IBMxxxx         IBMxxxx, CEExxxx, DFHxxxx
                  CEESG010        CEExxxx, IBMxxxx
                  PLISTART        CEExxxx
  -
  AD/Cycle C/370  CEEEV003        @@EMSGS
  -
  The following messages appear."
  -
  Replace the DFSMS Binder message number with IEW2454W.
  ===============================================================
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

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