IBM Support

PI92905: TSO SERVICE SUPPORT REMOTE SYSTEM

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • TSO SERVICE SUPPORT REMOTE SYSTEM
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of IBM z/OS Management Facility Version 2 Release  *
    * 3, HSMA230.                                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * z/OSMF TSO/E address space services is                       *
    * enhanced to support start TSO/E address space in remote      *
    * system                                                       *
    * and run TSO application in remote system in the sysplex.     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    z/OSMF REST TSO/E address space services allows caller to start
    TSO/E address space and run TSO application via REST API.
    Previously, it can only start TSO/E address space in the local
    system in which z/OSMF is running. With this APAR, TSO/E address
    
    space services is enhanced to support starting TSO/E address
    space and running TSO application in remote system in the
    sysplex.
    
    An additional parameter ?system? is added to the START TSO/E
    Address Space REST request, users who want to start a TSO
    address space on a remote system should provide the parameter,
    otherwise the address space will still be started in the local
    system. A remote system name and a connection handler will be
    returned to the caller, connection handler is a 100-byte binary
    key in Hex format string, it is used for callers to perform
    further operations with remote TSO address space.
    
    Start or reconnect to a TSO/E address space, you need to add
    a new parameter:
    system: The system name in the sysplex
    It is an optional parameter, for local TSO address space,
    this parameter is not needed.
    
    Return Value (or Return and reason code):
    In addition to the existing fields of the return data, two
    new fields will be added, if you are starting a remote
    TSO/E address space:
    1. remoteSys
    The value is system name of the remote system on which
    the user wants to start the address space.
    
    2. ceatsoconn
    The value is a Hex string of 100-byte binary key, it is
    a key for callers to perform further operations with
    remote TSO address space.
    
    If exploiters of z/OSMF REST TSO/E address space
    services have their own TSO/E backend application,
    it?s possible that they use an existing logic to get
    the message queue id from storage for a local TSO
    system. The same logic doesn?t work for remote TSO
    system, the message queue id on remote system could
    not be obtained by that logic.
    
    Exploiters who want to send/receive messages with
    remote TSO/E system outside z/OSMF TSO services could
    use the CEA APIs with the raw binary value returned
    by ?ceatsoconn?.
    
    The current field ?servletKey? will be updated to add the
    remote system name, ZOSMFAD-SY2-55-aaakaaac, if the remote
    system name doesn?t exist in the servletKey, the address
    space started with the key is still on the local system.
    
    Please refer to <IBM z/OS Management Facility Programming
    Guide> for details of z/OSMF REST TSO/E address space
    services.
    

Problem conclusion

Temporary fix

Comments

  • See problem summary.
    

APAR Information

  • APAR number

    PI92905

  • Reported component name

    Z/OSMF CORE

  • Reported component ID

    5655S28SM

  • Reported release

    230

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2018-01-25

  • Closed date

    2018-03-13

  • Last modified date

    2018-04-04

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

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

    UI54411

Modules/Macros

  • IZUGNACS IZUGNACR IZUGNACZ
    

Publications Referenced
SC27841930SC27842030   

Fix information

  • Fixed component name

    Z/OSMF CORE

  • Fixed component ID

    5655S28SM

Applicable component levels

  • R230 PSY UI54411

       UP18/03/29 P F803  

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.

[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"230","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"230","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 April 2018