Re: WLM Service Classes
This is usually very misunderstood. It's really the number of service class PERIODS WITH velocity or response GOALS (i.e. with an importance level). The reason is because WLM on each system will wake up every ten seconds (that's an eternity in a z14!) to see if goals are being missed. It starts with importance=1 periods and works its way down. If there are too many periods, the ones at a lower importance level will never get adjusted and you might have some less important periods exceeding their goals while more important periods are missing their goals. I was able to include both my own recommendations and other IBM recommendations when I was on an IBM residency working for Frank Kyne and writing a really neat Redbook called System z Mean Time to Recovery Best Practices - SG24-7816 - http://www.redbooks.ibm.com/redbooks/pdfs/sg247816.pdf. I consider it one of the most useful Redbooks I own. It contains best practices for reducing start up and shut down of z/OS and each of the major subsystems. I especially like the section that explains the IPL process. As an example, here are recommendations from section 5.2 of the Redbook: General WLM recommendations: 1. Keep your WLM policy as simple as possible. Service classes with only a single period are usually better than two periods, and two periods are almost always better than three periods. Of course there are exceptions to every recommendation, but this provides a good place to start. 2. Use response time goals, especially percentile response time goals, when you can. Only use velocity goals when transactions goals are not supported, or for test subsystems. Specifically, you should use percentile response time goals for DB2, CICS, IMS, and WebSphere. 3. Remember to review and possibly adjust velocity goals after any hardware upgrade. 4. If you have a very large number of classification rules, consider their sequence carefully. The rules are applied serially, starting with the first one, until a match is found. 5. Do not have too many service class periods with non-discretionary goals. A good guideline is to have less than 30 non-discretionary service class periods that are active on any one system. [Cheryl note: ON ANY ONE SYSTEM! If a service class is active on SYSA and not on SYSB, you don't need to count that on SYSB.] 6. Any service class with velocity goals should have multiple address spaces assigned to it so that it can collect meaningful statistics. If you need more granularity for reporting reasons, assign the address spaces to report classes. 7. If you have not reviewed your WLM policy in several years, take the time to do it now. Several enhancements to WLM have been made that can simplify your policy, or improve response time for transactions. Cheers! Cheryl -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: question on enqueues
It's DYNALLOC that does the ENQ, not the utility. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu] Sent: Tuesday, February 16, 2021 4:34 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [EXTERNAL] Re: question on enqueues On Tue, 16 Feb 2021 20:43:30 +, Dave Barry wrote: >If I'm not mistaken, FDR has an ENQ/NOENQ option. You decide which you can >tolerate in your situation. > Some other utilities have alternative DSN|DD arguments. For DSN, the utility performs the ENQ; for DD it assumes the caller's allocation has done it. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: question on enqueues
The Initiator does an ENQ (SYSZDSN) at the beginning of the job. An authorized
program can upgrade an ENQ under the Initiator TCB.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Tuesday, February 16, 2021 5:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Re: question on enqueues
On Tue, 16 Feb 2021 22:19:56 +, Pommier, Rex wrote:
>Thanks, Dave, you pointed me in the right direction although the FDR
>documentation makes it sound like it doesn't matter how the DSNENQ option is
>set. I found this little tidbit in the FDR manual:
>
>If a data set name appears in a DD statement with DISP=SHR within the
>FDR job (not necessarily in the FDR step, FDR changes the scheduler
>enqueue for the data set to EXCLUSIVE (DISP=OLD). The data set may be
>unavailable to other tasks until the FDR job ends.
>
Nowadays it might downgrade the ENQ to the initial SHR status at completion.
If it cared to.
("scheduler" enqueue? What's a scheduler that performs enqueues?)
It hardly matters unless there are additional steps in the job.
-- gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: question on enqueues
On Tue, 16 Feb 2021 22:19:56 +, Pommier, Rex wrote:
>Thanks, Dave, you pointed me in the right direction although the FDR
>documentation makes it sound like it doesn't matter how the DSNENQ option is
>set. I found this little tidbit in the FDR manual:
>
>If a data set name appears in a DD statement with DISP=SHR within the
>FDR job (not necessarily in the FDR step, FDR changes the scheduler
>enqueue for the data set to EXCLUSIVE (DISP=OLD). The data set may be
>unavailable to other tasks until the FDR job ends.
>
Nowadays it might downgrade the ENQ to the initial SHR status at completion.
If it cared to.
("scheduler" enqueue? What's a scheduler that performs enqueues?)
It hardly matters unless there are additional steps in the job.
-- gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: question on enqueues
Thanks, Dave, you pointed me in the right direction although the FDR documentation makes it sound like it doesn't matter how the DSNENQ option is set. I found this little tidbit in the FDR manual: If a data set name appears in a DD statement with DISP=SHR within the FDR job (not necessarily in the FDR step, FDR changes the scheduler enqueue for the data set to EXCLUSIVE (DISP=OLD). The data set may be unavailable to other tasks until the FDR job ends. So that answered my question. Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of Dave Barry Sent: Tuesday, February 16, 2021 2:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [EXTERNAL] Re: question on enqueues If I'm not mistaken, FDR has an ENQ/NOENQ option. You decide which you can tolerate in your situation. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Clark Morris Sent: Monday, February 15, 2021 7:24 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: question on enqueues CAUTION! This email originated outside of the organization. Please do not open attachments or click links from an unknown or suspicious origin. == [Default] On 15 Feb 2021 15:37:38 -0800, in bit.listserv.ibm-main rpomm...@sfgmembers.com (Pommier, Rex) wrote: >I have one that's puzzling me and I'm sure there's a simple solution/answer. >I'm seeing 2 jobs running on a single system that are hitting an enqueue >problem on a parmlib. The JCL in both jobs has DISP=SHR, yet one of the jobs >has an exclusive ENQ on the library. Here's the scenario: > I suspect the flash process does an exclusive ENQ on all data sets being flashed. Clark Morris >Job A is a system backup job. It does a bit of early processing, then runs an >FDRFlash of most of our disk, then runs FDR to back up the offline volumes >created in the flash as well as some volumes that weren't flashed. Once the >backup step is done (3 hours later) it does some more post backup processing. >There are 3 steps in the post processing that allocate this parmlib, all >allocating the same member - call it A.B.C.PARM(MEMB), all with DISP=SHR. > >Job B is a cyclical job that runs in a matter of a few seconds and runs every >5 minutes. It also has A.B.C.PARM(MEMB) DISP=SHR as well as A.B.C.PARM(MEMZ) >DISP=SHR in a different step. > >Timing: > >Job A started and was doing its preliminary work. >Job B started and ended successfully. >Job A does the flash step and starts the full volume dumps. >Job B comes along again and can't start because job A has an exclusive ENQ on >A.B.C.PARM. Job B does not start until job A has completed the last step with >A.B.C.PARM in the JCL. > >A couple other points are that A.B.C.PARM is on a volume that was flashed, so >the source volume wasn't part of the backup. The job steps in both jobs with >A.B.C.PARM in them are all conditional steps that actually didn't execute. > >So my question is what could have caused an ENQ change from SHR to OLD when >the JCL explicitly has SHR? > >TIA, > >Rex > >The information contained in this message is confidential, protected from >disclosure and may be legally privileged. If the reader of this message is >not the intended recipient or an employee or agent responsible for delivering >this message to the intended recipient, you are hereby notified that any >disclosure, distribution, copying, or any action taken or action omitted in >reliance on it, is strictly prohibited and may be unlawful. If you have >received this communication in error, please notify us immediately by replying >to this message and destroy the material in its entirety, whether in >electronic or hard copy format. Thank you. > > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, send >email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this
Re: [EXTERNAL] Re: question on enqueues
On Tue, 16 Feb 2021 20:43:30 +, Dave Barry wrote: >If I'm not mistaken, FDR has an ENQ/NOENQ option. You decide which you can >tolerate in your situation. > Some other utilities have alternative DSN|DD arguments. For DSN, the utility performs the ENQ; for DD it assumes the caller's allocation has done it. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: question on enqueues
If I'm not mistaken, FDR has an ENQ/NOENQ option. You decide which you can tolerate in your situation. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Clark Morris Sent: Monday, February 15, 2021 7:24 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: question on enqueues CAUTION! This email originated outside of the organization. Please do not open attachments or click links from an unknown or suspicious origin. == [Default] On 15 Feb 2021 15:37:38 -0800, in bit.listserv.ibm-main rpomm...@sfgmembers.com (Pommier, Rex) wrote: >I have one that's puzzling me and I'm sure there's a simple solution/answer. >I'm seeing 2 jobs running on a single system that are hitting an enqueue >problem on a parmlib. The JCL in both jobs has DISP=SHR, yet one of the jobs >has an exclusive ENQ on the library. Here's the scenario: > I suspect the flash process does an exclusive ENQ on all data sets being flashed. Clark Morris >Job A is a system backup job. It does a bit of early processing, then runs an >FDRFlash of most of our disk, then runs FDR to back up the offline volumes >created in the flash as well as some volumes that weren't flashed. Once the >backup step is done (3 hours later) it does some more post backup processing. >There are 3 steps in the post processing that allocate this parmlib, all >allocating the same member - call it A.B.C.PARM(MEMB), all with DISP=SHR. > >Job B is a cyclical job that runs in a matter of a few seconds and runs every >5 minutes. It also has A.B.C.PARM(MEMB) DISP=SHR as well as A.B.C.PARM(MEMZ) >DISP=SHR in a different step. > >Timing: > >Job A started and was doing its preliminary work. >Job B started and ended successfully. >Job A does the flash step and starts the full volume dumps. >Job B comes along again and can't start because job A has an exclusive ENQ on >A.B.C.PARM. Job B does not start until job A has completed the last step with >A.B.C.PARM in the JCL. > >A couple other points are that A.B.C.PARM is on a volume that was flashed, so >the source volume wasn't part of the backup. The job steps in both jobs with >A.B.C.PARM in them are all conditional steps that actually didn't execute. > >So my question is what could have caused an ENQ change from SHR to OLD when >the JCL explicitly has SHR? > >TIA, > >Rex > >The information contained in this message is confidential, protected from >disclosure and may be legally privileged. If the reader of this message is >not the intended recipient or an employee or agent responsible for delivering >this message to the intended recipient, you are hereby notified that any >disclosure, distribution, copying, or any action taken or action omitted in >reliance on it, is strictly prohibited and may be unlawful. If you have >received this communication in error, please notify us immediately by replying >to this message and destroy the material in its entirety, whether in >electronic or hard copy format. Thank you. > > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, send >email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
CA OPSMVS batch job
Might anyone be able to point me to an example of a BATCH JCL Job that can submit CA OPSMVS commands to shutdown and start up tasks, like CICS regions? thanks Bill -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: question on enqueues
IEBGENER may do an ENQ of its own, and OPEN does a different ENQ, but the Initiator only does a shared ENQ for that SYSUT2 with DISP=SHR. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Radoslaw Skorupka [r.skoru...@hotmail.com] Sent: Tuesday, February 16, 2021 9:37 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: question on enqueues Few remarks: 1. DISP=SHR does not guarantee the SHR in effect. Actual ENQ can be different. Test: SYSUT2 in IEBGENER step and DISP=SHR - you will see exclusive ENQ. 2. I don't know FDRflash, but tools using DASD Point in Time replication features (Flashcopy, Snapshot, TimeFinder...) can work with no regular ENQ processing. -- Radoslaw Skorupka (looking for new job) Lodz, Poland W dniu 16.02.2021 o 00:37, Pommier, Rex pisze: > I have one that's puzzling me and I'm sure there's a simple solution/answer. > I'm seeing 2 jobs running on a single system that are hitting an enqueue > problem on a parmlib. The JCL in both jobs has DISP=SHR, yet one of the jobs > has an exclusive ENQ on the library. Here's the scenario: > > Job A is a system backup job. It does a bit of early processing, then runs > an FDRFlash of most of our disk, then runs FDR to back up the offline volumes > created in the flash as well as some volumes that weren't flashed. Once the > backup step is done (3 hours later) it does some more post backup processing. > There are 3 steps in the post processing that allocate this parmlib, all > allocating the same member - call it A.B.C.PARM(MEMB), all with DISP=SHR. > > Job B is a cyclical job that runs in a matter of a few seconds and runs every > 5 minutes. It also has A.B.C.PARM(MEMB) DISP=SHR as well as A.B.C.PARM(MEMZ) > DISP=SHR in a different step. > > Timing: > > Job A started and was doing its preliminary work. > Job B started and ended successfully. > Job A does the flash step and starts the full volume dumps. > Job B comes along again and can't start because job A has an exclusive ENQ on > A.B.C.PARM. Job B does not start until job A has completed the last step > with A.B.C.PARM in the JCL. > > A couple other points are that A.B.C.PARM is on a volume that was flashed, so > the source volume wasn't part of the backup. The job steps in both jobs with > A.B.C.PARM in them are all conditional steps that actually didn't execute. > > So my question is what could have caused an ENQ change from SHR to OLD when > the JCL explicitly has SHR? > > TIA, > > Rex > > The information contained in this message is confidential, protected from > disclosure and may be legally privileged. If the reader of this message is > not the intended recipient or an employee or agent responsible for delivering > this message to the intended recipient, you are hereby notified that any > disclosure, distribution, copying, or any action taken or action omitted in > reliance on it, is strictly prohibited and may be unlawful. If you have > received this communication in error, please notify us immediately by > replying to this message and destroy the material in its entirety, whether in > electronic or hard copy format. Thank you. > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: question on enqueues
What is the full name on the ENQ? That consists of both major and minor names. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Pommier, Rex [rpomm...@sfgmembers.com] Sent: Monday, February 15, 2021 6:37 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: question on enqueues I have one that's puzzling me and I'm sure there's a simple solution/answer. I'm seeing 2 jobs running on a single system that are hitting an enqueue problem on a parmlib. The JCL in both jobs has DISP=SHR, yet one of the jobs has an exclusive ENQ on the library. Here's the scenario: Job A is a system backup job. It does a bit of early processing, then runs an FDRFlash of most of our disk, then runs FDR to back up the offline volumes created in the flash as well as some volumes that weren't flashed. Once the backup step is done (3 hours later) it does some more post backup processing. There are 3 steps in the post processing that allocate this parmlib, all allocating the same member - call it A.B.C.PARM(MEMB), all with DISP=SHR. Job B is a cyclical job that runs in a matter of a few seconds and runs every 5 minutes. It also has A.B.C.PARM(MEMB) DISP=SHR as well as A.B.C.PARM(MEMZ) DISP=SHR in a different step. Timing: Job A started and was doing its preliminary work. Job B started and ended successfully. Job A does the flash step and starts the full volume dumps. Job B comes along again and can't start because job A has an exclusive ENQ on A.B.C.PARM. Job B does not start until job A has completed the last step with A.B.C.PARM in the JCL. A couple other points are that A.B.C.PARM is on a volume that was flashed, so the source volume wasn't part of the backup. The job steps in both jobs with A.B.C.PARM in them are all conditional steps that actually didn't execute. So my question is what could have caused an ENQ change from SHR to OLD when the JCL explicitly has SHR? TIA, Rex The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM Service Classes
We're in the software developmental business and one of our customers reported a problem when 100 WLM service classes were defined and active. We needed to reproduce their environment to test a fix. Once I read the advice "don't do it", I used one of our stand-alone z/OS systems to model the customers environment so as not to impact other activities in our main sysplex. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Tuesday, February 16th, 2021 at 9:38 AM, Martin Packer wrote: > We normally put it this way: > > Too many ACTIVE service class periods with too little work in each of them > > makes it difficult for WLM to be helpful. > > Cheers, Martin > > Martin Packer > > Systems Investigator & Performance Troubleshooter, IBM > > +44-7802-245-584 > > email: martin_pac...@uk.ibm.com > > Twitter / Facebook IDs: MartinPacker > > Blog: https://mainframeperformancetopics.com > > Mainframe, Performance, Topics Podcast Series (With Marna Walle): > > https://anchor.fm/marna-walle > > Youtube channel: https://www.youtube.com/channel/UCu_65HaYgksbF6Q8SQ4oOvA > > From: "Edgington, Jerry" jerry.edging...@westernsouthernlife.com > > To: IBM-MAIN@LISTSERV.UA.EDU > > Date: 16/02/2021 13:21 > > Subject: [EXTERNAL] Re: WLM Service Classes > > Sent by: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU > > Mark, > > IBM recommends < 30 Service Classes. WLM has a limited amount of time to > > cycle through the WLM service classes, and if > 30 service classes, IBM > > says WLM can't complete it in time. > > Jerry > > -Original Message- > > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf > > Of Mark Jacobs > > Sent: Tuesday, February 16, 2021 8:17 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: WLM Service Classes > > This message was sent from an external source outside of Western & > > Southern's network. Do not click links or open attachments unless you > > recognize the sender and know the contents are safe. > > I seem to recall that there's a recommendation not to exceed a certain > > number of defined WLM service classes for reasons. Is my recollection > > correct? > > Mark Jacobs > > Sent from ProtonMail, Swiss-based encrypted email. > > GPG Public Key - > > https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com > > > > > For IBM-MAIN subscribe / signoff / archive access instructions, send email > > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > Unless stated otherwise above: > > IBM United Kingdom Limited - Registered in England and Wales with number > > 741598. > > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU > > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM Service Classes
We normally put it this way: Too many ACTIVE service class periods with too little work in each of them makes it difficult for WLM to be helpful. Cheers, Martin Martin Packer Systems Investigator & Performance Troubleshooter, IBM +44-7802-245-584 email: martin_pac...@uk.ibm.com Twitter / Facebook IDs: MartinPacker Blog: https://mainframeperformancetopics.com Mainframe, Performance, Topics Podcast Series (With Marna Walle): https://anchor.fm/marna-walle Youtube channel: https://www.youtube.com/channel/UCu_65HaYgksbF6Q8SQ4oOvA From: "Edgington, Jerry" To: IBM-MAIN@LISTSERV.UA.EDU Date: 16/02/2021 13:21 Subject:[EXTERNAL] Re: WLM Service Classes Sent by:IBM Mainframe Discussion List Mark, IBM recommends < 30 Service Classes. WLM has a limited amount of time to cycle through the WLM service classes, and if > 30 service classes, IBM says WLM can't complete it in time. Jerry -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mark Jacobs Sent: Tuesday, February 16, 2021 8:17 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: WLM Service Classes This message was sent from an external source outside of Western & Southern's network. Do not click links or open attachments unless you recognize the sender and know the contents are safe. I seem to recall that there's a recommendation not to exceed a certain number of defined WLM service classes for *reasons*. Is my recollection correct? Mark Jacobs Sent from [ProtonMail]( https://protonmail.com ), Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: question on enqueues
Few remarks: 1. DISP=SHR does not guarantee the SHR in effect. Actual ENQ can be different. Test: SYSUT2 in IEBGENER step and DISP=SHR - you will see exclusive ENQ. 2. I don't know FDRflash, but tools using DASD Point in Time replication features (Flashcopy, Snapshot, TimeFinder...) can work with no regular ENQ processing. -- Radoslaw Skorupka (looking for new job) Lodz, Poland W dniu 16.02.2021 o 00:37, Pommier, Rex pisze: I have one that's puzzling me and I'm sure there's a simple solution/answer. I'm seeing 2 jobs running on a single system that are hitting an enqueue problem on a parmlib. The JCL in both jobs has DISP=SHR, yet one of the jobs has an exclusive ENQ on the library. Here's the scenario: Job A is a system backup job. It does a bit of early processing, then runs an FDRFlash of most of our disk, then runs FDR to back up the offline volumes created in the flash as well as some volumes that weren't flashed. Once the backup step is done (3 hours later) it does some more post backup processing. There are 3 steps in the post processing that allocate this parmlib, all allocating the same member - call it A.B.C.PARM(MEMB), all with DISP=SHR. Job B is a cyclical job that runs in a matter of a few seconds and runs every 5 minutes. It also has A.B.C.PARM(MEMB) DISP=SHR as well as A.B.C.PARM(MEMZ) DISP=SHR in a different step. Timing: Job A started and was doing its preliminary work. Job B started and ended successfully. Job A does the flash step and starts the full volume dumps. Job B comes along again and can't start because job A has an exclusive ENQ on A.B.C.PARM. Job B does not start until job A has completed the last step with A.B.C.PARM in the JCL. A couple other points are that A.B.C.PARM is on a volume that was flashed, so the source volume wasn't part of the backup. The job steps in both jobs with A.B.C.PARM in them are all conditional steps that actually didn't execute. So my question is what could have caused an ENQ change from SHR to OLD when the JCL explicitly has SHR? TIA, Rex The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM Service Classes
Thanks. Exactly what I was looking for. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Tuesday, February 16th, 2021 at 8:20 AM, Edgington, Jerry wrote: > Mark, > > IBM recommends < 30 Service Classes. WLM has a limited amount of time to > cycle through the WLM service classes, and if > 30 service classes, IBM says > WLM can't complete it in time. > > Jerry > > -Original Message- > > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf Of > Mark Jacobs > > Sent: Tuesday, February 16, 2021 8:17 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: WLM Service Classes > > This message was sent from an external source outside of Western & Southern's > network. Do not click links or open attachments unless you recognize the > sender and know the contents are safe. > > I seem to recall that there's a recommendation not to exceed a certain number > of defined WLM service classes for reasons. Is my recollection correct? > > Mark Jacobs > > Sent from ProtonMail, Swiss-based encrypted email. > > GPG Public Key - > https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com > > > > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > --- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM Service Classes
Mark, IBM recommends < 30 Service Classes. WLM has a limited amount of time to cycle through the WLM service classes, and if > 30 service classes, IBM says WLM can't complete it in time. Jerry -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mark Jacobs Sent: Tuesday, February 16, 2021 8:17 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: WLM Service Classes This message was sent from an external source outside of Western & Southern's network. Do not click links or open attachments unless you recognize the sender and know the contents are safe. I seem to recall that there's a recommendation not to exceed a certain number of defined WLM service classes for *reasons*. Is my recollection correct? Mark Jacobs Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
WLM Service Classes
I seem to recall that there's a recommendation not to exceed a certain number of defined WLM service classes for *reasons*. Is my recollection correct? Mark Jacobs Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
