, PINION, RICHARD W.
wrote:
>You can always ZAP the VVR in the VVDS :)
>
>-iriginal Message-
>From: IBM Mainframe Discussion List On Behalf Of
>Steve Horein
>Sent: Thursday, December 23, 2021 9:08 AM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: Zfs recatalog
: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf Of
> Steve Horein
>
> Sent: Thursday, December 23, 2021 9:08 AM
>
> To: IBM-MAIN@LISTSERV.UA.EDU
>
> Subject: Re: Zfs recatalog error
>
> [External Email. Exercise caution when clicking links or opening
You can always ZAP the VVR in the VVDS :)
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Steve Horein
Sent: Thursday, December 23, 2021 9:08 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Zfs recatalog error
[External Email. Exercise caution when clicking links
*Explanation:* The catalog associated with this data set does not match
the catalog name found in the VVR.
*Programmer Response:* You can only recatalog pagespace, swapspace, or SYS1
data sets to a different catalog than the one specified in the VVR. If the
data set you are recataloging is one
Google is your friend.
Joe
On Thu, Dec 23, 2021 at 3:47 AM Jake Anderson
wrote:
> Hello
>
> I moved the zfs to the new system and when I try to recatalog I get this
> error message and the dataset is in that volume
>
> IDCAMS SYSTEM SERVICES TIME: 22:36:40
>
>
&g
Hello
I moved the zfs to the new system and when I try to recatalog I get this
error message and the dataset is in that volume
IDCAMS SYSTEM SERVICES TIME: 22:36:40
DEFINE CLUSTER(NAME(OMVS.OSRSA2.ROOT.ZFS) -
VOLUME(OSRSA2) -
LINEAR -
RECATALOG)
IDC3014I CATALOG ERROR
IDC3009I
In
0524368475122199.wa.elardus.engelbrechtsita.co...@listserv.ua.edu,
on 08/27/2014
at 03:32 AM, Elardus Engelbrecht elardus.engelbre...@sita.co.za
said:
Many things in ISPF can be done in ISPF.
ITYM from the TSO READY prompt.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO
Shmuel Metz (Seymour J.) wrote:
Many things in ISPF can be done in ISPF.
ITYM from the TSO READY prompt.
Yes, that too. Thanks for correcting me. I actually wanted to say 'can be done
in TSO READY, batch and now with that thread about ISPF service, also via ISPF
services'.
Thanks Shmuel for
Hi,
How do I rename a dataset in batch if it will need to be cataloged in a
different catalog?
For example, I would like to rename SYS1.FOOBAR to SYSV.FOOBAR.
Datasets with an HLQ of SYSV are cataloged in a different catalog the datasets
with an HLQ of SYS1.
This is very simple in ISPF, but
and the dataset is both
non-VSAM and non-SMS, then using IDCAMS you can:
Uncatalog it with DEL NSCR
Rename it with ALTER NEWNAME FILE
Recatalog it with DEFINE NVSAM in any catalog you want.
If the dataset is VSAM, your best bet is to copy it (e.g., IDCAMS or
ADRDSSU) to the new DSN and then delete
Gadi wrote:
How do I rename a dataset in batch if it will need to be cataloged in a
different catalog?
For example, I would like to rename SYS1.FOOBAR to SYSV.FOOBAR.
Datasets with an HLQ of SYSV are cataloged in a different catalog the datasets
with an HLQ of SYS1.
This is very simple in ISPF,
Of ??? ?? ???
Sent: Wednesday, August 27, 2014 12:35 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Rename dataset and recatalog
Hi,
How do I rename a dataset in batch if it will need to be cataloged in a
different
catalog?
For example, I would like to rename SYS1.FOOBAR to SYSV.FOOBAR.
Datasets
Subject: Re: Rename dataset and recatalog
Are the datasets all NON VSAM that you want to rename? Are then on SMS or
NONSMS volumes?
Could you explain more of what this rename is for? Why you need to do this?
If it is because of version changes in software, look at SYMBOLICRELATE
function.
I use
On Wed, Aug 27, 2014 at 6:54 AM, גדי בן אבי gad...@malam.com wrote:
Actually, the TSO Rename commands works just fine, so does the rename
command in FTP.
Gadi
as does the ALTER ... NEWNAME(...) command in IDCAMS. Using ISPF has
crippled the OP. Much like using Windows.
--
There is
and recatalog
To: IBM-MAIN@LISTSERV.UA.EDU
Date: Wednesday, August 27, 2014, 3:35 AM
Hi,
How do I rename a dataset in batch if it will need to be
cataloged in a different catalog?
For example, I would like to rename SYS1.FOOBAR to
SYSV.FOOBAR.
Datasets with an HLQ of SYSV are cataloged
I had to re-catalog the VVDS for the CATALOGS which no longer exists but still
show up on the DIAGNOSE.
This is what I did:
I defined the CATALOG (which doesn't exist)
I then did a DEFINE RECATALOG of the VVDS entry
Next I performed the DEL NSCR of the VVDS entry.
Deleted the CATALOG
Willie,
What you did was recatalog a VVDS which probably was not needed.
If you did not accidently delete the VVDS in the CATALOG, you do not need to
do this in my opinion.
VVDS is a VSAM ESDS data set and can be considered an extension of the VTOC.
There is one VVDS on every volume
Lizette:
I will just say it is a tidy thing to do, so it doesn't look like the
sysprog is not doing his duty.
Ed
On Jul 2, 2014, at 8:03 PM, Lizette Koehler wrote:
Willie,
What you did was recatalog a VVDS which probably was not needed.
If you did not accidently delete the VVDS
Good Day,
Can you spot my error. I am trying to define the VVDS to a specif USERCAT. Is
the RECATALOG option allowed?
DEF NVSAM -
(NAME(SYS1.VVDS.VPROM56) -
DEVT(3390
')
TO('DATE') | FOR('DAYS')
RECATALOG | NORECATALOG )
CATALOG('CATNAME/PASSWORD')
REQUIRED - NONVSAM, NAME, DEVICETYPES, VOLUMES
Move the recatalog inside the inclusive ()
_
Dave Jousma
Assistant Vice President, Mainframe Engineering
david.jou...@53.com
1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H
p 616.653.8429
f 616.653.2717
-Original Message
@LISTSERV.UA.EDU
Subject: IDCAMS QUESTION - RECATALOG
Good Day,
Can you spot my error. I am trying to define the VVDS to a specif
USERCAT. Is
the RECATALOG option allowed?
DEF NVSAM -
(NAME(SYS1.VVDS.VPROM56) -
DEVT(3390)-
VOL
DEF NVSAM -
(NAME(SYS1.VVDS.VPROM56) -
DEVT(3390)-
VOL(PROM56)
Recatalog
I verified your example with my JCL and I didn't see any difference. Am I
missing something?
On Wed, 7/2/14, Greg Shirey wgshi...@benekeith.com wrote:
Subject: Re: IDCAMS QUESTION - RECATALOG
To: IBM-MAIN@LISTSERV.UA.EDU
Received: Wednesday, July
willie bunter wrote:
I verified your example with my JCL and I didn't see any difference. Am I
missing something?
Yes. Position of keyword RECATALOG is, as stated by others, wrong.
Change
...
VOL(PROM56)) -
CATALOG(SYS1.ICFCAT.SYSPRM) -
RECATALOG
to this
...
VOL
David,
Your suggestion worked. I was missing the ) after the RECATALOG parm.
On Wed, 7/2/14, Jousma, David david.jou...@53.com wrote:
Subject: Re: IDCAMS QUESTION - RECATALOG
To: IBM-MAIN@LISTSERV.UA.EDU
Received: Wednesday, July 2, 2014, 6:11
.
On Wed, 7/2/14, Lizette Koehler stars...@mindspring.com wrote:
Subject: Re: IDCAMS QUESTION - RECATALOG
To: IBM-MAIN@LISTSERV.UA.EDU
Received: Wednesday, July 2, 2014, 6:11 AM
Why do you think you need
to do this?
The VVDS is a special dataset and part
So why use the RECATALOG?
The message says
Run DIAGNOSE ICFCATALOG for the extraneous catalog name. Determine whether
data sets are missing from the volume. If no data sets are missing, use the
DELETE command with the NOSCRATCH option to remove the VVDS entry from the
extraneous catalog.
If any
On Wed, 2 Jul 2014 06:03:44 -0700, willie bunter wrote:
I am trying to define the VVDS to a specif USERCAT. Is the RECATALOG option
allowed?
The VVDS is part of the catalog. The BCS points to the volume and the data set
type.
IIRC, all of the other information that you see when you perform
I remember reading it somewhere. I will dig around and post it.
On Wed, 7/2/14, Lizette Koehler stars...@mindspring.com wrote:
Subject: Re: IDCAMS QUESTION - RECATALOG
To: IBM-MAIN@LISTSERV.UA.EDU
Received: Wednesday, July 2, 2014, 6:36 AM
So
Lizette,
This is what I found in our internal archives regarding the RECATALOG parm :
The RECATALOG parameter is required for VSAM and SMS managed datasets. It
basically tells IDCAMS to read information out of the VVDS to reconstruct the
catalog entry correctly
On Wed, 2 Jul 2014 08:59:39 -0500, Tom Marchant wrote:
you could have simply issued a DELETE NOSCRATCH for that
catalog of the VVDS.
This won't do anything useful. You had said that the VVDS is
not cataloged in that catalog. Deleting the catalog reference
from the VVDS is not so easy. I
If you can perform a LISTCAT for the datasets on PROM56 and see the data
that is stored in the VVDS (e.g., for non-VSAM, you can see the storage,
data, and management classes), then the VVDS is working properly and there
is no need for you to recatalog the VVDS in any catalog dataset.
Optional
I have a copy of a DASD volume that contains some OMVS (ZFS) filesystems.
I realized that I cannot use ISPF 3.4 to catalog the dataset. I get a VSAM
DATA SET error. Looking in at DFSMS AMS I find a RECATALOG option for a
couple of DEFINEs. But the ZFS files are created via ALLOC
Define cluster name(dataset.name) recatalog nixd) ?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Mark,
You should be able to use the DEF RECATALOG. With the RECATALOG, IDCAMS will
look at the dataset on the DASD volume and build the catalog entries for the
dataset.
Rex
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Mark
If the clusters are not currently defined, no problem. DEFINE CL (NAME(cluster)
VOLUME(volser) LINEAR RECATALOG). (All ZFS's are Linear VSAM).
If they are currently defined, there are 2 solutions to this:
1) Move the HLQ (presumably OMVS) to a UCAT and provide uniqueness at qualifier
2
Thank you all for the information.
DEFINE CL (NAME(cluster) VOLUME(volser) LINEAR RECATALOG
Did the trick.
On Thu, Mar 6, 2014 at 1:49 PM, Staller, Allan allan.stal...@kbmg.comwrote:
If the clusters are not currently defined, no problem. DEFINE CL
(NAME(cluster) VOLUME(volser) LINEAR
38 matches
Mail list logo
