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 Not under consideration
Categories Other
Created by Guest
Created on Apr 14, 2014

CICS Web Services Assisant.

From the created COPYLIB member:
* Comments for field 'OriginSPLC':
* This field represents the value of XML element
* '/RateRankRequest/RatingRequest/ShipHeaderInfo/OriginSPLC'.
* XML data type: 'string'.
* XML 'whiteSpace' facet value: 'preserve'.
* XML 'pattern' facet value: '((0-9){9})'.
* This field contains a varying length array of characters or
* binary data.
* 09 OriginSPLC-length PIC S9999 COMP-5 SYNC.
* 09 OriginSPLC PIC X(255).
*


--------------------------------------------------------------------------------
From the DFHWS2LS log:
Processing element: #OriginSPLC type namespace: null
Processing simple type: http://eta.sddc.army.mil/xsd/raterankrequest#OriginSPLC_._type typeName: OriginSPLC
Found simple type derived from: string
Type is: null#OriginSPLC
XPATH is: +++http://eta.sddc.army.mil/xsd/raterankrequest~~~RateRankRequest+++null~~~RatingRequest+++null~~~ShipHeaderInfo+++null~~~OriginSPLC
Default value is: null
is aligned: true
are widechars: false
facet: whiteSpace value: preserve
facet: pattern value: ÝÝ0-9¨{9}¨
Adding entry for 'length for OriginSPLC' for type 'NUMERIC' and language 'COBOL' of length '2' and required alignment 'HALF-WORD' at offset '504' with mapping strategy 'NOT APPLIC' to level '-881338832'.
Adding entry for 'OriginSPLC' for type 'TEXT' and language 'COBOL' of length '255' and required alignment 'BYTE' at offset '506' with mapping strategy 'VARYING_ARRAY' to level '-881338832'.

in isStructuralElement(particle, false) content is of type: org.eclipse.xsd.impl.XSDElementDeclarationImpl
= 1 maxOccurs = 1 isComplex = false delegate = null
in isMixedContent(particle) content is of type: org.eclipse.xsd.impl.XSDElementDeclarationImpl
Particle must appear 1 to 1 times.
is structural: false
is mixed: false
supress padding message: true


--------------------------------------------------------------------------------
From XSD file:
<xs:element name="OriginSPLC">
<xs:annotation>
<xs:documentation>Host validation: 'SPLC'</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="[0-9]{9}"/>
</xs:restriction>
</xs:simpleType>
</xs:element>

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
    |
    May 19, 2014

    The "pattern" facet in XML is for specifying a Regular Expression against which the contents of an XML element must match, for validation purposes. Any Regular Expression is valid, though this requirement only asks for validation of the length. There are other (better) ways to define the maximum length of a field in an XML schema. The example quoted requires the contents to be numeric, something that could be enforced by using a more specific data-type (an xsd:integer with totalDigits=9 comes to mind, rather than an xsd:string and a Regular Expression), and which would map appropriately.

    At the moment we have no support in the CICS data transformation/mapping service for Regular Expression based validation. We tolerate the presence of Regular Expressions in the Schema, but don't do anything with them, other than echoing them into the generated copy-books for informational purposes. Looking at current plans, it is not likely that this would be implemented in the next two CICS TS releases, so correspondingly this requirement is being rejected. You have an opportunity to resubmit in eighteen months time if you wish it to be considered then.