|
The preferred method would be to call the QWCRTVCA API which is detailed in the work management apis book. Of course if you are looking for a way to handle calling Any command via QcmdExec with parameters flying around as reference I think you would not be pleased as QcmdExec requires a string (that is key here) therefore you can not pass pointers to your variables. Otherwise the only way I know of of doing what you want is pretty bad. One clearly painful way of doing that would be to find the command processing program for the command, then figure out what the real order and type of the parameters (quite painful indeed). I had to do this on a number of occassions (one being getting the users password and slamming password changes to a second machine so that our Mimix environment would keep in sync back in the V2R3 days). It would be nice if RPG/V had an interface to the command prompter/interface internally :-) Hint Hint nudge nudge Thanks Eric ______________________________________________ Eric N. Wilson President Doulos Software & Computer Services 2913 N Alder St Tacoma WA 98407 ----- Original Message ----- From: Rob Berendt <rob@dekko.com> To: <RPG400-L@midrange.com> Sent: Monday, August 09, 1999 11:22 AM Subject: RE: imbedded CL in RPG > No, you have to roll your own. > > And they never did get back to me as to whether or not the following will > be supported, or is doable: > > C Eval JobUser = *blanks > C CALLP Runcmd(RTVJOBA USER(&JobUser) ) > C DSPLY JobUser > > > > > > dbale@genfast.com on 08/09/99 12:57:06 PM > Please respond to RPG400-L@midrange.com@Internet > To: RPG400-L@midrange.com@Internet > cc: > Fax to: > Subject: RE: imbedded CL in RPG > > > > Hans, Bob, et al: > > >>C CALLP Runcmd('OVRPRTF QPRINT OUTQ(' + variablename + ')')<< > > Uh, is this Runcmd procedure available to us already, in the compiler? Or do we > have to build this ourselves? I scanned for Runcmd in the softcopy but came up > with zilch. We're at V4R2. > > - Dan Bale > > > > > > +--- > | 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 > +---END > > > > +--- > | 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 > +---END > +--- | 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 +---END
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.