ca.portal.admin

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,
Petra

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.
Petra



At 12:10 PM 1/10/2007, you wrote:
I think the restructure puts the expanded records in the
new sequence in=3D0D=3D
=3D0Athe set=3D2E I always thought of restructure handling the
logical=3D0D=3D0Aorg=3D
anization of the database and unload/reload the physical org=3D2E I
dont=3D0D=3D
=3D0Athink you need to run an unload/reload unless you're also
changing
the=3D
=3D0D=3D0Apage size or cleaning up
fragmentation=3D2E=3D0D=3D0A=3D0D=3D0ALutz Petzold=3D0D=3D

=3D0A=3D0D=3D0A=3D0D=3D0A=3D0D=3D0A=3D0D=3D0A---------------------------=
--------------=3D0D
=3D0AT
=3D
his e-mail may contain confidential or privileged information=3D2E
If=3D0D=3D0Ayo=3D
u think you have received this e-mail in error, please advise
the=3D0D=3D0Asend=3D
er by reply e-mail and then delete this
e-mail immediately=3D2E=3D0D=3D0AThank yo=3D
u=3D2E Aetna=3D0D=3D0A
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Record and set changes
"Do the member records have the foreign key of the owner? If so you could
DISCONNECT all the member records, do your restructure. Then in a single
program you could populate the new data items and CONNECT the member
records back into the set - this would now give you the correct sort
sequence.

If you don't have the foreign keys - in the DISCONNECT program get the
key of the owner record for each member record and write to a flat file
(this file would need to have some way of relocating the member records
- perhaps a DBKEY if there's nothing else to access directly such as a
CALC key). Do your database changes. Run the CONNECT and populate step
using the flat file to guide the navigation.

Just a thought - cheers - Gary

Outcomes