Re: [IBMiOSS] Checking return status of Pyhon program -- OPENSOURCE

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

I'd probably use the logging module to log everything that happens in the
Python program. Doesn't give your calling CL any good info, but it will
let you analyze after the fact to see if it was successful or not...

On Thu, Sep 29, 2016 at 10:47 AM, Roger Harman <roger.harman@xxxxxxxxxxx>
wrote:

I have a CL driver that calls a Python program to retrieve data via a
webservice.

CALL PGM(QP2SHELL) PARM('/QOpenSys/usr/bin/python3'
'/NYSLA/YMAR701.py')

I'm not seeing an obvious way to validate if the Python program ran
successfully. It has try/on exception blocks so it won't blow up.

For example, I made a slight change and had an indentation error. Obvious
Python failure but how can I inform the CL?

Doing a RCVMSG *LAST, I don't see any message "call QP2SHELL ......" like
I see with "call QSH ......".

I see some documentation that IBM recommends calling QSH and invoking PASE
thru that.

Suggestions? Does anyone have an example of using the QSH method and
error checking that they could share?

Thanks.

Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power

--
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.

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.