Browse Prior Art Database

Use of AML Gf Ii Robotic Software Multi-Tasking Capability for Increased Program Storage Capacity

IP.com Disclosure Number: IPCOM000037334D
Original Publication Date: 1989-Dec-01
Included in the Prior Art Database: 2005-Jan-29
Document File: 1 page(s) / 12K

Publishing Venue

IBM

Related People

Barnes, RD: AUTHOR

Abstract

A software control method is disclosed which utilizes the greater data space made available through multi-tasking in the enhanced version of the IBM AML (A Manufacturing Language) operating system running on a Series 1 computer. (Image Omitted)

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 87% of the total text.

Page 1 of 1

Use of AML Gf Ii Robotic Software Multi-Tasking Capability for Increased Program Storage Capacity

A software control method is disclosed which utilizes the greater data space made available through multi-tasking in the enhanced version of the IBM AML (A Manufacturing Language) operating system running on a Series 1 computer.

(Image Omitted)

The operating system allows the creation of up to four multi- tasking partitions or "tasks", each additional task being a duplicate of the original workspace. The data space made available through the creation of the other tasks may be used for program storage to prevent loading and unloading files during the machine cycle. Refer to Fig. 1, which demonstrates the creation of the additional tasks.

A control loop is used in each of the additional tasks (TASK2, TASK3) to supervise the execution of subroutines in that task. TASK1 is used to control the machine cycle by requesting the execution of subroutines in the other tasks via semaphores. During the execution of these subroutines, TASK1 provides a real- time display of status and messages passed from the subroutines via shared variables. Refer to Fig. 2, which demonstrates the machine cycle control, status display, and error handling in TASK1.

(Image Omitted)

The control loops executing in TASK2 and TASK3 are identical in structure. The loop is designed to meet two ground rules: 1) all errors must be passed to TASK1; 2) the loop must always remain in control (i.e., there is no...