IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Add a new idea Subscribe
Status Not under consideration
Workspace CICS Transaction Server for z/OS
Categories Runtime
Created by Guest
Created on Mar 29, 2013

RELATED IDEAS

XRMIOUT exit invoked because of an EXEC DLI command issued by a program that was Cobol called needs a way to determine RSA

The situation:
1) The Initial Program of a CICS transaction, or a program that was invoked by EXEC CICS LINK or EXEC CICS XCTL, does a Cobol Call to invoke a ProgramB.
2) This ProgramB does an EXEC DLI call.
3) There is a Global User Exit program that is enabled to run at the XRMIOUT exit. This program program wants to determine what program made the EXEC DLI call
.
The problem: There is no supported way for the exit program in this situation to determine that it was ProgramB that made the EXEC DLI call.
.
What is needed: There needs to be a supported way for the exit program to determine the program that made the EXEC DLI call.
.
Some details:
1) XPI call DFHPGISX Function(INQUIRE_CURRENT_PROGRAM) will return the name of the CICS application program that made the Cobol Call to ProgramB. It will not return the name of the program that made the EXEC DLI call in this case.
.
2) UEPHMSA can normally be used by a XRMIOUT to access the RSA of the program that made the External Resource Manager call. Then R14 could be accessed from that RSA. Backing up from there it is possible to figure out what program made the call. But this doesn't work for EXEC DLI calls because CICS uses two TRUEs (DFHEDP 1st and then DFHDBAT) for EXEC DLI calls. That is why UEPHMSA doesn't address the RSA of the program that made the EXEC DLI call.
.
There needs to be something like perhaps a new function for the DFHPGISX XPI call.... something like Invoking_Program_RSA that will always return the RSA of the invoking program even when the invoking program did an EXEC DLI call.

Idea priority High
  • Guest
    Reply
    |     Oct 5, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Transaction Processing
    Product - CICS Transaction Server

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - CICS Transaction Server

  • Guest
    Reply
    |     Apr 4, 2013

    With Dan's agreement, I think we will reject this RFE and start over with a resh one, doumenting the problem seen by the customer.

  • Guest
    Reply
    |     Apr 3, 2013

    I have been straightened out. We can and do successfully use the TRUE's UEPHMSA when XRMIOUT is driven for the DLI (DFHEDP) TRUE. So we are all set for EXEC DLI calls. But the problem is with applications that use the DLI Call interface (i.e. Call CBLTDLI). Using that interface, the DLI (DFHEDP) TRUE is not involved. So for that interface, XRMIOUT is only driven for the DBCTL (DFHDBAT) TRUE. It is for that interface that we have no supported to way to use an XRMIOUT program to access the calling application's RSA.

  • Guest
    Reply
    |     Apr 1, 2013

    You need to look at the TRUE's UEPHMSA for the TRUE with name DLI (ie DFHEDP) rather than DBCTL (DFHDBAT)

  • Guest
    Reply
    |     Apr 1, 2013

    I am looking at the UEPHMSA in the DFHUEPAR for the TRUE. In the DFHUEPAR for XRMIOUT, UEPTRUEN is the address of characters 'DBCTL ' and UEPTRUEP addresses the DFHUEPAR for that TRUE.

  • Guest
    Reply
    |     Mar 31, 2013

    Which UEPHMSA are you looking at ? There is one for a GLUE and one for a TRUE. XRMIOUT will get invoked twice, once for DFHDBAT and once for DFHEDP.  One of the parms passed to the XRMIOUT GLUE as well as its own DFHUEPAR plist is the DFHUEPAR plist for the TRUE just invoked. I would expect UEPHMSA in the TRUEs (DFHEDP's) plist to point back to the application.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.