good catch
Scott Rowe wrote:
I assume the list below was cut and pasted from ISPF 3.4, in which case I can
not imagine how the first entry could not be cataloged, how else could it have
been displayed?
Howard Rifkind [EMAIL PROTECTED] 10/7/2008 4:22 PM
Hello all,
I'm trying
To me, it sounds like this dataset is orphaned in the wrong usercat. You need
to temporary delete the alias to the correct usercat; delete the cluster with
the catalog parameter (or define the alias to the wrong usercat before the
delete); finally define the alias back to the correct usercat.
I'm sure we can help you but I suspect a phone call will be needed. Why
don't you email me directly and I can give you my direct phone number. I
promise not to push any vendor tool on you! I'm sure we can get to the
bottom of this by using LISTCAT, perhaps some VTOC lists, some prints of
your
If you use the CATALOG(xxx) parameter, you don't need to delete or
redefine the alias.
Bruce Richardson wrote:
To me, it sounds like this dataset is orphaned in the wrong usercat. You need
to temporary delete the alias to the correct usercat; delete the cluster with
the catalog parameter (or
Hi I replied yesterday on the Google group forum for IBMMAIN but saw no
posting when reading the Listserv postings today
What I have to say is if the VSAM is definitely uncataloged then the following
will work
) Run an IEHLIST LISTVTOC of the volume on which the VSAm DS resides
2) Check that
First you need to check all the components. The LISTCAT is listing the BCS.
You should list the VVDS of the volume where the DATA and INDEX
components are located. Check if the entries are there and if they point to
the right catalog. Also, using 3.4 and specifying the VOLSER, see if the
Thanks...been there done that and still NO Go
Mohd Shahrifuddin [EMAIL PROTECTED] 10/8/2008 1:07 AM
Dear Howard,
How about try to delete using VVR option. May be can help.
--
For IBM-MAIN subscribe / signoff / archive access
I may be totally off base, but what if you run a DEFINE CLUSTER to try
and get it in your catalog and then see if it will let you delete it??
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Howard Rifkind
Sent: Wednesday, October 08, 2008
On Tue, 7 Oct 2008 16:22:09 -0400, Howard Rifkind wrote:
I'm trying to delete the following datasets:
PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL *VSAM*
PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL.DATA OPSPR2
PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL.INDEX
Tom Marchant wrote:
On Tue, 7 Oct 2008 16:22:09 -0400, Howard Rifkind wrote:
I'm trying to delete the following datasets:
PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL *VSAM*
PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL.DATA OPSPR2
Let's try something :
VSAM = 'PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL'
VOL = 'OPSPR2'
Option1:
Listcat VSAM
If Catalog.VSAM = Catalog.HLQ.VSAM Then
If VOL OFFLINE Then
ONLINE VOL
Endif
Else
REPRO VSAM Mergecat to Catalog.HLQ.VSAM
Endif
DELETE VSAM
Option2:
If VOL OFFLINE
there used to be a RECATALOG option which allowed the datasets to be redefined
and then deleted -i am not sure if it is still around.
DEFINE -
CLUSTER -
(NAME(.yyy) -
INDEXED FILE(DD1) -
RECATALOG -
SPEED -
SHR(3,3) -
TRACKS(005,5) -
Howard,
The point of my last reply is this: These datasets are NOT uncataloged. You
need to get that idea out of your head. This is a VSAM cluster that is indeed
cataloged, but you seem to be having a problem locating them in your catalog
structure. Get away from any ideas of uncataloging
On Tue, 7 Oct 2008 16:22:09 -0400, Howard Rifkind wrote:
I'm trying to delete the following datasets:
PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL *VSAM*
PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL.DATA OPSPR2
PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL.INDEX
Assuming you are on a current version of ISPF, if you check the 3.4
screen there is a field/option labelled Display Catalog Name. If you
place a / there the display will show you what CATALOG the file(s)
were found.
Dennis
-Original Message-
From: IBM Mainframe Discussion List
Hello all,
I'm trying to delete the following datasets:
PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL *VSAM*
PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL.DATA OPSPR2
PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL.INDEX OPSPR2
For the first one a 'D'
Try a DELETE NOSCRATCH on each component.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Howard Rifkind
Sent: Tuesday, October 07, 2008 3:22 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Help with deleting datasets which are not cataloged or don't
This has been talked about numerous times, try the archives.
Easiest way is to recatalog the DSN and then delete it (hopefully no BCS
name issue) if you don't have one of the catalog products.
Jack Kelly
202-502-2390 (Office)
Thanks but this didn't do itJCL below...
//STEP01 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
DELETE -
PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL.INDEX -
NOSCRATCH -
DEL 'cluster name' NSCR
If that fails,
DEL 'component name' VVR FILE(DD1)
Where DD1 points to volume OPSPR2
HTH,
snip
I'm trying to delete the following datasets:
PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL *VSAM*
PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL.DATA
Could these datasets be catalogued/shared on another system? If so, and they
are unallocated and unwanted, then delete NOSCRATCH them from each system. On
the last system use the SCRATCH.
DELETE -
PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL -
CLUSTER -
Tried that also, No Go.
Jack Kelly [EMAIL PROTECTED] 10/7/2008 4:34 PM
This has been talked about numerous times, try the archives.
Easiest way is to recatalog the DSN and then delete it (hopefully no BCS
name issue) if you don't have one of the catalog products.
Jack Kelly
202-502-2390
Try again, this time use only NOSCRATCH.
And, as another poster pointed out, verify we are working in the catalog
we think we are working in.
If all that fails, let's take a look at the specific error message(s).
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL
I assume the list below was cut and pasted from ISPF 3.4, in which case I can
not imagine how the first entry could not be cataloged, how else could it have
been displayed?
Howard Rifkind [EMAIL PROTECTED] 10/7/2008 4:22 PM
Hello all,
I'm trying to delete the following datasets:
Yes it was.
Here is the listing from a LISTCAT.
CLUSTER --- PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL
DATA --- PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL.DATA
INDEX -- PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL.INDEX
NONVSAM --- SCRIPT.R40.ADCFASM
If you do a TSO DELETE 'PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL'what R
eturn Reason Codes do you get back from IDCAMS.
Might provide some clue as to what's going on.
Cheers.Jason.
Howard Rifkind [EMAIL PROTECTED]
Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU
There is an entry there but that's all.
Howard Rifkind [EMAIL PROTECTED] 10/7/2008 5:57 PM
Yes it was.
Here is the listing from a LISTCAT.
CLUSTER --- PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL
DATA --- PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL.DATA
INDEX --
Thanks but this didn't do itJCL below...
//STEP01 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
DELETE -
PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL.INDEX -
NOSCRATCH -
IDC3012I ENTRY PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL NOT FOUND+
IDC0551I ** ENTRY PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL NOT DELETED
IDC0014I LASTCC=8
IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEG-42
***
Perhaps it is in the wrong catalog?
Howard Rifkind wrote:
IDC3012I ENTRY PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL NOT FOUND+
IDC0551I ** ENTRY PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL NOT DELETED
IDC0014I LASTCC=8
IDC3009I ** VSAM CATALOG RETURN CODE
On Tue, 7 Oct 2008 17:57:47 -0400, Howard Rifkind wrote:
Here is the listing from a LISTCAT.
CLUSTER --- PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL
DATA --- PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL.DATA
INDEX -- PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL.INDEX
...
What you've got here is a VSAM Cluster. List the catalogs to find the
catalog that contains it, then do a
DELETE PDB.SYSPROG.TMON.LMCICS.V22.VTCWCNTL CLUSTER -
CAT(catalog name)
It sounds like you may be mis-cataloged. Is the HLQ valid in your
catalog? Is it an alias pointing to
Dear Howard,
How about try to delete using VVR option. May be can help.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives
In a message dated 10/8/2008 12:07:25 A.M. Central Daylight Time,
[EMAIL PROTECTED] writes:
How about try to delete using VVR option. May be can help.
If you know which pack it's on can do DIAGNOSE and it should tell you the
problems.
Sounds like to me the UCAT is missing or
34 matches
Mail list logo
