T24 system, jBASE level issue: WHERE command shows different processes to Windows Process Explorer

[Phil Knight]

The jBASE ‘WHERE’ command sometimes shows spurious information. In the
example below, PID 1660 on port 2 is shown as the Temenos Service
Manager, but it Windows Process Explorer it is shown as Sophos Anti-
Virus.

We have also noticed that the ‘WHERE’ command often shows processes as
still running, that Process Explorer shows as closed.

Does anyone know if the WHERE command is referencing an internal file
that is lagging behind what is actually happening in the operating
system?

Philip


jsh Prod ~ -->WHERE

Port Device Account PID
Command
1 vt220 Prod 3792 jsh -Jz -c tSA 1
tSA 1
tSM
2 vt220 Prod 1660 jsh -Jz -c tSA 1
tSA 1
tSM
*3 vt220 Prod 3700 C:\TAFC\R10\bin\jsh -
WHERE
jsh Prod ~ -->

jsh Prod ~ -->JDIAG
jdiag - jBASE diagnostic '$Revision: 1.15 $'

System Information
==================

System : WinNT R10 5.2 AMD64
OS Release : Windows Server 2003, Build 3790, Service
Pack 2
NT User : Prod
Time : Fri Nov 19 14:50:27 2010

Environment
===========

JBCPORTNO : Not Set
TAFC_HOME : 'C:\TAFC\R10'
JBCGLOBALDIR : 'C:\TAFC\R10'
JBCDATADIR : 'C:\TAFC\R10\jbase_data'
WARNING: JBCDATADIR is subdirectory of JBCGLOBALDIR
HOME : 'E:\bnk\bnk.run'
JEDIFILEPATH : 'E:\bnk\bnk.run;.'
JEDIFILENAME_MD : 'E:\bnk\bnk.run\VOC'
JEDIFILENAME_SYSTEM : 'C:\TAFC\R10\src\SYSTEM'
RELEASE Information : Major 10.0 , Minor 0.1 , Patch (Change
88624)
Spooler dir (JBCSPOOLERDIR) : 'C:\TAFC\R10\jspooler'
JBCEMULATE : 'prime'
TEMP file path : 'C:\WINDOWS\TEMP\'
Object path (JBCOBJECTLIST) : 'E:\bnk\bnk.run\lib;E:\bnk\bnk.run
\t24lib;E:\bnk\bnk.run\peclib;E:\bnk\bnk.run\blmlib;E:\bnk\bnk.run
\GR0800006lib;E:\bnk\bnk.run\gdgitl'
WARNING: From checking the registry, It appears that VC++ is not
loaded
jBASE Compiler Run-time : 'C:\TAFC\R10\config\system.properties'
Program dir (JBCDEV_BIN) : 'E:\bnk\bnk.run\bin'
Subroutine dir (JBCDEV_LIB) : 'E:\bnk\bnk.run\lib'
jsh Prod ~ -->

[Jim Idle]

WHERE polls the processes and asks them to update a table, which it uses to
report with. I think that there is some way to clear the table. You can
probably use tools from sysinternals to better advantage. I don't think
Windows is what anyone should be using as a multi-user system myself though.

I would also unload Sophos and replace it with Windows Security Essentials,
which is free and much better.

Jim

> --
> Please read the posting guidelines at:
> http://groups.google.com/group/jBASE/web/Posting%20Guidelines
>
> IMPORTANT: Type T24: at the start of the subject line for questions
> specific to Globus/T24
>
> To post, send email to jB...@googlegroups.com To unsubscribe, send
> email to jBASE-un...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/jBASE?hl=en

[VK]

Hi,
look into "proc" subdirectory of jbase home for this table. In my case
there is another subdirectory called "port0-499" with files inside
(though neither in hashed or text format). File name represents a
port; in one case I've deleted a file corresponding to the port which
I knew wasn't active and WHERE then didn't show it.

