Re: UNIXCMD & unexplained stdout messages

I don't know "printf debugging", but I assume it means ad nauseum log
statements. I log the inputs into UNIXCMD and the outputs. I need help
logging what happens inside UNIXCMD. My RPGUnit tests use the same inputs
that cause errors in production, but it runs fine in the test.

date: Thu, 11 Mar 2021 11:40:21 -0700

from: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
subject: Re: UNIXCMD & unexplained stdout messages

On Thu, Mar 11, 2021 at 11:24 AM Justin Taylor <jtaylor.0ab@xxxxxxxxx>
wrote:

It's intermittent, and I've never been able to replicate (even with
identical inputs).

I'm sure you're right about that. Nonetheless, what I wrote

*Error found searching for command FontBold* strongly suggests some text

is

being interpreted as a command.

is still true. Some output of something, for whatever reason, is getting
into the character stream of your command and the command interpreter is
searching for FontBold as if it were a command.

The way I'd determine what's happening is what we call "printf debugging":
making sure all the inputs and outputs get written to some file you create
in the IFS.

I can see what PASE and/or whatever shell is trying to execute your
commands is telling you quite clearly.

How crunchy ol' RPG interacts with PASE and the various shells is still
somewhat mysterious to me.

If possible, life is always simpler if you can convert an IFS/PASE workflow
to a Python script and call the script with params generated by your RPG
than trying to orchestrate everything directly from within RPG code.

--
Jack Woehr, IBM Champion 2021
<
https://www.youracclaim.com/badges/528d23d6-087f-4698-8d17-d59688106ac4/public_url

Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021