Matt, Yep I remembered the days we had source for CICS modules and VM. Scott
On Mon, Jan 7, 2019 at 9:34 PM Matt Hogstrom <m...@hogstrom.org> wrote: > You are correct David, thanks. I was the proud recipient of a kidney > stone Sunday night so my response is a bit delayed. > > It looks like most of the questions / comments were answered. If you want > further information please let me know and I’ll provide the best info I can. > > I recall someone made the comment that “it’s open source so its good”. > Z/OS back in the pre-OCO SP3.8 days was “open source” if you call fiche > open source. A lot of products shipped source and patched (I recall the > days of installing UCC-1, 7 and 11). Hopefully what we’ll see is a return > to community code for the platform as a framework and collection of > services through Zowe. At least that is my intent. Honestly, our biggest > challenge now is how to make z/OS instances available to college students > that are interested in getting involved. It’s. A good problem to have. > > Matt Hogstrom > m...@hogstrom.org > PGP Key: 0x90ECB270 > Facebook <https://facebook.com/hogtopia> LinkedIn < > https://linkedin.com/in/mhogstrom> Twitter <https://twitter.com/hogstrom> > > "Never attribute to malice that which is adequately explained by > stupidity.” - Hanlon’s Razor > > > On Jan 7, 2019, at 9:20 AM, David Crayford <dcrayf...@gmail.com> wrote: > > > > I can't speak for Matt but... > > > > On 7/01/2019 2:06 pm, Farley, Peter x23353 wrote: > >> Matt, > >> > >> Thanks for the extended and detailed response. There are many of us > out here who are still wondering what this project really is. > >> > >> First, a caution: Please, please define your acronyms the first time > you use them. E.G., what is JWT? Most of us (well, this application > programmer in particular) have no idea what that is. Java Work Tooling? I > am left to guess. > > > > JWT stands for JSON Web Token > https://en.wikipedia.org/wiki/JSON_Web_Token which are used for > authentication for web services. This is a huge upgrade on z/OSMF which > uses a proprietary method based upon Websphere. > > Everybody writing clients for REST APIs understands JWTs. > > > >> Another couple of examples: "HTML5 enabled desktop". Does that mean > code that runs in a browser on my desktop? "WebSocket enabled APIs"? Same > question. > > > > HTLM5 is current standard for web browsers, so enough said. Web sockets > are used to send data from a server to a client (usually a browser) over a > stream. WebSockets server can send data, such as performance data, SMF etc > > to multiple clients without being polled. Huge performance benefits. > > > >> > >> I thought I grokked this one: "JES Explorer (GUI to interact with JES > much like a Finder or Explorer on Windows would work" until the next > sentence: "web interface that doesn’t require 3270 to submit, etc.". > Again, does that mean a separate program like Windows Explorer, or just a > new browser interface? > >> > >> It would help greatly if there was a video demonstration of these > capabilities. Did any of the Zowe presentations at SHARE include live > online demonstrations of already-available capabilities, and if so are > those video's available through SHARE or on the Zowe website? > >> > >> For the application programmer (not for the systems gurus who maintain > the environment) what is the experience intended to be? I'm not from > anywhere near Missouri, but I really need to be shown how what Zowe is > touting could help me in my everyday work. > >> > >> If I understand it, perhaps I can make a case to my management. But > first I have to understand it. > >> > >> Still somewhat confused . . . > >> > >> Peter > >> > >> -----Original Message----- > >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Matt Hogstrom > >> Sent: Sunday, January 6, 2019 6:16 PM > >> To: IBM-MAIN@LISTSERV.UA.EDU > >> Subject: Re: Zowe? > >> > >> Not to mention the difference between nappies and diapers. > >> > >> Zowe is an open source project created to host technologies that > benefit the Z platform from all members of the Z community (ISV’s and > consumers). The initial code base was seeded with technologies from CA > Technologies, IBM and Rocket. Each of us had developed capabilities that > we wanted to use to enhance the platform but proprietary products were not > the way to create an eco-system; creating proprietary products was just > BAU. We needed to see if such a community was viable and so each > contributed a set of technology and we worked through the legal issues of > moving what was new and some long-standing code to an EPL-2.0 license which > allows anyone to consume and use the code. The choice of three was more > about being able to manage the issues of community formation and not in any > way to be exclusive. Three was a lot of work and we now have a good > framework (legal, governance, hosting, etc.) to start with. > >> > >> A late addition by CA was the addition of the Mediation Layer which we > are using to federate a number of platform services. We have an advanced > use of JWT that allows for accessing multiple services only requiring a > user to sign-on once. This is ahead of platform goals of using JWT in the > Security Managers. Open source allows us to experiment and deliver > capabilities faster than traditional development methods and delivery > streams on Z. > >> > >> The initial contributions were the CLI and some VS Code extensions from > CA, WebSocket enabled APIs from IBM and a HTML5 enabled desktop that > allowed for hosting multiple Angular applications. Consider these > contributions to be more of the framework for enabling access to Z on-top > of which new applications can be built. The applications that are provided > as of now and a few more candidates for 1.0 later this month are: > >> > >> CLI plugins (Console, TSO, file, JES interface, etc.) where developers > that are not accustomed to Z can interact using their shell of choice (we > expect most people to be some bash variant). This interface uses direct > z/OSMF APIs for these services. > >> > >> JES Explorer (GUI to interact with JES much like a Finder or Explorer > on Windows would work). Simple and familiar web interface that doesn’t > require 3270 to submit, retrieve check status on jobs, etc. > >> > >> MVS and USS explorer. Provides access for retrieving / sending files > to and from the z/OS system. Again, very Finder / Explorer like. A > significant advantage here is the applications run in an HTML 5 framework > and eliminate the maintenance of Java and other frameworks on desktops. > There are a number of customers that are looking to eliminate Desktop > dependencies around Java. > >> > >> Contextual Editor (allows for editing and updating with a context > sensitive editor that is extensible with a language server). > >> > >> TN3270 Emulator - fully functional 3270 emulator that runs in the > desktop. All models supported. No client install needed. > >> > >> Some applications that I’m working on are an IPL explorer that will > interrogate the systems in a Plex and navigate the rats nest of Parmiib > members. Doing this at night so going is a bit slow right now. > >> > >> Other products are using Zowe capabilities like the IBM Db2 Dev/Ops > experience as well as the OMEGAMON for Storage. Other products are coming > as well. > >> > >> The best way I have to describe Zowe is that its like Mac or Windows > where they come with a set of APIs and OS capabilities that applications > build on and include some applications out of the box like described above. > >> > >> The goal is to innovate faster, in the open under the oversight of a > community that vets the code, verifies its source and tests what is > delivered. > >> > >> Sorry for the long response to the WTF question but I think it was a > fair question that deserved a response. > >> > >> -- > >> > >> > >> This message and any attachments are intended only for the use of the > addressee and may contain information that is privileged and confidential. > If the reader of the message is not the intended recipient or an authorized > representative of the intended recipient, you are hereby notified that any > dissemination of this communication is strictly prohibited. If you have > received this communication in error, please notify us immediately by > e-mail and delete the message and any attachments from your system. > >> > >> > >> ---------------------------------------------------------------------- > >> 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
