Conversion Does Not Work in Development Studio Client Version 4.0

If you have trouble converting in Version 4.0, this might be related to the communications environment in CODE Designer. Although it is not obvious, the WebFacing Tool invokes the CODE Designer tool during WebFacing conversion. CODE Designer in Development Studio Client Version 4.0 uses the CODE communications layer and not the Remote System Explorer support that the WebFacing Tool normally uses.

Note  

It is highly recommended that you use a host name and not an IP address when defining server identifications in the CODE communications layer. If you do not have a name server, use the hosts file under your Windows system directory to map the IP address to a host name.

One way to find out whether the CODE communications are causing a problem is to simply try starting CODE Designer from the Windows Start menu and try loading the DDS member from the iSeries server that you use for the WebFacing conversion. If this works, communications should not be a problem.

If it does not work,

• Close CODE Designer.

• Go to the Windows Task Manager.

• Look in the Processes page for image names that start with evf. You can sort the list by clicking the header Image Name.

Figure 18.14: Windows Task Manager with evf* processes

End each of these evf processes by

• Selecting the process

• Clicking the End Process push button

After you end all evf processes, start CODE Designer again and access the DDS source member on your iSeries server.

If you are successful now,

• Close CODE Designer and start the WebFacing conversion again.

Hopefully the WebFacing conversion now works. Otherwise, use the contacts listed in the beginning of this chapter to determine the cause for this problem.

Note  

In Development Studio Client Version 5.0, the WebFacing conversion is changed so that CODE Designer does not use the CODE communications when performing WebFacing conversion.