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=0D=
=0Athe set=2E I always thought of restructure handling the
logical=0D=0Aorg=
anization of the database and unload/reload the physical org=2E I
dont=0D=
=0Athink you need to run an unload/reload unless you're also changing
the=
=0D=0Apage size or cleaning up
fragmentation=2E=0D=0A=0D=0ALutz Petzold=0D=

=0A=0D=0A=0D=0A=0D=0A=0D=0A-----------------------------------------=0D=0AT
=
his e-mail may contain confidential or privileged information=2E
If=0D=0Ayo=
u think you have received this e-mail in error, please advise
the=0D=0Asend=
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
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Record and set changes
"My recollection:

Restructure will only alter the contents of records; either data and/or
prefix portion. It will not adjust set order, only an UNLD/RLD (or rebuild
for an indexed set) will accomplish that.

If the set is not already in sort order, you MAY have issues with updating
the data once you define it as sorted. You're probably OK as long as you
don't do something that would cause IDMS to want to process the set sequence
(e.g., FIND/OBTAIN USING, STORE, MODIFY).

This last is where you're liable to run into issues. If you have already
defined the set as sorted, and then go in an MODIFY the sort field contents,
IDMS may ""notice"" the set is not correctly ordered, and you MAY have a
problem (This is pure guesswork; anybody else want to chime in?).

Safest sequence is:

RSTU the new fields.
MODIFY to get all the right data established.
Define the set order as sorted.
UNLD/RLD.

As Bill points out, you can accomplish the final two steps together, with an
exit to the UNLD/RLD... but that isn't necessarily trivial.

Don Casey
Unattached

Outcomes