Re: Users of a hfs file
zlsof https://www.ibm.com/docs/en/zos/2.2.0?topic=scd-zlsof-displays-information-about-open-files-sockets-pipes > On 20 May 2021, at 6:37 pm, Joe Owens wrote: > > Is it possible to determine, without trying to unmount a file, which > processes are using resources below that point in the hierachy, and would > prevent an unmount from completing, then relate this back to jobs, stcs, or > TSO users? > > Regards, Joe > > -- > 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: Best catch up resources for MVS / ZOS Technologies
In some cases individual instuctions can't be directly replaced but code sequences can. IAC, for someone who precedes z, a look at the current PoOps can be an eye opener. I know that the mantra is "Those new instructions are just for compilers.", but some of them warm the cockles of this old assembler programmer's heart. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Mike Schwab [mike.a.sch...@gmail.com] Sent: Thursday, May 20, 2021 7:11 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Best catch up resources for MVS / ZOS Technologies Since they drop the register addressing with PSW relative addressing they execute faster. Does somebody have a list of S/370 instructions with possible XA/ESA/Z replacements that can directly replaced? On Thu, May 20, 2021 at 11:47 AM Charles Mills wrote: > > If you are a significant coder or maintainer of assembler code, one big > improvement that IIRC no one has mentioned is the relaxation of the base > register nightmare. You know, where you go to make a one-minute change to > some code and you kick it over the 4K boundary and you are faced with three > unappealing choices: commit another register to be an additional base, split > the module in half, or figure out some hack that gets some big data area out > of the basic 4K range. > > The solution is the relatively (ha ha) new branch relative instructions, > commonly referred to as jumps due to their Jxx mnemonics -- plus some other > "relative" instructions such as LARL. A full tutorial is out of scope for a > mailing list e-mail, but the classics comics version is that you replace all > of the Bxx instructions with Jxx, move your data areas to the beginning of > the CSECT with LOCTR, and your 4K base register issues should go away, pretty > much for good. > > Charles > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Steve Estle > Sent: Monday, May 17, 2021 6:42 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Best catch up resources for MVS / ZOS Technologies > > Hello Everyone in Mainframe Land, > > I've been out of the mainframe world since about 2001, but spent the prior 20 > years immersed in that world working with everything from MVS/370 to MVS/ESA > and VM, performance and capacity planning disciplines across a variety of > situations in the IT Services and consulting spaces. I, am, now as a "IT > Infrastructure Engineer- IBM z/OS Mainframe Engineer" after nearly 20 years > of other activities (Project Mgmt, entrepreneur, etc) am about to potentially > come back into a new mainframe role and I need to catch up as quickly as > possible. Any suggestions on ways to fill in the gaps for ZOS, ZVM, > hardware, performance, etc? Bottom line I'm looking for that gap education > to as quickly as possible get up to speed with changes in platforms since > 2001. If prefer to call - all my info is below. > > -- > 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: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies
Yep. Digital Research had a contract with all their prior customers. If they cut the price for a new customer, they change the price and REFUND the difference on all previous sales. On Thu, May 20, 2021 at 11:47 AM Seymour J Metz wrote: > > Admittedly DR-C was a sin for which there is no forgiveness, but my > understanding is that the IBM-DR negotiations foundered on the issue of > contract terms, and IBM gave away the farm with m$. > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > > > From: IBM Mainframe Discussion List on behalf of > Charles Mills > Sent: Thursday, May 20, 2021 11:38 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for > MVS / ZOS Technologies > > Digital Research was certainly an accomplice in its own strangulation. > > Charles > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Seymour J Metz > Sent: Thursday, May 20, 2021 8:07 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources > for MVS / ZOS Technologies > > Stuck to DR-DOS? We would have all been better off had m$ not taken over the > PC OS market and used the monopoly to strangle its competitors. > > SMB? Doesn't NFS play better with the *ix world? > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > > > From: IBM Mainframe Discussion List on behalf of > Pommier, Rex > Sent: Thursday, May 20, 2021 10:37 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources > for MVS / ZOS Technologies > > Sorry Chris, > > But I would venture a guess that you're pretty much standing alone here. > The "if it ain't broke don't fix it" otherwise known as "if it's good enough > for me it should be good enough for everybody else" attitude is what has us > on a slowly dying platform. So what if IF/THEN doesn't handle all the > arcane COND= Boolean logic? Sysprogs aren't the only people using JCL. If > I can easily train an application developer or an implementation analyst on > the use of IF/THEN once and have them go away and build their own JCL > without needing my continual assistance to help them understand COND= logic, > it is a win-win situation. I would bet every sysprogs on this list has > horror stories of having to fix somebody's COND= screw-up. > > It's actually quite enjoyable having a developer come to me puzzled about > COND=something and be able to say "Here, use this IF/THEN JCL logic > instead", and see the light come on in their eyes. > > But then, if PCs would have stuck with DR-DOS the mainframe would still be a > more major player in the SMB business arena. > > Rex > > -Original Message- > From: IBM Mainframe Discussion List On Behalf Of > CM Poncelet > Sent: Wednesday, May 19, 2021 8:50 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [External] Re: JCL COND vs IF/THEN - Best catch up resources for > MVS / ZOS Technologies > > Again and with all due respect, progress is made not by blunting the tool > but by sharpening the user. > > "IF/THEN" does not handle all boolean AND/OR/NAND/XOR and steps-not-executed > conditions. > > Let not those who cannot master playing the violin demand that the violin be > made more easy, but let them try playing the banjo instead. > > And SMP/E? In the 1980's it was 'recommended' to use its dialogs. In the > late 90's, its Custom-Pak etc. became 'de rigueur' and 'de facto'. And yet I > continued to use only native SMP/E - and did so daily to track down and fix > PTFEs etc. etc. > > Who gains from this progressive and continual stultification of mainframe > systems programming? Is it not Windows for mainframes? > > As they say, "Use it or lose it." > > Cheers, Chris Poncelet (r) > > > > On 19/05/2021 01:55, Nash, Jonathan S. wrote: > > Once I learned of the IF/THEN statements for JCL I never used COND= > > again. IF/THEN is much easier to use and to explain to new people. > > I have seen many people code COND statements incorrectly because they > > did not acually understand how they worked. > > > > > > -Original Message- > > From: IBM Mainframe Discussion List On > > Behalf Of CM Poncelet > > Sent: Tuesday, May 18, 2021 8:19 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: [EXTERNAL] Re: Best catch up resources for MVS / ZOS > > Technologies > > > > With all due respect, anyone who has difficulty coding JCL COND= > > statements should consider *not* working with IBM mainframe systems. > > > > All boolean conditional execution steps can be handled using only > > COND= statements. I submitted a paper on this & it was published in > > "Computing" in 1989. I would but cannot attach it, as uploading PDF > > files to this discussion list is not permitted. > > > > No sysprog worth his salt has ever had a problem with
Re: Best catch up resources for MVS / ZOS Technologies
Since they drop the register addressing with PSW relative addressing they execute faster. Does somebody have a list of S/370 instructions with possible XA/ESA/Z replacements that can directly replaced? On Thu, May 20, 2021 at 11:47 AM Charles Mills wrote: > > If you are a significant coder or maintainer of assembler code, one big > improvement that IIRC no one has mentioned is the relaxation of the base > register nightmare. You know, where you go to make a one-minute change to > some code and you kick it over the 4K boundary and you are faced with three > unappealing choices: commit another register to be an additional base, split > the module in half, or figure out some hack that gets some big data area out > of the basic 4K range. > > The solution is the relatively (ha ha) new branch relative instructions, > commonly referred to as jumps due to their Jxx mnemonics -- plus some other > "relative" instructions such as LARL. A full tutorial is out of scope for a > mailing list e-mail, but the classics comics version is that you replace all > of the Bxx instructions with Jxx, move your data areas to the beginning of > the CSECT with LOCTR, and your 4K base register issues should go away, pretty > much for good. > > Charles > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Steve Estle > Sent: Monday, May 17, 2021 6:42 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Best catch up resources for MVS / ZOS Technologies > > Hello Everyone in Mainframe Land, > > I've been out of the mainframe world since about 2001, but spent the prior 20 > years immersed in that world working with everything from MVS/370 to MVS/ESA > and VM, performance and capacity planning disciplines across a variety of > situations in the IT Services and consulting spaces. I, am, now as a "IT > Infrastructure Engineer- IBM z/OS Mainframe Engineer" after nearly 20 years > of other activities (Project Mgmt, entrepreneur, etc) am about to potentially > come back into a new mainframe role and I need to catch up as quickly as > possible. Any suggestions on ways to fill in the gaps for ZOS, ZVM, > hardware, performance, etc? Bottom line I'm looking for that gap education > to as quickly as possible get up to speed with changes in platforms since > 2001. If prefer to call - all my info is below. > > -- > 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
Re: OMVS user.hfs shared
I should have clarified, we do have sysplex /etc, /var and /log. have no idea why it was set up that way all those years ago I can see that if I created a sysplex /home things will be well :) thanks for the help -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: OMVS user.hfs shared
aha. I will take this offline but for clarity-I had noticed recently that we do not have a sysplex root... Thanks David -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: OMVS user.hfs shared
>Of course I'm missing something... >If I'm getting contention on the USER.HFS (because it's shared in the sysplex) >why does it matter what directory it's in? >/u or /home it's still the same file I think you said you have /u as part of your IBM root file system. You also said you have one system at 1.13, and one at V2.?. So that indicates to separate root filesystems. if both of them have /u in it, and you try to mount the file system at both locations, it fails. you cannot mount the same file system 2 different places in the directory tree. If indeed /u is in your IBM root filesystem, then the absolute path would be something like /root1/u/whatever and the other would be /root2/u/whatever. you can verify that by doing a df -vk /u in both locations and see what you get. My suggestion was to move your home directory to a single shared /home that is based in the highest level of sysplex root, not z/OS root. If I have misunderstood your situation, please feel free to take this offline with me if you wish. david.jou...@53.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: OMVS user.hfs shared
Of course I'm missing something... If I'm getting contention on the USER.HFS (because it's shared in the sysplex) why does it matter what directory it's in? /u or /home it's still the same file -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies
Sorry, my mind was in the gutter. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Pommier, Rex Sent: Thursday, May 20, 2021 11:46 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Shmuel, By SMB I meant small and medium business, not server message block or whatever Micro$oft meant by it. Rex -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Thursday, May 20, 2021 8:07 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Stuck to DR-DOS? We would have all been better off had m$ not taken over the PC OS market and used the monopoly to strangle its competitors. SMB? Doesn't NFS play better with the *ix world? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Pommier, Rex Sent: Thursday, May 20, 2021 10:37 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Sorry Chris, But I would venture a guess that you're pretty much standing alone here. The "if it ain't broke don't fix it" otherwise known as "if it's good enough for me it should be good enough for everybody else" attitude is what has us on a slowly dying platform. So what if IF/THEN doesn't handle all the arcane COND= Boolean logic? Sysprogs aren't the only people using JCL. If I can easily train an application developer or an implementation analyst on the use of IF/THEN once and have them go away and build their own JCL without needing my continual assistance to help them understand COND= logic, it is a win-win situation. I would bet every sysprogs on this list has horror stories of having to fix somebody's COND= screw-up. It's actually quite enjoyable having a developer come to me puzzled about COND=something and be able to say "Here, use this IF/THEN JCL logic instead", and see the light come on in their eyes. But then, if PCs would have stuck with DR-DOS the mainframe would still be a more major player in the SMB business arena. Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of CM Poncelet Sent: Wednesday, May 19, 2021 8:50 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Again and with all due respect, progress is made not by blunting the tool but by sharpening the user. "IF/THEN" does not handle all boolean AND/OR/NAND/XOR and steps-not-executed conditions. Let not those who cannot master playing the violin demand that the violin be made more easy, but let them try playing the banjo instead. And SMP/E? In the 1980's it was 'recommended' to use its dialogs. In the late 90's, its Custom-Pak etc. became 'de rigueur' and 'de facto'. And yet I continued to use only native SMP/E - and did so daily to track down and fix PTFEs etc. etc. Who gains from this progressive and continual stultification of mainframe systems programming? Is it not Windows for mainframes? As they say, "Use it or lose it." Cheers, Chris Poncelet (r) On 19/05/2021 01:55, Nash, Jonathan S. wrote: > Once I learned of the IF/THEN statements for JCL I never used COND= > again. IF/THEN is much easier to use and to explain to new people. > I have seen many people code COND statements incorrectly because they > did not acually understand how they worked. > > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of CM Poncelet > Sent: Tuesday, May 18, 2021 8:19 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [EXTERNAL] Re: Best catch up resources for MVS / ZOS > Technologies > > With all due respect, anyone who has difficulty coding JCL COND= > statements should consider *not* working with IBM mainframe systems. > > All boolean conditional execution steps can be handled using only > COND= statements. I submitted a paper on this & it was published in > "Computing" in 1989. I would but cannot attach it, as uploading PDF > files to this discussion list is not permitted. > > No sysprog worth his salt has ever had a problem with coding JCL COND= > statements. > > Likewise IF/THEN statements belong in "JCL for dummies" - as do > symbols in JCL and SYSIN. Ditto IF/THEN in assembler. > > Chris Poncelet (r) > > > . > On 18/05/2021 14:02, Charles Mills wrote: >> Yeah, and IF/THEN is slightly better than COND= >> >> Also symbols in SYSIN data. >> >> Charles >> >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >> On Behalf Of Steve Horein >> Sent: Tuesday, May 18, 2021 5:35 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: Best catch up resources for MVS /
Re: Best catch up resources for MVS / ZOS Technologies
There have been a lot of useful changes in the z architecture besides the relative and long displacement instructions. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Charles Mills Sent: Thursday, May 20, 2021 12:46 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Best catch up resources for MVS / ZOS Technologies If you are a significant coder or maintainer of assembler code, one big improvement that IIRC no one has mentioned is the relaxation of the base register nightmare. You know, where you go to make a one-minute change to some code and you kick it over the 4K boundary and you are faced with three unappealing choices: commit another register to be an additional base, split the module in half, or figure out some hack that gets some big data area out of the basic 4K range. The solution is the relatively (ha ha) new branch relative instructions, commonly referred to as jumps due to their Jxx mnemonics -- plus some other "relative" instructions such as LARL. A full tutorial is out of scope for a mailing list e-mail, but the classics comics version is that you replace all of the Bxx instructions with Jxx, move your data areas to the beginning of the CSECT with LOCTR, and your 4K base register issues should go away, pretty much for good. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Estle Sent: Monday, May 17, 2021 6:42 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Best catch up resources for MVS / ZOS Technologies Hello Everyone in Mainframe Land, I've been out of the mainframe world since about 2001, but spent the prior 20 years immersed in that world working with everything from MVS/370 to MVS/ESA and VM, performance and capacity planning disciplines across a variety of situations in the IT Services and consulting spaces. I, am, now as a "IT Infrastructure Engineer- IBM z/OS Mainframe Engineer" after nearly 20 years of other activities (Project Mgmt, entrepreneur, etc) am about to potentially come back into a new mainframe role and I need to catch up as quickly as possible. Any suggestions on ways to fill in the gaps for ZOS, ZVM, hardware, performance, etc? Bottom line I'm looking for that gap education to as quickly as possible get up to speed with changes in platforms since 2001. If prefer to call - all my info is below. -- 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: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies
Admittedly DR-C was a sin for which there is no forgiveness, but my understanding is that the IBM-DR negotiations foundered on the issue of contract terms, and IBM gave away the farm with m$. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Charles Mills Sent: Thursday, May 20, 2021 11:38 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Digital Research was certainly an accomplice in its own strangulation. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Thursday, May 20, 2021 8:07 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Stuck to DR-DOS? We would have all been better off had m$ not taken over the PC OS market and used the monopoly to strangle its competitors. SMB? Doesn't NFS play better with the *ix world? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Pommier, Rex Sent: Thursday, May 20, 2021 10:37 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Sorry Chris, But I would venture a guess that you're pretty much standing alone here. The "if it ain't broke don't fix it" otherwise known as "if it's good enough for me it should be good enough for everybody else" attitude is what has us on a slowly dying platform. So what if IF/THEN doesn't handle all the arcane COND= Boolean logic? Sysprogs aren't the only people using JCL. If I can easily train an application developer or an implementation analyst on the use of IF/THEN once and have them go away and build their own JCL without needing my continual assistance to help them understand COND= logic, it is a win-win situation. I would bet every sysprogs on this list has horror stories of having to fix somebody's COND= screw-up. It's actually quite enjoyable having a developer come to me puzzled about COND=something and be able to say "Here, use this IF/THEN JCL logic instead", and see the light come on in their eyes. But then, if PCs would have stuck with DR-DOS the mainframe would still be a more major player in the SMB business arena. Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of CM Poncelet Sent: Wednesday, May 19, 2021 8:50 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Again and with all due respect, progress is made not by blunting the tool but by sharpening the user. "IF/THEN" does not handle all boolean AND/OR/NAND/XOR and steps-not-executed conditions. Let not those who cannot master playing the violin demand that the violin be made more easy, but let them try playing the banjo instead. And SMP/E? In the 1980's it was 'recommended' to use its dialogs. In the late 90's, its Custom-Pak etc. became 'de rigueur' and 'de facto'. And yet I continued to use only native SMP/E - and did so daily to track down and fix PTFEs etc. etc. Who gains from this progressive and continual stultification of mainframe systems programming? Is it not Windows for mainframes? As they say, "Use it or lose it." Cheers, Chris Poncelet (r) On 19/05/2021 01:55, Nash, Jonathan S. wrote: > Once I learned of the IF/THEN statements for JCL I never used COND= > again. IF/THEN is much easier to use and to explain to new people. > I have seen many people code COND statements incorrectly because they > did not acually understand how they worked. > > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of CM Poncelet > Sent: Tuesday, May 18, 2021 8:19 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [EXTERNAL] Re: Best catch up resources for MVS / ZOS > Technologies > > With all due respect, anyone who has difficulty coding JCL COND= > statements should consider *not* working with IBM mainframe systems. > > All boolean conditional execution steps can be handled using only > COND= statements. I submitted a paper on this & it was published in > "Computing" in 1989. I would but cannot attach it, as uploading PDF > files to this discussion list is not permitted. > > No sysprog worth his salt has ever had a problem with coding JCL COND= > statements. > > Likewise IF/THEN statements belong in "JCL for dummies" - as do > symbols in JCL and SYSIN. Ditto IF/THEN in assembler. > > Chris Poncelet (r) > > > . > On 18/05/2021 14:02, Charles Mills wrote: >> Yeah, and IF/THEN is slightly better than COND= >> >> Also symbols in SYSIN data. >> >> Charles >> >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >> On Behalf Of Steve Horein
Re: Best catch up resources for MVS / ZOS Technologies
If you are a significant coder or maintainer of assembler code, one big improvement that IIRC no one has mentioned is the relaxation of the base register nightmare. You know, where you go to make a one-minute change to some code and you kick it over the 4K boundary and you are faced with three unappealing choices: commit another register to be an additional base, split the module in half, or figure out some hack that gets some big data area out of the basic 4K range. The solution is the relatively (ha ha) new branch relative instructions, commonly referred to as jumps due to their Jxx mnemonics -- plus some other "relative" instructions such as LARL. A full tutorial is out of scope for a mailing list e-mail, but the classics comics version is that you replace all of the Bxx instructions with Jxx, move your data areas to the beginning of the CSECT with LOCTR, and your 4K base register issues should go away, pretty much for good. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Estle Sent: Monday, May 17, 2021 6:42 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Best catch up resources for MVS / ZOS Technologies Hello Everyone in Mainframe Land, I've been out of the mainframe world since about 2001, but spent the prior 20 years immersed in that world working with everything from MVS/370 to MVS/ESA and VM, performance and capacity planning disciplines across a variety of situations in the IT Services and consulting spaces. I, am, now as a "IT Infrastructure Engineer- IBM z/OS Mainframe Engineer" after nearly 20 years of other activities (Project Mgmt, entrepreneur, etc) am about to potentially come back into a new mainframe role and I need to catch up as quickly as possible. Any suggestions on ways to fill in the gaps for ZOS, ZVM, hardware, performance, etc? Bottom line I'm looking for that gap education to as quickly as possible get up to speed with changes in platforms since 2001. If prefer to call - all my info is below. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: OMVS user.hfs shared
On Thu, 20 May 2021 10:39:20 -0500, Dave Jousma wrote: >Elaine, > >you cannot have the same filesystem mounted twice(or more) in different spots >in the directory tree in sysplex filesystem. > Blessedly, the rules are different for NFS because the server handles integrity. I usefully mounted my Solaris home directory concurrently twice, once BINARY; once with EBCDIC translation. But the HFS mount map option UPPERCASE-NAME invites denial-of-service. I might ( cd /u/FooBar ) and FOOBAR's home would remain mounted there for a time and FOOBAR couldn't access it mapped as /u/foobar. IBM addressed this with a mode that required the mountpoint to be entirely lower case. I thought that ASIS-NAME with DISABLE(DSNCHECK) would have been a better approach. > ... As mentioned before, you really dont want to define user home directories > in the root filesystem supplied by IBM. What we have done is created a > automount managed directory in the sysplex root called /home that all user > filesystems get mounted off from.Then from any system in the sysplex, the > user is accessing the same filesystem from all systems. -- 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: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies
Shmuel, By SMB I meant small and medium business, not server message block or whatever Micro$oft meant by it. Rex -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Thursday, May 20, 2021 8:07 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Stuck to DR-DOS? We would have all been better off had m$ not taken over the PC OS market and used the monopoly to strangle its competitors. SMB? Doesn't NFS play better with the *ix world? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Pommier, Rex Sent: Thursday, May 20, 2021 10:37 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Sorry Chris, But I would venture a guess that you're pretty much standing alone here. The "if it ain't broke don't fix it" otherwise known as "if it's good enough for me it should be good enough for everybody else" attitude is what has us on a slowly dying platform. So what if IF/THEN doesn't handle all the arcane COND= Boolean logic? Sysprogs aren't the only people using JCL. If I can easily train an application developer or an implementation analyst on the use of IF/THEN once and have them go away and build their own JCL without needing my continual assistance to help them understand COND= logic, it is a win-win situation. I would bet every sysprogs on this list has horror stories of having to fix somebody's COND= screw-up. It's actually quite enjoyable having a developer come to me puzzled about COND=something and be able to say "Here, use this IF/THEN JCL logic instead", and see the light come on in their eyes. But then, if PCs would have stuck with DR-DOS the mainframe would still be a more major player in the SMB business arena. Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of CM Poncelet Sent: Wednesday, May 19, 2021 8:50 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Again and with all due respect, progress is made not by blunting the tool but by sharpening the user. "IF/THEN" does not handle all boolean AND/OR/NAND/XOR and steps-not-executed conditions. Let not those who cannot master playing the violin demand that the violin be made more easy, but let them try playing the banjo instead. And SMP/E? In the 1980's it was 'recommended' to use its dialogs. In the late 90's, its Custom-Pak etc. became 'de rigueur' and 'de facto'. And yet I continued to use only native SMP/E - and did so daily to track down and fix PTFEs etc. etc. Who gains from this progressive and continual stultification of mainframe systems programming? Is it not Windows for mainframes? As they say, "Use it or lose it." Cheers, Chris Poncelet (r) On 19/05/2021 01:55, Nash, Jonathan S. wrote: > Once I learned of the IF/THEN statements for JCL I never used COND= > again. IF/THEN is much easier to use and to explain to new people. > I have seen many people code COND statements incorrectly because they > did not acually understand how they worked. > > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of CM Poncelet > Sent: Tuesday, May 18, 2021 8:19 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [EXTERNAL] Re: Best catch up resources for MVS / ZOS > Technologies > > With all due respect, anyone who has difficulty coding JCL COND= > statements should consider *not* working with IBM mainframe systems. > > All boolean conditional execution steps can be handled using only > COND= statements. I submitted a paper on this & it was published in > "Computing" in 1989. I would but cannot attach it, as uploading PDF > files to this discussion list is not permitted. > > No sysprog worth his salt has ever had a problem with coding JCL COND= > statements. > > Likewise IF/THEN statements belong in "JCL for dummies" - as do > symbols in JCL and SYSIN. Ditto IF/THEN in assembler. > > Chris Poncelet (r) > > > . > On 18/05/2021 14:02, Charles Mills wrote: >> Yeah, and IF/THEN is slightly better than COND= >> >> Also symbols in SYSIN data. >> >> Charles >> >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >> On Behalf Of Steve Horein >> Sent: Tuesday, May 18, 2021 5:35 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: Best catch up resources for MVS / ZOS Technologies >> >> I would argue JCL got better when symbols were allowed! :-) >> https://www.ibm.com/docs/en/zos/2.4.0?topic=es-symlist-parameter >> >> On Mon, May 17, 2021 at 10:46 PM Charles Mills wrote: >> >>> Steve, let me wade in here and suggest some big picture. I think >>> SHARE and such is great for the details. >>> >>> What has changed since 2001? An
Re: OMVS user.hfs shared
Elaine, you cannot have the same filesystem mounted twice(or more) in different spots in the directory tree in sysplex filesystem. As mentioned before, you really dont want to define user home directories in the root filesystem supplied by IBM. What we have done is created a automount managed directory in the sysplex root called /home that all user filesystems get mounted off from. Then from any system in the sysplex, the user is accessing the same filesystem from all systems. here is my sysplex tree structure at the highest level.in BPXPRM maps to the SYSRES - in our case RS* packs, then we have a few other, like vendor sysres (VS*), we automount NFS mounts, and then have system specific mount points (TEC*) that system specific stuff hangs off from. TEC1:$ ls -al total 200 lrwxrwxrwx 1 OMVSKERN OMVSGRP9 Jun 4 2013 $SYSNAME -> $SYSNAME/ lrwxrwxrwx 1 OMVSKERN OMVSGRP9 Jun 4 2013 $VERSION -> $VERSION/ drwxr-xr-x 24 OMVSKERN OMVSGRP 8192 Dec 15 07:28 . drwxr-xr-x 24 OMVSKERN OMVSGRP 8192 Dec 15 07:28 .. drwxr-xr-x 2 OMVSKERN OMVSGRP0 Jun 4 2013 ... drwxr-xr-x 5 OMVSKERN OMVSGRP 8192 Jun 6 2013 NFS drwxr-xr-x 2 OMVSKERN OMVSGRP0 Dec 11 2013 RSM01A drwxr-xr-x 2 OMVSKERN OMVSGRP0 Dec 11 2013 RSM02A drwxr-xr-x 14 OMVSKERN OMVSGRP 8192 Dec 21 08:05 RST01A drwxr-xr-x 2 OMVSKERN OMVSGRP0 Jun 6 2013 RST02A drwxr-xr-x 2 OMVSKERN OMVSGRP0 Aug 12 2013 RST03A drwxr-xr-x 3 OMVSKERN OMVSGRP 8192 Jun 6 2013 ServiceCICS drwxr-xr-x 3 OMVSKERN OMVSGRP 8192 Jun 6 2013 ServiceDB2 drwxr-xr-x 3 OMVSKERN OMVSGRP 8192 Aug 26 2020 ServiceQREP drwxr-xr-x 8 OMVSKERN OMVSGRP 8192 Jan 14 14:10 TEC1 drwxr-xr-x 9 OMVSKERN OMVSGRP 8192 Sep 19 2018 TEC2 drwxr-xr-x 2 OMVSKERN OMVSGRP0 Aug 27 2013 VSM01A drwxr-xr-x 2 OMVSKERN OMVSGRP0 Aug 27 2013 VSM02A drwxr-xr-x 2 OMVSKERN OMVSGRP0 Aug 27 2013 VSM03A drwxr-xr-x 2 OMVSKERN OMVSGRP0 Aug 27 2013 VST01A drwxr-xr-x 6 OMVSKERN OMVSGRP 8192 Jan 14 09:56 VST02A drwxr-xr-x 6 OMVSKERN OMVSGRP 8192 Jan 14 09:56 VST02A drwxr-xr-x 2 OMVSKERN OMVSGRP0 Aug 27 2013 VST03A drwxr-xr-x 53 OMVSKERN OMVSGRP 8192 Aug 26 2020 altroot lrwxrwxrwx 1 OMVSKERN OMVSGRP 12 Jun 4 2013 bin -> $VERSION/bin lrwxrwxrwx 1 OMVSKERN OMVSGRP 12 Jun 4 2013 dev -> $SYSNAME/dev lrwxrwxrwx 1 OMVSKERN OMVSGRP 12 Jun 4 2013 etc -> $SYSNAME/etc dr-xr-xr-x 36 OMVSKERN TTY0 May 20 08:49 home lrwxrwxrwx 1 OMVSKERN OMVSGRP 12 Jun 4 2013 lib -> $VERSION/lib drwxr-xr-x 2 OMVSKERN OMVSGRP0 Jun 19 2014 null lrwxrwxrwx 1 OMVSKERN OMVSGRP 12 Jun 4 2013 opt -> $VERSION/opt lrwxrwxrwx 1 OMVSKERN OMVSGRP 25 Jun 6 2013 remote -> $SYSSYMA/NFS//remot lrwxrwxrwx 1 OMVSKERN OMVSGRP 16 Jun 4 2013 samples -> $VERSION/samples drwxr-xr-x 4 OMVSKERN OMVSGRP 8192 Dec 10 10:56 shared lrwxrwxrwx 1 OMVSKERN OMVSGRP 12 Jun 4 2013 tmp -> $SYSNAME/tmp lrwxrwxrwx 1 OMVSKERN OMVSGRP 10 Jun 6 2013 u -> $SYSNAME/u lrwxrwxrwx 1 OMVSKERN OMVSGRP 12 Jun 4 2013 usr -> $VERSION/usr lrwxrwxrwx 1 OMVSKERN OMVSGRP 12 Jun 4 2013 var -> $SYSNAME/var lrwxrwxrwx 1 OMVSKERN OMVSGRP 15 Aug 27 2013 vendor -> $SYSSYMA/ TEC1:$ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies
Digital Research was certainly an accomplice in its own strangulation. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Thursday, May 20, 2021 8:07 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Stuck to DR-DOS? We would have all been better off had m$ not taken over the PC OS market and used the monopoly to strangle its competitors. SMB? Doesn't NFS play better with the *ix world? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Pommier, Rex Sent: Thursday, May 20, 2021 10:37 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Sorry Chris, But I would venture a guess that you're pretty much standing alone here. The "if it ain't broke don't fix it" otherwise known as "if it's good enough for me it should be good enough for everybody else" attitude is what has us on a slowly dying platform. So what if IF/THEN doesn't handle all the arcane COND= Boolean logic? Sysprogs aren't the only people using JCL. If I can easily train an application developer or an implementation analyst on the use of IF/THEN once and have them go away and build their own JCL without needing my continual assistance to help them understand COND= logic, it is a win-win situation. I would bet every sysprogs on this list has horror stories of having to fix somebody's COND= screw-up. It's actually quite enjoyable having a developer come to me puzzled about COND=something and be able to say "Here, use this IF/THEN JCL logic instead", and see the light come on in their eyes. But then, if PCs would have stuck with DR-DOS the mainframe would still be a more major player in the SMB business arena. Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of CM Poncelet Sent: Wednesday, May 19, 2021 8:50 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Again and with all due respect, progress is made not by blunting the tool but by sharpening the user. "IF/THEN" does not handle all boolean AND/OR/NAND/XOR and steps-not-executed conditions. Let not those who cannot master playing the violin demand that the violin be made more easy, but let them try playing the banjo instead. And SMP/E? In the 1980's it was 'recommended' to use its dialogs. In the late 90's, its Custom-Pak etc. became 'de rigueur' and 'de facto'. And yet I continued to use only native SMP/E - and did so daily to track down and fix PTFEs etc. etc. Who gains from this progressive and continual stultification of mainframe systems programming? Is it not Windows for mainframes? As they say, "Use it or lose it." Cheers, Chris Poncelet (r) On 19/05/2021 01:55, Nash, Jonathan S. wrote: > Once I learned of the IF/THEN statements for JCL I never used COND= > again. IF/THEN is much easier to use and to explain to new people. > I have seen many people code COND statements incorrectly because they > did not acually understand how they worked. > > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of CM Poncelet > Sent: Tuesday, May 18, 2021 8:19 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [EXTERNAL] Re: Best catch up resources for MVS / ZOS > Technologies > > With all due respect, anyone who has difficulty coding JCL COND= > statements should consider *not* working with IBM mainframe systems. > > All boolean conditional execution steps can be handled using only > COND= statements. I submitted a paper on this & it was published in > "Computing" in 1989. I would but cannot attach it, as uploading PDF > files to this discussion list is not permitted. > > No sysprog worth his salt has ever had a problem with coding JCL COND= > statements. > > Likewise IF/THEN statements belong in "JCL for dummies" - as do > symbols in JCL and SYSIN. Ditto IF/THEN in assembler. > > Chris Poncelet (r) > > > . > On 18/05/2021 14:02, Charles Mills wrote: >> Yeah, and IF/THEN is slightly better than COND= >> >> Also symbols in SYSIN data. >> >> Charles >> >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >> On Behalf Of Steve Horein >> Sent: Tuesday, May 18, 2021 5:35 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: Best catch up resources for MVS / ZOS Technologies >> >> I would argue JCL got better when symbols were allowed! :-) >> https://www.ibm.com/docs/en/zos/2.4.0?topic=es-symlist-parameter >> >> On Mon, May 17, 2021 at 10:46 PM Charles Mills wrote: >> >>> Steve, let me wade in here and suggest some big picture. I think >>> SHARE and such is great for the details. >>> >>> What has changed since 2001? An idiosyncratic, IMHO list: >>> >>> - In
OMVS user.hfs shared
I have a question about user HFS in a sysplex LPARs are sysplex'd but not OMVS SYSPLEX(NO) Migrating 1.13 to 2.2 LPAR1 - 1.13 LPAR2 - 2.2 separate root so, /u/userid.USER.HFS is off root but there is only one userid.USER.HFS so it's getting shared and will only allocate on one system do I have to point to a 'new' userid.xxx.USER.HFS when migrating in a sysplex? don't these have to be pre-allocated? maybe there's a dynamic way but we don't have one implemented any other options? Thanks, Elaine -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies
Stuck to DR-DOS? We would have all been better off had m$ not taken over the PC OS market and used the monopoly to strangle its competitors. SMB? Doesn't NFS play better with the *ix world? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Pommier, Rex Sent: Thursday, May 20, 2021 10:37 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Sorry Chris, But I would venture a guess that you're pretty much standing alone here. The "if it ain't broke don't fix it" otherwise known as "if it's good enough for me it should be good enough for everybody else" attitude is what has us on a slowly dying platform. So what if IF/THEN doesn't handle all the arcane COND= Boolean logic? Sysprogs aren't the only people using JCL. If I can easily train an application developer or an implementation analyst on the use of IF/THEN once and have them go away and build their own JCL without needing my continual assistance to help them understand COND= logic, it is a win-win situation. I would bet every sysprogs on this list has horror stories of having to fix somebody's COND= screw-up. It's actually quite enjoyable having a developer come to me puzzled about COND=something and be able to say "Here, use this IF/THEN JCL logic instead", and see the light come on in their eyes. But then, if PCs would have stuck with DR-DOS the mainframe would still be a more major player in the SMB business arena. Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of CM Poncelet Sent: Wednesday, May 19, 2021 8:50 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Again and with all due respect, progress is made not by blunting the tool but by sharpening the user. "IF/THEN" does not handle all boolean AND/OR/NAND/XOR and steps-not-executed conditions. Let not those who cannot master playing the violin demand that the violin be made more easy, but let them try playing the banjo instead. And SMP/E? In the 1980's it was 'recommended' to use its dialogs. In the late 90's, its Custom-Pak etc. became 'de rigueur' and 'de facto'. And yet I continued to use only native SMP/E - and did so daily to track down and fix PTFEs etc. etc. Who gains from this progressive and continual stultification of mainframe systems programming? Is it not Windows for mainframes? As they say, "Use it or lose it." Cheers, Chris Poncelet (r) On 19/05/2021 01:55, Nash, Jonathan S. wrote: > Once I learned of the IF/THEN statements for JCL I never used COND= > again. IF/THEN is much easier to use and to explain to new people. > I have seen many people code COND statements incorrectly because they > did not acually understand how they worked. > > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of CM Poncelet > Sent: Tuesday, May 18, 2021 8:19 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [EXTERNAL] Re: Best catch up resources for MVS / ZOS > Technologies > > With all due respect, anyone who has difficulty coding JCL COND= > statements should consider *not* working with IBM mainframe systems. > > All boolean conditional execution steps can be handled using only > COND= statements. I submitted a paper on this & it was published in > "Computing" in 1989. I would but cannot attach it, as uploading PDF > files to this discussion list is not permitted. > > No sysprog worth his salt has ever had a problem with coding JCL COND= > statements. > > Likewise IF/THEN statements belong in "JCL for dummies" - as do > symbols in JCL and SYSIN. Ditto IF/THEN in assembler. > > Chris Poncelet (r) > > > . > On 18/05/2021 14:02, Charles Mills wrote: >> Yeah, and IF/THEN is slightly better than COND= >> >> Also symbols in SYSIN data. >> >> Charles >> >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >> On Behalf Of Steve Horein >> Sent: Tuesday, May 18, 2021 5:35 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: Best catch up resources for MVS / ZOS Technologies >> >> I would argue JCL got better when symbols were allowed! :-) >> https://www.ibm.com/docs/en/zos/2.4.0?topic=es-symlist-parameter >> >> On Mon, May 17, 2021 at 10:46 PM Charles Mills wrote: >> >>> Steve, let me wade in here and suggest some big picture. I think >>> SHARE and such is great for the details. >>> >>> What has changed since 2001? An idiosyncratic, IMHO list: >>> >>> - In 2001 SNA was yielding to TCP/IP. That transition has continued. >>> An awful lot of mainframe connectivity is now TCP/IP. Lots and lots >>> of Internet connectivity to the mainframe. >>> - Security is huge. Encryption is hot. Zero Trust is the buzzword of >>> the month. >>> - Everything is of course bigger. Z hardware goes up to what? 4TB real? >>>
Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies
Actually that was a mistake on my part. I was thinking CP/M which was before MS-DOS. :-) I've actually used CP/M eons ago but don't know if I ever used DR-DOS. Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of PINION, RICHARD W. Sent: Thursday, May 20, 2021 9:41 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies DR-DOS, now that's a name I've not heard in a long time (Obi Wan Kenobe). -Original Message- From: IBM Mainframe Discussion List On Behalf Of Pommier, Rex Sent: Thursday, May 20, 2021 10:38 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies [External Email. Exercise caution when clicking links or opening attachments.] Sorry Chris, But I would venture a guess that you're pretty much standing alone here. The "if it ain't broke don't fix it" otherwise known as "if it's good enough for me it should be good enough for everybody else" attitude is what has us on a slowly dying platform. So what if IF/THEN doesn't handle all the arcane COND= Boolean logic? Sysprogs aren't the only people using JCL. If I can easily train an application developer or an implementation analyst on the use of IF/THEN once and have them go away and build their own JCL without needing my continual assistance to help them understand COND= logic, it is a win-win situation. I would bet every sysprogs on this list has horror stories of having to fix somebody's COND= screw-up. It's actually quite enjoyable having a developer come to me puzzled about COND=something and be able to say "Here, use this IF/THEN JCL logic instead", and see the light come on in their eyes. But then, if PCs would have stuck with DR-DOS the mainframe would still be a more major player in the SMB business arena. Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of CM Poncelet Sent: Wednesday, May 19, 2021 8:50 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Again and with all due respect, progress is made not by blunting the tool but by sharpening the user. "IF/THEN" does not handle all boolean AND/OR/NAND/XOR and steps-not-executed conditions. Let not those who cannot master playing the violin demand that the violin be made more easy, but let them try playing the banjo instead. And SMP/E? In the 1980's it was 'recommended' to use its dialogs. In the late 90's, its Custom-Pak etc. became 'de rigueur' and 'de facto'. And yet I continued to use only native SMP/E - and did so daily to track down and fix PTFEs etc. etc. Who gains from this progressive and continual stultification of mainframe systems programming? Is it not Windows for mainframes? As they say, "Use it or lose it." Cheers, Chris Poncelet (r) On 19/05/2021 01:55, Nash, Jonathan S. wrote: > Once I learned of the IF/THEN statements for JCL I never used COND= > again. IF/THEN is much easier to use and to explain to new people. > I have seen many people code COND statements incorrectly because they > did not acually understand how they worked. > > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of CM Poncelet > Sent: Tuesday, May 18, 2021 8:19 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [EXTERNAL] Re: Best catch up resources for MVS / ZOS > Technologies > > With all due respect, anyone who has difficulty coding JCL COND= > statements should consider *not* working with IBM mainframe systems. > > All boolean conditional execution steps can be handled using only > COND= statements. I submitted a paper on this & it was published in > "Computing" in 1989. I would but cannot attach it, as uploading PDF > files to this discussion list is not permitted. > > No sysprog worth his salt has ever had a problem with coding JCL COND= > statements. > > Likewise IF/THEN statements belong in "JCL for dummies" - as do > symbols in JCL and SYSIN. Ditto IF/THEN in assembler. > > Chris Poncelet (r) > > > . > On 18/05/2021 14:02, Charles Mills wrote: >> Yeah, and IF/THEN is slightly better than COND= >> >> Also symbols in SYSIN data. >> >> Charles >> >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >> On Behalf Of Steve Horein >> Sent: Tuesday, May 18, 2021 5:35 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: Best catch up resources for MVS / ZOS Technologies >> >> I would argue JCL got better when symbols were allowed! :-) >> https://urldefense.com/v3/__https://www.ibm.com/docs/en/zos/2.4.0?top >> ic=es-symlist-parameter__;!!HnnddUIWDII9UQ!HOqHZ01GFT4JGSB82v3WH370P0 >> t7s0tHIMVgDmGr4We6lrkYplP2aODrYvHAioFxoZg$ >> >> On Mon, May 17, 2021 at 10:46 PM Charles Mills wrote: >> >>> Steve, let me wade in here and suggest some big picture. I think >>> SHARE and
Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies
DR-DOS, now that's a name I've not heard in a long time (Obi Wan Kenobe). -Original Message- From: IBM Mainframe Discussion List On Behalf Of Pommier, Rex Sent: Thursday, May 20, 2021 10:38 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies [External Email. Exercise caution when clicking links or opening attachments.] Sorry Chris, But I would venture a guess that you're pretty much standing alone here. The "if it ain't broke don't fix it" otherwise known as "if it's good enough for me it should be good enough for everybody else" attitude is what has us on a slowly dying platform. So what if IF/THEN doesn't handle all the arcane COND= Boolean logic? Sysprogs aren't the only people using JCL. If I can easily train an application developer or an implementation analyst on the use of IF/THEN once and have them go away and build their own JCL without needing my continual assistance to help them understand COND= logic, it is a win-win situation. I would bet every sysprogs on this list has horror stories of having to fix somebody's COND= screw-up. It's actually quite enjoyable having a developer come to me puzzled about COND=something and be able to say "Here, use this IF/THEN JCL logic instead", and see the light come on in their eyes. But then, if PCs would have stuck with DR-DOS the mainframe would still be a more major player in the SMB business arena. Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of CM Poncelet Sent: Wednesday, May 19, 2021 8:50 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Again and with all due respect, progress is made not by blunting the tool but by sharpening the user. "IF/THEN" does not handle all boolean AND/OR/NAND/XOR and steps-not-executed conditions. Let not those who cannot master playing the violin demand that the violin be made more easy, but let them try playing the banjo instead. And SMP/E? In the 1980's it was 'recommended' to use its dialogs. In the late 90's, its Custom-Pak etc. became 'de rigueur' and 'de facto'. And yet I continued to use only native SMP/E - and did so daily to track down and fix PTFEs etc. etc. Who gains from this progressive and continual stultification of mainframe systems programming? Is it not Windows for mainframes? As they say, "Use it or lose it." Cheers, Chris Poncelet (r) On 19/05/2021 01:55, Nash, Jonathan S. wrote: > Once I learned of the IF/THEN statements for JCL I never used COND= > again. IF/THEN is much easier to use and to explain to new people. > I have seen many people code COND statements incorrectly because they > did not acually understand how they worked. > > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of CM Poncelet > Sent: Tuesday, May 18, 2021 8:19 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [EXTERNAL] Re: Best catch up resources for MVS / ZOS > Technologies > > With all due respect, anyone who has difficulty coding JCL COND= > statements should consider *not* working with IBM mainframe systems. > > All boolean conditional execution steps can be handled using only > COND= statements. I submitted a paper on this & it was published in > "Computing" in 1989. I would but cannot attach it, as uploading PDF > files to this discussion list is not permitted. > > No sysprog worth his salt has ever had a problem with coding JCL COND= > statements. > > Likewise IF/THEN statements belong in "JCL for dummies" - as do > symbols in JCL and SYSIN. Ditto IF/THEN in assembler. > > Chris Poncelet (r) > > > . > On 18/05/2021 14:02, Charles Mills wrote: >> Yeah, and IF/THEN is slightly better than COND= >> >> Also symbols in SYSIN data. >> >> Charles >> >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >> On Behalf Of Steve Horein >> Sent: Tuesday, May 18, 2021 5:35 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: Best catch up resources for MVS / ZOS Technologies >> >> I would argue JCL got better when symbols were allowed! :-) >> https://urldefense.com/v3/__https://www.ibm.com/docs/en/zos/2.4.0?top >> ic=es-symlist-parameter__;!!HnnddUIWDII9UQ!HOqHZ01GFT4JGSB82v3WH370P0 >> t7s0tHIMVgDmGr4We6lrkYplP2aODrYvHAioFxoZg$ >> >> On Mon, May 17, 2021 at 10:46 PM Charles Mills wrote: >> >>> Steve, let me wade in here and suggest some big picture. I think >>> SHARE and such is great for the details. >>> >>> What has changed since 2001? An idiosyncratic, IMHO list: >>> >>> - In 2001 SNA was yielding to TCP/IP. That transition has continued. >>> An awful lot of mainframe connectivity is now TCP/IP. Lots and lots >>> of Internet connectivity to the mainframe. >>> - Security is huge. Encryption is hot. Zero Trust is the buzzword of >>> the month. >>> - Everything is of course bigger. Z hardware goes up
Re: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies
Sorry Chris, But I would venture a guess that you're pretty much standing alone here. The "if it ain't broke don't fix it" otherwise known as "if it's good enough for me it should be good enough for everybody else" attitude is what has us on a slowly dying platform. So what if IF/THEN doesn't handle all the arcane COND= Boolean logic? Sysprogs aren't the only people using JCL. If I can easily train an application developer or an implementation analyst on the use of IF/THEN once and have them go away and build their own JCL without needing my continual assistance to help them understand COND= logic, it is a win-win situation. I would bet every sysprogs on this list has horror stories of having to fix somebody's COND= screw-up. It's actually quite enjoyable having a developer come to me puzzled about COND=something and be able to say "Here, use this IF/THEN JCL logic instead", and see the light come on in their eyes. But then, if PCs would have stuck with DR-DOS the mainframe would still be a more major player in the SMB business arena. Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of CM Poncelet Sent: Wednesday, May 19, 2021 8:50 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Again and with all due respect, progress is made not by blunting the tool but by sharpening the user. "IF/THEN" does not handle all boolean AND/OR/NAND/XOR and steps-not-executed conditions. Let not those who cannot master playing the violin demand that the violin be made more easy, but let them try playing the banjo instead. And SMP/E? In the 1980's it was 'recommended' to use its dialogs. In the late 90's, its Custom-Pak etc. became 'de rigueur' and 'de facto'. And yet I continued to use only native SMP/E - and did so daily to track down and fix PTFEs etc. etc. Who gains from this progressive and continual stultification of mainframe systems programming? Is it not Windows for mainframes? As they say, "Use it or lose it." Cheers, Chris Poncelet (r) On 19/05/2021 01:55, Nash, Jonathan S. wrote: > Once I learned of the IF/THEN statements for JCL I never used COND= > again. IF/THEN is much easier to use and to explain to new people. > I have seen many people code COND statements incorrectly because they > did not acually understand how they worked. > > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of CM Poncelet > Sent: Tuesday, May 18, 2021 8:19 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [EXTERNAL] Re: Best catch up resources for MVS / ZOS > Technologies > > With all due respect, anyone who has difficulty coding JCL COND= > statements should consider *not* working with IBM mainframe systems. > > All boolean conditional execution steps can be handled using only > COND= statements. I submitted a paper on this & it was published in > "Computing" in 1989. I would but cannot attach it, as uploading PDF > files to this discussion list is not permitted. > > No sysprog worth his salt has ever had a problem with coding JCL COND= > statements. > > Likewise IF/THEN statements belong in "JCL for dummies" - as do > symbols in JCL and SYSIN. Ditto IF/THEN in assembler. > > Chris Poncelet (r) > > > . > On 18/05/2021 14:02, Charles Mills wrote: >> Yeah, and IF/THEN is slightly better than COND= >> >> Also symbols in SYSIN data. >> >> Charles >> >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >> On Behalf Of Steve Horein >> Sent: Tuesday, May 18, 2021 5:35 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: Best catch up resources for MVS / ZOS Technologies >> >> I would argue JCL got better when symbols were allowed! :-) >> https://www.ibm.com/docs/en/zos/2.4.0?topic=es-symlist-parameter >> >> On Mon, May 17, 2021 at 10:46 PM Charles Mills wrote: >> >>> Steve, let me wade in here and suggest some big picture. I think >>> SHARE and such is great for the details. >>> >>> What has changed since 2001? An idiosyncratic, IMHO list: >>> >>> - In 2001 SNA was yielding to TCP/IP. That transition has continued. >>> An awful lot of mainframe connectivity is now TCP/IP. Lots and lots >>> of Internet connectivity to the mainframe. >>> - Security is huge. Encryption is hot. Zero Trust is the buzzword of >>> the month. >>> - Everything is of course bigger. Z hardware goes up to what? 4TB real? >>> Someone will correct me if that is wrong. >>> - Tape drives have pretty much gone away. They live on as virtual, >>> emulated-on-DASD tape drives. >>> - The Cloud. Read any airline magazine for the latest. >>> - Remember VM? It was pretty moribund in 2001. It has found new life >>> hosting thousands of Linux instances. Yes, Linux running like a >>> champ on Z hardware. Mainframe Linux is huge. You can run Linux in a >>> region of MVS in a "container." >>> - Speaking of which, there is a
Re: SMF - SIGVALIDATE parameter
On Wed, 19 May 2021 03:11:30 -0500, Jordi Bornay wrote: >SIGVALIDATE is for checking digital signature on SMF records. How should this >help to find out if smf records of a subtype are missing for a time interval ? > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Possibly the OP is interested with the IFASMFDP report-detail parameter REPORTOPTS(SUBTYPE) which was added with z/OS V2R4? Scott Barry SBBTech LLC -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies
BTDT,GTS. They made us write in 650 machine code before they taught us about assemblers. I've also written zaps now and then. But, yes, happiness is a warm macro assembler, and only a masochist willingly writes in machine language. BTW, "high level" is in the mind of the beholder: I could make a case that HLASM is higher level than C. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Lennie Dymoke-Bradshaw [032fff1be9b4-dmarc-requ...@listserv.ua.edu] Sent: Thursday, May 20, 2021 5:17 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Can I deduce from this that you don’t use high level languages? But if so, then even using assembler is too easy. Let's write everything in machine code . Lennie Dymoke-Bradshaw Reverse Sweep Consulting Limited https://secure-web.cisco.com/1QltAnKi-NU_CgtMHtNPS2QGlFmcLIggQfq1m35k0Mgrmfap0hNyGQTnNR6PnqcJHu9zSsXZT46CILPTesIT4OQcEu-WHBoCB0PM2BKszRSP3qmWRN02w-CyVl4cyks1cpCs9moh0aNw-Ijo8C09RZa8xOeD2T_jbrqMXUdSpIiEJxN-ZT165ZvME9NEd2Gwt7Hptp8vpzes30l0d2EvezWN3IK5QYYg7ZDiwXbeO6hbiVEPKGAwupchNkLRwGja2jNu5KpwJ5jk2XVRpJUbgvM-Wj8p4vptCnWPUiUiGW94cXaV5CtEtxxe2CBHQAum04hXffGNh4BVpr6zJwwc7Xnpxc5vkP51y2riYrtx89hrC9FFahehZXN-8vHtWVDQqmlnkcUlGiMJUuhO9KEIyDSAMylqEM_3eoBuZCFa8Vb44-N-2ctttBstwUZ9gfQHP/https%3A%2F%2Frsclweb.com ‘Dance like no one is watching; encrypt like everyone is’ -Original Message- From: IBM Mainframe Discussion List On Behalf Of CM Poncelet Sent: 20 May 2021 02:50 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Again and with all due respect, progress is made not by blunting the tool but by sharpening the user. "IF/THEN" does not handle all boolean AND/OR/NAND/XOR and steps-not-executed conditions. Let not those who cannot master playing the violin demand that the violin be made more easy, but let them try playing the banjo instead. And SMP/E? In the 1980's it was 'recommended' to use its dialogs. In the late 90's, its Custom-Pak etc. became 'de rigueur' and 'de facto'. And yet I continued to use only native SMP/E - and did so daily to track down and fix PTFEs etc. etc. Who gains from this progressive and continual stultification of mainframe systems programming? Is it not Windows for mainframes? As they say, "Use it or lose it." Cheers, Chris Poncelet (r) On 19/05/2021 01:55, Nash, Jonathan S. wrote: > Once I learned of the IF/THEN statements for JCL I never used COND= > again. IF/THEN is much easier to use and to explain to new people. > I have seen many people code COND statements incorrectly because they > did not acually understand how they worked. > > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of CM Poncelet > Sent: Tuesday, May 18, 2021 8:19 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [EXTERNAL] Re: Best catch up resources for MVS / ZOS > Technologies > > With all due respect, anyone who has difficulty coding JCL COND= > statements should consider *not* working with IBM mainframe systems. > > All boolean conditional execution steps can be handled using only > COND= statements. I submitted a paper on this & it was published in > "Computing" in 1989. I would but cannot attach it, as uploading PDF > files to this discussion list is not permitted. > > No sysprog worth his salt has ever had a problem with coding JCL COND= > statements. > > Likewise IF/THEN statements belong in "JCL for dummies" - as do > symbols in JCL and SYSIN. Ditto IF/THEN in assembler. > > Chris Poncelet (r) > > > . > On 18/05/2021 14:02, Charles Mills wrote: >> Yeah, and IF/THEN is slightly better than COND= >> >> Also symbols in SYSIN data. >> >> Charles >> >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >> On Behalf Of Steve Horein >> Sent: Tuesday, May 18, 2021 5:35 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: Best catch up resources for MVS / ZOS Technologies >> >> I would argue JCL got better when symbols were allowed! :-) >> https://www.ibm.com/docs/en/zos/2.4.0?topic=es-symlist-parameter >> >> On Mon, May 17, 2021 at 10:46 PM Charles Mills wrote: >> >>> Steve, let me wade in here and suggest some big picture. I think >>> SHARE and such is great for the details. >>> >>> What has changed since 2001? An idiosyncratic, IMHO list: >>> >>> - In 2001 SNA was yielding to TCP/IP. That transition has continued. >>> An awful lot of mainframe connectivity is now TCP/IP. Lots and lots >>> of Internet connectivity to the mainframe. >>> - Security is huge. Encryption is hot. Zero Trust is the buzzword of >>> the month. >>> - Everything is of course bigger. Z hardware goes up to what? 4TB real? >>> Someone will correct me if that is wrong. >>> - Tape drives have pretty much gone away. They live on as virtual,
Re: SMF - SIGVALIDATE parameter
SMF signatures include metadata describing both the record contents and the number of records per type and subtype that are written during each interval. Validation processing ensures that neither the record contents nor the counts have changed. Bonnie Ordonez, IBM SMF, Level 3 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Users of a hfs file
Is it possible to determine, without trying to unmount a file, which processes are using resources below that point in the hierachy, and would prevent an unmount from completing, then relate this back to jobs, stcs, or TSO users? Regards, Joe -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Best catch up resources for MVS / ZOS Technologies
Hi gil, Which correct tool did you use? Thanks and regards, David On 2021-05-19 23:16, Paul Gilmartin wrote: On Thu, 20 May 2021 03:13:19 +0100, CM Poncelet wrote: Saving "test.pdf.txt", renaming it as "test.pdf" and then trying to open it as a PDF produces the following error message: "Adobe reader could not open 'test.pdf' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded)." HTH. But using the correct tool, I was able to open it cleanly with Adobe Reader. "rename" is simply the wrong tool. -- 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: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies
Can I deduce from this that you don’t use high level languages? But if so, then even using assembler is too easy. Let's write everything in machine code . Lennie Dymoke-Bradshaw Reverse Sweep Consulting Limited https://rsclweb.com ‘Dance like no one is watching; encrypt like everyone is’ -Original Message- From: IBM Mainframe Discussion List On Behalf Of CM Poncelet Sent: 20 May 2021 02:50 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Again and with all due respect, progress is made not by blunting the tool but by sharpening the user. "IF/THEN" does not handle all boolean AND/OR/NAND/XOR and steps-not-executed conditions. Let not those who cannot master playing the violin demand that the violin be made more easy, but let them try playing the banjo instead. And SMP/E? In the 1980's it was 'recommended' to use its dialogs. In the late 90's, its Custom-Pak etc. became 'de rigueur' and 'de facto'. And yet I continued to use only native SMP/E - and did so daily to track down and fix PTFEs etc. etc. Who gains from this progressive and continual stultification of mainframe systems programming? Is it not Windows for mainframes? As they say, "Use it or lose it." Cheers, Chris Poncelet (r) On 19/05/2021 01:55, Nash, Jonathan S. wrote: > Once I learned of the IF/THEN statements for JCL I never used COND= > again. IF/THEN is much easier to use and to explain to new people. > I have seen many people code COND statements incorrectly because they > did not acually understand how they worked. > > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of CM Poncelet > Sent: Tuesday, May 18, 2021 8:19 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [EXTERNAL] Re: Best catch up resources for MVS / ZOS > Technologies > > With all due respect, anyone who has difficulty coding JCL COND= > statements should consider *not* working with IBM mainframe systems. > > All boolean conditional execution steps can be handled using only > COND= statements. I submitted a paper on this & it was published in > "Computing" in 1989. I would but cannot attach it, as uploading PDF > files to this discussion list is not permitted. > > No sysprog worth his salt has ever had a problem with coding JCL COND= > statements. > > Likewise IF/THEN statements belong in "JCL for dummies" - as do > symbols in JCL and SYSIN. Ditto IF/THEN in assembler. > > Chris Poncelet (r) > > > . > On 18/05/2021 14:02, Charles Mills wrote: >> Yeah, and IF/THEN is slightly better than COND= >> >> Also symbols in SYSIN data. >> >> Charles >> >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >> On Behalf Of Steve Horein >> Sent: Tuesday, May 18, 2021 5:35 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: Best catch up resources for MVS / ZOS Technologies >> >> I would argue JCL got better when symbols were allowed! :-) >> https://www.ibm.com/docs/en/zos/2.4.0?topic=es-symlist-parameter >> >> On Mon, May 17, 2021 at 10:46 PM Charles Mills wrote: >> >>> Steve, let me wade in here and suggest some big picture. I think >>> SHARE and such is great for the details. >>> >>> What has changed since 2001? An idiosyncratic, IMHO list: >>> >>> - In 2001 SNA was yielding to TCP/IP. That transition has continued. >>> An awful lot of mainframe connectivity is now TCP/IP. Lots and lots >>> of Internet connectivity to the mainframe. >>> - Security is huge. Encryption is hot. Zero Trust is the buzzword of >>> the month. >>> - Everything is of course bigger. Z hardware goes up to what? 4TB real? >>> Someone will correct me if that is wrong. >>> - Tape drives have pretty much gone away. They live on as virtual, >>> emulated-on-DASD tape drives. >>> - The Cloud. Read any airline magazine for the latest. >>> - Remember VM? It was pretty moribund in 2001. It has found new life >>> hosting thousands of Linux instances. Yes, Linux running like a >>> champ on Z hardware. Mainframe Linux is huge. You can run Linux in a >>> region of MVS in a "container." >>> - Speaking of which, there is a Z box that will not IPL z/OS! It is >>> called Linux One. It's a mainframe with a bit hobbled somewhere such >>> that mainframe operating systems will not IPL, only Linux. >>> - Lots of new features in core MVS but you would fully recognize the >>> environment. If you sit down at a TSO/ISPF session it will seem like >>> nothing has changed. JCL has not gotten any better (or any worse, >>> thankfully). >>> - Remember the issue of "above the (24-bit) line"? It is still >>> there, but pretty much in the background. The new thing is data and >>> execution "above the (2GB/31-bit) bar." Lots of software products >>> are exploiting data above 2GB, and code can even run there, with lots of >>> limitations. AMODE/RMODE 64. >>> - IBM JES3 is dead. Long live Phoenix JES3 plus. IBM ditched JES3, >>>
Re: How can I tell the zFS files being used by my application
Timothy, Thanks for these links. Are these fixes available in the ACDC downloads? I was told that shared classes should make startup faster. I've been playing with it and have noticed a few interesting things. 1. I think the default shared classes cache size is 60MB... Ive made it 100MB and it is 93% full ! it would be good if appropriate size was given in z/OSMF 2. When I start z/OSMF a second time, the SMF 92-11 records show over 1000 jar files are being opened, and some are being opened more than once, for example /usr/include/java_classes/IRRRacf.jar is being opened 68 times! 1. Shared classes are being used, as I can display the file information in the shared cache 2. It looks like jar files are >not< being loaded from the shared classes data space and they are being loaded from the file system. Are there any magic options to say "load a jar - just once ... not once for each thread", or to tell Java to load from the shared classes cache? It feels like an old (non java) problem of having a non reentrant load module, so it was loaded from disk every time, instead of reusing the in-memory copy. Colin On Thu, 20 May 2021 at 06:00, Timothy Sipples wrote: > If you're experiencing long z/OS Management Facility startup times then > please check that you have installed the PTFs for several APARs. You might > consider disabling the z/OSMF help feature (if you can safely live without > it) since it represents a substantial fraction of startup time/energy. > Details are available here: > > > https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/jing-hua-jiang1/2020/10/30/make-your-zosmf-server-starts-significantly-faster > > https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/zhi-li1/2020/08/10/tailor-your-zosmf-server-for-better-performance-in > > - - - - - - - - - - > Timothy Sipples > I.T. Architect Executive > Digital Asset & Other Industry Solutions > IBM Z & LinuxONE > - - - - - - - - - - > E-Mail: sipp...@sg.ibm.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
Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies
Progress is also not made by pretending that a blunt tool is sharp just because you're used to it. COND= is a blunt tool, and IF/THEN puts a bandage over some, but not all, of its ugliness. What's wrong with taking advantage of skeletons and such? Yes, I have been known to hand craft an SMP/E job when the templates didn't suit my needs, but what's wrong with taking advantage of them when it saves me time? I don't like it when IBM takes away tools, but that's not the same as providing new tools that I can ignore when they don't suit the task at hand. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of CM Poncelet [ponce...@bcs.org.uk] Sent: Wednesday, May 19, 2021 9:50 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies Again and with all due respect, progress is made not by blunting the tool but by sharpening the user. "IF/THEN" does not handle all boolean AND/OR/NAND/XOR and steps-not-executed conditions. Let not those who cannot master playing the violin demand that the violin be made more easy, but let them try playing the banjo instead. And SMP/E? In the 1980's it was 'recommended' to use its dialogs. In the late 90's, its Custom-Pak etc. became 'de rigueur' and 'de facto'. And yet I continued to use only native SMP/E - and did so daily to track down and fix PTFEs etc. etc. Who gains from this progressive and continual stultification of mainframe systems programming? Is it not Windows for mainframes? As they say, "Use it or lose it." Cheers, Chris Poncelet (r) On 19/05/2021 01:55, Nash, Jonathan S. wrote: > Once I learned of the IF/THEN statements for > JCL I never used COND= again. IF/THEN is much > easier to use and to explain to new people. > I have seen many people code COND statements > incorrectly because they did not acually > understand how they worked. > > > -Original Message- > From: IBM Mainframe Discussion List On Behalf Of > CM Poncelet > Sent: Tuesday, May 18, 2021 8:19 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [EXTERNAL] Re: Best catch up resources for MVS / ZOS Technologies > > With all due respect, anyone who has difficulty coding JCL COND= > statements should consider *not* working with IBM mainframe systems. > > All boolean conditional execution steps can be handled using only COND= > statements. I submitted a paper on this & it was published in > "Computing" in 1989. I would but cannot attach it, as uploading PDF > files to this discussion list is not permitted. > > No sysprog worth his salt has ever had a problem with coding JCL COND= > statements. > > Likewise IF/THEN statements belong in "JCL for dummies" - as do symbols > in JCL and SYSIN. Ditto IF/THEN in assembler. > > Chris Poncelet (r) > > > . > On 18/05/2021 14:02, Charles Mills wrote: >> Yeah, and IF/THEN is slightly better than COND= >> >> Also symbols in SYSIN data. >> >> Charles >> >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >> Behalf Of Steve Horein >> Sent: Tuesday, May 18, 2021 5:35 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: Best catch up resources for MVS / ZOS Technologies >> >> I would argue JCL got better when symbols were allowed! :-) >> https://www.ibm.com/docs/en/zos/2.4.0?topic=es-symlist-parameter >> >> On Mon, May 17, 2021 at 10:46 PM Charles Mills wrote: >> >>> Steve, let me wade in here and suggest some big picture. I think SHARE and >>> such is great for the details. >>> >>> What has changed since 2001? An idiosyncratic, IMHO list: >>> >>> - In 2001 SNA was yielding to TCP/IP. That transition has continued. An >>> awful lot of mainframe connectivity is now TCP/IP. Lots and lots of >>> Internet connectivity to the mainframe. >>> - Security is huge. Encryption is hot. Zero Trust is the buzzword of the >>> month. >>> - Everything is of course bigger. Z hardware goes up to what? 4TB real? >>> Someone will correct me if that is wrong. >>> - Tape drives have pretty much gone away. They live on as virtual, >>> emulated-on-DASD tape drives. >>> - The Cloud. Read any airline magazine for the latest. >>> - Remember VM? It was pretty moribund in 2001. It has found new life >>> hosting thousands of Linux instances. Yes, Linux running like a champ on Z >>> hardware. Mainframe Linux is huge. You can run Linux in a region of MVS in >>> a "container." >>> - Speaking of which, there is a Z box that will not IPL z/OS! It is called >>> Linux One. It's a mainframe with a bit hobbled somewhere such that >>> mainframe operating systems will not IPL, only Linux. >>> - Lots of new features in core MVS but you would fully recognize the >>> environment. If you sit down at a TSO/ISPF session it will seem like >>> nothing has changed. JCL has not gotten any better (or any worse, >>> thankfully). >>> - Remember the issue of "above the
