PH25567: PARAMETER MAP FROM PACKAGES IN DATA MODULES FAILS

APAR status

• Closed as suggestion for future release.

Error description

• For a data module with at least two packages as source, where
  each of them is containing parameter maps, results will be only
  correct for the parameter map of the package, which was added
  first to the data module.
  
  Should a report or dashboard use a parameter map of the second
  package, the expression will be validated against the first
  package. If the parameter exists in the first package key and
  value pairs are taken from this parameter map. If the parameter
  map does not exist in the first package, '' will be used as
  value.
  
  This can lead to different errors (ie. incorrect data type
  comparison) or unexpected results to be returned.
  

Local fix

• The first package should contain all parameter maps and all
  possible values.
  

Problem summary

Problem conclusion

Temporary fix

Comments

• Currently, we will only use the parameter maps of the first
  package that has parameter maps.  The observed behaviour of
  getting an empty string '' in the case that a parameter map
  entry is not found, is correct and part of the macro language
  definition.
  
  
  
  To address this, we will need to add functionality to allow a
  Data Module to have its' own parameter map definitions.  Our
  Development and Product Management teams review APARs and
  features on an ongoing basis for inclusion in a future release
  of our software.
  

APAR Information

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

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

Fix information

Applicable component levels