We resolved the issue last week but to further explain....
A "standard" library list would not work. Using CL to issue overrides
would not work - not allowed. Client only uses CL in our "true" batch
processes. The file I'm converting from and the file I'm converting to
are the same file except versioned. We've added a few new fields and
reformatted another for our next release. I couldn't simply cpyf w/ map
drop because we need some "special" formatting for one of the fields
that changed from 2.0 signed to 5 alpha.
Thanks,
S. Ellsberry
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[
mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, April 23, 2007 11:37 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: Dynamic SQL using Parameter Markers
How do you handle it with F spec files? Most people set up a library
list
before calling the program. We too, process multiple companies. People
working for one company don't often cross the line. So a typical
(simplified for this example) library list may look like.
CMP01DATA
CMP01PGM
CORPWIDEPG
VENDORPGM
QGPL
QTEMP
Company 02 may look like:
CMP02DATA
CMP02PGM
CORPWIDEPG
VENDORPGM
QGPL
QTEMP
And if your custom SQL program is in CORPWIDEPG then you should have no
issue. Do not use a parameter marker for the file name. Just assume
the
library list is right. After all, that is what you would do for your F
spec files, eh?
Would this work for you?
Rob Berendt
midrange.com
