Hi All:
We are planning to upgrade to remedy V4. We started with change management
application which is running on V 3.2.1.
What we did, we build a test server running V4 and imported all schemas and
the related stuff (AL, etc..) from production server to the test server
which is running V4. Then, I started to rename the schemas, filters, active
links, and menus. After that, I did some change on the workflow of the main
schema of change management to get rid of scrolling by using the new feature
in V4 (paging or tabbing). Notice that I didn't delete or modify any label
names, only I added some boxes and move field from place to place without
using cut and paste. When I checked the active links and filters, I found
that some of the filed name in (Run If & If Action) is changed to another
filed name.
To resolve this problem I selected the most difficult way which is comparing
all field names all active links and filters on the test machine to the. I
experienced a tedious job and headache.
Please, I am interested to share any information regarding schema renaming.
Best Regards.
Suwaie Mohammed
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:ARSLIST@LISTSERV.ACSU.BUFFALO.EDU] On Behalf Of John Gerzsenyi
Sent: Saturday, January 30, 1999 12:16 AM
To: ARSLIST@LISTSERV.ACSU.BUFFALO.EDU
Subject: [Fwd: The perils of renaming a schema.]
<< Message: Re: The perils of renaming a schema. (2.58 KB) >>
janos@us.ibm.com wrote:
>
> Peter,
>
> regarding the schema rename operation I did some tests. I started
with
> a fresh (AR 3.2.1)
> copy of our application. First, I exported out ALL definitions into before
> image files. The most interesting
> was the active links with embedded macros looked like:
> action {
> macro-name : Staff:UpdateBDPrincipal
> macro-text : Set-schema: Staff
> $%$
> Query:
>
> 101=$Nome$
> 536870916=$Met$
>
>
> Modify-bulk:
> 620000000=0
>
> end
>
> macro-parms : 1\%\$-6$
> macro-parms : 3\Met\$750000020$
> }
>
> Notice the Staff schema name in the middle of macro code. Second brave
step
> was to rename Staff schema to "XZYABC"
> by admin tool. (See AdminGuide, Vol 1, page 6-10)
>
> Then, I exported out ALL definitions into after image files. When I did a
> diff by an NT tool (NOT ardiff), I got diffs like:
> before image===>
> set-field :
> 0\536870917\102\1\@\5\Staff\1\536870942\4\1\99\536870913\1\536870916\2\3\
> set-field :
> 1\536870918\102\1\@\5\Staff\1\536870927\4\1\99\536870913\1\536870916\2\3\
> set-field :
> 2\536870919\102\1\@\5\Staff\1\536870928\4\1\99\536870913\1\536870916\2\3\
> schema-name : Staff
> schema-name : Staff
> schema-name : Staff
> after image ===>
> set-field :
> 0\536870917\102\1\@\6\XYZABC\1\536870942\4\1\99\536870913\1\536870916\2\3\
> set-field :
> 1\536870918\102\1\@\6\XYZABC\1\536870927\4\1\99\536870913\1\536870916\2\3\
> set-field :
> 2\536870919\102\1\@\6\XYZABC\1\536870928\4\1\99\536870913\1\536870916\2\3\
> schema-name : XYZABC
> schema-name : XYZABC
> schema-name : XYZABC
>
> Hurray ! It showed that the schema name got updated inside the macro in
all
> places.
> Then, I peeked into my ORACLE DB and I noticed the same thing:
>
> DCSWO:TechSetComunicado Staff:UpdateBDPrincipal Set-schema: XYZABC
> $%$
> Query:
> 101=$Nome$
> 536870916=$Met$
>
> Modify-bulk:
> 620000000=0
> end
>
> The bottom line: we can safely rename schemas which is VERY important for
> internationalization.
>
> Regards,
> John Gerzsenyi
> janos@us.ibm.com
> Senior Software Engineer
> IBM/US Telecommunications & Media ISU
> Voice: (919) 301-3625 T/L: 352-3625 Fax: (919) 301-3833
>
> P.S. Upon request I can e-mail bmp files showing more details.
>
>
>
See my test results above.
--
John Gerzsenyi
(a.k.a. Janos)
janos@us.ibm.com
(919)301-3625 T/L 352 FAX 919-301-3833
IBM/US Telecommunications & Media ISU
Bldg. 678, Dept. DWIA/45, Office BB228
1001 Winstead Drive, Cary, NC 27513-2116
Previous Topic
Index