Re: System Symbols
Just for clarification: No, we don't IPL daily - apologies for my poor wording. My use of IEASYMU2 creates two 'new' system symbols 'PRYYMMDD' and 'PRYYDDD' after IPL, but then I change the values in those symbols at about 00:01 each day. As for "This is the sort of thing that should be routinely provided by the OS." - a huge YES! to that, and other associated values like 'first working day of the week/month/year' and so on. Its a crying shame that the only other way of getting such values in to a jobstream - that I know of! - is by spending $many for something like CA-7 or Tivoli. Sean On Sun, 30 Dec 2018 at 22:55, scott Ford wrote: > Peter , > > Do customers typically add their own SYS type symbols ? I am curious. > > Scott > > On Sun, Dec 30, 2018 at 8:44 AM Peter Relson wrote: > > > Using IEASYMU2 is fine. > > > > I suspect that most would not use "routinely" to express the desirability > > of IBM providing a symbol for "yesterday". > > I have not seen a requirement for such a thing (this would be a "dynamic > > symbol" rather than a "static symbol"). > > FWIW, at this point, compatibility would be a concern with adding any > > symbol that does not begin with "SYS". > > > > So Sean's implementation of a symbol for his own site makes sense. > > > > Peter Relson > > z/OS Core Technology Design > > > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > -- > Scott Ford > IDMWORKS > z/OS Development > > -- > 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: System Symbols
>Do customers typically add their own SYS type symbols I expect not. They should not. My point was that we could safely add a symbol starting with SYS but could not safely add a symbol such as &YESTERDAY due to the compatibility concerns that a customer might have done so and our definition could cause them a problem. &SYSYESTERDAY would be OK, but of course would not be in line with the names of the other time/date-oriented symbols. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Crosshair cursor
I'm sorry, I should have been more clear...I mean of course the 'vector graphics' (a.k.a APA) that was supported by devices like the 3179G. Happy New Year, too. DJ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: System Symbols
z/OS 2.2 and above allow use of system symbols in batch. See the SYSSYM=ALLOW parameter of JOBDEF and JOBCLASS in the JES manuals. HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of scott Ford Sent: Saturday, December 29, 2018 12:37 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: System Symbols Peter, Exactly. I saw the responses after I read through the manual, just wanted to make sure I understood the process before thinking about a design. In theory, we would have customer set the symbol and use the Service to query it as you had indicated. As always Peter, very much appreciated, and I learned someone again. Regards, Scott On Sat, Dec 29, 2018 at 10:15 AM Peter Relson wrote: > > Has anyone created their own system symbol and then referenced it in > HLASM ? > > > Adding system symbols is not something that a program should be doing. > IEASYMxx is the supported method for defining system symbols. > SETLOAD IEASYM is the supported method for adding a system symbol > after IPL. > > > what I am not clear on is how to have HLASM code read the system > symbol table and compare for the desired symbol.What i want to do is > if we find a specific symbol set, have a exit perform conditional logic. > > > You should not "read the system symbol table". If you want to see if a > specific symbol is set, then you should use the ASASYMBM service to > try to substitute a string that has that symbol in it and see if > substitution occurred. > > This of course is very inefficient, and unless this will happen only > once in the life of the system you would be better off doing this > once, somewhere, and stashing the result so that subsequent times can > get the result quickly. > > Peter Relson > z/OS Core Technology Design > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Scott Ford IDMWORKS z/OS Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IBM Mapping macro for ISPF statistics in PDS Directory entries?
Which Macro? -Original Message- From: IBM Mainframe Discussion List On Behalf Of Steve Smith Sent: Saturday, December 29, 2018 9:05 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IBM Mapping macro for ISPF statistics in PDS Directory entries? I found this macro in the ISPF maclib. It's not convenient for me to look for it now, but it should be easy to find. btw, this question was asked before... in 2004. sas On Fri, Dec 28, 2018 at 7:35 PM Ed Jaffe wrote: > On 12/28/2018 2:40 PM, David Cole wrote: > > > > I'm looking for an IBM written mapping macro for the ISPF statistics > > found in PDS directory entries. I've searched high and low, but I'm > > not having much luck. > > We had the same issue and ended up constructing our own. > > We never would have done so if an IBM macro existed... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IBM Mapping macro for ISPF statistics in PDS Directory entries?
Found it here: SYS1.SISPMACS(ISPDSTAT) .*$MAC(ISPDSTAT) COMP(04021): ISPF Directory Entry mapping macro .* .* DESCRIPTIVE-NAME = ISPF Directory Entry mapping macro -- Lionel B. Dyck (Contractor) < Mainframe Systems Programmer – RavenTek Solution Partners -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Allan Staller Sent: Monday, December 31, 2018 7:50 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: IBM Mapping macro for ISPF statistics in PDS Directory entries? Which Macro? -Original Message- From: IBM Mainframe Discussion List On Behalf Of Steve Smith Sent: Saturday, December 29, 2018 9:05 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IBM Mapping macro for ISPF statistics in PDS Directory entries? I found this macro in the ISPF maclib. It's not convenient for me to look for it now, but it should be easy to find. btw, this question was asked before... in 2004. sas On Fri, Dec 28, 2018 at 7:35 PM Ed Jaffe wrote: > On 12/28/2018 2:40 PM, David Cole wrote: > > > > I'm looking for an IBM written mapping macro for the ISPF statistics > > found in PDS directory entries. I've searched high and low, but I'm > > not having much luck. > > We had the same issue and ended up constructing our own. > > We never would have done so if an IBM macro existed... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- -- 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: Clarification on using a hardware
It is possible, despite what you mean exactly. It is possible to set up some LPAR on EC12 and start here any z/OS (or other OS) currently working on z14. It is possible to start vanilla new OS on the EC12.LPAR. Caution: possible does not mean legal. In theory starting licensed software on spare machine would cause license 'duties', even if you do that hust for fun. Good excuse could be 'cold backup' - but is it valid reason? -- Radoslaw Skorupka Lodz, Poland W dniu 2018-12-30 o 10:45, Peter pisze: Hi We recently moved from zec12 to z14 and routers all connections ,storage, tapes to the new hardware. So as of now zec12 doesn't have any workload. So it will be just active for few months. Is it possible to build an LPAR from scratch using the new machine and move it to zec12 just for a practice and training purpose ? Regards Peter -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN . == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2018 r. wynosi 169.248.488 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital City of Warsaw, 12th Commercial Division of the National Court Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 169,248,488 as at 1 January 2018. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Clarification on using a hardware
You are referring to a "architectural level set". I don’t have the details, but some OS'es will not support the hardware. Some hardware will not support the OS;es. E.G. z/OS 2.3 is not supported on z9 (I doubt it would work). z/VM is your friend. You can mimic older hardware. HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of R.S. Sent: Monday, December 31, 2018 8:42 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Clarification on using a hardware It is possible, despite what you mean exactly. It is possible to set up some LPAR on EC12 and start here any z/OS (or other OS) currently working on z14. It is possible to start vanilla new OS on the EC12.LPAR. Caution: possible does not mean legal. In theory starting licensed software on spare machine would cause license 'duties', even if you do that hust for fun. Good excuse could be 'cold backup' - but is it valid reason? -- Radoslaw Skorupka Lodz, Poland W dniu 2018-12-30 o 10:45, Peter pisze: > Hi > > We recently moved from zec12 to z14 and routers all connections ,storage, > tapes to the new hardware. > > So as of now zec12 doesn't have any workload. So it will be just active for > few months. Is it possible to build an LPAR from scratch using the new > machine and move it to zec12 just for a practice and training purpose ? > > Regards > Peter > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > . > == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,https://apac01.safelinks.protection.outlook.com/?url=www.mBank.pl&data=02%7C01%7Callan.staller%40HCL.COM%7C674f623419194970b5f508d66f2e414f%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636818641814156820&sdata=25k600URggn7NM7kVDqnHPjIiknFP%2FR%2BwChzMOWJ6MM%3D&reserved=0, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2018 r. wynosi 169.248.488 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 Warszawa,https://apac01.safelinks.protection.outlook.com/?url=www.mBank.pl&data=02%7C01%7Callan.staller%40HCL.COM%7C674f623419194970b5f508d66f2e414f%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636818641814156820&sdata=25k600URggn7NM7kVDqnHPjIiknFP%2FR%2BwChzMOWJ6MM%3D&reserved=0, e-mail: kont...@mbank.pl. District Court for the Capital City of Warsaw, 12th Commercial Division of the National Court Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 169,248,488 as at 1 January 2018. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this mess
Re: System Symbols
On Mon, 31 Dec 2018 08:29:19 +, Sean Gleann wrote: > >As for "This is the sort of thing that should be routinely provided by the >OS." - a huge YES! to that, and other associated values like 'first working >day of the week/month/year' and so on. >Its a crying shame that the only other way of getting such values in to a >jobstream - that I know of! - is by spending $many for something like CA-7 >or Tivoli. > I have routinely kept JCL wrapped in UNIX shell scripts, as here-documents (think "instream") in which I can routinely do such things with command substitution. z/OS UNIX is a boon, and the (incremental) price is right. And Peter R. has clarified that it's not customers but IBM that's advised to use SYS as a prefix. Should ISVs yet stay with registered componend prefixes? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IBM Mapping macro for ISPF statistics in PDS Directory entries?
On 12/30/2018 9:37 PM, David Cole wrote: Thanks Tom! That is exactly what I was looking for. I also want to thank a couple of people who sent me off-list messages, but they'd prefer to remain anonymous. I wondered how we never found this. The answer turned out to be a simple one. The macro never existed before 2006. $01=ZOS19 2006/05/27 HO: Created -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: System Symbols
When VTAM/SNA went to Multi Systems Networking Facility (MSNF) in the 1980s, shops suddenly needed to take the whole world into account when exposing heretofore 'private' node names. Most shops had a SYSA, which would not do when everyone began interconnecting. IBM's recommendation at the time was to prefix outward-facing node names with the SHARE installation code, such as SCE. Shops following that convention would unlikely collide with another installation. When we adopted system symbols in the 90s, we followed a similar strategy. All of our in-house symbols begin 'SCE'. Never had a conflict. Also serves to mark such symbols as home-grown. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Monday, December 31, 2018 8:01 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: System Symbols On Mon, 31 Dec 2018 08:29:19 +, Sean Gleann wrote: > >As for "This is the sort of thing that should be routinely provided by >the OS." - a huge YES! to that, and other associated values like 'first >working day of the week/month/year' and so on. >Its a crying shame that the only other way of getting such values in >to a jobstream - that I know of! - is by spending $many for something >like CA-7 or Tivoli. > I have routinely kept JCL wrapped in UNIX shell scripts, as here-documents (think "instream") in which I can routinely do such things with command substitution. z/OS UNIX is a boon, and the (incremental) price is right. And Peter R. has clarified that it's not customers but IBM that's advised to use SYS as a prefix. Should ISVs yet stay with registered componend prefixes? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: System Symbols
Batch symbols were introduced in z/OS 2.1. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Allan Staller Sent: Monday, December 31, 2018 5:49 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: System Symbols z/OS 2.2 and above allow use of system symbols in batch. See the SYSSYM=ALLOW parameter of JOBDEF and JOBCLASS in the JES manuals. HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of scott Ford Sent: Saturday, December 29, 2018 12:37 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: System Symbols Peter, Exactly. I saw the responses after I read through the manual, just wanted to make sure I understood the process before thinking about a design. In theory, we would have customer set the symbol and use the Service to query it as you had indicated. As always Peter, very much appreciated, and I learned someone again. Regards, Scott On Sat, Dec 29, 2018 at 10:15 AM Peter Relson wrote: > > Has anyone created their own system symbol and then referenced it in > HLASM ? > > > Adding system symbols is not something that a program should be doing. > IEASYMxx is the supported method for defining system symbols. > SETLOAD IEASYM is the supported method for adding a system symbol > after IPL. > > > what I am not clear on is how to have HLASM code read the system > symbol table and compare for the desired symbol.What i want to do is > if we find a specific symbol set, have a exit perform conditional logic. > > > You should not "read the system symbol table". If you want to see if a > specific symbol is set, then you should use the ASASYMBM service to > try to substitute a string that has that symbol in it and see if > substitution occurred. > > This of course is very inefficient, and unless this will happen only > once in the life of the system you would be better off doing this > once, somewhere, and stashing the result so that subsequent times can > get the result quickly. > > Peter Relson > z/OS Core Technology Design > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Scott Ford IDMWORKS z/OS Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: System Symbols
Paul, do you have a sample? (This would actually enable something for me.) Thanks, Martin Sent from my iPad > On 31 Dec 2018, at 16:01, Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > >> On Mon, 31 Dec 2018 08:29:19 +, Sean Gleann wrote: >> >> As for "This is the sort of thing that should be routinely provided by the >> OS." - a huge YES! to that, and other associated values like 'first working >> day of the week/month/year' and so on. >> Its a crying shame that the only other way of getting such values in to a >> jobstream - that I know of! - is by spending $many for something like CA-7 >> or Tivoli. >> > I have routinely kept JCL wrapped in UNIX shell scripts, as here-documents > (think "instream") in which I can routinely do such things with command > substitution. z/OS UNIX is a boon, and the (incremental) price is right. > > And Peter R. has clarified that it's not customers but IBM that's advised > to use SYS as a prefix. Should ISVs yet stay with registered componend > prefixes? > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IBM Mapping macro for ISPF statistics in PDS Directory entries?
On 12/31/2018 11:12 AM, Ed Jaffe wrote: On 12/30/2018 9:37 PM, David Cole wrote: Thanks Tom! That is exactly what I was looking for. I also want to thank a couple of people who sent me off-list messages, but they'd prefer to remain anonymous. I wondered how we never found this. The answer turned out to be a simple one. The macro never existed before 2006. $01=ZOS19 2006/05/27 HO: Created Dinosaur. Regards, Tom Conley -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
IBMLink hostage crisis over
FYI, Our long national nightmare is over. You can now go back to using www.ibmlink.ibm.com. Not sure when the hostage crisis ended, but it works again. Regards, Tom Conley -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: System Symbols
Gil, Same here I use Linux a lot , love see what you did, I do some stuff in oRexx on z/PDT ... Scott On Mon, Dec 31, 2018 at 11:54 AM Martin Packer wrote: > > Paul, do you have a sample? > > (This would actually enable something for me.) > > Thanks, Martin > > Sent from my iPad > > > On 31 Dec 2018, at 16:01, Paul Gilmartin > <000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > > >> On Mon, 31 Dec 2018 08:29:19 +, Sean Gleann wrote: > >> > >> As for "This is the sort of thing that should be routinely provided by > the > >> OS." - a huge YES! to that, and other associated values like 'first > working > >> day of the week/month/year' and so on. > >> Its a crying shame that the only other way of getting such values in to > a > >> jobstream - that I know of! - is by spending $many for something like > CA-7 > >> or Tivoli. > >> > > I have routinely kept JCL wrapped in UNIX shell scripts, as > here-documents > > (think "instream") in which I can routinely do such things with command > > substitution. z/OS UNIX is a boon, and the (incremental) price is right. > > > > And Peter R. has clarified that it's not customers but IBM that's advised > > to use SYS as a prefix. Should ISVs yet stay with registered componend > > prefixes? > > > > -- gil > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >Unless stated otherwise above: > IBM United Kingdom Limited - Registered in England and Wales with number > 741598. > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Scott Ford IDMWORKS z/OS Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: System Symbols
>>> My use of IEASYMU2 creates two 'new' system symbols 'PRYYMMDD' and >
'PRYYDDD' after IPL, but then I change the values in those symbols at about
> 00:01 each day.
Sean,
DFSORT can calculate any date in both greogorian and Julian format. A
Simple DATE1-1 will get you yesterday's date in Gregorian format as
CCYYMMDD format and DATE3-1 will get you yesterday's date in Julian format
as CCYYDDD.
Here is a sample to generate various date related symbols
//STEP0100 EXEC PGM=SORT
//SYSOUT DD SYSOUT=*
//SORTIN DD *
SAMPLE
//SORTOUT DD SYSOUT=*
//SYSINDD *
OPTION COPY
INREC BUILD=(DATE1,X,DATE1-1)
OUTFIL BUILD=(C'CURRDATE IN GREGORIAN FORMAT :',DATE1,/,
C'CURRDATE IN JULIAN FORMAT:',DATE3,/,
C'CURRENT DAY OF WEEK :',
01,8,Y4T,WEEKDAY=CHAR9,/,
C'CURRENT WEEK NUMBER IN USA :',
01,8,Y4T,WEEKNUM=USA,/,
C'LASTDAY OF CURRENT WEEK(GREGORIAN) :',
01,8,Y4T,LASTDAYW,TOGREG=Y4T,/,
C'LASTDAY OF CURRENT MONTH(GREGORIAN) :',
01,8,Y4T,LASTDAYM,TOGREG=Y4T,/,
C'LASTDAY OF CURRENT QUARTER(GREGORIAN):',
01,8,Y4T,LASTDAYQ,TOGREG=Y4T,/,
C'LASTDAY OF CURRENT YEAR(GREGORIAN) :',
01,8,Y4T,LASTDAYY,TOGREG=Y4T,/,
C'LASTDAY OF CURRENT WEEK(JULIAN) :',
01,8,Y4T,LASTDAYW,TOJUL=Y4T,/,
C'LASTDAY OF CURRENT MONTH(JULIAN) :',
01,8,Y4T,LASTDAYM,TOJUL=Y4T,/,
C'LASTDAY OF CURRENT QUARTER(JULIAN) :',
01,8,Y4T,LASTDAYQ,TOJUL=Y4T,/,
C'LASTDAY OF CURRENT YEAR(JULIAN) :',
01,8,Y4T,LASTDAYY,TOJUL=Y4T,/,
C'YESTERDAY IN GREGORIAN FORMAT:',DATE1-1,/,
C'YESTERDAY IN JULIAN FORMAT :',DATE3-1,/,
C'YESTERDAY DAY OF WEEK:',
10,8,Y4T,WEEKDAY=CHAR9,/,
C'YESTERDAY WEEK NUMBER IN USA :',
10,8,Y4T,WEEKNUM=USA,80:X)
//*
The output of this is
CURRDATE IN GREGORIAN FORMAT :20181231
CURRDATE IN JULIAN FORMAT:2018365
CURRENT DAY OF WEEK :MONDAY
CURRENT WEEK NUMBER IN USA :53
LASTDAY OF CURRENT WEEK(GREGORIAN) :20190104
LASTDAY OF CURRENT MONTH(GREGORIAN) :20181231
LASTDAY OF CURRENT QUARTER(GREGORIAN):20181231
LASTDAY OF CURRENT YEAR(GREGORIAN) :20181231
LASTDAY OF CURRENT WEEK(JULIAN) :2019004
LASTDAY OF CURRENT MONTH(JULIAN) :2018365
LASTDAY OF CURRENT QUARTER(JULIAN) :2018365
LASTDAY OF CURRENT YEAR(JULIAN) :2018365
YESTERDAY IN GREGORIAN FORMAT:20181230
YESTERDAY IN JULIAN FORMAT :2018364
YESTERDAY DAY OF WEEK:SUNDAY
YESTERDAY WEEK NUMBER IN USA :53
> As for "This is the sort of thing that should be routinely provided by
the
> OS." - a huge YES! to that, and other associated values like 'first
working
> day of the week/month/year' and so on.
> Its a crying shame that the only other way of getting such values in to
a
> jobstream - that I know of! - is by spending $many for something like
CA-7
> or Tivoli.
DFSORT has a plethora of functions that can do what you asked for any given
date.
NEXTDSUN calculates the next Sunday for a date field.
NEXTDMON calculates the next Monday for a date field.
NEXTDTUE calculates the next Tuesday for a date field.
NEXTDWED calculates the next Wednesday for a date field.
NEXTDTHU calculates the next Thursday for a date field.
NEXTDFRI calculates the next Friday for a date field.
NEXTDSAT calculates the next Saturday for a date field.
PREVDSUN calculates the previous Sunday for a date field.
PREVDMON calculates the previous Monday for a date field.
PREVDTUE calculates the previous Tuesday for a date field.
PREVDWED calculates the previous Wednesday for a date field
PREVDTHU calculates the previous Thursday for a date field.
PREVDFRI calculates the previous Friday for a date field.
PREVDSAT calculates the previous Saturday for a date field.
LASTDAYW calculates the last Friday of the week for a date field.
LASTDAYM calculates the last day of the month for a date field.
LASTDAYQ calculates the last day of the quarter for a date field.
LASTDAYY calculates the last day of the year for a date field.
ADDDAYS, ADDMONS or ADDYEARS can be used to add days, months or years to a
date field.
SUBDAYS, SUBMONS or SUBYEARS can be used to subtract days, months or years
from a date field.
DATEDIFF can be used to calculate the number of days between two date
fields.
Check this white paper which explains in detail ab
Re: System Symbols
On Mon, 31 Dec 2018 16:54:08 +, Martin Packer wrote: > >Paul, do you have a sample? > >(This would actually anable something for me.) > I have nothing in use that I can share, but something like: #! /bin/sh -x submit <
Re: System Symbols
We have our own CI, using GIT, she and rspec, so I am always curious on
technique Gil, thx.
Scott
On Mon, Dec 31, 2018 at 1:10 PM Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Mon, 31 Dec 2018 16:54:08 +, Martin Packer wrote:
>
> >
> >Paul, do you have a sample?
> >
> >(This would actually anable something for me.)
> >
> I have nothing in use that I can share, but something like:
>
> #! /bin/sh -x
>
> submit < //${LOGNAME}A JOB ...
> //STEP EXEC PGM=IEBGENER
> //SYSUT2 DDDSN=${LOGNAME}.$( date "+D%y%m%d.T%H%M%S" ).OUTPUT,...
> ...
> //
> end-of-jcl
>
> (For the current day. Yes, previous working day is harder.)
>
> -- gil
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
--
Scott Ford
IDMWORKS
z/OS Development
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Crosshair cursor
I do. From: IBM Mainframe Discussion List on behalf of zMan Sent: Saturday, December 29, 2018 10:46 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Crosshair cursor Does anybody here voluntarily use a crosshair cursor in your 3270 emulator? -- zMan -- "I've got a mainframe and I'm not afraid to use it" -- 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: Crosshair cursor
Happy New Year all On Mon, Dec 31, 2018 at 2:56 PM Frank Swarbrick wrote: > I do. > > > From: IBM Mainframe Discussion List on behalf > of zMan > Sent: Saturday, December 29, 2018 10:46 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Crosshair cursor > > Does anybody here voluntarily use a crosshair cursor in your 3270 emulator? > -- > zMan -- "I've got a mainframe and I'm not afraid to use it" > > -- > 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 > -- Scott Ford IDMWORKS z/OS Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Clarification on using a hardware
No, and no. No, there is no z/OS system which work on z14, but would not work on EC12. Note: z9 is different (much older) animal - it is not possible to IPL z/OS 2.2+ (I'm not sure about 2.1) on z9. BUT THIS IS NOT THE CASE. No, I don't refer to any "ALS". To be precise, for any mainframe OS there's a version which is supported on both z14 and EC12. At least, the most current z/OS (2.3) and z/VM (7.1), and z/VSE (6.2) , and RHEL (7) do support both z 14 (obvious) and EC12. I'm not sure about z/TPF and other Linux distros, but I believe this is also the case. In other words, it would be very hard to run any OS on z14 while the same OS does not support EC12. Regards -- Radoslaw Skorupka Lodz, Poland W dniu 2018-12-31 o 15:53, Allan Staller pisze: You are referring to a "architectural level set". I don’t have the details, but some OS'es will not support the hardware. Some hardware will not support the OS;es. E.G. z/OS 2.3 is not supported on z9 (I doubt it would work). z/VM is your friend. You can mimic older hardware. HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of R.S. Sent: Monday, December 31, 2018 8:42 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Clarification on using a hardware It is possible, despite what you mean exactly. It is possible to set up some LPAR on EC12 and start here any z/OS (or other OS) currently working on z14. It is possible to start vanilla new OS on the EC12.LPAR. Caution: possible does not mean legal. In theory starting licensed software on spare machine would cause license 'duties', even if you do that hust for fun. Good excuse could be 'cold backup' - but is it valid reason? -- Radoslaw Skorupka Lodz, Poland W dniu 2018-12-30 o 10:45, Peter pisze: Hi We recently moved from zec12 to z14 and routers all connections ,storage, tapes to the new hardware. So as of now zec12 doesn't have any workload. So it will be just active for few months. Is it possible to build an LPAR from scratch using the new machine and move it to zec12 just for a practice and training purpose ? Regards Peter == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2018 r. wynosi 169.248.488 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital City of Warsaw, 12th Commercial Division of the National Court Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 169,248,488 as at 1 January 2018. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: System Symbols
On Mon, 31 Dec 2018 at 11:40, Jesse 1 Robinson wrote: When VTAM/SNA went to Multi Systems Networking Facility (MSNF) in the > 1980s, shops suddenly needed to take the whole world into account when > exposing heretofore 'private' node names. Most shops had a SYSA, which > would not do when everyone began interconnecting. > > IBM's recommendation at the time was to prefix outward-facing node names > with the SHARE installation code, such as SCE. Shops following that > convention would unlikely collide with another installation. > In the mid 1990s, when SNA interconnection between enterprises was at its peak, IBM had an SNA network name registry. (For all I know they may still have it.) Names were of the form , so e.g. IBM itself was USIBM (and CAIBM or whatever you were connecting to). I wonder if USCAD was ever registered... Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Network names (was: System Symbols)
On Mon, 31 Dec 2018 16:00:02 -0500, Tony Harminc wrote: > >In the mid 1990s, when SNA interconnection between enterprises was at its >peak, IBM had an SNA network name registry. (For all I know they may still >have it.) Names were of the form character customer code>, so e.g. IBM itself was USIBM (and CAIBM or >whatever you were connecting to). I wonder if USCAD was ever registered... > Sounds like a tiny step in the direction of a DNS. I've long wondered whether a robust DNS would have enabled SNA to compete better with TCP/IP. Or was price a determining factor? Was EBCDIC vs. ASCII ever a concern? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: System Symbols
Tony, Yep we did that also, when put out networks in. It took to build a schema flexible enough to support 56 Internaltional sites and all their LUs. Scott On Mon, Dec 31, 2018 at 4:00 PM Tony Harminc wrote: > On Mon, 31 Dec 2018 at 11:40, Jesse 1 Robinson > wrote: > > When VTAM/SNA went to Multi Systems Networking Facility (MSNF) in the > > 1980s, shops suddenly needed to take the whole world into account when > > exposing heretofore 'private' node names. Most shops had a SYSA, which > > would not do when everyone began interconnecting. > > > > IBM's recommendation at the time was to prefix outward-facing node names > > with the SHARE installation code, such as SCE. Shops following that > > convention would unlikely collide with another installation. > > > > In the mid 1990s, when SNA interconnection between enterprises was at its > peak, IBM had an SNA network name registry. (For all I know they may still > have it.) Names were of the form character customer code>, so e.g. IBM itself was USIBM (and CAIBM or > whatever you were connecting to). I wonder if USCAD was ever registered... > > Tony H. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Scott Ford IDMWORKS z/OS Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Crosshair cursor
No cross-hairs for me (in this context). I think it looks hideodeous. If I don't know where the cursor is, I just put it where I want it to be. Now I have experience with all kinds of sysprogs and sysadmins that love to restrict every feature and impose their will on every possible option; but haven't seen anyone dictate a particular cursor yet. Hopefully my present shop won't get any ideas. fwiw, I've used Bluezone for years, and I like it. The latest versions have sorted out the options nightmare it used to have -- at least somewhat. sas ... > > > > From: IBM Mainframe Discussion List on behalf > > of zMan > > Sent: Saturday, December 29, 2018 10:46 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Crosshair cursor > > > > Does anybody here voluntarily use a crosshair cursor in your 3270 > emulator? > > -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Crosshair cursor
I have never liked the distraction of a crosshair cursor. The one exception was 3 decades ago, using a 4-in-1 3290 screen in the ops bridge, where it was sometimes not easy to keep track of which of the 4 screens was 'active', which the crosshair did actually make it a lot more obvious than the usual blob cursor did. On Mon, 31 Dec 2018 at 23:23, Steve Smith wrote: > No cross-hairs for me (in this context). I think it looks hideodeous. If > I don't know where the cursor is, I just put it where I want it to be. > > Now I have experience with all kinds of sysprogs and sysadmins that love to > restrict every feature and impose their will on every possible option; but > haven't seen anyone dictate a particular cursor yet. Hopefully my present > shop won't get any ideas. > > fwiw, I've used Bluezone for years, and I like it. The latest versions > have sorted out the options nightmare it used to have -- at least somewhat. > > sas > > ... > > > > > > > From: IBM Mainframe Discussion List on > behalf > > > of zMan > > > Sent: Saturday, December 29, 2018 10:46 AM > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > Subject: Crosshair cursor > > > > > > Does anybody here voluntarily use a crosshair cursor in your 3270 > > emulator? > > > -- > > -- > 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
