I would hope FDR full volume restore would do an honest restore and
leave the change bits as they were.
Of course we do
--
Bruce A. Black
Senior Software Developer for FDR
Innovation Data Processing 973-890-7300
personal: [EMAIL PROTECTED]
sales info: [EMAIL PROTECTED]
tech support: [EMAIL PROTE
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of Clark Morris
>
> I hope that you will be trying to convince your management to
> send this to your IBM sales representative or higher.
>
> Incidentally how does Innovation's FDR handle this?
I've heard that FDR "doe
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of Joel C. Ewing
> Sent: Monday, 2 April 2007 9:08 AM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: DFSMSdss DOC APAR OA20117 (was RE: HSM Missing
> Member from Recalled Data
tralia
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Clark Morris
Sent: Sunday, 1 April 2007 7:10 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: DFSMSdss DOC APAR OA20117 (was RE: HSM Missing
Member from Recalled Dataset -- Update
I hope that you w
M Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of Clark Morris
> Sent: Sunday, 1 April 2007 7:10 AM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: DFSMSdss DOC APAR OA20117 (was RE: HSM Missing
> Member from Recalled Dataset -- Update
>
> I hope that you will be tr
I hope that you will be trying to convince your management to send
this to your IBM sales representative or higher.
Incidentally how does Innovation's FDR handle this?
On 31 Mar 2007 13:24:05 -0700, in bit.listserv.ibm-main you wrote:
>Good Lord!
>
>What idiot could have thought this counter-int
Good Lord!
What idiot could have thought this counter-intuitive behavior is a
reasonable default:
"When restoring data in a full volume or tracks operation,
DFSMSdss resets the data-set-changed indicator
in the VTOC entries of each data set that has had its data
restored. This is to indi
I'd like to second John's request/recommendation on adding your
voices to either the marketing request or the SHARE requirement.
The more people interested in a particular change that add their
voices/votes, the more it helps the priority get set so that the
change gets done.
Thanks,
Andrew Wilt
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of Richards.Bob
> Sent: Thursday, December 14, 2006 4:01 PM
>
> No, and I just read it a few hours ago in an attempt to help
> you. That DEFAULT behavior WAS NOT documented.
The subject DOC APAR closed today, 26 March.
Background: Over the Thanksgiving holiday weekend (U.S.) we relocated
our datacenter. We moved the mainframes' DASD volumes via DFSMSdss DUMP
FULL at the old site, followed by RESTORE FULL at the new site. On the
day the DUMP FULL of every volume was taken, a TSO user had recalled a
migrated PDS
@BAMA.UA.EDU
Subject: Re: HSM Missing Member from Recalled Dataset -- Update
Latest update on my PMR:
DFSMSdss is "WAD". The "change bits" are reset on "physical" RESTOREs
(i.e., RESTORE FULL and RESTORE TRACKS), but not on "logical" RESTOREs
(i.e., RE
Latest update on my PMR:
DFSMSdss is "WAD". The "change bits" are reset on "physical" RESTOREs
(i.e., RESTORE FULL and RESTORE TRACKS), but not on "logical" RESTOREs
(i.e., RESTORE DATASET). What this means is that RESTORE FULL does NOT
create a true and correct copy of the source volume that
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of Richards.Bob
>
> Just for fun, can you post the dump and restore JCL from your test?
Dump:
//STEP001 EXEC PGM=ADRDSSU,REGION=8192K
//SYSPRINT DD SYSOUT=*
/
Just for fun, can you post the dump and restore JCL from your test?
Bob Richards
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Chase, John
Sent: Thursday, December 14, 2006 1:17 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: HSM Missing Member
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of Richards.Bob
>
> John,
>
> These DFSMSdss dumps were not from AUTODUMP, were they?
> Because if they were, the DUMPCLASS could have the RESET
> keyword in its definition.
No; "DASD Backup Supervisor" from OpenTech
, December 14, 2006 12:34 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: HSM Missing Member from Recalled Dataset -- Update
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of Jack Kelly
>
> or the changed bit was reset and hsm thought that the dsn had
> not c
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of Jack Kelly
>
> or the changed bit was reset and hsm thought that the dsn had
> not changed and then reconnected?
Opened a PMR with DFSMShsm, and among other things they explained how
hsm determines a dataset's eligib
> -Original Message-
> From: IBM Mainframe Discussion List
>
> or the changed bit was reset and hsm thought that the dsn had
> not changed and then reconnected?
Since we have a spare volume, we just restored the backup tape again
(DFSMSdss RESTORE FULL PURGE) and I ran a LISTVTOC for th
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of Jack Kelly
>
> or the changed bit was reset and hsm thought that the dsn had
> not changed and then reconnected?
It's apparently true that DFSMSdss resets all the dataset-changed bits
at full-volume restore, so that
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of John Ticic
>
> --- snip ---
> When he recalled it again, the member that he had added was missing.
>
> I checked through SMF and saw the activity. The fact that the dataset
> ([data.set.name]) was on [volser] (a NONS
or the changed bit was reset and hsm thought that the dsn had not changed
and then reconnected?
Jack Kelly
LA Systems @ US Courts
x 202-502-2390
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [E
--- snip ---
When he recalled it again, the member that he had added was missing.
I checked through SMF and saw the activity. The fact that the dataset
([data.set.name]) was on [volser] (a NONSMS volume) complicates matters
a little.
--- snip ---
What kind of activity did you see in SMF that sho
>From an internal note:
=== Begin quote ===
[A colleague] came up to me this morning saying that a dataset he had
recalled from ML2 last Wednesday on [lparname] and had added a member to
was back on ML2 this morning.
When he recalled it again, the member that he had added w
23 matches
Mail list logo
