PI60924: OM XML INPUT IS LIMITED TO 16 MEGABYTES IN LENGTH

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Due to an internal limitation within OM, the output of a command
  processed by OM is limited in length to 16 megabytes.  If the
  output exceeds this limit, it is simply truncated, leading to
  incorrect output and possibly an ABEND0C4 or other abend in the
  address space that issued the command (e.g., SPOC).
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of IMS v14 Operations Manager or TSO SPOC.         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * OM command output is truncated if it is longer than 16777216 *
  * bytes (16MB).                                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * INSTALL CORRECTIVE SERVICE FOR APAR/PTF                      *
  ****************************************************************
  When a Type 2 command is sent to OM via TSO SPOC, and the
  XML output produced by this command exceeds 16,777,216
  bytes in length, the command will fail with one of several
  possible failure scenarios.  These include, but are not
  limited to:
  
  - Expected response lines are missing from the TSO SPOC display
  - TSO SPOC displays an internal error "Get output buffer or
  parser error     rc='49285650'x      rea='59000000'x"
  - TSO SPOC displays return code 08000014 and reason code
  00004000.
  In addition, the message "CSLM053E DFSSPOC severe error -
  getmain failed."
  
  In all cases, the root cause is the same -- the XML command
  output
  from OM is truncated at a certain point, and SPOC encounters an
  error while trying to process this truncated XML.
  

Problem conclusion

• There are two separate points in the code that contribute to
  the truncation of OM command output XML:
  
  1.  In all places where OM internally moves command response
  data from one buffer to another, the code uses an MVCL assembler
  instruction to perform the move.  The MVCL instruction
  does not support buffer lengths above 16MB.  If an attempt
  is made to use MVCL for a longer buffer, it copies only a
  portion of the data.  These MVCL instructions are replaced with
  MVCLE, which supports operands up to 2GB in length.
  
  2.  Like OM, SPOC internally moves command output XML from
  one buffer to another using MVCL.  These are changed to use
  MVCLE.
  
  
  Modules changed
  ---------------
  CSLOCM00, CSLOCR00, CSLOCR10, CSLOOUT0 - When copying OM
  response data
  from one buffer to another, use the MVCLE instruction instead of
  MVCL
  
  CSLULCM2, CSLULCM6 - Following the call to CSLOMCMD, the OM
  command
  response is copied into a new buffer using MVCLE instead of
  MVCL.
  
  CSLULCMX - This module contains commented-out code that uses
  MVCL to
  copy OM response data into a new buffer.  A comment is added to
  document this to avoid introducing a defect if and when the
  commented-out code is used in the future.
  

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:

  UI39692

Modules/Macros

• CSLOOUT0 CSLOCR00 CSLOCR10 CSLOCM00 CSLULCM2 CSLULCMX CSLULCM6
  

Fix information

• Fixed component name

  IMS V14

• Fixed component ID

  5635A0500

Applicable component levels

• R400 PSY UI39692

     UP16/07/29 P F607

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.