Re: Python CL Command Wrappers

I added the following to the command definition

for each of the parm01 - parm20

PMTCTL(*PMTRQS) and INLPMTLEN(17)

Press F-10 to see the PARM01-PARM20 and make the visible parameter line shorter. (lengthen with "& " <enter> in the first character to make it "longer".

Cosmetic changes only

in the CPP for the command changed "/python" to /python2"
yum installed version 2 of python as python2

/* Set python executable */
IF COND(&PYVERSION *NE '3') THEN(CHGVAR +
VAR(&PYEXE) VALUE(&PYPATH |< '/python2'))


Bryan



Richard Schoen wrote on 4/25/2019 12:49 PM:

Of course not. The more input the better we can make these things 😊

I'll work up some parm return examples soon as well to illustrate that. I'll lift a couple of examples from the Java command wrapper I did a few years back.

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
Phn: (612) 315-1745


------------------------------

message: 6
date: Thu, 25 Apr 2019 10:37:10 -0600
from: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
subject: Re: Python CL Command Wrappers

On Thu, Apr 25, 2019 at 10:00 AM Richard Schoen <richard@xxxxxxxxxxxxxxxxx>
wrote:

The PYRUNC CL is really essentially just composing the python command
line to run, executing it and returning data via STDOUT. Along with
some extra validation.

Richard, do you mind if I add a slide about your PYONi stuff to my PowerUp
2019 presentation?