Gavin, you aren't doing anything wrong.  Check out this apar and
upgrade to the 2.1.0.8 client or a version 3 client.  I thing the file
you are trying to restore is indeed length=0 and can't be restored.
It was sent incorrectly due to this bug.  I have had restores fail like
this too.

--
--------------------------
--------------------------
Bill Colwell
Bill Colwell
C. S. Draper Lab
Cambridge, Ma.
bcolwell AT draper DOT com
--------------------------
  APAR Identifier ...... IC16603       Last Changed..97/03/28
  APAR Identifier ...... IC16603       Last Changed..97/03/28
  ADSM SUNOS CLIENT LEVEL 6 INCORRECTLY BACKS UP SOME FILES
  DIRECLTY TO TAPE WHEN MAX FILE SIZE IS DEFINED

  Symptom ...... IN INCORROUT         Status ........... CLOSED  OEM
  Severity ................... 1      Date Closed ......... 97/03/28
  Component .......... 565511902      Duplicate of ........
  Reported Release ......... AEJ      Fixed Release ............
  Component Name ADSM CLIENTS V2      Special Notice
  Current Target Date ..97/06/24      Flags
  SCP ................... UNIX
  Platform ............ UNIX

  Status Detail: Not Available

  PE PTF List:

  PTF List:
  Release AE1   : PTF not available yet
  Release AEJ   : PTF not available yet


  Parent APAR:
  Child APAR list:


  ERROR DESCRIPTION:
  When running the ADSM SunOS level 6 client on SunOS 4.1.3 and
  backups are being written to a disk pool with a nextpool defined
  and a max filesize set to a value other than nolimit, some of
  the files may be backed up directly to the nextpool. In the
  reporting customers case this was a tape pool. A subsequent
  restore of these files when some were in the higher level disk
  pool and some in the next level tape pool failed on the server
  with the following message:
   anr9999d smtrans.c(758): Invalid header size for Object Header.
  We have been able to duplicate this problem in house.


  LOCAL FIX:
  Do not use a value for max filesize in the higher level storage
  pool. Use nolimit.


  PROBLEM SUMMARY:
  ****************************************************************
  * USERS AFFECTED: SunOS 4 ADSM client only                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Files can be backed up to tape or not   *
  *                      backed up at all, when they should be   *
  *                      backed up to disk, when the Maximum     *
  *                      Filesize option has been changed from   *
  *                      the default of Nolimit to a value.      *
  ****************************************************************


  PROBLEM CONCLUSION:
  There is a bug in the SunSoft ANSI C Compiler 1.0, that caused
  the compiled ADSM client code to send random values for the
  estimated file size to the ADSM server when backing up a file.
  If the random value was above the maximum file size set for the
  first storage pool on the server (usually disk), the server
  chose the next storage pool (usually tape) to backup the data.
  If the random value was 0, the file would not be backed up.
  The ADSM code has been rewritten to avoid the compiler bug,
  and the correct estimated file size is now sent to the
  ADSM server.

  Please note this problem did not occur on the Solaris clients,
  only on the SunOS 4 client, and only when the Maximum Filesize
  option was changed from the default of Nolimit to a numeric
  value.


In <99Jun9.123407est.40359 AT border.alcanet.com DOT au>, on 06/09/99
   at 12:50 PM, Gavin Ring <Gavin.Ring AT ALCATEL.COM DOT AU> said:

>Hello ADSMers'

>What am I doing wrong......the database says the file is 12064 bytes but the
>restore indicates that nothing was transferred.

>Regards

>Gavin

>atcsun2 ~ > dsmc q b /home/a8610/amistas.lama/projects/SAS5/ORMIX_SAS5/GDF/
>ADSTAR Distributed Storage Manager
>Command Line Backup Client Interface - Version 2, Release 1, Level 0.6
>(C) Copyright IBM Corporation, 1990, 1996, All Rights Reserved.

>             Size      Backup Date       Mgmt Class A/I File
>             ----      -----------       ---------- --- ----
>           12,064  06/01/1999 19:21:12   DEFAULT     A  /home/a8610/amistas.lam
>a/projects/SAS5/ORMIX_SAS5/GDF/CAE_SAS5_ORMIX


>atcsun2 ~ > dsmc restore /home/a8610/amistas.lama/projects/SAS5/ORMIX_SAS5/GDF/
>CAE_SAS5_ORMIX
>ADSTAR Distributed Storage Manager
>Command Line Backup Client Interface - Version 2, Release 1, Level 0.6
>(C) Copyright IBM Corporation, 1990, 1996, All Rights Reserved.


>Total number of objects restored:         1
>Total number of bytes transferred:        0 <====================
>Total failures:                           0
>Elapsed processing time:            0:00:00


>Environment:

>Client:
>atcsun2 ~ > uname -a
>SunOS atcsun2 4.1.4 1 sun4m

>Server:
>ADSTAR Distributed Storage Manager for MVS
>Version 3, Release 1, Level 2.15