Using RISC as development, sending to CISC. Any problems forseen? -- MIDRANGE-L

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?


Bradley V. Stone        
bvstone@taylorcorp.com
http://prairie.lakes.com/~bvstone/
"Closing my mouth before I scream.  No one can shake my self-esteem."
-YJM


> -----Original Message-----
> From: Buck Calabro [SMTP:mcalabro@commsoft.net]
> Sent: Tuesday, June 30, 1998 12:31 PM
> To:   'MIDRANGE-L@midrange.com'
> Subject:      RE: Alert job owner of QSYSOPR message?
> 
> On Tuesday, June 30, 1998 11:16 AM, Rob Berendt [SMTP:rob@dekko.com] 
> wrote:
> > See:
> > >From "Keeping Watch on QSYSOPR," NEWS 3X/400, March 1994
> >
> > I'd copy the code but parts of it say copyright and since this
> mailing
> > list is managed by the competition....
> 
> AFAIK, this listserver is managed by David Gibbs; not Midrange
> Computing. 
> 
> The copyright instructions in News/400 read (in part) "These programs
> may 
> not be reproduced or distributed in any form without permission in
> writing 
> from the publisher."  I wonder how they expect me to type the source
> code 
> into a computer if I can't reproduce the programs in any form?
> Obviously, 
> they want to keep this stuff public domain as opposed to having it 
> integrated into a "for fee" product, and I don't think News/400 would
> have 
> a problem with one of us posting the complete (copyright notice
> included) 
> code from the article.  I'll write them and find out.
> 
> In any event, go to http:www.news400.com, click the Resources tab on
> the 
> left frame, click the "Code" link on the left frame and there you'll
> see 
> the code archives.  you should be able to copy down the March 94 code
> from 
> there.
> 
> Buck Calabro
> Commsoft, Albany, NY
> mailto:mcalabro@commsoft.net
> 
> +---
> | 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
+---