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

["O'Connor, Peter H." <PHOC@xxxxxxxxxxxxxx>]

Bradley asks:

>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?
<
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&7

When you compile to 3.2 and execute on RISC, it will execute.  When you
restore back onto CISC system, during the restore the program will be
converted back to a non-RISC program.  It works fine, I do it all the time.

Peter H. O'Connor
PAE Inc.
7 Riverway Rd.
Salem, MA 01970-5343
978-744-8612(T)
978-745-7945(F)
e-mail 102736.3535@compuserve.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
+---