A fix is available
APAR status
Closed as program error.
Error description
PE for PTF UI65673(September 2019) This PE only impacts IMS users who map virtual tables using DBDs that define a data capture exit (EXIT= on either the DBD or SEGM macro). The symptoms impacted users see are: 1. IMS virtual tables are missing from the Virtual Tables subtree of the SQL node in the Data Studio. 2. Attempts to query missing IMS tables fail with the message "Unable to process map map-name" 3. At system startup, an parsing error occurs for impacted DBDs. A sample message is: Error parsing source for DBD dbd-name, macro number nn, reason = INVALID KEYWORD LOG
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IMS USERS * **************************************************************** * PROBLEM DESCRIPTION: PE for PTF UI65673(September 2019) * * * * This PE only impacts IMS customers who * * map virtual tables using DBDs that * * define a data capture exit * * (EXIT= on either the DBD or SEGM * * macro). * * The symptoms impacted customers * * see are: * * 1. IMS virtual tables are missing * * from the Virtual Tables subtree * * of the SQL node in the Data Studio. * * 2.Attempts to query missing IMS * * tables fail with the message * * "Unable to process map map-name" * * 3. At system startup, an parsing * * error occurs for impacted DBDs. * * A sample message is: Error parsing * * source for DBD dbd-name, macro * * number nn, * * reason = INVALID KEYWORD LOG * **************************************************************** * RECOMMENDATION: APPLY PTF * **************************************************************** PE for PTF UI65673(September 2019) This PE only impacts IMS customers who map virtual tables using DBDs that define a data capture exit (EXIT= on either the DBD or SEGM macro). The symptoms impacted customers see are: 1. IMS virtual tables are missing from the Virtual Tables subtree of the SQL node in the Data Studio. 2.Attempts to query missing IMS tables fail with the message "Unable to process map map-name" 3. At system startup, an parsing error occurs for impacted DBDs. A sample message is: Error parsing source for DBD dbd-name, macro number nn, reason = INVALID KEYWORD LOG
Problem conclusion
APPLICABLE FOR IMS USERS
Temporary fix
Comments
×**** PE20/02/11 FIX IN ERROR. SEE APAR PH22108 FOR DESCRIPTION
APAR Information
APAR number
PH19355
Reported component name
IDAA LOADER DAT
Reported component ID
5639OLE01
Reported release
210
Status
CLOSED PER
PE
YesPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-11-18
Closed date
2019-11-22
Last modified date
2020-02-21
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI66586
Modules/Macros
HLVCPRSE HLVCRDBD HLVIMPMP HLVOAPDR HLVOPAGN HLVPB HLVSQ29D HLVSQ29N HLVSQ2AD HLVSQ2AN HLVSQ2BD HLVSQ2BN HLVSQ2CD HLVSQ2CN HLVSQL9D HLVSQL9N HLVSQLAD HLVSQLAN HLVSQLBD HLVSQLBN HLVSQLCD HLVSQLCN
Fix information
Fixed component name
IDAA LOADER DAT
Fixed component ID
5639OLE01
Applicable component levels
R210 PSY UI66586
UP19/12/11 P F912 {
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.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.1.0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCQN5S","label":"Db2 Analystics Accelerator Loader Data Map"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.1.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
21 February 2020