|
I see your point very well, here is how we do it: <-interactive-><------ batch ------> CMD -> CL -> CMD -> CL -> RPg - The command prompt for any parameters - the CL programs has 2 section: interactive and batch (using the RTVJOBA command, a CL can find out if it is running in batch or interactive) - The interactive part does a SBMJOB of the command - The batch part does the call to the RPG This may sound complicated but once you see it, it is fairly straightfoward. Denis Robitaille Cascades inc. Tel: 819-363-5187 DRobitaille@cascades.com >>> "Moore, Rob" <moorer@londonhydro.com> 09/30 1:16 pm >>> See I am using a CMD --> CL --> RPG. I use the CMD just to prompt the user for the parameters (plus with help text and parameter options and some validation checking). All the CL program does is takes those parms and SBMJOB a call to the RPG program. I may very well add some job monitoring here as well (ie. Message monitoring). I suppose I could get away without the CL program and just have the command call the RPG...but I don't think I could use the SBMJOB then. Because if I SBMJOB CMD(mycmd) the user will not be prompted as this now batch job will not be attached to any particular terminal. Rob Moore Phone: (519) 661-5893 Technical Analyst Fax: (519) 661-4760 London Hydro E-mail : moorer@londonhydro.com <mailto:moorer@londonhydro.com> -----Original Message----- From: Denis Robitaille [mailto:DRobitaille@Cascades.com] Sent: Wednesday, September 30, 1998 11:35 AM To: RPG400-L@midrange.com Subject: Re: RE: Passing parms to RPG I had forgotten this special case. Her we go around that by using a command as a front end to our programs. This way if we SBMJOB the command, the parameter description stay unchanged. Denis Robitaille Cascades inc. Tel: 819-363-5187 DRobitaille@cascades.com >>> "Moore, Rob" <moorer@londonhydro.com> 09/30 10:17 am >>> Ok, I have found the problem. Because my CL program uses the SBMJOB command to CALL my RPG program, the SBMJOB command translates all my parameters to constants first, therefore forcing my RPG program to except only 15,5 DEC variables as the rules state for passing constants. When you pass decimal constants to a program, the receiving program must declare the parameters as *DEC with length 15,5. There is no allowance for any other length. (CL for the AS/400 - 2nd edition, Bryan Meyers & Dan Riehl). It was fine if I removed the SBMJOB and just did a plain CALL....which isn't what I really wanted to do. So I will stick with the SBMJOB and the 15,5. Thanks for the great discussion. BTW - I would highly recommend the CL programming book noted above...it is most excellent. Rob Moore Phone: (519) 661-5893 Technical Analyst Fax: (519) 661-4760 London Hydro E-mail : moorer@londonhydro.com <mailto:moorer@londonhydro.com> -----Original Message----- From: Buck Calabro [mailto:mcalabro@commsoft.net] Sent: Tuesday, September 29, 1998 2:50 PM To: 'RPG400-L@midrange.com' Subject: RE: Passing parms to RPG On Tuesday, September 29, 1998 1:02 PM, Moore, Rob [SMTP:moorer@londonhydro.com] wrote: > Oh yes, thanks. I think I remember reading somewhere that the default > parm > size for DEC is 15 5. Yes, it's the default, but you're not using the default here: you've specified *DEC (3 0) in the CL and PARM 3 0 in the RPG. I think Dennis R hit the nail on the head when he mentioned data structures. See if your RPG program is putting the parm in a DS. If it is, then the DS will change the definition from PACK to ZONE - check the compile listing to verify this. Buck Calabro Commsoft, Albany, NY mailto:mcalabro@commsoft.net * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the RPG/400 Discussion Mailing List! To submit a new * * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * * from this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe RPG400-L' in the body of your message. Questions should * * be directed to the list owner / operator: david@midrange.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the RPG/400 Discussion Mailing List! To submit a new * * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * * from this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe RPG400-L' in the body of your message. Questions should * * be directed to the list owner / operator: david@midrange.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the RPG/400 Discussion Mailing List! To submit a new * * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * * from this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe RPG400-L' in the body of your message. Questions should * * be directed to the list owner / operator: david@midrange.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the RPG/400 Discussion Mailing List! To submit a new * * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * * from this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe RPG400-L' in the body of your message. Questions should * * be directed to the list owner / operator: david@midrange.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the RPG/400 Discussion Mailing List! To submit a new * * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * * from this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe RPG400-L' in the body of your message. 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.
midrange.com
