I just double-checked the latest report I submitted with comments added to my mainframe CSV file, and the comments are on the report on the LMS site.
Rex -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Pommier, Rex Sent: Thursday, February 23, 2023 4:10 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [EXTERNAL] Re: SCRT and not operating LPAR With all due respect, I have to disagree. Granted I haven't had to make any explanations to LMS since IBM took away the FTP transmission and required us to go through the web site for transmissions, but before that I would add my comments to the mainframe version of the CSV and then directly FTP it from the mainframe to LMS, all without any issues. I have the prior 12 months' worth of SCRT reports on the mainframe and I found where I had commented in at least 3 of these reports and didn't have IBM reject any of them. Unless, of course, IBM was silently rejecting them Rex -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Radoslaw Skorupka Sent: Thursday, February 23, 2023 3:58 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [EXTERNAL] Re: SCRT and not operating LPAR You cannot update CSV file. There is a checksum at the bottom. Any update, including such comment causes the file will not be accepted by the LMS. BTDT. Of course it is possible to upload the file to LMS and then add explanations. But then IBM knows the rest of file is not amended. BTW: I'm pretty sure of the above. I had plenty Activated, but Not operating LPARs in my former shop and the reports did not require any explanation for that. It was kind of cloud or "on demand provisioning" - we created system + application instances on demand. A lot of them, quite frequently. The problem occured when someone forgot to archive SMF data before system shutdown and scratch. However it was slightly another scenario - LPAR was both Active and Operating, but some records were lost. Of course the rules may have changed. For example in the past it was acceptable to collect 95% (time) SMF data, but the SCRT tool could not accept duplicate SMF IDs. Now it's the opposite - any SMF loss causes explanations requirement, but SMF ID need not to be unique any longer. -- Radoslaw Skorupka Lodz, Poland W dniu 23.02.2023 o 21:33, Pommier, Rex pisze: > Hi John, > > Actually I think you remembered right the first time. :-) When our sandbox > is down for an extended period, I get the "(required)" in the CSV file as > well. I just change "(required)" with "LPAR down for refresh" or whatever > reason the LPAR isn't reporting SMF data and then send the CSV in. The only > times I recall having to fix the data once it gets to IBM is when I forgot to > update the CSV before submitting it. > > Rex > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > Behalf Of John McKown > Sent: Thursday, February 23, 2023 12:33 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [EXTERNAL] Re: SCRT and not operating LPAR > > Misremembered. The CVS file says "(required)". When uploaded to IBM there is > a prompt, in red, to fill the field in. That's when I enter "not in use". > > On Thu, Feb 23, 2023, 04:52 John McKown <john.archie.mck...@gmail.com> > wrote: > >> We have this situation. There is a REMARKS field in the SCRT cvs file. >> I put the sentence "No longer in use." in that field during the >> generation of it on my Windows desktop. I've done that for years now >> with no problems with IBM. >> >> On Thu, Feb 23, 2023, 04:05 Radoslaw Skorupka < >> 00000471ebeac275-dmarc-requ...@listserv.ua.edu> wrote: >> >>> As it is known, all the z/OS LPAR have to report SMF data to SCRT >>> otherwise SCRT report would contain "data missing" field for given >>> LPAR and explanation will be required. >>> What about not operating LPARs? >>> I mean an LPAR which is Activated, but not IPLed. Or the OS was shut >>> down and LPAR was reset (but still remain active). >>> >>> AFAIR there was no problem with not operating LPARs in the past - >>> that mean the LPARs were not included in the report. >>> However It seems something changed and now such LPAR will cause >>> "data missing" issue. >>> >>> Any clue? >>> >>> >>> -- >>> Radoslaw Skorupka >>> Lodz, Poland >>> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
