On 01 Feb 2013 10:50, Chamara Withanachchi wrote:
I do not look in to this old server as it is managed by another guy
in company, but the migration came to me. According to my colleague
it's in v4r3 and having TCP card and he specially mention that it's
running on M/36 (as I know it's a 150 box)
AFaIK the migration utilities were all removed since some V5 release,
so the actual migration might be easier using the old system. The
source members and data members can all be moved easily enough, but the
conversion features went away with the utilities. I forget the means to
move the data to media on the S/36, but the Restore S/36 File (RSTS36F)
restores the file data to the new system and the Restore S/36 Library
Members (RSTS36LIBM) to restore the /objects/ into source files QS36SRC
and QS36PRC and into the data files QS36LOD and QS36SBR. Many of the
S/36 library objects will be worthless without the associated CVTS36xxx
commands however; e.g. without CVTS36QRY, its associated member in
QS36SBR is just taking up storage. At the following link are some
documents for "migration" from the System/36; search on that in the page
Or my next option is let the current system run as it is and rewrite
everything in new box and migrate data to DB2 files and let them use
If the new application is done outside of the S/36EE then that would
probably be best. Best because that could avoid migration of most
eveything other than the database data and metadata. For example,
migrating the users, libraries, and library contents are not very
relevant if the new application is not running under the S/36E; all that
OCL and anything else dependent on S/36-like features would be moot.
Test and verify the ETL of the data, plus the results under the new
application, then schedule a cutoff for the final ETL event followed by
bringing the new application online to the new system.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.