• Subject: RE: Using RISC as development, sending to CISC. Any problems forseen?
  • From: Bob Crothers <bob@xxxxxxxxxxxxxx>
  • Date: Wed, 1 Jul 1998 08:20:22 -0000
  • Organization: Cornerstone Communications, LLC

Actually IMHO, One of the server models makes a great development box. 

What happens most on a development box?  Compiles.  In batch.  Which 
is where the server models scream.

Of course, if your programmers are in the habit of interactive 
compiles, that needs to be stoped.  And other stupid programmer tricks 
like large interactive querys, doing CPYF of a million records, etc 
should never be done interactively on any system.  But especially not 
on a server model.

We use a 40S for a development box and are very happy with it.

Regards,
Bob Crothers
Cornerstone Communications, LLC
www.faxserver401.com



-----Original Message-----
From:   Vernon Hamberg [SMTP:hambergv@goldengate.net]
Sent:   Tuesday, June 30, 1998 6:45 AM
To:     MIDRANGE-L@midrange.com
Cc:     bvstone@taylorcorp.com
Subject:        Re: Using RISC as development, sending to CISC.  Any problems 
forseen?

Brad

At 01:14 PM 6/30/1998 -0500, you wrote:
>Hello.
>
>We are currently thinking of upgrading our developement machine to a
>RISC box (50S, I think).  We have multiple plants that use our 
software,
>some on RISC, most on CISC.
>
>We did some testing today and it seems if you compile an object on a
>RISC box as V3R2, and run it, it does not get converted to RISC (or
>already is RISC).  We can send it to a CISC box and it seems to run
>without problems.
>
>I guess we are used to sending programs from our CISC devo box to a 
RISC
>machine and having it convert the object automatically.  We thought 
that
>if we compiled to V3R2 on a RISC box, and ran it, it would convert to
>RISC, making it unsendable to CISC boxes.  But, it seems this isn't 
the
>case and that things will work out fine.
>
>Does anyone have experience, or things to watch out for after we 
convert
>to RISC and still send the object to CISC boxes?
>

No problemo!

We do this all the time. Our dev box is a 510 at v4r1. We have various 
v3r2
boxes, as well as a v3r7 and another v4r1. Absolutely no problem, so 
long
as you use the TGTRLS parameter, as you seem you be doing. Be sure to 
use
the appropriate TGTRLS on your save files, too. We use Aldon's CMS 
change
management system, which handles the save file issue automatically. It 
does
not, however, handle the TGTRLS for creating objects.

I _would_ question using a server box like the 50S. You could get poor
interactive performance. Admittedly it's supposed to be better now, 
but we
got bit verrry badly with a 50S. If you can keep your interactive CPU 
% <
10%, you'll probably be OK.

Cheers

Vernon Hamberg
Systems Software Programmer
Old Republic National Title Insurance Company
400 Second Avenue South
Minneapolis, MN  55401-2499
(612) 371-1111 x480


+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.