A Technical Look at Adabas 2006

1
A Technical Look at Adabas 2006

• Becky Albin
• Chief IT Architect
• Software AG
• Becky.Albin_at_softwareagusa.com

2
Product Portfolio
Open Standard Access
Data Replication Distribution
Database Administration
Productivity and Performance Products
Event Replicator for Adabas
SQL Gateway
Adabas Manager
Delta Save
Adabas Vista
Adabas Online Systems
SOA Gateway
Cluster Services
Adabas Review
Parallel Services
Fastpath
Adabas Statistic Facility
Adabas Base Technology Adabas v8.1 - Mainframe
(z/OS, VSE, z/OS.e, VM, BS2000, MSP) Adabas v5.1
UNIX, Linux, OpenVMS and Windows
Mainframe platforms only
3
Adabas Big Picture - Proven Performance
Enterprise-wide Interoperability
Application
Java
.NET
3GL
Natural
Cross-platform
Tamino XML Server
Data Management
Administration
Data Access
Text Retrieval
SQL
Java
XML
SOA
Security
Cluster
External e.g. RACF

• Availability
• Load Balancing

Monitoring
Performance

• Partitioning
• Save/Restore

Data Organization
Statistics
Windows, Unix. Linux, Mainframe
Utilities

• Replication
• Transaction

Data Distribution
VSAM
DL/1
DB2
Apps
4
Adabas v8.1for Mainframes
5
Adabas v8
Rule

• An Adabas V8 nucleus will support and execute all
  features as supported by a V74 nucleus

6
Adabas v8

• New Features
• Lifting Repeating Field Limits
• Lifting Record Limits
• Lifting Extent Limits
• New Field Formats
• Enhanced Direct Call Interface
• Adabas System Manager

7
Adabas v8 Lifting Limits - MU/PE limits

• Lifting Repeating Field limits MU/PE limits
• Increase to 2 bytes - 191 to 65,534 occurrences
• Actually 4 bytes potentially allowing 2 billion
  occurrences
• Occurs at the file level
• Count field in Index Block increased by three
  bytes
• Re-invert required for PE descriptors
• New Hyper-exit required for expanded MU/PE count
• HEXV8V7 module for Hyper-exit conversion for non
  MUPEX files
• Link with existing Hyper-exit

8
Adabas v8 Lifting Limits - MU/PE limits

• Lifting Repeating Field limits MU/PE limits
• Occurs at the file level
• Increase to 2 bytes - 191 to 65,534 occurrences
• Actually 4 bytes potentially allowing 2 billion
  occurrences
• Count field in Index Block increased by three
  bytes
• Re-invert required for PE descriptors
• Modification of Hyper-exit required for expanded
  MU/PE count

9
Adabas v8 Lifting Limits - MU/PE limits

• Lifting Repeating Field limits MU/PE limits
• Response Code 55, sub-code 9 if gt 191 occurrences
  and Format Buffer has only 1 byte
• Compressed Data Storage Record layout for MU/PE
  fields
• xC0 gt 191 occurs of MU/PE
• Byte indicating of count bytes
• Count bytes
• ex xC0020204
• 516 occurrences

10
Adabas v8 Lifting Limits - MU/PE limits

• Lifting Repeating Field limits MU/PE limits
• May result in
• Larger records not fitting into one data storage
  block or
• LWP (Work Pool) size definition may need to be
  increased to accommodate the update a higher
  count of occurrences.
• LP (WORK Part 1) size definition may need to be
  increased to accommodate the large number of
  occurrences.
• PLOGSIZE may need to be increased to accommodate
  the large number of occurences
• LFP (Internal Format Pool ) size definition may
  need to be increased because the Internal Format
  Element has increased. The total format may be as
  large as 2G.

11
Adabas v8 Lifting Limits Large Record Support

• Lifting Record Limits Large Record Support
• Compressed Record may exceed one physical Data
  Storage Block
• Optional feature that would be set at the file
  level

12
Adabas v8 Lifting Limits Large Record Support

• Lifting Record Limits Large Record Support
• Logical record will be split at the field level
• Data Storage will reflect an Expanded Record
• Primary Record allocated as always
• Secondary Records allocated with different AC
  extents
• Secondary ISN allocation transparent to the
  application
