Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Migration from 9370 cics to AS400

26 views
Skip to first unread message

Jim Miller

unread,
Nov 25, 1996, 3:00:00 AM11/25/96
to

We are planning to migrate from a 9370 using VSE/CICS to an AS400. Does
any one have any suggestion on a good? migration plan from VSE/CICS to the
AS400.
Experiences on using AS400 CICS would be appreciated.

Thanks,
Jim Miller (jmi...@rosenet.net)

Randy Kuseske

unread,
Nov 27, 1996, 3:00:00 AM11/27/96
to Jim Miller


Jim,

I'm a member of the CICS/400 development team. Believe the key to a
good, clean migration to CICS/400 is planning and understanding CICS
for the AS400. CICS/VSE is the architectural standard for CICS and
has functions/features that may or may not be supported by other
platforms, such as the AS400.

In general, all CICS/VSE applications can be migrated relatively
easily. Here is a general list of things to consider when planning
for the migration:

1. Ensure that when planning the right-sizing, the AS400 processor
(CPU) is sized correctly. There are a few tools available for this.
Contact your branch office or marketing rep for additional
information.

We've been through several situations with customers where the
CPU is not sufficient for the workload on the AS400.

2. Understand that due to architectural and implementation
differences,
CICS/400 does not always support the exact same features or work
the
same as CICS/VSE. You may need to do some fine tuning. A good
reference for determining what API and SPI are available is the
manual "CICS Family: API Structure", SC33-1007.

3. When planning for the migration, you may want to consider changing
some of your application(s) to run natively on the AS400. Due to
implementation differences, some functions run faster natively
than they do through CICS/400.

4. Part of the performance tuning for CICS/400 will be set up and
fine tuning of the AS400. This is a fact that is often overlooked
during a migration.

5. Don't know your situation, but you may want to consider:
a) A third party migrator. There are several.
b) Bringing your application into the Rochester lab through
Partners in Development (PID).

6. Here's a list of manuals that you may want to peruse:

CICS Family Manuals:
SC33-0824 CICS Family: Inter-Product Communication
SC33-1007 CICS Family: API Structure
CICS/400 Specific Manuals:
SC33-1384 CICS/400 Problem Determination
SC33-1386 CICS/400 Application Programming Guide
SC33-1387 CICS/400 Administration and Operations Guide
SC33-1388 CICS/400 Intercommunication
CICS/400 Redbooks:
GG24-2534 CICS Clients Unmasked
GG24-4006 Mainframe CICS to CICS/400 V2R2 Migration Cookbook
GG24-4182 CICS/400 Tasks and Examples

The IBM CICS web page at "http://www.hursley.ibm.com/cics/".

If you have any specific questions, comments, or would like additional
assistance, please contact me.

/s/

Randy Ray Kuseske
email Net: rrku...@vnet.ibm.com
Phone: (507) 253-4866
(t/l) 553-4866
Address: Dept HPT(AiC) CICS400
Bldg 005-2, C109
IBM Rochester, MN

0 new messages