in a pooled session environment, I had two sessions
active. I closed session 1, and session 2 was listed as
Active|Available. When I reran the code containing the
CONNECT, instead of getting the available session 2, it
allocated a brand new session 1, requiring all the signon
stuff. Doesn't seem like that's how it's supposed to
work. I'll send the trace file via email with the ticket
number in the subject.