Re: How to find source of JES2 change
On Fri, 8 Sep 2006 20:01:56 -0400, Robert A. Rosenberg <[EMAIL PROTECTED]> wrote: >At 12:32 -0500 on 09/08/2006, Tom Marchant wrote >about Re: How to find source of JES2 change: > >>On Fri, 8 Sep 2006 12:36:31 -0400, Robert A. Rosenberg <[EMAIL PROTECTED]> >>wrote: >>> >>>Look like an idea for a JES Mod or Feature Enhancement >> >>It *was* an enhancement. So that JES2 would retain modified parameters >> > >The Enhancement I was talking about was NOT the retention of modified >parameters but the reporting of mismatches between the defined (in >the start-up parameters) and the retained parameters that will be >used due to being in the checkpoint dataset. IOW: Report on the >parameters that were overridden by JES2 Commands without >simultaneously updating the Parms (so they are now out of sync). > I agree that it would be a good thing. Submit a requirement. There is already warning messages about mismatches for some of the other (sub) parms where the checkpointed value is used ($HASP496), for example SPOOLDEF, JOBDEF, and OUTDEF. -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group mailto: [EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ 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: How to find source of JES2 change
At 12:32 -0500 on 09/08/2006, =?iso-8859-1?Q?Tom_Marchant?= wrote about Re: How to find source of JES2 change: On Fri, 8 Sep 2006 12:36:31 -0400, Robert A. Rosenberg <[EMAIL PROTECTED]> wrote: Look like an idea for a JES Mod or Feature Enhancement It *was* an enhancement. So that JES2 would retain modified parameters The Enhancement I was talking about was NOT the retention of modified parameters but the reporting of mismatches between the defined (in the start-up parameters) and the retained parameters that will be used due to being in the checkpoint dataset. IOW: Report on the parameters that were overridden by JES2 Commands without simultaneously updating the Parms (so they are now out of sync). -- 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: How to find source of JES2 change
On Fri, 8 Sep 2006 12:36:31 -0400, Robert A. Rosenberg wrote: >At 08:11 -0500 on 09/08/2006, Mark Zelden wrote >about Re: How to find source of JES2 change: > >>Yes, but I would not recommend people just go around and issue this command >>without research. I'm thinking a lot of people are running with JOBCLASS >>parms that have been changed and aren't reflected in the JES2 PARMs (just >>check the archives for similar threads). OS/390 2.4 was a long time ago. > >Look like an idea for a JES Mod or Feature Enhancement - ie: A way of >comparing the JES2 PARMs against the current settings (since the >Parms are ignored except on a COLD START and are not apparently even >checked on an ALL Member WARM Start [although I have the impression >that some are to insure compatibility with the Checkpointed version >of the settings]). Isn't this something that the Health Checker ought to detect? (I'm not a firm believer in the entire Health Checker implementation from IBM, but there are bits and pieces that make sense. This is one.) -- Tom Schmidt Madison, WI (I'm also not a believer in "best practices" since I have seen it used too many times to stifle innovation and growth. The term "your mileage may vary" applies to far more things than mileage in my experience. YMMV, of course.) -- 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: How to find source of JES2 change
On Fri, 8 Sep 2006 12:36:31 -0400, Robert A. Rosenberg <[EMAIL PROTECTED]> wrote: > >Look like an idea for a JES Mod or Feature Enhancement It *was* an enhancement. So that JES2 would retain modified parameters -- 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: How to find source of JES2 change
At 08:11 -0500 on 09/08/2006, =?ISO-8859-1?Q?Mark_Zelden?= wrote about Re: How to find source of JES2 change: Yes, but I would not recommend people just go around and issue this command without research. I'm thinking a lot of people are running with JOBCLASS parms that have been changed and aren't reflected in the JES2 PARMs (just check the archives for similar threads). OS/390 2.4 was a long time ago. Look like an idea for a JES Mod or Feature Enhancement - ie: A way of comparing the JES2 PARMs against the current settings (since the Parms are ignored except on a COLD START and are not apparently even checked on an ALL Member WARM Start [although I have the impression that some are to insure compatibility with the Checkpointed version of the settings]). -- 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: How to find source of JES2 change
> -Original Message- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Jon Brock > Sent: Friday, September 08, 2006 9:14 AM > To: IBM-MAIN@BAMA.UA.EDU > Subject: Re: How to find source of JES2 change > > > That leads to one of my points of curiosity: why did we > make this change? I'm not really concerned about the actual > differing values; we do no chargeback, and I'm not worried > about whether a job is using 70 minutes instead of 60 minutes > of CPU time. (I may become worried about it at some point, > but not yet.) I'm just curious as to why we did it, and also > why the goofball number of 72? I could see 75 or 90, but 72? > > I have looked back a few weeks for the command with no > joy, so I may reload a year's worth or so of syslog and check > it next week. > > Thanks for the responses, folks. You answered my > question, as usual. > > Jon Because 72 is a mystic number? Think about it. It is (2^3)*(3^2). That is the product of the first two prime numbers raised to the other number power. Gotta be mystical! Yes, it is Friday. And I'm weirder that usual due to lack of sleep. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -- 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: How to find source of JES2 change
That leads to one of my points of curiosity: why did we make this change? I'm not really concerned about the actual differing values; we do no chargeback, and I'm not worried about whether a job is using 70 minutes instead of 60 minutes of CPU time. (I may become worried about it at some point, but not yet.) I'm just curious as to why we did it, and also why the goofball number of 72? I could see 75 or 90, but 72? I have looked back a few weeks for the command with no joy, so I may reload a year's worth or so of syslog and check it next week. Thanks for the responses, folks. You answered my question, as usual. Jon Yes, but I would not recommend people just go around and issue this command without research. I'm thinking a lot of people are running with JOBCLASS parms that have been changed and aren't reflected in the JES2 PARMs (just check the archives for similar threads). OS/390 2.4 was a long time ago. -- 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: How to find source of JES2 change
On Fri, 8 Sep 2006 02:15:07 -0500, Bruce Hewson <[EMAIL PROTECTED]> wrote: > >to issue a $TJOBCLASS(?) command. Then active and parmlib will be in synch. > Yes, but I would not recommend people just go around and issue this command without research. I'm thinking a lot of people are running with JOBCLASS parms that have been changed and aren't reflected in the JES2 PARMs (just check the archives for similar threads). OS/390 2.4 was a long time ago. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group mailto: [EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ 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: How to find source of JES2 change
On Thu, 7 Sep 2006 20:56:02 -0500, Tom Marchant <[EMAIL PROTECTED]> wrote: >On Thu, 7 Sep 2006 16:47:59 -0500, Mark Zelden <[EMAIL PROTECTED]> wrote: Is there a way to find out when and how a JOBCLASS definition was changed in JES2?... >>> >>>The only ways that I know of are: (1) the MVS SYSLOG or (2) RACF, if you >>>are auditing the OPERCMDS and who issues them. You'd need to go back to >>>the last IPL. >>> >> >>He'll most likely never find when it was changed as it could have been >>years ago. Since OS/390 2.4 (with a $ACTIVATEd spool) JOBCLASS parms >>are MAS in scope and only changed via cold start or operator command. >> >... and retained in checkpoint across warm starts. And I am not even sure that JES2 will report the mismatch between the JOBCLASS values in checkpoint and parmlib. If you want the TIME value coded in your parmlib to be active you will need to issue a $TJOBCLASS(?) command. Then active and parmlib will be in synch. I just completed a test. JES2 WARM start does not report a change in the TIME parameter. Regards Bruce Hewson -- 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: How to find source of JES2 change
On Thu, 7 Sep 2006 16:47:59 -0500, Mark Zelden <[EMAIL PROTECTED]> wrote: >>> >>> Is there a way to find out when and how a JOBCLASS >>> definition was changed in JES2?... >> >>The only ways that I know of are: (1) the MVS SYSLOG or (2) RACF, if you >>are auditing the OPERCMDS and who issues them. You'd need to go back to >>the last IPL. >> > >He'll most likely never find when it was changed as it could have been >years ago. Since OS/390 2.4 (with a $ACTIVATEd spool) JOBCLASS parms >are MAS in scope and only changed via cold start or operator command. > ... and retained in checkpoint across warm starts. -- 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: How to find source of JES2 change
On Thu, 7 Sep 2006 14:03:12 -0500, McKown, John <[EMAIL PROTECTED]> wrote: >> -Original Message- >> From: IBM Mainframe Discussion List >> [mailto:[EMAIL PROTECTED] On Behalf Of Jon Brock >> Sent: Thursday, September 07, 2006 1:55 PM >> To: IBM-MAIN@BAMA.UA.EDU >> Subject: How to find source of JES2 change >> >> >> Is there a way to find out when and how a JOBCLASS >> definition was changed in JES2? We specify TIME=(0060,00) on >> the JOBCLASS statement for a particular class in our JES2 >> startup parms, but when I issue a $TJOBCLASS(A) from the >> console, the resulting display shows TIME=(72,00). I >> can't find any sort of exit that would be changing the >> default, nor is there any sort of automatic command that >> would be doing it. All I can think is that sometime in the >> past someone issued a $TJOBCLASS command to change the time >> limit and it has been carried through the subsequent warm starts. >> This isn't a major deal, but my curiosity is up. >> >> >> Thanks, >> Jon > >The only ways that I know of are: (1) the MVS SYSLOG or (2) RACF, if you >are auditing the OPERCMDS and who issues them. You'd need to go back to >the last IPL. > He'll most likely never find when it was changed as it could have been years ago. Since OS/390 2.4 (with a $ACTIVATEd spool) JOBCLASS parms are MAS in scope and only changed via cold start or operator command. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group mailto: [EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ 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: How to find source of JES2 change
>SMF record cut by JES maybe? Don't know if JES does this or not, just >throwing it out there. Try checking before throwing. SMF doesn't audit JES2 commands except through auditing OPERCMDS under RACF. When in doubt. PANIC!! -- 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: How to find source of JES2 change
>All I can think is that sometime in the past someone issued a $TJOBCLASS >command to change the time limit and it has been carried through the >subsequent warm starts. SYSLOG is your friend. There are CBT tools that do searches. The issue is how much SYSLOG you keep. When in doubt. PANIC!! -- 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: How to find source of JES2 change
On Thu, 7 Sep 2006 14:55:23 -0400, Jon Brock <[EMAIL PROTECTED]> wrote: > Is there a way to find out when and how a JOBCLASS definition was changed in JES2? We specify TIME=(0060,00) on the JOBCLASS statement for a particular class in our JES2 startup parms, but when I issue a $TJOBCLASS (A) from the console, the resulting display shows TIME=(72,00). I can't find any sort of exit that would be changing the default, nor is there any sort of automatic command that would be doing it. All I can think is that sometime in the past someone issued a $TJOBCLASS command to change the time limit and it has been carried through the subsequent warm starts. > This isn't a major deal, but my curiosity is up. > > >Thanks, >Jon > SMF record cut by JES maybe? Don't know if JES does this or not, just throwing it out there. -- 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: How to find source of JES2 change
Syslog(?). I just altered our JOBCLASS(A) on our tech LPAR through SDSF and it shows up like any other JES message on the log. Gives the TSU number and the ID with the time stamp. Jon Brock <[EMAIL PROTECTED]> Sent by: IBM Mainframe Discussion List 09/07/2006 02:55 PM Please respond to IBM Mainframe Discussion List To IBM-MAIN@BAMA.UA.EDU cc Subject How to find source of JES2 change Is there a way to find out when and how a JOBCLASS definition was changed in JES2? We specify TIME=(0060,00) on the JOBCLASS statement for a particular class in our JES2 startup parms, but when I issue a $TJOBCLASS(A) from the console, the resulting display shows TIME=(72,00). I can't find any sort of exit that would be changing the default, nor is there any sort of automatic command that would be doing it. All I can think is that sometime in the past someone issued a $TJOBCLASS command to change the time limit and it has been carried through the subsequent warm starts. This isn't a major deal, but my curiosity is up. Thanks, Jon -- 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: How to find source of JES2 change
> -Original Message- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Jon Brock > Sent: Thursday, September 07, 2006 1:55 PM > To: IBM-MAIN@BAMA.UA.EDU > Subject: How to find source of JES2 change > > > Is there a way to find out when and how a JOBCLASS > definition was changed in JES2? We specify TIME=(0060,00) on > the JOBCLASS statement for a particular class in our JES2 > startup parms, but when I issue a $TJOBCLASS(A) from the > console, the resulting display shows TIME=(72,00). I > can't find any sort of exit that would be changing the > default, nor is there any sort of automatic command that > would be doing it. All I can think is that sometime in the > past someone issued a $TJOBCLASS command to change the time > limit and it has been carried through the subsequent warm starts. > This isn't a major deal, but my curiosity is up. > > > Thanks, > Jon The only ways that I know of are: (1) the MVS SYSLOG or (2) RACF, if you are auditing the OPERCMDS and who issues them. You'd need to go back to the last IPL. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -- 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
How to find source of JES2 change
Is there a way to find out when and how a JOBCLASS definition was changed in JES2? We specify TIME=(0060,00) on the JOBCLASS statement for a particular class in our JES2 startup parms, but when I issue a $TJOBCLASS(A) from the console, the resulting display shows TIME=(72,00). I can't find any sort of exit that would be changing the default, nor is there any sort of automatic command that would be doing it. All I can think is that sometime in the past someone issued a $TJOBCLASS command to change the time limit and it has been carried through the subsequent warm starts. This isn't a major deal, but my curiosity is up. Thanks, Jon -- 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
