Conference turris::languages

246.0. "DECtrace (EPC) internal field test start" by CREDIT::OCONNELL (Mike) Mon Aug 14 1989 10:34

+___________________________+ TM
|   |   |   |   |   |   |   |
| d | i | g | i | t | a | l |		INTEROFFICE MEMORANDUM
|   |   |   |   |   |   |   |
+---------------------------+

TO:  distribution			DATE:	August 8, 1989
					FROM:	Mike O'Connell
					DEPT: 	Database Systems
					EXT:	381-2374
					MS:	ZK02-1/P05
					ENET:	CREDIT::OCONNELL


SUBJECT:   Announcement of Internal Field Test for DECtrace (formerly EPC -
	   Event Performance Collector). 

The internal field test for DECtrace will begin on Thursday, August 10th, 1989.
This memo describes the field test, kit locations, training, and support
mechanism. If you have any questions please send mail to CREDIT::OCONNELL. Some
of you on this distribution have already agreed to field test.  Those who were
unaware of the field test are being invited to participate. 

This memo contains information regarding:

	o Field test description

	o Field test restrictions

	o Kit availability

	o Field test training

	o Field test support


Mike

***

Field test description:

DECtrace is a general facility that collects event and performance data.  By
instrumenting application code with DECtrace service routine calls, a developer
can gain performance metrics at a very fine level of granularity (eg, per
application major function, module, or specific line or lines of code). This
information can then be used for performance tuning of the application,
capacity planning, application behavior analysis, etc. DECtrace provides both
summary and detail default reports.  It also stores its data in an Rdb/VMS
database or RMS file for easy formatting and retrieval by DECtrace users. 

DECtrace requires VMS V5.0 or higher and the Rdb/VMS V3.0B or T3.1 FT3 runtime
kit to be installed on the system. 

DECtrace has no special processor requirements other than those of Rdb/VMS. 
DECtrace will store its data on disk.  The amount of disk space depends upon
the length of the collection and the frequency of events collected. 

We are looking for internal field test sites who are currently engaged in
applications development and tuning or who may be interested in this
technology. 

These sites would be primarily assessing the product from a user interface,
product quality and reliability, and product documentation standpoint. 

**

VAX ACMS T3.1 has been instrumented DECtrace service routine calls.  DECtrace
can be used to collect and report on performance information about ACMS
applications.  DECtrace superceeds ACMS EPC.

We are looking for internal field test sites who are field testing ACMS T3.1
and who are interested in obtaining performance metrics about their ACMS
applications. 

Note: Sites do not have to modify their applications to collect DECtrace
information from ACMS.  The DECtrace service routine calls are already in the
ACMS T3.1 code itself. 

**

Rdb/VMS T3.1 and VAX DBMS T4.1 and T4.2 have been instrumented with DECtrace
service routine calls.  By collecting DECtrace data from those database
products while transactions are being executed, the DBA can assess the
performance of the database and determine the workload which was being
executed.  This information provides data in addition to that presented by the
current database performance monitors (ie, RMU/SHOW STATISTICS, DBO/SHOW
STATISTICS). 

We are looking for internal field test sites who are currently measuring the
performance of their Rdb/VMS or VAX DBMS databases or who may be interested in
this technology. 

Note: Sites do not have to modify their applications or databases to collect
DECtrace information from Rdb/VMS or VAX DBMS.  The DECtrace service routine
calls are already in the database products themselves. 

These sites would be primarily assessing the product from a user interface,
product quality and reliability, and product documentation standpoint. 

***

Limitations of DECtrace INTERNAL FIELD TEST KIT (T1.0-4)

The functionality of DECtrace V1.0 is nearing completion.  Roughly 85%
of  the  functionality is present in the internal field test software.
Much of the functionality that  layered  product  developers  need  to
place and debug calls to DECtrace service routines is complete.  Also,
users will  be  able  to  generate  informative  reports,  useful  for
analyzing application performance and workload characteristics.

