Radoslaw, Rest assured that your post elicited only admiration. Most of us are familiar with the noun 'anathema', which allowed us to decode the verb formation with minimal effort. I was also impressed that Windows 10 spell checker did not blink over the verb. I cannot promise to follow my granddaughter's endearing practice of sprinkling my daily conversation with this cool new word--although it is political campaign season here, so opportunities may arise. 😉
-----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of R.S. Sent: Thursday, October 3, 2019 4:57 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Planned ESQA change and HealthCheck Jesse, It is English word, taken from dictionary. Actually it has Latin root, and the word is similar to Polish "anatema" which mean "klątwa" (noun) and also has Latin roots. BTW: my dictionary (bab.la) says that "klątwa" in English is "curse" or "anathema". And Polish "anatema" is ..."anathema". So, I see no mistake in using "anathematized". I also sustain my words about HealthChecker quick and dirty procedure. Yes, there is a risk of anathema... Regards -- Radoslaw Skorupka Lodz, Poland W dniu 2019-10-01 o 18:38, Jesse 1 Robinson pisze: > I stand in awe of the Polish guru who can both entertain and educate. > Including English vocabulary. No anathematization here. > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of > R.S. > Sent: Tuesday, October 1, 2019 7:24 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):Re: Planned ESQA change and HealthCheck > > (I will be anathematized for the text below) Simple solution: > stop HZSPROC > delete HZSDATA dataset > create it again using plain IEFBR14 or any other method - just empty PS > dataset start HZSPROC > > It works. No animal will be injured by deletion of the dataset. No climate > change will happen when you create new dataset using cursed method as the > above. Some prophets say it may happen badly, but it had never happened yet... > > > -- > Radoslaw Skorupka > Lodz, Poland > > > > > > > W dniu 2019-10-01 o 13:25, Jousma, David pisze: >> Ok, I answered the first question. How to get it back, F HZSPROC,ADDNEW. >> But how do I reset the history is still outstanding. >> >> Thanks, Dave >> >> _____________________________________________________________________________________________________ >> Dave Jousma >> AVP | Manager, Systems Engineering >> >> Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, >> MI 49546 >> 616.653.8429 | fax: 616.653.2717 >> >> >> -----Original Message----- >> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of >> Jousma, David >> Sent: Tuesday, October 1, 2019 7:20 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Planned ESQA change and HealthCheck >> >> **CAUTION EXTERNAL EMAIL** >> >> **DO NOT open attachments or click on links from unknown senders or >> unexpected emails** >> >> Ok, This is one of those dumb moments...IPLed one of my tech systems last >> night with a planned increase of ESQA. The associated health check popped >> after the IPL CHECK(IBMVSM,VSM_CSA_CHANGE) because of the decrease in EPVT. >> It's not clear to me how to reset the history for this healthcheck so that >> it doesn't show as a critical problem. In my guessing, I ended up deleting >> that check. >> >> So how do I get it back(short of IPLing), and how do I reset the history >> since this was a planned change? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
