PI51532: INVALID GUR CALL RESPONSE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• During tests with DFSMAP / DFSCASE statements in a DBD a GUR
  call
  results in an invalid XML response. The mapping information was
  placed
  within a XDFLD element in the GUR response.
  .
  DBD coding around the error area is:
  FIELD NAME=(IBAN),
        EXTERNALNAME=IBAN,
        BYTES=34,
        START=22,
        TYPE=C,
        DATATYPE=CHAR.
  LCHILD NAME=(ACCIDXI,BANKCUS2),
        POINTER=INDX.
  XDFLD NAME=IBANXDF,           <- new xdfld
        EXTERNALNAME=INDEX_ON_IBAN,
        SRCH=IBAN.
  FIELD NAME=(ACCTYPE),
        EXTERNALNAME=ACCOUNT_TYPE,
        BYTES=30,
        START=56,
        TYPE=C,
        DATATYPE=CHAR.
  FIELD NAME=(CURRENCY),
  .
  XML coding
  <field>ACCNO</field>
  </search>
  </xdfld>  <-- end looks to be misplaced
  </lchild>
  <lchild dbd="BANKCUS2" pointer="INDX" name="ACCIDXI">
  <xdfld name="INDEX_ON_IBAN" imsName="IBANXDF">   <-- looks to
  misplaced
  <search>
  <field>IBAN</field>
  </search>
  <mapping dependingOnField="ACCOUNT_TYPE" name="ACCOUNT_MAPS">
  <case name="GIRO_ACCOUNT_MAP">
  

Local fix

• No.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All IMS V14 users with the IMS catalog                       *
  * enabled using the IMS Explorer to generate                   *
  * DBD source.                                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The XML document generated with the                          *
  * GUR DL/I call contains misplaced xdfld                       *
  * and lchild end tags                                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * INSTALL CORRECTIVE SERVICE FOR APAR/PTF                      *
  ****************************************************************
  The IMS catalog contains all of the information decoded from
  the runtime control blocks used by IMS. The constructed module
  DFS3GUR1 builds the XML document during a GUR call however the
  xdfld and lchild tags are misplaced.
  During the construction of the XML tags, the opening
  tags of the lchild and xdfld tags were created.
  However, before the lchild and xdfld tags closed, the
  segment_name changed to Map which intialized the start of the
  mapping tag. This resulted in the incorrect placement of the
  mapping tags inside the xdfld and lchild tags.
  

Problem conclusion

• DFS3GUR1
  Code has been added to detect the change of the segment_name
  to Map concurrently with the the lchild_cont and xdfld_cont
  flags still turned on. If this case is reached, the end tags
  of the xdfld and lchild_cont will be set before the starting
  map tag is set.
  

Temporary fix

Comments

APAR Information

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

  PI42341

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

  UI37797

Modules/Macros

• DFS3GUR1
  

Fix information

• Fixed component name

  IMS V14

• Fixed component ID

  5635A0500

Applicable component levels

• R400 PSY UI37797

     UP16/05/16 P F605

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.