Re: Python CL Command Wrappers

Hi Richard,

Thanks so much for posting and making your Python CL Wrapper available.
I have a couple of small questions if you have a moment some time.

What would be your CCSID recommendation for someone living in the UK?
Would it make sense to scan your PYONI/SOURCE file and change and CCSID 37s
to 285?
( I wouldn't just do a blanket scan and replace... I can see there are few
references to "37" which are just text or nothing to do with CCSIDs)

Also, I'm running Python 3.6.8 in a virtual environment at the moment. I
used --system-site-packages to point to the yum install to gain access to
things like iToolkit which aren't easily installed into a venv (for me at
least...)
Is there a recommended way to use your wrapper with virtual environments?

thanks kindly,
Craig

On Mon, 22 Apr 2019 at 01:01, Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

I think it's fine and will serve as a pattern for some invocations. Sparser
code is possible when the requirements are seen differently.

I was observing that the design patterns, the one your code demonstrates or
another one, comprise the important lesson.

On Sun, Apr 21, 2019 at 5:34 PM Richard Schoen <richard@xxxxxxxxxxxxxxxxx>
wrote:

Haven't you ever defined a command ? Those parm definitions look pretty
straightforward to me.

Apparently in your rush to poke holes you didn't read my post closely

that

mentioned I will probably tweak the parms to be closer in line with the
MONO command which has a single args value that takes in 1-40 parms.

This code iteration was done a couple years back and since John Y asked
for the code I packaged it up.

The important thing for me is that it works and works right every time.

If

nobody else uses it they can at least study and learn from it and do

their

own thing with it.

Back to my Easter food coma.

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

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

message: 4
date: Sun, 21 Apr 2019 00:52:38 -0600
from: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
subject: Re: Python CL Command Wrappers

On Sat, Apr 20, 2019 at 11:12 PM Richard Schoen <

richard@xxxxxxxxxxxxxxxxx

wrote:

Really, it's complicated ?

Ummm ...

**snip**
PARM KWD(PARM14) TYPE(*CHAR) LEN(400) +
CASE(*MIXED) PROMPT('Parameter 14')
PARM KWD(PARM15) TYPE(*CHAR) LEN(400) +
CASE(*MIXED) PROMPT('Parameter 15')
PARM KWD(PARM16) TYPE(*CHAR) LEN(400) +
CASE(*MIXED) PROMPT('Parameter 16')
PARM KWD(PARM17) TYPE(*CHAR) LEN(400) +
CASE(*MIXED) PROMPT('Parameter 17')
PARM KWD(PARM18) TYPE(*CHAR) LEN(400) +
CASE(*MIXED) PROMPT('Parameter 18')
PARM KWD(PARM19) TYPE(*CHAR) LEN(400) +
CASE(*MIXED) PROMPT('Parameter 19')
PARM KWD(PARM20) TYPE(*CHAR) LEN(400) +
CASE(*MIXED) PROMPT('Parameter 20')
**snip**

... no, not at all ... did I say something? :)

The important thing is, "Is it eagerly seized upon by some set of users

as

a solution?"

Most likely you have made some folks happy with your fine work.

Sorry to miss you at COMMON. I'll keep Calvin busy :)

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

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

NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com