In the age of technological advancements happening almost every minute, upgrading a business is a must to survive competition, offer beyond expected Customer experience while deploying less resources to derive value out of any process/business.

Platform upgradation, Software upgradation, Security upgradation, Architectural upgradation and so on are required to ensure stability, agility, and efficiency.

Customers prefer to move from Legacy systems to Cloud due to the offerings it brings. From Cost/Monitoring/Maintenance/Operations/ease-of-use/Landscape, Cloud has transformed D&A businesses significantly over the last decade.

Movement from Informatica Powercenter to IDMC has been perceived as the need of the hour due to the humongous advantages it offers. Developers must understand both the flavors to effectively perform this code transition.

This post explains the PWC vs IDMC CDI gaps from different perspectives.,

• Development
• Data
• Operations

• Native Datatypes difference could be observed in IDMC while importing Source/target/Lookup. Workaround as follows.,
  • If any consistency seen in IDMC mappings with Native Datatype/Precision/Scale, ensure to edit Metadata to keep them in sync between DDL and CDI mappings.
• In CDI, taskflow workflow parameter values have read/consumption issues. Workaround as follows.,
  • A Dummy Mapping task has to be created where the list of Parameters/Variables need to be defined for further consumption by tasks within the taskflows (Ex. Command task/Email task etc)
  • Make sure to limit the # of Dummy Mapping tasks during this process
  • Best practice is to create 1 Dummy Mapping task for a folder to capture all the Parameters/Variables required for that entire folder.
  • For Variables whose value needs to be persistent for the next taskflow run, make sure the Variable value is mapped to the Dummy Mapping task via an Assignment task. This Dummy mapping task would be used at the START & END of the taskflow to ensure the overall taskflow processing is enabled for Incremental Data processing.
• All mapping tasks/sessions in IDMC are reusable. They could be used in any taskflows. If some Audit sessions are expected to run concurrently within other taskflows ensure enabling the property “Allow the mapping task to be executed simultaneously”.
• Sequence generator Data overlap issues in CDI. Workaround as follows.,
  • If a sequence generator is likely to be used in multiple sessions/workflows, better to make it as REUSBALE/SHARED Sequence.
• VSAM Sources/Normalizer not available in CDI. Workaround as follows.,
  • Use Sequential File connector type for mappings using Mainframe VSAM Sources/Normalizer.
• Sessions configured to have STOP ON ERRORS >0. Workaround as follows.,
  • Ensure the LINK conditions for the next task to be “PreviousTask.TaskStatus – STARTS WITH ANY OF 1, 2” within CDI taskflows.
• Partitions are not supported with Sources under Query mode. Workaround as follows.,
  • Ensure multiple sessions are created and run in parallel as a workaround.
• Currently parameterization of Schema/Table not possible for Mainframe DB2. Workaround as follows.,
  • Use ODBC type connection to access DB2 with Schema/Table parameterization.
• A mapping with LOOKUP transformation used across 2 sessions cannot be overridden at session/mapping task level to have caching enabled/disabled. Workaround as follows.,
  • Use 2 different mappings with LOOKUP transformations if 1 mapping/session has to have cache enabled and the other mapping/session to have cache disabled

• IDMC Output data containing additional Double quotes. Workaround as follows.,
  • Session level – use this property – __PMOV_FFW_ESCAPE_QUOTE=No
  • Administrator settings level – use this property – UseCustomSessionConfig = Yes
• IDMC Output data containing additional Scale values with Decimal datatype (ex. 11.00). Workaround as follows.,
  • Use IF-THEN-ELSE statement to remove Unwanted 0s in data (O/P : from 11.00 -> 11)

• CDI doesn’t store logs beyond 1000 mapping tasks run/3 days on Cloud (it does store in Secure Agent). Workaround as follows.,
  • To retain Cloud job run stats, create Audit tables and use Data Marketplace utility to get the Audit info (Volume processes, Start/End time etc) loaded to the Audit tables by scheduling this job at regular intervals (Hourly or Daily).
• Generic Restartability issues occur during IDMC Operations. Workaround as follows.,
  • Ensure a Dummy assignment task is introduced whenever the code contains Custom error handling flow.
• SKIP FAILED TASK and RESUME FROM NEXT TASK operations have issues in IDMC. Workaround as follows.,
  • Ensure every LINK condition has an additional condition appended “Mapping task. Fault.Detail.ErrorOutputDetail.TaskStatus=1”
• In PWC, any task can be run from anywhere within a workflow but not possible in IDMC. Workaround as follows.,
  • Feature request worked upon by GCS to update Software
• IDMC mapping task config level is not capable due to parameters concatenation issues. Workaround as follows.,
  • Ensure to use a separate parameter within parameter file to have Mapping task log file names suffixed with Concurrent run workflow instance name
• IDMC doesn’t honour “Save Session log for these runs” property set at the mapping task level when session log file name is parameterized. Workaround as follows.,
  • Ensure to copy mapping task log files in Secure agent server after job run
• If Session Log File Directory contains / (Slash) when used along with parameters (ex., $PMSessionLogDir/ABC) under Session Log Directory Path, this would append every run log to the same log file. Workaround as follows.,
  • Ensure to use a separate parameter within parameter file for $PMSessionLogDir
• In IDMC, @numAppliedRows , @numAffectedRows feature not available to get the source and target success rows to load it in audit table. Workaround as follows.,
  • @numAppliedRows is used instead of @numAffectedRows
• Concurrent runs cannot be performed on taskflows from CDI Data Integration UI. Workaround as follows.,
  • Use Paramset utility to upload concurrent paramsets and use runAJobCli utility to run taskflows with multiple concurrent run instances from the command prompt.

While performing PWC to IDMC conversions, following these Development and Operations workarounds will help avoid rework and save efforts thereby achieving customer satisfaction on Delivery.

This post was originally published on this site - UniAspect assumes no responsibility or liability for any errors or omissions in the content of this article. The information contained in this article is provided on an "as is" basis with no guarantees of completeness, accuracy, usefulness or timeliness and without any warranties of any kind, express or implied.