Re: Friday Follies/Why won't this work?/TSO Rant #387
Metz wrote: >Well, I've only been using REXX for 35 years. The problems that I have seen >from not quoting words have been few and far between, not nearly as many as, >e.g., problems related to continuation, omitting a period in a stem, incorrect >capitalization in a string literal. You seem stuck on this capitalization thing. I’ve never had such a problem, perhaps because I capitalize literals as needed. I’d never assume that mixed case in a literal is OK unless it’s deliberate, no matter the environment. Part of my Rexx Programming Style presentation, given at SHARE many times! I have seen nasty bugs from not quoting literals, not to mention the performance hit. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to get last node in DFSORT
That sounds like a great use case for regexen. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Billy Ashton [bill00ash...@gmail.com] Sent: Friday, May 22, 2020 3:57 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: How to get last node in DFSORT Hi folks! This should be easy, but it escapes me... I have an 80-byte LRECL list of filenames (starting in col 1, varying lengths), and I need to capture just the last node of the file, and store it as a separate word on the record, in col 51. For example, if the file has JOSEPH.CONTROL.SAMPLIB.JCL PRODUCTION.CONTROL.VSAM.DATABASE.INDEX I would like the records to be JOSEPH.CONTROL.SAMPLIB.JCL(now here 24 spaces)JCL PRODUCTION.CONTROL.VSAM.DATABASE.INDEX(12 spaces)INDEX I expect I can use a Parse statement, but not sure how to get the last occurrence of something... Thanks for your help! Billy -- 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: Friday Follies/Why won't this work?/TSO Rant #387
Well, I've only been using REXX for 35 years. The problems that I have seen from not quoting words have been few and far between, not nearly as many as, e.g., problems related to continuation, omitting a period in a stem, incorrect capitalization in a string literal. BTDT,GTS -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Phil Smith III [li...@akphs.com] Sent: Friday, May 22, 2020 8:47 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Friday Follies/Why won't this work?/TSO Rant #387 Metz wrote: > Running with signal on novalue and quoting everything leads to hard-to-debug > surprises errors when you get the case wrong (present example is typical.) ;-) After almost 40 years of writing Rexx, I've never had that problem. Quoting literals avoids far more problems than it causes, as does SIGNAL ON NOVALUE. You want hard-to-debug surprises, try not quoting a literal and then having someone define a variable that happens to match your literal token. ...phsiii -- 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: Friday Follies/Why won't this work?/TSO Rant #387
This is great David, thank you kind sir On Sat, May 23, 2020 at 3:54 AM David Crayford wrote: > On 2020-05-23 3:20 AM, scott Ford wrote: > > I got bit on case and end of line characters using GIT. I was using > > Notepad++ and had the EOL set incorrectly, duh ! > > > Create a .gitattributes file to control line endings > https://www.edwardthomson.com/blog/git_for_windows_line_endings.html > > > > Scott > > > > On Fri, May 22, 2020 at 3:10 PM Seymour J Metz wrote: > > > >> While I started with upper case only languages and progressed to case > >> independent languages, there is a case for case dependent languages. It > >> helps if you have a good IDE. > >> > >> > >> -- > >> Shmuel (Seymour J.) Metz > >> http://mason.gmu.edu/~smetz3 > >> > >> > >> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on > behalf > >> of Steve Smith [sasd...@gmail.com] > >> Sent: Friday, May 22, 2020 3:00 PM > >> To: IBM-MAIN@LISTSERV.UA.EDU > >> Subject: Re: Friday Follies/Why won't this work?/TSO Rant #387 > >> > >> Case sensitivity is the root of all evil. > >> > >> sas > >> > >> Disclaimer: The above may contain excessive generalization, hyperbole, > and > >> offend your sensibilities. I'd say I'm sorry, but that would just add > >> flat-out lying to the mix. > >> > >> -- > >> For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >> > >> -- > >> For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >> > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- 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: IODF Activation Question - Followup
W dniu 22.05.2020 o 17:42, Dana Mitchell pisze: On Fri, 22 May 2020 14:10:02 +0200, R.S. wrote: Personally I used to start with "the last system" - that means HSA update, and then ACTIVATE SOFT on rest, however the "more recommended" way is the above. Did this actually work this way? Seems to me that the hardware & software activate on the first lpar would make the rest of the systems think they are out of sync and would refuse to even do a software only activate? Its been a while since I tried it Dana Yes, it does. I'm pretty sure about it, I did it many times. A lot of. BTW: just try this. My humble opinion: people tend to think IODF ACTIVATE is dangerous. It isn't. In most cases the ACTIVATE will not work due to some reasons. Adding devices is safe. Removing or altering devices require the devices (or channels) to be offline. Offlined device is not used by any application (with exception to FDR and similar). IMHO the most important risk is to have a system out of sync with HSA, which can be fixed dynamically when the system was in sync. For fresh-IPLed system the solution is to re-IPL. Disclaimers (fine print): I did not considered parallel sysplex things like CF and sysplex links No responsibility... -- Radoslaw Skorupka Lodz, Poland == 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.2020 r. wynosi 169.401.468 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.401.468 as at 1 January 2020. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 2.3 systems show OPI=YES
...one level 1 support tech actually told me what you had said, not documented that way but then why would it . The behavior of OPI= is (I think quite clearly) documented. There is a lengthy note. The documentation describes the default and the behavior from one IEASYSxx to another. You apparently made an assumption about what Mark Z's IPLINFO showed (which is similar to what DISPLAY IPLINFO,OPI would have showed -- so not picking on Mark's program). And if you have a need to be able to tell what it sounds like you're trying to tell (No use of OPI for individual, no use of OPI=YES), then that is what RFE's are for. 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: Schema will not load
Thank you, Joe. We checked security but it wasn’t. What we found was the coder had Left a sequence number at the end of a line And since it was longer than 80 bytes we didn’t see it until I hit the Pf11 key in my ispf edit and saw the numbers. Crazy stuff looked at it for a couple of days. Thanks. On Sat, May 16, 2020 at 5:26 PM Joe Monk wrote: > Could it be permissions? RACF? The userid that youre using in production > doesnt have permissions to load some element in the XML schema? > > Joe > > > > On Sat, May 16, 2020 at 3:59 PM Roberto Halais > wrote: > > > Listers: > > I am already at the end of searches and reading. > > We have a batch job that connects to an external site using XML. > > It works well in our test environment but we are getting an error when we > > execute in production. > > I have googled but haven't had any luck. > > Any idea would be welcomed. > > Thank you. > > When we try to execute we get the following: > > == NEW PAGE > > OSR file: /APPL/LCR/DOEP_eFile.osr > > Number of schemas: 1 > > Schema file: /APPL/LCR/FinCEN_DOEP_eFile.xsd > > > > 0100 > > Ý--- Calling gxluInitOSRG ---¨ > > Ý--- Calling gxluLoadSchema ---¨ #1 > > FATAL - gxluLoadSchema Failure: Reason Code 7067 > > Ý--- Calling gxluControlOSRG ---¨ > > 0 == Diagnostic Area: Begin == > > OIMA Address: 21e36f80 > > Last Return Code: 10 > > Last Reason Code: 7067 > > StringID Return Code: 0 > > StringID Reason Code: 0 > > Java Exception Condition Code: 0 > > Number of Error Messages: 0 > > Custom Message: > > Java Exception Messages: > > :::@ycol: /APPL/LCR/FinCEN_DOEP_eFile.xsd > > d == > > Ý--- Calling gxluTermOSRG ---¨ > > = NEW PAGE > > Options Report for Enclave main 05/15/20 8:33:15 PM > > Language Environment V02 R02.00 > > > > -- > > 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 > -- Politics: Poli (many) - tics (blood sucking parasites) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Friday Follies/Why won't this work?/TSO Rant #387
On 2020-05-23 3:20 AM, scott Ford wrote: I got bit on case and end of line characters using GIT. I was using Notepad++ and had the EOL set incorrectly, duh ! Create a .gitattributes file to control line endings https://www.edwardthomson.com/blog/git_for_windows_line_endings.html Scott On Fri, May 22, 2020 at 3:10 PM Seymour J Metz wrote: While I started with upper case only languages and progressed to case independent languages, there is a case for case dependent languages. It helps if you have a good IDE. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Steve Smith [sasd...@gmail.com] Sent: Friday, May 22, 2020 3:00 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Friday Follies/Why won't this work?/TSO Rant #387 Case sensitivity is the root of all evil. sas Disclaimer: The above may contain excessive generalization, hyperbole, and offend your sensibilities. I'd say I'm sorry, but that would just add flat-out lying to the mix. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
