James, Argreed. But even more important than actually creating and destroying the thread, are the thread synchronization objects such as Critical Sections, Events and Mutex's. Without these, you WILL corrupt data. The only question is when. Bob -----Original Message----- From: email@example.com [mailto:firstname.lastname@example.org]On Behalf Of James Rich Sent: Monday, January 14, 2002 4:06 PM To: email@example.com Subject: Re: Multithreading (was 'more good iseries news') On Mon, 14 Jan 2002, Andy Nolen-Parkhouse wrote: > A standard, single-threaded program will not take advantage of more than > one processor. This would include the standard RPG/COBOL interactive > and batch programs found in most older systems. Multi-threaded > applications should be able to take advantage of multiple processors, > although I'm a little over my head here as to specifics. I don't know > whether the HTTP server supports multiple threads. I'm unsure of the capabilities of *new* RPG programs to take advantage of multi-threading. Multi-threaded apps have ops such as thread_create(), thread_lock(), thread_destroy(), etc. (or some variation). RPG doesn't have these ops as far as I know. Perhaps the compiler can do some fancy magic to enable threading but it seems unlikely. James Rich firstname.lastname@example.org _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-Lemail@example.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.