What I also did was to disable the IXVTOC run the zap and re-enable it.
Ed
On Jul 22, 2015, at 3:09 AM, retired mainframer wrote:
Unfortunately, if the VTOC is indexed this causes problems.
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-
[email protected]] On
Behalf Of Ed Gould
Sent: Tuesday, July 21, 2015 9:10 PM
To: [email protected]
Subject: Re: Deleting data sets in use
The *OLD* way is to get the address of the format4.dscb of the data
set (from iehlist)
Use amaspzap with the syslib of format4.dscb (and dcb=keylen=44)
the zap statement with something like :
... I am forgetting what the first statement is but I am thinking
cchhr 8 hex address you got from doing the iehlist
but the next is ver 00 e2
* verify the first charachter is s
rep 00 c1
* replace the s with an a
Then iehprogm to scratch the dsn ays2.tso.clist,vol=sysda=volser
Ed
On Jul 21, 2015, at 9:02 AM, Fred Kaptein wrote:
Any suggestions to get around this problem would be appreciated.
--------------------------------------------------------------------
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-
MAIN
---------------------------------------------------------------------
-
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-
MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
