Re: System 36 and Machine 36

Just a few notes:
If you have a save of the files and libraries from the m36,
then look at the rsts36f command for files and the rsts36libm
for library source members.

On the "to" system, GO CMDS36 for many commands, especially
Configuration and Environment Attributes.

You will need SS1 option 5 (which is free but may not be installed) on the
system for the S36 Environment.

(and Chuck's description of my earlier statement is spot on - I garbled the
thing using "like..." in a bad way.)
Jim Franz

----- Original Message ----- From: "Chamara Withanachchi" <chamaraw@xxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Cc: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, February 01, 2013 1:50 PM
Subject: Re: System 36 and Machine 36

Hi,

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 its in v4r3 and having tcp card and he specially mention that its running on M/36 (as I know it's a 150 box)

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 new application.

Thanking you


Chamara Withanachchi

Sent from my iPad

On 2013 පà·Tබ 1, at ප.à·?. 11.59, rob@xxxxxxxxx wrote:

Ok, I am thinking if your old box has TCP/IP then it is NOT M36 but it is
OS/400 with the S/36 environment installed. Even the first AS/400's
didn't have TCP/IP. Can the box do any os/400 commands at all? Well,
duh, Rob, of course it does. If he can save it to save files it must be
S/36 environment and not M36.

If this is all true then your only problem should be if the programs have
observability enough to run on something higher than V5R4. Study
ANZOBJCVN.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: chamaraw@xxxxxxxxxx
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>,

Date: 02/01/2013 12:11 PM
Subject: Re: System 36 and Machine 36
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Hi,

My old box have a tcp connectivity, I was thinking to use save files to
transfer data to power7 box and I'm having v4r3 in my old box.

I have the source codes of all old programs. So I guess that will b ok.


Chamara
Sent via BlackBerry® from Dialog

-----Original Message-----
From: DrFranken <midrange@xxxxxxxxxxxx>
Sender: midrange-l-bounces@xxxxxxxxxxxx
Date: Fri, 01 Feb 2013 11:48:53
To: Midrange Systems Technical Discussion<midrange-l@xxxxxxxxxxxx>
Reply-To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: System 36 and Machine 36

This is absolutely a source code migration. You can restore the files
and convert them as has been mentioned. The source code is required for
this migration as well as the S36 versions of the compilers. The S/36
OCL will run in the S/36 environment. If you have ALL of that then you
can do a migration.

You will need some flavor of tape compatibility to get that data moved
or a very old machine that supports M36 and then configure
communications between the M36 and OS/400 to move the stuff. Wow my head
hurts just trying to remember THAT configuration...

- Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

On 2/1/2013 11:42 AM, Jerry C. Adams wrote:

Chamara,

Like Rob, the good (well, fair) Doctor, and I have pointed out M36 is no
longer supported. In fact, according to this Tech Document, they will

not

even run:

http://www-912.ibm.com/s_dir/SLKBase.nsf/1ac66549a21402188625680b0002037e/49

dd3c2549f2e6ad8625698a0060e07d?OpenDocument
http://tinyurl.com/M36forI

Jerry C. Adams
IBM i Programmer/Analyst
Sex is hereditary. If your parents never had it, chances are you won't
either.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.