• FCB to reflect both AC allocations
• Impact on the FCB for AC allocations
• Segment of a logical record may be read/updated
  independent of other records
• Index structures only contain primary ISN

13
Adabas v8 Lifting Limits Large Record Support

• Lifting Record Limits Large Record Support

14
Adabas v8 Lifting Limits Large Record Support

• Lifting Record Limits Simple Large Record
  Support

AC
FCB
Data
Secondary Address Convertor
AC2
AC1
AC
Primary Address Convertor
 
Contiguous blocks
OR
Non contiguous blocks
 
 
 
 
15
Adabas v8 Lifting Limits Large Record Support

• Lifting Record Limits Large Record Support
• Physical sequential commands will automatically
  skip the secondary records in the data storage.
• Read by ISN will be unaffected
• Primary records are included in TOP-ISN and
  MAX-ISN.
• Maximum Record Length, specified for a file, will
  have no relevance for file supporting this
  feature.
• Utilities that report on maximum record length
  will now state n/a.
• ISN settings for the utility (e.g. MIN-ISN option
  with Load) will refer to the primary ISNs only
  (NOT secondary)
• Primary ISNs will be counted from MINISN to
  MAXISN, and secondary ISNs will be counted from
  MINSEC to MAXSEC
• A larger NH and NISNHQ parameter may be needed

16
Adabas v8 Lifting Limits Large Record Support

• Lifting Record Limits Large Record Support
• Segmentation is done at field level
• Segmentation by byte is done for long alpha
  fields and long wide fields
• All utilities that use compressed or uncompressed
  data are enhanced to support spanning of the
  logical record across multiple records on the
  operating system files
• ADAULD UNLOAD retains SPAN attribute
• Increased space is needed to store both the BI/AI
  and DVT of a spanned record
• This can also be for several update threads
  running in parallel
• LWP/PLOGSIZE/LP

17
Adabas v8 Lifting Limits Large Record Support

• Lifting Record Limits Large Record Support
• Data Storage Record Header
• Length of this segment
• Record Indicator P/S
• ISN Current Record
• ISN Primary Record
• ISN Next Secondary Record

18
Adabas v8 Lifting Limits - Large Object Field
Types

• Lifting Field Limits Large Object Field Types
• Single field up to 2G in size (2,147,483,643
  bytes)
• Store/Retrieve an entire LOB
• Defined as ZERO length
• Binary and Character LB fields
• Fields may contain any type of date, example
• Jpegs
• AVI files
• PPT, XCL
• Large documents
• Images
• Fingerprints
• Separate file entity for LOB field types
• Requires change to ACB
• Support for segmented Buffers
• Permit Length optimization with communication
  protocol

19
Adabas v8 Lifting Limits - Large Object Field
Types

• Lifting Field Limits Large Object Field Types

FCB
FCB
Primary file
Lob file
AC
Data
AC
AC
Address Convertor for Primary file
Address Convertor for LOB file
Lob File
AC
Lob Fields
File
Primary fields
 
20
Adabas v8 Lifting Limits - Large Object Field
Types

• Lifting Field Limits Large Object Field Types
• May have any of the options NU, NC, NN, NV, NB,
  or MU.
• NV-option (no conversion) specifies that no
  conversion is to occur
• NB-option (no blank compression) for alphanumeric
  or wide character fields
• NC-option (SQL Null Value) for Field may contain
  a null value
• NN-option (SQL not Null) for Field defined with
  NC option must always have a value defined

21
Adabas v8 Lifting Limits - Large Object Field
Types

• Lifting Field Limits Large Object Field Types
• Cannot have the options FI (fixed) or LA (long
  alpha).
• Cannot be a descriptor or a parent of a special
  (phonetic, sub-, super-, or hyper-) descriptor
• Cannot be specified in a search buffer
• May be part of a simple group or a PE-group
• FBL21-10. to select first 10 occurrences of
  LO field
• FBL21-N. not allowed to have an opened ended
  notation of a LO field within a PE

22
Adabas v8 Lifting Limits - Large Object Field
Types

• Lifting Field Limits Large Object Field Types
• Defined to FDT as A or W
• Not as B, to get Binary use both NV and NB
  options
• B format can imply byte swapping, which does not
  apply to binary LB fields
• Zero length

23
Adabas v8 Lifting Limits Physical Extents

