On Wed, 12 Mar 2008 22:31:38 -0700, Edward Jaffe
[EMAIL PROTECTED] wrote:
Hmmm. When a data set is migrated, the VTOC entry is removed. But, the
catalog entry is still there (though the volume ID is changed to MIGRAT).
Can't IDCAMS tell from the catalog whether the migrated data set is VSAM
or
- Original Message
From: William Bishop [EMAIL PROTECTED]
The problem is that if you perfrom an IDCAMS DELETE and specify nonvsam,
HSM does a recall. Without the nonvsam, he does an HDELETE if the dataset
is migrated.
Correct. We have CA-Disk in place and it behaves the same.
On Wed, 12 Mar 2008 22:21:34 -0500, Chase, John [EMAIL PROTECTED] wrote:
Indeed, how should Allocation know whether the program about to execute
wants to do something with the dataset(s) before deleting it/them?
Perhaps Allocation could be educated to issue HDELETE iff the dataset
is migrated
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Edward Jaffe
[ snip ]
Hmmm. When a data set is migrated, the VTOC entry is removed.
But, the catalog entry is still there (though the volume ID
is changed to MIGRAT).
Can't IDCAMS tell from the catalog
Dave Cartwright wrote:
No, a VSAM cluster is turned into a flat file on migration and is cataloged as a
NONVSAM dataset on volume MIGRAT. If its device type is tape it shows as
MIGRAT2, else it's MIGRAT1.
Too bad. That seems like a poor design choice in hindsight given the
current topic.
I think you are a bit confused, HDELETE does not have a NONVSAM option, IDCAMS
does. At the time of a delete, IDCAMS cannot assume that HSM is the migrator,
it could just as easily be FDRABR or some other product.
Paul Gilmartin [EMAIL PROTECTED] 3/13/2008 10:18 AM ( mailto:[EMAIL
On Thu, 13 Mar 2008 04:17:40 -0700, Edward Jaffe wrote:
Dave Cartwright wrote:
No, a VSAM cluster is turned into a flat file on migration and is cataloged
as a
NONVSAM dataset on volume MIGRAT. If its device type is tape it shows as
MIGRAT2, else it's MIGRAT1.
Too bad. That seems like a
Apparently there is a bit of both going on here. HSM knows that the
VSAM components are in fact components of a cluster, but if you do a
LISTCAT of a migrated VSAM dataset, whether you LISTCAT the CLUSTER name
or one of the components, it shows the entry is of a nonvsam dataset
type. LISTCATting
On Thu, 13 Mar 2008 10:59:37 -0400, Scott Rowe wrote:
I think you are a bit confused, HDELETE does not have a NONVSAM option, IDCAMS
does. At the time of a delete, IDCAMS cannot assume that HSM is the migrator,
it could just as easily be FDRABR or some other product.
Thank you for improving
In the case of the generic DELETE (without NONVSAM), FDRABR intercepts the
HDELETE issued by IDCAMS, and it works fine (IIRC). The interfaces are not
compatible, I agree that it would be beneficial, but someone (IBM) would have
to define such an API - and share it with the ISVs - in order to
In [EMAIL PROTECTED],
on 03/12/2008
at 10:21 PM, Chase, John [EMAIL PROTECTED] said:
Perhaps Allocation could be educated to issue HDELETE iff the dataset
is migrated *AND* DISP=(,DELETE) *AND* PGM=IEFBR14.
Bletch! I hope that was intended as a joke.
--
Shmuel (Seymour J.) Metz,
---snip--
Thank you for improving my understanding.
But still ...
It appears that the consensus of this thread is that in the absence
of the NONVSAM option, IDCAMS converts a DELETE request for a migrated
data set to HDELETE. If IDCAMS doesn't know whether the
Programmers have been deleting for years using BR14 (MOD,DELETE), and
IDCAMS DELETE. I am finding that we are spending ever more time on HSM
Migrated ds being recalled just to delete them. Is there an EASY way to
convert these deletes into HSEND DELETE?
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of John Mattson
Sent: Wednesday, March 12, 2008 11:44 AM
To: IBM-MAIN@bama.ua.edu
Subject: Easy way to covert IEFBR14 and IDCAMS deletes to HDELETE
Programmers have been deleting for
John Mattson wrote:
Programmers have been deleting for years using BR14 (MOD,DELETE), and
IDCAMS DELETE. I am finding that we are spending ever more time on HSM
Migrated ds being recalled just to delete them. Is there an EASY way to
convert these deletes into HSEND DELETE?
I thought
The problem is that if you perfrom an IDCAMS DELETE and specify nonvsam,
HSM does a recall. Without the nonvsam, he does an HDELETE if the dataset
is migrated.
I am trying to figure a way to convert my deletes without having to go
thru a massive change process to remove the nonvsam entries.
John Mattson wrote:
Programmers have been deleting for years using BR14 (MOD,DELETE), and
IDCAMS DELETE. I am finding that we are spending ever more time on HSM
Migrated ds being recalled just to delete them. Is there an EASY way to
convert these deletes into HSEND DELETE?
CBT File 673: A
DTS has a product, ACC, that can handle these for you. We use it and it
works great. It cut out our recalls for BR14 deletes completely.
ThanksRick
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of John Mattson
Sent: Wednesday, March 12,
William Bishop wrote:
The problem is that if you perfrom an IDCAMS DELETE and specify nonvsam,
HSM does a recall. Without the nonvsam, he does an HDELETE if the dataset
is migrated.
This sounds APARable to me.
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd,
In
[EMAIL PROTECTED],
on 03/12/2008
at 09:44 AM, John Mattson [EMAIL PROTECTED] said:
Programmers have been deleting for years using BR14 (MOD,DELETE), and
IDCAMS DELETE.
IEFBR14 doesn't delete the data set. By the time IEFBR14 gets control the
data set has already been recalled. But I
On Wed, 12 Mar 2008 11:03:41 -0700, Edward Jaffe
[EMAIL PROTECTED] wrote:
William Bishop wrote:
The problem is that if you perfrom an IDCAMS DELETE and specify nonvsam,
HSM does a recall. Without the nonvsam, he does an HDELETE if the dataset
is migrated.
This sounds APARable to me.
I
On Wed, 12 Mar 2008 11:03:41 -0700, Edward Jaffe wrote:
William Bishop wrote:
The problem is that if you perfrom an IDCAMS DELETE and specify nonvsam,
HSM does a recall. Without the nonvsam, he does an HDELETE if the dataset
is migrated.
This sounds APARable to me.
... or a Requirement?
Amen brother gil..thats because most of the sys admins don't really know how
to program
Scott
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Paul Gilmartin
Sent: Wednesday, March 12, 2008 8:52 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re:
I've got basically the same thing with a HBDELETE first. I call it
HBEGONE.
Ages ago, before TSO/IDCAMS was so nearly smart, I coded in
Rexx (IIRC):
address 'TSO'
'HDELETE ''DATA.SET.NAME'' WAIT'
if RC0 then
'DELETE
On 12 Mar 2008 17:52:58 -0700, in bit.listserv.ibm-main
(Message-ID:[EMAIL PROTECTED])
[EMAIL PROTECTED] (Paul Gilmartin) wrote:
Ages ago, before TSO/IDCAMS was so nearly smart, I coded
in
Rexx (IIRC):
address 'TSO'
'HDELETE ''DATA.SET.NAME'' WAIT'
if RC0 then
'DELETE
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Shmuel Metz (Seymour
J.)
John Mattson said:
Programmers have been deleting for years using BR14 (MOD,DELETE), and
IDCAMS DELETE.
IEFBR14 doesn't delete the data set. By the time IEFBR14 gets
control the
Walt Farrell wrote:
On Wed, 12 Mar 2008 11:03:41 -0700, Edward Jaffe
[EMAIL PROTECTED] wrote:
William Bishop wrote:
The problem is that if you perfrom an IDCAMS DELETE and specify nonvsam,
HSM does a recall. Without the nonvsam, he does an HDELETE if the dataset
is migrated.
27 matches
Mail list logo
