ca.portal.admin

Order of members in an unsorted via set

Discussion created by ca.portal.admin on May 25, 2005
Latest reply on May 25, 2005 by ca.portal.admin
Hello all

We have a set relationship that is not acting the way I expect it to.

Record1 is the owner and is calc. Record2 is via an unsorted set with
""ORDER IS NEXT"" specified in the set. In normal online situations, when
we add new entries of Record2, they show up at the end of the set as I
expect. Last in last out. We have a batch COBOL load program to re-load
Record2 after a format change. We try to keep the order of Record2
entries by unloading using an area sweep on Record1 and reading Record2
through the set until reaching the end of set for each occurance of
Record1. When we load Record2 records back, they end up in the reverse
order that they were unloaded in. That's not what I expected it to do,
nor what I remembered it doing. Any ideas why it's doing this?

Thanks
Richard

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Order of members in an unsorted via set
"It looks like you re-establish currency on the owner (record1) between
stores of record2
You need to have currency on record2 when storing, so the next is
end-of-set. I you have currency on record1 next will be start-of-set.

Tommy Petersen




Richard Everitt
<reveritt@DIS.UMS
MED.EDU> To
Sent by: IDMS IDMS-L@LISTSERV.IUASSN.COM
Public Discussion cc
Forum
<IDMS-L@LISTSERV. Subject
IUASSN.COM> Order of members in an unsorted via
set

05/25/2005 05:33
PM


Please respond to
IDMS Public
Discussion Forum
<IDMS-L@LISTSERV.
IUASSN.COM>






Hello all

We have a set relationship that is not acting the way I expect it to.

Record1 is the owner and is calc. Record2 is via an unsorted set with
""ORDER IS NEXT"" specified in the set. In normal online situations, when
we add new entries of Record2, they show up at the end of the set as I
expect. Last in last out. We have a batch COBOL load program to re-load
Record2 after a format change. We try to keep the order of Record2
entries by unloading using an area sweep on Record1 and reading Record2
through the set until reaching the end of set for each occurance of
Record1. When we load Record2 records back, they end up in the reverse
order that they were unloaded in. That's not what I expected it to do,
nor what I remembered it doing. Any ideas why it's doing this?

Thanks
Richard

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: XA Storage Type Terminal and Database
"Thanks Sam.

We had it applied to production for yesterday and saw the DB pool come
right back down again. Wonder when this fix and TF24458 will become
'real' apars?

Thanks

Chris

Outcomes