Migrating Applications From VSE To OS390

PRINCE Software, Inc.
Migrating
Migrating Applications
Applications
from
from
VSE
VSE to
to OS/390
OS/390
Z/VM, VSE and Linux
on IBM Enterprise Servers
Technical Conference
Session E86
Ted Agen
Why
Why Installations
Installations Migrate
Migrate
n Technical Issues
– Capacity Constraints
– Enhanced Systems Availability
– Systems Management
1
Teda@princesoftware.com
Why
Why Installations
Installations Migrate
Migrate
n Business Reasons
– Mergers & Acquisitions
– Data Center Consolidations
– Application Availability
– Staff Availability
– Positioning for New Technology
Migration
Migration Overview
Overview
n Review Hardware Capacities
n Identify VSE Components
– System Software
– Vendor Products
– Application Software
n Select Replacement Strategy
2
System
System Software
Software
n Operating System
– Existing MVS or OS/390 Environment
– New OS/390 Environment
n Environmental/Operational Products
– Do We Need It?
– OS/390 Version?
– Replacement Product?
– New Functions?
Environmental
Environmental // Operational
Operational
Products
Products
n Security System
n Editor
n Library System / Configuration Mgmt
n Automated Scheduler
n Tape Management System
n Report Distribution / Print Utilities
3
Formalized
Formalized Procedures
Procedures
n Security
n Change Control / Configuration Mgmt
n Problem Control / Help Desk
n Performance Measurement
n Capacity Planning
Application
Application Software
Software
n In-House Developed
– Convert
– Re-develop
– Vendor Package
– New Platform
n Vendor Products
– OS/390 Version
– Convert
– Replacement Package
4
Pre-Conversion
Pre-Conversion Preparation
Preparation
n Application Inventory
– Production JCL
– Source Libraries
– Core Image Libraries
– CICS PPT / RDO
– VSE Production LISTCATs
Pre-Conversion
Preparation
n Application Analysis
– Source Languages
– Files / Databases
– Vendor / Home-Grown Utilities
– Exception Items
5
Pre-Conversion
Preparation
n Standards & Naming Conventions

– Dataset Names
– Program / Job Names
– Library Structure
– JCL Standards
Project
Project Planning
Planning
n Migration Strategy
– Phased vs. Mass Conversion
n Conversion Work Groups (Kernels)
– Application Dependencies
– Ease of Testing
n Conversion Procedures
– Program / JCL Transfer
– Translation Process
– Testing Procedures
6
Project
Project Control
Control
n Project Staffing
– Conversion Specialists
– Application Knowledge
n Education
– Formal Education
– Knowledge Transfer
n Schedule & Timelines
– On-going Workload
– Migration Pace
– Desired Completion Date
Program
Program Conversion
Conversion
n COBOL for OS/390
– DOS/VSE COBOL
– COBOL II
– COBOL for VSE/ESA
– COBOL REPORT WRITER
n BAL
– Called Subroutine
– Main Program / Driver
– High Level Assembler
– 31-bit Addressing
7
Program
Program Conversion
Conversion
n PL/I
n RPG, 4GLs
n Macro Level CICS
n Code Generators
Program
Program Conversion
Conversion
n Special Considerations
– ISAM / BDAM
– Console Messages
– ABEND Handling
– COMREG
– Print Output
– SEGMENT Macro
8
JCL
JCL Conversion
Conversion
n VSE JCL
– Input Stream
– PROCs & SLIs
– Standard Label Track
– Default Assignments
– Carry-Forward File Definitions
– Vendor Generated JCL
JCL
JCL Conversion
Conversion
n File Attributes from Programs
n // DATE Usage
n // UPSI
n // PAUSE
n Power LST Statements
n Conditional JCL / Return Codes
9
OS/390
OS/390 JCL
JCL
n MVS-Style PROCs
n Symbolic Parameters
n I/O Efficiency
n DISP Parameter
n Conditional JCL / COND Parameter
n Control Statement PDS
File
File // Database
Database
Considerations
Considerations
n Sequential DASD
n Tape Files
n VSAM
n Databases
n File / Database Transfer
n File Sharing
10
Batch
Batch Systems
Systems Workflow
Workflow
n VSE Baseline Run
n Program & JCL Translation
n OS/390 Volume Testing
n Output Verification
n Problem Resolution
CICS
CICS Systems
Systems Workflow
Workflow
n Program Translation
n BMS Map Assembly
n Difference Resolution
n Unit Testing
n Load Testing
n Problem Resolution
11
Automated
Automated Conversion
Conversion Tools
Tools
n Inventory Tools
– Inventories Programs, Jobs, Files
– Program, Job, File Cross-references
– Identifies Vendor Utilities
– Provides Counts of Job, Jobsteps,
Programs, Files
Automated
Conversion Tools
Tools
n Language Translators
– COBOL, BAL, PL/I, RPG, 4GLs
– Supports Library System
– Supports Database Coding
– Processes COPY/INCLUDE Members
Dynamically
– Translation Audit Trail
12
Automated
Conversion Tools
Tools
n JCL Translator
– Generates PROCs / In-line JCL
– Provides Automated Renaming of Files, JOBs
& Other Elements
– Recalculates Blocksize & SPACE Allocations
– Automates Replacement of Utility Steps
– Generates PROC Overrides for Testing
– Generates File Compare Steps for Output
Verification
Conversion
Conversion Vendors
Vendors
n Proven Track Record
n Multiple Conversion Strategies
n Automated Tools
n Fixed Price
n Supports Client Migration Pace
n Provides Support of Client Testing
13
Questions
Questions ??
14

Migrating Applications From VSE To OS390

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Migrating Applications From VSE To OS390

Uploaded by

Copyright:

Available Formats

PRINCE Software, Inc.

n Standards & Naming Conventions

You might also like