06-05-05 10:45 PM
By experience, I know that the HATS behaviour when using a HTTP session
variable instead of an specified value is diferent.
With a session variable, HATS creates a new definition of the connection, a
copy of the original. You can check it in the HATS administrative console,
try both ways and look at the connection management pages.
I haven't tried with the LUName Parameter, but I think it's related with
this.
Also look at this technote (1180279):
http://www-1.ibm.com/support/docvie...G&context=SSALH
E&dc=DB520&q1=URL&uid=swg21180279&loc=en_US&cs=utf-8&lang=en
"David Nguyen" <david.nguyen@qbe.com> escribió en el mensaje
news:ctjthi$79kk$1@news.boulder.ibm.com...
> Hi There,
>
> We just recently migrated our Host Publisher 3.5 application, to Host
> Publisher 4.0, to HATS 5.0.
>
> What is the difference between specifying a LU Name (either through a
> "Specified Value" or "HTTP Session") in the Advanced Section of the
> Connection Definitions, and the LUName option in the Configure Optional
> Section?
>
> What I noticed, is that, if the change was made in the Advanced Section
and
> initiated a connection, an LU connection was NOT initiated to the
specified
> pool (instead was connection via the general public pools). And if, the
> change was made via the Configure Optional Section and initiated a
> connection, then there was an LU Connection to the specified pool (the
> Mainframe Developers were able to advise me, if there was or not a
> connection).
>
> I am interested in utilising the option of specifying an LU Name via the
> "HTTP Session" option, would anyone please advise of how to do this?.
>
> Thanks.
>
>
[ Post a follow-up to this message ]
|