This section details all of the DECtrace V1.0 functionality  that has not yet
been completed. 

       o  The   FORMAT    command    does    not    yet    accept    the
          /CDDPLUS_DEFINITIONS qualifier for RMS formatted data files.

       o  Deinstallation command procedure.

       o  Help command

       o  Functionality not yet available in REPORT:

           -  RESTRICTION COLLECTION (not tested)
           -  RESTRICTION NODE (not tested)
           -  There is no major headers for each event.  The event  name
              is temporarily placed in the report subtitle.
           -  Summary Page
           -  RESTRICTION ITEM when item type is Quadword.
           -  Only one REPORT command at a time can be executed from the
              DECtrace prompt or from command files.
           -  Overflows  occurring  while  calculating  Total,  Standard
              Deviation,  95  Percentile  will  cause  a  DECtrace image
              bugcheck.  This would only occur when  internal  temporary
              values exceed 1.7*1038.

       o  The  SHOW  COLLECTION  command  does  not   yet   accept   the
          collection-name   parameter   and   does   not   produce   the
          /FORMAT=FULL report.

       o  SHOW DEFINITION /FORMAT=BRIEF command is not implemented.   It
          currently will display the /FORMAT=FULL report.

       o  SHOW SELECTION command

       o  SHOW VERSION command
 



Requirements:

          o  Hardware

	      - DECtrace operates on a character mode terminal.  While it runs 
		on any VAX processor, the minimum configuration should support 
		Rdb/VMS since DECtrace layers upon this database product.

          o  Software

	      - DECtrace requires Rdb/VMS 3.0B OR T3.1 FT3 or higher and VMS 
		V5.0 or higher.

	      - VAX Rdb/VMS T3.1 FT3 or higher for sites testing DECtrace with 
		Rdb/VMS.  

	      - VAX DBMS V4.1 requires CDD/Plus V4.1 or T4.2 for sites testing 
		DECtrace with VAX DBMS.  (Note: VAX DBMS V4.1 requires VMS T5.2)


	 Prerequisite software can be obtained over the network as described
	 below.


Kit locations:

	  o The DECtrace kit can be obtained by completing the following and 
	    sending it to CREDIT::OCONNELL.  The kit will be copied to the
	    location specified on the next day.  If additional groups within 
	    your organization wish to install the kit and access the QAR 
	    system and field test notes file, please have them complete the 
	    following and send mail as well.  If they will be using the same 
	    kit, then have them indicate that.

		Name:
		Organization:
		DTN or tel:
		VAX mail:
		Node(s) from which support notes conference will be accessed:


		Complete directory specification to copy doc and software to:


		Testing DECtrace in your code? (Y/N):
		Testing DECtrace with VAX ACMS (Y/N):
		Testing DECtrace with Rdb/VMS  (Y/N):
		Testing DECtrace with VAX DBMS (Y/N):

		Need access to the DECtrace QAR system (Y/N):
		(Note: if you already have access to the EPC QAR system you
		should enter 'N' here.)

		Number of individuals will attend DECtrace training:
		Number of individuals will attend RdbExpert training:
		{see 'training' below for more information}


	  o The VAX DBMS V4.1 kit can be obtained by sending mail to 
	    NOVA::MJOHNSON.

	  o The Rdb/VMS V3.0b kit can be obtained by:

                <<< NOVA::DVD12:[NOTES$LIBRARY]RDB30B.NOTE;1 >>>
                             -< VAX Rdb/VMS V3.0B >-
================================================================================
Note 4.0                    Network Installation Kit                   2 replies
BANZAI::SMITHI "Regard this simple silver salt cell" 36 lines  11-JUL-1989 12:29
--------------------------------------------------------------------------------
Following are instructions for your use in pulling the desired Rdb/VMS kit. 

If you encounter problems using this procedure, please send mail to 
NOVA::SYSTEM.

*************************************************************************
On-line documentation can be copied from: REORG::USER2:[RDBVMSDOC.PUBLIC]

Please note:  You will need 31,977 free blocks to copy the kit.
*************************************************************************

1.  SET HOST NOVA (or SET HOST BANZAI)

2.  USERNAME: RDBKIT

3.  PASSWORD: RDBKIT

4.  At this point a command procedure will run which will ask for the 
    following information:

    - Your name:  
    - Your badge number:
    - The version you wish to copy.  This procedure also copies VAX SQL since 
      it is now part of the Rdb/VMS kit.
    - The NODE you wish the kit copied TO.  (colons are not necessary).
    - The DEVICE SPECIFICATION you wish the kit copied TO. (colon is not 
      necessary)
    - The DIRECTORY SPECIFICATION you wish the kit copied TO. (brackets not
      necessary).
    - The USERNAME you wish the kit copied TO.
    - The PASSWORD of the USERNAME you wish the kit copied TO.

