PM34280: CALLS TO APL2 WILL NOT INITIALIZE WHEN TSO IS NOT PRESENT

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When attempting to use APL2PI (Calls to APL2) from an
    environment where TSO is not running, return code 0 5 is
    recevied from the initialization call.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of Calls to APL2 (APL2PI) in           *
    *                 the MVS/TSO environment.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: APL2 requires that APL2PI be            *
    *                      invoked under the TSO Terminal          *
    *                      Monitor Program, IKJEFT01.              *
    *                      Invoking it from any other              *
    *                      environment results in an error         *
    *                      return code from the                    *
    *                      initialization call.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    APL2PI contained only rudimentary checks for the presence of
    TSO.  It contained no code to support being called under the
    TSO Environment Service (IKJTSOEV) nor to start the TSO
    Environment Service if not already present.
    

Problem conclusion

  • APL2PI is modified so that in addition to detecting the
    presence of IKJEFT01, it will also detect the presence of
    IKJTSOEV.  If neither is present, APL2PI will call IKJTSOEV
    to start the TSO environment before initializing APL2.
    
    Notes & Restrictions:
    
     - When APL2PI calls IKJTSOEV to start TSO, the TSO
       environment will persist until the address space
       terminates.
    
     - When running in the IMS Message Processing Region, APL2PI
       can only be used once to initialize APL2. APL2PI starts
       TSO sucessfully using IKJTSOEV on the first call, but on
       subsequent calls it is unable to successfully reconnect
       with that TSO environment.
    
     - Programs running under the z.OS Unix shell can call APL2PI
       if three conditions are met:
       1. If the TSO command OMVS is used to start the shell, the
          OMVS SHAREAS option must be used to force OMVS to use
          the TSO address space.
       2. The _BPX_SHAREAS environment variable must be set to YES
          so the shell does not start a new address space for the
          program.
       3. The program must be a shell program. It cannot be a link
          to a module in a load dataset.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM34280

  • Reported component name

    APL2

  • Reported component ID

    566889901

  • Reported release

    222

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-03-07

  • Closed date

    2011-05-12

  • Last modified date

    2011-06-02

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

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

    UK67668

Modules/Macros

  •    AP2TAPI
    

Fix information

  • Fixed component name

    APL2

  • Fixed component ID

    566889901

Applicable component levels

  • R222 PSY UK67668

       UP11/05/17 P F105

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

APL2
Mainframe APL2

Software version:

222

Reference #:

PM34280

Modified date:

2011-06-02

Translate my page

Machine Translation

Content navigation