|
Yes. Exactly. We agree. Richard Jackson mailto:richardjackson@richardjackson.net www.richardjacksonltd.com Voice: 1 (303) 808-8058 Fax: 1 (303) 663-4325 -----Original Message----- From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On Behalf Of Mark Holliday Sent: Tuesday, July 18, 2000 11:46 AM To: 'RPG400-L@midrange.com' Subject: Re: RPG/400 pgm strange behavior Richard Jackson wrote: > Using a command interface to solve this problem > is pointless and a gigantic waste of > CPU and human cycles. Scott Klement wrote: >You shouldn't have this problem calling from a CL program to another CL >program. However, if you do a SBMJOB from a CL program to call another >CL program, you'll run into this error again. Maybe thats what you're >thinking of? You're right on the money, Scott. A co-worker and I wrote an email utility that sits on the MSF and monitors for incoming messages. Obviously the pgm's run in batch. Thanks for pointing out the difference. I would guess that Richard is referring to interactive jobs and that he's well aware of the batch vs. interactive issue. Mark +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
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.