What’s new in MIMIX 9

Stephan LeisseSolution Architect

stephan.leisse@syncsort.com

Continuous Value Delivered in MIMIX

MIMIX 7.0

Seven Wows!

• Vision Solutions Portal (VSP) • Single Point of Switch• Historical Reporting• Customizable Automation• Enhanced Apply Performance (2)• Integration with MIMIX Global

MIMIX 7.1

Faster, Stronger, Smarter

• 6 apply performance enhancements• Priority based auditing• Target side tracking & repair• Transaction analysis graphing• Replicated objects view• iOptimize• VSP on Windows• MIMIX event subscriptions• E-mail notification• 29 additional service pack features

MIMIX 8.0

Easy. Efficient.

• Data protection reports• Browser-based configuration• Integrated IFS replication• Streamlined standard install• Self-service license management• Enhanced access path maintenance• Enhanced server-to-server

communication• Server-level custom procedures• Support for IBM i 7.2 and Power 8• New MIMIX for PowerHA• New Metered usage licensing

MIMIX 8.1 SPs

Features in Service Packs!

• Active SBSD replication improvements

• Omit DTAARA/DTAQ content support

• VSP SNMP support• VSP configuration Export/Import• 64-bit JVM support for VSP• Up to 7x - 10x reduction in

STRMMX time• Significant switch time

improvement for enterprise environments (Up to 8x)

• IFS embedded generics support• RCAC support • IFS Audit Performance

improvements • VSP Performance / Scale

improvements• IFS Replication performance

improvement 2x-3x (8.1.17) • Temporal Table Support (8.1.18)

MIMIX 8.1

Innovation & Evolution

• Virtual Switch• Continuous AutoFix Technology • Enhanced replication performance• Greater control of audit status• Smart problem resolution• Simplified replication configuration• Automated point-in-time backups• Additional locking option• Side by side object comparison• Support for IBM i 7.3

October 2010

March 2012

Sept 2014

Jan 2016

2016-2017 SP’s

Faster, More Efficient ReplicationMulti-threaded Apply Benefits Incorporate true multi-threading in our DB Apply engine

• Significant increase in the number of active apply threads

• Thread ranges vary by product level (DR, Professional, Enterprise)

• MIMIX DR (LOW only)

• MIMIX Professional (LOW, MED)

• MIMIX Enterprise (LOW, MED, HIGH)

Better separation of DB, IFS, Data Area and Data Queue workloads within a DG

Will include a conversion feature to simplify the process of converting to/from multi-threading

Automatically drops into non-thread mode for non thread safe operations or certain file level operations

Unique “look ahead” processing for better efficiency and performance

Will continue to support current apply engine

Files 1 – Nare permanently assigned to one of the apply jobs

regardless of file size or processing time

DB Apply Today Limited to

6 Apply Jobs

A

B

C

D

E

F

Files 1 - 100

Files 101 - 200

Files 201 - 300

Files 301 - 400

Files 401 - 500

Files 501 – 600…

Multi-Threaded Apply

Files 1 – Nare dynamically and evenly distributed

across threads for fastest processing

ONE

Apply

Job

---Controlling

Thread

MANY

Threads

Threads respond back to

Controlling Thread when

complete and wait for

next request

Thread 1

Thread 2

Thread 3

Thread 4

Thread 5

Thread 6

Thread 7

Thread 8

Thread 9

Thread 10

Thread 11

Thread 12

Thread …

Redesigned, Mobile-Friendly Graphical DashboardNew in MIMIX 9

• Color-coded dashboard gives a summary view of all aspects of the MIMIX environment on a single page, including:

• Replication throughput

• Audit status

• Switch procedure results

• Data protection reports

• Configurable to include additional details

• Displays optimally on full-size monitor, tablet or smart phone

Benefits

• Easy to use for operators or admins with constrained skillsets or time

• Convenient access to MIMIX from any browser and device

• Color-coding enables monitoring at a glance

• Single dashboard for launching into all aspects of MIMIX management

New Key Metric Analysis ViewNew in MIMIX 9

• New view displays analysis of critical RPO and RTO metrics

• RPO based on current transaction volumes for the past minutes, hours or day

• RTO based on current transaction volumes and historical switch times

