Re: Convert Page

Discussion created by ca.portal.admin on Jan 4, 2008
On Thu, 3 Jan 2008 16:58:51 -0700, Mike Baker <mikebaker345@HOTMAIL.COM>

We have been doing some Convert Page's recently, and have some more to
do soon. In the Utility manual, it says;

""If an area that is being converted has a cross-area set or linked
constraint, then you must convert all areas touched by the set or link.
You must determine what files are affected, and therefore what files
must be converted.""

We got burnt by this in Test, as in one of our Convert Page jobs,
several Areas/Files were accidently omitted, and it was not noticed
until a User was trying to navigate the database, and it just said,
""Read Error'. It was subsequently backed out and re-done correctly.

What I want to know, and would appreciate feedback on, is if this
happened in production, and we (for eg.) converted Areas ""A"", ""B"", and
""C"". But only later (to late to back anything out) we discovered that
we should have also included Area ""D"" in the Convert Page job, how
would we fix this?? Would an OBTAIN, DELETE, and STORE (of the obtained
record) of all the records in Area ""D"" fix the problem??

Thank you.
Correction... I guess that we'd need to do an Unload/Reload.

Would this fix the corrupt Page Numbers/Database Keys??

IDMS Public Discussion Forum


Re: Convert Page
Similar to Mike's suggestion, I just omit the DD(s) for the database
file(s). The job abends but still produces the area depenencies.

Joe S Cates, Database Analyst II
Systems Architecture and Operations
Database Management/Unix Administration
Montgomery County Public Schools
Rockville, MD 20850