RE: RISC to CISC -- MIDRANGE-L

Art, 

If it saved to V3R2M0 without a hitch, you should have no problem restoring
it to a V3R2 machine.  We develop on V4R3 and ship out to V3R2 and up
without problems.  

You don't have to recompile.

Bradley V. Stone
Taylor Corporation - OASIS Programmer/Analyst   
bvstone@taylorcorp.com


> -----Original Message-----
> From: Art Baker [SMTP:Art_Baker@baan.com]
> Sent: Friday, May 14, 1999 7:23 PM
> To:   'MIDRANGE-L@midrange.com'
> Subject:      RE: RISC to CISC
> 
> Brad,
>       I did save the library specifying V3R2M0, that worked OK. A
> co-worker here told me not to ship the tape because the client is on CISC
> format(V3R2) and it won't work since we have a RISC format. 
>       From the response today on midrange it looks like I need to
> recompile, on a new library, and then cut a tape. There is no data
> involved.
> It's one Cobol program with four PF files for forms definitions, bunch of
> 1099 tax stuff that ties to a accounting system.
>       The orginal program was in CISC format, our machine converted it to
> RISC. Wish I had the orginal tape but it can't find it. It was lost before
> I
> ever worked here. 
> Art        
> 
> -----Original Message-----
> From: Stone, Brad V (TC) [mailto:bvstone@taylorcorp.com]
> Sent: Friday, May 14, 1999 4:15 PM
> To: 'MIDRANGE-L@midrange.com'
> Subject: RE: RISC to CISC
> 
> 
> Art,
> 
> If they can't be saved to V3R2M0, the system will tell you.  If you save
> to
> release V3R2M0 and everything goes well, it will be no problem.
> 
> If you do get an error telling you you can't save to a previous release,
> recompile specifying V3R2M0.  If it won't even compile, it's because
> you're
> using something that doesn't work in V3R2M0 (such as some %bifs or
> something) and you may have to change the source and recompile again.
> 
> So, just try saving it first.  Start there.  
> 
> Bradley V. Stone
> Taylor Corporation - OASIS Programmer/Analyst 
> bvstone@taylorcorp.com
> 
> 
> > -----Original Message-----
> > From:       Art Baker [SMTP:Art_Baker@baan.com]
> > Sent:       Friday, May 14, 1999 4:13 PM
> > To: 'MIDRANGE-L@midrange.com'
> > Subject:    RE: RISC to CISC
> > 
> > Al,
> >     So what your saying is I save this library to TGTRLS V3R2 and when
> > the client restores it on their machine, it will covert the objects to
> > CISC
> > format? 
> > The question now is: Do I need to recompile these objects before the
> > SAVLIB
> > or just do a SAVLIB/TGTRLS V3R2 and the CISC machine will recompile
> > automatically?
> > Art  
> > 
> > -----Original Message-----
> > From: Al Barsa, Jr. [mailto:barsa2@ibm.net]
> > Sent: Friday, May 14, 1999 2:29 PM
> > To: MIDRANGE-L@midrange.com
> > Subject: Re: RISC to CISC
> > 
> > 
> > At 11:58 AM 5/14/99 -0400, you wrote:
> > >Hello,
> > >   I have been off the midrange list for the past few months, too many
> > >projects. But I'm back!
> > >   Have a question on saving libraries. My machine is running RISC V3R7
> > >and a client of mind wants a copy of a library but, the client is
> running
> > >V3R2 CISC. There is the TGTRLS (target release) option on the SAV menu
> > for
> > >typing in what version you want the library saved at but can a RISC
> > library
> > >be converted back to CISC format? I was thinking there was something in
> > the
> > >midrange archive but have not found anything yet for converting
> libraries
> > >from RISC to CISC format.
> > 
> > Any object can be restored back to CISC from V3R7, as long as it was
> both
> > compiled and saved specifying TGTRLS(V3R2M0 or lower).  The objects will
> > reencapsulate on the restore to CISC, so keep in mind that this can be a
> > slow, piggish process.
> > 
> > Al
> > 
> > 
> > 
> > 
> > +--------------------------------------------------+
> > | Please do not send private mail to this address. |
> > | Private mail should go to barsa@ibm.net.         |
> > +--------------------------------------------------+
> > 
> > Al Barsa, Jr. - Account for Midrange-L
> > Barsa Consulting, LLC.      
> > 400 > 390
> > 
> > Phone:      914-251-1234
> > Fax:        914-251-9406
> > http://www.barsaconsulting.com
> > http://www.taatool.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
> > +---
> > +---
> > | 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
> +---
> +---
> | 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
+---