Mixed application server environment with z/OS
I'm looking for more information from SAP when running a system in a mixed application server platform environment. In other words, the system would look like the following:
1. Central instance (only MS and EN processes - i.e. standalone enqueue) running on AIX
2. Dialog instance (disp+work processes - i.e. spool, batch, dialog, upd) running on Windows 2003 or Linux
3. Database running on z/OS
I see from the Product Available Matrix, that Windows and/or Linux are supported with z/OS, but there is no mention of running a mixed environment as described above.
Any help/guidance would be appreciated.
Brian Walker replied
Yes, we have already been down the road of zLinux. Thanks to some pricing issues on the DB2 z/OS side, we had to give up our IFLs and thus zLinux. Our application servers are now on Windows 2003 x64. Even when we were on zLinux, we were forced to run some Windows application servers for Adobe Document Services as this is not supported on zLinux and SAP/Adobe have thus far refused to port it.
The inconsistency is that while SAP says it is "ok" to use something like SAMBA to share out SAPMNT and have it work under windows, it introduces unneeded complexity in many areas. SAP note 680617 describes this process. For us, it was a neverending headache with the unix vs windows text file format differences (supposedly handled by instance parameter abap/NTfmode=b) and there are complications for path names for batch jobs, etc.
I am sure all of those issues can be sorted out eventually, but it is just much easier to stick with one application server platform.
If you're considering zLinux, I would be extremely careful. There are only a handful of SAP customers in the world running it. Most likely you'll run into problems that no other customer has encountered yet and which will require a PTF or a new SAP kernel to fix (when you can finally get them). We ran into one such problem communicating to the ASCS/SCS in USS from zLinux over hipersockets. This really plagued our project team with hung locks (especially during LSMW imports of master data) until SAP released kernel 150 for zLinux which coded around the "unexpected" extreme low latency of hipersockets.