Re: Command Processing

[Martin Rowe <martin@xxxxxxxxxx>]

On Friday 13 July 2001 20:53, thomas@inorbit.com wrote:
<snipped>
> With nothing else to go on, I'd suspect you would have trouble with
> SBMJOB's CMD() parameter. You might want to try the RQSDTA() parameter
> instead, which is where the real action takes place anyway.
>
> Have your function determine the initial command string and then prompt
> it with QCMDCHK or QCAPCMD, then place the returned command string into
> RQSDTA(&CmdStr). Ignore the CMD() parameter completely.
>
> Tom Liotta

Tom

This has me confused (not difficult). I have always assumed that the 
CMD() parm was added as in improvement to RQSDTA(). I can't think of 
anmywhere at our site, other than legacy S/38 apps, that still use 
RQSDTA. I thought I've read there's a more restrictive command length 
limit on it too, plus all the escaping of quotes required and no 
prompting available. What *is* the difference then, and what makes RQSDTA 
more powerful/preferable? Pointers to the appropriate docs if you haven't 
the time/inclination to go into detail on this would be appreciated.

Regards, Martin
-- 
martin@dbg400.net / jamaro@firstlinux.net
http://www.dbg400.net  DBG/400 - DataBase Generation utilities 
Open Source test environment tools for the AS/400 / iSeries and 
miscellaneous database & spooled file management commands.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---