Closed as program error.
Using the -ASYS command option with the msdexport/msdimport command may result in systems being lost from the Integration Flow Designer documents. For example, using the following commands on any .MSD document with systems defined will result in a new.msd file with no systems defined. msdexport old.msd -o export.xml -asys -log msdimport export.xml -o new.msd -asys -log
WTXCQ - WTX00041463 PB / PB Circumvention: Do not use the -ASYS command flag. If required, remove Servers imported into the document manually.
Users Affected: WebSphere Transformation Extender customers using MSDIMPORT and MSDEXPORT utilities Problem Description: MSDIMPORT command line utility does not generate the system definition file (.msd) from the exported system definition file (.xml) when the command line uses -ASYS command option with out any systems included in the command value (to include all systems). Platforms Affected: Win32
Fixed a problem with MSDIMPORT and MSDEXPORT command line utilities where they now work as expected with -ASYS and -ASVR command options in the command line by generating the XML and MSD files correctly. Delivered in: 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels