 |
 |
Archives of the TeradataForum
Message Posted: Mon, 02 Jun 2003 @ 21:53:33 GMT
Subj: | | PM API MONITOR SESSION bug? |
|
From: | | Anomy Anom |
<-- Anonymously Posted: Monday, June 02, 2003 17:50 -->
I'm trying to write a PM API app that monitors individual sessions via MONITOR SESSION and MONITOR SQL...but MONITOR SESSION doesn't seem
to behave as documented when I supply an explicit username/session number. If I leave them both NULL, then I get all the sessions for the
host ID (way more than I want), but if I include a valid username and/or session number, I don't get anything back. I've tried this on 4.1
and 5.0 demo's, both behave the same way.
Is this a known problem, or is there a magic combination of bits I'm overlooking? I noticed that PMON doesn't seem to provide a way to
enter explicit session/username settings either...
TIA
| |