Start again the Converter (see topic Starting the Converter), but now, from the menu in Figure 02-02 select
"1. Conversions performed".
You will get the following page:

This page lists all the conversions performed for which the following data

GWCS inputs Batch Conversion log

are still available.

Please note that in this example, such data are available for the last 90 days.
In other words, data for rerunning conversions performed 100 days ago are no longer available.
The number of days these data are saved is set by command iweb/rtncvtdta (Retain iWEB Conversion Data),
which defaults to 90 days.  

2.6.1 Displaying a conversion log

To display a conversion log, in the screen of Figure 02-21 just select a conversion through a radio button
and press button "display conversion log".
The conversion log is shown as in Figure 02-20.  

2.6.2 Changing compile commands

Sometimes a conversion is partially non successful because some compile commands
(automatically generated from the Batch Conversion job did fail.
One may also establish that rerunning that mass conversion would be of no help,
as the same compile commands would be generated and executed.
In such cases, what one would want is to have a way of changing some of the generated compile commands.

This is exactly what button "change compile commands" in Figure 02-21 is after.
By selecting a conversion and pressing this button, a list of the compile commands
generated and executed in the batch run is made available.
Proper icons are used to tell whether a given command was successful or not.
See Figure 02-22.

From this screen you can edit and change individual compile commands according to your needs. Changed commands are syntax checked. Changed commands override the commands automatically generated by the Batch Conversion job and are just related to a given conversion run.

When you rerun a given conversion run, any changed command will be run in place of the automated one.
For rerunning given conversion runs, see the next topic.  

2.6.3 Rerunning a conversion

By this token we mean reprocessing a conversion starting from a GWCS (Graphical WEB Conversion Session) checkpoint taken at "Parameters" level.

If you press the button "rerun a conversion" in Figure 02-21, or if you press the button "submit conversion of library ..." in Figure 02-22,
you will restart execution of a GWC session exactly at the first parameter block, see Figure 02-15. The only difference here is that the inputs previously entered are back, so you do not have to remember what you did.
Once a batch conversion run completes, its data are saved and override those of the previous conversion run for the same library.