Re:Re: Record and set changes

Discussion created by ca.portal.admin on Jan 10, 2007
Hi Bill,

I must admit I know very little to nothing about assembler. The fields
will get initialized with values based on other data values so I am
afraid it must be updated via program. At least my programming skills
will get used again. :-)

Thanks for your help,

At 01:05 PM 1/10/2007, you wrote:
Hello Petra:

If you know assembler language you don't need a program to initialize
the fields, you can just modify the output of the Schema Compare and
change the statements to the proper format for your new fields.

I'll look around for an example that I might have.

Bill Allen

In a message dated 1/10/2007 2:27:36 P.M. Eastern Standard Time,
lafresep@U.ARIZONA.EDU writes:

I thought it might be the case. My program that initializes the data
would then cause the set to be updated and put in the proper order.

Thanks for your help.

At 12:10 PM 1/10/2007, you wrote:
I think the restructure puts the expanded records in the
new sequence in=0D=
=0Athe set=2E I always thought of restructure handling the
anization of the database and unload/reload the physical org=2E I
=0Athink you need to run an unload/reload unless you're also
=0D=0Apage size or cleaning up
fragmentation=2E=0D=0A=0D=0ALutz Petzold=0D=

his e-mail may contain confidential or privileged information=2E
u think you have received this e-mail in error, please advise
er by reply e-mail and then delete this
e-mail immediately=2E=0D=0AThank yo=
u=2E Aetna=0D=0A
IDMS Public Discussion Forum


Re: Record and set changes
"I agree with Don that restructure does not modify set order.

However.......I'm confused by your email in that I can't tell if you are
changing to a sorted set or an indexed set (user owned index).

If it is a sorted set and you modify/initialize the sort key, your
program will put the records into the proper order as long as you change
the set definition first and change at least one field in the sort key.
One caveat here is that you MUST process the member records via an area
sweep. Since you are changing set order, you can reposition yourself
within the set with each modify and potentially miss records. Keep in
mind that this can run a while, particularly if you are processing a lot
of data.

If it is an indexed set and the index doesn't yet exist, this is
trickier and I'd need to think more about it. One complication for a
change from an NPO set to an indexed set is the pointer changes.

Which is it?

Linda Campbell
Informatix Inc