PH48801: FAIL TO HANDLE EITHER A LF OR A CRLF AS THE LINE END OF CICS TAGGING FILE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The dump showed the lines had trailing spaces (x'20') on each
  line before the LF (X'0A').  Perhaps the trailing space in front
  of the LF or CRLF is the real problem.  Somehow in the copying
  of the yaml file the trailing space got on each line.  Normally
  Edit would get rid of a trailing space unless it is trying to
  preserve the length.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: CICS parsing of the cicstags.yaml file  *
  *                      fails to handle the case where the      *
  *                      carriage return byte has been replaced  *
  *                      by a space character.                   *
  ****************************************************************
  CICS will parse a buffer created from reading through the
  cicstags.yaml file during initialisation. It expects each line
  to terminate with a carriage return followed by a line feed. In
  UTF-8 this means a 0D followed by an 0A. In the customer's case,
  something was affecting their edit environment such that the
  CR byte was being replaced by a blank (20).
    The parsing code in DFHPATP encountered the 1.0.0 within the
  part of the file data containing:
  schemaVersion: regionTagging/1.0.0
  regiontags:
    Having confirmed the 1.0.0 matched as expected, it next wanted
  to check for the regionTags: string. However, the next byte in
  the buffer from the customer was a space, not a CR. This meant
  the logic failed to reposition to the start of the next logical
  line within the buffer, by skiping over the following two bytes.
  (normally a CR then LF). Instead the code pointed at the LF byte
  at the end of the previous line. Since this did not match the
  expected string of "regiontags:" the parsing failed. CICS issued
  message DFHPA2214 (a regiontags label has not been found).
  

Problem conclusion

• DFHPATP has been changed to accept the potential for a line of
  yaml to terminate with a space character before a line feed
  byte.
  

Temporary fix

Comments

APAR Information

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

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

  UI83022

Modules/Macros

• DFHPATP
  

Fix information

• Fixed component name

  CICS TS Z/OS V6

• Fixed component ID

  5655YA100

Applicable component levels

• R400 PSY UI83022

     UP22/10/27 P F210

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.