To answer Rick's questions about features: unfortunately, this appears to be a bug. It was intended that CopyBook BizComp would support the in-memory structure. The feature got corrupted in the overhaul of resource processing during 5.x development. We will fix this. We are still discussing internally whether it should use the attributes defined for the MFBizComp (xa:source_type="message") to specify a memory versus file structure, or if it will work the same as the 4.x CopybookBizComp. Current thinking is to make it work like the MFBizComp with xa:source_type="message".

The fact that some pic values in MFBizComp are not properly applied and processed is also a bug. A pic value in MFBizComp should do the same thing as it does in CopybookBizComp.

I understand this conversion to 5.x is scheduled for production later in the year. Could you please let me or Paul know via email the current schedule so we can adequately address your schedule?

Thanks,

-Kirstan