ca.portal.admin

Re:Re: IDMS @ TDMF

Discussion created by ca.portal.admin on Jul 20, 2006
Hi Dave,
We make extensive use of TDMF and have not had any problems with it.
We are just coming to the end of a data centre consolidation project
where we have moved well over 50 CV's from one data centre to another
using TDMF. The CV's, which are very busy, were up and running during
the transfers and we have not had any problems.

The only time I have seen a problem was when we used it on a failing
box, moving the volumes off to a good box without having to take the
service down. The disk performance, which was very poor anyway, took a
further hit which caused IDMS problems - but I have never seen a
problem
when using it against a good device.

I also used LDMF for the first time a few weeks ago. This lets you
move
individual files whilst IDMS is still accessing them. Again no
problems.


Regards,
Steve

Steve Terry
BT

'This post represents the views of the author and does not necessarily
accurately represent the views of BT.'
British Telecommunications plc
Registered office: 81 Newgate Street London EC1A 7AJ
Registered in England no. 1800000

This electronic message contains information from British
Telecommunications plc which may be privileged and confidential. The
information is intended to be for the use of the individual(s) or
entity
named above. If you are not the intended recipient, be aware that any
disclosure, copying, distribution or use of the contents of this
information is prohibited. If you have received this electronic
message
in error, please notify us by telephone or e-mail (to the number or
address above) immediately.
We are using TDMF to copy our system from one set of dasd to another
set of
dasd. Has anyone out in IDMS land had any positive, negative or
neural
experiences with using TDMF to move idms database while the database
is
up
and running?



David Brenner

IDMS SYSTEM PROGRAMMER

ACS

2828 N. Haskell

Dallas, TX 75204

214-841-6492

David.Brenner@acs-inc.com <mailTo:David.Brenner@acs-inc.com>

This E-Mail has been scanned for viruses.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: IDMS @ TDMF
"Hi Don,

Given the following two things you've said ....
something comes to my mind :
.... we've seen incidents where the broken chains are best
explained by a ""write that didn't happen""; e.g.; two set
occurrences pointing (both next and prior) into a page where
the two records in question just aren't there. Either IDMS,
MVS, the Shark DASD, the EMC DASD, or TDMF dropped the ball
somewhere.

... , we have just located the STORE event in the journals,
and are attempting to tie that to when the volume was
physically moved.


I have used journals in times past to at least get an idea
if IDMS ""thought"" he/it had received confirmations from the
I/O subsystem that writes to DASD successfully happened
for all of the pages - represented (by records) - found on
journal images.

I am thinking if you guys can find on the journal the ""two
records in question"" that ""just aren't there"" (on the
database now anyway) --- then, maybe that fact could reduce
the likelihood that IDMS was the principle ""culprit"".

Man, if you can see those ""missing"" stored records on the
journal here is you might accomplish :

--- Less suspicion of some possible (perhaps stress
related) ""Bug"" in IDMS. ----

So now you could concentrate more on :

- 1) MVS
- 2) Shark DASD,
- 3) EMC DASD,
- 4) TDMF

!-! Wow - now things are really narrowed down! !-!

<chuckle>

-Dennis

Outcomes