Re: Replacing an element in a record

Discussion created by ca.portal.admin on May 7, 2009

I think you can do it.
Create a new version of the record - same layout, then add that version to
the schema.
Change version 1 to the new layout, that is the one used by the programs,
but no longer by the schema.
Then change the schema once again to use version 1 and recompile the

You lose control of which programs recognize the new layout, but I guess
that is what you were looking for.

I have not tested this, but in theory it should work.

As Yogi Berra said, ""In theory there is no difference between theory and
practice. In practice there is.""

Tommy Petersen
110 Cokesbury Rd
Room 542H
Lebanon, NJ 08833

Internal 200 - 3699
External (908) 236-3699
Fax: (908) 236-3692

Petra LaFrese
Public Discussion cc
IUASSN.COM> Replacing an element in a record

05/07/2009 08:23

Please respond to

I have a simple question and I know all you experts can help me.

I have a record that is composed of 3 main data elements each consisting
of subordinate elements. A subordinate element is being changed in one
of the main data elements.

Normally, I change the record to a higher version number, create a new
version 1 record, recompile the schema with the new record version 1,
and then recompile all the programs that use this record so they are all
using the same record definition. It is a lot of work but then I know
every program is using the same record definition.

In the interest of speed, it was decided not to recompile all the
programs since they will not use the new fields (the system is being
replaced in the next 2-3 years, unfortunately not using IDMS :-( ) The
part of the record being changed is defined as filler and is all spaces.
The new elements are all alphanumeric so I do not have to initialize
them. But how do I get the record to recognize the changed subordinate
element without going through schema and program compiles? I cannot
simply replace the record as it is in a schema and so is owned by the
schema compiler. Is there a way to get around this?

We are running V16.0 SP7.

Thanks for your help.

------------------------------ IMPORTANT NOTICE ---------------------------=
This email transmission and any accompanying attachments contain confidenti=
information intended only for the use of the individual or entity named abo=
Any dissemination, distribution, copying or action taken in reliance on the
contents of this email by anyone other than the intended recipient is stric=
prohibited. If you have received this email in error please immediately del=
it and notify sender at the above email address.
------------------------------ IMPORTANT NOTICE ---------------------------=
IDMS 3rd-party providers forum


Re: Replacing an element in a record
"Tommy's version of the events are bang on and are similar to what we routinely do.

More importantly this method allows you to preserve IDD statistics associated with the programs, schemas and subschemas. What we sometimes do is to associate the new subordinate element with the newly ""copied"" record to prove that the new format works.

Once the schema is associated with the ""copied"" record, you can now modify the original record with the new subordinate element. Then reassociate the schema with the original record (version 1). Validate the schema, regenerate the affected subschemas.

Given your situation, all that's left is to recompile the programs that need to exploit the new subordinate elements. All other programs can be left uncompiled/unmodified as they do not exploit the new subordinate elements.

Brian Lee
Pacific Blue Cross.