|
The problem with the program I am working with is that it is used very strangely and must use their way of doing things without breaking it. I tried to use numeric but didn't work. I am converting it to numeric in the program that is processing it. That part works fine. Everything works fine now, of course I would have loved to do it a different way, but because of way the programs work, I most do it their way. As I said, after I submitted my question to the group, I figured it out (I was soooo tired, that is what I get for staying up 'til 12:30 on a work night). I figured that the EBCDIC hex code was X'7D'. Thanks for all the help from everyone! Mike -----Original Message----- From: Peter Dow [mailto:pcdow@yahoo.com] Sent: Tuesday, May 08, 2001 3:10 PM To: RPG400-L@midrange.com Subject: Re: Building a CL command in a RPG Program (Help!) Hi Mike, I hope you took all the suggestions from others into account -- I didn't catch the part about some parms being numeric (in which case they shouldn't have quotes) and I also noticed I've been dealing with ASCII too much lately -- x'34' is an ASCII double quote; x'7D' is the correct EBCDIC value for a single quote. Regards, Peter Dow Dow Software Services, Inc. 909 425-0194 voice 909 425-0196 fax ----- Original Message ----- From: "Wills, Mike N. (TC)" <MNWills@taylorcorp.com> To: <RPG400-L@midrange.com> Sent: Tuesday, May 08, 2001 6:22 AM Subject: RE: Building a CL command in a RPG Program (Help!) > All, > > After I wrote in I realized that this is how I should have built it. (Man I > was tired) That part now works good. The reason for using a CL is because I > am modifying a program and I don't want to change how it works (so I don't > break anything). If I was writing the program from scratch I would have done > it differently. > > Thanks for all the help! > > Mike > > -----Original Message----- > From: Peter Dow [mailto:pcdow@yahoo.com] > Sent: Monday, May 07, 2001 9:29 PM > To: RPG400-L@midrange.com > Subject: Re: Building a CL command in a RPG Program (Help!) > > > Hi Mike, > > It looks like you're using double quotes in your eval, so the resulting > command string would be > > SBMJOB CMD(CALL PGM(PGMNAME) PARM("PARM1" "PARM2" "PARM3" "PARM4")) > JOB(JOBNAME) > > which the command processor would not like. The quickest way to fix it would > be to use SEU to change all occurrences of " to ''. A better way might be > to define a constant called Quote: > > d Quote c x'34' or > d Quote c '''' > > then change your eval to > > EVAL CMD = 'SBMJOB CMD(CALL PGM(PGMNAME) PARM(' + > Quote + Parm1 + Quote + ' ' + > Quote + Parm2 + Quote + ' ' + > Quote + Parm3 + Quote + ' ' + > Quote + Parm4 + Quote + '))' + > ' JOB(JOBNAME)' > > hth, > Peter Dow > Dow Software Services, Inc. > 909 425-0194 voice > 909 425-0196 fax > > > ----- Original Message ----- > From: "Wills, Mike N. (TC)" <MNWills@taylorcorp.com> > To: <RPG400-L@midrange.com> > Sent: Monday, May 07, 2001 12:17 PM > Subject: Building a CL command in a RPG Program (Help!) > > > > I am trying to build a CL call command within a RPG program with four > > parameters. I cannot get the command to work. I am modifying a program and > > for some reason unable to debug it to verify the command is right. What is > > the proper syntax for putting quotes around parameters? > > > > This is the command I want to call: > > SBMJOB CMD(CALL PGM(PGMNAME) PARM('PARM1' 'PARM2' 'PARM3' 'PARM4')) > > JOB(JOBNAME) > > > > This is the code I have to build it: > > EVAL CMD = 'SBMJOB CMD(CALL PGM(PGMNAME) ' + > > 'PARM("' + Parm1 + '" ' + > > '"' + Parm2 + '" ' + > > '"' + Parm3 + '" ' + > > '"' + Parm4 + '"))' + > > ' JOB(JOBNAME)' > > > > The command is being passed to a CL where is then uses QCMDEXC to execute > > the command. My program gets a data decimal error because on some of the > > parameters, it picks up the double quotes as part of the parameter (ex. A > > date field would look like "0501200). > > > > Thanks for any help! > > > > Mike > > +--- > > | 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.