|
The CGILIB *SRVPGM is built on top of the regular xTools RPGLIB *SRVPGM. So you only need CGILIB but you end up loading both for CGI programs because CGILIB requires RPGLIB. CGIDEV2 has stuff to set up your initial configuration, but as you see, there's a lot of extra clutter in there. xTools does not attempt to set up the configuration as the migration tool (from the classic server) and the set up Wizard are pretty handy for that. I have CGIDEV2 on my system and some older applications are still using it. It still works fine. Everything new (CGI RPG IV anyway) uses CGILIB for obvious reason. <g> -Bob -----Original Message----- From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Mike Skvarenina Sent: Tuesday, November 16, 2004 7:28 AM To: 'Web Enabling the AS400 / iSeries' Subject: RE: [WEB400] CGIDEV2 problems when updating to 9/2004 release And the reason why I ask all of this is because I'm considering a clean install of CGIDEV2 (and CGILIB when it arrives) so I can be sure I didn't incorrectly install the update to CGIDEV2 earlier this week causing the problem listed below. Another thing I'm really trying to do is clean-up my HTTP configs. There's a lot of CGIDEV2 directives in there that I'm not sure are necessary. I've cut a pasted some of it below but what I'd like to have is just the essentials and not a bunch of things there solely for the purpose of running the demo programs. MapMatch ^/cgidev2/start$ /QSYS.LIB/CGIDEV2.LIB/DEMOHTML.FILE/DEMOFRAME.MBR 75 MapMatch ^/cgidev2/setup$ /QSYS.LIB/CGIDEV2.LIB/DEMOHTML.FILE/SETUPCSA.MBR 76 MapMatch ^/cgidev2h/(.*)\.htm$ /cgidev2h/$1.mbr 77 MapMatch ^/cgidev2o/(.*)\.htm$ /cgidev2o/$1.mbr 78 MapMatch ^/cgidev2oit/(.*)\.htm$ /cgidev2oit/$1.mbr 79 MapMatch ^/cgidev2o/(.*) /QSYS.LIB/CGIDEV2.LIB/DEMOHTML.FILE/$1 80 MapMatch ^/cgidev2oit/(.*) /QSYS.LIB/CGIDEV2.LIB/DEMOHTMLIT.FILE/$1 81 MapMatch ^/cgidev2h/(.*) /QSYS.LIB/CGIDEV2.LIB/HTMLSRC.FILE/$1 82 MapMatch ^/cgidev2r/(.*) /QSYS.LIB/CGIDEV2.LIB/QRPGLESRC.FILE/$1 83 MapMatch ^/cgidev2l/(.*) /QSYS.LIB/CGIDEV2.LIB/QCLSRC.FILE/$1 84 MapMatch ^/cgidev2d/(.*) /QSYS.LIB/CGIDEV2.LIB/QDDSSRC.FILE/$1 85 MapMatch ^/cgidev2f/(.*) /cgidev/$1 -----Original Message----- From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Mike Skvarenina Sent: Tuesday, November 16, 2004 8:22 AM To: 'Web Enabling the AS400 / iSeries' Subject: RE: [WEB400] CGIDEV2 problems when updating to 9/2004 release I guess what I'm trying to understand is what makes up CGIDEV2 & CGILIB for that matter. I understand there's a service program that contains a bunch of sub-procedures such as "cgiWrtSection" but in the case of CGIDEV2, there's a library of 210 objects and XTools has 35 objects. Part of this is my ignorance of RPG IV programming and the use of service programs, binding directories, etc as I don't use them, but what would be great is a basic description on what's really required to develop RPG CGI apps. For example in the xTools case, are we saying that all that's really needed is the CGILIB service program with our programs making calls to the sub-procedures within it, or are other objects from the xTools library necessary to make it work? -----Original Message----- From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Mike Skvarenina Sent: Monday, November 15, 2004 10:25 PM To: 'Web Enabling the AS400 / iSeries' Subject: RE: [WEB400] CGIDEV2 problems when updating to 9/2004 release Hmmm, actually I don't think we did that. We started by downloading the current version and loading it to CGIDEV2 library. The we ran the 2 REXX procedures then did a SETCGILIB to the library we place our source and objects in. At that point I checked the service program and it was updated from the previous version. Next we recompiled both programs. We figured a fresh compile may be better than just rebinding Now we're back on the old service program, but we're not confident we're back to the way we were. -----Original Message----- From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Bob Cozzi Sent: Monday, November 15, 2004 3:05 PM To: 'Web Enabling the AS400 / iSeries' Subject: RE: [WEB400] CGIDEV2 problems when updating to 9/2004 release Did you rebind to the service program? UPDPGM mycgipgm BNDSRVPGM(CGISRVPGM2) Not sure if Giovanni uses binder language to keep the exports in order (he should) and if he does, then the UPDPGM might help -Bob -----Original Message----- From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Mike Skvarenina Sent: Monday, November 15, 2004 2:34 PM To: WEB400@xxxxxxxxxxxx Subject: [WEB400] CGIDEV2 problems when updating to 9/2004 release OK folks, I updated to the latest CGIDEV2 library. Following the instructions in the readme as best as possible. Now at times we're seeing something like this in the joblog for a CGI instance: Level check on file CGIDEBUG in library CGIBIN with member CGIDEBUG. The starting address for reallocation is not valid. RPG status 00426 caused procedure UPDHTMLVAR in program CGIBIN/CGISRVPGM2 to stop. RPG status 00202 caused procedure UPDHTMLVAR in program CGIBIN/CGISRVPGM2 to stop. The starting address for reallocation is not valid. RPG status 00426 caused procedure UPDHTMLVAR in program CGIBIN/CGISRVPGM2 to stop. RPG status 00202 caused procedure UPDHTMLVAR in program CGIBIN/CGISRVPGM2 to stop. Any ideas anyone? _______________________________________________ This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/web400 or email: WEB400-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/web400. _______________________________________________ This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/web400 or email: WEB400-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/web400. _______________________________________________ This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/web400 or email: WEB400-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/web400. _______________________________________________ This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/web400 or email: WEB400-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/web400. _______________________________________________ This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/web400 or email: WEB400-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/web400.
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.
midrange.com
