|
Thanks, Al. We use RSF from bugbusters for object transfer, so in a sense it is using the save file technique you describe. 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: Al Barsa, Jr. [SMTP:barsa2@ibm.net] > Sent: Wednesday, July 01, 1998 9:37 AM > To: MIDRANGE-L@midrange.com > Subject: RE: Using RISC as development, sending to CISC. Any > problems forseen? > > At 08:10 AM 7/1/98 -0000, you wrote: > >Brad, > > > >If you compile with Target Release V3R1 or V3R2 on your Risc box, you > > >can then save with Target Release V3R1 or R2, restore the pgms and > >stuff with no problem. > > > >Be aware that if you do your SAVOBJ/LIB with target V3R1 and then > >restore to a risc box, it will take a LONG time. Longer than if the > >object was compiled on a CISC box and then restored to RISC. I do > not > >know exactly what is going on in this, but if you are going to > restore > >to a RISC box, save with a target release of V3R6 or better. > > The reason that the restore of a RISC capable program to CISC takes a > long > time is that the program has to reencapsulate when it is restored to > CISC, > and that happen on the restore. A few points: > > - I don't see any reason why it should take longer to restore if > the > program had ever been compiled on CISC. > > - To minimize tape drive delay, save the programs to a save file, > restore > the save file (fast), and then restore the programs from the save file > in > batch in the background at low priority. This will especially save > time > on a server system. > > Al > > > > Al Barsa, Jr. - Account for Midrange-L > Barsa Consulting, LLC. > 400 > 390 > > Phone: 914-251-9400 > Fax: 914-251-9406 > > > > > > Private mail should be sent to barsa@ibm.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 +---
As an Amazon Associate we earn from qualifying purchases.
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.