|
I wrote the same kind of program myself recently, with a lot of parameters being passed (18 parameters). There are 4 files I wound up having to maintain. AgingFM - The Display file AgingCL - The initial CL that calls the display file and then submits the job AgingJQ - The CL that is submitted and that calls the RPG program Aging - The RPG program itself. It is a pain to have to maintain 4 files. I added 2 parameters the other day and had to modify all 4 programs, then run to see if I missed anything, which I did, so had to fix it and re run it. I don't remember why I wound up with 2 CLs instead of 1, however, but it probably has something to do with not being able to pass numerics other than 15,5 to RPG programs and I wanted to pass them at their real lengths and not have to kludge my program. By creative parameter passing I wound up with my RPG receiving them as numeric but passing them as strings in the CL. I could probably get rid of the second CL if I wished. The selection criteria is processed in the RPG program itself, not the CL. The CL just passes on the information. I could think of other ways I could do this, but wouldn't want to, such as a data queue, a file with the parameters written and then read, etc... They are parameters, pass them as such is my opinion. Regards, Jim Langston The second thing that goes is your memory. I don't remember what the first this is. Jose Vega wrote: > > Newbie question here, > > I want to call a query from either an RPG or CL program, with parms passed > in from a screen. Passing the parms might be tricky. I think this would be > easier than writing the rpg program that generates the report but could be > wrong. I am using DBU and we are an rpg400 shop. Any comments or > suggestions would be appreciated. > Thanks. +--- | 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.