SIMON (Batch Interactive test/debug)
- SIMON (Batch Interactive test/debug)
SIMON (Batch interactive test/debug) was a proprietary test/debugging toolkit for interactively testing Batch programs designed to run on IBM's System 360/370/390 architecture.
It operated in two modes, one of which was full Instruction Set Simulator mode and provided Instruction step, conditional Program Breakpoint ("Pause") and storage alteration features for Assembler, COBOL and PL/1 programs.
High level language (HLL) users were also able to see and modify variables directly at a breakpoint by their symbolic names and set conditional breakpoints by data content.
Many of the features were also available in "partial monitor mode" which relied on deliberately interrupting the program at pre-defined points or when a "program check" occurred.In this mode, processing was not significantly different from normal processing speed without monitoring.
It additionally provided features to prevent application program errors such as Program Check, "Wild branch" , and Program loop. It was possible to correct many errors and interactively alter the control flow of the executing application program. This permitted more errors to be detected for each compilation which, at the time, were often scheduled batch jobs with printed output, often requiring several hours "turnaround" before the next test run.
Operating Systems
Simon could be executed on IBM MVS, MVS/XA, ESA or DOS/VSE operating systems and required IBM 3270 terminals for interaction with the application program.
Origin of the product name
The name SIMON was not an acronym (despite its suggestive connection to instruction SIMulatiON). In fact it was simply named after the writer's son, like its predecessor OLIVER!
ee also
* Assembly language
* Batch programs
* Instruction Set Simulator for description of "full simulation mode"
* OLIVER (CICS interactive test/debug)
* SIMMON a similar tool, internal to IBM laboratories and written entirely independently
Wikimedia Foundation.
2010.
Look at other dictionaries:
IBM OLIVER (CICS interactive test/debug) — OLIVER (CICS interactive test/debug) was a proprietary testing and debugging toolkit for interactively testing programs designed to run on IBM s Customer Information Control System (CICS) on IBM s System/360/370/390 architecture. It provided… … Wikipedia
Debug symbol — A debug symbol is information that expresses which programming language constructs generated a specific piece of machine code in a given executable module. Sometimes the symbolic information is compiled together with the module s binary file, or… … Wikipedia
Simon — See also: Simeon Infobox Given name 2 gender = male meaning = he has heard origin = Genesis 29:33Simon is a common name, from Hebrew שִׁמְעוֹן Šimʿon , meaning he [God] has heard (compare Ishmael ). *Simeon (name) *Simon (surname)People called… … Wikipedia
Debugger — A debugger or debugging tool is a computer program that is used to test and debug other programs (the target program). The code to be examined might alternatively be running on an instruction set simulator (ISS), a technique that allows great… … Wikipedia
Wild branch — In computer programming, a wild branch is a description of a GOTO instruction where the target address is indeterminate, random or otherwise unintended. [ [http://www.priorartdatabase.com/IPCOM/000099292/ Debug Aid for Wild Branch Conditions ] ]… … Wikipedia
Dynamic program analysis — is the analysis of computer software that is performed by executing programs built from that software system on a real or virtual processor. For dynamic program analysis to be effective, the target program must be executed with sufficient test… … Wikipedia
Динамический анализ кода — (англ. Dynamic program analysis) анализ программного обеспечения, выполняемый при помощи выполнения программ на реальном или виртуальном процессоре (анализ, выполняемый без запуска программ называется статический анализ кода). Утилиты… … Википедия
Instruction step — An instruction step is a method of executing a computer program one step at a time to determine how it is functioning. This might be to determine if the correct program flow is being followed in the program during the execution or to see if… … Wikipedia
Breakpoint — A breakpoint, in software development, is an intentional stopping or pausing place in a program, put in place for debugging purposes. More generally, a breakpoint is a means of acquiring knowledge about a program during its execution. During the… … Wikipedia
