The Source Migration Analysis Reporting Toolset Version 2.1B (SMART) has several new enhancements to help you migrate your Windows applications to OS/2 using the new IBM Developer API Extensions for OS/2 (DAPIE). The DAPIE expands the OS /2 Warp API - helping you create common code for the OS/2 Warp and Windows 32-bit platforms. For more information about DAPIE, read David Reich's article IBM Developer API Extensions, which appeared in Volume 8 of The Developer Connection News.
The new features include:
- Two new tables to help migrate 16-bit Windows applications to OS/2 Warp. The W16DAPIE table identifies, categorizes, and migrates 16-bit Windows applications to the correct OS/2 traditional API and the new DAPIE. The DAPIE16 table identifies the keywords that are not DAPIE.
- A new User Defined Migration Database (UDMD) called DAPIE32.DCT in SMARTAUX\DAPIE32. This UDMD contains all of the DAPIE keywords and can be helpful during the analysis and migration of Windows 32-bit applications.
- Two new reporting and analysis utilities: DAPIEMRG.CMD and Migration Export Library (MEL). DAPIEMRG is used with the output files of W16DAPIE and DAPIE16 to create two reports - one that identifies those keywords in your 16- bit Windows application that are DAPIE supported, and one that identifies keywords that are not DAPIE supported. MEL runs in a Windows environment and compiles and links as any Windows library. However, MEL only includes the DAPIE, so a program compiled and linked with MEL will never actually link or run. But, as an artifact of the linking process, a list of unresolved Windows APIs is generated by the linker. The list of unresolved Windows APIs will be those that are not DAPIE. These new utilities provide information that helps you analyze the migration effort of Windows source modules to DAPIE.
- A new checkbox choice in the SMART Resource Translator dialog box which lets you convert resources in one of the following formats:
- String ID - Select the Support String ID checkbox when using the DAPIE for resources. The .HHH file is not required. The resource compiler accepts the resources with IDs specified as quoted strings.
- Integer ID - Be sure that Support String ID is not selected to generate the required .HHH file. This file defines the resource IDs for use with the traditional OS/2 APIs.
Reprint Courtesy of International Business Machines Corporation, © International Business Machines Corporation