WLM- Initiators: Someone here had changed the 'sysprog class' (the only one open right after IPL) to WLM-managed (and didn't care about the serviceclass).
IPL'd of one system in order to upgrade a database to a new release. Used the class for sysprogs (which traditionally under JES2 would lead to the job being converted and executed on the system it was submitted). Fell flat on my face with an abend806 for the product to be upgraded. Panic. Why the hell is the new product not working? The 'missing' module is in linklist! It took me quite a while to figure out that the job had been routed by WLM (despite an open initiator on a system without *any batch*) to a system it shoudn't/cannot run on! Not having the command ready to make it JES- managed again and not using the sysaff statement correctly, it took me a good 45 minutes to get that job to run on the system it was supposed to run! (To explain further, we do NOT use SYSAFF. Our system-affinity is set by specifying an init that only exists on *that* system!) So don't tell me how great WLM-managed inits are! They're not. We're 1.8. Regards, Barbara Nitz ---------------------------------------------------------------------- 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
