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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
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
Closing as the customer's issue has been resolved.
Closing as the customer's issue has been resolved.
Hi,
Thank you for your update. I've forwarded the information to the customer and will update with their feedback.
The customer was setting up new WebServices when migrating to CICS 4.2 which must have required the need to run DFHWS2LS. With mapping-level of 3.0, we changed the xsd:datetime format returned to that of the CICS ASKTIME format:
http://pic.dhe.ibm.com/infocenter/cicsts/v4r2/topic/com.ibm.cics.ts.applicationprogramming.doc/datamapping/dfhws_hllxml_limitations.html
Re-running DFHWS2LS with DATETIME=STRING resolved the customer's issue.
Thank you,
Debbie McLaughlin
CICS Level 2
The XML specification requires that timestamps be serialized using ISO 8601 format. It's not possible for an xsd:dateTime to be in any format other than ISO 8601, so we don't understand why client side data representations are relevant. It doesn't matter what the client is, the data will always be in ISO 8601 format on the wire.
Is the customer aware of the EXEC CICS FORMATTIME command? It can be used to convert an ABSTIME field in to almost any representation that's desired.
Is the customer aware of the DATETIME=STRING parameter on DFHWS2LS? If that's used, DFHWS2LS doesn't attempt to map xsd:dateTime fields into ABSTIME at all.
The combination of one or both of the above technique ought to be sufficient to address everything that's being asked for in the requirement.
Lastly, why is the customer regenerating COBOL Web Service bindings as part of a CICS migration? That shouldn't be necessary! The old CICS mapping levels are still supported, so older Web Service programs will continue to work unchanged. DFHWS2LS continues to support every mapping level since Web Services were first introduced.