Did iwgen change in Service Pack 2?

Lex

Previously we called iwgen in a perl script from an external task in a workflow. We would build the arguments to iwgen as follows:

my $iw_gen = "d:\\iw-home\\bin\\iwgen";
my $template = $iw_mount.$area_vpath."\\templatedata\\wyaboutus\\wywklyforest\\presentation\\wymaindefault.tpl";
my $datarecord = $iw_mount.$area_vpath. "\\" . $file_path;
#$filepath comes from an array of files attached to the job
my $default_file = $iw_mount.$area_vpath . "\\default.asp";

And call iwgen like this:

my $success = system("$iw_gen -t $template -r $datarecord $default_file");

This all worked fine. However, after applying service pack 2 (both TS and Templating) last week, we found that this call to iwgen no longer worked. After some debugging, we discovered the problem is the $iw_mount variable on the front. Removing this returned things to normal, but I'm curious why this worked before and now suddenly it doesn't?

Thanks!

Migrateduser

Well... first things first, what you currently have is technically wrong. Look at the clt manual for a definition of a vpath. According to iwgen's -h output:

In reply to:

---

# iwgen -h
Usage: iwgen -t templatevpath -r recordvpath [-e encoding] vpath
where templatevpath specifies a path to a TeamSite
Templating presentation template
where recordvpath specifies a path to a TeamSite
Templating data record
where encoding is the encoding to use for the generated file.
Supported encodings:
ISO-8859-1
UTF-8 (default)
where vpath specifies a path to write the TeamSite
Templating generated file

Usage: iwgen [-h|-v]
-h displays this usage information.
-v displays this command's version number.

---

The paths passed to iwgen are supposed to be vpaths (not filesystem paths, also note the slashes should be forward slashes "/" for vpaths). My guess is that iw_mount has /iwmnt or rather more likely /.iwmnt. It may be that in the past iwgen was more permissive than it should have been.

I know that you may disagree about this, but the fact is that if you make sure to use vpaths or filesystem paths (whatever is asked for) with TeamSite's CLT's you are much more likely to end up not having problems between releases (and you may also find that the code is more portable between OS's as well).