Displays current Diagnostic Data Collection settings and allows you to change the settings.

PROMON Diagnostic Data Collection

The following shows a sample display:

   			 OpenEdge Release 13 Monitor (R&D)
                Diagnostic Data Collection

        Current Diagnostic Data Collection Settings:

         1. Diagnostic directory:       ""
         2. Diagnostic field separator: ' '
         3. Diagnostic pause time:      0
         4. Diagnostic prefix value:    diagEvent_
         5. Diagnostic report format    csv

         6. Lock Table Overflow:       0: Data collection disabled
         7. BI Threshold:              0: Data collection disabled
         8. System Error:              0: Data collection disabled
		
        10. Reporting frequency:	   0
        11. Report only top offenders: 0

		99a. Collect enabled diagnostic data now
		99b. Collect diagnostic data for a particular event

Enter a number, P, T, or X (? for help):

For items 1-5, change any value by entering the number, and entering a new value as prompted.

For items 6-8, the following menu prompts you to set a value for the data collection.

Enter 0: Disabled
      1: Summary
      2: Summary & Detailed
      3: Summary, Detailed & Protraces
    4-7: Proc invocation in combination w/chosen option 0 thru 3
   8-15: Report all enabled event collectors in combination w/chosen option 0 thru 4
 (-15 to 15):

Note that negative values collect the same amount of data, but only in the case of a fatal error that will bring down the database.

For options 10 and 11, change the value by entering the number, and enter a new value as prompted.

For option 99a, the data collection executes immediately, and does not respect the pause time value or the values set for options 10 (Reporting frequency) and 11 (Report only top offenders).
Note: For backward compatibility, you can also enter 9 to access option 99a.
For option 99b, select an event type by number from the following menu to collect diagnostic data for only the number of connections specified by option 11:
Enter event to initiate or Q to Quit
								(1-Lock Table Overflow, 2-BI Threshold, 3-System Error):

The Lock Table Overflow and BI Threshold events triggered by option 99b comply with the current value for the -diagTopN startup parameter or the value set for option 11 through PROMON. The System Error event does not honor the value of -diagTopN.

The raised event adheres to the existing diagnostic setting for -diagTopN. For example, if the event type for option 99b is Lock Table Overflow, any BI threshold data recorded will be specific to the number of connections for the lock table event as specified by -diagTopN. Conversely, if the event type is BI Threshold, any lock table information recorded will be specific to the number of connections for the BI threshold event, as specified by -diagTopN.

This behavior is identical to that of a real event raised by the running system, with the exception that because this request for collecting diagnostic data for a specific number of connections originates from PROMON, the value set for the -diagFrequency parameter, or option 10, does not limit reporting frequency.

For more information, see Diagnostic frequency (-diagFrequency) and Top diagnostic event triggers (-diagTopN).