PH31089: ENHANCEMENTS FOR OFF PLATFORM STREAMING

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Enhancements to IBM Z performance and capacity analytics
  off platform streaming service.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM Z Performance and Capacity Analytics     *
  *                 customers who perform streaming off          *
  *                 platform.                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1. Missing data rows when streaming     *
  *                         to Splunk or ELK.                    *
  *                      2. Splunk and ELK reports do not        *
  *                         display historical data.             *
  *                      3. Streaming very large volumes of      *
  *                         data via JDBC may cause performance  *
  *                         issues.                              *
  *                      4. Bad data causes the Forecaster to    *
  *                         terminate with an exception.         *
  *                      5. Data is occasionally duplicated.     *
  *                      6. The Publisher produces data that is  *
  *                         unreadable by ELK or Splunk.         *
  ****************************************************************
  * RECOMMENDATION: Apply the provided PTFs.                     *
  ****************************************************************
  1. When streaming the following views to off-platform locations
     such as Splunk or ELK some rows have duplicate keys
     resulting in lost data in the reports.
       KPMZ_JOB_INT_HV,
       KPMZ_JOB_STEP_TV
  
  2. Shadowing does not have a mechanism for streaming
     historical data, resulting in Splunk and ELK
     reports not displaying data for historical periods.
  
  3. If a configuration is created that uses a JDBC stage
     requesting millions of rows of data without providing an
     adequate .split definition, then the Forecaster will
     acquire significant memory which may have an adverse
     impact on the system.
  
  4. The Forecaster terminates unexpectedly if it
     processes a badly formed data packet.
  
  5. An internal stage outputs data from each packet twice.
  
  6. The supplied sample Publisher configuration specifies
     code page IBM-1047, which is not compatible for
     ingestion by Splunk and ELK.
  

Problem conclusion

• 1. Mapping key file DRLJMTVK is updated with the correct key
     values for the views:
       KPMZ_JOB_INT_HV
       KPMZ_JOB_STEP_TV
  2. The sample configuration ShadowerRange.properties is
     added to the Forecaster. There are two mechanisms that allow
     the shadowing of older data:
     a) .initial=ALL shadows all historical data in a table
        or view.
     b) .initial=RANGE allows a specific time range to be
        shadowed.
        Update the from and to values for each table/view. For
        example:
          input.1.table.1.initial = RANGE
          input.1.table.1.range.from  = 2020.06.01 00:00:00
          input.1.table.1.range.to    = 2020.11.01 00:00:00
  3. A parameter is added to the JDBC stage that specifies the
     maximum number of whole lines that the stage can process.
     The default value is 500,000. This can be altered by
     specifying:
        .max_records = nnnnn
     If the number of lines is reached, the Forecaster issues
     an error message and stops. The message has the format:
        DRLJ0318E Exceeded maximum number of rows: <max_rows>
  4. The Forecaster is modified to validate data packets prior
     to processing. If validation fails, the Forecaster issues
     an error message and stops. The message has the format:
        DRLJ0401E Error instantiating Data Packet; Dictionary
        incomplete; missing <part-name>
  
  5. The internal stage is modified to no longer duplicate
     packets.
  
  6. The publisher samples are modified to specify UTF-8 for
     JSON encoding.
  

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:

  UI72639 UI72640

Modules/Macros

• DRLDOD18 DRLDOD19 DRLJMTVK DRLPJFC
  

Fix information

• Fixed component name

  TDS FOR Z/OS

• Fixed component ID

  569510100

Applicable component levels

• RC01 PSY UI72639

     UP20/11/19 P F011

• RCA8 PSY UI72640

     UP20/11/19 P F011

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.