ca.portal.admin

Re:Re: Computed DBKEY from a SQL Table Procedure

Discussion created by ca.portal.admin on Jun 26, 2007
Joe,

This is only happening on dbkeys with very high page
numbers. Right? When the page number is greater than
8,388,607 (x'7fffff'), the high order bit in the dbkey
is on, so it is a negative number.

Rich Kurzawski
--- ""Cates, Joe"" <Joe_Cates@MCPSMD.ORG> wrote:
I have written a number of COBOL Table Procedures
over the past several
years to help with data migration to a relational
database. These Table
Procedures use EDBC and have performed well. There
is now a need to
include the DBKEY, in a decimal format, as an
additional column. There
is an unusual situation with the computed key in
that the page number is
correct but the line isn't. For example, a DBKEY
that should compute to
page 1234 and line 56 gives 1234 for the page and
944 for the line. Line
57 computes to 943, 58 to 942 etc. The work around
is to subtract the
line number from 1000 to get the correct result. I
have an open issue
with CA and was given some instructions to create a
version of CEEUOPT
and link it with my program to allow for TRAP=OFF.
The program was
altered to do a zero divide to cause an ABEND. The
job is to run locally
to produce a SYSMDUMP. The systems programmer
followed those
instructions but we are unable to produce the
required dump. The other
frustrating situation is we are unable to get the
CEEUOPT to resolve via
an INCLUDE. Any suggestions??



Thanks,



Joe S Cates, Database Analyst II

Systems Architecture and Operations
Database Management/Unix Administration

Montgomery County Public Schools

Rockville, MD 20850

301-279-3697

joe_cates@mcpsmd.org






________________________________________________________________________
____________Ready for the edge of your seat?
Check out tonight's top picks on Yahoo! TV.
http://tv.yahoo.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: Computed DBKEY from a SQL Table Procedure
"I think its important to understand that for Joe and myself, this problem
didn't happen with straight Cobol programs. It only occurred in Cobol Table
procedures which was very perplexing.

Dan, I agree that this will only work with standard radix. It also only
works if your page numbers are less than 8 million. In my case, we only use
standard radix and our page numbers aren't that big at this time. We did,
however want to have growth room, so the Cobol code was changed.

But the perplexing part has been why it works with regular Cobol programs
and not with table procedures. Anyone have any idea what that's all about?

Outcomes