Interesting. The startup JCL for the server on OS/390 here has DISP=MOD
for the options file and as such I have to down *SM to run the utilities
to format new log,db volumes. I guess I still have "foot in mouth"
disease. I did not read carefully enough to see that you were talking
about the client. My appologies.

 Al

wboyer AT ptd DOT net wrote:
>
> From: wboyer AT PTD DOT NET
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: Tue, 20 Mar 2001 12:06:42 -0500
> Subject: Re: Antwort: jcl to run admin client in batch
>
> Works for me. You are thinking of the *SM server opening the options file
> DISP=MOD, but that's usually if you do any kind of SETOPT command to make
> the *SM server add that option to his DSMSERV options.
>
> As far as I'm aware, the client doesn't open the options file for anything
> other that read. I've even coded the DSCOPT file as '//DSCOPT DD *' to
> specify my own options for testing.
>
> Bill Boyer
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Alan Davenport
> Sent: Tuesday, March 20, 2001 10:39 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Antwort: jcl to run admin client in batch
>
> This will work not work for the following reason: Be aware that *SM
> opens the options file with DISP=MOD. If you submit this JCL in batch it
> will wait on the options file dataset. *SM has a lock on it. You would
> have to shut down *SM in order for this JCL to run but in that case the
> query will fail because *SM is not up! Catch 22. ):
>
>  Alan Davenport
>  Selective Insurance
>  alan.davenport AT selective DOT com
>
> gerhard.wolkerstorfer AT t-systems DOT at wrote:
> >
> > From: Gerhard.Wolkerstorfer AT T-SYSTEMS DOT AT
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Date: Tue, 20 Mar 2001 15:46:56 +0100
> > Subject: Antwort: jcl to run admin client in batch
> >
> > Gary,
> > try this =>
> > //DSMADMC  EXEC PGM=DSMADMC,
> > // PARM=('/-ID=&USER -PASSWORD=&PASSWORD -NOCONFIRM
> > //             -ERRORLOGNAME=''&ERRORLOG''')
> > //SYSPRINT DD SYSOUT=*
> > //SYSOUT   DD SYSOUT=*
> > //DSCLANG  DD DSN=xxx,DISP=SHR
> > //DSCOPT   DD DSN=yyy,DISP=SHR
> > //SYSIN    DD *
> > your query
> > QUIT
> > /*
> > //
> >
> > where
> > &USER is your TSM Admin
> > &PASSWORD is your Password
> > &ERRORLOG is the TSM Errorlog (Seq. Dataset) - I am not sure, if you need
> this !
> > xxx is your Language-Dataset (We have SYS1.DSM.SANSMSG(ANSMENU))
> > yyy is your Optionfile (We have DSM.ANSADSM.OPTIONS)
> > SYSPRINT is the Output
> > SYSIN is your Query, Select or whatever....
> >
> > You will need a Steplib if DSMADMC is not in a specific Systemlibrary
> >
> > Greetings
> >
> > Gerhard Wolkerstorfer
> >
> > GLEE AT BSU DOT EDU (Lee. Gary D.) am 20.03.2001 15:05:44
> >
> > Bitte antworten an ADSM-L AT VM.MARIST DOT EDU
> >
> > An:   ADSM-L AT VM.MARIST DOT EDU
> > Kopie:     (Blindkopie: Gerhard Wolkerstorfer/DEBIS/EDVG/AT)
> > Thema:    jcl to run admin client in batch
> >
> > tsm v3.7,
> > os/390 v2.8
> >
> > I am trying to execute the admin client in a batch job to run various
> > scripts for reporting and creation of a pull list and return list to/from
> > our tape vaults.
> >
> > I have loked through the admin guide, admin reference and quick start but
> no
> > joy.  Anyone out there got a piece of jcl for accomplishing this?
> >
> > TIA.
> >
> > Gary Lee
> > Senior Operating Systems Analyst
> > Ball State University
> > phone 765-285-1310