Planning For Migration From IBM Mainframe Systems

1
Planning For Migration From IBM Mainframe Systems
David Wade Technology Consultant Professional
ServicesCompaq
2
(No Transcript)
3
Objectives

• There are still many mainframe based e-mail
  systems in operation
• This session looks at the factors to consider
  when planning a migration from these systems

4
Which Systems Covered?

• Office Vision/VM and PROFS
• Office Vision/MVS
• Fisher TAO
• Verimation Memo
• Office Vision / 400

5
Auditing Existing System

• We need to know what we are starting from
• Mainframes are complex environments
• Complexity from age
• Complex through size
• Following slides highlight some areas to check

6
Functionality

• All products were sold as Electronic Offices,
  not just e-mail
• Check which features are used
• E-mail
• Calendar/Diary
• Document preparation, storage, and management
• Directory services
• Any other uses - e.g. simple workflow

7
Basic E-Mail Connectivity

• Just plain messages or attachments
• Any e-mail based applications
• Expenses approval
• Batch job status reports
• Which client are they using
• Standard 3270 screens
• PC based client
• Commtouch pMail
• Home Grown

8
External Connectivity

• Native connections to IBMMAIL for X.400 and SMTP
• SMTP connections to an ISP
• X.400 connections
• Special connections
• SITA, Pagers, SMS

9
Internal Connectivity

• Mainframe or mid-range systems
• AS/400
• VAX/VMS
• Gateways to LAN based systems -
• MS Mail
• CCMail
• Others
• Softswitch

10
Calendar/Diary FunctionThis is IMPORTANT !!!

• In general organizations either
• Live and die by the calendar
• PROFS OV/VM especially
• Dont use it except perhaps for the odd dinner
  date
• Also check for meeting rooms or resources

11
Directories/Address Books

• Which address book in use
• Early versions had limited function
• User customized and expanded
• 3rd party add-ins and PRPQs
• Later came Enterprise Address Book (EAB)
• Check any existing synchronisation
• Any other uses
• E.g. Phone List

12
Documents And Document Libraries

• Document Formats -
• IBM Formats - DCF, DCA, DW370
• PC File Formats - WP, Ami-Pro
• GDDM Graphics Files
• External document references
• Used to point to paper documents

13
Other Uses

• If MEMO or TAO do they use forms
• Any mail-enabled applications
• E.g. batch status reports
• What other customisation
• Extra Menu Screens (Panels)
• Extra Menu Items
• Special User Exits
• Any other 3rd part add-ins
• CLASY

14
Report Findings

• Agree with users what you have
• E-Mail connectivitey
• Documents
• Calenders
• Be prepared for things to crawl from the woodwork

15
Spring Cleaning

• Dead users
• Dead connections
• Document library
• Ancient treasure troves of messages pre-dating
  the Dead Sea Scrolls

16
Stage II

• Planning the Migration

17
Select The Connector

• SNADS or PROFS
• Meeting Notice Conversion
• Flexible RR and COD handling
• Only one attachment per message
• Warning - Only single stream
• SMTP or X.400
• May be better for TAO and MEMO(not native SNADS
  systems)

18
Select Physical Link

• For SNA connectors
• SNA Server required
• SDLC or Token Ring may be needed
• May be problems with host resources
• For X.400
• May need X.25 card - only 2 types supported by
  Exchange

19
Select the logical link

• OV/VM or PROFS connector
• No choice - must be NJE
• Can use multiple links for resilience
• SNADS connector
• Can use dependant or independent LUs
• Independent LUs preferable but
• Not supported by all products
• Only one link supported

20
Plan SNADS/PROFS

• Plan for node names for Exchange
• Default - one DGN (node) per site
• May want to use one DGN per Org
• May want to use one DGN per group
• RSCS Nodes
• For PROFS may need to set up additional nodes

21
Connector Options

