midwest regional tandem user’s group road show 16-19 september 2003 nonstop business continuity...
TRANSCRIPT
Midwest Regional Tandem User’s GroupMidwest Regional Tandem User’s Group Road Show Road Show
16-19 September 200316-19 September 2003
NonStop Business ContinuityNonStop Business Continuity
Midwest Regional Tandem User’s GroupMidwest Regional Tandem User’s Group Road Show Road Show
16-19 September 200316-19 September 2003
NonStop Business ContinuityNonStop Business Continuity
Harry Scott
Co-founderCarrScott Software Inc.
Harry Scott
Co-founderCarrScott Software Inc.
2
AGENDAAGENDA
Two questions – many answers (I hope!...You’ll be the judge)
Question #1 – Three applications: some TMF, some not some SQL, some not
How to provide appropriate Disaster Recovery (DR) / Business Continuity (BC) ??
Question #6 – How best to support DR for Base24? Base24 – some TMF, mostly not
– some SQL, mostly not
One set of solutions addresses both questions:Base24 as example of non-audited, Enscribe application
First, what is ‘appropriate Disaster Recovery / Business Continuity’?
3
DR / BC is more than just database replication!DR / BC is more than just database replication!
Database replication is step #1Database replication is step #1
Only way to successfully guarantee accurate database Only way to successfully guarantee accurate database replication is having the disc process capture changes asreplication is having the disc process capture changes asitit makes them (TMF). makes them (TMF).
Accurate, up-to-date copy of database is great, but alone, Accurate, up-to-date copy of database is great, but alone, recovery time could be days, weeks or worse!recovery time could be days, weeks or worse!
Need full, accurate application replication, not just database.Need full, accurate application replication, not just database.
Taking the application down to repartition the database or Taking the application down to repartition the database or upgrade the OS, is still downtime!upgrade the OS, is still downtime!
‘‘No downtime, no excuses’No downtime, no excuses’HP’s $100 million investment in true continuous availability HP’s $100 million investment in true continuous availability
4
Recover from multiple points of failureRecover from multiple points of failure No planned outages—eliminate application-level impact of No planned outages—eliminate application-level impact of
planned outages in a multi-node environmentplanned outages in a multi-node environment domain-wide host IPdomain-wide host IP domain-enabled app anywhere in domaindomain-enabled app anywhere in domain data ownership may move betweendata ownership may move between
systems within a domainsystems within a domain Seamless scaling of applicationsSeamless scaling of applications
across multiple systemsacross multiple systems single application domain single application domain single management domainsingle management domain
based on OpenViewbased on OpenView single security domainsingle security domain
NonStop advanced architecture raises the bar NonStop advanced architecture raises the bar on availability and scalability for the industryon availability and scalability for the industry
multi-system application domain
app
objectreference
serially accessible
data
app
objectreference
serially accessible
data
5
Indestructible Scalable Computing (ISC): Indestructible Scalable Computing (ISC): Keeping applications alive and growingKeeping applications alive and growing
Adding hardware as the application grows ...Adding hardware as the application grows ... Making changes to add functionality or upgrade to Making changes to add functionality or upgrade to
new technology ...new technology ... applicationapplication databasedatabase systemssystems networkingnetworking
Relocating a data center ...Relocating a data center ... Surviving multiple failures ...Surviving multiple failures ...
… without affecting your critical business applications
6
HP’s investing $ millions in ISCHP’s investing $ millions in ISCBUT…it all assumes you are: TMF, RDF and NS SQL!
multi-system application domain (constellation)
client
single host view IP
app
app
object reference
object reference
serially-accessible data
serially-accessible data
•Domain-wide host IP Application anywhere in domain
•Ownership of data can move between systems within a domain
7
How to make the transition:How to make the transition:BASE24 (current) – Enscribe Files, no TMFBASE24 (current) – Enscribe Files, no TMF*
$PPMN – PATHMON Process
Server-CPF
Pathway Server Classes
CPF file
Server-HCF
HCF file
Server-IDF
IDF file
Server-CAF
CAF file
Server-PTD
PTDF file
Server-RDF
PRDF file
XPNETNode
PTLF file
* - Base24 release 6.0 as released by ACI does have some (minor) TMF protected files and SQL tables but no ‘core’ files.
8
Upgrading existing applications vs. replacing them!Upgrading existing applications vs. replacing them!
Every step in improving uptime should improve the application overallEvery step in improving uptime should improve the application overall
Ensure current investments won’t have to be replaced soon Ensure current investments won’t have to be replaced soon (i.e., current development shouldn’t be new legacy systems)(i.e., current development shouldn’t be new legacy systems)
Ensure your investments are in line with the vendor’s (hp) investments:Ensure your investments are in line with the vendor’s (hp) investments:– World-class Relational database – NonStop SQL (heterogeneous data access, World-class Relational database – NonStop SQL (heterogeneous data access,
leveraging packaged software)leveraging packaged software)– Standards based user interfaces – Java, XML, J2EE, etc...Standards based user interfaces – Java, XML, J2EE, etc...
(reduce cost of development and better usability)(reduce cost of development and better usability)– Zero Downtime – Indestructible Scalable Computing / NonStop Advanced Zero Downtime – Indestructible Scalable Computing / NonStop Advanced
Architecture (system outage = lost customers / revenue)Architecture (system outage = lost customers / revenue)
Legacy business logic works, legacy tools cost you $ millionsLegacy business logic works, legacy tools cost you $ millions
How do we implement Continuous Availability into our existing How do we implement Continuous Availability into our existing environment without throwing out the baby with the bath water??environment without throwing out the baby with the bath water??
9
How to go from Legacy to Current without reprogramming:How to go from Legacy to Current without reprogramming:Incremental improvements using 'intercept' TechnologyIncremental improvements using 'intercept' Technology
What is 'intercept' technologyWhat is 'intercept' technology User Library that intercepts OS calls and performs alternate or User Library that intercepts OS calls and performs alternate or
additional functionality on behalf of programsadditional functionality on behalf of programs Low risk, fast implementation, and 'blessed' by HPLow risk, fast implementation, and 'blessed' by HP
Using intercept technology to implement 'building blocks'Using intercept technology to implement 'building blocks' NonStop AutoTMF automatically provides TMF transaction protectionNonStop AutoTMF automatically provides TMF transaction protection
– Greatly improved data integrity– Improved application performance– 'building block' for disaster recovery
Escort SQL replaces Enscribe files with NonStop SQLEscort SQL replaces Enscribe files with NonStop SQL– Industry standard SQL access (ODBC, EJB, XML, ...)– Leverage packaged software and data integration
Does this work with Base24 and other ‘real’ applications?Does this work with Base24 and other ‘real’ applications? +200 NonStop Server production installations +200 NonStop Server production installations Every step makes the application better!Every step makes the application better!
10
Step #1Step #1Add TMF protection for critical filesAdd TMF protection for critical files
AutoTMF AutoTMF
$PPMN – PATHMON Process
AutoTMF
Server-CPF
TMF
AutoTMF AutoTMF AutoTMF
Pathway Server Classes
CPF file
Server-HCF
HCF file
Server-IDF
TMFTMF
IDF file
Server-CAF
CAF file
Server-PTD
TMFTMF
PTDF file
Server-RDF
PRDF file
XPNET Node
TMF
PTLF file
TMF
Spooler
Note: Don’t forget the Spooler when planning for Disaster Recovery. AutoTMF/TMF protect Spooler datafiles and then replicate.
11
TMF, AutoTMF and database replicationTransaction Protection and Database Replication
• NonStop AutoTMF provides automatic TMF transactions on behalf of programs, transparently
• TMF / DP2 capture I/Os and create audit-trail of all changes to database, guaranteed
• Replication products (RDF, E/R, Shadowbase, etc.) read audit-trail and replicate it to backup
• They then apply audit-trail on backup to create exact image of database
Source node Destination node
DP2
Extractor
Updaters
Receiver
AutoTMF
Usr Pgm
Enscribe orNonStop SQL
Database
NonStop TMF
Audit-trailsTMF
Audit- trails
Enscribe orNonStop SQL
Database
12
Step #2 – Step #2 – Replace selected Enscribe files with NS SQL tablesReplace selected Enscribe files with NS SQL tables
Online database management and repartitioningOnline database management and repartitioning #1 reason for downtime is planned outages to reorganize data#1 reason for downtime is planned outages to reorganize data Moving from Enscribe to NS SQL for key files, eliminates downtimeMoving from Enscribe to NS SQL for key files, eliminates downtime
Industry standard data accessIndustry standard data access #1 factor in reducing cost and time to deliver projects#1 factor in reducing cost and time to deliver projects Single uniform view of data using industry standard interfacesSingle uniform view of data using industry standard interfaces Allows use of industry standard productsAllows use of industry standard products Web & cross-platform access Web & cross-platform access (i.e.,ODBC, Java (JDBC, EJB), XML, cgi,...)(i.e.,ODBC, Java (JDBC, EJB), XML, cgi,...)
SQL & TMF – foundation for hp’s ISCSQL & TMF – foundation for hp’s ISC Indestructible Scalable Computing architecture Indestructible Scalable Computing architecture
– No downtime, no excusesNo downtime, no excuses– Rolling (invisible) system upgrades (NS SQL online DB management) Rolling (invisible) system upgrades (NS SQL online DB management)
13
Step #2 Step #2 (example Base24 but same for other applics)(example Base24 but same for other applics) Core files replaced with SQL tablesCore files replaced with SQL tables
Note: Enscribe files replaced with NonStop SQL tables. Legacy programs unchanged and transparently accessing SQL tables.
Escort SQLAutoTMF
Escort SQLAutoTMF
$PPMN – PATHMON Process
Escort SQLAutoTMF
Server-CPF
TMF
Escort SQLAutoTMF
Escort SQLAutoTMF
Escort SQLAutoTMF
Pathway Server Classes
CPF file
Server-HCF
HCF file
Server-IDF
TMFTMF
IDF file
Server-CAF
CAFSQL Table
Server-PTD
TMFTMF
PTDF SQL Table
Server-RDF
PRDF SQL Table
XPNET Node
TMF
PTLF SQL Table
TMF
Spooler
14
EscortEscortSQL – Replacing Enscribe with NS SQLSQL – Replacing Enscribe with NS SQL
Incremental migration from Incremental migration from Enscribe to NonStop SQLEnscribe to NonStop SQL
Replace one file at a timeReplace one file at a time Intercept technology replacesIntercept technology replaces
Enscribe I/O with NonStop SQLEnscribe I/O with NonStop SQL Fast conversion to SQLFast conversion to SQL
Converts challenging legacy Converts challenging legacy schemas to well-designed, schemas to well-designed, normalized, standardized SQLnormalized, standardized SQL
Enscribe programs using SQL tablesEnscribe programs using SQL tables No reprogrammingNo reprogramming Excellent performanceExcellent performance
Lowest risk, highest return on investmentLowest risk, highest return on investment
EnscribeDatabase
Enscribe Program
EscortSQL
Messages
Enscribe FS SQL FS
READEnscribe
ProcedureCalls
EnscribeProcedure
Calls
Pass-throughPass-through Dynamic SQLDynamic SQL
OPEN
ProcessProcess
SQLDatabase
Disk Process
15
Having Database Replication does not ensure Having Database Replication does not ensure business continuity / disaster recoverybusiness continuity / disaster recovery
Database replication does not provide disaster recoveryDatabase replication does not provide disaster recovery
How do you manage the “Application Environment”?How do you manage the “Application Environment”? TACL macros and Edit filesTACL macros and Edit files Configuration files (Pathway, Batch, Spooler, etc...)Configuration files (Pathway, Batch, Spooler, etc...) Object / Source filesObject / Source files Report files, BLOBs, etc...Report files, BLOBs, etc... Non-audited Enscribe files / SQL tablesNon-audited Enscribe files / SQL tables
Auditing of these files is either impractical or impossibleAuditing of these files is either impractical or impossible
16
AutoSYNC for non-database file replicationAutoSYNC for non-database file replication
Replicated Database
Replicated ApplicationEnvironment
\REMOTE
Database
ApplicationEnvironment
Transactions
New Programs
Config Updates
Online Users
Operators,Developers,
Production Control
\PRIMARY
NonStop AutoSYNC
File Replicationfor Disaster Recovery
E/R, RDF, Shadowbase
Transaction Replication for Disaster Recovery
17
AutoSYNC for Software DistributionAutoSYNC for Software Distribution
ApplicationEnvironment
NewPrograms
Config Updates
Operators,Developers,
Production Control
\HQ
NonStop AutoSYNC
NonStop AutoSYNC
Replicated ApplicationEnvironment
\PARIS
Replicated ApplicationEnvironment
\ROME
Replicated ApplicationEnvironment
\TOKYO
NonStop AutoSYNC
18
Is Base24 really different from any other Is Base24 really different from any other Enscribe, non-TMF application? Enscribe, non-TMF application?
COBOL, TAL, C / Pathway or not – All applications running COBOL, TAL, C / Pathway or not – All applications running on NonStop servers call the same basic procedures on NonStop servers call the same basic procedures (Guardian)(Guardian)
Most applications (like Base24) are really a mixed Most applications (like Base24) are really a mixed environment that have some TMF and every NS server has environment that have some TMF and every NS server has NS SQL installed for OS utilitiesNS SQL installed for OS utilities
Given the number of Base24 installations, are there any Given the number of Base24 installations, are there any specific instructions / guidance?specific instructions / guidance?
What about for other applications?What about for other applications?
19
BASE24 – Major Files(1)BASE24 – Major Files(1)
BASE24 access a number of files when processing a BASE24 access a number of files when processing a transaction. The more important ones are:transaction. The more important ones are:
POS Terminal Data File (PTDF). Typically updated twice POS Terminal Data File (PTDF). Typically updated twice during a Transaction Request.during a Transaction Request.
POS Retailer Definition File. Usually read once per POS Retailer Definition File. Usually read once per Transaction RequestTransaction Request
POS Transaction Log File. Usually written to once per POS Transaction Log File. Usually written to once per Transaction RequestTransaction Request
Interchange Log Files (for BIC and Interchange processes). Interchange Log Files (for BIC and Interchange processes). Usually written to once per Transaction Request.Usually written to once per Transaction Request.
20
BASE24 – Major Files(2)BASE24 – Major Files(2)
CAF and PBF files. Usually Read and Updated per CAF and PBF files. Usually Read and Updated per Transaction Request.Transaction Request.
Negative Files. Access depends on the BASE24 Negative Files. Access depends on the BASE24 configuration. configuration.
SAF (Store-and-forward) files. Only really used if a Host or SAF (Store-and-forward) files. Only really used if a Host or Interchange is unavailable.However, certain transactions Interchange is unavailable.However, certain transactions (reversals, advices) may be written to the SAF first rather (reversals, advices) may be written to the SAF first rather than being sent online directly.than being sent online directly.
Other files e.g. CPF, EMF, AST, KEYF, KEYA are accessed Other files e.g. CPF, EMF, AST, KEYF, KEYA are accessed during Process initialisation and stored in memory tables.during Process initialisation and stored in memory tables.
21
BASE24 and AUTOTMFBASE24 and AUTOTMF
AUTOTMF provides automatic TMF AUTOTMF provides automatic TMF support for BASE24.support for BASE24.
Install AUTOTMFInstall AUTOTMF Bind the AUTOTMF Runtime into Bind the AUTOTMF Runtime into
BASE24 User Libraries (SKELB and BASE24 User Libraries (SKELB and NETLIB) NETLIB)
PREPARE all BASE24 Object PREPARE all BASE24 Object Code.Code.
Turn AUDIT on those files to be Turn AUDIT on those files to be TMF-protected.TMF-protected.
Also turn AUDITCOMPRESS for Also turn AUDITCOMPRESS for heavily-updated files (PTDF, PRDF, heavily-updated files (PTDF, PRDF, CAF, PBF)CAF, PBF)
AUTOTMF WEAK Isolation Mode AUTOTMF WEAK Isolation Mode works well for most BASE24 works well for most BASE24 Satellite processesSatellite processes
Some Satellites e.g. SPDH Device Some Satellites e.g. SPDH Device Handler leave PTDF records locked Handler leave PTDF records locked (until response is received), so may (until response is received), so may need to configure AUTOTMF need to configure AUTOTMF ‘Record Transactions’‘Record Transactions’
Global AUTOTMF settings generally Global AUTOTMF settings generally work well for most BASE24 work well for most BASE24 processes but….processes but….
Some BASE24 processes, mainly Some BASE24 processes, mainly Pathway Servers, do not expect the Pathway Servers, do not expect the AUDIT attribute to be returned in AUDIT attribute to be returned in calls to FILEINFO. Use calls to FILEINFO. Use HIDEAUDIT against Relative FilesHIDEAUDIT against Relative Files
Issues with Full-file Refreshes. Issues with Full-file Refreshes.
22
Base24 – AutoTMF, TMF & RDFBase24 – AutoTMF, TMF & RDF
Don’t have to AUDIT all filesDon’t have to AUDIT all files Can configure Auxiliary Can configure Auxiliary
Audittrails to spread audit loadAudittrails to spread audit load If using RDF then don’t NEED If using RDF then don’t NEED
to dump Audittrails to to dump Audittrails to disc/tapedisc/tape
POS Settlement can generate POS Settlement can generate substantial amounts of audit at substantial amounts of audit at cutover. This very much cutover. This very much depends on the number of depends on the number of POS terminals, cutover times, POS terminals, cutover times, how many totals records are how many totals records are written to the PTLF (i.e. check written to the PTLF (i.e. check the settings of the PTDF totals the settings of the PTDF totals flags).flags).
Don’t have to RDF all Don’t have to RDF all AUDITED files…BUTAUDITED files…BUT
Best performance if only Best performance if only RDFed files configured to the RDFed files configured to the MATMAT
May need to use RDF/IMPx May need to use RDF/IMPx (AutoTMF may generate more (AutoTMF may generate more TMF txns than business txns)TMF txns than business txns)
Consider implications of POS Consider implications of POS Settlement (see left)Settlement (see left)
May need to configure May need to configure multiple RDF Image trails multiple RDF Image trails
Provide more bandwidth Provide more bandwidth rather than less rather than less
23
A better world with DR/BC and SQLA better world with DR/BC and SQL
ODS(TMF Audited, NonStop SQL)
Mining Mart (Unix/Linux)
Extract(fat fast pipe)
Model Building(SAS Enterprise Miner)
Model Deployment
Rules Engine
Query Transactions(Clickstream, CDRs, ...)
Applications External Access
Internal (Full Access)
Applications
• Backups and Query access against read-only database
Database Replication
Production Database(TMF Audited, NonStop SQL)
ApplicationReplication(AutoSYNC)
24
Answering the questionsAnswering the questions
1.1. We have three applications, they run across four We have three applications, they run across four systems. Two are not TMF protected and on flat systems. Two are not TMF protected and on flat (Enscribe) files. Each of these is running on its own (Enscribe) files. Each of these is running on its own system. The third is TMF protected, mostly SQL and system. The third is TMF protected, mostly SQL and running on two systems. We have 3 DR systems running on two systems. We have 3 DR systems available soon. How do you Implement?available soon. How do you Implement?Convert main files to NS SQL and Audit all. Convert main files to NS SQL and Audit all. Replicate to centralized DR systems.Replicate to centralized DR systems.
6. How can your software best support a Base24 environment (Enscribe and SQL) needing replicate (real-time) and synchronize (batch) data records to a hp NonStop hot standby system?Again, convert core files to NS SQL and turn on TMF auditing for all dynamic database files (Enscribe & SQL)
25
Want More Information?Want More Information? EscortEscortSQL, RANGER, Journaling, AutoTMF & AutoSYNCSQL, RANGER, Journaling, AutoTMF & AutoSYNC
Product Information Product Information – EscortSQL http://www.CarrScott.com/sql.shtml – EscortRANGER http://www.CarrScott.com/ranger.shtml– EscortJournaling http://www.CarrScott.com/journaling.shtml– EscortAutoTMF http://www.carrscott.com/auto_tmf.shtml – NonStop AutoTMF http://nonstop.compaq.com/view.asp?IOID=4800 – EscortAutoSYNC http://www.carrscott.com/auto_sync.shtml – NonStop AutoSYNC http://nonstop.compaq.com/view.asp?IOID=5807
Contact Information Contact Information – Harry Scott, Co-founderHarry Scott, Co-founder +1.781.934.0989+1.781.934.0989
[email protected]@CarrScott.com
– Phil Nye, Cardlink ConsultantsPhil Nye, Cardlink ConsultantsBase24 TMF, AutoTMF, RDF guruBase24 TMF, AutoTMF, RDF [email protected]@cardlink.co.uk
26
BACKUP SLIDESBACKUP SLIDES
Peruse to learn more details about the products Peruse to learn more details about the products behind the magnificent upgrades of so many behind the magnificent upgrades of so many mission critical applications.mission critical applications.
27
SQL is great but reprogramming is not!SQL is great but reprogramming is not! Big Bang migrationsBig Bang migrations
High technical riskHigh technical risk Complex project managementComplex project management Only Only long-termlong-term ROI ROI
SQLPrograms
SQLDatabase
EnscribeDatabase
EnscribePrograms
Big B
ang Migration A Better approachA Better approach
Incremental migration (low risk)Incremental migration (low risk) Retain existing programs (lower cost)Retain existing programs (lower cost) Replace database, not programs (ROI)Replace database, not programs (ROI)
SQLPrograms
SQLDatabase
SQLDatabase
EnscribePrograms
EnscribeDatabase
EnscribePrograms
EnscribePrograms
MigratingDatabase
MigratingPrograms
MigratingPrograms
MigratingPrograms
SQLDatabase
28
EscortEscortSQL Migration StepsSQL Migration Steps
EscortEscortSQLSQL system installationsystem installation
Database design and conversionDatabase design and conversion
Program preparationProgram preparation
Test, tune and deployTest, tune and deploy
Follow on native SQL developmentFollow on native SQL development (Optional)(Optional)
29
EscortEscortSQL Installation and ManagementSQL Installation and Management
Software & IPMs available via secure Internet FTP siteSoftware & IPMs available via secure Internet FTP site EscortEscortSQL installs in five minutesSQL installs in five minutes
no SYSGENno SYSGEN no SUPERno SUPER
One operator command at system cold loadOne operator command at system cold load No ongoing operator interventionNo ongoing operator intervention No changes to standard operation proceduresNo changes to standard operation procedures No changes to PATHWAY or batch configurationsNo changes to PATHWAY or batch configurations Extensive self-checkingExtensive self-checking Fault-tolerantFault-tolerant
30
EscortEscortSQLSQL Program PreparationProgram Preparation
Program PreparationProgram Preparation Half-second per programHalf-second per program No source; no recompileNo source; no recompile One-time step, unless One-time step, unless
program is recompiledprogram is recompiled Minimum ImpactMinimum Impact
No changes to program No changes to program logiclogic
No changes to data space No changes to data space allocationallocation
Still portable; no Still portable; no SQLCOMP requiredSQLCOMP required
Has no effect until files Has no effect until files are converted to SQLare converted to SQL
OriginalEnscribePrograms
EnscribeDatabase
Enscribe Program
Enscribe FS
Disk Process
Preparation
PreparedEnscribePrograms
EnscribeDatabase
Enscribe Program
EscortSQLEnscribe FS SQL FS
SQLDatabase
Disk Process
31
EscortEscortSQL - Enscribe to SQL conversionSQL - Enscribe to SQL conversion
Incremental migration from Incremental migration from Enscribe to NonStop SQLEnscribe to NonStop SQL
Replace one file at a timeReplace one file at a time Intercept technology replacesIntercept technology replaces
Enscribe I/O with NonStop SQLEnscribe I/O with NonStop SQL Fast conversion to SQLFast conversion to SQL
Converts challenging legacy Converts challenging legacy schemas to well-designed, schemas to well-designed, normalized, standardized SQLnormalized, standardized SQL
Enscribe programs using SQL tablesEnscribe programs using SQL tables No reprogrammingNo reprogramming Excellent performanceExcellent performance
Lowest risk, highest return on investmentLowest risk, highest return on investment
EnscribeDatabase
Enscribe Program
EscortSQL
Messages
Enscribe FS SQL FS
READEnscribe
ProcedureCalls
EnscribeProcedure
Calls
Pass-throughPass-through Dynamic SQLDynamic SQL
OPEN
ProcessProcess
SQLDatabase
Disk Process
32
EscortEscortSQLSQL Data MigrationData Migration
Replace Enscribe files with well-designed SQL tablesReplace Enscribe files with well-designed SQL tables Eliminate legacy and proprietary data formatsEliminate legacy and proprietary data formats Relational SQL, with appropriate standard SQL data typesRelational SQL, with appropriate standard SQL data types Normalize where desiredNormalize where desired Optionally, redesign database artifacts and compromisesOptionally, redesign database artifacts and compromises
Convert large databases with minimal outageConvert large databases with minimal outage High-performanceHigh-performance Maximize parallelism automaticallyMaximize parallelism automatically Scrub data gracefully and efficientlyScrub data gracefully and efficiently
Rapid deployment of production SQL databaseRapid deployment of production SQL database
33
Replacing Enscribe with well designed Replacing Enscribe with well designed NonStop SQL TablesNonStop SQL Tables
Convert files to SQL Convert files to SQL tables with a single tables with a single commandcommand
Allows great flexibility in Allows great flexibility in redesigning databaseredesigning database
EscortEscortSQLSQL retains retains translation rules translation rules (aka "mappings")(aka "mappings")
Documents relationship Documents relationship Enscribe <–> SQLEnscribe <–> SQL
Used for loading and Used for loading and Enscribe emulationEnscribe emulation
ESCORTSQLESCORTSQL
EnscribeFile
CONVERT...
SQLTable
EscortMappings
FileAttributes
Record Definition
Mapping
DDL
34
EscortEscortSQL Table Design optionsSQL Table Design options
Convert Proprietary Data FormatsConvert Proprietary Data Formats Dates (e.g., YYMMDD) to SQL DATETIMEDates (e.g., YYMMDD) to SQL DATETIME Compressed and encoded fieldsCompressed and encoded fields Eliminate duplicate fieldsEliminate duplicate fields
Convert Non-relational Record FormatsConvert Non-relational Record Formats Multiple record definitions in one fileMultiple record definitions in one file Redefined groupsRedefined groups Arrays (OCCURS)Arrays (OCCURS) Compressed and encoded recordsCompressed and encoded records
Perform NormalizationPerform Normalization Many-to-one and one-to-manyMany-to-one and one-to-many
Many other features and enhancementsMany other features and enhancements
35
Specify special conversion between Enscribe and SQL Specify special conversion between Enscribe and SQL datadata (where desired).(where desired).
Used for initial data conversion and Enscribe emulationUsed for initial data conversion and Enscribe emulation
Built-inBuilt-in Data Types Data Typeshandle common caseshandle common cases
Legacy date/time to Legacy date/time to SQL DATETIMESQL DATETIME
Chars to VARCHARChars to VARCHAR Data scrubbingData scrubbing
CustomCustom Data Types Data Types can be easily addedcan be easily added
Data TypesData Types
Pic 9(7)Pic X(30)Pic 9(2)Pic 9(2)Pic 9(2)
Binary 64
Account
NUMERIC(7)
VARCHAR(30)
DATE
TIMESTAMP
EnscribeRecord DDL
NameDOB-YY
DOB-MMDOB-DD
Last-Update
EscortData Types
TRIM-SPACES
YYMMDD
JULIANTIMESTAMP
??Custom??
SQL TableSchema
36
Normalizing REDEFINESNormalizing REDEFINES
Common problem with Common problem with legacy data: multiple legacy data: multiple record formats in a filerecord formats in a file
Escort can normalize Escort can normalize REDEFINES (or multiple REDEFINES (or multiple record DDLs)record DDLs)
One file converted to One file converted to many tablesmany tables
Each table contains one Each table contains one record formatrecord format
Tables joined by common Tables joined by common keykey
Non-RelationalEnscribe
Record DDL(one file)
NormalizedSQL Table
Schema(three tables)
AccountAccountNameBranchType
CheckingAccountBalance
Overdrafts
LoanAccount
Payment-AmtDue-Date
02 Common-Info 03 Account (key) 03 Name 03 Branch 03 Type(check/loan)02 Checking-Info 03 Balance 03 Overdrafts02 Loan-Info REDEFINES Checking-Info 03 Payment-Amt 03 Due-Date
37
Other FeaturesOther Features Direct execution of CREATE TABLE/INDEX statementsDirect execution of CREATE TABLE/INDEX statements Physical SQL table attributes (extents, audited, etc.)Physical SQL table attributes (extents, audited, etc.) Index name and physical attributesIndex name and physical attributes Delete prefixes (CUST-NAME, CUST-ADDR, CUST-…)Delete prefixes (CUST-NAME, CUST-ADDR, CUST-…) Use of correct standard data types (i.e., DATE)Use of correct standard data types (i.e., DATE) Specify Built-in and Custom conversions (e.g., YYMMDD)Specify Built-in and Custom conversions (e.g., YYMMDD) Convert PIC 9 to NUMERIC (more efficient than DECIMAL)Convert PIC 9 to NUMERIC (more efficient than DECIMAL) Column widths expanded for future requirementsColumn widths expanded for future requirements Duplicate and obsolete fields eliminatedDuplicate and obsolete fields eliminated Obsolete fields replaced by constantsObsolete fields replaced by constants Convert relative files to key-sequenced tablesConvert relative files to key-sequenced tables Allow NULL values where desiredAllow NULL values where desired Use DESCENDING keys instead of complemented valuesUse DESCENDING keys instead of complemented values And more...And more...
38
Data Conversion and LoadingData Conversion and Loading
AutomaticAutomatic parallelism parallelism Load one-to-many Load one-to-many
normalization in parallelnormalization in parallel Load partitions in parallelLoad partitions in parallel
Sophisticated error Sophisticated error analysisanalysis
Each rejection is Each rejection is explainedexplained
Production data can be Production data can be pre-checked prior to pre-checked prior to actual migrationactual migration
Minimal conversion Minimal conversion outageoutage
ESCORTSQL
LOAD ...
EscortMappings
Mapping
SQLTableSQL
Table
SQLTableSQL
TableSQLTable
RejectedRecords
RejectionDetails
One-to-many Normalization
TablePartitions
ParallelLoadingParallelLoading
EnscribeFile
ErrorAnalysisError
Analysis
Legacy DataLegacy Data
39
Journaling for Online Database LoadsJournaling for Online Database Loads
Load database while Load database while application live application live
Background load of Background load of "original" to "new" file"original" to "new" file
Journaling captures changes Journaling captures changes during loadduring load
When load complete,When load complete,Journaling applies changes Journaling applies changes that occurred during loadthat occurred during load
When Journaled updates When Journaled updates have been applied to new have been applied to new file, redirect programs to file, redirect programs to "new" file"new" file
Minimal outage windowMinimal outage window
DB Loader
LOAD ...
NewFile
JournalQfile
OriginalFile
Applications
Journaling
DB Updater
1. ApplicationLive
2. BeginJournaling
3. StartDB Load
4. ApplyJournal
5. RedirectApplications
40
Program ExecutionProgram Execution
Enscribe EmulationEnscribe Emulation Operations on Enscribe Operations on Enscribe
files are passed throughfiles are passed through Operations on SQL tables Operations on SQL tables
are directly emulated with are directly emulated with dynamic SQLdynamic SQL
No extra processes or No extra processes or messagesmessages
EnscribeDatabase
Enscribe Program
EscortSQL
Messages
Enscribe FS SQL FS
READEnscribe
ProcedureCalls
EnscribeProcedure
Calls
Pass-throughPass-through Dynamic SQLDynamic SQL
OPEN
ProcessProcess
SQLDatabase
Disk Process
41
Enscribe EmulationEnscribe Emulation
EscortEscortSQLSQL supports all supports all Enscribe procedures Enscribe procedures except CHECKOPENexcept CHECKOPEN
Supports all Tandem Supports all Tandem languages:languages:
COBOLCOBOL CC C++C++ PascalPascal TALTAL BASICBASIC
ABORTTRANSACTIONALTERAWAITIO[X]BEGINTRANSACTIONCANCELCANCELREQCLOSECONTROLCONTROLBUFCREATEENDTRANSACTIONFILEINFOFILEINQUIREFILERECINFOFILE_ALTERLIST_FILE_CLOSE_FILE_CREATELIST_FILE_CREATE_FILE_GETINFOBYNAME_FILE_GETINFOLISTBYNAME_FILE_GETINFOLIST_FILE_GETINFO_FILE_OPEN_FILE_PURGE_FILE_RENAME_
GETSYNCINFOKEYPOSITION[X]LOCKFILELOCKRECOPENPOSITIONPURGEREAD[X]READLOCK[X]READUPDATE[X]READUPDATELOCK[X]RENAMEREPLY[X]SAVEPOSITIONSETMODESETMODENOWAITSETPARAMSETSYNCINFOSYSTEMENTRYPOINTLABELUNLOCKFILEUNLOCKRECWRITE[X]WRITEREAD[X]WRITEUPDATE[X]WRITEUPDATEUNLOCK[X]
42
Application Performance OverviewApplication Performance Overview
EscortEscortSQL program performance is better than a SQL program performance is better than a hand-translated SQL programhand-translated SQL program
SQL programs may use more CPU than EnscribeSQL programs may use more CPU than Enscribe SQL programs have better throughput and response timeSQL programs have better throughput and response time
Performance can be easily improved where desiredPerformance can be easily improved where desired Use more sophisticated SQL in performance-critical areasUse more sophisticated SQL in performance-critical areas Does not require rewrite or redesign of programDoes not require rewrite or redesign of program
Advanced SQL capabilities can be implementedAdvanced SQL capabilities can be implementedwhere desired for increased functionality or where desired for increased functionality or unparalleled performanceunparalleled performance
Change only the programs necessaryChange only the programs necessary
43
EscortEscortSQLSQL Migration RoadmapMigration Roadmap
Preparation
EnscribeDatabase
EnscribePrograms
EnscribeDatabase
SQL Data Migration
Hybrid Migration SQLDatabase
Native SQL Migration
EnscribePrograms
SQLDatabase
SQLDatabase
Time Required:Minutes
Time Required: Days
Time Required: Weeks
Time Required: ????
Each step is incremental.Each step is low risk.Each step has ROI.
EnscribePrograms
EscortSQL
HybridPrograms
EscortSQL
EscortSQL
SQLPrograms
44
EscortEscortRANGER RANGER Database analyzer and Parallel Database Access MethodDatabase analyzer and Parallel Database Access Method
Ranger quickly and efficiently analyzes Tandem Enscribe files and NonStop SQL tables and determines optimal file partitioning ranges.
Ranger allows truly parallel, multi-threaded application processing. Run multiple copies of your programs, each against a portion of the database, resulting in linear, scalable performance, especially in batch processing environments.
Before using Escort RANGER
After using Escort RANGER
Transaction and Data Protection
EscortEscortAutoTMFAutoTMF
Product OverviewProduct Overview
EscortEscortAutoTMFAutoTMF
Product OverviewProduct Overview
46
The Problem – The Problem – TMF for non-TMF applications TMF for non-TMF applications
NonStop TMF has great advantagesNonStop TMF has great advantages Online backups for 24 X 7 availabilityOnline backups for 24 X 7 availability Data recoveryData recovery Improved application performanceImproved application performance
Nearly half of the existing applications on Nonstop ServerNearly half of the existing applications on Nonstop Server systems are not coded to use TMF systems are not coded to use TMF
Even most Even most TMF-awareTMF-aware applications do not protect all files applications do not protect all files Leaves a hole for replication and disaster protectionLeaves a hole for replication and disaster protection
Re-programming to use TMF is daunting and riskyRe-programming to use TMF is daunting and risky Development $$ better used for new featuresDevelopment $$ better used for new features RDF requires TMF to provide guaranteed replicationRDF requires TMF to provide guaranteed replication Only TMF audited files are protected against the largestOnly TMF audited files are protected against the largest
exposure to data loss and system outage...human error exposure to data loss and system outage...human error
47
The Solution – AutoTMF The Solution – AutoTMF Complete TMF database protectionComplete TMF database protection
AutoTMF enables applications for TMF quickly A few minutes to install A few minutes to install A few minutes to prepare object filesA few minutes to prepare object files
– Requires no programming or re-compiling or bindingRequires no programming or re-compiling or binding A few minutes to audit desired filesA few minutes to audit desired files
Same library and "prep" as Escort SQL Same library and "prep" as Escort SQL No install required if already using Escort SQLNo install required if already using Escort SQL Simply turn it on and let it go!Simply turn it on and let it go!
Low overhead and minimal operations requirementsLow overhead and minimal operations requirements Gain TMF benefits immediatelyGain TMF benefits immediately
Replication, online dumping and performanceReplication, online dumping and performance Data consistency same or better than pre-AutoTMF applicationData consistency same or better than pre-AutoTMF application
– Automatic transaction boundaries are not “Business transactions”Automatic transaction boundaries are not “Business transactions”– Incremental “Business transaction” consistency is possible to Incremental “Business transaction” consistency is possible to
implement incrementallyimplement incrementally
48
AAutoutoTMF OverviewTMF Overview
Same intercept technology Same intercept technology used in Escort SQLused in Escort SQL
Intercepts file system and Intercepts file system and TMF callsTMF calls
Begins / Ends TMF Begins / Ends TMF transactions as requiredtransactions as required
Operations on non-audited Operations on non-audited files are passed throughfiles are passed through
Many configuration options Many configuration options available to address available to address application specific needsapplication specific needs
Designed for performanceDesigned for performance Files are bufferedFiles are buffered Efficient block splitsEfficient block splits Many I/Os per transaction Many I/Os per transaction Native Mode supportNative Mode support
Non-AuditedFiles
AuditedFiles
AUTOTMF
Non TMF Program
“WRITE”
TMFOperation
Non-TMFOperation
Disk Process
Passthrough With
Transaction
49
Automatic Transactions RulesAutomatic Transactions Rules
All AutoTMF transactions must be committedAll AutoTMF transactions must be committed AutoTMF never ABORTs automatic transactionsAutoTMF never ABORTs automatic transactions Emulates file operations on a unaudited database Emulates file operations on a unaudited database A program cannot stop without committing automatic transactionsA program cannot stop without committing automatic transactions
Automatic transactions preserve locking protocol Automatic transactions preserve locking protocol Cannot commit an automatic transaction if unaudited file access Cannot commit an automatic transaction if unaudited file access
still has a record / file lockedstill has a record / file locked Automatic transactions are local to one processAutomatic transactions are local to one process
Cannot be exported or inheritedCannot be exported or inherited
50
Automatic Transactions StartAutomatic Transactions Start
First transactional access determines use of automatic First transactional access determines use of automatic transactions for the open:transactions for the open:
The The firstfirst access occurs when the application has not started access occurs when the application has not started or inherited its own transaction (default)or inherited its own transaction (default)
Or when automatic transactions are configured for the fileOr when automatic transactions are configured for the file Well-known operations on an audited file which start an Well-known operations on an audited file which start an
automatic transactionautomatic transaction READLOCKREADLOCK WRITEWRITE LOCKFILELOCKFILE
51
Automatic Transactions CommitAutomatic Transactions Commit
Application must have released locksApplication must have released locks Logical points in the processingLogical points in the processing
READUPDATE $RECEIVEREADUPDATE $RECEIVE REPLYREPLY File close and process stopFile close and process stop
Isolation driven (configurable)Isolation driven (configurable) Server SENDServer SEND Other external communication (spooler e.g.)Other external communication (spooler e.g.)
Activity-driven (configurable)Activity-driven (configurable) Elapsed timeElapsed time Number of updatesNumber of updates
Balance performance and consistencyBalance performance and consistency
52
Automatic Transactions AbortAutomatic Transactions Abort
AutoTMF never aborts an automatic transactionAutoTMF never aborts an automatic transaction Emulates non-audited behaviorEmulates non-audited behavior Does not export automatic transactionsDoes not export automatic transactions
Protects transactions from ABENDS / traps, etc.Protects transactions from ABENDS / traps, etc.
Intercepts STOP, ABEND, instruction failures, etc. and Intercepts STOP, ABEND, instruction failures, etc. and commits automatic transactions before program terminationcommits automatic transactions before program termination
In the event of a system failure (i.e., unilateral abort), pre-TMF In the event of a system failure (i.e., unilateral abort), pre-TMF recovery procedures still apply (very rare)recovery procedures still apply (very rare)
Great effort has been applied to ensure that database integrity is Great effort has been applied to ensure that database integrity is ALWAYS at least the same as or better than pre-TMF environmentALWAYS at least the same as or better than pre-TMF environment
53
TMF / AutoTMF PerformanceTMF / AutoTMF Performance AutoTMF is optimizedAutoTMF is optimized
No additional processes; no extra I/ONo additional processes; no extra I/O One configuration message on process start and audited file opensOne configuration message on process start and audited file opens
– Configuration parameters are cached in memoryConfiguration parameters are cached in memory Automatic transaction generation requires very little processingAutomatic transaction generation requires very little processing Passthrough is virtually free (a few microseconds)Passthrough is virtually free (a few microseconds)
AutoTMF performance is TMF performanceAutoTMF performance is TMF performance Buffering can increase performance by up to 80% with 0% riskBuffering can increase performance by up to 80% with 0% risk TMF audited files eliminates block splitting overheadTMF audited files eliminates block splitting overhead
TMF activity is optimizedTMF activity is optimized Minimizes number of transactions - several inserts/updates per Minimizes number of transactions - several inserts/updates per
transactiontransaction Parallelism when multiple (Separate) transactions are configuredParallelism when multiple (Separate) transactions are configured Nowait transactionsNowait transactions User configurableUser configurable
54
Escort AutoTMF, TMF and RDFTransaction Protection and Database Replication
• AutoTMF provides automatic TMF transactions on behalf of programs • TMF / DP2 capture I/Os and create audit-trail of all changes to database• RDF has low-level interface to read audit-trail and replicate it to backup • RDF then applies audit-trail on backup to create exact image of database• RDF provides the highest performance DR replication and guaranteed database integrity
Primary node Duplicate node
DP2
Extractor
Updaters
Expand
Receiver
AutoTMF
Usr Pgm
Enscribe orNonStop SQL
Database
NonStop™ TM/MP
(aka TMF) Audit-trails
Audit- trails
Enscribe orNonStop SQL
Database
55
NonStop AutoTMF FuturesNonStop AutoTMF Futures
Proposed FuturesProposed Futures RDF/TMF Lock-step transaction support RDF/TMF Lock-step transaction support (eliminate need for reprogramming)(eliminate need for reprogramming)
RDF file RENAME and PURGE supportRDF file RENAME and PURGE support Super-Fast Take Over support (SFTO a.k.a. Wait_for_RDF)Super-Fast Take Over support (SFTO a.k.a. Wait_for_RDF) AutoTMF support for unaudited SQL tablesAutoTMF support for unaudited SQL tables
Replication of non-Database filesReplication of non-Database files
EscortEscortAutoSYNCAutoSYNC
Product OverviewProduct Overview
EscortEscortAutoSYNCAutoSYNC
Product OverviewProduct Overview
57
EscortEscortAutoSYNCAutoSYNCNon-Database File ReplicationNon-Database File Replication
Database replication does not provide disaster recoveryDatabase replication does not provide disaster recovery
How do you manage the “Application Environment”?How do you manage the “Application Environment”? TACL macros and Edit filesTACL macros and Edit files Configuration files (Pathway, Batch, Spooler, etc...)Configuration files (Pathway, Batch, Spooler, etc...) Object / Source filesObject / Source files Report files, BLOBs, etc...Report files, BLOBs, etc... Non-audited Enscribe files / SQL tablesNon-audited Enscribe files / SQL tables
Auditing of such files is either impractical or impossibleAuditing of such files is either impractical or impossible
58
EscortEscortAutoSYNC OverviewAutoSYNC Overview
Synchronizes filesets between Nonstop Server systemsSynchronizes filesets between Nonstop Server systems Replication of entire files, not individual recordsReplication of entire files, not individual records
Complements RDF and other replication productsComplements RDF and other replication products
Easy to install; easy to configure and manageEasy to install; easy to configure and manage Completely automatic; set it and forget itCompletely automatic; set it and forget it Fault tolerant; highly reliableFault tolerant; highly reliable Uses standard security facilitiesUses standard security facilities
Primary uses:Primary uses: Complete Disaster Recovery preparation Complete Disaster Recovery preparation Automated Operations support (SW distribution)Automated Operations support (SW distribution)
59
AutoSYNC for non-database file replicationAutoSYNC for non-database file replication
Duplicate Database
Duplicate ApplicationEnvironment
\REMOTE
Database
ApplicationEnvironment
Transactions
New Programs
Config Updates
Online Users
Operators,Developers,
Production Control
\PRIMARY
EscortAutoSYNC
File Replicationfor Disaster Recovery
RDF
Transaction Replication for Disaster Recovery
60
AutoSYNC for Software DistributionAutoSYNC for Software Distribution
ApplicationEnvironment
NewPrograms
Config Updates
Operators,Developers,
Production Control
\HQ
Escort AutoSYNC
Escort AutoSYNC
Duplicate ApplicationEnvironment
\PARIS
Duplicate ApplicationEnvironment
\ROME
Duplicate ApplicationEnvironment
\TOKYO
Escort AutoSYNC
61
AutoSYNC Processing Architecture AutoSYNC Processing Architecture
AutoSYNC
ESCSYNC
$DATA.SRV.* \REMOTE.$BACK
“Sync DATA.SRV*.*,\REMOTE.$BACK.*.*”
1. Send synccommand
ESCSYNC2. Fetch localfile signatures
4. Fetch remotefile signatures
3. Transmitfile signatures
5. Transmitsync file list
6. Synchronizefiles
62
Selecting Files for SynchronizationSelecting Files for SynchronizationAutoSYNC synchronizes files in the Fileset that:AutoSYNC synchronizes files in the Fileset that: Do not exist on the remote systemDo not exist on the remote system
Are “older” on the remote systemAre “older” on the remote system User may update files on the remote system to change User may update files on the remote system to change
system/volume names, etc.system/volume names, etc. Difference in system clocks is factored inDifference in system clocks is factored in ““Exact” synchronization can be specifiedExact” synchronization can be specified
Are not open for exclusive or update accessAre not open for exclusive or update access
Are not TMF auditedAre not TMF audited
Are not “ZZ” files (unless specified)Are not “ZZ” files (unless specified)
63
Synchronization ModesSynchronization Modes
Online SynchronizationOnline Synchronization Immediate, command-driven synchronizationImmediate, command-driven synchronization Employs current user’s local and remote access rightsEmploys current user’s local and remote access rights Same security requirements as a FUP DUPSame security requirements as a FUP DUP
Scheduled SynchronizationScheduled Synchronization Multiple users can configure synchronizationMultiple users can configure synchronization Automatic; no user interventionAutomatic; no user intervention Reliable, fault-tolerantReliable, fault-tolerant Requires security authorizationRequires security authorization
64
Online Sync Architecture Online Sync Architecture
Escort CI SYNC $DATA.JOE.* TO \REMOTE.$DATA.*.*;
ESCSYNC
$DATA.JOE.* \REMOTE.$DATA
USER.JOE
USER.JOELocal Access
USER.JOERemote Access
User issues command for each sync operation
• Uses standard security for file access
• Could be performed by BATCH scheduler
• Does not require configuration or user setup
65
Scheduled Sync Architecture Scheduled Sync Architecture
$DATA.JOE.* \REMOTE.$DATA
Executes as USER.JOE
Joe’s RemoteAccess
$ZESC(monitor)$ZESC
AutoSYNC MonitorFault-tolerant Process pair
SYNCUSER
ESCSYNCP
Joe’sSyncFiles
Sam’sSyncFiles
USER.JOE USER.SAM
Joe’s LocalAccess
$DATA.SAM.* \REMOTE.$DATA
Executes as USER.SAM
Sam’s RemoteAccess
ESCSYNCP
Sam’s LocalAccess
66
Fileset Scheduling OptionsFileset Scheduling Options
Default is every 5 minutesDefault is every 5 minutes User can specify interval from 1 minute to User can specify interval from 1 minute to nn days. days.
Daily START and STOP timesDaily START and STOP times Can specify “sync every day starting at 6PM until midnight”Can specify “sync every day starting at 6PM until midnight”
SUSPEND and ACTIVATESUSPEND and ACTIVATE Can temporarily suspend synchronization without deleting Can temporarily suspend synchronization without deleting
fileset configurationfileset configuration
67
CompressionCompression
Uses LZW algorithmUses LZW algorithm
Eliminates 60% to 80% of network trafficEliminates 60% to 80% of network traffic
CPU-intensiveCPU-intensive Compression may not increase throughput if lines are fastCompression may not increase throughput if lines are fast
AutoSYNC uses compression if it improves throughput AutoSYNC uses compression if it improves throughput (dynamic calculation)(dynamic calculation)
Compression can be enabled/disabled to fit customerCompression can be enabled/disabled to fit customer
68
Performance OptionsPerformance Options
Automatic synchronization parallelism for different users Automatic synchronization parallelism for different users and/or different remote systemsand/or different remote systems
Configured parallelism by specifying “batchid”Configured parallelism by specifying “batchid”
Priority and ThrottlingPriority and Throttling Synchronization should not affect ongoing production workSynchronization should not affect ongoing production work User can specify process priorityUser can specify process priority User can specify maximum percentage of busy timeUser can specify maximum percentage of busy time
69
Destination File Purge OptionDestination File Purge Option
Files that do not exist in the source fileset can be purged in Files that do not exist in the source fileset can be purged in the destination filesetthe destination fileset
Used to maintain subvolumes in parallelUsed to maintain subvolumes in parallel
Does not purge files in a destination subvolume if the Does not purge files in a destination subvolume if the source subvolume does not existsource subvolume does not exist
70
Security and Ownership OptionsSecurity and Ownership Options Automatic upgrade to network security Automatic upgrade to network security
Local security could prevent access after remote syncLocal security could prevent access after remote sync Local security changed to network security (“A” becomes “N”)Local security changed to network security (“A” becomes “N”) Can be disabled with NO NETWORKSECURE optionCan be disabled with NO NETWORKSECURE option
(Input on default mode: Network Secure or no?)(Input on default mode: Network Secure or no?)
SyncUser can specify owner of replicated filesSyncUser can specify owner of replicated files
SyncUser can specify security of replicated filesSyncUser can specify security of replicated files
Purge security could prevent repeated syncsPurge security could prevent repeated syncs Changed to allow sync user to purge fileChanged to allow sync user to purge file
– Example: Example: “N” security if SyncUser and file owner are in different groups“N” security if SyncUser and file owner are in different groups
Might allow anyone to purge a replicated fileMight allow anyone to purge a replicated file Does not allow any new access to file contentsDoes not allow any new access to file contents
71
AutoSYNC FuturesAutoSYNC Futures
Implementation dates subject to customer commitmentsImplementation dates subject to customer commitments TriggersTriggers
Execute a user-specified program or macro when file is synchronizedExecute a user-specified program or macro when file is synchronized Examples of functions that Triggers could perform:Examples of functions that Triggers could perform:
– Execute EDIT scripts to adjust system / volume namesExecute EDIT scripts to adjust system / volume names– SQLCOMP programsSQLCOMP programs– Run batch jobs or other user-defined processesRun batch jobs or other user-defined processes– etc...etc...
Enhanced RDF Online SynchronizationEnhanced RDF Online Synchronization Entry-sequenced file supportEntry-sequenced file support Improved performanceImproved performance Partitioned structured files (investigation)Partitioned structured files (investigation)
OSS support OSS support (investigation)(investigation) TCP/IP (non-Expand) supportTCP/IP (non-Expand) support
72
EscortEscort Tools Tools Tracing and debuggingTracing and debugging
Configured via a simple command without altering process startupConfigured via a simple command without altering process startup– No changes to Pathway server configuration neededNo changes to Pathway server configuration needed
Shows every procedure callShows every procedure call Show process startup and termination state (defines, assigns, Show process startup and termination state (defines, assigns,
startup message)startup message) Shows all Journaling operations Shows all Journaling operations Optionally shows input and output dataOptionally shows input and output data
Lock management toolsLock management tools One command to display all record and file locks (reworked One command to display all record and file locks (reworked
LISTLOCK command)LISTLOCK command) Deadlock detectionDeadlock detection Long transaction detectionLong transaction detection
73
Carr Scott Software -Carr Scott Software - family of productsfamily of products
EscortEscortSQL SQL Enscribe to SQL conversion (where it all began)Enscribe to SQL conversion (where it all began)
EscortEscortRANGER RANGER Database and partition analyzer (Escort SQL customers only)Database and partition analyzer (Escort SQL customers only)
EscortEscortAutoTMFAutoTMF (a.k.a. HP NonStop AutoTMF)(a.k.a. HP NonStop AutoTMF)TMF for non-TMF applications – data protection and disaster recoveryTMF for non-TMF applications – data protection and disaster recovery
EscortEscortAutoSYNC AutoSYNC (a.k.a. HP NonStop AutoSYNC)(a.k.a. HP NonStop AutoSYNC)Replication of non-database (non-audited) files – file synchronization Replication of non-database (non-audited) files – file synchronization
EscortEscortJournalingJournalingOn-line database loadingOn-line database loading