ca.portal.admin

Re:Re: Exceeds Resource Limits using DMLO

Discussion created by ca.portal.admin on Aug 29, 2005
Any indexes on the SERVIC record?


----- Original message -----
From: ""Ruth Kraber-Lendt"" <rkraber@DHS.STATE.IA.US>
To: IDMS-L@LISTSERV.IUASSN.COM
Date: Mon, 29 Aug 2005 15:12:25 -0500
Subject: 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
Prior with SQL
"Hi Everyone:

To the experts with sql, how we can create a sql to get prior in a set
relationship, we know that with teh fetch we can move forward, but how to do
that backward ???? We are converting some ads application using netwok
database, and we need to convert ""Obtain prior withiin"" in different
processes.

TIA.

Javier S.

_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!
http://search.msn.com/

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








Normal

Normal
Re: Prior with SQL
"Javier,

If your OBATAIN PRIOR only gets 1 record the the SQL ""set-name"" would be LAST ""IDMS-SET-NAME"". That gets the PRIOR from OWNER. I don't think the SQL can navigate all members
backwards. The only way I know of to do that is via a Table Procedure.

Joe S Cates, C.C.P.
Database Analyst
Office of Global Access Technology
Montgomery County Public Schools
Rockville, MD 20850
email: Joe_Cates@fc.mcps.k12.md.us


t.IUASSN.COM> on Tuesday,
August 30, 2005 at 10:41 AM wrote:

Hi Everyone:

To the experts with sql, how we can create a sql to get prior in a set
relationship, we know that with teh fetch we can move forward, but how to
do
that backward ???? We are converting some ads application using netwok
database, and we need to convert ""Obtain prior withiin"" in different
processes.

TIA.

Javier S.

_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!
http://search.msn.com/
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: 0326 on an OBTAIN NEXT RECORD WITHIN INDEX-SET
"The Manual states:


0326 „  Either the record or SPF index entry cannot be found or
no more duplicates exist for the named record.

Not sure how that might happen unless the member records are also CALC
with duplicates allowed..


----- Original message -----
From: ""Bill Allen"" <ARCHCONB@AOL.COM>
To: IDMS-L@LISTSERV.IUASSN.COM
Date: Tue, 30 Aug 2005 13:00:02 EDT
Subject: 0326 on an OBTAIN NEXT RECORD WITHIN INDEX-SET

Hello All:

Does anyone know why you would receive an 0326 on:

OBTAIN NEXT RECORD WITHIN INDEX-SET.

This is a local mode batch retrieval job, the index set connection is
MA, we
are not using a sort key in the obtain.

Bill Allen

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








Normal

Normal
Re: 0326 on an OBTAIN NEXT RECORD WITHIN INDEX-SET
"We see this occasionally in local mode retrieval jobs when the CV is
active and is using the records or areas in question. It is because
SR8's have been updated and the key that IDMS expects to find is not
there. We just habe production control restart the job and everything
runs fine. If your application is critical, then you will need to
either have the areas offline to the CV or ready the area in protected
or exclusive update.

Dan Miley
Lockheed Martin

Outcomes