client process arguments
Posted in 2013
Topics: General Discussion
Hi everybody,
Do you know how to get client process's arguments from any sysmaster table?
sysmaster:syssessions.peprogram only tells the client process name, but not
its arguements.
Here you have an example:
In this case client process name is /.../.../fglgo.
(Does not show its arguments)
Select * from syssessions:sid 107980
username jlrbcnpr
uid 3314
pid 28298
hostname crtdesa
tty /dev/pts/140
connected 1378449288
feprogram /home1/informix11.70/bin/fglgo
whereas ps does(jlr020913):
ps ef:
jlrbcnpr 28298 28295 0 08:34:49 pts/140 0:00 fglgo jlr020913
Thanks in advance,
You'll have to go to the OS to get that command line arguments, Informix
never sees them.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
other organization with which I am associated either explicitly,
implicitly, or by inference. Neither do those opinions reflect those of
other individuals affiliated with any entity with which I am affiliated nor
those of the entities themselves.
On Fri, Sep 6, 2013 at 2:49 AM, JUAN ROCA <jluis.roca@hotmail.com> wrote:
> Hi everybody,
>
> Do you know how to get client process's arguments from any sysmaster table?
>
> sysmaster:syssessions.peprogram only tells the client process name, but not
> its arguements.
>
> Here you have an example:
>
> In this case client process name is /.../.../fglgo.
> (Does not show its arguments)
>
> Select * from syssessions:> sid 107980
> username jlrbcnpr
> uid 3314
> pid 28298
> hostname crtdesa
> tty /dev/pts/140
> connected 1378449288
> feprogram /home1/informix11.70/bin/fglgo
>
> whereas ps does(jlr020913):
>
> ps ef:
> jlrbcnpr 28298 28295 0 08:34:49 pts/140 0:00 fglgo jlr020913
>
> Thanks in advance,
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001a11c2672a6db52c04e5d52820