Regarding this comment:
I am facing the similar issue, hipaa_data_complicance map from IBM Helathcare pack is working fine in Windows. Now I have to deploy this to Linux, compiled this map and other dependent maps with lnx extension and deployed, but getting the below errors ..
The Compliance map has 1 main map and many Run maps. The Run maps (34?) must have an extension of .mmc, not others like .lnx. Only the main map has the extension of .lnx. There are 2 ways to do it, the first one is what some do, the second one is my recommended way. I have also attached a writeup I put together when I did this in AWS EKS.
In addition, I also recommend copying hcsvu.so from the pack's platform folder to the container side as it's shipped with one which may not be compatible with your pack.
If you are not running in container, the idea is the same. Give it a try and hopefully may resolve your problem
- Rename all Run maps from lnx to mmc.
- Since V10, ITX Design Studio has an option to compile a map with multiple extension. I changed the option to Windows and Linux. This is so that I don't have to worry about 2 map versions. I only have to remember 1 version. It should have an extension of .mmc. Copy these maps to the Linux side and make a copy the main map (hipaa_data_compliance) with an extension of lnx.
------------------------------
Rex Chan
------------------------------
Original Message:
Sent: Tue July 29, 2025 03:43 PM
From: Bhanu Prakash
Subject: Compliance check map issue
I am facing the similar issue, hipaa_data_complicance map from IBM Helathcare pack is working fine in Windows. Now I have to deploy this to Linux, compiled this map and other dependent maps with lnx extension and deployed, but getting the below errors ..
Error: x12initialcontrolsummary.mmc did not complete successfully
x12allackgenerate.mmc was not executed and no acknowledgements were created
Do we need to manually go to each rule and update .mmc to .lnx? That means we are modifying the OOB map from IBM and I think this is not recommended.
Is there any better way to compile and execute the HIPAA compliance check map in Linux environment with out breaking the OOB functionality.
Best Regards
Bhanu
#hipaa compliance check
#ITX Healthcare pack
------------------------------
Bhanu Prakash
Original Message:
Sent: Thu July 29, 2010 11:38 AM
From: Archive User
Subject: Compliance check map issue
Originally posted by: SystemAdmin
In what cases do we get this below error, All the maps in the HIPAA pack are complied in AIX enviroment and deployed. The paths are pointing to the AIX paths.
x12allackgenerate.mmc was not executed and no acknowledgements were created.Error: x12initialcontrolsummary.mmc did not complete
successfully x12allackgenerate.mmc was not executed and no acknowledgements were created.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange