IWS using Service Program - Conflicting Structs in PCML -- WEB400

Subject: IWS using Service Program - Conflicting Structs in PCML
From: Mitch Gallman <mgallman@xxxxxxxxxxxx>
Date: Thu, 18 May 2017 16:11:40 +0000
List-archive: <http://archive.midrange.com/web400/>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: "Web Enabling the IBM i \(AS/400 and iSeries\)" <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

Created an RFE (though it may need to be a PMR).

I have a service program that has two procedures.

Each procedure has a qualified data structure being used as a parameter. I named this qualified data structure the same in each procedure (T_REQUEST). When PCML is generated it has the two structs for T_REQUEST that are different. IWS ends up using the last struct found in the PCML for both procedures.

My work around is to never use the same data structure name twice in the service program if it's used as a template for a parameter.

http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=105337

Mitch Gallman | U.S. Xpress, Inc.
IBM i Applications Developer

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: IWS using Service Program - Conflicting Structs in PCML , Jon Paris

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.