The COMP-3 wizard issue is a known bug in the 5.1.0 GA release (the Engine can correctly process the BizComponent as show in the Designer Help Example, but the wizard fails to recognize the COMP-3 type). This is being fixed now and is targeted to be included in the 5.1.1 (patch) GA release scheduled for Sep 9. You can track the status in our SourceForge Issue Tracker for Bug #2058503.

In the meantime, you could workaround the issue by modifying the copybook layout to use 9(n), for the appropriate byte length of the COMP-3 value. After the wizard has completed and the Bizcomp is saved, you can edit the Bizcomp to add the COMP-3 format and appropriate display pic_value -- for example, change:
<SALARY xa:start="20" xa:field_length="5"
xa:pic_value="9(5)">

to:
<SALARY xa:start="20" xa:field_length="5"
xa:packed_type="COMP-3"
xa:pic_value="999999v99">


Only the COMP-3 numeric type has currently been implemented. I have added a request to support the COMP numeric type to our SourceForge Issue Tracker for FR #2079017, to include in our Build 5.2 planning (which could be in a year-end GA release, but available in an earlier daily/Stable build).

(You could implement the COMP type by adding it to the Spring config file, and implementing its class, similar to the COMP-3 implementation, as Kirstan has mentioned previously. The class can be deployed in /dynamic for Designer and deployed through the Update XAware Ear/War utility. It would be great to add the implementation files to the XAware Extras project in Community Projects.)