Browse Prior Art Database

Interactive Command Block Generator

IP.com Disclosure Number: IPCOM000036686D
Original Publication Date: 1989-Oct-01
Included in the Prior Art Database: 2005-Jan-29
Document File: 2 page(s) / 38K

Publishing Venue

IBM

Related People

Fawcett, BW: AUTHOR

Abstract

This article describes a code debugger tool for use in a multi-tasking environment. This debugger provides a human-friendly, interactive interface to the task-under-test functions. It enables the operator to build and send task control blocks interactively and have the results immediately displayed. The data in the request and the response is interpreted by the debugger in human-understandable terms, not just hex data.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 61% of the total text.

Page 1 of 2

Interactive Command Block Generator

This article describes a code debugger tool for use in a multi-tasking environment. This debugger provides a human-friendly, interactive interface to the task-under-test functions. It enables the operator to build and send task control blocks interactively and have the results immediately displayed. The data in the request and the response is interpreted by the debugger in human- understandable terms, not just hex data.

This is done by creating a driver task that serves as the interface between the task-under-test and the operator. It interfaces to the operator via an attached console (typically through an asynchronous communication port). And it interfaces to the task-under-test via the multi-tasking operating system's send facilities.

Here is a typical scenario:

1. Operator starts up the system.

2. Driver task displays a menu of target tasks (via

the console).

3. Operator selects target task-under-test.

4. Driver task initializes the task-under-test

control block format and data interpretation

algorithms to those associated with the selected

task. Because the different task's control block

and data definition may vary, this step is very

important for customizing the driver task to the

selected target task.

5. Operator edits the control block. The operator

may ask for assistance by pressing the help key.

This help key causes the driver task to run

special data interpretation routines which will

perform some data validation che...