Re: Control block values that exempt 522 Timeouts
Somehow I deleted the text of my reply. The significance of 1440 has nothing to do with the clock cycle; it's the number of minutes in a day. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Lindy Mayfield Sent: Thursday, September 26, 2019 10:53 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Control block values that exempt 522 Timeouts It could have been hardware related based on clock speed on early machines. Perhaps it's more appropriate ask this on the RACF group. /Lindy -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mike Schwab Sent: tiistai 17. syyskuuta 2019 18.35 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Control block values that exempt 522 Timeouts EXTERNAL Well, if that represents 24 hours then 2555 is 1 second. On Tue, Sep 17, 2019 at 8:09 AM Lindy Mayfield wrote: > > Hi, > > I understand that address spaces can be made exempt from 522 timeouts if > there is a particular value in one of three control blocks. If I have it > correct they are: > > 1) The JSTL is 86400 seconds (Comes from TIME=1440 on Job card?) > 2) The ASCBTOFF bit in the ASCBRCTF is set > 3) The SWTL contains the magic number x'0D286880' > > What can I learn from one or more of those values being set? For example, > which z/OS or application components update those control blocks or cause > them to be updated? > > Thanks in advance for any insight! > > Kind regards, > Lindy > > P.S. I think I asked some years ago where they magic number x'0D286880' > comes from. I forgot. I think it was historical, and maybe counted in > timerons or something similar. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- 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: Control block values that exempt 522 Timeouts
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Lindy Mayfield Sent: Thursday, September 26, 2019 10:53 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Control block values that exempt 522 Timeouts It could have been hardware related based on clock speed on early machines. Perhaps it's more appropriate ask this on the RACF group. /Lindy -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mike Schwab Sent: tiistai 17. syyskuuta 2019 18.35 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Control block values that exempt 522 Timeouts EXTERNAL Well, if that represents 24 hours then 2555 is 1 second. On Tue, Sep 17, 2019 at 8:09 AM Lindy Mayfield wrote: > > Hi, > > I understand that address spaces can be made exempt from 522 timeouts if > there is a particular value in one of three control blocks. If I have it > correct they are: > > 1) The JSTL is 86400 seconds (Comes from TIME=1440 on Job card?) > 2) The ASCBTOFF bit in the ASCBRCTF is set > 3) The SWTL contains the magic number x'0D286880' > > What can I learn from one or more of those values being set? For example, > which z/OS or application components update those control blocks or cause > them to be updated? > > Thanks in advance for any insight! > > Kind regards, > Lindy > > P.S. I think I asked some years ago where they magic number x'0D286880' > comes from. I forgot. I think it was historical, and maybe counted in > timerons or something similar. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN 1440 has nothing to do with clock speed. 1440 = 60 * 24. -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- 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: Control block values that exempt 522 Timeouts
I found the old post! I think it has most what I need. I didn't find it before, but now I did, I should have looked harder, mea culpa. /lindy -Original Message- From: IBM Mainframe Discussion List On Behalf Of Massimo Biancucci Sent: torstai 26. syyskuuta 2019 18.05 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Control block values that exempt 522 Timeouts EXTERNAL Hi, I think you gave the main answer TIME=1440 (or NOLIMIT) on JCL. AFAIK, there're monitor product (like BMC SYSPROG Services for instance) that can update the value on the fly. Regards. Max Il giorno mar 17 set 2019 alle ore 15:09 Lindy Mayfield < lindy.mayfi...@sas.com> ha scritto: > Hi, > > I understand that address spaces can be made exempt from 522 timeouts > if there is a particular value in one of three control blocks. If I > have it correct they are: > > 1) The JSTL is 86400 seconds (Comes from TIME=1440 on Job card?) > 2) The ASCBTOFF bit in the ASCBRCTF is set > 3) The SWTL contains the magic number x'0D286880' > > What can I learn from one or more of those values being set? For > example, which z/OS or application components update those control > blocks or cause them to be updated? > > Thanks in advance for any insight! > > Kind regards, > Lindy > > P.S. I think I asked some years ago where they magic number x'0D286880' > comes from. I forgot. I think it was historical, and maybe counted in > timerons or something similar. > > -- > 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: Control block values that exempt 522 Timeouts
Not funny. ☹ -Original Message- From: IBM Mainframe Discussion List On Behalf Of Steve Beaver Sent: torstai 26. syyskuuta 2019 18.05 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Control block values that exempt 522 Timeouts EXTERNAL Talk to your MVS people -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lindy Mayfield Sent: Thursday, September 26, 2019 9:54 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Control block values that exempt 522 Timeouts It could have been hardware related based on clock speed on early machines. Perhaps it's more appropriate ask this on the RACF group. /Lindy -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mike Schwab Sent: tiistai 17. syyskuuta 2019 18.35 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Control block values that exempt 522 Timeouts EXTERNAL Well, if that represents 24 hours then 2555 is 1 second. On Tue, Sep 17, 2019 at 8:09 AM Lindy Mayfield wrote: > > Hi, > > I understand that address spaces can be made exempt from 522 timeouts if > there is a particular value in one of three control blocks. If I have it > correct they are: > > 1) The JSTL is 86400 seconds (Comes from TIME=1440 on Job card?) > 2) The ASCBTOFF bit in the ASCBRCTF is set > 3) The SWTL contains the magic number x'0D286880' > > What can I learn from one or more of those values being set? For example, > which z/OS or application components update those control blocks or cause > them to be updated? > > Thanks in advance for any insight! > > Kind regards, > Lindy > > P.S. I think I asked some years ago where they magic number x'0D286880' > comes from. I forgot. I think it was historical, and maybe counted in > timerons or something similar. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Control block values that exempt 522 Timeouts
Hi, I think you gave the main answer TIME=1440 (or NOLIMIT) on JCL. AFAIK, there're monitor product (like BMC SYSPROG Services for instance) that can update the value on the fly. Regards. Max Il giorno mar 17 set 2019 alle ore 15:09 Lindy Mayfield < lindy.mayfi...@sas.com> ha scritto: > Hi, > > I understand that address spaces can be made exempt from 522 timeouts if > there is a particular value in one of three control blocks. If I have it > correct they are: > > 1) The JSTL is 86400 seconds (Comes from TIME=1440 on Job card?) > 2) The ASCBTOFF bit in the ASCBRCTF is set > 3) The SWTL contains the magic number x'0D286880' > > What can I learn from one or more of those values being set? For example, > which z/OS or application components update those control blocks or cause > them to be updated? > > Thanks in advance for any insight! > > Kind regards, > Lindy > > P.S. I think I asked some years ago where they magic number x'0D286880' > comes from. I forgot. I think it was historical, and maybe counted in > timerons or something similar. > > -- > 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: Control block values that exempt 522 Timeouts
Talk to your MVS people -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lindy Mayfield Sent: Thursday, September 26, 2019 9:54 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Control block values that exempt 522 Timeouts It could have been hardware related based on clock speed on early machines. Perhaps it's more appropriate ask this on the RACF group. /Lindy -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mike Schwab Sent: tiistai 17. syyskuuta 2019 18.35 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Control block values that exempt 522 Timeouts EXTERNAL Well, if that represents 24 hours then 2555 is 1 second. On Tue, Sep 17, 2019 at 8:09 AM Lindy Mayfield wrote: > > Hi, > > I understand that address spaces can be made exempt from 522 timeouts if > there is a particular value in one of three control blocks. If I have it > correct they are: > > 1) The JSTL is 86400 seconds (Comes from TIME=1440 on Job card?) > 2) The ASCBTOFF bit in the ASCBRCTF is set > 3) The SWTL contains the magic number x'0D286880' > > What can I learn from one or more of those values being set? For example, > which z/OS or application components update those control blocks or cause > them to be updated? > > Thanks in advance for any insight! > > Kind regards, > Lindy > > P.S. I think I asked some years ago where they magic number x'0D286880' > comes from. I forgot. I think it was historical, and maybe counted in > timerons or something similar. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- 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: Control block values that exempt 522 Timeouts
It could have been hardware related based on clock speed on early machines. Perhaps it's more appropriate ask this on the RACF group. /Lindy -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mike Schwab Sent: tiistai 17. syyskuuta 2019 18.35 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Control block values that exempt 522 Timeouts EXTERNAL Well, if that represents 24 hours then 2555 is 1 second. On Tue, Sep 17, 2019 at 8:09 AM Lindy Mayfield wrote: > > Hi, > > I understand that address spaces can be made exempt from 522 timeouts if > there is a particular value in one of three control blocks. If I have it > correct they are: > > 1) The JSTL is 86400 seconds (Comes from TIME=1440 on Job card?) > 2) The ASCBTOFF bit in the ASCBRCTF is set > 3) The SWTL contains the magic number x'0D286880' > > What can I learn from one or more of those values being set? For example, > which z/OS or application components update those control blocks or cause > them to be updated? > > Thanks in advance for any insight! > > Kind regards, > Lindy > > P.S. I think I asked some years ago where they magic number x'0D286880' > comes from. I forgot. I think it was historical, and maybe counted in > timerons or something similar. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- 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: Control block values that exempt 522 Timeouts
Well, if that represents 24 hours then 2555 is 1 second. On Tue, Sep 17, 2019 at 8:09 AM Lindy Mayfield wrote: > > Hi, > > I understand that address spaces can be made exempt from 522 timeouts if > there is a particular value in one of three control blocks. If I have it > correct they are: > > 1) The JSTL is 86400 seconds (Comes from TIME=1440 on Job card?) > 2) The ASCBTOFF bit in the ASCBRCTF is set > 3) The SWTL contains the magic number x'0D286880' > > What can I learn from one or more of those values being set? For example, > which z/OS or application components update those control blocks or cause > them to be updated? > > Thanks in advance for any insight! > > Kind regards, > Lindy > > P.S. I think I asked some years ago where they magic number x'0D286880' > comes from. I forgot. I think it was historical, and maybe counted in > timerons or something similar. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Control block values that exempt 522 Timeouts
Hi, I understand that address spaces can be made exempt from 522 timeouts if there is a particular value in one of three control blocks. If I have it correct they are: 1) The JSTL is 86400 seconds (Comes from TIME=1440 on Job card?) 2) The ASCBTOFF bit in the ASCBRCTF is set 3) The SWTL contains the magic number x'0D286880' What can I learn from one or more of those values being set? For example, which z/OS or application components update those control blocks or cause them to be updated? Thanks in advance for any insight! Kind regards, Lindy P.S. I think I asked some years ago where they magic number x'0D286880' comes from. I forgot. I think it was historical, and maybe counted in timerons or something similar. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
