ca.portal.admin

Restructure syntax

Discussion created by ca.portal.admin on Aug 26, 2005
Let's call the owner record FREDPTR and the member records FREDCASE. We
want to erase all the FREDCASE instances but think it would be faster to
Init FREDCASE-AREA and then fix the pointers in the FREDPTR instances
with a restructure. The manuals don't provide such an example, however.
An old Listserve message suggests something like this would work. Would
it? Thanks.



...

IDMSRSTT RECNAME=FREDPTR

IDMSRSTT SETPTR=(1,1)

IDMSRSTT SETPTR=(*,2,FREDPTR-FREDCASE) RE-INIT NEXT POINTER

IDMSRSTT SETPTR=(*,3,FREDPTR-FREDCASE) RE-INIT PRIOR POINTER

IDMSRSTT SETPTR=(4,4)

IDMSRSTT SETPTR=(5,5)

...



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








Normal

Normal
Restructure syntax
"Let's call the owner record FREDPTR and the member records FREDCASE. We
want to erase all the FREDCASE instances but think it would be faster to
Init FREDCASE-AREA and then fix the pointers in the FREDPTR instances
with a restructure. The manuals don't provide such an example, however.
An old Listserve message suggests something like this would work. Would
it? Thanks.



...

IDMSRSTT RECNAME=FREDPTR

IDMSRSTT SETPTR=(1,1)

IDMSRSTT SETPTR=(*,2,FREDPTR-FREDCASE) RE-INIT NEXT POINTER

IDMSRSTT SETPTR=(*,3,FREDPTR-FREDCASE) RE-INIT PRIOR POINTER

IDMSRSTT SETPTR=(4,4)

IDMSRSTT SETPTR=(5,5)

...



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








Normal

Normal
Exceeds Resource Limits using DMLO
"Hello,

I have a situation where I'm exceeding resource limits while trying to
modify a record using DMLO. The limits are set at 7000.

Here is the scenario that I'm abending on.

Owner Record Client
Member Record Servic
Client-Servic set is defined as NPO MA DSC Date-End-Servic DF

The Client owner record has 4 Servic member records. Listed below are the 4
servic records along with the Date-End-Servic value.
I populate the Date-End-Servic with the value of 20030823 on Servic 1 and
modify the Servic record using DMLO. This is where I exceed resource limits
and abend. If the modify would have completed the set would then be in a
different order with Servic 2 being listed first and Servic 1 being listed
second. This is a common process that we do and have not had problems
before with exceeding resource limits.

Date-End-Servic
Servic 1 99999999
Servic 2 99999999
Servic 3 20030301
Servic 4 20030204


We did change the limits to 10000 and the record modified okay. Does anyone
have a clue why I would abend when I'm trying to modify 1 record in a sorted
set that contains only 4 members? I can walk this set forward and backward
which indicates no broken chains and when I increase limits the record will
modify?

Thanks for any input.


Ruth Kraber-Lendt
Child Welfare Information Systems (CWIS)
rkraber@dhs.state.ia.us
515-281-0376

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








Normal

Normal
Re: Exceeds Resource Limits using DMLO
"No - the servic record has no indexes. However, thanks for asking that
question. It does have another owner record that has a large number of
records attached to it. I'm sure this is why I'm abending with a DC244003
message. Thanks

Outcomes