Having WLM manage the initiators will prevent new jobs from entering the system when the system is at 100%. This is good from a performance viewpoint. Users tend not to understand that and want to know why their job isn't running. Also if you are currently using Jes2 Priority, be prepared for that mechanism to no longer work. Jobs will enter the system based on their defined importance according to WLM. Thank You, Dave O'Brien NIH Contractor ________________________________________ From: Wim [wim.hond...@atosorigin.com] Sent: Monday, February 22, 2010 8:52 AM To: IBM-MAIN@bama.ua.edu Subject: WLM managed Initiators
I am reading about the WLM Managed Initiator possibility. As fas as I understand, the option is designed to use it in a Sysplex environment with mutiple systems. Are there any advantages and/or disadvantages when activating it in a Monoplex environment (so only on a single system) or is it of no use in this situation? Thanks in advance. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
