> If it were me, I wouldn't let the community design the puzzle pieces that 
> speak HTTP on one end and function/component-specific, native API on the 
> other.. IBM is best placed to make this happen since they've got the teams 
> designing and maintaining parts of z/OS.

For good or bad I work for IBM :)  The community is mostly made up of system 
engineers that have been building Z products for years.  We’re hoping that like 
CBT and other open source venues to have folks contribute and make their 
creations available via Zowe.

Matt Hogstrom
[email protected]
PGP Key: 0x90ECB270

It ain't what you don't know that gets you into trouble.
It's what you know for sure that just ain't so.
-Mark Twain




> On Jan 10, 2019, at 8:13 AM, Sankaranarayanan, Vignesh 
> <[email protected]> wrote:
> 
> Thank you Matt, are you working on something in this area..  ? 
> 
> Just wanted to hear from experienced z folk on whether the thing I've 
> mentioned below sounds doable.
> And if it seems simpler than zOSMF + Zowe.
> Reckon the "security module" for IHSA can even be baked into core IHSA, if it 
> isn't a function abstract-able to a mere 'module' level
> If accessibility (API modules for IHSA) to system functions is established, 
> then IHSA itself can provide DoS mitigation, rate limiting, etc, as should a 
> web server (or some light-weight product on top of it).
> If it were me, I wouldn't let the community design the puzzle pieces that 
> speak HTTP on one end and function/component-specific, native API on the 
> other.. IBM is best placed to make this happen since they've got the teams 
> designing and maintaining parts of z/OS.
> 
> It would be superb if this functionality comes as a IHSA edition or some 
> such. 
> IHSA normal web server edition vs IHSA total control edition.
> 
> – Vignesh
> Mainframe Infrastructure
> 
> -----Original Message-----
> From: IBM Mainframe Discussion List <[email protected] 
> <mailto:[email protected]>> On Behalf Of Matt Hogstrom
> Sent: 10 January 2019 12:43
> To: [email protected] <mailto:[email protected]>
> Subject: [EXTERNAL] Re: Zowe question for IBM
> 
> I’d say that for me personally that is what I want to make available.  Of 
> course, everything you highlighted needs security and some guide rails to 
> ensure that the system is protected against DoS kinds of attacks.
> 
> That is not what z/OSMF is doing.  z/OSMF is a collection of RESTful services 
> that are developed by IBM and are closed so the priority of what is being 
> worked on is dependent on the IBM development community.  Of course they take 
> input from customers and address issues that they prioritize as best for the 
> platform and customers.  Zowe is an opportunity for the community to build 
> and contribute services like you described because they have value to you.  
> 
> As you described it, making access to z/OS system data and ability to manage 
> if via REST is one of the things I am interested but I’m only one guy :)  
> 
> Just a matter of code and test.
> 
> Matt Hogstrom
> [email protected]
> +1-919-656-0564
> PGP Key: 0x90ECB270
> Facebook <https://facebook.com/matt.hogstrom 
> <https://facebook.com/matt.hogstrom>>  LinkedIn 
> <https://linkedin/in/mhogstrom <https://linkedin/in/mhogstrom>>  Twitter 
> <https://twitter.com/hogstrom <https://twitter.com/hogstrom>>
> 
> “It may be cognitive, but, it ain’t intuitive."
> — Hogstrom
> 
>> On Jan 10, 2019, at 2:48 AM, Sankaranarayanan, Vignesh 
>> <[email protected]> wrote:
>> 
>> Hello All,
>> 
>> The recent Zowe discussion got me wondering...
>> Let's say there are thousands of components or subsystems in z/OS, such as 
>> the service for catalog services, ISPF, ISMF, SMS, SDSF, JES2, RACF/ESM, 
>> XCF, IOS, parts within CICS, DB2, IMS, etc. etc.
>> Is it not possible to create a module for each of these 
>> subsystems/components that, in essence, maps the existing assembler/C/REXX 
>> APIs to HTTP APIs, and provides detailed documentation (so as to cover what 
>> is callable via HTTP)?
>> By module I mean modules for a web server, such as the IBM HTTP Server for 
>> Apache.
>> This way, since z/OS comes with IHSA these days, exposing z/OS guts via HTTP 
>> is just a matter of adding modules to the HTTP server.
>> 
>> I don't know if what I've described is basically z/OSMF, but with WAS 
>> Liberty... ?
>> 
>> C'est possible?
>> 
>> - Vignesh
>> Mainframe Infrastructure
>> 
>> 
>> MARKSANDSPENCER.COM
>> ________________________________
>> Unless otherwise stated above:
>> Marks and Spencer plc
>> Registered Office:
>> Waterside House
>> 35 North Wharf Road
>> London
>> W2 1NW
>> 
>> Registered No. 214436 in England and Wales.
>> 
>> Telephone (020) 7935 4422
>> Facsimile (020) 7487 2670
>> 
>> www.marksandspencer.com
>> 
>> Please note that electronic mail may be monitored.
>> 
>> This e-mail is confidential. If you received it by mistake, please let us 
>> know and then delete it from your system; you should not copy, disclose, or 
>> distribute its contents to anyone nor act in reliance on this e-mail, as 
>> this is prohibited and may be unlawful.
>> 
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions, send 
>> email to [email protected] with the message: INFO IBM-MAIN
> 
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
> [email protected] <mailto:[email protected]> with the message: 
> INFO IBM-MAIN
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] <mailto:[email protected]> with 
> the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to