2.1 Starting the Converter

Note: This Chapter treats the "mass conversion" which is the first step of the conversion process. Following a mass conversion, to perform regular application maintenance for single object, you may use the command IWEB/WEBCOMPILE (which could be invocated directly from PDM). See Single object compile command (IWEB/WEBCOMPILE)

To start the Graphical WEB Conversion Session (GWCS), on your WEB browser location line enter 

http://nnn.nnn.nnn.nnn:8008
(where nnn.nnn.nnn.nnn is the IP address of your iSeries).
The page in Figure 02-01 is displayed: select the English language and push the "go" button.

The GWCS would now display its menu (see Figure 02-02): you should select "2. Convert another library".

The Converter would now retrieve the names and the text descriptions of all the non-system libraries and display them to you (see Figure 02-03).

Maybe this is the right time to explain how the Graphical WEB Conversion Session (GWCS) works.

  • The Converter works at library level: it would try to convert to WEB all the 5250 interactive programs found in that library.
  • The Converter would retrieve the program references of each program (or module): it would take into account only the interactive programs, that is only programs referencing display files. It should be noted that
    • File references are collected in the program (module) object when it is compiled.
      If the referenced files cannot be found by the GWCS, the GWCS would ask the user the name of the library containing them.
      This is needed in order to establish the type (database, printer, display file) of the referenced files.
  • The Converter would check the existence of the source members of each interactive program (module), referenced display file, menu and panel group. Again, this type of information is saved in the objects when they are created.
    • Should some sources be not found, the GWCS would stop and ask the information to the user.

In other words, the process of the Graphical WEB Conversion Session is basically driven by the information stored by the system in the objects themselves.
Any time such information is found no longer correct (for instance, because the display files were moved to another library, or the source files were renamed), the process would stop and ask for user intervention.