RE: Python CL Command Wrappers

So I tested this and it appears that python and pthon2 call the same thing - Python2. And python3 calls Python3.

Does that really need to change ?

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

-----Original Message-----
From: Richard Schoen
Sent: Thursday, April 25, 2019 2:06 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: Python CL Command Wrappers

Hey Bryan,

You might want to grab the latest from a couple days ago.

After jack complained I refactored the main PYRUN command to have a single ARGS parm with up to 40 parms.

I left the original PYRUN command there as PYRUN2.

Although I hadn't done the Python2 bit. I'll make that tweak in the next build.

So basically don't ever use python by itself now. Use either use python2 or python3 ? right ?

I was only ever testing V3 😊

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

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

message: 2
date: Thu, 25 Apr 2019 13:18:25 -0400
from: Bryan Dietz <bdietz400@xxxxxxxxx>
subject: 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