[ic] very weird IC Cron issue SOLVED (WEIRD!!!)

[Grant]

> I have a few UserTag which do some stuff and then set a few scratch
> variables.  3 out of 4 of them do this perfectly, but there is a very
> strange issue with the fourth.  The scratch values that it sets can be
> retrieved with the following code on a test page:
>
> [ebay_getsellertransactions]
> count_response: [scratch count_response]
>
> but if the exact same code is run via IC Cron, the cron results
> show a blank
> value for the [scratch count_response].  This seems really
> strange since the
> other UserTags I'm testing have no problem passing scratch
> variables to code
> being run via IC Cron.
>
> Does anyone have any idea?  Even a clue would be much appreciated.  I'm
> stumped.
>
> - Grant

After hours of debugging I've got this working, but the solution seems
ridiculous.  Basically, the following run via IC Cron (aka Jobs) doesn't
return anything even though it should:

[ebay_getsellertransactions]
[scratch count_response]

It does, however, work perfectly when run in an HTML test page.  Here's the
weird part: The following returns the scratch value perfectly when run
through IC Cron:

[tmp whatever1][/tmp]
[calc] $Scratch->{whatever2}; [/calc]
[ebay_getsellertransactions]
[scratch count_response]

Does this make sense to anyone?  The two "whatever" variable names can be
anything at all.  It only seems important that a scratch variable is set via
ITL (even if it's blank) and either [calc] or [perl] is used before the rest
of the code.

- Grant