Re: [IBMiOSS] dbtoxlsx.py / PASE QShell -- OPENSOURCE

Subject: Re: [IBMiOSS] dbtoxlsx.py / PASE QShell
From: John Yeung <gallium.arsenide@xxxxxxxxx>
Date: Thu, 30 Aug 2018 10:06:33 -0400
List-archive: <https://archive.midrange.com/opensource/>
List-help: <mailto:opensource-request@midrange.com?subject=help>
List-id: IBMi Open Source Roundtable <opensource.midrange.com>
List-post: <mailto:opensource@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/opensource>, <mailto:opensource-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/opensource>, <mailto:opensource-request@midrange.com?subject=unsubscribe>

I am confident your suspicion about SQL server mode is correct. I've
come across it myself with iSeriesPython.

How I've come to cope with it is to always submit a new job to run
Python. I mean, from the 5250, interactive use is pretty crappy
anyway, so I've tailored both my Python scripts and my own workflow
habits to be centered around SBMJOB.

You may want to make a generic wrapper which you always use for all
your Python calls, and have that wrapper handle everything that's
needed, including submitting a new job. (For me, that also includes
setting ALWMLTTHD(*YES).)

John Y.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: [IBMiOSS] dbtoxlsx.py / PASE QShell , Craig Richards
Re: [IBMiOSS] dbtoxlsx.py / PASE QShell , Jesse Gorzinski

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.