RE: Sub-procedures and internal print file

Rick,

As I recall, I've used program described printer output with procedure based
code.  The O specs and the procedures must live in the same source, with the
O specs positioned just before you begin defining your procedures.  The
fields referenced on the O specs must be global, and in your procedure you
must move any local data to the global variables before you EXCEPT your
output.  FWIW, you're in the same boat with externally defined printer
files, since they have the same "global/local" scoping issues as program
described printer output.

hth,

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: Rick.Chevalier@xxxxxxxxxxxxxxx
[mailto:Rick.Chevalier@xxxxxxxxxxxxxxx]
Sent: Thursday, June 24, 2004 10:49 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Sub-procedures and internal print file


--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.