The Best Performance for Adabas and Natural

Document Sample
The Best Performance for Adabas and Natural Powered By Docstoc
					      The Best Performance for
      Adabas and Natural

           For Online or Web Activity.


                      Do you feel the love?
By
Jonathan B. Kinberg
Natural
Traditional Natural capabilities


                            Simplified
           Multi-  Program
                            Interactive
         Threading Exchange
                                IO

                   Procedural Simplified
         Security     vs.        DB
                  Event driven Access


        Interpreted Optimizer   Dynamic
         Execution Compiler      linking
However...


                           Simplified
          Multi-  Program
                           Interactive
        Threading Exchange
                               IO

                  Procedural Simplified
        Security     vs.        DB
                 Event driven Access


       Interpreted Optimizer   Dynamic
        Execution Compiler      linking
Natural facts

 4GL language requires more cycles…
      More is being done for you
      Interpreted
           Dynamic
           Non-procedural
 Multi-threading limited by single tasking architecture
  of operating environment
 Conversational nature of Natural expensive to
  implement under non-conversational environments
Natural is now an application server



             XML or HTML Peers


          EntireX, DCOM or MQ Series
                     Peers


                 RPC Servers
Do you feel the love?
Natural and the RPC Server

     DCOM
    Wrapper

    CORBA
    Wrapper

     Java        EntireX
    Wrapper    Communicator
                               RPC
     XML                      Server
    Wrapper

     Remote
     Callnat
Natural and Soap
<Calculation>
  <Opcode>+</Opcode>
                               SOAP
  <Operand1>33</Operand1>
                               Request
  <Operand2>44</Operand2>
</Calculation>




               XML          EntireX
              Wrapper       Broker
                                          Calculation (
                                           Opcode,
                                           Operand1,
<Calculation>                              Operand2,
                               SOAP        Result)
  <Result>77</Result>          Response
</Calculation>
EntireX Communicator




     Stub
Native generation of XML or HTML
Open systems only?
No third party vendor offers a solution




Physical machine   Physical machine
Most of the time, solve problem w/ EntireX




Physical machine   Physical machine
Does Natural feel the love?
We need a new execution environment

 Which runs on the mainframe
 Which is new, State of the art architecture
 Which is multi-tasking and multi-processing
 Which is purely conversational
 Which offers the full compliment of Natural’s
  mainframe capabilities
 Which integrates ADABAS/Broker requests with
  Program Exchange
 Which is a native MVS Web Server
We have the environment!


 Basis for the Tamino mainframe server
 Possible basis for future Sag products
System architecture


                                                  CGI
                   Native                     applications
           Utili             Spool
  VTAM             appli-            Telnet                  Product X
           ties
  Inter-           cations
                                                 HTTP
  face
Demonstrate your love for Natural!
Natural’s place


                                        CGI
           Utili   Spool            applications
  VTAM                     Telnet                  Product X
           ties
  Inter-                               HTTP
  face
Task management




      Physical machine: CPU, Memory and I/O capability
OLTP Environment on the mainframe




      Physical machine: CPU, Memory and I/O capability
Single-Tasking: Single TCB, single queue

              Single Processor allocation - (CICS)
  Processor
    busy




                                                     Time
Multi-Tasking: Many independent TCBs

   Multi processor allocation - Thread (new environment)

 Processor
   busy




                                                Time
Dynamic dispatching of user programs




       Physical machine: CPU, Memory and I/O capability
Active - Inactive program exchange




       Physical machine: CPU, Memory and I/O capability
Buffering: Pools of fixed buffers




                      Nucleus
                      Routines


     Buffers
ADABAS/Broker Access




      Physical machine: CPU, Memory and I/O capability
Terminal communications: Traditional




       Physical machine: CPU, Memory and I/O capability
Terminal communications: Web enabled!




                 Physical machine: CPU, Memory and I/O
Printout spooling/message switching




       Physical machine: CPU, Memory and I/O capability
HTTP server network architecture




                                           Nucleus Modules



                                 Buffers




                         SYS1.PROCLIB
               JES2 ->
What is the HTTP server?



 Allows the execution environment address space to
  become a web server, providing HTML, GIF, VB or
  JAVA script and other binaries from OS datasets
 Installed as a Server under the execution environment
  architecture
 May become a new Software AG product
HTTP Server capabilities 1


 Pooling of Servers
      Servers kept in a pool and are available for reuse once
       request is completed
      Next Request acquires a server from the pool
      NATURAL sessions can be kept active between
       requests
      Once Servers are created they wait on ROLEVT in the
       execution environment thread architecture
HTTP Access using HTTP Server



 Http://ibm1.software-ag.de:3081/sys1/proclib/jes2
      http://
      ibm1.software-ag.de
      :3081
      /sys1/proclib/jes2
HTTP Server capabilities 2



 Conversational tasks
      The HTTP servers can use the HTTP header to
       maintain a context with the client
      This an extension of the pool server concept
      HTTP Clients can converse with the same context over
       multiple requests
We have the execution environment!

 It runs on the mainframe
 It’s new, State of the art technology built and
  engineered, based upon the needs of Natural
 It’s multi-tasking and multi-processing
 It’s purely conversational
 It allows the full compliment of Natural’s mainframe
  capabilities
 It integrates ADABAS/Broker requests with Program
  Exchange
 It’s a native MVS Web Server
We have the environment!


 It’s the basis for the Tamino mainframe server
 Is the execution environment for future Sag products
Show Natural you love him!
COM-PLETE + HTTP server nucleus:
Jonathan’s Point of view...
COM-PLETE version 6 new features


 All version 5 features remain unchanged
 Core technology has been extracted to become an RTS for
   ADABAS, NATURAL, EntireX and Tamino! -> (SMARTS) <-
 New HTTP Server allows PDS members or sequential datasets to
   be sent as web content over internet
 CGI interface allows exposure of application logic to the internet,
   including facilitating Natural Web interface
 Telnet server allows application access from any browser
   anywhere without changes to existing code
COM-PLETE traditional features

 Task Management
 Dynamic dispatching of user programs
 ADABAS/BROKER access
 Terminal communications
 Printout spooling/message switching
 Online utilities/COM-PASS “home state”
 Security Management
 VASM IDAM BDAM access
 Operator communications
Grand Claims
Grand Claims
Grand Claims
Why should I keep or buy COM-PLETE?

 It’s still the best place to run NATURAL.
 It’s still the most efficient place from which to issue
  ADABAS or EntireX Broker calls.
 The only place where the full compliment of Natural’s
  mainframe capabilities are available
 It’s the only HTTP (web) server that runs natively under
  MVS
       Without the overhead of USS like Websphere
 The Telnet feature exposes existing online applications
  to the inter/intra net.
Why should I keep or buy COM-PLETE?

 It’s also the most efficient place from which to
  issue DB2 and MQ Series calls
 It’s not on the sunset list. Has never been...
      The technology will live on and be developed as RTS so even if
       the customer base dwindles it will still be enhanced.
 CICS is one task per address space compared
  to up to 255 for COM-PLETE. CICS multi-tasks
  by propagating CICS’s
      It takes 200 machine instructions to dispatch another task in an
       active address space, but between 5 to 10 thousand to
       dispatch an inactive address space
Part of a comprehensive solution

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:29
posted:2/9/2012
language:
pages:50