|
Joe said: >There's nothing in any of the literature to tell someone >about editing in situ, creating separate instances, exporting >to the IFS and using CL to copy or anything like that. Same for green screen applications. >According to the manual, it's update in WDSC and >deploy. It requires a pretty sound understanding >of the architecture to do the things you're doing, Buck. I wouldn't say that I have a better than average understanding, but I also don't think it's as difficult as it appears at first blush. There simply is no documentation that describes the WAS architecture in total, any more than there is documentation that describes the green screen architecture in total. Remember, we're not talking about a single element, but all elements together. In green screen that means (at least) source members, compilers, DSPF, PF, LF, PGM, library, security and job description. In the web world that means HTML, JSP, class and maybe bean, JAR, WAR/EAR as well as minimal understanding of HTTP server and servlet engine configuration. I don't think it's much more complex than understanding the relationships between subfiles (control, record) and the RPG needed to use them. It's just new to us, so it seems hard. --buck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.