FAQs





These are the questions we have been asked so far.

 Q: Why did you develop this server?  Are there not MainFrame
    http servers already out there?
 
 A: Yes there are other MainFrame http servers available but they all
    require USS or Unix System Services.  Most implementations and
    directions with these servers require an investment in USS/OMVS.
    OMVS is basically UNIX running as an address space under MVS.  The
    other MainFrame http servers generaly run under the UNIX-like
    environment wich in turn runs under (or is a process in) MVS.
    DragonFly runs directly under MVS.  Because of this DragonFly has
    full access to all of the MVS functions and data.  It also
    eliminates the need to train staff in UNIX development and
    administration. Web Sphere also runs under MVS but uses USS or
    Unix System Services.  Our server uses native MVS IO.
 
 
 Q: What are the advantages of the DragonFly server over other
    mainframe web servers.
 
 A: Our server comes with a browser/capture utility.
    This is a distinct advantage.   Gather information to your
    mainframe from any server on the Internet or your Intranet and
    store it in a file for production processing.
 
    DragonFly is efficient.  It can use blocked socket IO so that it
    consumes 0 (zero) cpu while waiting.  We have seen Dragonly
    use less cpu in 1 week of operation than IBMs http server with
    any WebSphere plugin uses at startup.
 
    DragonFly does not use screen scraping, a term often disguised with
    phrases such as "reusing or building on legacy applications" or
    "uses CICS as a back end system".
 
    Our server uses native MVS IO processing.  No bottle-necks here.
 
    Speaking of fast, no one has taken more than an hour to get it
    going yet.  That includes the FTP from our site, the receive
    command process that unzips it, the generation of the VSAM
    database and the final process of submiting a batch job to
    activate it.
 
    DragonFly needs no authorized load libraries to run and thus
    a complicated SMP/E install is not necessary.
 
    DragonFly will run on older versions of MVS (an IP stack is all
    that is required.
 
    DragonFly does not use Unix System Services.
 
    DragonFly can be dropped in with a solution on any MVS release and
    not interfere with or rely on the state or implementation of your
    USS subsystem.
 
    DragonFly allows your mainframe staff to develop and program on
    MVS while at the same time allowing your artists or E-commerce
    teams to develop forms and graphics on their familiar platforms.
 
    Multi-Tier implementations become a thing of the past.  If you can
    still get Yahoo on your browser then there is only one team you
    have to call.  Finger pointing between teams is eliminated.
 
 Q: Why would I want an http server that uses MainFrame languages
    instead of the new alternate platforms? (besides eliminating tiers)
 
 A: Some shops do not have alternate platform developers.  Those that
    do usualy don't have developers that also understand what is on
    the MainFrame and how to get at it.  It is much easier for a
    MainFrame developer to learn how to use or adapt
    HTML as a presentation
    medium than it is for an alternate platform developer to learn the
    MainFrame environment.  In other words you cannot create a
    MainFrame based Web Application without a MainFrame developer.  If
    you use the other Web Servers you will need both MainFrame and
    non-Mainframe developers.  With DragonFly you only need the
    MainFrame developer.  Two days salary for an alternate platform
    developer could easily pay for the DragonFly server.
 
 Q: Does DragonFly front-end existing Legacy applications running
    on CICS?
 
 A: No.  DragonFly is not a screen scraper application.  It is a true
    http server with a native MVS CGI interface.  If the other
    MainFrame Web Servers connect to Legacy applications, how are you
    supposed to write a new MainFrame data sourced application with
    them?  This becomes a multi tier effort.  DragonFly makes this
    kind of complexity unneccessary.
 
 
 Q: Can DragonFly use SSL or 128 bit encryption?
 
 A: Not in this release.
 
 
 Q: When will version 2 of the DragonFly server be available?
 
 A: Version 2 is scheduled out in January 2003 but more functionality
    will come with version 1.5
 
 
 Q: What is the pricing strategy of the DragonFly server?
 
 A: See pricing from the executive summary page.
 
 
 Q: Can we request new features?
 
 A: The most asked for features will be included where possible in new
    releases.  Custom features can be included for your corporation on
    a pro-rated pricing structure.  This would include modifications
    for equipment control systems.
 

Other questions? Contact sales for more information or use our contact form at Tyson Systems.

© 1998-2002 Tyson Systems Inc. All rights reserved.