Re: [IBMiOSS] Early impressions of Litmis Spaces for Python

(I don't fully understand chroot, but from what I can gather, it would

seem Litmis Spaces uses it while pub400.com doesn't.)

I wrote about chroot in the following articles:
- bit.ly/ibmsystemsmag-chroot
- bit.ly/ism-chroot2

I'd love feedback on things that you feel I don't explain well. I believe
"containers" play an important role in the future of running PASE workloads
on IBM i, and right now chroot is the best one we have (that I am aware
of). Btw, chroot (aka ibmichroot) is delivered with 5733OPS opt 3. IBM
named opt 3 "GCC" which is somewhat a misnomer. In short, 5733OPS opt 3
gives you ease of chroot creation via shell scripts, and ease of installing
perzl.org rpms via shell scripts.

Aaron Bartell
litmis.com - Services for open source on IBM i


On Thu, Aug 11, 2016 at 11:41 AM, John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

OK, so it's established that using iDB2Call is a suitable workaround,
but for those people who are following particularly closely (yeah, I
know, it's easier to find unicorns and abominable snowmen), there's a
technical detail that I want to comment on. I had said:

On Tue, Aug 2, 2016 at 5:31 PM, John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

Incidentally, if there were no errors in the returned XML, then the
icmd_rtvjoba.py script would still have problems, because it then goes
on to try to print just the four pieces of information asked for
(USRLIBL, SYSLIBL, CCSID, and OUTQ) and because dictionary keys (and
everything else in Python) is case-sensitive, the lookups would fail.
(This part I know is a python-itoolkit problem, not unique to Litmis
Spaces, and not necessarily a problem with XMLSERVICE or other
implementations of itoolkit.)

I know now that these lookups are fine. They work using the preferred
iLibCall from pub400.com and using iDB2Call from Litmis Spaces. The
dictionary keys seem to have been automatically converted to all caps
during successful "transport". But when it errors out as I've
mentioned earlier, the keys are lowercase. So I don't know if the keys
are lowercase due to the chroot-related issues; and I don't know if
the appearance of lowercase keys is a cause or an effect of the error
I was seeing.

(I don't fully understand chroot, but from what I can gather, it would
seem Litmis Spaces uses it while pub400.com doesn't.)

In any event, it looks like I can move forward with experimentation on
both systems, which I will do as time permits.

John Y.
--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.