Logical segment expansion problem.

keitholsen · New User Joined: 07 Mar 2008 Posts: 5 Location: Elgin, IL

I have an logical segment that I've tried to expand by 10 bytes in the 'Intersection Data' area. When I try to use the new 10 byte area, IMS seems to ignore it.

Here is the old logical segment in the DBD:

SEGM NAME=MSMTCOM,
PARENT=((MSROOT,SNGL),(CPMROOT,V,DBCPM1)),
BYTES=098,
POINTER=(T,LTB),
RULES=PVV
FIELD NAME=(MSMTKEY,SEQ,U),
BYTES=34,
START=65

Here is the new logical segment in the DBD.

SEGM NAME=MSMTCOM,
PARENT=((MSROOT,SNGL),(CPMROOT,V,DBCPM1)),
BYTES=108,
POINTER=(T,LTB),
RULES=PVV
FIELD NAME=(MSMTKEY,SEQ,U),
BYTES=34,
START=65
FIELD NAME=MSINTLVL,
BYTES=10,
START=99,
TYPE=C

Nothing else has been changed.

I do not get any errors when I regen/reload the database PSB's and ACB's. I also do not get any errors when I do GU, REPL, ISRT in my program. But the new 10 byte area is ignored.

Thanks for any help.

Keith

Bitneuker · Posted: Fri Mar 07, 2008 10:58 pm

Did you also change the physical database DBCPM1?

keitholsen · New User Joined: 07 Mar 2008 Posts: 5 Location: Elgin, IL

Thanks for responding.

I didn't change the DBCPM1 database. From what I can see from the IBM manuals, this being a "Bidirectional virtually paired logical relationship", only one physical child is created and that being under the DBMER1 database. Unless I'am wrong about this being a Virtually Paired vs a Physically Paired relationship.

Here is the DBD SEGM from the DBCPM1 database.

SEGM NAME=CPMTMER,
PARENT=CPMROOT,
POINTER=PAIRED,
SOURCE=((MSMTCOM,D,DBMER1))
FIELD NAME=(CTMKEY,SEQ,U),
BYTES=30,
START=1

Bitneuker · Posted: Sun Mar 09, 2008 2:33 am

Backout/Recovery/Reload?

keitholsen · New User Joined: 07 Mar 2008 Posts: 5 Location: Elgin, IL

The Backout and Reload run OK with no errors. We are not doing a Recovery.

Bitneuker · Posted: Mon Mar 10, 2008 11:53 pm

Is this MSINTLVL field defined in any physical database? Also check this

keitholsen · New User Joined: 07 Mar 2008 Posts: 5 Location: Elgin, IL

The MSINTLVL data not in any physical database. It is only in the Intersection Data area of the logical segment.

From what I've read, this area of the logical segment is for data that is unique only for the logical relationship between 2 databases. That is exactly what I need.

I'm missing something somewhere. I'll keep you posted.

Bitneuker · Posted: Tue Mar 11, 2008 12:40 am

I did some re-reading in your first post and noticed you showed a physical DBD. Check this out for the RULES parameter in a physical DBD.

Follow the first link in my signature and search for 'physical dbd' and 'logical dbd' and do some exploring.

By the way: you might also consult your DBA.

Bitneuker · Posted: Tue Mar 11, 2008 12:49 am

Also check with intersection data.

keitholsen · New User Joined: 07 Mar 2008 Posts: 5 Location: Elgin, IL

George,

I've been reading those links you have sent me trying to find something. My fix is buried in there somewhere!!

We do have our DBA helping us. We might end up having to call IBM on this one. I will let you know if we find what it is.

Thanks again for all your help.

Keith