IBM Support

PH27154: SDSF REXX FUNCTION ISFQUERY() WILL NOT WORK WHEN AN EXEC IS RUN IN THE SDSF CLIENT IN SDSF V2R4.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • When using SDSF REXX under an SDSF client in V2R4
    (using it for a user action for example), the isfquery()
    function will not complete successfully. This is due
    to the limitation of one connect per address space TCBs
    to the SDSF sever in SDSF V2R4.
    

Local fix

  • As a work-around, the SDSF special DD ISFMIGRL can be
    allocated to avoid this problem.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of SDSF V2R4                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: No REXX special variables will be       *
    *                      created by the isfquery() function the  *
    *                      exec is invoked using the % action      *
    *                      character from a tabular panel.         *
    ****************************************************************
    The % action character invokes the REXX exec under a subtask.
    Although the user has connected to the SDSF server, the subtask
    has not.  As a result, isfquery() cannot retrieve any SDSF
    information since the task is not connected.
    

Problem conclusion

Temporary fix

Comments

  • The implementation of isfquery() needs to be changed to handle
    the case of being invoked under a subtask.
    This issue will be addressed in a future release of SDSF and
    is closed FIN.
    

APAR Information

  • APAR number

    PH27154

  • Reported component name

    SDSF

  • Reported component ID

    566548801

  • Reported release

    7C0

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-07-06

  • Closed date

    2020-08-03

  • Last modified date

    2020-08-05

  • 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

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"7C0","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 December 2020