Setopt will work with no problems with disp=shr
TSM stores this information in the database.
So yes if you wish to keep the option file in line with the database you do
need to halt the
server at some time, because although disp=shr allows you read the file you
cannot update it
while TSM is active.
However in the OS390 world if you are making global changes as in the TSM
options file, they
should go through a change control process, which will allow you to record
that you are making
the original change through setopt, and that TSM will be downed at a
convenient time to update the server option file.
I have not found this a problem, maybe I do not make that many changes.
John
Gerhard Wolkerstorfer <[EMAIL PROTECTED]> on 03/21/2001
02:27:20 PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (bcc: John Naylor/HAV/SSE)
Subject: Re: Antwort: jcl to run admin client in batch
I am very confused about that.....
We are accessing the OPT-File in the Serverprogram (DSMSERV) with DISP=SHR
I did the following:
I changed e.g the EXPQUIET to YES through SETOPT.
But in the OPT File EXPQUIET is still NO.
After HALTing and restarting the Server,
the EXPQUIET is still NO in the OPT File and
QU OPT shows that EXPQUIET still YES as SET before.
Now the big question is =>
Where is TSM storing this information ??
And another thing:
The History of the Optionsfile shows, that nobody has changed this file since
the systemprogramer added some new features (SELFTUNExxxx)
TSM himself has never updated this file.
-- Gerhard --
[EMAIL PROTECTED] (Alan Davenport) am 21.03.2001 14:44:04
Bitte antworten an [EMAIL PROTECTED]
An: [EMAIL PROTECTED]
Kopie: (Blindkopie: Gerhard Wolkerstorfer/DEBIS/EDVG/AT)
Thema: Re: Antwort: jcl to run admin client in batch
Interesting. I'd like to do this also. I have one question however. If I
were to change the options file to DISP=SHR what would be the result if
someone decided to use SETOPT? Would this lock up the server?
Al
[EMAIL PROTECTED] wrote:
>
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Date: Wed, 21 Mar 2001 09:32:52 +0000
> Subject: Re: Antwort: jcl to run admin client in batch
>
> Alan,
>
> That is exactlly why I changed the server options file back to a disp=shr.
> You might want to review how often you actually made use of the disp=mod
>
> John
>
> Alan Davenport <[EMAIL PROTECTED]> on 03/20/2001 05:41:28 PM
>
> Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>
> To: [EMAIL PROTECTED]
> cc: (bcc: John Naylor/HAV/SSE)
> Subject: Re: Antwort: jcl to run admin client in batch
>
> 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
>
> [EMAIL PROTECTED] wrote:
> >
> > From: [EMAIL PROTECTED]
> > To: [EMAIL PROTECTED]
> > 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:[EMAIL PROTECTED]]On Behalf Of
> > Alan Davenport
> > Sent: Tuesday, March 20, 2001 10:39 AM
> > To: [EMAIL PROTECTED]
> > 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
> > [EMAIL PROTECTED]
> >
> > [EMAIL PROTECTED] wrote:
> > >
> > > From: [EMAIL PROTECTED]
> > > To: [EMAIL PROTECTED]
> > > 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
> > >
> > > [EMAIL PROTECTED] (Lee. Gary D.) am 20.03.2001 15:05:44
> > >
> > > Bitte antworten an [EMAIL PROTECTED]
> > >
> > > An: [EMAIL PROTECTED]
> > > 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
>
> **********************************************************************
> The information in this E-Mail is confidential and may be legally
> privileged. It may not represent the views of Scottish and Southern
> Energy plc.
> It is intended solely for the addressees. Access to this E-Mail by
> anyone else is unauthorised. If you are not the intended recipient,
> any disclosure, copying, distribution or any action taken or omitted
> to be taken in reliance on it, is prohibited and may be unlawful.
> Any unauthorised recipient should advise the sender immediately of
> the error in transmission.
>
> Scottish Hydro-Electric and Southern Electric are trading names of
> Scottish and Southern Energy Group.
> **********************************************************************
**********************************************************************
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.
Scottish Hydro-Electric and Southern Electric are trading names of
Scottish and Southern Energy Group.
**********************************************************************
