Robert,

I discovered the bug while using the export/import to move nodes between
storage pools on the same ADSM-server. The 3.1.2.40 fixed the bug.

Ciao

Mauro, STM

> This was a bug in the 3.1.2.20 code and we are told it has been
corrected in
> the 3.1.2.40 code
> If anybody is still experiencing these import errors on the new
3.1.2.40
> code please reply...
> thanks
> Robert Burton
> Open Systems Storage Analyst
> Royal Bank of Canada
> (416) 348-3849
> Robert.Burton AT RoyalBank DOT com
>
>
>
> -----Original Message-----
> From: Moir,Betsy [mailto:betsy.moir AT ABBOTT DOT COM]
> Sent: 1999, September, 14 2:11 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Restoring Imported Node Data
>
>
> Not encouraging news since I have about 200 clients I want to move from
one
> server to another.  I guess I'll have to look further into the "virtual
> volumes" and "filetype server" options for moving this information.
Thanks
> for the response, though.
>
>
>
>
> ADSM-L AT VM.MARIST DOT EDU on 09/14/99 11:23:59 AM
> Please respond to ADSM-L AT VM.MARIST DOT EDU @ INTERNET
> To: ADSM-L AT VM.MARIST DOT EDU @ INTERNET
> cc:
> Subject: Re: Restoring Imported Node Data
>
> We had users report this same problem against our VMS client (ABC).
> While investigating, one of our customers sent along this extract from
one
> of IBM's problem managment systems.  Here is that info:
>
>      PQ28166 ADSM CLIENT RESTORE/RETRIEVE FAILS W/ ANS4032E ON DATA
THAT
>      WAS  EXPORTED FROM ONE V3 SERVER & IMPORTED TO SAME OR ANOTHER
SERVER
>
>       ADSM development has uncovered a problem with the restore and/or
>       retrieve of data that has been exported from one ADSM V3 server
and
>       imported on the same server or on another server. The actual
>       export/import process works just fine. The problem does not
appear
>       until the client attemptsto restore or retrieve this data.  One
>       reported symptom on theclient is an ANS4032E Error processing
'file':
>       file is not compressed. Another symptom is that the client will
>       reportreturn code (RC) 150, which means "unknown file/data type
>       during restore or retrieve".
>
> -----Original Message-----
> From: Moir,Betsy <betsy.moir AT ABBOTT DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU <ADSM-L AT VM.MARIST DOT EDU>
> Date: Tuesday, September 14, 1999 9:13 AM
> Subject: Restoring Imported Node Data
>
>
> >I'm trying to export a node, including their file data from one server
and
> >import that node and data to another server.  My  client is a
version3.1.6
> NT
> >client and my server is a version3 VM mainframe.  The command I'm
using is:
> >EXPORT NODE nodename DEV=ETAPES FILED=ALL.
> >
> >The export works fine.  No errors.  Then I do an import on the second
> >server.  The command I'm using is IMPORT NODE nodename DEV=ETAPES
FILED=ALL
> >VOL=volser-from-export-log.  The import works fine.  No errors.
> >
> >When I login as the client and try to restore any of these imported
files
> to
> >their original or to a different location, however, I get an error
that
> >reads, "File thought to be compressed but was not."  Not only does it
not
> >restore the files, but if I was restoring to the original location,
it's
> >erasing them from my hard drive!
> >
> >Anybody seen this?  Am I overlooking something?
> >
> >Any help is always appreciated.  Thanks.
> >