Re: SQL0314 on V5R4 - Was (Encapsulation - Service Programs, Procedures, SQL, LDA, etc.) -- RPG400-L

Subject: Re: SQL0314 on V5R4 - Was (Encapsulation - Service Programs, Procedures, SQL, LDA, etc.)
From: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
Date: Sun, 17 Feb 2008 13:16:05 -0600
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

Joe D wrote:

I should have specified, the error is being thrown for DirEDs.DirE and DirEDs.DirGrp, which are used in the SQL in both procedures....

Which I think is because the same variable name is being defined in two procedures. While it works for RPG, I don't think SQL likes it. Have you tried just using simple variable names? Just define LOCAL_DIRE and LOCAL_DIRGRP (with the appropriate hardcoded attributes) in both procedures and use those in your SQL statements, and see if the preprocessor gives you the same message. I'm wondering if SQL recognizes variable scope even for non-DS variables.

Joe

Follow-Ups:

Re: SQL0314 on V5R4 - Was (Encapsulation - Service Programs, Procedures, SQL, LDA, etc.) , Joe D

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