Re: Possible SQL Activation Group Issues -- MIDRANGE-L

Subject: Re: Possible SQL Activation Group Issues
From: dlclark@xxxxxxxxxxxxxxxx
Date: Fri, 14 Oct 2016 14:57:59 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

David L Clark/it/crp/WinWholesale wrote on 10/14/2016 02:23:37 PM:

My batch application is using an MVC architecture.

CLLE --> non-SQL RPGLE "Controller" (with PRTF "View") --> SQLRPG
"Service Layer" --> SQLRPG DAO "Model"

Thus, we can't use *ENDMOD because we would lose the cursor which
only exists in the Service Layer.

OK, I recompiled my controller program to use *NEW for the
activation group. All of our RPG programs, modules, and service programs
are normally compiled to use *CALLER for the activation group. So, my
service layer and model still use *CALLER for the activation group. All
of our CLLE programs are compiled using our chosen named activation group.
I made no other code changes and am running the process again. We'll see
what happens.

Sincerely,

Dave Clark

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Possible SQL Activation Group Issues , dlclark

This mailing list archive is Copyright 1997-2025 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.