Jeff,

     Thanks, I tried this with the following result:

     ANR2475E FORMAT DB: File  could not be opened.

     This is my PARM statement:

     //   PARM='/FORMAT 1 SYS3.ADSMP.RCVRYLG1 4 FILE:"SYS3.ADSMP.FORMATDB"'

     I checked and the dataset name is correctly spelled. Now what the APAR does
     NOT talk about are the attributes for 'the file'. What recfm, lrecl, etc.
     Also what format for the database names within it, i.e., should they be
     strung out: SYS3.ADSMP.DB01 SYS3.ADSMP.DB02 SYS3.ADSMP.DB03 SYS3.ADSMP.DB04

                            OR
     one name per line:
     SYS3.ADSMP.DB01
     SYS3.ADSMP.DB02
     SYS3.ADSMP.DB03
     SYS3.ADSMP.DB04
                            OR ????

     Anybody have any ideas?  Is IBM listening: It would help if the doc had a
     bit more detail.

     Thanks,

     Frank Rehor
     The Clorox Services Company

______________________________ Reply Separator _________________________________
Subject: Re: ADSM/MVS Server Recovery
Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> at Internet
Date:    10/27/98 4:14 PM


Frank,

Here is information contained in APAR PN78840 which basically tells you how
 to put your database and recovery log
names into file rather than coding them on the parm where your limited to
100 chars.  I assume this still works for version
3 servers.  Also, substitute /FORMAT for /INSTALL coded on the parm in the
sample JCL below since that changed with
V3.

Hope this helps,

Jeff Connor
Niagara Mohawk Power Corp



 ****************************************************************
 * PROBLEM DESCRIPTION:                                         *
 Allow reading log and db volumes from a file during install.
 ****************************************************************
 * RECOMMENDATION:                                              *
 apply fixing ptf when available
 ****************************************************************
 Fully qualified data set names may be long.  The PARM field
 is limited to 100 characters.  Customers would like to
 provide files containing the candidate recovery log and data-
 base volume names when installing the server.


 PROBLEM CONCLUSION:
 The new syntax for installing an ADSM MVS server is:


 where:
   nLog           the number of log volume names that follow, or
                  are in logFilename

   log1 ... logn  the names of candidate log volumes.  They
                  must be VSAM linear data sets that have been
                  formatted using the dsmfmt utility


     logFilename    the file that contains a list of candidate

                    log volumes



     nDb            the number of database volume names that

                    follow, or are in dbFilename



     db1 ... dbn    the names of candidate database volumes



     dbFilename     the file that contains a list of candidate

                    database volumes



   Also note that from Version 2, the server does not format VSAM

   linear data sets as part of the "install" or "define" commands.

   Allocating and formatting the data sets must be done outside of

   the server.  asamplib members are provided to help.

   An example of using the FILE: option in ANRINST.ASAMPLIB follows



   //SERVER  EXEC PGM=DSMSERV,DYNAMNBR=300,

   //        PARM='/INSTALL 1 FILE:''LOG.FILE'' 1 FILE:''DB.FILE'''



   where LOG.FILE contains:

      ADSM.RCVRYLOG

  and DB.FILE contains:
     ADSM.DB1