Re: Shelling out CRTLF via QCMDEXC -- question about success/failure
Jason Olson <[email protected]> Mon, 8 Jun 2026 16:48:05 -0500
| Newsgroups | gmane.comp.hardware.ibm.midrange |
|---|---|
| Message-ID | <CALYHtpuiz0m_Dar2KpESmaGGw04D5pU+e=OqMXATL+9caXSVag@mail.gmail.com> |
https://www.rpgpgm.com/2013/12/qcapcmd-another-alternative-to-qcmdexc.html One nice thing about QCAPCMD too is that you can use that API to test the command you are going to run before you run it. That why if you are building your command string on the fly, you can see if it at least built correctly before trying to run it. Also the error messages that come back have not only the error id, but you get the replacement text too. That way if you are going to use something like send program message the message is complete with replacement values. Good for subfile messages and the like. Thanks, Jason E. Olson IBM i Engineer/Developer [email protected] 480.223.2952 On Mon, Jun 8, 2026 at 4:31 PM James H. H. Lampert via MIDRANGE-L < [email protected]> wrote: > I've got a project in which I will be using a QCMDEXC call to shell out > a CRTLF (from a generated source member). What is the easiest way for > the calling program to determine whether the CRTLF was successful? > > -- > JHHL > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: [email protected] > To subscribe, unsubscribe, or change list options, > visit: https://lists.midrange.com/mailman/listinfo/midrange-l > or email: [email protected] > Before posting, please take a moment to review the archives > at https://archive.midrange.com/midrange-l. > > Please contact [email protected] for any subscription related > questions. > > -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: [email protected] To subscribe, unsubscribe, or change list options, visit: https://lists.midrange.com/mailman/listinfo/midrange-l or email: [email protected] Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l. Please contact [email protected] for any subscription related questions.