David, You may want to also consider using Tomcat on z/OS, which can not only host static pages but also run great content management applications like JspWiki. Rob Schramm (a list member) pioneered using JspWiki on z/OS for internal documentation. JspWiki is fantastic in that it allows you to collaboratively create content while maintaining revision history. It also supports file upload and attachments as well as cool plugins, like a PDF plugin that dynamically generates a PDF from your wiki pages.
Here's a link to a page with links on installing JspWiki on z/OS... all you need to do is drop the war into Tomcat and customize a single properties file: http://www.jspwiki.org/wiki/ZOSInstall Installing the free open source Apache Tomcat servlet container on z/OS is now a piece of cake using our "T:Z QuickStart for Tomcat" prebuilt z/OS distribution, also free. This package streamlines installation of Tomcat along with DB2 JDBC connections and SAF (RACF) authentication. If you use SAF authentication, you can use SAF resources to control groups and access levels to your JspWiki pages, since our Tomcat distro maps them into J2EE roles. see: http://www.dovetail.com/products/tomcat.html for more information on T:Z Kirk Wolf Dovetailed Technologies http://dovetail.com On Wed, Jun 10, 2009 at 6:44 AM, David Johnston < [email protected]> wrote: > Hello, > We are undertaking moving our internal web-facing documentation from an > NFS mapped unix server to uss on z/OS. We are having issues with codepages > 037 and 1047. Our initial problem is the primary entry point for these > pages is > through CICS, which is CP037. The pages all display correctly, however, a > piece of javascript in a page does not function. We beileve this is > isolated to > the cp037-cp1047 issue that many have discussed concerning the square > brackets ([ ]). In an effort to confirm this, I created another page and > loaded > it directly from an SMB shared directory. The javascript still produces an > error: invalid character. I understand that there is a difference between > the > location of these characters in the codepage, but even allowing for this, > we > are unable to process the javascript from uss. I can only use this if I > run it > from the original NFS location, or imbed it locally in each page. Neither > of > these is an option; we are moving everything off the NFS server, and do not > want to key the same code in multiple pages. Is there an issue accessing > javascript through a browser from uss? > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
