× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: ##EMailNumber 01-WNY-2138181 FTP & Save Files: RISC V4R2M0 to CISC V3R2M0
  • From: stefan.tageson@xxxxxxxxxxxxx
  • Date: Thu, 13 Aug 1998 18:20:39 +0200

According to the manual "AS/400 Road Map for Changing to PowerPC Technology
Version 4 "
 You have to apply some ptf:s before trying to restore objects from the
save file:

APPENDIX1.4.6 Program Temporary Fixes for Network Interoperability

To exchange objects between PowerPC AS systems in a network (any supported
release) and IMPI systems running earlier releases,
(V2R3M0, V3R0M5, V3R1M0, or V3R2M0), you must apply PTFs to the earlier
systems. You cannot restore objects created on a PowerPC AS
system to earlier systems in the network until you apply the PTFs to the
earlier systems. To avoid this delay, order the necessary PTFs now
and apply them to the systems that will remain at earlier release levels.

Use Table D-4 to determine which PTFs to order for the systems that remain
at earlier release levels. You will receive several corequisite PTFs
when you order any of the PTFs shown. You need these for the following:


   Restoration of save files


   Database objects


   Journal receivers


   Program objects


   Objects that are associated with byte stream files:

    -   Document objects (*DOC)

    -   Stream File objects (*STMF)

    -   Symbolic Link objects (*SYMLNK)




+------------------------------------------------------------------------+

¦ Table  D-4. PTFs for Earlier Systems in a Network to Enable Exchanging ¦
¦             Data                                                       ¦
+------------------------------------------------------------------------¦
¦           Order this PTF           ¦  For System Remaining at Release  ¦
+------------------------------------+-----------------------------------¦
¦               SF26145              ¦               V3R0M5              ¦
+------------------------------------+-----------------------------------¦
¦               SF26146              ¦               V3R1M0              ¦
+------------------------------------+-----------------------------------¦
¦               SF33467              ¦               V3R2M0              ¦
+------------------------------------------------------------------------+

// Good Luck!

// Stefan Tageson
+>----------------------------------------------------------------------<+
  tel:         +46 40 693 3500
  fax:         +46 40 693 3600
  mobile: +46 708 51 3543
  e-mail       stefan.tageson@notes.sema.se
+>---------------------------------------------------------------------<+





Patrick Townsend <townsend@patownsend.com> on 98-08-13 03:38:44

Please respond to MIDRANGE-L@midrange.com
                                                              
                                                              
                                                              
 To:      MIDRANGE-L@midrange.com                             
                                                              
 cc:      fkix@militarycars.com(bcc: Stefan Tageson/MMX/Sema  
          Group/SE)                                           
                                                              
                                                              
                                                              
 Subject: Re: ##EMailNumber 01-WNY-2138181 FTP & Save Files:  
          RISC V4R2M0 to            CISC V3R2M0               
                                                              





Hi Jorge!

I'm doing exactly what you describe. But you have to be very careful
about the release level of the objects. On the RISC machine you have to
create programs for the target release of V3R2 AND save them for that
release. There can be other objects that won't save for the earlier
release. Have you tried to determine which objects will not restore? You
should be able to see this in the job log. There is usually a pretty
good description of the reason it won't restore.

Patrick

jmoreno@militarycars.com wrote:
>
> Hello Everyone,
>
> How can I use the FTP support between the RISC V4R2M0 and the CISC V3R2M0
to
> Send SAVE FILES and Successfully Do Save / Restores of Large Amounts of
Data and Objects.
>
> (At the present time our Tape drives are suffering of Very Old Age and/or
Technical Problems)
>
>
---------------------------------------------------------------------------
----------------------------------------------------------
> ---
>                                                   T H I S   I S   M Y  P
R O B L E M
>
---------------------------------------------------------------------------
----------------------------------------------------------
> --
>
> Save Objects in the RISC V4R2M0 Machine to a Save File with target
Release V3R2M0,
> FTP the SAVE File to the CISC V3R2M0  nd Restore Those Objects from the
Save File ?
>
>  o       I have used  NAMFMT "0" and "1" in all my tests,
>  o      Used Type  "BIN"
>  o      Created the  Save File in the Target Library PRIOR to the PUT
operation
>  o      Successfully  created  and/or  loaded the save file in the Traget
CISC V3R2M0
>            (Depending On the NAMEFMT "0" / "1")
>  o      I WAS NOT ABLE  to execute the RSTOBJ command in the Target CISC
V3R2M0 AS/400
>           BECAUSE theCONTENTS of the Save File Reflect a Higher RELEASE
.... <How is this possible ?>
>           < I had saved the objects with Target Release V3R2M0 >... <
What Gives ?>
> o       Tried sending a Physical File WITH the Save File Info and
Rebuilding The Save File In The
>            Target V3R2M0 with the same results .... I need your Help
AS/400 Techies .....
>
>  I will apreciate your answers ....
>
> Regards
Jorge Moreno / military car Sales / Woodbury, NY
>
> +---
> | 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
> +---

--

Patrick Townsend                       mailto:townsend@patownsend.com
Patrick Townsend & Associates, Inc.    http://www.patownsend.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 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.