RE: embedded sql, procedure, and report output -- RPG400-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: RE: embedded sql, procedure, and report output
From: rob@xxxxxxxxx
Date: Wed, 26 Oct 2005 10:46:12 -0500
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>

He did kind of mix up the terminology by calling them subroutines and then 
throwing in "begin procedure statement".  But I do believe that he is 
using subprocedures.

When it comes to precompiler it is very important to report the current 
version of OS/400 you are running.  Prior to V5R3 the precompiler was a 
rather detestable piece of excrement.  Starting with V5R3 they are fixing 
many of it's issues.  We need to know which version you are running.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: embedded sql, procedure, and report output , Duane Kehoe

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.