In order for a simulation model to be useful, output indicating what occurred has to be produced so that it can be analyzed. The following kinds of output can be produced from CSIM:

• Reports
  CSIM always collects usage and queueing information on facilities and storage units. In addition, it will collect summary information from tables, qtables, histograms and qhistograms, if any were created by the user. All of this information can be printed via various report statements.
• Model statistics
  CSIM collects statistics on the model itself. This information will be printed upon request.
• Status reports
  Throughout the execution of the model, CSIM collects information on current status. This information will be printed via various status statements.

If no report statement is specified, CSIM will not generate any output (although the user can generate customized output by gathering data through the various information retrieval statements, doing calculations on it, if desired, and printing it).

19.1 Generating Reports

19.1.1 Partial Reports

A partial report can contain information on just one type of object or just the header.

Prototype: void report_hdr(void)

Prototype: void report_facilities(void)

Prototype: void report_storages(void)

Prototype: void report_buffers(void)

Prototype: void report_classes(void)

Prototype: void report_events(void)

Prototype: void report_mailboxes(void)

Prototype: void report_tables(void)

Prototype: void report_qtables(void)

Prototype: void report_meters(void)

Prototype: void report_boxes(void)

Where:

• report_hdr prints the header of the report
• report_facilities prints the usage statistics for all facilities defined in the model
• report_storages prints the usage statistics for all storage units defined in the model
• report_buffers prints the usage statistics for all buffers defined in the model
• report_classes prints the process usage statistics for all process classes defined in the model
• report_events prints the usage statistics for all events defined in the model and for which the monitor method has been invoked
• report_mailboxes prints the usage statistics for all mailboxes defined in the model and for which the monitor method has been invoked
• report_tables prints the summary information for all tables (with histograms and confidence intervals)
• report_qtables prints the summary information for all qtables (with histograms and confidence intervals)
• report_meters prints the summary information for all meters (with histograms and confidence intervals)
• report_boxes prints the summary information for all boxes (with histograms and confidence intervals)

Notes:
Details of the contents of these reports are in the section 19.2, "CSIM Report Output".

19.1.2 Complete Reports

A complete report contains all of the sub-reports.

Prototype: void report(void)

Notes:
The sub-reports appear in the order:

• report_hdr
  
• report_facilities
• report_storages
• report_buffers
• report_classes
• report_events
• report_mailboxes
• report_tables
• report_qtables
• report_meters
• report_boxes

Details of the contents of these reports are in the section 19.2, "CSIM Report Output".

19.1.3 To change the model name:

Prototype: void set_model_name(char* new_name)
Example: set_model_name("prototype system");

Where:

• name - is the new name for the simulation model (quoted string or type char*)

Notes:
name appears as the model name in the report header (in report_hdr and report).

Unless changed by this statement, the model name will be "CSIM".

19.2 CSIM Report Output

The output generated by the report statements present information on the simulation run as it has progressed so far. The sub-reports, comprising the overall report are:

• Header
• Report on facility usage (if any facilities were declared)
• Report on storage usage (if any storage units were declared)
• Report on buffer usage (if any buffers were declared)
• Report on the process classes (if more than one process class (the default process class) has been declared)
• Report on the monitored events
• Report on the monitored mailboxes
• Summary for each table (with histogram and confidence interval) declared
• Summary for each qtable (with histogram and confidence interval) declared
• Summary for each meter (with histogram and confidence interval) declared
• Summary for each box (with histogram and confidence interval) declared

The following tables give a complete description of each of these sub-reports.

19.2.1 Report_Hdr Output

19.2.2 Report_Facilities Output

Notes:

• When computing averages based on the number of requests for facilities, the number of completed requests is used. Thus, any requests waiting or in progress when the report is printed do not contribute to these statistics.
• If collection of process class statistics is specified, then the above items are repeated on a separate line for each process class which uses the facility.

19.2.3 Report_Storages Output

Notes:

• When computing averages based on the number of requests for storage, the number of completed requests is used. Thus, any requests waiting or in progress when the report is printed do not contribute to these statistics.

19.2.4 Report Buffers Output

19.2.5 Report_Classes Output

Notes

• If no process classes are specified, the report for the "default" class (every process begins as a member of this class)is not provided. If any process classes are specified, then the report includes the default class.

• All histogram output for qtables is grouped by state value, where each interval except the last includes only one state value. The last bucket contains all state values greater than the value covered by the penultimate value.

19.2.10 Report_Meters Output

19.2.11 Report_Boxes Output

19.3 Printing Model Statistics

19.3.1 To generate a report on the model statistics:

Example: mdlstat();

• This report lists:
• CPU time used
• Number of events processed
• Main memory obtained via malloc calls
• Number of malloc calls
• Process information:
• Number of processes started
• Number of processes saved
• Number of processes terminated
• Maximum number of processes active at one time
• Information about storage for run-time stacks

• status_processes prints the status of all processes defined in the model
• status_next_event_list prints the pending state changes for processes
• status_events prints the status of all events defined in the model
• status_mailboxes prints the status for all mailboxes defined in the model
• status_facilities prints the status of all facilities defined in the model
• status_storages prints the status of all storages defined in the model

• status_processes
• status_next_event_list
• status_events
• status_mailboxes
• status_facilities
• status_storages