• Documented in the LINKINI.HLP
• In c\exchsrvr\connect\exchconn
• Attachment handling
• Allow attachments from MS Exchange
• May depend on client used
• File mappings
• Control mapping host types to PC types
• Control EBCDIC/ASCII conversion

22
Connector Options

• RR and COD mappings
• Host returns confirmation on in-box open
• Connector allows this to be mapped to RR or COD
• Must document and tell users
• Handling of FFT documents
• By default sent as attachments
• Can be sent in-body - more natural

23
Directory Migration And Co-existence

• Need to plan for Directory Sync
• Microsoft Supplied solution for PROFS, OV/MVS and
  MEMO
• Direct ME for OV/400 -
• Needs Connect-Me connector
• Fisher TAO - Shuttle from CompuSven
• Roll Your Own or manual sync
• Other tools e.g. Compaq LDSU
• Will usually require customization

24
Calendaring/Scheduling

• Is the Calendar Connector required?
• OV/VM ONLY
• Free/Busy only
• Not required for meeting notices
• Performance hit on mainframe?
• PC Meeting Scheduler easy to use

25
Documents

• Format Conversion is a problem
• Connector converts some formats
• Some formats (DCF, LIST3820) may not be usable on
  a PC
• Some formats (e.g. RFT/FFT) may need additional
  software on PC
• Single image is lost
• May not have documents on host
• External Reference
• May use tools (CLASY Archive) not available in
  Exchange

26
Schedules, Forms

• May be able to migrate schedules
• But speed may mean you dont want to
• Forms are more difficult
• 3270 FORMS - SEQUENTIAL FLOW
• WINDOWS GUI - MORE EVENT DRIVEN
• Probably better to start again !!!
• May be able to use standard PC tools.

27
External LinksSMTP , X.400, IBMMAIL

• Plan for co-existence
• External Addresses known by both sides
• Use Exchange Server Connector
• Best features for Exchange Users
• Host users may need to use in-body addressing
• Use server connector
• May cause least initial disruption
• Limited function for Exchange

28
Planning A Pilot

• Proof-of-concept pilot
• No Real Users
• Tools can be tested
• Staff gain experience
• Exchange Connectivity Administrator
• Documentation can be verified
• Allows functionality to be tested
• Also allows different options to be tested

29
Planning A Pilot

• Use the pilot to test
• Document Conversions
• RR/COD configuration
• Gateway Access
• Distribution Lists
• Should have a formal plan
• Check list of the test
• Prepare formal report

30
Migrating Existing Data

• If you can get away with it - dont do it
• Migration tools
• Only migrate mail not the document store
• May not convert formats
• May have problems with external addresses - names
  may change

31
Some Common Problems

• Mainframe team compartmentalised
• Difficult to find the right person
• May get conflicting answers
• Mainframe team Anti PC
• Their jobs may vanish
• Will try to prove Mainframe is best
• People problems
• Exchange environment richer Learning Curve

32
Migration Problems

• Duplicate SNADS/PROFS addresses
• Plan to prevent
• Distribution lists
• May exist in two places
• Unrepliable messages
• Because the user has moved use
• OV/Rerouter - TBS Soft
• AWAY Facility/VM (5799-FLP)

33
Mail Problems

• RR and COD work differently
• Need to educate users
• Reply All may not work as expected
• Again, educate users
• Connectivity Administrator
• Need to learn how to use

34
More Information

• Me Dave.Wade_at_compaq.com
• Exchange Connectivity Competency Center
  ec3_at_microsoft.com
• Migration
• http//www.microsoft.com/exchange/migrate
• Load balancing whitepaper http//support.microsof
  t.com/support/exchange/content/whitepapers/ovvm.a
  sp
• Customizing dir sync KB Q180517
  httpwww.microsoft.com/support

35
Third Party Tools

• TBS Software
• www.tbssoft.com
• Keane
• product_support_at_keane.uk.com
• CompuSven
• http//www.compusven.com/microsoft.htm

36
(No Transcript)