• Shows results of past switches

Benefits

• Easy visibility into current RPO and RTO metrics

• Enables reporting to stakeholders on ability to meet SLAs

• Helps identify trends to support early action if needed

Audit Level Improvements

Easier to understand controls for audit level• Reduces questions for “What is *LEVEL20?”Policy changes only to understand controls for audit level• Make the auditing options easier to understand with new terminology (words not

levels)• No affect to how the audits actually run• One value to enable or disable all audits for a data group without affecting auditing

options• Separate auditing option controls for File Data (#FILDTA), Directories (#IFSATR), and

Folders (#DLOATR) auditsAdd capability to run audits at highest level without policy changes • Already best practice to run audits at highest level in preparation for a switch

Mapping of Policies During Upgrade

Old AUDLVL policy New AUDRUN policy New auditing option policies

*DISABLED *DISABLED DLOAUDOPT(*ALL *ALL)IFSAUDOPT(*ALL *ALL)FILDTAOPT(100 100)

*LEVEL10 *ENABLED DLOAUDOPT(*ATTRONLY *ATTRONLY)IFSAUDOPT(*ATTRONLY *ATTRONLY)FILDTAOPT(5 5)

*LEVEL20 *ENABLED DLOAUDOPT(*ALL *ALL)IFSAUDOPT*ALL *ALL)FILDTAOPT(20 20)

*LEVEL30 *ENABLED DLOAUDOPT(*ALL *ALL)IFSAUDOPT(*ALL *ALL)FILDTAOPT(100 100)

Spool File Support

New object type - *SPLF• Affects all commands and panels that support OBJTYPE

xxxDGOBJE commands will support new object type• Valid on ADD and CHG when REPSPLF(*YES) and

OBJTYPE(*ALL|*SPLF|*OUTQ)

• Default values for spool file fields• REPSPLF(*NO)

• Spool File Name (*ALL)

• Creator Job Name (*ALL)

• UserName (*ALL)

Command Example – Object Type *SPLF

New Object type *SPLF

Spooled file criteria (SPLF) -

3-element configuration

New in MIMIX 9

• Support for ignore differences for auditing and synchronization

• New parameter on configuration

• Object entries, DLO entries, IFS entries and File entries

• New option on SYNCxxx commands

• Controls whether ignored attributes are kept as they already exist on the target system, if possible, or forced to the values from the source system object

Distribution Feature

Production Server

HA/DRServer

Data Distribution

Server

Ignored attributes supportThis capability for ignoring differences is basically acknowledging that the objects are NOT fully synchronized between source and target system.

• Therefore we are restricting the capability to ignore differences to NON-SWITCHABLE data groups (either replicating to a replicate node or a data group configured as not switchable)

• Only Auditing and Synchronizing will use the Ignored attribute configuration

• This does NOT change replication – if the attribute is changed on the source system, it WILL BE replicated!

• This does NOT change Target Journal Inspection (TJI) - changes to objects on the target are still reported and recovered

None (*NONE)

Attributes Only (*ATRONLY)

Data Only (*DATAONLY)

Attributes and Data (*ATRDATA)

Select Differences

Add Data Group Object Entry (ADDDGOBJE)

Type choices, press Enter.

Additional Parameters

File and tracking ent. opts: FEOPT

Journal image . . . . . . . . *DGDFT

Omit open/close entries . . . *DGDFT

Replication type . . . . . . . *DGDFT

Lock member during apply . . . *DGDFT

Apply session . . . . . . . . *DGDFT

Collision resolution . . . . . *DGDFT

Disable triggers during apply *DGDFT

Process trigger entries . . . *DGDFT

Synchronize on start . . . . . . SYNCONSTR *NO

Attributes to ignore . . . . . . IGNATR *NONE

+ FOR MORE VALUES

BOTTOM

F3=EXIT F4=PROMPT F5=REFRESH F12=CANCEL F13=HOW TO USE THIS DISPLAY

F24=MORE KEYS

New IGNATR parameter

NEW – IGNATR parameter

New column Ignored Differences

Synchronize Object (SYNCOBJ)

Type chioces, press enter.

Synchronize authorities . . . . SYNCAUT *YES

Synchronize attributes . . . . . SYNCATR *DFT

Save active . . . . . . . . . . SAVACT *SYSDFN

Save active wait time . . . . . SAVACTWAIT 120

Maximum sending size (MB) . . . MAXSIZE *NOMAX

System 1 ASP group or device . . ASPGRP1 *CURRENT

System 2 ASP device number . . . SYS2ASP *SAVASP

System 2 ASP device name . . . . SYS2ASPD *ASPGRP1

Submit to batch . . . . . . . . BATCH *YES

Ignored attribute processing . . IGNATRPRC *KEEP

Job description . . . . . . . . JOBD MXSYNC

Library . . . . . . . . . . . *LIBL

Job name . . . . . . . . . . . . JOB *CMD

BOTTOM

F3=EXIT F4=PROMPT F5=REFRESH F12=CANCEL F13=HOW TO USE THIS DISPLAY

F24=MORE KEYS

ALREADY AT BOTTOM OF AREA.

Ignored Attributes - SYNC commands

New parm – IGNATRPRC• *KEEP - keeps current target

values of ignored attributes

• *FORCE – forces ignored attributes to source system value

Only used by SYNCxxxcommands when a data group is specified

Display Report

Query . . . : DLMDTAD/CMPDLOAQD

Position to line . . . . .

Line ....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+...

COMPARED DIFFERENCE SYSTEM 1 SYSTEM 2 SYSTEM 1

ATTRIBUTE INDICATOR INDICATOR INDICATOR DLO

000001 * *IN DLMIGN2/DOC1

000002 *PRVAUTIND *IN DLMIGN2/DOC1

000003 *PUBAUTIND *IN DLMIGN2/DOC1

****** ******** End of report ********

Audit Results File Example With *IN

NEW – *IN difference indicator

NEW – *IN Object audit status

JOBQ Entries ReplicationSupport for replicated jobs on a job queue

What are replicated jobs?

• These are jobs that are submitted to run on the source

• They may or may not have had a chance to run and/or complete on the source before switch

• These jobs are not allowed to run on the target until switch time

• Jobs are staged only on the target until needed, but completed jobs are cleaned up

• The resolutions of these jobs happen on the new source system after a switch

• They can be resolved before starting replication, or they can be delayed until later

• You may view and work with staged jobs on the target, but submitting them will fail

• When the final job is resolved either by submitting or removing, the indicator is turned off

New configuration parameter - REPJOB• Controls if job information within *JOBQ’s is replicated

• Available on xxxDGOBJE commands

New commands:• Work with interface for viewing and dealing with Replicated Jobs• WRKREPJOB

• DSPREPJOB

• RMVREPJOB

• RTVREPJOB

• SBMREPJOB

Replicated Job Support – Native Interface

Command - CHGDGOBJEChange Data Group Object Entry (CHGDGOBJE)

Type choices, press Enter.

Data group definition: DGDFN

Name . . . . . . . . . . . . . Name, F4 for list

System 1 . . . . . . . . . . . Name, *LOCAL, *RCYDMN...

System 2 . . . . . . . . . . . Name, *LOCAL, *RCYDMN...

System 1 library . . . . . . . . Name, generic*, *NONE LIB1

System 1 object . . . . . . . . Name, generic*, *ALL, *NONE OBJ1

Object type . . . . . . . . . . *ALL Type, *ALL, F4 for list OBJTYPE

Attribute . . . . . . . . . . . *ALL Name, *ALL, F4 for list OBJATR

Spooled file criteria: SPLF

Spooled file name . . . . . . *ALL Name, generic*, *ALL

Job name . . . . . . . . . . . *ALL Name, generic*, *ALL

Job user . . . . . . . . . . . *ALL Name, generic*, *ALL

To data group definition: TODGDFN

Omit content . . . . . . . . . . *SAME *SAME, *NONE, *DTAARA... OMTDTA

+ for more values

Replicate jobs on job queue . . *SAME *SAME, *NO, *YES REPJOB

Replicate spooled files . . . . *SAME *SAME, *YES, *NO REPSPLF

Keep deleted spooled files . . . *SAME *SAME, *DGDFT, *YES, *NO KEEPSPLF

Spooled file options . . . . . . *SAME *SAME, *NONE, *HLD, *HLDONSAV SPLFOPT

Object retrieval delay . . . . . *SAME 0-999, *SAME, *DGDFT OBJRTVDLY

User profile status . . . . . . *SAME *SAME, *DGDFT, *DISABLED... USRPRFSTS

System 1 library ASP number . . *SAME 1-32, *SAME, *SRCLIB, *ASPDEV LIB1ASP

System 1 library ASP device . . *SAME Name, *SAME, *LIB1ASP LIB1ASPD

Replicate Jobs

LODDGOBJE

WRKDGOBJE –

DSP/PRT/Outfile

RTVDGOBJE

REPJOB - Parm

in other commands

Work with Replicated Jobs (WRKREPJOB)

Type choices, press Enter.

Data group definition: DGDFN

Name . . . . . . . . . . . . . *ALL Name, generic*, *ALL...

System 1 . . . . . . . . . . . *ALL Name, generic*, *ALL...

System 2 . . . . . . . . . . . *ALL Name, generic*, *ALL...

Orig. system job queue . . . . . *ALL Name, generic*, *ALL JOBQ

Library . . . . . . . . . . . *ALL Name, *ALL

Job name . . . . . . . . . . . . *ALL Name, *ALL JOB

User . . . . . . . . . . . . . *ALL Name, *ALL

Number . . . . . . . . . . . . *ALL 000000-999999, *ALL

Job status . . . . . . . . . . . *ALL *ALL, END, HLD, JOBQ... JOBSTS

Originating system . . . . . . . *ALL *ALL, *LCL, *RMT ORIGSYS

Application group . . . . . . . *ALL Name, *ALL, *NONE... AGDFN

Data resource group entry . . . *ALL Name, *ALL, *NONE... DTARSCGRP

Output . . . . . . . . . . . . . * *, *PRINT, *OUTFILE OUTPUT

File to receive output . . . . . Name OUTFILE

Library . . . . . . . . . . . *LIBL Name, *LIBL, *CURLIB

Output member options: OUTMBR

Member to receive output . . . *FIRST Name, *FIRST

Replace or add records . . . . *REPLACE *REPLACE, *ADD

Bottom

F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display

F24=More keys

Command Work Replicated Jobs - WRKREPJOB

NEW – WRKREPJOB Command

Work with Replicated Jobs

System:

Type options, press Enter.

4=Remove 5=Display 6=Print 7=Submit

Data Orig. Job Job

Opt Group System 1 System 2 job queue Name Status

DG1 CHICAGO LONDON JOBQ1 MYJOB JOBQ

STANDALONE CHICAGO LONDON JOBQ2 MYJOB JOBQ

Bottom

Parameters or command

===>

F3=Exit F4=Prompt F5=Refresh F10=View AG name F12=Cancel

F13=Repeat F18=Subset F21=Print list

Recovery status added for file, IFS tracking, and object tracking entries

Most severe status of any recoveries for an object identified in a file entry, IFS tracking entry, or Possible recovery status values:

• *NONE - No recoveries exist for the object or all known recoveries for the object have been successfully handled

• *NEW - The recovery is new and processing has not yet started

• *CAPTURING - The recovery is capturing information on the source system

• *WAITING - The recovery is waiting to be processed while a virtual switch is in progress and either the database apply process is ended or has a backlog

• *FAILED - The recovery has failed

WRKDGFE example

DSPDGSTS example

MIMIX cleanup

1. File Alias Naming

2. UPS Monitor

3. CHKMMX

4. CLRMMXDTA

5. ECS Support

6. SAP 3 Tier support

7. HW Switch types SM517A & SM900A

8. Data Area Polling

9. Extended Policy MCDISABLEDG

10. SYNCDG

11. *Apply History Logspaces

12. OBJONTGT(*SYNC)

13. Transfer definitions types *SNA & *OPTI

• Includes *SNA configured RJ

Examples

26

WRKDG Before

WRKDG After

CRTDGDFN

DSPDGDFN - APYHSTLOG

MIMIX 9.0 other Highlights

Additional Support / Best Practices

• LPARs > 256

• Remove midnight rollover

• Modified audit scheduling best practices

• MBRRCDCNT recoveries

• IBM OS 7.1 minimum release support

• Status send process status

Q&A