• Lifting Physical Extent Limits GCB Changes

• two blocks in Asso
• Fixed area location
• Database features
• Version
• Replication
• UES
• Physical Extents
• Physical Extents extended

Work
Work
Asso
Asso
Asso
Asso
Asso
Asso

• Increase ASSO/DATA physical extents up to 99
• Standard 3390 can have 75 ASSO/DATA/DSST extents
• Removing five-extent limits provides better 24x7
  support

24
Adabas v8 Lifting Limits Logical Extents

• Lifting Logical Extent Limits FCB Changes

File Control Block
FCB
Fixed Area

• one block in Asso
• Fixed area location
• Extent RABNs
• File features
• MU/PE
• Spanned DS
• LOB support
• FDT location
• File extent info
• LOB Info

Extents info
AC
DATA
FDT
DATA
MI
AC
AC
UI
NI
MI
NI
NI
NI
NI
NI

• Increase logical file extents for NI, UI, DS
  allocations
• Maximum depends on size of Associator block
• 3390 can have around 40 extents of each type
• Or there could be more of one type and less for
  another
• Removing five-extent limits provides better 24x7
  support

25
Adabas v8 Lifting Limits ASSO Structure

• Lifting Logical Extent Limits Adabas V7 ASSO
  Structure

Associator
Fixed Area (RABNs 1-30)
GCB

File Control Blocks (1- maxfiles)
FCB

FDT
Field Definitions (4maxfiles)

PPT

• Variable Area of Associator
• Normal Index
• Upper Index
• Main Index
• DS Space Table
• Address Convertor
• PPT

DSST
MI
NI
AC
NI
UI
AC
UI
MI
26
Adabas v8 Lifting Limits ASSO Structure

• Lifting Logical Extent Limits Adabas V8 ASSO
  Structure

Associator
Fixed Area (RABNs 1-30)
GCB

File Control Blocks (1- maxfiles)
FCB

Field Definitions (nmaxfiles)
PPT
FDT
FDT
FDT

• Variable Area of Associator
• Normal Index
• Upper Index
• Main Index
• DS Space Table
• Address Converter
• PPT
• Field Definitions

DSST
MI
NI
AC
NI
FDT
UI
FDT
AC
UI
MI
27
Adabas v8 Lifting Limits FDT changes

• FDT Changes
• May be larger than 4 blocks
• Will move from the fixed area to the dynamic area
  in Asso
• Increase Field Definition Element size
• Support new Field data types of Large Object
• Support only I and S options for LF command
• new Command Option X to allow the read of the
  extended FDT
• Extend Long Alphas to specify lengths gt 253 and lt
  16K
• Positioned for the future e.g.Date/Time formats

28
Adabas v8 Lifting Limits Direct Call Interface

• Enhanced Direct Call Interface
• Needed for RBL gt 32K
• Needed for LOBs
• Needed for segmented Record Buffers
• Format Buffers will map the Record Buffers 11
• Increased number of Command Option fields
• Increased number of Additions Field
• Increased size for User area
• Positioned for the future

29
Adabas v8 Lifting Limits Direct Call Interface

• Enhanced Direct Call Interface
• Adabas Calling Procedure between V7 and V8

RBL (B2)
ABD
RBL (B4)
Call Adabas using ACB FB RB SB VB IB
Call Adabas using ACBX FB1 FB2 FB3.FB10
RB1 RB2 RB3 RB10 SB VB IB
30
Adabas v8 Lifting Limits Direct Call Interface
31
Adabas v8 Lifting Limits Direct Call Interface
32
Adabas v8 Lifting Limits Direct Call Interface
33
Adabas v8 Lifting Limits Direct Call Interface
Adabas Control Block Extended 172 bytes
34
Adabas v8 Lifting Limits Direct Call Interface

• Enhanced Direct Call Interface
• Adabas Calling Procedure between V7 and V8
• User exits 1 and 4 will be replaced by exits 11
  and 14
• Original ACB will still be supported
• Nucleus will primarily run in ACBX mode
• Conversion normally performed during router logic
• New Adalinks will no longer be provided in source
  form
• New ACBX interface required only with new features

35
Adabas v8 - Miscellaneous Topics

• Expanded System File numbers
• Adabas system file numbers can now be two-byte
• Adabas v8 SVC requires APF authorization
• New ADARUN parameter
• EXCPVR
• Used when running APF authorized

