Timothy asked: >I need to port our latest piece of software to the mainframe. >The software >runs as a server using TCP/IP on Linux/Unix/Windows already. Therefore, >porting to USS should be fairly painless. What pros and cons would there >be porting this server to native z/OS? When porting your application to z/OS and large mainframes, there are a few areas to watch out for: For socket based servers, how many concurrent users do you expect to support. When LOTUS NOTES was ported to z/OS, they used 1 thread per client and about 100 threads per process. This got kind of nasty as they started supporting 20,000+ clients. They eventually converted to use asynch I/O which avoids many of the pitfalls like too many threads and huge bit masks for select(). You can support a very large number of clients in a single process with 50 worker threads using asynch I/O.
Another area to watch out for is security (as mentioned in another response). If you process all transactions under the indentity of the server, then the port should be fairly straight forward. If you want to process the transaction under the requestor's identity, then there are various design choices. USS supports a task level identity, which is not available on other *NIX platforms. If you go this route, there are various rules and security profiles that are required such that you maintain the integrity of the application. I worked in USS for the first 10 years it was developed (aka kernel Don). Over the years I've discussed server design with internal products as well as ISV and customer products. If you want to discuss your server application and how it will work on z/OS, feel free to give me a call. Don Ault, 845-435-1750 ---------------------------------------------------------------------- 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
