Kbase P108034: Batch client wrongly displayed as ? under connect-batch VST
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/19/2007 |
|
Status: Verified
FACT(s) (Environment):
Progress 9.1x
OpenEdge 10.0x
OpenEdge 10.1A
SYMPTOM(s):
Setting of _connect._connect-batch is incorrect
Batch client wrongly displayed as "?" under _connect VST
_connect._connect-batch returns "?" instead of "Yes" when querying local batch clients
_connect._connect-batch returns "No" instead of "Yes" when searching for remote batch clients
promon shows client as a Batch correctly
CAUSE:
The VST was checking the incorrect value for a batch user.
CAUSE:
Bug# OE00119526
FIX:
Upgrade to OpenEdge 10.1B where this issue was initially fixed so that the _connect-batch VST field will display "yes" if the client is a batch mode client, and "no" if the client is not batch.
Workarounds:
W1: on Unix/Linux, the parameter "-b" used for batch clients so this can be seen within the result of:
"ps -ef | grep <pid>"
W2: promon <dbname> , R&D, 1. Status Displays, 4. Processes/Clients, 5. Local Batch Clients
shows the number of self-service batch clients.
W3: as batch sessions usually connect using their own userid:
relate _user to _connect,
When not using blank user ID, _connect._Connect-name = _user._userID.
When using blank user ID, _connect._Connect-name = OS user ID.
for example,the VST _Connect._Connect-Device field value will be 'batch'