Topic
  • 3 replies
  • Latest Post - ‏2013-06-04T08:04:02Z by RobJones
NenadV
NenadV
4 Posts

Pinned topic CICS request exit and DFHXCURM ?

‏2013-01-15T13:59:02Z |
Hello,

could someone explain if the CICS request exit introduced in CTG V8 can be used, beside IPIC, for EXCI as well .

This is what doc. says:

"The CICS request exit is part of the Gateway daemon and can be used for redirecting requests over EXCI or IPIC connections. Because the CICS request exit supports IPIC, you can use it to redirect ECI requests calling CICS channel based programs and ESI requests which are not supported over EXCI connections.

The DFHXCURM user replaceable module is used for redirecting requests over EXCI in a local mode topology. DFHXCURM cannot be used with IPIC connections."

I.e. is DFHXCURM still the only option for EXCI ?
Regards,
Nenad
Updated on 2013-02-18T13:21:02Z at 2013-02-18T13:21:02Z by RobJones
  • RobJones
    RobJones
    11 Posts

    Re: CICS request exit and DFHXCURM ?

    ‏2013-02-18T13:21:02Z  
    Hi Nenad,

    Apologies for the delayed response, I hope I can clear up any confusion.

    The CICS Request Exit can choose a target CICS server which can be either an IPIC server, defined in the Gateway daemon configuration file, or a CICS APPLID for connection using EXCI.

    DFHXCURM allows the target CICS APPLID to be changed for any DPL request using EXCI to access CICS TS, including CICS TG ECI requests. However, DFHXCURM is an EXCI exit point, and as such, CICS TG is unaware of any routing decision taken by DFHXCURM. It also means that DFHXCURM can not be involved in IPIC connectivity.

    For both of these reasons, CICS TG added the CICS Request Exit in V7.2, which allows routing decisions to be taken within the Gateway daemon. This allows selection of any supported CICS connection (EXCI, IPIC on z/OS) and means CICS TG knows where a request has been sent, allowing meaningful accounting through CICS TG statistics.

    Whilst it is possible for someone to use both CICS Request Exit and then have an DFHXCURM exit active within EXCI - this would be quite confusing and loses transparency in monitoring/statistics.

    You might consider reviewing SupportPac CA1T, which offers a pre-built CICS Request Exit offering a variety of configurable options:

    http://www-01.ibm.com/support/docview.wss?uid=swg24021484

    Also, since CICS TG for z/OS V8.1, there is a built-in feature called "DSSPOLICY", Dynamic Server Selection policy. This operates as an alternative to the CICS Request Exit, offering an easy way to configure round-robin or failover selection of CICS server without the need for any exit code.

    FYI - CICS TG for z/OS V9.0 is the latest release, Generally Available since December, 14th, 2012:

    http://tinyurl.com/cicstg90datasheet
    http://tinyurl.com/cicstg90announce

    Best regards,
    Rob Jones

    Raise a CICS TG requirement: http://ibm.biz/Bdxiga
    ______________________________________________________________________________________
    Rob C Jones - CICS Transaction Gateway Strategy and Technical Planning
    IBM United Kingdom Limited,
  • NenadV
    NenadV
    4 Posts

    Re: CICS request exit and DFHXCURM ?

    ‏2013-05-23T07:07:42Z  
    • RobJones
    • ‏2013-02-18T13:21:02Z
    Hi Nenad,

    Apologies for the delayed response, I hope I can clear up any confusion.

    The CICS Request Exit can choose a target CICS server which can be either an IPIC server, defined in the Gateway daemon configuration file, or a CICS APPLID for connection using EXCI.

    DFHXCURM allows the target CICS APPLID to be changed for any DPL request using EXCI to access CICS TS, including CICS TG ECI requests. However, DFHXCURM is an EXCI exit point, and as such, CICS TG is unaware of any routing decision taken by DFHXCURM. It also means that DFHXCURM can not be involved in IPIC connectivity.

    For both of these reasons, CICS TG added the CICS Request Exit in V7.2, which allows routing decisions to be taken within the Gateway daemon. This allows selection of any supported CICS connection (EXCI, IPIC on z/OS) and means CICS TG knows where a request has been sent, allowing meaningful accounting through CICS TG statistics.

    Whilst it is possible for someone to use both CICS Request Exit and then have an DFHXCURM exit active within EXCI - this would be quite confusing and loses transparency in monitoring/statistics.

    You might consider reviewing SupportPac CA1T, which offers a pre-built CICS Request Exit offering a variety of configurable options:

    http://www-01.ibm.com/support/docview.wss?uid=swg24021484

    Also, since CICS TG for z/OS V8.1, there is a built-in feature called "DSSPOLICY", Dynamic Server Selection policy. This operates as an alternative to the CICS Request Exit, offering an easy way to configure round-robin or failover selection of CICS server without the need for any exit code.

    FYI - CICS TG for z/OS V9.0 is the latest release, Generally Available since December, 14th, 2012:

    http://tinyurl.com/cicstg90datasheet
    http://tinyurl.com/cicstg90announce

    Best regards,
    Rob Jones

    Raise a CICS TG requirement: http://ibm.biz/Bdxiga
    ______________________________________________________________________________________
    Rob C Jones - CICS Transaction Gateway Strategy and Technical Planning
    IBM United Kingdom Limited,

    Hello Rob,

    thank you for your reply and clarification. We altered our configuration in a way you suggested and now we are hitting a problem described in this enhancement request (RFE):

    http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=33341

    Could you please comment ?

     

    Regards,

    Nenad 

     

  • RobJones
    RobJones
    11 Posts

    Re: CICS request exit and DFHXCURM ?

    ‏2013-06-04T08:04:02Z  
    • NenadV
    • ‏2013-05-23T07:07:42Z

    Hello Rob,

    thank you for your reply and clarification. We altered our configuration in a way you suggested and now we are hitting a problem described in this enhancement request (RFE):

    http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=33341

    Could you please comment ?

     

    Regards,

    Nenad 

     

    Hi Nenad,

    I have returned the RFE with some thoughts, and some questions.

    Best regards,
    Rob Jones

    Raise a CICS TG requirement: http://ibm.biz/Bdxiga
    ______________________________________________________________________________________
    Rob C Jones - CICS Transaction Gateway Strategy and Technical Planning
    IBM United Kingdom Limited