Re: Good News: Introducing Mobile Workload Pricing (MWP) for z/OS
Here's our first take on it - http://www.watsonwalker.com/clist175.html. See Item #5. This is especially wonderful for banks, and other institutions that are increasing their mobile use. All my best, Cheryl == Cheryl Watson Watson Walker, Inc. www.watsonwalker.com cell text: 941-266-6609 == On May 8, 2014, at 6:44 AM, Shane Ginnane ibm-m...@tpg.com.au wrote: Oh joy, just what we all need, yet another pricing model. Timothy offered his rendition - I wonder how much extra business it will generate for people like Al and Cheryl. Shane ... -- 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: Good News: Introducing Mobile Workload Pricing (MWP) for z/OS
On Mon, 12 May 2014 11:32:20 -0500, Paul Gilmartin wrote: o .bin is customarily reserved for DOS executables, which confused me. It is? MS-DOS won't run a .bin file, AFAIK. Are you confusing it with .exe? -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Good News: Introducing Mobile Workload Pricing (MWP) for z/OS
On Tue, 13 May 2014 07:57:04 -0500, Tom Marchant wrote: On Mon, 12 May 2014 11:32:20 -0500, Paul Gilmartin wrote: o .bin is customarily reserved for DOS executables, which confused me. It is? MS-DOS won't run a .bin file, AFAIK. Are you confusing it with .exe? I stand corrected. If I were a Windows partisan, I'd stand humiliated. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Good News: Introducing Mobile Workload Pricing (MWP) for z/OS
MRWT is expected to be available next month (June). In the meantime, it's probably not worth speculating too much. As informed speculation, the MWRT path isn't going to be much different from the SCRT path given that MWRT is announced as a perfect superset. Thus I would predict it's pretty much business as usual for those of you already working with SCRT. As always, if you have concerns about the tool, let IBM know through official channels. With respect to the Microsoft Windows requirement, I must have been thinking of the spreadsheet method of viewing and editing an SCRT report. And that's optional, correct. (And it doesn't require Microsoft Windows as it happens.) That may be what the MWP announcement letter was referring to (awkwardly or even incorrectly perhaps), but we'll soon find out. Timothy Sipples IT Architect Executive, zEnterprise Industry Solutions, AP/GCG/MEA 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
Re: Good News: Introducing Mobile Workload Pricing (MWP) for z/OS
I've been doing SCRT reporting for about 5 years now. AFAIK there's no Microsoft Windows based component to SCRT. And looking at the very latest UG, I don't see any mention of it either. The tool itself is delivered as a self-extracting zip, which produces a .bin file that you upload to the mainframe where it's executed. But the tool itself is all run on z/OS. Certainly, I download the produced CSV to my workstation, but there's no software delivered with SCRT that uses that output in Windows. At least that I know about. What have I missed? Scott Chapman On Mon, 12 May 2014 10:20:46 +0800, Timothy Sipples sipp...@sg.ibm.com wrote: Roger Lowe asks: Surely, the functionality of MWRT could have been added to SCRT so that us customers could keep running it on z/OS? IBM did that, as I understand it -- and I thought I explained that, but I'll try again. SCRT also has a Microsoft Windows-based tool component. MWRT is a *replacement* for that Windows-based SCRT component. If you're using MWRT, you don't have to also use SCRT (the Windows tool). This is path augmentation, not path duplication. For those of you who are not going to use MWRT, it's business as usual (SCRT). -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Good News: Introducing Mobile Workload Pricing (MWP) for z/OS
On Mon, 12 May 2014 06:42:13 -0500, Scott Chapman wrote: ... The tool itself is delivered as a self-extracting zip, which produces a .bin file that you upload to the mainframe where it's executed. ... Wouldn't a .xmit be simpler; fewer steps? How does the mainframe execute a .bin? BTW, on what platform(s) will the self-extracting zip self-extract? Would a .jar be more portable? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Good News: Introducing Mobile Workload Pricing (MWP) for z/OS
Once uploaded binary to z/OS, the .bin file contains JCL to run the SCRTTOOL. The object code consists of inline 80 byte ESD and TXT records passed via SYSLIN to LOADER (along with some other paramter files). For ease of testing/updating, we store the loader input in a pds member that is accessed from our standard reporting job. Seems sort of retro, but it works. Dana On Mon, 12 May 2014 09:11:32 -0500, Paul Gilmartin paulgboul...@aim.com wrote: How does the mainframe execute a .bin? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Good News: Introducing Mobile Workload Pricing (MWP) for z/OS
On Mon, 12 May 2014 10:51:13 -0500, Dana Mitchell wrote: Once uploaded binary to z/OS, the .bin file contains JCL to run the SCRTTOOL. The object code consists of inline 80 byte ESD and TXT records passed via SYSLIN to LOADER (along with some other paramter files). For ease of testing/updating, we store the loader input in a pds member that is accessed from our standard reporting job. Seems sort of retro, but it works. OK. A few thoughts: o The jar command can (probably) be used to extract the .zip, removing the requirement for a desktop system. o Extracting on z/OS provides verification over more of the transfer path, largely detecting problems caused by EBCDIC, code page, and newline conversion. o .bin is customarily reserved for DOS executables, which confused me. o Some transfer methods balk at .bin because of the threat of malware. o Yet some transfer methods are careful not to corrupt .bin files by reformatting, newline conversion, etc. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Good News: Introducing Mobile Workload Pricing (MWP) for z/OS
W dniu 2014-05-12 18:32, Paul Gilmartin pisze: On Mon, 12 May 2014 10:51:13 -0500, Dana Mitchell wrote: Once uploaded binary to z/OS, the .bin file contains JCL to run the SCRTTOOL. The object code consists of inline 80 byte ESD and TXT records passed via SYSLIN to LOADER (along with some other paramter files). For ease of testing/updating, we store the loader input in a pds member that is accessed from our standard reporting job. Seems sort of retro, but it works. OK. A few thoughts: o The jar command can (probably) be used to extract the .zip, removing the requirement for a desktop system. o Extracting on z/OS provides verification over more of the transfer path, largely detecting problems caused by EBCDIC, code page, and newline conversion. o .bin is customarily reserved for DOS executables, which confused me. o Some transfer methods balk at .bin because of the threat of malware. o Yet some transfer methods are careful not to corrupt .bin files by reformatting, newline conversion, etc. It's not broken, why do you want to fix it? I agree, the form of delivery is not the best I can imagine, but it's working, quite easy to use and more or less convenient. What I would want to have is not changed delivery, rather some atomization, separated ESD, JCL and DD * files. Reason: no need to re-customize the tool during version upgrade. BTW: What DOS do you mean? VSE or MS-DOS? I don't know VSE, bit the .BIN extension remains me AMSDOS system (Amstrad CPC H/W platform). -- 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 authorized 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. 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, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2014 r. kapitał zakładowy mBanku S.A. (w całości wpłacony) wynosi 168.696.052 złote. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Good News: Introducing Mobile Workload Pricing (MWP) for z/OS
On 2014-05-12 14:24, R.S. wrote: o The jar command can (probably) be used to extract the .zip, removing the requirement for a desktop system. o Extracting on z/OS provides verification over more of the transfer path, largely detecting problems caused by EBCDIC, code page, and newline conversion. It's not broken, why do you want to fix it? I've seen enough errors in FTP or IND$FILE, (almost) always due to user error, that I can't consider it not broken. At best, error-prone. I agree, the form of delivery is not the best I can imagine, but it's working, quite easy to use and more or less convenient. What I would want to have is not changed delivery, rather some atomization, separated ESD, JCL and DD * files. Reason: no need to re-customize the tool during version upgrade. Ah! That sounds like TSO TRANSMIT (cf. cbttape.org), or even .tar.Z (oops! Perhaps not for ESD); both using native z/OS methods. BTW: What DOS do you mean? VSE or MS-DOS? I don't know VSE, bit the .BIN extension remains me AMSDOS system (Amstrad CPC H/W platform). MS-DOS. I used a perhaps archaic OS name deliberately. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Good News: Introducing Mobile Workload Pricing (MWP) for z/OS
Roger Lowe asks: Surely, the functionality of MWRT could have been added to SCRT so that us customers could keep running it on z/OS? IBM did that, as I understand it -- and I thought I explained that, but I'll try again. SCRT also has a Microsoft Windows-based tool component. MWRT is a *replacement* for that Windows-based SCRT component. If you're using MWRT, you don't have to also use SCRT (the Windows tool). This is path augmentation, not path duplication. For those of you who are not going to use MWRT, it's business as usual (SCRT). Think of this as SCRT Standard Edition and SCRT Advanced Edition (MWRT), basically. For now, at least, there will be two tools/paths with MWRT a perfect superset of SCRT. If the Microsoft Windows desktop/laptop requirement for SCRT/MWRT is not a good requirement, let IBM know through the appropriate channels. Radoslaw Skorupka asks: How can the tool recognize which transactions are mobile? Aled Hughes remarks: I may be stupid, but I have yet to understand the basics - what is defined as a 'mobile transaction'. I thought I was clear on that point, too, but I'll try again. If *you* can distinguish between a mobile transaction and a non-mobile transaction, IBM is willing to at least discuss the measurement and reporting processes. Both you and IBM sit down to agree on a measurement plan consistent with IBM's views of the term mobile transaction. If that measurement plan is reasonable, it'll probably be approved. For those of you still scratching your heads thinking that's a radical notion, it's not. As long as the definitions are well understood, and as long as you and IBM can measure (and if necessary audit) against those definitions, there should be no particular impediment. Most of you already know how many of your customers are arriving via iOS devices, and how many are arriving via Android devices, and how many are arriving via Blackberries, and so on. Most of you probably already know the nature and number of CICS transactions (for example) attributable to each of those devices (or at least those devices collectively). If you do, great, work out a measurement and reporting plan with IBM. If you don't, that might be a problem already (for customer service, capacity planning, and/or security reasons), and now you've got some additional incentive to address those possible gaps. One of my IBM colleagues provided me with some additional information over the weekend. MWP is even better than I described. Here are the points of clarification (in no particular order): 1. MWP is actually the *third* sub-sub-capacity licensing innovation. The first was Getting Started Sub-Capacity Pricing (GSSP), then IWP arrived, now MWP. (I wrote that MWP was the second sub-LPAR sub-capacity licensing option from IBM, but it's actually the third.) A lot of you said you didn't always like having separate LPARs for separate licensing, and IBM continues to respond to your requests. 2. MWP *can* apply to zNALC LPARs. If you have a z/OS LPAR (zNALC or not) with only z/OS (and z/OS elements) but no other IBM products, then MWP doesn't apply. I stated that correctly. But if you have a qualified zNALC LPAR with other IBM products (e.g. DB2 for z/OS) licensed via AWLC or AEWLC or sub-capacity IPLA, *yes*, MWP *can* apply to those other products. Good news again. 3. Relatedly, MWRT will adjust the MSUs downward for *all* sub-capacity eligible IBM products running on z/OS, based on measured mobile transactions as agreed with IBM. Yes, that includes sub-capacity IBM International Program License Agreement (IPLA) products. To pick an example, if you're running IBM Integration Bus for z/OS (formerly known as WebSphere Message Broker for z/OS), MWRT can adjust that product's reported MSUs, too, based on mobile use of Integration Bus's services. Your IBM CICS tools are adjusted with your CICS, your IBM IMS tools with your IMS, your IBM DB2 tools with your DB2, your IBM MQ tools with your MQ, your ACLS It's across the (z/OS-based) board, according to the amount of workload classed as mobile transactions (as agreed with IBM), excluding only z/OS and z/OS elements. It's not only the big IBM products I listed. Everything IBM that's (a) sub-capacity eligible, (b) riding on z/OS, (c) with mobile activity. Very good news. 4. Sysplex qualification rules are unaffected, as I wrote. I really should not have mentioned Sysplex aggregation rules so close together with SCRT/MWRT measurements since Sysplex qualification and the 50% rule are measured quite differently. But, to reiterate, nothing changes there -- and that's good. You wouldn't want MWP to suddenly make you ineligible for Sysplex aggregation as your billed MSUs drop, and it doesn't -- MWP has no impact on those rules. To respond to the comments about licensing complexity, I think I addressed that adequately, too, but I'll try again. MWP shouldn't require much work to adopt, and the work it requires versus status quo should be of a one-time nature
Re: Good News: Introducing Mobile Workload Pricing (MWP) for z/OS
Fundamental question: How can the tool recognize which transactions are mobile? -- Radoslaw Skorupka Lodz, Poland -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc 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 authorized 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. mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2014 r. kapita zakadowy mBanku S.A. (w caoci wpacony) wynosi 168.696.052 zote. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Good News: Introducing Mobile Workload Pricing (MWP) for z/OS
W dniu 2014-05-08 12:44, Shane Ginnane pisze: Oh joy, just what we all need, yet another pricing model. Timothy offered his rendition - I wonder how much extra business it will generate for people like Al and Cheryl. Well, I was first customer of WLC and we are (were) very happy of that model. Now, as a leader in mobile banking, with the mainframe on the backend we are interested in new pricing model (read: *cost savings*, MONEY!). Of course we would accept discounts even without new pricing models and reporting tools. -- 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 authorized 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. 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, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2014 r. kapitał zakładowy mBanku S.A. (w całości wpłacony) wynosi 168.696.052 złote. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
