Re: Managing WLM manged initiators
Yes, SDSF is a utility, but it doesn’t do everything I am looking for. Gadi -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Mark Zelden Sent: Monday, July 11, 2011 5:16 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Managing WLM manged initiators On Mon, 11 Jul 2011 12:44:09 +0300, #1490;#1491;#1497; #1489;#1503; #1488;#1489;#1497; gad...@malam.com wrote: Hi, We’ve started using WLM managed initiators. Using JES2 commands we can specify the maximum number of initiators per class, and even per system. The number of jobs per system is visible and changeable using the JC command. Does anyone know of a utility that can display and change the values per system? I don't understand what you are looking for. $DJOBCLASS(*),LONG $DSRVCLASS(*),LONG $TJOBCLASS(n),XEQCOUT=n And all can be displayed and change with the SDSF JC command as you wrote. XEQMEMBER takes a JES2 command to change (unless that was added in z/OS 1.12) $TJOBCLASS(n),XEQMEMBER(abc)=(MAXIMUM=n) Isn't SDSF a utility? Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- 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 לשימת לבך, בהתאם לנהלי החברה וזכויות החתימה בה, כל הצעה, התחייבות או מצג מטעם החברה, מחייבים מסמך נפרד וחתום על ידי מורשי החתימה של החברה, הנושא את לוגו החברה או שמה המודפס ובצירוף חותמת החברה. בהעדר מסמך כאמור (לרבות מסמך סרוק) המצורף להודעת דואר אלקטרוני זאת, אין לראות באמור בהודעה אלא משום טיוטה לדיון, ואין להסתמך עליה לביצוע פעולה עסקית או משפטית כלשהי. Please note that in accordance with Malam's signatory rights, no offer, agreement, concession or representation is binding on the company, unless accompanied by a duly signed separate document (or a scanned version thereof), affixed with the company's seal. -- 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
Re: Managing WLM manged initiators
Yes, SDSF is a utility, but it doesn't do everything I am looking for. Gadi Hi, We've started using WLM managed initiators. Using JES2 commands we can specify the maximum number of initiators per class, and even per system. The number of jobs per system is visible and changeable using the JC command. Does anyone know of a utility that can display and change the values per system? I don't understand what you are looking for. $DJOBCLASS(*),LONG $DSRVCLASS(*),LONG $TJOBCLASS(n),XEQCOUT=n And all can be displayed and change with the SDSF JC command as you wrote. XEQMEMBER takes a JES2 command to change (unless that was added in z/OS 1.12) $TJOBCLASS(n),XEQMEMBER(abc)=(MAXIMUM=n) Isn't SDSF a utility? Mark Gadi, Can you tell us exactly what SDSF does not do? If you can give us more details perhaps we can help. If you want something in SYSVIEW then I would contact CA. I have always found them very helpful when I try to build functions. They may have something built, or they might help you build it. Lizette -- 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
Re: Managing WLM manged initiators
Hi, I have an issue open with CA. I would like to: 1. See the value of XEQCOUNT MAXIMUM 2. be able to change the value of XEQCOUNT MAXIMUM 3. be able to see the value XEQMEMBER(xx)=(MAXIMUM for each member is the sysplex 4. be able to change the value XEQMEMBER(xx)=(MAXIMUM for each member is the sysplex This first two are possible in SDSF. In SYSVIEW, only the first option is available. The filed cannot be updated. Options 3 and 4 are not possible in either SDSF or SYSVIEW. Gadi -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Lizette Koehler Sent: Tuesday, July 12, 2011 2:28 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Managing WLM manged initiators Yes, SDSF is a utility, but it doesn't do everything I am looking for. Gadi Hi, We've started using WLM managed initiators. Using JES2 commands we can specify the maximum number of initiators per class, and even per system. The number of jobs per system is visible and changeable using the JC command. Does anyone know of a utility that can display and change the values per system? I don't understand what you are looking for. $DJOBCLASS(*),LONG $DSRVCLASS(*),LONG $TJOBCLASS(n),XEQCOUT=n And all can be displayed and change with the SDSF JC command as you wrote. XEQMEMBER takes a JES2 command to change (unless that was added in z/OS 1.12) $TJOBCLASS(n),XEQMEMBER(abc)=(MAXIMUM=n) Isn't SDSF a utility? Mark Gadi, Can you tell us exactly what SDSF does not do? If you can give us more details perhaps we can help. If you want something in SYSVIEW then I would contact CA. I have always found them very helpful when I try to build functions. They may have something built, or they might help you build it. Lizette -- 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 לשימת לבך, בהתאם לנהלי החברה וזכויות החתימה בה, כל הצעה, התחייבות או מצג מטעם החברה, מחייבים מסמך נפרד וחתום על ידי מורשי החתימה של החברה, הנושא את לוגו החברה או שמה המודפס ובצירוף חותמת החברה. בהעדר מסמך כאמור (לרבות מסמך סרוק) המצורף להודעת דואר אלקטרוני זאת, אין לראות באמור בהודעה אלא משום טיוטה לדיון, ואין להסתמך עליה לביצוע פעולה עסקית או משפטית כלשהי. Please note that in accordance with Malam's signatory rights, no offer, agreement, concession or representation is binding on the company, unless accompanied by a duly signed separate document (or a scanned version thereof), affixed with the company's seal. -- 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
Re: Managing WLM manged initiators
Gadi, Then the question comes up: why do you want to change those values? You will be manually interfering in the WLM algorithmes to manage your batch and the systems in the sysplex in the most optimal way and according to your the Goals you set. What do you want to achieve with limiting WLM in this? Kees. ??? ?? ??? gad...@malam.com wrote in message news:c11ded818b17214792b97fba28712bed04fa69c...@jer-email1.jer.ad.malam .com... Hi, I have an issue open with CA. I would like to: 1. See the value of XEQCOUNT MAXIMUM 2. be able to change the value of XEQCOUNT MAXIMUM 3. be able to see the value XEQMEMBER(xx)=(MAXIMUM for each member is the sysplex 4. be able to change the value XEQMEMBER(xx)=(MAXIMUM for each member is the sysplex This first two are possible in SDSF. In SYSVIEW, only the first option is available. The filed cannot be updated. Options 3 and 4 are not possible in either SDSF or SYSVIEW. Gadi -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Lizette Koehler Sent: Tuesday, July 12, 2011 2:28 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Managing WLM manged initiators Yes, SDSF is a utility, but it doesn't do everything I am looking for. Gadi Hi, We've started using WLM managed initiators. Using JES2 commands we can specify the maximum number of initiators per class, and even per system. The number of jobs per system is visible and changeable using the JC command. Does anyone know of a utility that can display and change the values per system? I don't understand what you are looking for. $DJOBCLASS(*),LONG $DSRVCLASS(*),LONG $TJOBCLASS(n),XEQCOUT=n And all can be displayed and change with the SDSF JC command as you wrote. XEQMEMBER takes a JES2 command to change (unless that was added in z/OS 1.12) $TJOBCLASS(n),XEQMEMBER(abc)=(MAXIMUM=n) Isn't SDSF a utility? Mark Gadi, Can you tell us exactly what SDSF does not do? If you can give us more details perhaps we can help. If you want something in SYSVIEW then I would contact CA. I have always found them very helpful when I try to build functions. They may have something built, or they might help you build it. Lizette -- 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 ? ???, ? ? ? ??? ?? ??, ?? , ?? ??? ?, ??? ? ?? ??? ? ?? ?? ?, ? ?? ? ?? ??? ?? ??? ? ?. ? ? (? ) ?? ?? ???, ??? ? ? ?? ??? ? ?, ?? ?? ? ? ?? ?? ?. Please note that in accordance with Malam's signatory rights, no offer, agreement, concession or representation is binding on the company, unless accompanied by a duly signed separate document (or a scanned version thereof), affixed with the company's seal. -- 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 information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- 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
Re: Managing WLM manged initiators
Because sometimes the client says that they want to see n number of jobs in a certain class running. We know that it might not be the best thing, but the client is always right. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Vernooij, CP - SPLXM Sent: Tuesday, July 12, 2011 3:15 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Managing WLM manged initiators Gadi, Then the question comes up: why do you want to change those values? You will be manually interfering in the WLM algorithmes to manage your batch and the systems in the sysplex in the most optimal way and according to your the Goals you set. What do you want to achieve with limiting WLM in this? Kees. ??? ?? ??? gad...@malam.com wrote in message news:c11ded818b17214792b97fba28712bed04fa69c...@jer-email1.jer.ad.malam .com... Hi, I have an issue open with CA. I would like to: 1. See the value of XEQCOUNT MAXIMUM 2. be able to change the value of XEQCOUNT MAXIMUM 3. be able to see the value XEQMEMBER(xx)=(MAXIMUM for each member is the sysplex 4. be able to change the value XEQMEMBER(xx)=(MAXIMUM for each member is the sysplex This first two are possible in SDSF. In SYSVIEW, only the first option is available. The filed cannot be updated. Options 3 and 4 are not possible in either SDSF or SYSVIEW. Gadi -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Lizette Koehler Sent: Tuesday, July 12, 2011 2:28 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Managing WLM manged initiators Yes, SDSF is a utility, but it doesn't do everything I am looking for. Gadi Hi, We've started using WLM managed initiators. Using JES2 commands we can specify the maximum number of initiators per class, and even per system. The number of jobs per system is visible and changeable using the JC command. Does anyone know of a utility that can display and change the values per system? I don't understand what you are looking for. $DJOBCLASS(*),LONG $DSRVCLASS(*),LONG $TJOBCLASS(n),XEQCOUT=n And all can be displayed and change with the SDSF JC command as you wrote. XEQMEMBER takes a JES2 command to change (unless that was added in z/OS 1.12) $TJOBCLASS(n),XEQMEMBER(abc)=(MAXIMUM=n) Isn't SDSF a utility? Mark Gadi, Can you tell us exactly what SDSF does not do? If you can give us more details perhaps we can help. If you want something in SYSVIEW then I would contact CA. I have always found them very helpful when I try to build functions. They may have something built, or they might help you build it. Lizette -- 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 ? ???, ? ? ? ??? ?? ??, ?? , ?? ??? ?, ??? ? ?? ??? ? ?? ?? ?, ? ?? ? ?? ??? ?? ??? ? ?. ? ? (? ) ?? ?? ???, ??? ? ? ?? ??? ? ?, ?? ?? ? ? ?? ?? ?. Please note that in accordance with Malam's signatory rights, no offer, agreement, concession or representation is binding on the company, unless accompanied by a duly signed separate document (or a scanned version thereof), affixed with the company's seal. -- 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 information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286
Re: Managing WLM manged initiators
Because sometimes the client says that they want to see n number of jobs in a certain class running. We know that it might not be the best thing, but the client is always right. You need to convince them (if you can) that performance experts know better. Having more jobs in a class than the WLM has determined optimum: 1. Can lead to over-initiation. 2. Doesn't guarantee the class throughput will improve. 3. Can impact other classes, or workloads. As long as service levels are met, all else is secondary. PS: What happens if there aren't N jobs in the system? - Ted MacNEIL eamacn...@yahoo.ca Twitter: @TedMacNEIL -- 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
Re: Managing WLM manged initiators
Believe me, we've tried, but they 'know best' -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Ted MacNEIL Sent: Tuesday, July 12, 2011 4:16 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Managing WLM manged initiators Because sometimes the client says that they want to see n number of jobs in a certain class running. We know that it might not be the best thing, but the client is always right. You need to convince them (if you can) that performance experts know better. Having more jobs in a class than the WLM has determined optimum: 1. Can lead to over-initiation. 2. Doesn't guarantee the class throughput will improve. 3. Can impact other classes, or workloads. As long as service levels are met, all else is secondary. PS: What happens if there aren't N jobs in the system? - Ted MacNEIL eamacn...@yahoo.ca Twitter: @TedMacNEIL -- 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 לשימת לבך, בהתאם לנהלי החברה וזכויות החתימה בה, כל הצעה, התחייבות או מצג מטעם החברה, מחייבים מסמך נפרד וחתום על ידי מורשי החתימה של החברה, הנושא את לוגו החברה או שמה המודפס ובצירוף חותמת החברה. בהעדר מסמך כאמור (לרבות מסמך סרוק) המצורף להודעת דואר אלקטרוני זאת, אין לראות באמור בהודעה אלא משום טיוטה לדיון, ואין להסתמך עליה לביצוע פעולה עסקית או משפטית כלשהי. Please note that in accordance with Malam's signatory rights, no offer, agreement, concession or representation is binding on the company, unless accompanied by a duly signed separate document (or a scanned version thereof), affixed with the company's seal. -- 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
Re: Managing WLM manged initiators
What does your contract say? If there's nothing in it about N jobs, then tell them you are going to enforce it. If there is, or it's ambiguous, you're out of luck. - Ted MacNEIL eamacn...@yahoo.ca Twitter: @TedMacNEIL -Original Message- From: גדי בן אבי gad...@malam.com Sender: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Date: Tue, 12 Jul 2011 16:23:38 To: IBM-MAIN@bama.ua.edu Reply-To: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Subject: Re: Managing WLM manged initiators Believe me, we've tried, but they 'know best' -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Ted MacNEIL Sent: Tuesday, July 12, 2011 4:16 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Managing WLM manged initiators Because sometimes the client says that they want to see n number of jobs in a certain class running. We know that it might not be the best thing, but the client is always right. You need to convince them (if you can) that performance experts know better. Having more jobs in a class than the WLM has determined optimum: 1. Can lead to over-initiation. 2. Doesn't guarantee the class throughput will improve. 3. Can impact other classes, or workloads. As long as service levels are met, all else is secondary. PS: What happens if there aren't N jobs in the system? - Ted MacNEIL eamacn...@yahoo.ca Twitter: @TedMacNEIL -- 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 לשימת לבך, בהתאם לנהלי החברה וזכויות החתימה בה, כל הצעה, התחייבות או מצג מטעם החברה, מחייבים מסמך נפרד וחתום על ידי מורשי החתימה של החברה, הנושא את לוגו החברה או שמה המודפס ובצירוף חותמת החברה. בהעדר מסמך כאמור (לרבות מסמך סרוק) המצורף להודעת דואר אלקטרוני זאת, אין לראות באמור בהודעה אלא משום טיוטה לדיון, ואין להסתמך עליה לביצוע פעולה עסקית או משפטית כלשהי. Please note that in accordance with Malam's signatory rights, no offer, agreement, concession or representation is binding on the company, unless accompanied by a duly signed separate document (or a scanned version thereof), affixed with the company's seal. -- 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
Re: Managing WLM manged initiators
Then, the easiest way to guarantee N jobs running concurrently is going back to JES2 managed jobclasses and start N initiators. The N jobs will run, but not necessaraly perform. But if that's what they want... Kees. ??? ?? ??? gad...@malam.com wrote in message news:c11ded818b17214792b97fba28712bed04fa69c...@jer-email1.jer.ad.malam .com... Believe me, we've tried, but they 'know best' -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Ted MacNEIL Sent: Tuesday, July 12, 2011 4:16 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Managing WLM manged initiators Because sometimes the client says that they want to see n number of jobs in a certain class running. We know that it might not be the best thing, but the client is always right. You need to convince them (if you can) that performance experts know better. Having more jobs in a class than the WLM has determined optimum: 1. Can lead to over-initiation. 2. Doesn't guarantee the class throughput will improve. 3. Can impact other classes, or workloads. As long as service levels are met, all else is secondary. PS: What happens if there aren't N jobs in the system? - Ted MacNEIL eamacn...@yahoo.ca Twitter: @TedMacNEIL -- 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 ? ???, ? ? ? ??? ?? ??, ?? , ?? ??? ?, ??? ? ?? ??? ? ?? ?? ?, ? ?? ? ?? ??? ?? ??? ? ?. ? ? (? ) ?? ?? ???, ??? ? ? ?? ??? ? ?, ?? ?? ? ? ?? ?? ?. Please note that in accordance with Malam's signatory rights, no offer, agreement, concession or representation is binding on the company, unless accompanied by a duly signed separate document (or a scanned version thereof), affixed with the company's seal. -- 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 information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- 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
Managing WLM manged initiators
Hi, We’ve started using WLM managed initiators. Using JES2 commands we can specify the maximum number of initiators per class, and even per system. The number of jobs per system is visible and changeable using the JC command. Does anyone know of a utility that can display and change the values per system? Thanks Gadi לשימת לבך, בהתאם לנהלי החברה וזכויות החתימה בה, כל הצעה, התחייבות או מצג מטעם החברה, מחייבים מסמך נפרד וחתום על ידי מורשי החתימה של החברה, הנושא את לוגו החברה או שמה המודפס ובצירוף חותמת החברה. בהעדר מסמך כאמור (לרבות מסמך סרוק) המצורף להודעת דואר אלקטרוני זאת, אין לראות באמור בהודעה אלא משום טיוטה לדיון, ואין להסתמך עליה לביצוע פעולה עסקית או משפטית כלשהי. Please note that in accordance with Malam's signatory rights, no offer, agreement, concession or representation is binding on the company, unless accompanied by a duly signed separate document (or a scanned version thereof), affixed with the company's seal. -- 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
Re: Managing WLM manged initiators
??? ?? ??? gad...@malam.com wrote in message news:c11ded818b17214792b97fba28712bed04fa69c...@jer-email1.jer.ad.malam .com... Hi, We've started using WLM managed initiators. Using JES2 commands we can specify the maximum number of initiators per class, and even per system. The number of jobs per system is visible and changeable using the JC command. Does anyone know of a utility that can display and change the values per system? Thanks Gadi See the $DSRVCLASS command to display the current limits set by WLM and used by JES2. Kees. For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- 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
Re: Managing WLM manged initiators
Thanks, but I'm looking for something that doesn't require command. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Vernooij, CP - SPLXM Sent: Monday, July 11, 2011 2:43 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Managing WLM manged initiators ??? ?? ??? gad...@malam.com wrote in message news:c11ded818b17214792b97fba28712bed04fa69c...@jer-email1.jer.ad.malam .com... Hi, We've started using WLM managed initiators. Using JES2 commands we can specify the maximum number of initiators per class, and even per system. The number of jobs per system is visible and changeable using the JC command. Does anyone know of a utility that can display and change the values per system? Thanks Gadi See the $DSRVCLASS command to display the current limits set by WLM and used by JES2. Kees. For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- 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 לשימת לבך, בהתאם לנהלי החברה וזכויות החתימה בה, כל הצעה, התחייבות או מצג מטעם החברה, מחייבים מסמך נפרד וחתום על ידי מורשי החתימה של החברה, הנושא את לוגו החברה או שמה המודפס ובצירוף חותמת החברה. בהעדר מסמך כאמור (לרבות מסמך סרוק) המצורף להודעת דואר אלקטרוני זאת, אין לראות באמור בהודעה אלא משום טיוטה לדיון, ואין להסתמך עליה לביצוע פעולה עסקית או משפטית כלשהי. Please note that in accordance with Malam's signatory rights, no offer, agreement, concession or representation is binding on the company, unless accompanied by a duly signed separate document (or a scanned version thereof), affixed with the company's seal. -- 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
Re: Managing WLM manged initiators
Using JES2 commands we can specify the maximum number of initiators per class, and even per system. The number of jobs per system is visible and changeable using the JC command. Does anyone know of a utility that can display and change the values per system? Thanks, but I'm looking for something that doesn't require command. Gadi - In JES2 it is always a command whether there is an panel interface with it or not. So, the question I have is - what specifically are your needs? Operations, end user, audit process and control? Automation? For example, with OPS/MVS you could devise a process. Or if you use Tivoli, then it may already be built-in. It would help to know your requirements for such an interface. Currently SDSF has a panel. Perhaps that is not what your needs require? Lizette -- 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
Re: Managing WLM manged initiators
I am looking for something I can show the operators. CA-SYSVIEW doesn't have it. Gadi -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Lizette Koehler Sent: Monday, July 11, 2011 3:09 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Managing WLM manged initiators Using JES2 commands we can specify the maximum number of initiators per class, and even per system. The number of jobs per system is visible and changeable using the JC command. Does anyone know of a utility that can display and change the values per system? Thanks, but I'm looking for something that doesn't require command. Gadi - In JES2 it is always a command whether there is an panel interface with it or not. So, the question I have is - what specifically are your needs? Operations, end user, audit process and control? Automation? For example, with OPS/MVS you could devise a process. Or if you use Tivoli, then it may already be built-in. It would help to know your requirements for such an interface. Currently SDSF has a panel. Perhaps that is not what your needs require? Lizette -- 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 לשימת לבך, בהתאם לנהלי החברה וזכויות החתימה בה, כל הצעה, התחייבות או מצג מטעם החברה, מחייבים מסמך נפרד וחתום על ידי מורשי החתימה של החברה, הנושא את לוגו החברה או שמה המודפס ובצירוף חותמת החברה. בהעדר מסמך כאמור (לרבות מסמך סרוק) המצורף להודעת דואר אלקטרוני זאת, אין לראות באמור בהודעה אלא משום טיוטה לדיון, ואין להסתמך עליה לביצוע פעולה עסקית או משפטית כלשהי. Please note that in accordance with Malam's signatory rights, no offer, agreement, concession or representation is binding on the company, unless accompanied by a duly signed separate document (or a scanned version thereof), affixed with the company's seal. -- 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
Re: Managing WLM manged initiators
I am looking for something I can show the operators. CA-SYSVIEW doesn't have it. Gadi Using JES2 commands we can specify the maximum number of initiators per class, and even per system. The number of jobs per system is visible and changeable using the JC command. Does anyone know of a utility that can display and change the values per system? Thanks, but I'm looking for something that doesn't require command. Gadi, In the SYSVIEW USER's guide there is a section on how to build your own display function. See if that will help. Lizette -- 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
Re: Managing WLM manged initiators
On Mon, 11 Jul 2011 12:44:09 +0300, #1490;#1491;#1497; #1489;#1503; #1488;#1489;#1497; gad...@malam.com wrote: Hi, Weve started using WLM managed initiators. Using JES2 commands we can specify the maximum number of initiators per class, and even per system. The number of jobs per system is visible and changeable using the JC command. Does anyone know of a utility that can display and change the values per system? I don't understand what you are looking for. $DJOBCLASS(*),LONG $DSRVCLASS(*),LONG $TJOBCLASS(n),XEQCOUT=n And all can be displayed and change with the SDSF JC command as you wrote. XEQMEMBER takes a JES2 command to change (unless that was added in z/OS 1.12) $TJOBCLASS(n),XEQMEMBER(abc)=(MAXIMUM=n) Isn't SDSF a utility? Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- 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
Re: Initiators
On Wed, 15 Sep 2010 17:10:11 -0400, Thompson, Steve wrote: -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Tom Marchant Sent: Wednesday, September 15, 2010 3:42 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Initiators On Wed, 15 Sep 2010 16:06:55 -0400, Thompson, Steve wrote: Each initiator, drained or running, takes up room in the SQA for ASCBs and such. An address space is created when the initiator is started. When the initiator is drained the address space ends. There is no ASCB for a drained initiator. SNIPPAGE And where does the ASCB go? It isn't pageable now is it? I could be wrong, but I thought that when an address space terminates the ASCB is deleted. I thought all of these had to be configured in IEASYSxx. And that is even if it is WLM controlled. MAXUSER=nn Yes, MAXUSER sets a limit to the number of ASIDs that can be in use. I thought that an ASCB was created when the address space was created and deleted when the address space terminated. But if, as I think you are suggesting, an ASCB is created for them all at IPL time, then it doesn't matter whether some number of those ASCBs are allocated to drained initiators, does it? -- Tom Marchant -- 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
Re: Initiators
On Thu, 16 Sep 2010 06:23:34 -0500, Tom Marchant wrote: I could be wrong, but I thought that when an address space terminates the ASCB is deleted. I thought all of these had to be configured in IEASYSxx. And that is even if it is WLM controlled. MAXUSER=nn Yes, MAXUSER sets a limit to the number of ASIDs that can be in use. I thought that an ASCB was created when the address space was created and deleted when the address space terminated. But if, as I think you are suggesting, an ASCB is created for them all at IPL time, then it doesn't matter whether some number of those ASCBs are allocated to drained initiators, does it? May I assume this applies equally to address spaces created by BPXAS? -- gil -- 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
Re: Initiators
On Thu, 16 Sep 2010 08:09:28 -0500, Mark Zelden mzel...@flash.net wrote: The ASCB (at least in z/OS 1.11) is 384 bytes and is located below the 16M line. It would be a very bad thing if they were all allocated / reserved based on MAXUSER. I meant to write... would have been in the context of MVS history. -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- 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
Re: Initiators
On Thu, 16 Sep 2010 06:23:34 -0500, Tom Marchant m42tom-ibmm...@yahoo.com wrote: On Wed, 15 Sep 2010 17:10:11 -0400, Thompson, Steve wrote: -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Tom Marchant Sent: Wednesday, September 15, 2010 3:42 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Initiators On Wed, 15 Sep 2010 16:06:55 -0400, Thompson, Steve wrote: Each initiator, drained or running, takes up room in the SQA for ASCBs and such. An address space is created when the initiator is started. When the initiator is drained the address space ends. There is no ASCB for a drained initiator. SNIPPAGE And where does the ASCB go? It isn't pageable now is it? I could be wrong, but I thought that when an address space terminates the ASCB is deleted. I thought all of these had to be configured in IEASYSxx. And that is even if it is WLM controlled. MAXUSER=nn Yes, MAXUSER sets a limit to the number of ASIDs that can be in use. I thought that an ASCB was created when the address space was created and deleted when the address space terminated. But if, as I think you are suggesting, an ASCB is created for them all at IPL time, then it doesn't matter whether some number of those ASCBs are allocated to drained initiators, does it? MAXUSER controls the creation of the ASVT (address space vector table), along with RSVSTRT and RSVNONR. Those entries are 4 bytes each. There is also storage used by CSCB/CSCXs which use SQA/ESQA (depends on your IEASYSxx CSCBLOC parm). That is all the storage that is reserved. As the name suggests, ASCBs are associated with address spaces. No address space, no ASCB. The ASCB (at least in z/OS 1.11) is 384 bytes and is located below the 16M line. It would be a very bad thing if they were all allocated / reserved based on MAXUSER. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- 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
Initiators
Is there any reason why you shouldn't have alot of initiators defined, but have alot of them drained. Is there any performance considerations? Thanks -- 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
Re: Initiators
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of gsg Sent: Wednesday, September 15, 2010 2:56 PM To: IBM-MAIN@bama.ua.edu Subject: Initiators Is there any reason why you shouldn't have alot of initiators defined, but have alot of them drained. Is there any performance considerations? Thanks So long as the shop is disciplined, then having defined, but drained, initiators are 0 cost. We are not disciplined. We had to remove initiators because we couldn't stop the NOC from firing up another one for this really hot job!. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-691-6183 cell john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- 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
Re: Initiators
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of gsg Sent: Wednesday, September 15, 2010 2:56 PM To: IBM-MAIN@bama.ua.edu Subject: Initiators Is there any reason why you shouldn't have alot of initiators defined, but have alot of them drained. Is there any performance considerations? Thanks SNIPPAGE Each initiator, drained or running, takes up room in the SQA for ASCBs and such. Other than that, there is some storage taken within JES2 (or JES3). That's about the only real overhead I can think of for excess, but drained, INITS. Later, Steve Thompson -- 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
Re: Initiators
Wouldn't you be better served by putting the initiators under WLM control? Then you would have as many initiators as you need without over committing CPU. Thank You, Dave O'Brien NIH Contractor From: McKown, John [john.mck...@healthmarkets.com] Sent: Wednesday, September 15, 2010 3:59 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Initiators -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of gsg Sent: Wednesday, September 15, 2010 2:56 PM To: IBM-MAIN@bama.ua.edu Subject: Initiators Is there any reason why you shouldn't have alot of initiators defined, but have alot of them drained. Is there any performance considerations? Thanks So long as the shop is disciplined, then having defined, but drained, initiators are 0 cost. We are not disciplined. We had to remove initiators because we couldn't stop the NOC from firing up another one for this really hot job!. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-691-6183 cell john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- 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
Re: Initiators
Why not just put them under WLM control, and then the system controls how many you use (up to your set limits)? This is much easier than manually stopping and starting initiators, and it takes the control away from operators who usually do not understand the impact starting too many initiators can have on system performance. C. Todd Burrell PMP, MCSE 2003:Security Security+, Network+ ITIL V3 Foundations CSC Lead z/OS Systems Programmer ITSO (404) 723-2017 (Cell) -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of gsg Sent: Wednesday, September 15, 2010 3:56 PM To: IBM-MAIN@bama.ua.edu Subject: Initiators Is there any reason why you shouldn't have alot of initiators defined, but have alot of them drained. Is there any performance considerations? Thanks -- 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
Re: Initiators
On Wed, 15 Sep 2010 16:06:55 -0400, Thompson, Steve wrote: Each initiator, drained or running, takes up room in the SQA for ASCBs and such. An address space is created when the initiator is started. When the initiator is drained the address space ends. There is no ASCB for a drained initiator. I agree with Dave O'Brien. WLM managed initiators are a good thing as long as they work for you. -- Tom Marchant -- 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
Re: Initiators
Thanks everyone for your replies. We haven't started using WLM YET, but I'll look into it. Thanks again. -- 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
Re: Initiators
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Tom Marchant Sent: Wednesday, September 15, 2010 3:42 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Initiators On Wed, 15 Sep 2010 16:06:55 -0400, Thompson, Steve wrote: Each initiator, drained or running, takes up room in the SQA for ASCBs and such. An address space is created when the initiator is started. When the initiator is drained the address space ends. There is no ASCB for a drained initiator. SNIPPAGE And where does the ASCB go? It isn't pageable now is it? I thought all of these had to be configured in IEASYSxx. And that is even if it is WLM controlled. MAXUSER=nn This parameter specifies a value that, under most conditions, the system uses to limit the number of jobs and started tasks that can run concurrently during a given IPL. The number includes time sharing jobs, batch jobs, started system tasks, the master scheduler, JES2 or JES3. MAXUSER entries can also include ASIDs that have been marked non-reusable if their total number exceeds the RSVNONR value. This parameter is also used to allocate console control block areas in CSA that contain run-time job description data. Regards, Steve Thompson -- 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
Re: Initiators
Wouldn't you be better served by putting the initiators under WLM control? Then you would have as many initiators as you need without over committing CPU. 1: WLM managed inits are not a panacea. 2: Undisciplined operators can still wreak havoc. - I'm a SuperHero with neither powers, nor motivation! Kimota! -- 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
Re: Initiators
Why not just put them under WLM control, and then the system controls how many you use (up to your set limits)? This is much easier than manually stopping and starting initiators, and it takes the control away from operators who usually do not understand the impact starting too many initiators can have on system performance. It does not take control away. It just moves the control. Operators can still start extra jobs. And, WLM controlled inits don't help in all situations. - I'm a SuperHero with neither powers, nor motivation! Kimota! -- 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
Re: Initiators
While I do recommend WLM-inits for many types of work, I don't recommend it for all types. While you can use JES commands to limit the max number of inits by Jobclass, WLM-inits work well for similar types of workloads. You can certainly have multiple Service Classes defined for WLM-inits, but you may know specifics about your workloads that WLM does not. Example, if you have some DB2 batch running, and it optimally uses 10 inits, WLM could double it based on the CURRENT state of the system(s). Just because the PI is acceptable, may not mean your DB2 databases can handle 20 or 50 parallel jobs. Also jobs dependent on real tape mounts, or even lengthy HSM recalls, can skew how well WLM-inits work. So, be sure you know your workloads, use both types of inits as appropriate. zNorman -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Ted MacNEIL Sent: Wednesday, September 15, 2010 Wednesday 4:01 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Initiators Why not just put them under WLM control, and then the system controls how many you use (up to your set limits)? This is much easier than manually stopping and starting initiators, and it takes the control away from operators who usually do not understand the impact starting too many initiators can have on system performance. It does not take control away. It just moves the control. Operators can still start extra jobs. And, WLM controlled inits don't help in all situations. - I'm a SuperHero with neither powers, nor motivation! Kimota! -- 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
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
Re: WLM managed Initiators
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
Re: WLM managed Initiators
Works just fine in a MONOPLEX. I am doing it now. Additional initiators are started/stopped based on the mix of work currently in the system. If you have some mix of JES and WLM managed inits, this can be used (as one example) to limit test/dev work when production is heavy. Pay close attention to your goals. If they are set unrealistically, you will not get good results. I recommend the following as *REQUIRED* reading before proceeding (watch the wrap): http://www-03.ibm.com/servers/resources/servers_eserver_zseries_zos_wlm_ pdf_cmgbatch_pdf_wlm_goal_based_initiator_management.pdf http://www-03.ibm.com/servers/resources/servers_eserver_zseries_zos_wlm_ pdf_wlminits_pdf_wlminitsjm.pdf http://www-03.ibm.com/servers/resources/servers_eserver_zseries_zos_wlm_ pdf_velocity_pdf_velocity.pdf HTH, snip 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? /snip -- 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
WLM initiators and IEF196I messages
Hi all, A little something I noticed... We have some code in IEFACTRT that issues WTO messages with route code 11 (don't ask..). When a job is running under a JES-managed initiator, the messages are displayed fine in the JESMSGLG. When a job is running under a WLM-managed initiator, each message is echoed again with IEF196I message. I know that is what IEF196I is for. I see IWM034I stating that the WLM-managed initiator was started with parameters SUB=MSTR. But isn't that behavior of WLM-managed initiators inconsistent with the behavior of JES-managed initiators? Shouldn't WLM-managed initiators be started under the JES subsystem like JES-managed initiators? Thanks, Gil. -- 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
Re: WLM initiators and IEF196I messages
On Mon, 2009-09-14 at 06:48 -0400, Gil Peleg wrote: We have some code in IEFACTRT that issues WTO messages with route code 11 Yes, we changed our ACTRT to issue messages with another route code so to avoid those superfluous (IMO) IEF196I messages. -- David Andrews A. Duda and Sons, Inc. david.andr...@duda.com -- 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
Re: WLM initiators
On Tue, 17 Feb 2009 16:19:29 -0600, Field, Alan C. wrote: We've tried to manage the number of inits manually to balance the utilization but it's not easy. We're wondering about WLM inits for this class. Early experience with WLM inits wasn't positive. I had great results with WLM initiators when I went to OS/390 2.4. I think it might have helped that all of my batch goals were response time goals. I made sure that none of my goals were too aggressive and for batch I used fairly low percentiles on my response time goals. At the time of the upgrade to 2.4, we were very far back level and were running at 100% all day. CICS response times were starting to suffer before going to 2.4 and goal mode. After the upgrade, we found that there were usually fewer initiatirs running and everything ran better, including test batch work. I'm not at that shop any more and am no longer doing WLM work as part of my regular responsibilities, so I can't give details. I did post them way back then so you could check the archives. This is what I remember. For our test job class, I had a goal of 50% complete in under 5 minutes. I had determined ahead of time that it was an easy goal to meet. For our production job classes I had a goal of something like 50% complete in less than 30 minutes. We did have a number of production jobs that ran for a lot longer than 30 minutes, but there were always enough fast running jobs in the system so that WLM was able to meet the goal. We had only one job class that couldn't use WLM initiators because of some automation that started and stopped the initiator and sometimes inserted a restore job to recover from abends. We tried to change the automation to set the maximum number of jobs in that class to zero and back to one rather than stop and start the init. It worked ok, but was too slow, so we put that job class back under JES control. You will find that with WLM managed inits, you can't see the initiators in an SDSF INIT display. You can, however see a lot of useful information in a JC display. Also, with WLM inits, when there is a job that needs to start now, you can simply use $S jobname. Of course, YMMV. -- Tom Marchant -- 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
WLM initiators
We are a JES2 shop, z/OS 1.8 going to 1.10. We have two production LPARS in a parallel sysplex. CLASS=A work can run on either lpar Because the job scheduling package runs on only one lpar is tends overload its lpar. We've tried to manage the number of inits manually to balance the utilization but it's not easy. We're wondering about WLM inits for this class. Early experience with WLM inits wasn't positive. Have things improved, should we give it another try? Alan -- 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
Re: WLM initiators
On Tue, 17 Feb 2009 16:19:29 -0600, Field, Alan C. alan.c.fi...@supervalu.com wrote: We are a JES2 shop, z/OS 1.8 going to 1.10. We have two production LPARS in a parallel sysplex. CLASS=A work can run on either lpar Because the job scheduling package runs on only one lpar is tends overload its lpar. We've tried to manage the number of inits manually to balance the utilization but it's not easy. We're wondering about WLM inits for this class. Early experience with WLM inits wasn't positive. Have things improved, should we give it another try? On my way out for the day so sorry for a brief answer. I am going to say a qualified yes. Some changes were made to help balance at the z/OS 1.8 level (I think that was it).Don't know when you tried it last.So it's still flawed but better than it used to be and may be good enough for you (we've been running WLM since OS/390 2.4). Search the archives, review the WLM redbook and SHARE for more information. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:mark.zel...@zurichna.com z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
Re: WLM managed initiators
Take care if you've assigned a resource group capping for these batch because WLM doesn't take into account this type of delay (RGC-delay). If your system is not saturated, WLM will continue to start new inits as more jobs are submitted. Regards -- 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
Re: WLM managed initiators
Hi, We implemented WLM managed inits in our shop back at 1.7, and ran into some of the same issues with WLM mangaged init - YES - if you change the class to wlm managed it takes effect for the entire mas, and at least prior to 1.9 (I haven't checked 1.9 yet), you could set a class limit but that was also mas wide, again no help in segregating jobs. The problems can get more complex when you want to stop jobs on only one system for a maintenance window for example so this should not be unique to your shop... What I did, was to make a change to my JES2 exits - I have been providing updates to the old MELLON shared spool mods for a dozen or more years now and we have since dropped the MELLON part - in fact we dropped the mods - they are really all standard exits at this point. With the latest version of our exits (available from the CBT tape website - File#766 in the Latest updates are always available to download here section), we can control the number of jobs that may be initiated on any system in the mas by class - regardless of whether they are WLM or JES2 managed. So for your situation I would simply set the class limit to zero on the system where you don't want wlm to start jobs, and the other system in your mas can take advantage of the WLM managed features. The mods were originally written to do the same thing that the SCHENV feature now handles, but we also, provide additional scheduling features or job dependencies such as BEFORE/AFTER/WTH job requirements, a features for timed scheduling such as HOLDFOR (time), or HOLDTTIL (time), and a feature that allows whoever codes the JCL to specify an arbitrary resource name to hold an exclusive or shared enqueue on - we use that feature to make sure only one person runs an SMP update job at a time without needing to check with all of our co-workers in 3 states first. Anyway, if you are interested - they are free, on the cbt tape web site, are smp packaged, are all standard exits, and come with install, operations, and users guides, and they work great. Just another option. Stephen McColley -- 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
Re: WLM managed initiators
On Wed, 13 Aug 2008 08:50:09 -0500, Stephen G. McColley [EMAIL PROTECTED] wrote: The problems can get more complex when you want to stop jobs on only one system for a maintenance window for example so this should not be unique to your shop... That has never been a problem. $PXEQ is single system in scope. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- 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
Re: WLM managed initiators
I suppose I should have been a bit more specific - during our maintenance window we typically want to stop all initiator classes except one which we use to run our maintenance job in. The $PXEQ will stop everything on that one system, and we still want to do some work - it's just very selective. So with the mods we change the limits for all classes to zero, and the limit for the class we want our work to run in to just a few - 3 or 4 is usually enough for us, then we can run install / change jobs without any 'other' work getting into the system. We also have the ability with these mods to limit (or stop) work coming in based on a masked userid or jobname, so they are pretty flexible in what we can allow to start or not start - that also keeps some of our more creative users from flooding the system with work as they occasionally try to do. Stephen McColley On Wed, 2008-08-13 at 10:23 -0500, Mark Zelden wrote: On Wed, 13 Aug 2008 08:50:09 -0500, Stephen G. McColley [EMAIL PROTECTED] wrote: The problems can get more complex when you want to stop jobs on only one system for a maintenance window for example so this should not be unique to your shop... That has never been a problem. $PXEQ is single system in scope. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- 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 -- 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
Re: WLM managed initiators
On Wed, 13 Aug 2008 12:14:12 -0400, Stephen McColley [EMAIL PROTECTED] wrote: I suppose I should have been a bit more specific - during our maintenance window we typically want to stop all initiator classes except one which we use to run our maintenance job in. The $PXEQ will stop everything on that one system, and we still want to do some work - it's just very selective. Since WLM inits came around (even before we used them), we defined one class as WLM controlled. We also still do this on some small monoplex systems that use JES2 inits. Anyway, even when batch is stopped due to $PXEQ, all you have to do is a $SJOB (J next to the job from the SDSF input queue display) to force the job to run. So we have complete control over what runs during the maintenance window. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- 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
Re: WLM managed initiators
Bob Rutledge wrote: Yep, and it almost works for the Gadi's requirement :( $TJOBCLASS(Q),XEQMEMBER(Z890)=(MAXIMUM=0) $HASP003 RC=(08),T 344 $HASP003 RC=(08),T JOBCLASS(Q) XEQMEMBER(Z890) MAXIMUM - VALUE $HASP003 IS OUTSIDE NUMERICAL RANGE, RANGE IS $HASP003 (1-4294967295) Ouch! I didn't realize a zero value was disallowed for JES2. :-( -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ -- 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
Re: WLM managed initiators
Looks like one of those packages - commercial, or non-commercial are looking better and better. Stephen McColley On Wed, 2008-08-13 at 10:27 -0700, Edward Jaffe wrote: Bob Rutledge wrote: Yep, and it almost works for the Gadi's requirement :( $TJOBCLASS(Q),XEQMEMBER(Z890)=(MAXIMUM=0) $HASP003 RC=(08),T 344 $HASP003 RC=(08),T JOBCLASS(Q) XEQMEMBER(Z890) MAXIMUM - VALUE $HASP003 IS OUTSIDE NUMERICAL RANGE, RANGE IS $HASP003 (1-4294967295) Ouch! I didn't realize a zero value was disallowed for JES2. :-( -- 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
WLM managed initiators
Gadi, John, The WLM managed initiators are defined on a sysplex level. Once you tell JES that a particular class is WLM managed, it will run jobs on all (in our case both) system in the sysplex. WLM initiators are defined on a JESPLEX level, not a Sysplex Level. Of course, if your Sysplex has only one Jesplex, the above is true (as it is for Gadi). You can use Scheduler Environments to 'route' jobs on the right system, or to prevent running on a specific lpar, is that is what you want to do. Scheduler Environments are quite easy to set up. Sincères salutations, Best Regards. Coen Wessels _ IBM Suisse Centre de Compétence Bancaire Banking Competence Center 100, Av. de a Vallombreuse CH - 1008 Prilly Téléphone : +41(0) 27 327 42 71 Téléphone mobile : +41(0) 78 803 26 21 Téléphone IBM : +41(0) 58 333 46 07 Fax : +41(0) 21 644 63 00 mailto:[EMAIL PROTECTED] http://www.ibm.ch -- 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
Re: WLM managed initiators
Bob Rutledge wrote: Edward Jaffe wrote: This has always been a trivial setting for JES3 (EXCRESC for the job class group) and the lack of this capability in JES2 was a glaring omission. To compensate, the most recent JES2 releases implement a maximum XEQCOUNT by member by class. XEQCOUNT has been around for a goodly while and is MAS-wide in scope. Are you thinking of XEQMEMBER (which I believe can be set by $TJOBCLASS only)? Exactly! -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ -- 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
Re: WLM managed initiators
Edward Jaffe wrote: Bob Rutledge wrote: Edward Jaffe wrote: This has always been a trivial setting for JES3 (EXCRESC for the job class group) and the lack of this capability in JES2 was a glaring omission. To compensate, the most recent JES2 releases implement a maximum XEQCOUNT by member by class. XEQCOUNT has been around for a goodly while and is MAS-wide in scope. Are you thinking of XEQMEMBER (which I believe can be set by $TJOBCLASS only)? Exactly! Yep, and it almost works for the Gadi's requirement :( $TJOBCLASS(Q),XEQMEMBER(Z890)=(MAXIMUM=0) $HASP003 RC=(08),T 344 $HASP003 RC=(08),T JOBCLASS(Q) XEQMEMBER(Z890) MAXIMUM - VALUE $HASP003 IS OUTSIDE NUMERICAL RANGE, RANGE IS $HASP003 (1-4294967295) Bob -- 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
Re: WLM managed initiators
On Sun, 10 Aug 2008 21:38:12 +, Ted MacNEIL [EMAIL PROTECTED] wrote: John wrote: I'm not really very knowledgable about WLM initiators, but wouldn't it be possible to only tell the JES2 on a particular system to service a specific class? E.g. JES2 on SY1 has a JOBCLASS(C) MODE=WLM defination in it. JES2 on SY2 has JOBCLASS(C) MODE=JES and does not have any static initiators set up to service class C. JOBCLASS(n) definitions are MAS wide, so assuming this is one MAS, then that would not be possible. I wouldn't mix up WLM JES management in the same MAS. Why? Not only is there no harm in doing it, it is a requirement in many shops. WLM inits were not meant for jobs that need immediate initiation as there can be some delay. I can give many examples, but a simple one would be a batch job submitted from a CICS transaction that does something that needs a very quick turnaround. A WLM init might not even start at all in that situation if the system is running near 100% busy. What you aren't suppose to do is mix WLM inits and JES2 inits in the same service class. Which also means you can ease into WLM inits by converting a certain set of service classes first (test vs. production). Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- 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
Re: WLM managed initiators
I wouldn't mix up WLM JES management in the same MAS. Why? I was responding to John's comment about mixed for the same jobclass, I meant what John said about two types of management for the same jobclass -- which at the time I responded, I had forgotten that a jobclass is sysplex wide. Not only is there no harm in doing it, it is a requirement in many shops. Yes. I know. . . What you aren't suppose to do is mix WLM inits and JES2 inits in the same service class. Yes. I know that, too. - Too busy driving to stop for gas! -- 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
Re: WLM managed initiators
bci ao `ai wrote: Hi, We would like to use WLM managed initiators for some of our classes. The jobs running in these classes can only run on one of the systems in our sysplex. Is there a way to make sure that the jobs will run on oe system other that using /*JOBPARM SYSAFF=? This has always been a trivial setting for JES3 (EXCRESC for the job class group) and the lack of this capability in JES2 was a glaring omission. To compensate, the most recent JES2 releases implement a maximum XEQCOUNT by member by class. -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ -- 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
Re: WLM managed initiators
I prefer using scheduling environments. In our environment, we set up scheduling environments to handle most jobs by supplying it in several JES2 exits. However, one issue scheduling environments does not address is JCL conversion. Conversion could occur on any system in the MAS. Most jobs have no dependencies during conversion, but if you have different proclib concatenations or utilize subsys parameters, conversion may only work on the systems where they are supported. In this case, you do have to revert to SYSAFF. -- 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
Re: WLM managed initiators
Actually, IBM recommends using both types of initiators depending on the type of work. Specifically, production batch under JES2 and the rest under WLM. Anyway, Scheduling Environments will segregate the work. Define an unique SE for each LPAR or member of the MAS, e.g. LPAR1, LPAR2 ... Define a unique resource for each, e.g. LPAR1, LPAR2 ... Then, when you activate the resources, set LPAR1 ON, LPAR2 OFF on LPAR1, and, vice versa on LPAR2. Also, the user must add a SCHENV parameter to the JOB statement. In our case, we couldn't rely on the user to do this, so I wrote JES2 Exits 2 52 to add the parameter in case the user do not supply one. -- 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
Re: WLM managed initiators
Edward Jaffe wrote: bci ao `ai wrote: Hi, We would like to use WLM managed initiators for some of our classes. The jobs running in these classes can only run on one of the systems in our sysplex. Is there a way to make sure that the jobs will run on oe system other that using /*JOBPARM SYSAFF=? This has always been a trivial setting for JES3 (EXCRESC for the job class group) and the lack of this capability in JES2 was a glaring omission. To compensate, the most recent JES2 releases implement a maximum XEQCOUNT by member by class. XEQCOUNT has been around for a goodly while and is MAS-wide in scope. Are you thinking of XEQMEMBER (which I believe can be set by $TJOBCLASS only)? Bob -- 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
WLM managed initiators
Hi, We would like to use WLM managed initiators for some of our classes. The jobs running in these classes can only run on one of the systems in our sysplex. Is there a way to make sure that the jobs will run on oe system other that using /*JOBPARM SYSAFF=? TIA Gadi -- 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
Re: WLM managed initiators
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of ??? ?? ??? Sent: Sunday, August 10, 2008 3:16 AM To: IBM-MAIN@BAMA.UA.EDU Subject: WLM managed initiators Hi, We would like to use WLM managed initiators for some of our classes. The jobs running in these classes can only run on one of the systems in our sysplex. Is there a way to make sure that the jobs will run on oe system other that using /*JOBPARM SYSAFF=? TIA Gadi I'm not really very knowledgable about WLM initiators, but wouldn't it be possible to only tell the JES2 on a particular system to service a specific class? E.g. JES2 on SY1 has a JOBCLASS(C) MODE=WLM defination in it. JES2 on SY2 has JOBCLASS(C) MODE=JES and does not have any static initiators set up to service class C. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- 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
Re: WLM managed initiators
I'm not really very knowledgable about WLM initiators, but wouldn't it be possible to only tell the JES2 on a particular system to service a specific class? E.g. JES2 on SY1 has a JOBCLASS(C) MODE=WLM defination in it. JES2 on SY2 has JOBCLASS(C) MODE=JES and does not have any static initiators set up to service class C. I wouldn't mix up WLM JES management in the same MAS. But, besides SYSAFF, there other options. Such as a scheduling environment. - Too busy driving to stop for gas! -- 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
Re: WLM managed initiators
Hi John, The WLM managed initiators are defined on a sysplex level. Once you tell JES that a particular class is WLM managed, it will run jobs on all (in our case both) system in the sysplex. We found this out the hard way. Gadi -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Monday, August 11, 2008 12:03 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: WLM managed initiators -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of ??? ?? ??? Sent: Sunday, August 10, 2008 3:16 AM To: IBM-MAIN@BAMA.UA.EDU Subject: WLM managed initiators Hi, We would like to use WLM managed initiators for some of our classes. The jobs running in these classes can only run on one of the systems in our sysplex. Is there a way to make sure that the jobs will run on oe system other that using /*JOBPARM SYSAFF=? TIA Gadi I'm not really very knowledgable about WLM initiators, but wouldn't it be possible to only tell the JES2 on a particular system to service a specific class? E.g. JES2 on SY1 has a JOBCLASS(C) MODE=WLM defination in it. JES2 on SY2 has JOBCLASS(C) MODE=JES and does not have any static initiators set up to service class C. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- 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 -- 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
WLM managed initiators
___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of ??? ?? ??? Sent: Sunday, August 10, 2008 3:16 AM To: IBM-MAIN@BAMA.UA.EDU Subject: WLM managed initiators Hi, We would like to use WLM managed initiators for some of our classes. The jobs running in these classes can only run on one of the systems in our sysplex. Is there a way to make sure that the jobs will run on oe system other that using /*JOBPARM SYSAFF=? TIA Gadi What about a JES2 Command such as $TJOBCLASS(x),QAFF=sysname ? Thanks Regards, - Stephen Hall Mainframe Platform Manager Platform Support Services Technology Services INSURANCE AUSTRALIA GROUP (IAG) ___ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses with Symantec Scan Engine and cleared by MailMarshal. ___ -- 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
Re: WLM managed initiators
Thanx. Unfortunatly, QAFF is not available on z/OS 1.7. It does work os z/OS 1.9. Gadi -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Hall Sent: Monday, August 11, 2008 7:30 AM To: IBM-MAIN@BAMA.UA.EDU Subject: WLM managed initiators ___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of ??? ?? ??? Sent: Sunday, August 10, 2008 3:16 AM To: IBM-MAIN@BAMA.UA.EDU Subject: WLM managed initiators Hi, We would like to use WLM managed initiators for some of our classes. The jobs running in these classes can only run on one of the systems in our sysplex. Is there a way to make sure that the jobs will run on oe system other that using /*JOBPARM SYSAFF=? TIA Gadi What about a JES2 Command such as $TJOBCLASS(x),QAFF=sysname ? Thanks Regards, - Stephen Hall Mainframe Platform Manager Platform Support Services Technology Services INSURANCE AUSTRALIA GROUP (IAG) ___ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses with Symantec Scan Engine and cleared by MailMarshal. ___ -- 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 -- 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
JES2 $TI or $SI command on initiators over initiator 99 return invalid
I need to pull out my WLM Managed Initiators to prepare for the outsourcer. In preparation, in testing, when we issue a $TI or $SI for initiators after initiator 99 I get $HASP650 IA0 INVALID OPERAND OR MISPLACED OPERAND. Anyone hit a similar problem or have a solution, we are at z/OS 1.4 at this time. TIA... -- 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
Re: JES2 $TI or $SI command on initiators over initiator 99 return invalid
Man, I hate replying to my own questions. Our ops guys figured that you need paren's around the actual initiator *after* initiator number 99. Hopefully the formatting of the commands below comes out. $SI99 $HASP892 INIT(99) $HASP892 INIT(99) STATUS=STARTING,CLASS=, $HASP892INELIGIBLE_CLASS=(X-WLM),NAME=99 $SI(A0) $HASP892 INIT(100) $HASP892 INIT(100) STATUS=STARTING,CLASS=, $HASP892INELIGIBLE_CLASS=(X-WLM),NAME=A0 [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 09/21/2007 09:22 AM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject JES2 $TI or $SI command on initiators over initiator 99 return invalid I need to pull out my WLM Managed Initiators to prepare for the outsourcer. In preparation, in testing, when we issue a $TI or $SI for initiators after initiator 99 I get $HASP650 IA0 INVALID OPERAND OR MISPLACED OPERAND. Anyone hit a similar problem or have a solution, we are at z/OS 1.4 at this time. TIA... -- 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
Re: Jobs and the initiators they run in
NOTICE: All information in and attached to the e-mail(s) below may be proprietary, confidential, privileged and otherwise protected from improper or erroneous disclosure. If you are not the sender's intended recipient, you are not authorized to intercept, read, print, retain, copy, forward, or disseminate this message. If you have erroneously received this communication, please notify the sender immediately by phone (704-758-1000) or by e-mail and destroy all copies of this message (electronic, paper, or otherwise). Thank you. I wanted to let everyone know that, thanks to Barry Merrill's note below, I was able to come up with a way to track what initiator a job runs in. It does require the use of MXG because Barry's IEFU84 exit is part of MXG, but it works great! As you can tell from his note, he assumes familiarity with MXG. Since it was a private note to me he was right. For those of you not familiar with MXG, he is referring to member IEFU84 in SOURCLIB. Jim Horne Lowe's Companies, Inc. Barry Merrill wrote: Member IEFU84 is the SMF Exit Code to add Initiator Name and Number to the SMF 30 Subtype 1, and member VMAC30 will then pick that information up. -- 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
Re: Jobs and the initiators they run in
Horne, Jim - James S [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... NOTICE: All information in and attached to the e-mail(s) below may be proprietary, confidential, privileged and otherwise protected from improper or erroneous disclosure. If you are not the sender's intended recipient, you are not authorized to intercept, read, print, retain, copy, forward, or disseminate this message. If you have erroneously received this communication, please notify the sender immediately by phone (704-758-1000) or by e-mail and destroy all copies of this message (electronic, paper, or otherwise). Thank you. Is there any way using SMF data that I can see what initiator a job was running in? I am trying to develop a map of what was running on a system at a particular time (jobs only) and it occurred to me that if I can somehow see what was in the initiators when, I've got what I need. Thanks in advance, Jim Horne Lowe's Companies Systems Programmer IT Technical Services IS7-5 [EMAIL PROTECTED] Why so complicated or do I miss something? The SMF 30 records of all jobs show on which system they ran. Why do you need to know the initiator it ran in? The JES2 $DA command will show which job runs in which initiator, or HASP373 will tell you, but you must process SYSLOG for this. Kees. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ** -- 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
Jobs and the initiators they run in
NOTICE: All information in and attached to the e-mail(s) below may be proprietary, confidential, privileged and otherwise protected from improper or erroneous disclosure. If you are not the sender's intended recipient, you are not authorized to intercept, read, print, retain, copy, forward, or disseminate this message. If you have erroneously received this communication, please notify the sender immediately by phone (704-758-1000) or by e-mail and destroy all copies of this message (electronic, paper, or otherwise). Thank you. Is there any way using SMF data that I can see what initiator a job was running in? I am trying to develop a map of what was running on a system at a particular time (jobs only) and it occurred to me that if I can somehow see what was in the initiators when, I've got what I need. Thanks in advance, Jim Horne Lowe's Companies Systems Programmer IT Technical Services IS7-5 [EMAIL PROTECTED] -- 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
Another question on WLM initiators
Hi, all We just began to use WLM initiator in our test system. It is a 6 LPARs SYSPLEX, the CPU is not so busy, about 60% or less at batch time. When we check SMF30SQT for our batch jobs, we find that for JES2 initiator, the average is 3887, and the maximum is 12616, remember the unit is 1024 microsecond, for WLM initiator, the average is 6220, and the maximum is 41422. We does not mix JES2 and WLM initiator in a same service class. It seems too long for batch waiting for a WLM initiator, so what is a reasonable number of SMF30SQT for WLM initiator? -- 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
Re: Another question on WLM initiators
[EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... Hi, all We just began to use WLM initiator in our test system. It is a 6 LPARs SYSPLEX, the CPU is not so busy, about 60% or less at batch time. When we check SMF30SQT for our batch jobs, we find that for JES2 initiator, the average is 3887, and the maximum is 12616, remember the unit is 1024 microsecond, for WLM initiator, the average is 6220, and the maximum is 41422. We does not mix JES2 and WLM initiator in a same service class. It seems too long for batch waiting for a WLM initiator, so what is a reasonable number of SMF30SQT for WLM initiator? There is no such thing as a reasonable Q-time for a WLM managed job. WLM manages the goal of the jobs and the goal refers to the execution velocity or the responsetime of the entire job-life, including Q-time. The Q-time part of the job's life is not individually controllable. But remember: the job will finish as the goal specifies, and that is what you are waiting for, not where it spends its time before finishing. Kees. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. ** -- 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