36
Adabas v8 - Miscellaneous Topics

• I/O Optimization
• Format-1 CCWs are used
• Reduces storage below 16M line
• Control how page-fixing occurs by using ADARUN
  EXCPVR
• Dropped support of VSAM containers for
  ASSO/DATA/WORK
• HEXV8V7 module
• Front-end stub, link with existing Hyper-exit
• Used for Hyper-exit conversion for non MUPEX
  files
• Converts 4-byte index to 1-byte index

37
Adabas v8 - Utilities

• ADACNV
• Must convert from a v72 or v74 database
• Cannot REVERT if using
• More than 5 physical extents
• More than 5 logical extents on any file
• Spanned records
• MUPEX set
• LB fields
• NB option
• System file w/2-byte FNR

38
Adabas v8 - Utilities

• ADAORD
• RESTRUCTURE from v5.n, v6.n, v7.n allowed as
  input to v8 STORE
• ADASAV
• Database level RESTORE only possible from v8 SAVE
• File level RESTORE possible from any v5.1 or
  higher ADASAV SAVE
• Restoring from v8 to previous versions
• v7.4
• v7.2
• v7.1 (AU713084/AU713085)
• No v8 features used

39
Adabas v8 - Utilities

• ADACMP
• ADACMP data sets from Adabas v5.1 or higher as
  input to ADALOD
• V8 ADACMP data sets can be used as input to
  v5.3.3 or later
• Providing no new v8 features used
• MUPEX
• ADALOD
• Accepts input from v5.1 or higher ADAULD or
  ADACMP
• ADAULD
• V8 ADAULD data sets can be used with v5.3 or
  higher

40
Adabas System Manager for Simplified DB
Administration
41
Adabas Manager
System Management Hub Integration for Computer
Associates Unicenter IBM Tivoli
42
Adabas Manager

• General database info
• info Icon

43
Adabas Manager

• File List info
• paging
• modifiable columns

44
Adabas Manager

• File List info
• use of drop boxes

45
Adabas Manager

• File info
• Column sorting option

46
Adabas Manager

• Container info
• Drop box for different view option

47
Adabas Manager

• User Queue info
• check boxes
• Execute function

48
Adabas Manager
Thread monitoring
49
Adabas Manager

• General Statistics
• use of graphics
• different panels

50
Adabas Manager

• Maintenance info
• sorting

51
ADABAS SQL GatewayAccessing Adabas Data Through
Open Standards
52
Open Connectivity and Real-time Data Sharing

• Challenges
• Heterogeneous application and database landscape
• Cross-platform application development
  Mainframe, Java or Microsoft .NET
• Adabas
• Adabas SQL Gateway
• Adabas SOA Gateway
• Real-time data sharing with Event Replicator for
  Adabas

Business Intelligence
Java .NET, Packaged Application
3GL and Natural
SQL
Web Services
XQuery
Direct
Open Access
Open Replication
XML
SQL DBMS
EAI Middleware
Data Warehouse
53
SQL SOA The Big Picture
54
Adabas SQL Gateway Architecture
Windows

z/OS, VSE, Unix, Win
O D B C
Adabas SQL Gateway Client
Adabas SQL Gateway Server
TCP/IP
Desktop Apps Crystal Reports, Business
Objects and access from .NET and OLE DB
environments
Data Dictionary
(Windows)
Java Server
J D B C
Adabas SQL Gateway Client
TCP/IP
Java Programs with embedded SQL statements
Data Dictionary
Host platforms available according to the
release schedule
(Windows)
55
Adabas SQL Gateway Strengths

• High performance distributed SQL engine
• distributes query processing between multiple
  systems.
• ANSI 92 SQL Support for SELECT, INSERT, UPDATE,
  DELETE
• supports complex SQL statements, correlated
  sub-queries, unions, etc. Giving the
  flexibility of using the full power of SQL to
  accomplish business goals.
• Advanced SQL Optimizer
• tools that will display the query plan and
  allows you to adjust SQL in order to control
  query execution paths.
• Future integration with Adabas
• more tightly integrated with Adabas, offering
  enhanced SQL capabilities.

56
Adabas SQL Gateway Key Features

• Provides cost-effective mainframe data
  reusability by extending access to Adabas via
  standard SQL applications.