VK

> >http://groups.google.com/group/jBASE?hl=en- Сакриј наведени текст -
>
> - Прикажи текст између наводника -

[Jim Idle]

Yes, but the point is that WHERE causes the cache to be built, but then when
the results are used to kill things (well, you should not be killing things,
but ...) then the information no longer reflects the PID because something
else is now using it.

That is why PIDs should cycle and not reuse slots. It does not matter what
you use, there will be a delay in reporting vs using the PID and things
could have changed by then. Both WHERE and anything else will suffer from
that, but it is more likely with where because it seems to take some time
before the processes update the tables.

[Phil Knight]

Thanks for the comments.

I wholeheartedly agree that processes should not be killed at OS level
if possible, but from the application within which they were started
if that application is maintaining a status file on those processes
that does not get updated in response to OS level events.

T24 maintains the file F.TSA.STATUS to report on its ‘Temenos Service
Agents’ and other online connections to T24 (tSS.exe), typically
browser sessions. This file is notoriously unreliable and that is why
I tend to use the jBASE ‘WHERE’ command as a reality check against it.
So it’s worrying to see that ‘WHERE’ is not 100% reliable either.
Another table, F.T24.SESSION maintains rudimentary information for
browser sessions.

The browser connections are made through the Temenos Connector Server,
which is installed as a Windows service with an automatic startup
type. This cannot be stopped from within T24.

After starting two browser sessions, viewing a report within each,
then signing off the browser sessions correctly the F.TSA.STATUS file
and ‘WHERE’ output start to diverge:

sort F.TSA.STATUS IF AGENT.STATUS EQ 'RUNNING' PROCESS.ID PORT.ID
CURRENT.SERVICE AGENT.STATUS PAGE
1 11:29:21 24 NOV 2010

@ID....... PROCESS.ID.. PORT.ID.....
CURRENT.SERVICE............... AGENT.STATUS.......................

1 2292 15
TSM RUNNING
2 3740 28
PRINT.OUT RUNNING
3 3804 29
SWIFT.OUT RUNNING
OLTP3021 5
OLTP RUNNING
OLTP442 33
OLTP RUNNING
OLTP4543 31
OLTP RUNNING
OLTP5715 32
OLTP RUNNING
OLTP7080 5
OLTP RUNNING

8 Records Listed

jsh Prod ~ -->

jsh Prod ~ -->WHERE
Port Device Account PID
Command

5 vt220 SYSTEM 3240 E:\bnk\bnk.run\t24bin
\eb_interface\tSS.exe
9 vt220 SYSTEM 1408 ***** Thread type Normal
*10 vt220 Prod 3780 C:\TAFC\R10\bin\jsh -
WHERE
15 vt220 Prod 2292 jsh -Jz -c tSA 1
tSA 1
tSM
27 vt220 SYSTEM 1844 ***** Thread type Normal
28 vt220 Prod 3740 jsh -Jz -c tSA 2
tSA 2
29 vt220 Prod 3804 jsh -Jz -c tSA 3
tSA 3
I would be interested to see some documentation on the design concepts
that have been used here to update and extract this information at
both the Jbase and T24 level if anyone has any?

Philip

> > > >http://groups.google.com/group/jBASE?hl=en-Ñàêðè¼ íàâåäåíè òåêñò -
>
> > > - Ïðèêàæè òåêñò èçìå ó íàâîäíèêà -

>
> > --
> > Please read the posting guidelines at:
> >http://groups.google.com/group/jBASE/web/Posting%20Guidelines
>
> > IMPORTANT: Type T24: at the start of the subject line for questions
> > specific to Globus/T24
>
> > To post, send email to jB...@googlegroups.com To unsubscribe, send
> > email to jBASE-un...@googlegroups.com
> > For more options, visit this group at

> >http://groups.google.com/group/jBASE?hl=en- Hide quoted text -
>
> - Show quoted text -