I can't recall how this works under REXX, so...do you have WTPMSG turned
on in your TSO/E profile?
Also, while this could be a destructive test (which will make it hard to
answer the original question), what happens if you use the same delete
command in IDCAMS in batch? My thought is that with MSGLEVEL=(1,1) you
might get more information from either IDCAMS messages or system
messages than you get from TSO/E foreground. And, is this the only data
set for which this happens?
Skip Robinson wrote:
Cleaning up after a ServerPac install. There are some 'operational' data
sets that I don't want to keep around. One of those is 'SYS1.XCF.CDS03',
which lives on the 'CAT' volume and cataloged in the ServerPac catalog
'MVSR21.ICF.MASTER' on the same volume. I wrote a simple Rexx to LISTC the
data set and, if it exists, delete it. LISTC shows the data set, DELETE
fails as shown.
I also LISTC and delete the associated alias 'OSR21.SYS1.XCF.CDS03' in the
same catalog. That command worked fine. What am I missing for the data set
delete? I run this Rexx under foreground TSO.
9 *-* "LISTC ENT('"dsn"') CAT('MVSR21.ICF.MASTER')"
>>> "LISTC ENT('SYS1.XCF.CDS03') CAT('MVSR21.ICF.MASTER')"
NONVSAM ------- SYS1.XCF.CDS03
13 *-* "DEL '"dsn"' CAT('MVSR21.ICF.MASTER')"
>>> "DEL 'SYS1.XCF.CDS03' CAT('MVSR21.ICF.MASTER')"
IKJ56228I DATA SET SYS1.XCF.CDS03 NOT IN CATALOG OR CATALOG CAN NOT BE
ACCESSED
IDC0551I ** ENTRY SYS1.XCF.CDS03 NOT DELETED
IDC0014I LASTCC=8
+++ RC(8) +++
<snip>
--
John Eells
z/OS Technical Marketing
IBM Poughkeepsie
[email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
