Durra: A Task-Level Description Language User`s Manual
Contents
1. dqwatch queue name rpc name dtbreak fask name rpc name dtwatch task name rpc name ww The above commands are used to delete break points or watch points which are de fined below pbreak port name rpcname pwatch port name roc name qbreak queue name rpc name J qwatch queue name rpc name J tbreak task name mc name twatch task name rpc name ww The above commands are used to set break points and watch points where a break or watch point is defined as a state in the application execution sequence at which a speci fied Durra object port queue or task is referenced by one of a specified set of task interface rocs When a break point is set and the application reaches the specified inter face call on from the specified object the application is interrupted and control passes to the monitor so that the user may issue further commands When a watch point is set the monitor informs the user that the watch point has been passed but the application continues to run In the following excerpt the user sets a watch point on the port main p1 out1 for all rpcs and then issues the go command causing the application to resume running The monitor disp2. Class UVAX i e microvax is a subset of class VAX and this is different from class vaAxvMs The former run the Ultrix 32 operating system the latter runs the VMS operating system Class SEIFI contains exactly one processor fi sei cmu edu and can be used as the value of the processor attribute of a task implementation that can only run on that processor The values of the xdisplay attribute are used to specify the display for a task under the X Window screen management system For example the first xaisplay line specifies that i sei cmu edu 0 0 will be the X Window display for all tasks that specify SEIFI as their xdisplay attribute The values of the xdisplay attribute are arbitrary although it makes sense to choose mnemonic values Note that this configuration file is not written in the task description language The ex ample shown is simply an illustration of the kinds of information that are likely to be in the file form and content of the file are implementation dependent See 2 for additional information CMU SEI 89 TR 33 CMU SEI 89 TR 33 4 Execution Environment The runtime executive gains access to the task implementations the configuration de scription and other application or user dependent information through file and directory names defined in the execution environment In the Unix implementation the execution environment is defined by the following shell environme
3. mo mo Wa Wa Wa Wa ni ni ni EC CC CC tc O tor dpwatch tor go UT1 tor qwatch main gb2 h at queue MAIN QB2 RPC MAIN PB1 0UT1 h at queue MAIN QB2 RPC Some task already waiting d h at queue MAIN QB2 RPC Queue is empty receiver 1 h at queue MAIN QB2 RPC TEST_OUTPUT_PORT on port SEND_PORT issued by task MAIN PB1 ata sent immediately GET_PORT issued by task MAIN P2 blocked TEST_OUTPUT_PORT on port MAIN PBl Ia ll Now the user removes all queue watch points and sets a watch point on the task main pb1 for all rocs Each time an rpc originates from that task a message identifying the rpc and the target port where appropriate is displayed In this case main pb1 is an instance of the predefined broadcast task and so the rpcs are only simulated monitor dqwatch doing doing doing doing doing doing doing monitor twatch main pbl monitor go Observed task MAIN PB1 Observed task MAIN PB1 Observed task MAIN PB1 Observed task MAIN PB1 Observed task MAIN PB1 Observed task MAIN PB1 Observed task MAIN PB1 CMU SEI 89 TR 33 TEST INPUT PORT at port MAIN PB1 IN1 TEST OUTPUT PORT at port MAIN PB1 OUT1 TEST OUTPUT PORT at port MAIN PB1 0UT2 GET PORT at port MAIN PB1 IN1 SEND PORT at port MAIN PB1 0UT1 SEND PORT at port MAIN PB1 0UT2 SAFE 17 Break points work exactly like watch points except that when a break point is
4. an ex pected rpc name the expands to all the Durra interface call names If an optional argument is omitted the effect is the same as if the value of the argument were Excerpts from a sample monitoring session on the previously described example Durra application appear throughout the following discussion In all excerpts lines beginning with the prompt monitor represent commands and all other lines represent monitor responses 6 1 Go Quit and Ctrl C Commands This section describes commands which control the interaction between the monitor and executive go duration y The go command tells the executive to continue processing the application for a speci fied amount of time in seconds before prompting the users for more commands If no duration is specified the application runs indefinitely The user can always regain control by typing ctrl C to interrupt the monitor CMU SEI 89 TR 33 15 quit The quit command ends the monitoring session ctrl C A ctrl C interrupts the application and prompts the user for a monitor command 6 2 Watch and Break Commands This section describes commands which allow the user to follow the flow of data through an application and interrupt the application at any point of communication with the Durra runtime dpbreak por name rpc name dpwatch port name rpc name dqbreak queue name rpc name
5. of one of these commands Additional information is displayed when the situ ation warrants For instance if any break points or watch points have been set on the ports queues or tasks in question then that information will be shown monitor gt show port main p3 inl NAME MAIN P3 IN1 ID 2 CONFIGURATION LEVEL MAIN DATA_TYPE STRING ASSOCIATED_QUEUE MAIN QB3 STATUS CONFIGURED PORT_DIRECTION IN The following example shows that the receiving tasks are waiting for data at queues main gb2 and main gb3 but neither sender nor receiver is waiting at queue main qlb since no waiting client field is displayed Queue main qib has an up per bound of 10 messages and currently contains three The results of any active track command would also be displayed here CMU SEI 89 TR 33 19 moni NAM tor show queue MAIN Q1B GI URCE PORT STINATION PORT UND EMENT_COUNT ATUS MAIN OB2 rO O O D H NAM NFIGURATION LEVEL NFIGURATION LEVEL URCE PORT STINATION PORT UND EMENT COUNT WAITING CLIENT STATUS MAIN OB3 E gouQubumHuvuowmu HOmMOOU T I NFIGURATION LEVEL ESTINATION PORT UND ELEMENT COUNT WAITING CLIENT STATUS ID CO SOURCE PORT DE BO I Some explanation of the task fields may be required MAIN MAIN P1 OUT1 MAIN PB1 IN1 10 3 CONFIGUR
6. provide more infor mation than is desired For example if at some point during application execution one wished to know how many messages were in each queue one could display all queue information using the command show queue and then browse through it looking for the relevant numbers Instead we provide the show state command the purpose of which is to display a concise picture of the state of the tasks and queues comprising the application Below is a sample the user may assume that any task not shown is not blocked currently and any queue not shown is empty monitor show state Task MAIN P2 consumer blocked at queue MAIN OB2 Queue MAIN Q1B contains 1 messages bound 1 show track queue name The show track command displays the results of a track command on the specified queue s The tracking operation records the elapsed time since tracking began the number of data items that have passed through the queue during that time the average time a data item spent in the queue and the number of times the sending and receiving tasks blocked while attempting to write to or read from the queue In the following ex cerpt we see the user request a track operation on all queues The application starts and runs until interrupted from the keyboard The results of the tracking operation after 90 seconds show that 120 data elements passed through each queue The receiving task connected to main qb2 had to wait every time hence the avera
7. the task implementations or the task application descriptions CMU SEI 89 TR 33 13 14 CMU SEI 89 TR 33 6 Monitor Commands The Durra application debugger monitor 4 is an interactive process which communi cates with the Durra executive at runtime to provide a user with information about and control over the progress of the application There are two ways to start the monitor in the Unix environment To start the Monitor when the application is started one includes an optional flag to the dexec command this requires X Window System support from the environment To start the Monitor after an application has begun executing use the dmonitor command as described in Section 5 2 Commands to the monitor may be entered from the keyboard or from a file or files specified by the user Commands and keywords may be abbreviated to the shortest non ambiguous initial substring identifiers must always be complete This section de scribes the commands recognized by the monitor The following notation is used in the monitor command descriptions command or keyword identifier or literal value st a b means choice of a or b a means that a is an optional argument The character is a wildcard symbol implying all possible values that make sense in the context In the context of an expected port queue task or type name the ex pands to all such names in the application currently running In the context of
8. ED 2 MAIN MAIN PB1 OUT1 MAIN P2 INI 10 0 MAIN P2 CONFIGURED 3 MAIN MAIN PB1 0UT2 MAIN P3 INI 10 0 MAIN P3 CONFIGURED The fields Mailbox and Server mailbox refer to communications channels from the master executive to the task and from the master executive to the server executive that started the task respec tively PID and XPID are the process IDs of the task and any associated xterm 5 Signal Pending indicates whether or not a signal has been received from this task during a reconfiguration Time Out is the time in seconds that the task has to get to a quiescent state 6 for reconfiguration before it is terminated Quiesce Status in dicates whether or not the task is in a reconfigurable state moni NAME ND MAIN P1 K I C ILBOX RVER MAILBOX S PID XPID PORTS SIGNAL PENDING TIME OUT ESCE STATUS I D ONFIGURATION LEVEL A RUNABLI tor gt show task main pl USER 3 MAIN 9 5 10099 0 MAIN P1 0UT1 FALSI 20 CONFIG Gl R zal oO HG The lower_bound and upper_bouna in the following type description refer to bounds on the size of the type since both have a value of 8 type byte is fixed length 8 bits 20 CMU SEI 89 TR 33 monitor show type byte NAME BYTE KIND ID LOWER BOUND UPPER BOUND SIZE TYPE show state The show queue and show task commands described above may
9. Go Quit and Ctrl C Commands 6 2 Watch and Break Commands 6 3 Kill Stop and Resume Commands 6 4 Show and Track Commands 6 5 Read Echo and Silent Commands 6 6 Set Commands 6 7 Miscellaneous Commands Index CMU SEI 89 TR 33 CMU SEI 89 TR 33 List of Figures Figure 1 Durra Application Example Figure 2 Configuration File CMU SEI 89 TR 33
10. Technical Report CMU SEI 89 TR 033 ESD TR 89 044 Durra A Task Level Description Language User s Manual Mario R Barbacci Dennis L Doubleday Charles B Weinstock September 1989 Technical Report CMU SEI 89 TR 033 ESD TR 89 044 September 1989 Durra A Task Level Description Language User s Manual Mario R Barbacci Dennis L Doubleday Charles B Weinstock Software for Heterogeneous Machines Project Unlimited distribution subject to the copyright Software Engineering Institute Carnegie Mellon University Pittsburgh Pennsylvania 15213 This report was prepared for the SEI Joint Program Office HQ ESC AXS 5 Eglin Street Hanscom AFB MA 01731 2116 The ideas and findings in this report should not be construed as an official DoD position It is published in the interest of scientific and technical information exchange FOR THE COMMANDER signature on file Thomas R Miller Lt Col USAF SEI Joint Program Office This work is sponsored by the U S Department of Defense Copyright O 1989 by Carnegie Mellon University Permission to reproduce this document and to prepare derivative works from this document for internal use is granted provided the copyright and No Warranty statements are included with all reproductions and derivative works Requests for permission to reproduce this document or to prepare derivative works of this document for external and commercial use should be
11. a command file from which monitor commands should be read Command files may contain nested read commands When the monitor finishes reading the commands in the file command processing continues from the scope in which the read command was invoked unless the file contains a quit command in which case the monitor is terminated as usual echo The echo command requests that monitor commands be displayed as they are proc essed This is the default when commands are entered interactively If the commands 22 CMU SEI 89 TR 33 are being read by the monitor from a file the default is silent or no display except when the file is being read via a nested read command in which case the echoing status is inherited from the calling environment silent The silent command suppresses the display of monitor commands that are read from command files This is the default unless echo is inherited from an enclosing file This command has no effect when issued interactively 6 6 Set Commands This section describes the commands used to change certain values maintained by the Durra runtime set attribute task name attribute name attribute value The set attribute command gives the specified task an arbitrarily named attribute with an arbitrary string value Attributes controlling process execution location and display location do not take effect until the next time the process is started Some attribute names are reserved because they have special mea
12. addressed to the SEI Licensing Agent NO WARRANTY THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN AS IS BASIS CARNEGIE MELLON UNIVERSITY MAKES NO WARRAN TIES OF ANY KIND EITHER EXPRESSED OR IMPLIED AS TO ANY MATTER INCLUDING BUT NOT LIMITED TO WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY EXCLUSIVITY OR RESULTS OBTAINED FROM USE OF THE MATERIAL CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT TRADEMARK OR COPYRIGHT INFRINGEMENT This work was created in the performance of Federal Government Contract Number F19628 95 C 0003 with Carnegie Mellon University for the operation of the Software Engineering Institute a federally funded research and development center The Government of the United States has a royalty free government purpose license to use duplicate or disclose the work in whole or in part and in any manner and to have or permit others to do so for government purposes pursuant to the copyright license under the clause at 52 227 7013 This document is available through SAIC ASSET 1350 Earl L Core Road PO Box 3305 Morgantown West Virginia 26505 Phone 304 284 9000 FAX 304 284 9001 World Wide Web http www as set com sei html e mail webmaster O www asset com Copies of this document are available through the National Technical Information Service NTIS For informa tion on ordering please conta
13. cessor since the master executive will subsume the server function for that processor If the s option is not used the executive starts in master mode In master mode the dexec command allows additional options and parameters dexec master executive options executive_program_file_name The only parameter required by the master executive is the name of a file containing executive instructions By convention these files have names of the form application_name durra SCHED The dexec command supplies the appropriate file ex tensions durra and SCHED if they are missing For example dexec some_application invokes the executive with the file some_application durra SCHED dexec cconfiguration_file The c option specifies the name of a file containing network configuration information e g the names of the available processors on which tasks can execute If not speci fied the executive looks by default for the configuration file config txt first in the cur rent directory and then in each directory specified in the DURRA PATH environment variable Section 4 dexec m dexec mdmonitor display dexec mfmonitor command file CMU SEI 89 TR 33 11 The m options specify that the monitor task is started by the executive The user can then use the monitor command language to interact with the executive before the appli cation task start The monitor task is specified by the DURRA MONITOR enviro
14. configuration level to occur regardless of the state of any specified trigger condition The configuration label is optional if there is only one possible reconfiguration The command has no effect when the specified configuration does not exist or is un reachable from the current configuration The command also fails when another recon figuration is pending i e the executive has initiated a configuration change but has not yet completed it for instance when waiting for a task to get to a quiescent state Only one reconfiguration may be in progress at any point in time 24 CMU SEI 89 TR 33 References 1 2 3 4 5 6 M R Barbacci MasterTask The Durra Task Emulator Technical Report CMU SEI 88 TR 20 DTIC ADA199429 Software Engineering Institute Carnegie Mellon University July 1988 M R Barbacci D L Doubleday and C B Weinstock The Durra Runtime Environment Technical Report CMU SEI 88 TR 18 DTIC ADA199480 Software Engineering Institute Carnegie Mellon University July 1988 M R Barbacci and J M Wing Durra A Task Level Description Language Reference Manual Version 2 Technical Report CMU SEI 89 TR 34 Software Engineering Institute Carnegie Mellon University September 1989 D L Doubleday The Durra Application Debugger Monitor Technical Report CMU SEI 89 TR 32 Software Engineering Institute Carnegie Mellon University September 1989 R W Scheifler and J Getty
15. ct NTIS directly National Technical Information Service U S Department of Commerce Springfield VA 22161 Phone 703 487 4600 This document is also available through the Defense Technical Information Center DTIC DTIC provides access to and transfer of scientific and technical information for DoD personnel DoD contractors and potential contrac tors and other U S Government agency personnel and their contractors To obtain a copy please contact DTIC directly Defense Technical Information Center Attn BRR 8725 John J Kingman Road Suite 0944 Ft Bel voir VA 22060 6218 Phone 703 767 8274 or toll free in the U S 1 800 225 3842 Use of any trademarks in this report is not intended in any way to infringe on the rights of the trademark holder B Durra A Task Level Description Language User s Manual Abstract Durra is a language designed to support the development of large grained parallel programming applications This is the manual for users of the Durra compiler runtime system and support tools Additional documents that describe the syntax and semantics of the language and the runtime environ ment are cited in the bibliography section 1 Introduction The syntax and semantics of Durra are described in Durra A Task Level Description Language Reference Manual 3 This users manual supplements the language refer ence manual by describing the facilities available to a Durra user to compile debug and execute d
16. ecutive and execute the example application 12 CMU SEI 89 TR 33 Define the environment variables user set hetsim usr projects hetsim Start the executive with a user specified configuration file Executive will execute as master out of user gt setenv DURRA PATH hetsim tasklib hetsim exec user dexec cseiag config txt broadcast example durra usr projects hetsim exec executiv Using configuration file seiag config txt Executive Server is executing on ag sei cmu edu Application dependent output Opening parameter file Message count 500 Message size 20 Process 3 Source Task Message Size 20 Messages Count 500 Process A4 Sink Task Message Size 20 Messages Count 500 Process 5 Sink Task Message Size 20 Messages Count 500 Application runs to completion user gt The invocation of dexec in this example illustrates the use of a user specified configu ration file seiag config txt to override the default configuration file config txt In this particular example the configuration file used consisted of a single line processor ag sei cmu edu UVAX VAX SUN SEIE SEIAG SEIFI The effect of using such a configuration file is to fold all the network processors and processor classes into one machine Although this example is extreme it illustrates the ability to configure the network and to control the allocation of resources without modi fying
17. figuration File The purpose of the configuration file is to provide information about the hardware config uration to the Durra runtime executive Figure 2 illustrates the definition of the hardware configuration i e the values for the processor attribute processor fi sei cmu edu VAX UVAX SEIFI processor cu sei cmu edu VAX UVAX SEICU processor ag sei cmu edu VAX UVAX SEIAG processor e sei cmu edu VAX UVAX SEIE processor sei cmu edu VAX SEI processor cr sei cmu edu VAXVMS SEICR processor fh sei cmu edu SUN SEIFH processor af sei cmu edu SUN SEIAF xdisplay fi sei cmu edu 0 0 SEIFI xdisplay ag sei cmu edu 0 0 SEIAG xdisplay e sei cmu edu 0 0 SEIE Figure 2 Configuration File Each line of the configuration file identifies a resource available to execute task imple mentations The first field of the line processor or xdisplay identifies the type of line The second field specifies the Internet address of the processor e g fi sei cmu edu or the X window display unit e g ag sei cmu edu 0 0 The rest of the fields specify values for the processor or xdisplay attributes used in the task descriptions The values of the processor attribute are used to specify classes of machines For example the first line specifies that processor fi sei cmu edu belongs to classes VAX UVAX and SEIFI The names of the classes are arbitrary although it makes sense to choose mnemonic values
18. ge time a datum spent in the queue was zero since each was sent directly out when it arrived In the other two queues neither sender nor receiver ever blocked and so the average wait time in the queue is non zero CMU SEI 89 TR 33 21 monitor track monitor go keyboard interrupt monitor gt show track NAME MAIN OIlB ELAPSED TRACK TIME 90 0 seconds DATA FLOW COUNT 120 AVG TIME IN QUEUE 1 666E 3 seconds SENDER_BLOCKED 0 times RECEIVER BLOCKED 0 times NAME MAIN OB2 ELAPSED TRACK TIME 90 0 seconds DATA FLOW COUNT 120 AVG TIME IN QUEUE 0 000E 0 seconds SENDER_BLOCKED O times RECEIVER BLOCKED 120 times NAME MAIN QB3 ELAPSED TRACK TIME 90 0 seconds DATA FLOW COUNT 120 AVG_TIME_IN_QUEUE 8 333E 5 seconds SENDER_BLOCKED 0 times RECEIVER BLOCKED 0 times track queue name dtrack queue name Beginning at the time it is issued the track command initiates the collection of data through the specified queue s Partial results of the tracking can be displayed at any time with the show track command Tracking continues until the dtrack command is issued 6 5 Read Echo and Silent Commands This section describes commands which affect the manner in which the monitor commu nicates with its user read command file The read command specifies
19. ing system level As noted previously break points interrupt a task at the point of some interface call to the executive It may happen though that the user wishes to interrupt an application task that executes for long periods of time without resorting to an interface call on such occasions the stop and resume commands are useful The kill command might be used to simulate the occurrence of unexpected task failure for sys tem testing purposes 18 CMU SEI 89 TR 33 6 4 Show and Track Commands This section describes commands which allow the user to see information about the ap plication currently executing show attributes task name The show attributes command displays the attributes of the specified task s In the example following we see the attributes of task main p2 monitor show attributes main p2 ATTRIBUTES of task MAIN P2 implementation sink task processor SUN Source taskb durra TREE xdisplay 0 0 show configuration The show configuration command displays the name of the current configuration and all configurations which can be reached directly from the current level show port port name show queue queue name show task task name show type type name These commands display information the Durra executive knows about the application s Durra ports queues tasks and types Each of the following fragments demonstrates the results
20. ion description file name SCHED 2 4 Examples The following script illustrates the use of these commands to create a library file contain ing a reference to an external library to compile several task descriptions and an appli cation description and finally to generate the executive commands to execute the appli cation 4 CMU SEI 89 TR 33 user dlibrary c user dlibrary a usr projects hetsim durralib user user dall taska durra taskb durra taskc durra taskmain durra taska durra taska durra TREE Link V4 0 1989 08 14 23 20 25 taska durra TASK TASKA Entered in library taskb durra taskb durra TREE Link V4 0 1989 08 14 23 20 34 taskb durra TASK TASKB Entered in library taskc durra taskc durra TREE Link V4 0 1989 08 14 23 20 44 taskc durra TASK TASKC Entered in library taskmain durra taskmain durra TREE Link V4 0 1989 08 14 23 20 50 taskmain durra TASK MAIN Entered in library u ser gt user gt dcode taskmain durra taskmain durra TREE gt taskmain durra SCHED No Errors found Created taskmain durra SCHED user gt After each successful compilation the library file is augmented with the information about the new unit This information is used by the compiler to identify the units and to detect changes that might require recompiling dependent units CMU SEI 89 TR 33 5 CMU SEI 89 TR 33 3 Con
21. istributed applications All the features described in the Durra language reference manual are implemented with the following two exceptions 1 Function and timing specifications cannot be used in task selections and the behavioral information part of a task description is treated as commentary information by the compiler However timing expressions are used to emu late the behavior of a task by the Durra task emulator 1 2 Only sequences of full item transformations are supported Array element and record field transformations are not implemented To illustrate the various commands and support tools we will use a small Durra appli cation The example application in Figure 1 consists of two type definitions a data source task with one output port two data sink tasks each with one input port and an instance of the predefined task broadcast which transmits data received from the source task to each of the sink tasks CMU SEI 89 TR 33 1 a Application Structure type byte is size 8 type string is array of byte b Type Declarations task taska ports outl out string attributes processor vax implementation source_task end taska task taskb ports inl in string attributes processor sun implementation sink task end taskb task taskc ports inl in string attributes processor vax implementation sink task end taskc c Task Descriptions task main structure process pl task
22. lays a message each time an rpc targeted at main p1 out1 occurs In this case only Send_Port calls are occurring on that port The messages continue until there is no more activity on that port or until the user interrupts from the keyboard 16 CMU SEI 89 TR 33 mo mo Wa Wa Wa Wa Wa Wa Wa ni ni EC Ec CC CC CC AIN P1 OUT OUT1 JOUET OUT1 OUT1 OUT1 OUT1 tor pwatch main pl outl tor go h at port MAIN PI RPC SEND PORT h at port MAIN PI RPC SEND PORT h at port MAIN PI RPC SEND_PORT h at port MAIN PI RPC SEND_PORT h at port MAIN PI RPC SEND_PORT h at port MAIN PI RPC SEND_PORT h at port RPC SEND_PORT Next the user removes all port watch points and sets a queue watch point on queue main gb2 for all rpcs The queue has an associated producer port main pbl outl and an associated consumer port main p2 in1 The occurrence of an rpc on either port then causes a message to be displayed by the monitor If the port watch point had not been removed port and queue watch point responses would have been interleaved When a Send_Port or Get_Port occurs the monitor describes the queue state Below when the Send_Port occurs the consumer task is already waiting for the data and so the data is immediately transmitted bypassing the queue The con sumer then issues another Get_Port before any more data has been sent and so it is blocked waiting for data to arrive mo
23. ning to the Durra runtime see the Durra User s Manual for details set bound queue name positive integer value The set bound command changes the maximum size of the specified queue The change takes effect immediately If a task has been blocked attempting to write to the queue and the new bound is larger than the old bound the task will be unblocked 6 7 Miscellaneous Commands This section describes monitor commands which don t fit into any of the preceding cate gories debug task name debugger string The debug command requests that the specified task be run under control of a source level debugger The command must be issued before the task is started or it will have no effect The optional debugger string provides a way to specify some debugger in vocation other than the environment specified default e g special arguments to the de CMU SEI 89 TR 33 23 fault debugger or a different debugger altogether Since a separate terminal interface is required for each debugger activated this feature is only available when the environ ment supports the X Window System Instead of starting the task directly the Durra executive starts an xterm and runs the specified debugger in it giving it the task name as an argument help The help command displays an online help screen which lists the monitor commands reconfigure configuration label The reconfigure command causes a reconfiguration to the specified
24. nment variable see Section 4 If mdmonitor display is specified then the X window for the monitor appears on the specified display otherwise it appears on the default display identified in the environment If mfmonitor command file is specified then the monitor reads its initial commands from the specified file dexec qqueue size The q option specifies the default size number of elements for those queues whose size was not provided in the task or application descriptions If this option is not speci fied the default queue size is 1 5 2 DMonitor Command The dmonitor command starts the Durra application debugger monitor dmonitor optional parameters This command may be issued on any currently configured processor The Durra execu tive must be running on some node in the configuration so that the monitor will be able to communicate with it dmonitor fmonitor command file The f option specifies a file from which the monitor will read an initial set of commands The default is interactive input dmonitor hexecutive host processor name The h option specifies the name of a processor on which an executive is currently run ning This parameter defaults to the local processor and must be supplied if the monitor is started on a processor on which there is no running executive 5 3 Examples The following script illustrates the use of these commands to define the environment variables start servers and ex
25. nt variables DURRA PATH is list of directories containing the task implementations and other run time programs including the location of the servers and executive This variable must be defined before running a Durra application For example it could be defined by setenv DURRA PATH hetsim tasklib hetsim exec DURRA MONITOR is the name of the monitor task The executive will start the monitor task if the m switch is used with the dexec command Section 5 1 For example it could be defined by setenv DURRA MONITOR hetsim mon monitor DURRA MONITOR WINDOW defines the window for the monitor task For example it could be defined by setenv DURRA MONITOR WINDOW geometry 80x50 150 20 CMU SEI 89 TR 33 9 10 CMU SEI 89 TR 33 5 Execution Commands Two Unix commands have been defined to invoke the runtime executive and monitor dexec and dmonitor 5 1 DExec Command The dexec command starts the executive This command must be issued on each processor available to the application The executive can run in two modes master and server One of the processors must run the master executive the others must run server executives dexec s The s options starts a executive in server mode This command must be issued on each processor that is to execute any of the application tasks However if any of these processors is also used to run the master executive then it is not necessary to start a server executive on that pro
26. reached the application is interrupted and the user has the opportunity to enter more commands In the following excerpt the user removes the watch points previously set and then sets a break point on any task doing a Get Port At each occurrence the user responds with the go command and the application continues to the next instance of Get Port The task break point is then removed and a queue break point set The effect of the queue break point is analogous to that of the task break point monitor dtwatch monitor tbreak get port monitor go Break at task MAIN PB1 doing GET PORT at port MAIN PB1 IN1 monitor go Break at task MAIN P3 doing GET PORT at port MAIN P3 IN1 monitor go Break at task MAIN P2 doing GET PORT at port MAIN P2 IN1 monitor dtbreak monitor qbreak main qlb monitor go Break at queue MAIN Q1B RPC SEND PORT issued by task MAIN P1 Some task already waiting data sent immediately monitor go Break at queue MAIN Q1B RPC TEST INPUT PORT on port MAIN PB1 IN1 monitor go Break at queue MAIN Q1B RPC GET PORT issued by task MAIN PB1 6 3 Kill Stop and Resume Commands This section describes commands used to control the execution state of an application s component tasks kill task name stop task name resume iask name These commands are used to terminate pause or continue execution of a task at the operat
27. s The X Window System ACM Transactions on Graphics 5 2 79 109 April 1986 C B Weinstock Performance and Reliability Enhancement of the Durra Runtime Environment Technical Report CMU SEI 89 TR 8 DTIC ADA207445 Software Engineering Institute Carnegie Mellon University February 1989 CMU SEI 89 TR 33 25 26 CMU SEI 89 TR 33 Index 15 DLIBRARY 3 Broadcast 17 Configuration file 7 Ctrl C 15 16 Dall 3 4 Dcode 3 4 Debug 23 Dexec 9 11 15 Dlibrary 3 Dmonitor 11 12 15 Dpbreak 16 Dpwatch 16 Dqbreak 16 Dqwatch 16 Dtbreak 16 Dtrack 22 Dtwatch 16 DURRA MONITOR 9 12 DURRA MONITOR WINDOW 9 DURRA PATH 9 Echo 22 23 Go 15 16 18 Help 24 Interrupt 15 Kill 18 Library file 3 Pbreak 16 Processor 7 Pwatch 16 Qbreak 16 Quiescent 20 24 Quit 16 22 Qwatch 16 Read 22 23 Reconfigure 24 Resume 18 Set attribute 23 CMU SEI 89 TR 33 Set bound 23 Show attributes 19 Show configuration 19 Show port 19 Show queue 19 21 Show state 21 Show task 19 21 Show track 21 22 Show type 19 Silent 23 Stop 18 Tbreak 16 Track 19 21 22 Twatch 16 Xdisplay 7 Xterm 20 28 CMU SEI 89 TR 33 Table of Contents 1 Introduction 2 Compilation Commands 2 1 DLibrary Command 2 2 DAll Command 2 3 DCode Command 2 4 Examples 3 Configuration File 4 Execution Environment 5 Execution Commands 5 1 DExec Command 5 2 DMonitor Command 5 3 Examples 6 Monitor Commands 6 1
28. taska p2 task taskb p3 task taskc pb task broadcast ports inl in string outl out2 out string end broadcast queues qlb 10 pl outl gt gt pb inl gqb2 10 pb outl gt gt p2 inl qb3 10 pb out2 gt gt p3 inl end main d Application Description Figure 1 Durra Application Example CMU SEI 89 TR 33 2 Compilation Commands Three Unix commands have been defined to invoke the Durra compiler the executive command generator and the Durra library management utility dall dcode and dlibrary 2 1 DLibrary Command The dlibrary command implements a modest library management utility dlibrary options file names The Durra library is a text file containing information about the various compilation units stored in the library and pointers to other libraries containing additional units The com piler looks first in the current library then in the libraries referenced in the current library and so on The library file is always named DLIBRARY and there can be at most one library file per Unix directory dlibrary c The c option creates a new library or reinitializes an existing library This command is normally used when starting the development of a new application dlibrary a directory name The a option extends the library by adding a pointer to a remote directory to be searched for imported task descriptions or type declarations dlibrary r directory name The r option complements
29. the a option and removes a pointer to a remote directory Task descriptions and type declarations defined in that directory are no longer acces sible dlibrary d durra file name The d option deletes a task description or type declaration from the library the source files are not disturbed only the library entry is deleted Under normal conditions there is no need to delete library entries using this option because the compiler takes care of inserting or deleting task descriptions or type declarations from the library CMU SEI 89 TR 33 3 2 2 DAII Command The dall command invokes the Durra compiler to process a type declaration a task de scription or an application description A lower level i e component task or type must be compiled before a higher level task or type that uses it dall durra description file name By convention a Durra source file name has the extension durra although this is not mandatory The output file syntax tree stored in the library is named durra description file name TREE 2 3 DCode Command The dcode command generates the executive instructions for the application dcode application description file name This command must be issued after all the components and the application descriptions have been compiled with the dall command This command is applied only to the appli cation description file and not to the component task files The output file executive program is named applicat
Download Pdf Manuals
Related Search