On Sat, 5 Oct 2019 16:37:43 +0000, Jesse 1 Robinson wrote:

>Depending on the size or your shop and the number of TSO users, you could 
>cause a FUBAR by renaming any shared ISPF data set. Those get allocated not 
>only through logon PROCs but also through any number of CLIST/REXX over which 
>you may have zero control or even knowledge. However you do this, aim to end 
>up with the original names so that users are not stranded.
>
>If you have a handful of users you can't cancel, use FORCE U=xxxx. It's messy, 
>but the pain will (most likely) be short lived. 
>
In such a situation I've sometimes resorted to a batch job with
    DD  DISP=(OLD,DELETE),...

Sooner or later, I get control of the DSN.  Probably sooner than later
the operator calls me, tells me I'm a troublemaker, and asks my permission
to cancel the job.

Often, I've relied on aliases.  GRS seems to ignore aliases -- I can delete
the existing one and DEFINE a new one RELATED to the new version.
Caveats?

o People tell me that's not what aliases are supposed to be for.

o There's a minuscule window where the alias doesn't exist.  Is it
  possible to ALTER the RELATED DSN with no such window's occurring?

o I had some contention with one user who wanted to create his
  own alias because IDCAMS wont allow an alias of an alias.  Dumb rule.

o The alias and the RELATED must belong to the same catalog.
  Dumb rule.

o That doesn't apply to symbolic aliases.  But the SYMBOLICRELATED
  DSN must contain at least one substitutable symbol.  Dumb Rule.

>-----Original Message-----
>From: Lizette Koehler
>Sent: Saturday, October 5, 2019 8:59 AM
>
>So using your normal change control process, the following steps can be taken
>
>   1)  Issue  D GRS,RES=(*,data-set-name-here)
>       See who has it allocated
>
>   2)  Set TSO USERMAX to 0.   F TSU,USERMAX=0  
>       Make sure you are logged on before you issue this command
>
>   3)  Start to cancel users that a e enqueued on the dataset
>
>   4)  Once enqueues are gone, rename the file
>    ...
-- gil

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to