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
"Hey Dennis!

Your second message came in as I was finishing this reply to your first
one; as you see below we fit your possible-hardware-issue scenario, with
one possible caveat.

We HAVE found the records in the journal, so IDMS DID at some point
think he put them to disk.

We then looked at the timestamp in the jrnl vs. the timings in TDMF and
they DID NOT line up (and yeah, we calculated and recalculated the GMT
offset in the jrnl vs. the local time in TDMF and still couldn't get
things to line up). The jrnl data happened a couple hours BEFORE the
volume was moved.

We then went and pfix printed the page from the source volume (still
sitting there unmolested), and the records WERE NOT on the source
volume. Means they either never made it there, or ""disappeared"" before
TDMF came along. TDMF appears to be off the hook for this one (with the
possible question of does he through some odd interaction mess up
Shark's caching processes).

We're still pondering, after having thrown out theories surrounding page
# overlaps (we use page groups), wormholes in space, and alien
abduction. Tagging this to a piece of hardware (would be Shark at this
point) is going to be messy.

Oh; one key thing I haven't mentioned yet; we're having unrelated
ABRT1125s in another application in this CV. CA has evidently never had
this ABRT reported, and it hints at buffer/bme corruption. Even though
it's associated with another app/different areas it's now our prime
suspect. Trying to reproduce to get a system snap for CA.

Cheers;

* DQC

Outcomes