Threaded environment for AS/400

• US 5,504,898 A
• Filed: 06/20/1994
• Issued: 04/02/1996
• Est. Priority Date: 06/20/1994
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: Candle Distributed Solutions, Inc.
• Inventors: Klein, Paul
• Primary Examiner(s): Heckler, Thomas M.
• Application Number:
  US08/261,795
• Time in Patent Office: 652 Days
• Field of Search: 395/650, 395/700
• US Class Current: 718/101
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system

Abstract

An AS/400 computer is provided with a threaded environment by using thread related batch jobs to accept thread tasks and individually apply them to specialized batch jobs that perform the tasks. Return data is applied by the thread related batch jobs to a common queue and the using application is caused to wait on the common queue, thereby overcoming the AS/400 limitation that an application can only wait on one queue at a time. The thread tasks are thereby performed asynchronously while the user application effectively waits on all such thread tasks by waiting on the common queue. The threaded environment maintains a pool of active thread related batch jobs and permits the cloning of new thread related batch jobs from existing thread related batch jobs to efficiently manage the thread pool.

Claims

1. A method of operating an AS/400 computer system, comprising the steps of:

applying each of a plurality of asynchronous thread tasks from an application as an input to each of a plurality of thread related batch jobs;

operating each such thread related batch job to perform the thread task applied thereto and produce return data associated with each said thread task;

applying the return data from each such thread related batch job to a single, common queue; and

causing the application to wait on the common queue to sequentially retrieve the return data from each of said thread tasks therefrom.

2. The invention of claim 1, wherein the step of operating each batch job to perform the thread task applied thereto further comprises the steps of:

reapplying the thread task from each such thread related batch job to a job queue associated with a specialized batch job specifically created to perform the thread task applied to the thread related batch job;

operating the specialized batch job to

wait on the job queue,

retrieve the thread task therefrom,

perform the thread task, and

return data to the job queue associated with the performance of the thread task by the specialized batch job; and

causing the thread related batch job to wait on the job queue to retrieve the return data therefrom,

whereby the application may utilize preexisting specialized batch jobs not configured to return data to the common queue to perform as an asynchronous thread task.

3. The invention of claim 1, wherein the step of applying each of a plurality of asynchronous thread tasks from an application as an input to each of a plurality of thread related batch jobs further comprises the steps of:

applying each of the plurality of asynchronous thread tasks to a thread queue associated with each of the plurality of thread related batch jobs;

causing each such thread related batch job to wait on the thread queue associated therewith in order to retrieve the thread task thereon,

whereby each thread related batch job may be used to sequentially perform a plurality of different thread tasks.

4. The invention of claim 1, further comprising the steps of:

creating an additional thread related batch job by cloning an existing thread related batch job.