S/36 procedures and commitment control -- MIDRANGE-L

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

Subject: S/36 procedures and commitment control
From: John Yeung <gallium.arsenide@xxxxxxxxx>
Date: Fri, 15 Dec 2023 14:14:49 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Let's say we have an OCL procedure that, among other things, calls an
SQLRPGLE program.

Are there any differences between the following:

1. Log in as a user configured to always be in the S/36 environment,
and run the procedure.

2. Log in as a native user, issue STRS36, and then run the procedure.

3. Log in as a native user, and run the procedure using STRS36PRC.

In particular, would any or all of these result in the SQLRPGLE
program being run as though compiled with COMMIT(*NONE)?

John Y.

As an Amazon Associate we earn from qualifying purchases.

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.