RE: CISC to RISC CONVERSION

Ah, the old logical files spanning libraries problem.  My boss solved this 
easily enough.  You run two RSTLIB's.
RSTLIB SAVLIB(*ALLUSR) DEV(TAP01) MBROPT(*ALL) ALWOBJDIF(*ALL)
RSTLIB SAVLIB(*ALLUSR) DEV(TAP01) OPTION(*NEW) MBROPT(*ALL) ALWOBJDIF(*ALL)
That option  OPTION(*NEW) will get the missing logical files.  Works like a 
champ.  Tested it using an unload/reload.  Store this into your recovery 
strategy.  
IBM should document this in the backup and recovery guide.






george.lemen@weyerhaeuser.com on 02/29/2000 06:50:46 PM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      
Fax to: 
Subject:        RE: CISC to RISC CONVERSION

Michael --
 I've done a half dozen of these migrations.
 As long as you follow the book IBM provides TO THE LETTER the migration
goes very well indeed.
 When you do a side-by-side make sure you understand how your environment is
put together. The hardest migration I've done is one where logical files,
physical files, journals and journal receivers are in different libraries.
You have to either get these reloaded in the correct order or you have a lot
of clean up. (A good disaster recovery plan with a detailed set of
instructions for reloading the system at the DR center is helpful -- IF the
reload has been successfully tested!)
 You will run into all the changes you get at a release upgrade to boot, so
be aware of what changes have been made to IBM's objects (what commands have
been duplicated, what changes you make each release etc). As always those
changes have to be re-implemented.

 The things that come to mind that have been the biggest impediments for me:
*       Software that is not observable and the source is missing. In the
case of vendor packages, you will most likely be replacing the software. For
in-house code you have a problem.....
*       Making sure I understand each vendor's migration process, and how
they move any data related to their application.
*       Synchronizing data (particularly with vendor applications) if there
is a large "run in parallel" window.
 
The good news is the compatibility is really there.
Good luck!
George Lemen
Sr. Project Analyst
CIBER Inc
Weyerhaeuser CER Technical Support and Operations Manager
Weyerhaeuser phone: (253) 924-7975
Weyerhaeuser e-mail: george.lemen@weyerhaeuser.com
CIBER Phone (425) 451-2575 x142
CIBER E-mail: glemen@ciber.com

> ----------
> From:         kenney@uwindsor.ca[SMTP:kenney@uwindsor.ca]
> Reply To:     MIDRANGE-L@midrange.com
> Sent:         Tuesday, February 29, 2000 9:36 AM
> To:   jdelist@jdelist.com; midrange-l@midrange.com
> Subject:      CISC to RISC CONVERSION
> 
> CISC to RISC  Conversion.
> 
>               Can anyone who has converted  from CISC to RISC comment
> briefly on how difficult/easy this was.  Did you do the migration yourself
> or did you have someone else do it for you i.e I.B.M     How long did it
> take .
> 
> 
> 
> This post is not a solicitation for CONSULTING services.
> 
> Michael Kenney
> IT Services
> University of Windsor
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---