|
I don't understand your concern with the issues you raise. Most applications today use several programs to do their task. The days of the monolithic 400 and 500 (and sometimes even larger!) line programs are dead, thank goodness. Also I've been told repeatedly that QTEMP travels with the submitted job. Is this is not true? Did I hear wrongly? _______________________ Booth Martin Booth@MartinVT.com http://www.MartinVT.com _______________________ "York, Albert" <albert.york@nissan-usa.com> Sent by: owner-rpg400-l@midrange.com 10/18/2000 07:59 PM Please respond to RPG400-L To: "'RPG400-L@midrange.com'" <RPG400-L@midrange.com> cc: Subject: RE: Accessing files In QTEMP There may be only one program, but there will still be two jobs. I have seen programs written this way but in my mind it just complicates things. What you have are two programs (interactive and batch) in one source file. I have found it to be easier to maintain as two separate programs. This doesn't address the problem though. The files created in the QTEMP library of the interactive job are not available in the batch job. The LDA is available but not the files. -----Original Message----- From: booth@martinvt.com [SMTP:booth@martinvt.com] Sent: Wednesday, October 18, 2000 4:11 PM To: RPG400-L@midrange.com Subject: RE: Accessing files In QTEMP OK, what am I missing here? I do this all the time and it works easily. Write a CL that checks if it is interactive or batch. If it's interactive, put QTEMP at the top of your library list. CRTDUPOBJ into QTEMP for all the files you need. They'll be empty and ready to use. Have the CL run the interactive program for you. Finish the interactive job and (still in the CL) submit the CL. Then, put the GOTO for the interactive/batch test (from the beginning of the CL), then put in all of your batch processes. By doing it this way, there's only one job. _______________________ Booth Martin Booth@MartinVT.com http://www.MartinVT.com _______________________ Frank Carpenter <fcarpenter@emedco.com> Sent by: owner-rpg400-l@midrange.com 10/18/2000 11:11 AM Please respond to RPG400-L To: "'RPG400-L@midrange.com'" <RPG400-L@midrange.com> cc: Subject: RE: Accessing files In QTEMP That's exactly how it's running. I'm currently setting up a file which will contain a unique member id based upon the job and will pass that member id along to the submitted job. To keep things clean I'll delete the member from the file when the job ends. I was just hoping that there was a cleaner way. Thanks anyhow. Frank Carpenter EMED Co., Inc. fcarpenter@emedco.com 716 626-1616 ext. 374 -----Original Message----- From: Chris Bipes [mailto:chris.bipes@cross-check.com] Sent: Wednesday, October 18, 2000 10:20 AM To: 'RPG400-L@midrange.com' Subject: RE: Accessing files In QTEMP Is the first part running interactively? Submitting the main processing to batch? If yes to both, we share one file for the interactive part and key by job name/user/number. Pass that as a parms to the batch program to process only those records. Qtemp cannot be shared between jobs, easily. Good Luck, Christopher K. Bipes mailto:ChrisB@Cross-Check.com Sr. Programmer/Analyst mailto:Chris_Bipes@Yahoo.com CrossCheck, Inc. http://www.cross-check.com 6119 State Farm Drive Phone: 707 586-0551 x 1102 Rohnert Park CA 94928 Fax: 707 586-1884 If consistency is the hobgoblin of little minds, only geniuses work here. Karen Herbelin - Readers Digest 3/2000 -----Original Message----- From: Frank Carpenter [mailto:fcarpenter@emedco.com] Sent: Wednesday, October 18, 2000 6:29 AM To: RPG400-L@midrange.com Subject: Accessing files In QTEMP Hi all I'm sure this is an easy way to do this that I don't know about. I have an RPG program that produces a file in QTEMP. The job then submits a second job. I need to be able to access the files created in the QTEMP library from the first job. How can I pass the files with the submitted job? I want to use QTEMP because several users can be running this job at the same time and QTEMP will allow me to have individual copies of the same files without banging into each other. Any help/suggestions would be appreciated. Frank Carpenter EMED Co., Inc. fcarpenter@emedco.com <mailto:fcarpenter@emedco.com> 716 626-1616 ext. 374 +--- | 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 +--- +--- | 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 +--- +--- | 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.