|
I also would strong suggest using CGIDEV or our eRPG SDK (www.erpgsdk.com).
But, it wouldn't hurt to look into the APIs just to get a general sense of
what they do. I think you'll find that the RPG/CGI part is the easy part,
and incorporating HTML/JS/CSS is where the learning curve will be. At
least I've found that to be the case with most IBM i programmers.
I also have a few books out on the subject that would be worth picking up.
I know the eRPG series can be purchased quite inexpensively now. :) Then
there are a couple training manuals that would be good as well. Feel free
to contact me off line for some assistance picking some out.
Brad
www.bvstools.com
On Sun, Mar 30, 2014 at 5:32 PM, Charles Wilt <charles.wilt@xxxxxxxxx>wrote:
Booth,
You want the HTTP API's
http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/rzaie/rzaierefapi.htm
But I'll second the recommendations to use the CGIDEV2 wrapper instead of
using them directly.
The CGIDEV2 wrapper was originally an IBM project...so maybe you can
consider it 2 1/2 party software :)
If nothing else, you could dig into the guts of CGIDEV to see how the HTTP
APIs are used.
Charles
On Sat, Mar 29, 2014 at 9:33 PM, Booth Martin <booth@xxxxxxxxxxxx> wrote:
This is a learning process for me. I can write a simple report to thelist
Intranet with an RPG program and it works well. (Thank you Scott
Klement for your directions on doing this.) I like that solution to
provide useful data to bosses and sales staff with no real learning
curve for them.
What I would like to do is to allow records to be added directly to the
data file. Once I have learned to do that, step 2 would be to allow
editing of those records.
I want to stay away from 3rd party software. That may be the wrong
answer from a production point of view, but I want to learn the process.
Any examples or tips would be appreciated.
(What I have done so far is visible at
http://martinvt.com/Ice_Cream_Project/ice_cream_project.html )
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.