Re: TS7740 and VTS B20
W dniu 2012-11-28 10:08, David Devine pisze: Hello again. Forgot to mention that it's not just HSM with it's own internal tape catalog you need to watch out for, there are some report archiving products that have it too. Migration of HSM data is a piece of cake. RECYCLE is your friend. -- Radoslaw Skorupka Lodz, Poland -- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2012 r. kapitał zakładowy BRE Banku SA (w całości wpłacony) wynosi 168.410.984 złotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Makes me love most of my z/OS software vendors.
Contact Joe Smith by telephone at (XXX) YYY- extension QQQ or his backup Sally Carter at extension RRR. Tring The number you dialed is not available because it is not paid up, cable is stolen, or the operator is asleep or drunk or needing a bribe. Please retry again later! Your call has been billed $9.11 and thank you for calling. Goodbye. ;-D Is it already Friday now? Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Anything to read on MetaCOBOL
Hi, I have come across a system which uses MetaCOBOL (CA product) and needs to be migrated to COBOL. Before suggesting any solution wanted to read on MetaCOBOL, but coludn't find anything on the internet. If someone has any pdfs/articles that could help, please share. Adarsh -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Anything to read on MetaCOBOL
adarsh khanna wrote: I have come across a system which uses MetaCOBOL (CA product) and needs to be migrated to COBOL. Where to what vendor of COBOL? On what system is that COBOL whereto you want to migrate? Oh yes, migration of programs is one thing. Data migration is another thing. What about migration of your data (input and output) and storage mediums of that data? Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Anything to read on MetaCOBOL
GIYF. www.move2open.com/metacobol-to-cobol.html http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14509093tstart=0 ftp://scftpd.ca.com/comp/R105M+11QAP.pdf ftp://scftpd.ca.com/comp/R205M+11UGP.pdf www.linkedin.com/groups/MetaCOBOL-Users-3267927/about HTH.. adarsh khanna wrote: I have come across a system which uses MetaCOBOL (CA product) and needs to be migrated to COBOL. Where to what vendor of COBOL? On what system is that COBOL whereto you want to migrate? Oh yes, migration of programs is one thing. Data migration is another thing. What about migration of your data (input and output) and storage mediums of that data? Groete / Greetings Elardus Engelbrecht -- 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
Extended Format ZFS's and Indirect volser support
This might be a silly question, but does the indirect volser support for zFS's work with SMS managed extended format zFS files? -- Mark Jacobs Time Customer Service Tampa, FL The quiet ones are the ones that change the universe... The loud ones only take the credit. Londo Mollari - Babylon 5 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Anything to read on MetaCOBOL
MetaCOBOL to IBM Z/OS Enterprise COBOL. Requirement is to keep the as-is functionality. Any tools that could be helpful? Regs Adarsh From: Elardus Engelbrecht elardus.engelbre...@sita.co.za To: IBM-MAIN@LISTSERV.UA.EDU Sent: Friday, 30 November 2012 6:14 PM Subject: Re: Anything to read on MetaCOBOL adarsh khanna wrote: I have come across a system which uses MetaCOBOL (CA product) and needs to be migrated to COBOL. Where to what vendor of COBOL? On what system is that COBOL whereto you want to migrate? Oh yes, migration of programs is one thing. Data migration is another thing. What about migration of your data (input and output) and storage mediums of that data? Groete / Greetings Elardus Engelbrecht -- 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
Changing PMR Severity (Was: Makes me love most of my z/OS software vendors)
On 11/29/2012 10:55 PM, Timothy Sipples wrote: Nevertheless, you are allowed to mark the problem incident as Severity 1 whenever you have somebody on shift.(*) Therefore it's possible to have your first qualified support person come in at, say, 8:00 a.m. and raise the PMR to Severity 1. Then, as your last qualified support person turns the lights out, that person lowers the PMR to Severity 2 (or lower if appropriate). Loop, repeat if necessary. That's entirely within the rules and even expected/recommended if you have a problem requiring Severity 1 attention from IBM. Interesting concept. Is this a common practice? Is anyone on IBM-MAIN routinely doing this? -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Changing PMR Severity (Was: Makes me love most of my z/OS software vendors)
On 11/30/2012 10:53 AM, Edward Jaffe wrote: On 11/29/2012 10:55 PM, Timothy Sipples wrote: Nevertheless, you are allowed to mark the problem incident as Severity 1 whenever you have somebody on shift.(*) Therefore it's possible to have your first qualified support person come in at, say, 8:00 a.m. and raise the PMR to Severity 1. Then, as your last qualified support person turns the lights out, that person lowers the PMR to Severity 2 (or lower if appropriate). Loop, repeat if necessary. That's entirely within the rules and even expected/recommended if you have a problem requiring Severity 1 attention from IBM. Interesting concept. Is this a common practice? Is anyone on IBM-MAIN routinely doing this? Ed, I've done that, especially when it was time for all of us to get some sleep and recharge. 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: Changing PMR Severity (Was: Makes me love most of my z/OS software vendors)
I've at times been asked by IBM to raise the severity to get attention - and later lowered it - but I have generally used the willingness of the support teams and client to be available 24x7 (in addition to technical knowledge of the problem, symptoms, impact) as a 'test' of a true Severity 1... If it is that important, they should be available... That certainly can include giving IBM (or other vendors) ways to contact our problem owner (cell, home, etc) - and not sitting watching for updates as the vendor is researching an issue... but available quickly if they need additional doc or information. The problem owner has the contact info for all the other groups involved. I also clearly spell out our expectations for vendor updates and coverage in the record - so there is no confusion. I try to use the severities to reflect the true problem impact - and reserve Sev 1 for those cases where we are truly down or seriously impacted or repeat occurrences. Sev 2 is still high priority - but normal business hours only - for those that don't warrant 'around the clock'. Many times a requested Sev 1 suddenly becomes a 2 or 3 when asking the reporter for 24x7 coverage (not end user... - but applications, dba, software) (There is sometimes a need for a 'political Sev 1' - but in general I try to let the realities of the impact dictate...) Thanks! Greg Cardillo Email: gregory.cardi...@hp.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Thomas Conley Sent: Friday, November 30, 2012 11:23 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Changing PMR Severity (Was: Makes me love most of my z/OS software vendors) On 11/30/2012 10:53 AM, Edward Jaffe wrote: On 11/29/2012 10:55 PM, Timothy Sipples wrote: Nevertheless, you are allowed to mark the problem incident as Severity 1 whenever you have somebody on shift.(*) Therefore it's possible to have your first qualified support person come in at, say, 8:00 a.m. and raise the PMR to Severity 1. Then, as your last qualified support person turns the lights out, that person lowers the PMR to Severity 2 (or lower if appropriate). Loop, repeat if necessary. That's entirely within the rules and even expected/recommended if you have a problem requiring Severity 1 attention from IBM. Interesting concept. Is this a common practice? Is anyone on IBM-MAIN routinely doing this? Ed, I've done that, especially when it was time for all of us to get some sleep and recharge. Regards, Tom Conley -- 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: Changing PMR Severity (Was: Makes me love most of my z/OS software vendors)
I won't do that. It's a double edged sword. I've had my management tell me to make something a SEV1, I *think* mostly because it's important to them, or maybe impatience. My stock answer is always, if it's a SEV1, I have to do anything to resolve it, up to and including disrupting the system further. A true SEV1 in my book is something of a crippling nature, that you work around the clock on until fixed or a workaround is in place, at which time, the problem is no longer a SEV1. If I expect my vendors to work around the clock, then I better be prepared to as well, otherwise it is not a SEV1. Making it a SEV1 just to get priority response is bad form, and tends to get ignored in the future by the same vendors. _ Dave Jousma Assistant Vice President, Mainframe Engineering david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Changing PMR Severity (Was: Makes me love most of my z/OS software vendors)
To me, and to every shop I've ever worked at, SEV 1 means we're dead and we are all staying here until we are working again. One time, this meant a 36 hour shift for all 3 sysprogs. I was much younger then. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Cardillo, Gregory Sent: Friday, November 30, 2012 11:55 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Changing PMR Severity (Was: Makes me love most of my z/OS software vendors) I've at times been asked by IBM to raise the severity to get attention - and later lowered it - but I have generally used the willingness of the support teams and client to be available 24x7 (in addition to technical knowledge of the problem, symptoms, impact) as a 'test' of a true Severity 1... If it is that important, they should be available... That certainly can include giving IBM (or other vendors) ways to contact our problem owner (cell, home, etc) - and not sitting watching for updates as the vendor is researching an issue... but available quickly if they need additional doc or information. The problem owner has the contact info for all the other groups involved. I also clearly spell out our expectations for vendor updates and coverage in the record - so there is no confusion. I try to use the severities to reflect the true problem impact - and reserve Sev 1 for those cases where we are truly down or seriously impacted or repeat occurrences. Sev 2 is still high priority - but normal business hours only - for those that don't warrant 'around the clock'. Many times a requested Sev 1 suddenly becomes a 2 or 3 when asking the reporter for 24x7 coverage (not end user... - but applications, dba, software) (There is sometimes a need for a 'political Sev 1' - but in general I try to let the realities of the impact dictate...) Thanks! Greg Cardillo Email: gregory.cardi...@hp.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Thomas Conley Sent: Friday, November 30, 2012 11:23 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Changing PMR Severity (Was: Makes me love most of my z/OS software vendors) On 11/30/2012 10:53 AM, Edward Jaffe wrote: On 11/29/2012 10:55 PM, Timothy Sipples wrote: Nevertheless, you are allowed to mark the problem incident as Severity 1 whenever you have somebody on shift.(*) Therefore it's possible to have your first qualified support person come in at, say, 8:00 a.m. and raise the PMR to Severity 1. Then, as your last qualified support person turns the lights out, that person lowers the PMR to Severity 2 (or lower if appropriate). Loop, repeat if necessary. That's entirely within the rules and even expected/recommended if you have a problem requiring Severity 1 attention from IBM. Interesting concept. Is this a common practice? Is anyone on IBM-MAIN routinely doing this? Ed, I've done that, especially when it was time for all of us to get some sleep and recharge. Regards, Tom Conley -- 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
Re: Changing PMR Severity (Was: Makes me love most of my z/OS software vendors)
I always reserve SEV 1 to issues that have made my primary systems unusable. I have had IBM'ers tell us to raise to SEV 1 in the morning and then drop to SEV 2 at quitting time. This never set well with me. I had a supervisor (who was and remains an idiot) who wanted me to open a SEV 1 ticket for an issue we had already identified and implemented a work around . We knew exactly what caused it and to fix it quickly if it happend again. I showed him the IBM severity chart and the responsibility for both parties. His response was that was the old way of thinking. I then asked if he would cover second shift work with IBM on the issue and he said no. I took it to the manager and director and they backed him down. SEV 1 to me always means we all work round the clock to fix or workaround the issue. Any other use seems to be abuse to me . This just my opinion. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Fwd: IBM developerWorks news: So long and thanks for all the clicks![sunset]
Hate see it go, just for the links and updates it provided. From: vrmm...@vrm.ca.ibm.com Reply-to: dwn...@us.ibm.com To: efinnel...@aol.com Sent: 11/30/2012 12:14:56 P.M. Central Standard Time Subj: IBM developerWorks news: So long and thanks for all the clicks! If you are unable to read the HTML e-mail below, please _view it online._ (http://www.ibm.com/vrm/newsletter_11461_9000449_1WEBEML/EFinnell106848702) 30 November 2012 | Volume 13, Issue 45 (http://www.ibm.com/vrm/newsletter_11461_9000449_244408_email_DYN_1IN/EFinnell106848702) Dear Friends, If you've been paying attention to developerWorks, you know that the only constant in the world of IT is change ... and that principle is no less true for newsletters. So, after 12 gloriously dynamic years, the developerWorks English-language newsletter is retiring. That's right, our social media efforts have proven so successful that we've decided to focus primarily on those outlets for promoting all the great stuff on developerWorks. Speaking of which, the site continues to grow more robust each week, with new articles, tutorials, downloads, community activities, and more. And we still have lots of options for staying abreast of all these resources, so check them out when you get a chance: * _developerWorks home page_ (http://www.ibm.com/vrm/newsletter_11461_9000449_244409_email_DYN_1IN/EFinnell106848702) * _developerWorks on Twitter_ (http://www.ibm.com/vrm/newsletter_11461_9000449_244409_email_DYN_2IN/EFinnell106848702) * _developerWorks on Facebook_ (http://www.ibm.com/vrm/newsletter_11461_9000449_244409_email_DYN_3IN/EFinnell106848702) * _developerWorks feeds_ (http://www.ibm.com/vrm/newsletter_11461_9000449_244409_email_DYN_4IN/EFinnell106848702) * _developerWorks new media_ (http://www.ibm.com/vrm/newsletter_11461_9000449_244409_email_DYN_5IN/EFinnell106848702) Over the next few weeks, we'll send additional reminders about the transition, but this will be the final issue to include technology-specific content (below). So now's a great time to start following developerWorks through one of these other channels, if you aren't already doing so. Of course, I'll miss this gig. Of the 600 or so issues that we've published, I've overseen about half. (And a tip of the hat to my predecessors, Scott Laningham and Robin Langford, who I'm happy to say are still with developerWorks.) The fact is, it takes a team of dedicated professionals -- authors, editors, coordinators, and more -- to bring you a customizable newsletter this complex, and I am indebted to all of them for their support, diligence, and patience over the years. They do an outstanding job creating first-rate resources for IT professionals, and that has made my job a piece of cake. Me? I am moving over to another team here at IBM, helping streamline communications for Big Blue and its partners. But I'll be checking in with developerWorks every week to see what's new with this, the finest IT-oriented destination on the web, where the goal continues to be helping you do your job better. It has been my privilege to be a part of that effort. Thanks for tuning in! _John Swanson_ (mailto:dwn...@us.ibm.com) and the developerWorks editorial team DEVELOPER RESOURCES Spotlight _Lotusphere fans, don't miss IBM Connect 2013 (27-31 Jan. in Orlando)_ (http://www.ibm.com/vrm/newsletter_11461_9000449_244412_email_DYN_1IN/EFinnell1 06848702) _Take IBM SmartCloud services for a spin (no charge)_ (http://www.ibm.com/vrm/newsletter_11461_9000449_244412_email_DYN_2IN/EFinnell106848702) _And try IBM PureSystems, also no charge_ (http://www.ibm.com/vrm/newsletter_11461_9000449_244412_email_DYN_3IN/EFinnell106848702) _IBM Champion program: Nominate experts and get connected_ (http://www.ibm.com/vrm/newsletter_11461_9000449_244412_email_DYN_4IN/EFinnell106848702) _Build your skills with developerWorks knowledge paths_ (http://www.ibm.com/vrm/newsletter_11461_9000449_244412_email_DYN_5IN/EFinnell106848702) _IBM Education Pack: Pre-pay for training and save 15%_ (http://www.ibm.com/vrm/newsletter_11461_9000449_244412_email_DYN_6IN/EFinnell106848702) _Join us for developerWorks Live! briefings _ (http://www.ibm.com/vrm/newsletter_11461_9000449_244412_email_DYN_7IN/EFinnell106848702) Downloads Trials _Trial: Lotus Domino and Lotus iNotes_ (http://www.ibm.com/vrm/newsletter_11461_9000449_244411_email_DYN_1IN/EFinnell106848702) _Evaluation software center_ (http://www.ibm.com/vrm/newsletter_11461_9000449_244411_email_DYN_2IN/EFinnell106848702) Additional Resources _IBM privacy policy_ (http://www.ibm.com/vrm/newsletter_11461_9000449_244410_email_DYN_1IN/EFinnell106848702) _IBM copyright and trademark information_
Re: New way to do UCB lookups
In CAE1XxDGsByDwmBjCQn1g==98ymcyxx1vi94sayu4jgjmulq...@mail.gmail.com, on 11/29/2012 at 09:32 PM, John Gilmore jwgli...@gmail.com said: Shmuel's comments, which suggested that I did not understand some things that I have understood for many years, were ad hominem Nonszense: what you *wrote* was wrong, whether you knew better or not, and if you really did know better than your subsequent post is inexplicable, since you defended your previous, incorrect, post. gratuitously ad hominem PKB. motivated by More ad hominem; either you are delusional or lying. quotes others' posts selectively I cite the relevant parts; I won't do cascades no matter how often you whine that you want them. -- Shmuel (Seymour J.) Metz, SysProg and JOAT Atid/2http://patriot.net/~shmuel We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Changing PMR Severity (Was: Makes me love most of my z/OS software vendors)
I, too, use SEV 1 only when the system is unusable. I feel fortunate that I've only had a handful of SEV 1's over the past 17 years. I've never had IBM make a request to raise the level as described, but I suspect if they did, I could agree to it. That is, if I believed the issue was SEV 2, but they asked me to make it a SEV 1 during working hours, I think I could go along with that for a time. FWIW, Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List On Behalf Of Chuck Kreiter Sent: Friday, November 30, 2012 12:23 PM I always reserve SEV 1 to issues that have made my primary systems unusable. I have had IBM'ers tell us to raise to SEV 1 in the morning and then drop to SEV 2 at quitting time. snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Changing PMR Severity (Was: Makes me love most of my z/OS software vendors)
On 11/30/2012 10:20 AM, McKown, John wrote: To me, and to every shop I've ever worked at, SEV 1 means we're dead and we are all staying here until we are working again. One time, this meant a 36 hour shift for all 3 sysprogs. I was much younger then. The inability to run daily system backups doesn't, on the surface, seem to rise to the level of SEV1. (Your systems are not DOWN!) OTOH, if while waiting for a diagnosis/fix you lose an important data set or even an entire DASD volume and don't have a suitable backup, things could get VERY painful VERY quickly. Maybe they need a SEV 1.5. ;) -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Changing PMR Severity (Was: Makes me love most of my z/OS software vendors)
Hi Ed, I have become curious. I know you run multiple Lpars at different levels of z/OS. It seem s unlikely to me that HSM is failing in all of them. And that you should be able to get your back-ups, at least temporarily form a working copy :) Dave Gibney Information Technology Services Washington State University -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edward Jaffe Sent: Friday, November 30, 2012 12:08 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Changing PMR Severity (Was: Makes me love most of my z/OS software vendors) On 11/30/2012 10:20 AM, McKown, John wrote: To me, and to every shop I've ever worked at, SEV 1 means we're dead and we are all staying here until we are working again. One time, this meant a 36 hour shift for all 3 sysprogs. I was much younger then. The inability to run daily system backups doesn't, on the surface, seem to rise to the level of SEV1. (Your systems are not DOWN!) OTOH, if while waiting for a diagnosis/fix you lose an important data set or even an entire DASD volume and don't have a suitable backup, things could get VERY painful VERY quickly. Maybe they need a SEV 1.5. ;) -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.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: Changing PMR Severity (Was: Makes me love most of my z/OS software vendors)
On Fri, 30 Nov 2012 12:07:57 -0800, Edward Jaffe edja...@phoenixsoftware.com wrote: On 11/30/2012 10:20 AM, McKown, John wrote: To me, and to every shop I've ever worked at, SEV 1 means we're dead and we are all staying here until we are working again. One time, this meant a 36 hour shift for all 3 sysprogs. I was much younger then. The inability to run daily system backups doesn't, on the surface, seem to rise to the level of SEV1. (Your systems are not DOWN!) OTOH, if while waiting for a diagnosis/fix you lose an important data set or even an entire DASD volume and don't have a suitable backup, things could get VERY painful VERY quickly. Maybe they need a SEV 1.5. ;) What I've done in those cases is to open as a Sev 2 and then explain the criticality of the situation and say please treat this like a sev 1 and that has worked well for me. Of course management (not my manager, but people above him) wants everything opened as a Sev 1 when it affects our clients systems, but I try not to do that except when there is an outage involved. I use to work for a shop who's manager always wanted Sev 1s opened for things I didn't consider Sev 1 and anything that was a Sev 1 was escalated to a crit sit. I figured IBM looked at the sev 1s and said oh, it's them again and just treated it like a sev 2. :-) (boy who cried wolf syndrome) Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Changing PMR Severity (Was: Makes me love most of my z/OS software vendors)
On 11/30/2012 12:12 PM, Gibney, Dave wrote: I have become curious. I know you run multiple Lpars at different levels of z/OS. It seem s unlikely to me that HSM is failing in all of them. And that you should be able to get your back-ups, at least temporarily form a working copy :) In this particular parallel sysplex we happen to be running three systems: two at z/OS 1.13 and one 'other' z/OS release. IBM's support structure for the 'other' z/OS release is not as robust as for z/OS 1.13, so we run the daily backups under z/OS 1.13 only. Follow-up: Based on the PDA logs, IBM thought that one large (5000 cylinder) ZFS seemed to be a trigger for whatever the problem was. We backed that up manually via BACKDS command and then the normal dailies started working again. (Whew!) In fairness, a big part of the delay in analyzing this SEV2 problem was the Thanksgiving holiday and the weekend. That added four days right there. If it's been a week since your last good backup, people start to get a little nervous... :-\ -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Changing PMR Severity (Was: Makes me love most of my z/OS software vendors)
On Fri, 30 Nov 2012 12:31:18 -0800, Edward Jaffe edja...@phoenixsoftware.com wrote: Follow-up: Based on the PDA logs, IBM thought that one large (5000 cylinder) ZFS seemed to be a trigger for whatever the problem was. We backed that up manually via BACKDS command and then the normal dailies started working again. (Whew!) With all the EAV fun you've already had, was that on an EAV volume in cyl managed space? Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Changing PMR Severity (Was: Makes me love most of my z/OS software vendors)
On 11/30/2012 12:44 PM, Mark Zelden wrote: With all the EAV fun you've already had, was that on an EAV volume in cyl managed space? Lol! You call that fun?? :D This most recent issue was on, what some people on this list would call, a 'MOD-81' volume. It is an EAV, but the 5000-cylinder ZFS in question has no extents in the EAS. The pervasive data set corruption problems we had (that eventually led to the creation of APAR OA40210) were on, what some people on this list would call, a 'MOD-236' volume. -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Makes me love most of my z/OS software vendors.
Timothy, I agree as a vendor, second software shop, worked a lot of Sev 1s. The question always is, is it really a technical , code sev 1 or a ' political sev1', those btw I hate. A code issue if we can reproduce it you can usually resolved IMHO. Scott ford www.identityforge.com Tell me and I'll forget; show me and I may remember; involve me and I'll understand. - Chinese Proverb On Nov 30, 2012, at 1:55 AM, Timothy Sipples sipp...@sg.ibm.com wrote: Edward Jaffe writes: We can't make PMRs Sev1 because we don't have a 24/7 response team and without Sev1 IBM works much more slowly than we do. :( The IBM Software Support Handbook, available here: ftp://ftp.software.ibm.com/software/server/handbook/webhndbk.pdf says this about Severity 1 problem incidents: An appropriately skilled technical person from your site must be available to work with IBM's technical support staff during the entire time we are performing support services outside of normal country business hours. Makes sense. If IBM is going to be working day and night, then it's reasonable to expect that you will be, too. So I think that's what you're referring to -- and thank you for following the rules. Nevertheless, you are allowed to mark the problem incident as Severity 1 whenever you have somebody on shift.(*) Therefore it's possible to have your first qualified support person come in at, say, 8:00 a.m. and raise the PMR to Severity 1. Then, as your last qualified support person turns the lights out, that person lowers the PMR to Severity 2 (or lower if appropriate). Loop, repeat if necessary. That's entirely within the rules and even expected/recommended if you have a problem requiring Severity 1 attention from IBM. Granted, it's a little bit odd to have a Sev 1 issue and not have 24/7 IT staffing, at least on a limited ad hoc/overtime basis, but it's possible. (*) On shift doesn't mean answering every call from IBM within 3 seconds -- although that would be nice. Use reasonable judgment here. It's helpful to IBM if you can update the PMR with information like Request next status update between 8:30 and 9:30 p.m. New York time. Contact Joe Smith by telephone at (XXX) YYY- extension QQQ or his backup Sally Carter at extension RRR. Thus if your support desk is unstaffed for an hour or two in the midst of a Sev 1 because somebody needs to go pick up his daughter from soccer practice before the next individual arrives, that'll be OK. Reminder: I'm not speaking for IBM. Timothy Sipples Consulting Enterprise IT Architect (Based in Singapore) 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: Changing PMR Severity (Was: Makes me love most of my z/OS software vendors)
Greg (and others), I had a case which I could only IPL on a Sunday and raised it to a 1 (from a 2) so that support could come in and walk me through the issue. Level 3 came in and we walked through the issue and they came up with a issue with APL (it was a sub issue of PSF) . They were actually able to produce a fix (IN APL no less) and give it to me over the phone. I thought it was strange but no APAR was created but a fix did show up even though the fix was applied. Its been 20 years so don't ask for details. The guy was genuinely helpful and he did resolve the issue. I have an sev 1 PMR's that the sky literally darkened with IBM types and our local IBM types were great as well. This was a to long of a tri-lead on a 168MP (hardware). Ed On Nov 30, 2012, at 11:55 AM, Cardillo, Gregory wrote: I've at times been asked by IBM to raise the severity to get attention - and later lowered it - but I have generally used the willingness of the support teams and client to be available 24x7 (in addition to technical knowledge of the problem, symptoms, impact) as a 'test' of a true Severity 1... If it is that important, they should be available... That certainly can include giving IBM (or other vendors) ways to contact our problem owner (cell, home, etc) - and not sitting watching for updates as the vendor is researching an issue... but available quickly if they need additional doc or information. The problem owner has the contact info for all the other groups involved. I also clearly spell out our expectations for vendor updates and coverage in the record - so there is no confusion. I try to use the severities to reflect the true problem impact - and reserve Sev 1 for those cases where we are truly down or seriously impacted or repeat occurrences. Sev 2 is still high priority - but normal business hours only - for those that don't warrant 'around the clock'. Many times a requested Sev 1 suddenly becomes a 2 or 3 when asking the reporter for 24x7 coverage (not end user... - but applications, dba, software) (There is sometimes a need for a 'political Sev 1' - but in general I try to let the realities of the impact dictate...) Thanks! Greg Cardillo Email: gregory.cardi...@hp.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM- m...@listserv.ua.edu] On Behalf Of Thomas Conley Sent: Friday, November 30, 2012 11:23 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Changing PMR Severity (Was: Makes me love most of my z/ OS software vendors) On 11/30/2012 10:53 AM, Edward Jaffe wrote: On 11/29/2012 10:55 PM, Timothy Sipples wrote: Nevertheless, you are allowed to mark the problem incident as Severity 1 whenever you have somebody on shift.(*) Therefore it's possible to have your first qualified support person come in at, say, 8:00 a.m. and raise the PMR to Severity 1. Then, as your last qualified support person turns the lights out, that person lowers the PMR to Severity 2 (or lower if appropriate). Loop, repeat if necessary. That's entirely within the rules and even expected/recommended if you have a problem requiring Severity 1 attention from IBM. Interesting concept. Is this a common practice? Is anyone on IBM-MAIN routinely doing this? Ed, I've done that, especially when it was time for all of us to get some sleep and recharge. Regards, Tom Conley -- 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
Re: Changing PMR Severity (Was: Makes me love most of my z/OS software vendors)
I had a somewhat similar situation, but it only lasted a couple of hours. A customer had a problem with using SDSF, in that many of its functions wouldn't work. This happened to several users. I finally put in a call to IBM support. I put it in at a severity 2, and the level 1 person said they couldn't call me till the next day. I made it a Sev 1, and someone called me back within 20 minutes or so. What I really thought was interesting - he was in Tazmania. While waiting for him, I started looking at some of the datasets in the logon proc. I found that a change had been made to the logon Clist that this user used. A dataset in one of the concatenations was commented out. The + at the end of the comment was within the /* */ . I sent the level 2 guy that information, and he said that was causing the rest of the datasets after that comment to be ignored, since the + was inside the comment. I put the + after the comment, and it worked fine. Had I not made it a Sev 1, many people who started at 8:00 the next day would have also had this problem. Eric Bielefeld Sr. Systems Programmer - Original Message - From: Edward Jaffe edja...@phoenixsoftware.com Newsgroups: bit.listserv.ibm-main To: IBM-MAIN@LISTSERV.UA.EDU Sent: Friday, November 30, 2012 9:53 AM Subject: Changing PMR Severity (Was: Makes me love most of my z/OS software vendors) On 11/29/2012 10:55 PM, Timothy Sipples wrote: Nevertheless, you are allowed to mark the problem incident as Severity 1 whenever you have somebody on shift.(*) Therefore it's possible to have your first qualified support person come in at, say, 8:00 a.m. and raise the PMR to Severity 1. Then, as your last qualified support person turns the lights out, that person lowers the PMR to Severity 2 (or lower if appropriate). Loop, repeat if necessary. That's entirely within the rules and even expected/recommended if you have a problem requiring Severity 1 attention from IBM. Interesting concept. Is this a common practice? Is anyone on IBM-MAIN routinely doing this? -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Changing PMR Severity (Was: Makes me love most of my z/OS software vendors)
Sev 1 can also cover security/integrity issues. Long ago I reported that under Profs (or maybe OfficeVision) a user could send a document (script file) to another user with embedded codes (.sy I think) which executed CMS or CP commands when the document was formatted, because the system's DCF (document formatter) default was to honor .sy codes. So I could send a document to erase another user's files, send them to me, or do other bad things. I think it was IBM's (good) idea to make it Sev 1 and don't think I was asked to be available 24/7. Of course, the fix was obvious -- patch DCF to make default behavior to NOT honor .sy commands, require specific permission for each document, each time. Also of course, a user (or site) could wrap an exec around DCF to enable .sy, but that's your gun, your bullet, your foot, not IBM's problem. McKown, Johnjohn.mck...@healthmarkets.com said: To me, and to every shop I've ever worked at, SEV 1 means we're dead and we are all staying here until we are working again. One time, this meant a 36 hour shift for all 3 sysprogs. I was much younger then. -- Gabriel Goldberg, Computers and Publishing, Inc. g...@gabegold.com 3401 Silver Maple Place, Falls Church, VA 22042 (703) 204-0433 LinkedIn: http://www.linkedin.com/in/gabegoldTwitter: GabeG0 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
