ca.portal.admin

0326 on an OBTAIN NEXT RECORD WITHIN INDEX-SET

Discussion created by ca.portal.admin on Aug 30, 2005
Latest reply on Aug 31, 2005 by ca.portal.admin
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
"Hi Bill,

I've seen 0326's happen when an index is broken (following an SR8 entry to
the next b-tree block and the target's not there). Being that this is
local mode, you might also want to be looking for CV changes that you're
not seeing (someone deletes a record, but the SR8 reflecting it hasn't
been written back to disk yet).

Hope it helps,

Alan Fields
VF Services
Greensboro, NC
336-424-4773
Alan_Fields@vfc.com


IDMS Public Discussion Forum <IDMS-L@LISTSERV.IUASSN.COM> wrote on
08/30/2005 01:00:02 PM:
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
"Those are most likely Phantom Broken Chains.

This is a quite common occurrence when running local mode batch against a
database while it is being updated. What happens is that your next pointer
points to a dbkey that does not exist. This can happen if the page you are
on was updated and written from the buffer but the page it points to was
not written back from the buffer, as well as the opposite.
The only way to avoid this is to run in CV mode or prevent updating
activity during the batch process.

There are other errors that you may get, all indicating a corrupt database
(broken chains).
Minor codes 53, 60 and 61 are also quite common for this situation.

This can of course also happen if you really do have broken chains in the
database.

Tommy Petersen
(Can you bribe a corrupt database?)




Bill Allen
<ARCHCONB@aol.com
> To
Sent by: IDMS IDMS-L@LISTSERV.IUASSN.COM
Public Discussion cc
Forum
<IDMS-L@LISTSERV. Subject
IUASSN.COM> 0326 on an OBTAIN NEXT RECORD
WITHIN INDEX-SET

08/30/2005 01:00
PM


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






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
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
Setting NOMAIL
"Hi IDMS'ers

I have misplaced (or lost..) the link for setting my subscription to
NOMAIL, can somebody please send it to me?

Thanks,
Steve Harmeson

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








Normal

Normal
QO71707 (15.0) and QO71701/2 (16.0)
"Hi,



These apars talk about SIGNON control blocks fragmenting storage pool
255.



Did anyone on the list discover this problem and what effect did they
cause?



Thanks



Chris Wood

Alberta Department of Energy

CANADA

This communication is intended for the use of the recipient to which it is addressed, and may contain confidential, personal and or privileged information. Please contact us immediately if you are not the intended recipients of this communication, and do not copy, distribute, or take action relying on it. Any communication received in error, or subsequent reply, should be deleted or destroyed.

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








Normal

Normal

"Has anyone sucessfully installed IDMS base products via the downloads as
opposed to tapes being delivered.
Were there many problems?

TIA
Tim

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








Normal

Normal

"Hi Tim,

I have installed R16 SP2 this way with no problems.

John

At 02:21 PM 8/31/2005, you wrote:
Has anyone sucessfully installed IDMS base products via the downloads as
opposed to tapes being delivered.
Were there many problems?

TIA
Tim
John Abell
International Software Products

This email may contain confidential and privileged material for the
sole use of the intended recipient(s). Any review, use, retention,
distribution or disclosure by others is strictly prohibited. If you
are not the intended recipient (or authorized to receive on behalf of
the named recipient), please contact the sender by reply email and
delete all copies of this message. Also, email is susceptible to data
corruption, interception, tampering, unauthorized amendment and
viruses. We only send and receive emails on the basis that we are not
liable for any such corruption, interception, tampering, amendment or
viruses or any consequence thereof.

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








Normal

Normal

"Hi Tim,

I downloaded R16 SP2 maintenance, and we did not have any real problems.
The only minor problem that I had was forgetting to save the
instructions (that were in a pdf format) once I downloaded the
maintenance. Of course, I got sidetracked by developper requests &
production problems, and by the time I came back to the installation a
couple of days later, I couldn't remember what I had read. It must be a
age thing. Anyway, I opened up a problem, and they sent me the pdf.
Basically, after you download the zip file, you will need to transfer
the .esd file up to your mainframe, and then use a new-to-me program
CAESDR to recreate the actual installation tape. And from then on, it's
the same process as before.

Laura Rochon
Ajilon Consulting

Tim Cauthorn wrote:
Has anyone sucessfully installed IDMS base products via the downloads as
opposed to tapes being delivered.
Were there many problems?

TIA
Tim


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








Normal

Normal

"Tim,
I've done this for both 15 base, 15 maint, and 16 base without any issues.

Dan Hall

-----Original Message-----
From: IDMS 3rd-party providers forum [mailTo:IDMSVENDOR-L@LISTSERV.IUASSN.COM] On Behalf Of Tim Cauthorn
Sent: Wednesday, August 31, 2005 2:22 PM
To: IDMSVENDOR-L@LISTSERV.IUASSN.COM
Subject:


Has anyone sucessfully installed IDMS base products via the downloads as
opposed to tapes being delivered.
Were there many problems?

TIA
Tim

"
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
"What was the resolution to your questiion?


----- 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: QO71707 (15.0) and QO71701/2 (16.0)
"We did not have an identified problem. We had someone from CA at the office
looking at some problem. While browsing pool 255 we noticed some control
blocks at fixed interval and level 2 identified them as SON control blocks.
CA wrote an apar to eliminate or reduce the fragmentation causes by the SON
control blocks since fragmentation may cause problems for some functions
requiring a contiguous piece of storage. This is a prevention apar to make
better use of pool 255.

Jacques Dumouchel
CCRA-ADRC

Outcomes