[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference orarep::nomahs::rdb_60

Title:Oracle Rdb - Still a strategic database for DEC on Alpha AXP!
Notice:RDB_60 is archived, please use RDB_70..
Moderator:NOVA::SMITHISON
Created:Fri Mar 18 1994
Last Modified:Fri May 30 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:5118
Total number of notes:28246

5006.0. "Does Rdb invoke sys$system:setp0 (setp-zero)" by M5::JHAYTER () Thu Feb 06 1997 14:55

Hi,

Rdb 6.1

Customer is claiming his rdb application is activating the image called
SETP0 a lot.  77, 55, etc times per second according to DECPS.

Does anything Rdb related invoke this image and if so, what for?

Thanks,
Jerry
T.RTitleUserPersonal
Name
DateLines
5006.1DUCATI::LASTOVICAIs it possible to be totally partial?Thu Feb 06 1997 15:461
I'll bet that RDB$SETVER does a 'SET COMMAND'...
5006.2M5::JHAYTERThu Feb 06 1997 16:556
>I'll bet that RDB$SETVER does a 'SET COMMAND'...

I checked sys$library:sql*.com and rdb*.com for a set command, none found.
Besides, I don't think his application would/could run setver 70 times a
second.
5006.3DUCATI::LASTOVICAIs it possible to be totally partial?Thu Feb 06 1997 17:209
I was incorrect about SET COMMAND I think. 
from what I can figure out (on a vms 7.1 vax system), the two
SET commands that use SETP0.EXE are SET MESSAGE and SET PASSWORD.
Some part of his application/system appears to be doing SET MESSAGE
or SET PASSWORD.  of the two, SET MESSAGE appears to be used in
one rdb-related place: SYS$COMMON:[SYSMGR]RDB$SHARE_HIGHEST_VERSION.COM.

If it was me, I'd add a security alarm to SETP0.EXE for successfull
file access and see what pops out.
5006.4NOVA::SMITHIDon't understate or underestimate Rdb!Thu Feb 06 1997 18:064
Doesn't SET PROCESS also call SETP0?
e.g. SET PROCESS/NAME for instance

Ian
5006.5DUCATI::LASTOVICAIs it possible to be totally partial?Thu Feb 06 1997 18:503
looking through the CLI tables for the SET command,
the only two to use SETP0 are SET PASSWORD and SET MESSAGE.
SET PROC/NAME doesn't.
5006.6DUCATI::LASTOVICAIs it possible to be totally partial?Thu Feb 06 1997 18:502
Another quick way to find out who's at fault would be to simply
rename SETP0.EXE to something else to find out who wants it!
5006.7M5::JHAYTERFri Feb 07 1997 16:307
Thanks for the replies.  I take it setp0 is not something Rdb makes much
use of and
SYS$COMMON:[SYSMGR]RDB$SHARE_HIGHEST_VERSION.COM.

is not something that gets ran very often.  I'll pass on the alarm and
rename ideas.
5006.8M5::LWILCOXChocolate in January!!Mon Feb 10 1997 08:384
                       <<< Note 5006.7 by M5::JHAYTER >>>


And let us know what you find out!