• Eliminates the need to duplicate or move data to
  a data warehouse with direct access to Adabas
  information from the desktop.
• Increases productivity for both IT programmers
  and business users by reducing the number of IT
  requests for Adabas information.
• Lowers operational costs with an easy to install,
  high performance SQL engine that provides quick
  and easy access to enterprise data stored on
  Adabas.
• Extensible by other SQL Adapter to do
  heterogeneous joins across disparate DBMS sources
• Proven track record with Adabas customers around
  the world

57
Adabas SQL Gateway Functionality Overview

• ODBC SQL Level 2
• Security
• Meta Data Management
• Enhanced SQL Capability
• Views
• Heterogeneous Joins
• Bi-directional Data Conversion
• Read/Write Access to Data

58
Adabas SQL Gateway Components

• Data Dictionary
• ODBC Driver
• OLE DB RPC Driver
• Database Server
• JDBC Driver (Thin client)
• JDBC Server
• JDBC Router

59
Adabas SQL Gateway Demo
O D B C
Adabas SQL Gateway Client
Data Dictionary
Desktop Apps Crystal Reports, Excel Spreadsheet,
Adhoc Query
TCP/IP
Adabas SQL Gateway Server
60
ADABAS SOA GatewayAccessing Adabas Data Through
Open Standards
61
SQL SOA The Big Picture
62
ADABAS SOA GatewayStructure
The Adabas SOA Gateway handles the generation of
WSDL mapping of SOAP messages to Adabas
resources
63
ADABAS SOA Gateway Request WSDL for File
WSDL Defines how to call server
HTTP//ltSoaServerNamegtltSoaServerPortgt/Production/
Employees?WSDL
64
ADABAS SOA Gateway WSDL Returned to client

• The WSDL for the file is returned to the client.
  Once the client has this file, it knows
• What functions/methods it can call for that
  file.
• The format of the input message required as
  input to that call.
• The format of the output message that will be
  returned to that call.
• This is how the ADABAS SOA Gateway can operate
  with zero client foot print

65
ADABAS SOA Gateway Issue request against file
The ADABAS SOA Gateway maps the request
(dynamically) to an Adabas direct call
66
ADABAS SOA Gateway Receive Response from Request

• The SOA Gateway takes the response from ADABAS
  and maps this back to XML
• The response message is returned to the client
  in the format published in the WSDL
• The client system needs to know nothing about
  the fact that it is talking to ADABAS

67
Architecture - Adabas SOA Gateway
Adabas SOA Gateway
APACHE SSL Security
APACHE HTTP Communication
SOAP/XML Processing usingXERCES
CommandLevelInterface
XML lt-gt ADABAS Mapping Technology
Adabas
68
Adabas SOA Gateway How does it work?
Firewall
Firewall
URL Connection Point
SOAP Request
Client App
Server
SOAP Packaging
Listener
XML ?? Native
HTTP
XML
XML
XML
XML
SOAPResponse or SOAPFault
SOAP Processor
Adabas
69
Adabas SOA Gateway Key Features

• High performance XML processing
• Native support on all platforms
• No client foot print
• Supporting open standards (Web Services SOAP,
  HTTP XQuery)
• HTTP communication
• Simple integration with JAVA, .NET and BPM
  Software packages
• Based on APACHE Infrastructure for performance
  and stability
• Full integration with platform security and
  transaction software
• XQuery processing engine

70
Which Adabas Gateway Should be Used ?
71
What the Gateways have in common?

• No additional programming required
• Support for Adabas security
• No knowledge of Adabas required by programmers
• Open Standards
• OLTP levels of performance
• Traditional mainframe class stability and
  service
• Simple installation and configuration
• Support for all Adabas platforms
• Close integration with Adabas

72
Adabas and Java

• No need to learn Adabas technology specifics
• Use open and common data access standards
• Use open source tools and frameworks (e.g. Apache
  AXIS, Mono (.NET for Linux))

JDBC
SOAP/HTTP
Adabas
Adabas SQL Gateway
Adabas SOA Gateway
73
Adabas and .NET
ltScreenshot MS Visual Studio or BizTalkgt

• Fully supports Microsoft data access technologies

