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

Conference microw::acmsxp

Title:	ACMSxp product questions and comments
Notice:	Refer to notes 1 through 11 for conference information
Moderator:	DUCAT::ROSCOE

Created:	Tue Oct 05 1993
Last Modified:	Thu Jun 05 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	282
Total number of notes:	1134

248.0. "RPC_DEBUG env var" by TKOV60::SHINDO (Y.Shindo/EJ3 PSC/Tokyo/Japan/8-699-4652) Mon Jan 27 1997 22:28

Hi,

Is there anyway to collect the timestamp data of RPC level ?

As you know, in pure DCE/RPC, we can collect several kind of trace data with
timestamp by RPC Event Logging Facility. We need such kind of timestamp 
data at 'call_start', 'call_end' with RPC level.

From my understanding, I believe we could get such kind of data by adding 
RPC_DEBUG env var on ACMSxp for VAX/VMS version. I've tried it on ACMSxp V3.1 
for DUnix, however nothing logged in xxx.outlog, xxx.errlog in the 
ACMS_WORK_DIR directory.

Is RPC_DEBUG env var still valid on ACMSxp V3.0 ?

Regards,
Yoshizumi

T.R	Title	User	Personal Name	Date	Lines
248.1	RPC_DEBUG	DUCAT::ROSCOE		`Tue Jan 28 1997 08:44`	6
	The RPC_DEBUG environment variable is useful only if the RPC code is compiled debug, on Digital Unix the DCE code stream that you are using is not built debug. Having said that I believe an IDL compiler switch may exist that might give you what you want. I't will take a day or two to dig up that info. rich
248.2		DUCAT::ROSCOE		`Mon Feb 10 1997 21:14`	5
	Check in the dce notes conference. I believe an idl compiler switch exists that allows debugging info to be displayed. I don't know if if this switch causes timestamps to be displayed. rich
248.3	ACMS_IDL_LOG	DUCAT::ROSCOE		`Wed Feb 12 1997 17:03`	6
	Set the following environment variable prior to running the stdl compiler. It will turn on idl tracing. The environment variable is ACMS_IDL_LOG. I don't know if that will cause timestamps to be generated. Give it a try. This is a feature of ACMSxp V3.0 rich
248.4	more info	TKOV60::SHINDO	Y.Shindo/EJ3 PSC/Tokyo/Japan/8-699-4652	`Mon Feb 17 1997 08:33`	23
	Rich, Sorry for late response. >Set the following environment variable prior to running the stdl compiler. >It will turn on idl tracing. The environment variable is ACMS_IDL_LOG. >I don't know if that will cause timestamps to be generated. Give it a try. I could get RPC debuggig information by setting the ACMS_IDL_LOG env var, however, unfortunatelly timestamps were not generated in the log. But if ACMS_IDL_LOG env var indicate '-trace all' option to the IDL compiler, I may get timestamps by setting RPC_EVENTS env var in runtime. Which trace option is set for IDL compiler if we set ACMS_IDL_LOG env var ? >This is a feature of ACMSxp V3.0 I could not use this env var on Windows NT version. (I could not compile stdl sources if I set this env var.) Regards, Yoshizumi
248.5		CAMINO::ROSCOE		`Mon Feb 17 1997 20:13`	15
	Shindo-san, the only tracing that is done is for errors: for nt #define IDL_COMPILER_LOG "idl -cc_opt -trace errors " for unix and alphavms #define IDL_COMPILER_LOG "idl -trace errors " Are you sure that trace all will produce timestamps? Why do you need this? some kind of performance measurement? Rich
248.6	TPC-C benchmark	TKOV60::SHINDO	Y.Shindo/EJ3 PSC/Tokyo/Japan/8-699-4652	`Mon Feb 17 1997 22:03`	25
	Rich, Thanks for the info. > the only tracing that is done is for errors: > > for nt > #define IDL_COMPILER_LOG "idl -cc_opt -trace errors " > > for unix and alphavms > #define IDL_COMPILER_LOG "idl -trace errors " > > Are you sure that trace all will produce timestamps? Yes. I tried it by pure DCE/RPC program. If I compiled IDL file with '-trace calls' option, I could get the timestamp data. > Why do you need this? some kind of performance measurement? Our customer(NTT) is planning to do TPC-C benchmark of several kind of TP monitor running on Windows NT and Unix box. Regards, Yoshizumi