5.  At this point, the command procedure will create and submit a batch job
    to be run after 7pm (EST) and before 5am (EST) tonight.  You will be 
    notified by mail when the batch job has completed.  



	  o The Rdb/VMS T3.1 kits can be obtained by sending mail to 
	    NOVA::HORN.

	  o The CDD/Plus kits can be obtained copying the following:

	    TLE::CDD$DEVICE:[CDD_PROXY]CDD041.*
			"	       CDD041PAK.MEM
			"	       CDD041_IG.LN03 (or POST or TXT)

Training:

	  o Two days of field test training starting on Sept 18th will be 
	    available for DECtrace.  This session will be followed by two days 
	    of training for RdbExpert (formerly Physical Database Designer - 
	    PDD) and one day for DEC internal users and support specialists.  

	    These will be ONLY field test training sessions offered for 
	    DECtrace and RdbExpert in the US.  RdbExpert field test is 
	    scheduled to begin in late October.

	    The training will be held in the ZK0 facility in Nashua, NH.


Support:

	  o Support will be provided through the use of an DECtrace QAR system 
	    as well as through a restricted field test notes conference.  The 
	    QAR system should be used to report all product bugs.  The notes 
	    conference should be used to ask any usage or general questions 
	    regarding the product. The field test notes conference is not the 
	    same as the existing DECtrace notes conference.  You will be added 
	    as a member to the field test notes conference when the above 
	    information is received and processed.  You should also reply to 
	    the conference registration note for the benefit of others using 
	    the notes file.

	    To add the entry to your notebook execute:

	  	ADD ENTRY CREDIT::DECTRACE_FT


	    The QAR system can be accessed by doing the following:

              1) Upon submission of the above information you will be sent an 
		 account name and password for the QAR system if you have 
		 indicated the need for one (ie you do not now have access to
		 the EPC QAR system).  Once you have that:

              2) SET HOST to BROKE::

              3) Enter your account name and password.

	  The QAR database for internal field test is DECTRACE_IFT.  As a 
	  participant of internal field test, you will receive instructions 
	  on how to use the QAR system when you receive your account name and 
	  password.

          If, due to network problems, you cannot access the QAR system 
	  directly,  you can send VAXmail to CREDIT::QAR_CSSE for an 
	  electronic copy of the QAR form for submission.  Send the completed
	  forms to CREDIT::QAR_CSSE.  An acknowledgment will be returned.
	  For your convenience, a copy of the form follows.




+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

   DECtrace field test QAR template for submitting QAR through VAXmail to 
   CREDIT::QAR_CSSE.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

   REQUIRED INFORMATION
   ====================

   Your name:
   Your organization's name:
   Customer name (company):
   Node name of system:
   Location of system:
   Your phone number and mail stop:
   Installed VMS version:
   Installed DECtrace baselevel:
   Publish [yes or no]:
   Reproducible at will [yes or no]:
   Attachments (Listing, Tape, etc.):
   Problem severity < one of High/Medium/Low/Zero>:
    
     The severity of the problem should reflect your perception of how
     seriously it affects your ability to use your system.
     
      
       H - Problem seriously disrupts normal operations, or causes system
           crashes during normal use (or by non-privileged users).  The
           problem makes it very difficult to get your work done.
     
           High severity also includes data corrupters, new features which do
           not work, features which worked in a previous version but which
           have been broken.  Also "HIGH" are problems causing field test to be
           less effective, performance degradation, incompatibilities which
           break applications/layered products, problems causing installation 
	   or upgrade to fail, and supported hardware that does not work.
    
       M - Problem has some effect, but a workaround is available.  If the
           system crashes, it only happens under unusual circumstances, or
           when someone with privileges does something out of the ordinary.
     
       L - Problem is easily worked around, or only causes minor annoyance.
       
     
       Z - Report does not concern a problem, but is a suggestion, an inquiry,
           or other communication.
     
   OPTIONAL INFORMATION
   ====================
     
   CPU type:
   Memory size:
   System disk:
   Other hardware/software configuration information:
     
   PROBLEM STATEMENT
   =================
     
   Please include the steps to recreate the problem.

    DECtrace V1.0 is being submitted to the SSB on May 14th.  It would be
    very interesting to hear from internal sites who have instrumented an
    application using DECtrace and an anecdotal review of their experience. 
    It would be even more interesting to track a customer who has pruchased
    it for instrumentation of their application and devemop a success story
    around this.  Please send reply here or send mail to OOTOOL::OCONNELL
    if you can help.
    
    Thanks,
    
    Mike