ODBC, OLE DB, .NET
SOAP/HTTP
Adabas
Adabas SQL Gateway
Adabas SOA Gateway
74
Adabas and Web Services
ltScreenshot XML Spygt ltScreenshot ESI productgt

• Fully supports Microsoft data access technologies

ODBC, OLE DB, .NET
SOAP/HTTP
Adabas
Adabas SQL Gateway
Adabas SOA Gateway
75
Event Replicator for AdabasReplicating Data
Across the Enterprise
76
Event Replicator for Adabas Replication Scenarios

• Disaster Recovery
• Replication of Adabas data from place to place,
  in entirety
• Provides for Real-Time hot-standby environment
• Data Warehousing
• Supports business analysis needs with Real-Time
  Adabas data
• Supplying Adabas data to a single target, such as
  a Data Warehouse, which may be combined with data
  from other sources
• Resource Optimization
• Replication of a single Adabas source to one or
  more targets, making local copies of centralized
  data.
• Supports business users without impacting
  production
• Adabas SQL Gateway customers can utilize this
• Data Synchronization
• Support Operational Systems by supplying Adabas
  data to subscribing applications/data stores
• Delivering Adabas data Real-Time to Any Target in
  Any Format

77
What is Event Replicator for Adabas?
Event-Driven Information Distribution Platform
Disaster Recovery
Resource Optimization
Data Synchronization
Data Warehouse
Event Driven Architecture (EDA)
Event Replicator for Adabas
MAPPING
PUSH
FILTER
SUBSCRIBE
MQ/EntireX
SQL
Adabas
DB2
Oracle
Other
78
Event Replicator for AdabasArchitecture Overview
79
Event Replicator for AdabasArchitecture Overview
80
Event Replicator for AdabasArchitecture Overview
81
Event Replicator for AdabasArchitecture Overview
82
Event Replicator for AdabasArchitecture Overview
83
Event Replicator for AdabasArchitecture Overview
84
Event Replicator for AdabasArchitecture Overview
85
Event Replicator for Adabas
86
Competitive AdvantageWhat Event Replicator for
Adabas offers

• Real-time solution
• Supports business demands
• Minimizes system resource usage
• Subscription mapping is integrated with message
  queues (EntireX, MQ Series)
• Helps in persistence and recovery
• Plug into any applications without having to
  mess with application infrastructure
• Opens the data up to non-database targets (i.e.
  mobile, PDAs)
• Transform replicated data into XML format to
  support web services and SOA
• Integrated with Adabas Nucleus
• Smooth upgrades as new versions of Adabas come
  out
• Ability to only send selected data
• Only send committed data conserving resource
  usage
• Hide the complexity of replicated environment
• Use familiar Adabas functionality to remotely
  administer replicated environment
• Automate data models to a replicate to a
  different model target
• Supports most Adabas utilities
• ADALOD LOAD/UPDATE, ADADBS REFRESH/NEWFIELD, etc

87
Competitive AdvantageWhat Event Replicator for
Adabas offers

• Lower System Costsbecause we only publish what
  you ask for
• Ability to publish discrete data elements and
  selected contents unlike CDC-based products which
  replicate at the table level and must process the
  entire Protection Log (PLOG) record
• Low volume of data published means lower system
  costs

88
Competitive Advantage What Event Replicator for
Adabas offers

• Seamless integrationbecause we build Adabas
• Event Replicator is designed in tandem with other
  SAG products which means that
• System upgrades will be seamless
• Administration is simpler
• The customer can have complete confidence in
  their Software AG environment, both now and in
  the future

89
Competitive Advantage What Event Replicator for
Adabas offers

• Information when and where you need itNO delays
• Can send changes anywhere you need it
• DB2, Oracle, Sybase, MS SQLServer, MySQL, etc
• Event Replicator for Adabas offers Real-Time
  replication unlike other solutions which are PLOG
  dependent and require additional filtering or
  data steps downstream before you get the
  information
• Real-time data means accurate information for
  business decision making and customer service
  the more business-critical the application the
  more important this capability

90
Competitive Advantage What Event Replicator for
Adabas offers

• High performance regardless of your Adabas
  workload
• Unlike other solutions, the Event Replicator
  works in very high-transaction environments
  because the Replication Server is a separate
  instance of Adabas
• This means performance demands will be met,
  ensuring business productivity

91
The Next Generation

• Thank you!