In converting from cgi/isapi to servlet, we've tripped over lots of words we just can't use. So i'll start a thread :
1. "SKIPIMAGE"... don't use this seemingly innocuous word as a statement label. Java will throw you slam into the middle of next week! who knew?
2. amperCOPY .. don't start any amper variable name with amperCOPY , such as
-SET amperCOPYTO = 'D:\IBI\....' ; and
-SET amperCOPYFROM = 'D:\...'; and then
CMD COPY amperCOPYFROM amperCOPYTO
It might work, but your echo will be a mess and you won't know.
(note: ampersands are printing in this board as copyright symbols..and i haven't figured out how to use ubbcode to fix that, so i've written it out as amper.)

I'm VERY interested in this subject! We are on WebFocus 5.2 and looking at cgi-bin vs. wfservlet. I was told by IBI Tech Support that the Projects Area of Developer Studio is not supported using wfservlet. Here are a couple of things that don't work from the Projects area;

CHECK FILE FILENAME give a foc1517 in CHECK FILE FILENAME

Editing the .ACX file in the projects area does not work (most of the time).

Folks doing Self-Service apps want to use wfservlet as there is a problem with prompting on the server.

Can anyone tell me why we need to change from cgi-bin to wfservlet or what the differences are?

Thanks!
Carol Dobson cdobson@dlbabson.com

3. &DATETYPE is another java "badword".

From what i've read, cgi's time has come and gone, in webworld in general. its slow and limited, and over. e.g.It times out alot. Try isapi (wepapi.dll) as an alternative. Its faster than cgi, installed along w/ your 5x, but not as cool as servlet. i'm not sure what you mean by an error in prompting or an error in your check file. I have found that when i migrate a fex from cgi to servlet, i test it, and if there's a java badword in there anywhere, it bombs like crazy (fun!) and often have to go line by line, and i mean actually REMOVING code and going 1 paragraph at a time, to find the offending word. So maybe in your MFD where you're doing your CHECK FILE, you have a java "badword";
I have found that the timeout with servlet is about an hour. Now i'm not sure if that's a meaningful comparison, but cgi timeouts were common, and now no prob!, at least for my site. I'm happy with servlet and would never go back.

actually any var starting with &DATE is a no-no