Skip to Main Content
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.

Status Delivered
Categories Runtime
Created by Guest
Created on Aug 10, 2012

CICS unable to process Webservice Requests after Warm Start

The problem is that CICS is shutdown and warm started within an active, high workload environment. As soon as CICS is up the TCPIPSERVICE, URIMAP, and PIPELINE resources are read from the catalog and installed. New Webservice work arriving at this time gets accepted because the URIMAP from the previous run of CICS is active and matches. The webservice request fails because the WEBSERVICE resource has not yet been installed. PIPELINE resolution occurs and a WEBSERVICE resource is created for each WSBIND file found. The previous URIMAPs just get reused if the WSBIND file is found to be unchanged. Only at this point will the webservice work run successfully.

The webservice work arriving before pipeline resolution will all fail with a DFHPI0500 message and abend APIG.

A design change needs to happen where CICS will either rejected or delay any webservice request until pipeline resolution has fully completed.

Idea priority Medium
  • 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
    |
    Jun 13, 2014

    This requirement is satisfied by CICS TS 5.2 which is generally available from June 13th 2014.
    The requirement can be addressed by utilising a cloud style deployment in CICS TS 5.2. For a webservice using the Cloud-style deployment, the URIMAP could be marked as an entrypoint. On recovery the application can be recovered back to an enabled state but would remain unavailable. This would allow all parts to become enabled in time, but return not_found 404 responses. The user can then make the application available, knowing that everything is in place and not receive intermediate abends.

  • Guest
    Reply
    |
    Jun 13, 2014

    This requirement is satisfied by CICS TS 5.2 which is generally available from June 13th 2014.

  • Guest
    Reply
    |
    Apr 14, 2014

    This requirement is satisfied by CICS TS 5.2 which was announced 7th April 2014 with a planned general availability date of June 13th 2014. For more information see the IBM CICS Transaction Server for  z/OS, V5.2 announcement letter

    http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS214-107

    The requirement can be addressed by utilising a cloud style deployment in CICS TS 5.2.  For a webservice using the Cloud-style deployment, the URIMAP could be marked as an entrypoint. On recovery the application can be recovered back to an enabled state but would remain unavailable. This would allow all parts to become enabled in time, but return not_found 404 responses. The user can then make the application available, knowing that everything is in place and not receive intermediate abends.

  • Guest
    Reply
    |
    Apr 9, 2014

    This requirement is satisfied by CICS TS 5.2 which was announced 7th April 2014 with a planned general availability date of June 13th 2014. For more information see the IBM CICS Tools for  z/OS, V5.2 announcement letter

    http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS214-107

    The requirement can be addressed by utilising a cloud style deployment in CICS TS 5.2.  For a webservice using the Cloud-style deployment, the URIMAP could be marked as an entrypoint. On recovery the application can be recovered back to an enabled state but would remain unavailable. This would allow all parts to become enabled in time, but return not_found 404 responses. The user can then make the application available, knowing that everything is in place and not receive intermediate abends.

  • Guest
    Reply
    |
    Jan 10, 2014

    This is something we would like to address. The RFE is being moved into 'Planned for Future release' status.  Please note:
    IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion.   Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.