Re: HTML storage

[<matt.haas@xxxxxxxxxxx>]

Bob,

You absolutely want to use the IFS instead of PF's. For sequential
access, the IFS is several times faster than a PF. Also, files in the
IFS file will be easier to deal with since there isn't a line length
limit like a PF and you can use HTML editors to modify them.

For the service program question, I'm sure you can dig up plenty of
examples in the RPG-400 archives to support using new techniques.
Performance over dynamic calls and being able to enforce parameters via
prototypes are just two examples of the benefits of using service
programs.

Matt

-----Original Message-----
From: web400-bounces+matt.haas=cengage.com@xxxxxxxxxxxx
[mailto:web400-bounces+matt.haas=cengage.com@xxxxxxxxxxxx] On Behalf Of
Bob P. Roche
Sent: Wednesday, October 31, 2007 4:56 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] HTML storage

Thanks for the help, I can setup the dtaara easily to provide a source 
location for the test and production areas. I like the IFS idea also,
but 
I think for now I'll have to use a PF. We have a check out / 
implementation program, but it was built an is maintained in house so 
things get added as needed. It will be faster to get the PF version
added 
compared to the IFS change. I hope to get SRVPGM's in with this change.
So 
far I keep getting told why can't a normal program do that. I've yet to 
find a reason I need a SRVPGM. that can't be handled with a standard 
program. 




"Bradley V. Stone" <bvstone@xxxxxxxxxxxx> 
Sent by: web400-bounces@xxxxxxxxxxxx
10/31/2007 03:40 PM
Please respond to
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>


To
"Web Enabling the AS400 / iSeries" <web400@xxxxxxxxxxxx>
cc

Subject
Re: [WEB400] HTML storage






If you're talking about templates, I'd store them in the IFS instead of 
PFs.
But, with CGIDEV2 there isn't a way I know of to set a "default"
directory
for an environment.

So, what I would probably do is create your own.  Create a data area or 
file
that stores the main path to the templates.  then in each CGI program
retrieve it (great use for ILE here).  Take it onto the subprocedure to 
load
it and you're all set.

You'll want two environments anyhow, so test points to the test
directory,
then prod points to prod.  This means a file holding the default
location 
in
each CGIDEV2 library/development environment.

Please note our change of address!  Our new address is as follows:

201 Mapleridge Drive
Mankato, MN 56001

Bradley V. Stone
BVSTools - www.bvstools.com
eRPG SDK - www.erpgsdk.com