02/08/84 eis_tester, et Syntax: et path {-control_args} Function: sets up and tests EIS instructions in a controlled environment. You must prepare an input script describing the EIS instructions to be tested. From this input script the EIS tester builds the EIS instructions (one at a time) and the indirect words, descriptors, and data that each instruction needs. The instruction to be tested is set up in a special ALM segment (etx). The eis_tester command calls etx in order to execute the EIS instruction; etx returns to eis_tester when the instruction has been executed. After executing the instruction, eis_tester tests correct execution of the instruction. If one of the test scripts in the ets data base fails and the successful execution of that test is dependent upon installation of a particular FCO, the FCO number is displayed in the error message. See the Multics System Diagnostic Aids manual (AR97) for details on the operation of the EIS tester and on how to write script input tests. Arguments: path is the pathname of a segment that contains input script data that defines the instructions to test. Control arguments: -brief, -bf suppresses all output except identification and error messages. -nox sets up the instruction but does not execute it; used to test the validity of the input script. -debug runs the test in a debugging loop where each instruction is tested 10 times but results from the test are not checked. Each time through the loop the instruction is set up completely, including all the specified faults. -select N, -sel N, -do N processes only test N (where N is a positive decimal number). This number has no relationship to the -ns field in any test. -help displays a brief usage statement. -instruction_type INSTR, -inst INSTR processes only tests that contain the instruction INSTR. -long, -lg displays all the related test information prior to executing a test. -repeat N, -rpt N repeats the entire execution of the selected tests N times. -stop_on_failure, -sof displays the failing data, machine condition, and history register information and return to command level if an error is detected in a test. The default is to display the failing data and continue with the next test. -from N, -fm N starts processing test N (where N is a positive decimal number) and continues processing all remaining tests in the input segment unless -to is used. -to N stops processing after test N (where N is a positive decimal number). If -from is not used, tests one through N are processed. Notes: The eis_tester program prints a message noting the beginning of each instruction test. It also prints the number of this test. If there are errors, it prints the incorrect data or incorrect indicators. If you do not specify -brief, then the data that eis_tester has set up for this instruction is printed before the instruction is executed. The eis_tester program is the main procedure in the EIS instruction tester. It calls et_test to parse the statements in your data file. It translates these statements into the data needed to build and test an EIS instruction in the external segment etx. After building the instruction, this procedure calls etx in order to execute the EIS instruction. When etx returns, the results of the EIS instruction are examined. The eis_tester program continues to build and test EIS instructions until there is no data left in the input file. The failure of one instruction only causes the termination of that one instruction test. Any remaining instructions specified in the input file are processed and tested. ----------------------------------------------------------- Historical Background This edition of the Multics software materials and documentation is provided and donated to Massachusetts Institute of Technology by Group BULL including BULL HN Information Systems Inc. as a contribution to computer science knowledge. This donation is made also to give evidence of the common contributions of Massachusetts Institute of Technology, Bell Laboratories, General Electric, Honeywell Information Systems Inc., Honeywell BULL Inc., Groupe BULL and BULL HN Information Systems Inc. to the development of this operating system. Multics development was initiated by Massachusetts Institute of Technology Project MAC (1963-1970), renamed the MIT Laboratory for Computer Science and Artificial Intelligence in the mid 1970s, under the leadership of Professor Fernando Jose Corbato. Users consider that Multics provided the best software architecture for managing computer hardware properly and for executing programs. Many subsequent operating systems incorporated Multics principles. Multics was distributed in 1975 to 2000 by Group Bull in Europe , and in the U.S. by Bull HN Information Systems Inc., as successor in interest by change in name only to Honeywell Bull Inc. and Honeywell Information Systems Inc. . ----------------------------------------------------------- Permission to use, copy, modify, and distribute these programs and their documentation for any purpose and without fee is hereby granted,provided that the below copyright notice and historical background appear in all copies and that both the copyright notice and historical background and this permission notice appear in supporting documentation, and that the names of MIT, HIS, BULL or BULL HN not be used in advertising or publicity pertaining to distribution of the programs without specific prior written permission. Copyright 1972 by Massachusetts Institute of Technology and Honeywell Information Systems Inc. Copyright 2006 by BULL HN Information Systems Inc. Copyright 2006 by Bull SAS All Rights Reserved