PK34015: DFHLS2WS GENERATES 4 BYTE FIELD FOR COBOL COMP FIELD IF COMP APPEARS BEFORE PIC CLAUSE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When running DFHLS2WS to convert a COBOL language structure to a
  WSDL, both the following are valid COBOL definitions to define a
  two byte binary field:
  03 TESTAREA    COMP PIC S9(4).
  03 TESTAREA    PIC S9(4) COMP.
  However, in the first case, where COMP appears before the PIC
  clause, DFHLS2WS incorrectly generates a 4 byte field.  In the
  second case, where COMP appears after the PIC clause (which is a
  more common coding practice) then DFHLS2WS will correctly
  generate a 2 byte field.
  

Local fix

• Temporarily change COBOL language structure so that COMP appears
  after the PIC clause instead of before.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: DFHLS2WS does not convert a COBOL       *
  *                      binary field correctly if COMP appears  *
  *                      before PICTURE in the field definition. *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When DFHLS2WS is being used to convert a COBOL data structure to
  a wsbind file, the PICTURE clause is expected to appear first in
  the definition of each field. If COMPUTATIONAL or BINARY is
  specified before PICTURE, it is ignored, and the definition is
  mapped as a DISPLAY field instead of binary. For example, a
  field specified as COMP PIC S9(4) is mapped as a 4-byte numeric
  DISPLAY field instead of a 2-byte binary field.
  
  This leads to problems in the implementation of the web service
  provider application, because the incoming soap request does not
  match the COBOL data structure. The symptoms of the problem will
  depend on where the mismatch occurs, but can include messages
  DFHPI1007, DFHPI1008, DFHPI1009 or DFHPI1010, or the LENGERR
  condition on the GET CONTAINER command.
  
  Additional keywords: abendAEIV AEIV MSGDFHPI1007 MSGDFHPI1008
  MSGDFHPI1009 MSGDFHPI1010
  

Problem conclusion

• DFHLS2WS has been modified to correctly parse variable
  declarations that specify the 'COMP' or 'COMPUTATIONAL'
  USAGE clause before the PICTURE clause.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UK20318

Modules/Macros

•    DFJ@H176
  

Fix information

• Fixed component name

  CICSTS 3.1 Z/OS

• Fixed component ID

  5655M1500

Applicable component levels

• R40D PSY UK20318

     UP06/12/12 P F612

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.