Well, thanks to the efforts of the IBM support and development
team, we were able to solve our problem.

Due to our somewhat complicated setup, the full description is
probably not of interest to those on the list. The ultimate
problem, however, was related to one that has been discussed
before on this list, that is the filespace name of directories
mounted within other filespaces.

Basically an additional filespace had been defined for this node
inadvertently. Because the files which we were attempting to
restore pattern matched this new filespace, ADSM was looking in
that table, rather than the root ('/') filespace table. By
forcing ADSM to reference the root filespace name, using
"{/}/POE/022/034/2d_cgi/OUTPUT_turbs/*" as the source file
specification we were able to restore the files in question.

 -- Tom

Thomas A. La Porte
DreamWorks Animation
tlaporte AT dreamworks DOT com

On Tue, 14 Jul 1998, Bill Colwell wrote:

>I saw a similar problem running a 3.1.0.4 fixtext client on solaris with a
>3.1.0.3 mvs server.  There were only 2 files in the directory.  Doing a 'q
>backup <path>/*' showed both files, but then a 'restore <path>/*' gave
>ANS1092E. We were able to do the restore by specifying enough of the file to
>resolve the wildcarding down to one file, i.e. /a* and /b* would restore the
>files where /* would not. Also specifying the full filename worked too.
>
>Since we didn't need to be on the fixtest 3104 client we reinstalled the
>3103 client and the problem disappeared.  This was all documented and
>reported to IBM. Obviously there is a serious bug somewhere!
>
>You could get the restore done by taking your SELECT output and generating a
>series of 'dsmc res' commands which specify a complete path and file name.
>The sql interface is a terrific addition to the administrators bag of
>tricks!
>
>--
>-----------------------------------------------------------
>Bill Colwell
>C. S. Draper Lab
>Cambridge, Ma.
>bcolwell AT draper DOT com
>-----------------------------------------------------------
>