The limitations or restrictions when using the enterprise service discovery or enterprise data discovery wizards or the imports and exports they produce are listed here.
The Workarounds for C and COBOL limitations and Workaround for missing arrow on Add to import list button sections have steps that can circumvent some of these limitations.
For CICS® and IMS, you can statically set values on the connectionSpec and interactionSpec properties. You cannot dynamically (programmatically) set or get their values.
COBOL
The limitations listed above for C and COBOL can be addressed indirectly. Accessing a generated business object can be achieved by switching to the J2EE perspective, creating a JavaServer Page (JSP), and then using the JSP to manually access the business object created by the enterprise service discovery wizard. Several examples of such JSPs are shown in WebSphere test environment setup in which JSPs manually access business objects generated by the enterprise service wizard.
In the COBOL section, an error is identified if the COMMAREA contains invalid data. The following steps show how to circumvent the problem.
The missing arrow is a code point. The reason the code point is not displaying on Windows is that a font mapping is required for the font in use to display the widget text in the IDE. Font linking on Windows is fully described in the Fonts section of Globalization Step-by-Step.
To add a font mapping to Windows that will add the arrow, follow these steps:
-----------Start of File Content--------------- REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink] "Tahoma"=hex(7):54,49,4d,45,53,2e,54,54,46,2c,54,69,6d,65,73,20,4e,65,\ 77,20,52,6f,6d,61,6e,00,00 -----------End of File Content---------------
In this sample content, the font displayed in the dialog in the preference page was Tahoma. If your font had a different name, replace Tahoma with the font name that was displayed in the dialog. Save the fontmap.reg file.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink
This registry entry contains the font mapping from your dialog font used in the IDE to the Times New Roman font.