Hi, We have multiple TWS environments consisting of controllers and trackers running on one LPAR and associated trackers on other LPARs. Users routinely access the controllers through the ISPF interface on LPAR's other than the one running the controller and in some cases are restricted from logging on to the LPAR running the controller. Our strategy is to have the TWS software on our sysres set and roll it out with our maintenance IPL's which results in the controller running on a downlevel LPAR until the maintenance cycle completes. Occasionally, we run into compatability problems between the maintenance level running the controller and the uplevel LPAR running the tracker or ISPF interface. We have considered taking the TWS software off sysres and creating 'controller' associated environments but believe there are then potential difficulties with the linklist, the subsystem and the JES interface. This would also lead to a complicated and error prone maintenance environment. Has anyone else had similar experiences and / or advice ?
Regards, Mike ---------------------------------------------------------------------- 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
