× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On Fri, 11 Feb 2005 15:22:23 -0500, Wilt, Charles <CWilt@xxxxxxxxxxxx> wrote:
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Steve Richter
> > Sent: Friday, February 11, 2005 12:15 PM
> > To: Midrange Systems Technical Discussion
> > Subject: Re: allow multiple threads in interactive job
> >
> >
> >
> > that stinks!  I was going to try and implement a message loop style of
> > programming in an interactive job.  The idea being to use the C record
> > io functions for display file i/o in a 2nd thread of the job.  A 3rd
> > thread might wait on an object lock.  or do a dlyjob. I was thinking
> > you could even use RCVJRNE to place a message on the message loop
> > queue when a record was added to a file.  All the threads then feed
> > their input to the data queue that the interactive job receives from
> > as its message loop.
> >
> > Was not sure if I could cancel a display file read in the background
> > thread without using INVITE or not.
> >
> > Too bad IBM places all these restrictions on their system.
> >
> > thanks,
> >
> > -Steve
> 
> My understanding is that threads were originally developed on other >systems 
> to work around those systems limitations of process switching >and sharing 
> between processes.  The AS/400 never had such limitations >so multi-threading 
> wasn't a requirement originally.
> 
> http://www.serpentine.com/~bos/os-faq/FAQ-1.html#Threads
> http://www.serpentine.com/~bos/os-faq/FAQ-1.html#The-history-of-threads

those are good links Charles.  Thanks.  
A thread to me is a way to organize work on the system. All the
threads of a job end when a job ends.  Threads share the address space
of a job. Threads also dont display in the WRKACTJOB display ( unless
you drill down from the job ).  They run with the same user profile as
the job and dont take long to start and end.

> As I understand it, the only reason threads were added to the 400 was to 
> >support Client-Server type applications where you are constantly starting 
> >and ending threads.  Since a process startup on the 400 is >still 
> "exspensive".

What about the scenario I described?  Message loop / event driven
programs have been proven to be a valid way of structuring a program.

> 
> End result, thread support on the 400 is a recent requirement, and no >doubt 
> will improve as time goes on.

I dont share your optimism on that.  I had been told on these lists
that it was only RPG that did not support threads on the as400.  It
was disappointing to learn today that os400 does not support threads
in interactive jobs.

-Steve

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.