| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
A customer who runs ALL-IN-1 v2.4 has modified form MAIN, and it has
ended up in SITEMEMRES.FLB.
They have an earlier modification of form MAIN which is live in
SITEOAFORM.
They tell that they have used Customization Management and have not
inserted MAIN manually into SITEMEMRES with FMS commands.
1.
Why does ALL-IN-1 place form MAIN in SITEMEMRES and not in SITEOAFORM,
when the form gets moved to live area?
2.
How can we correct this?
Do we use FMS commands, extract MAIN from SITEMEMRES, insert the form
into SITEOAFORM, and delete MAIN in SITEMEMRES?
3.
Will this also have efect on future customizations, so that form MAIN
gets placed into the right form library if we make a new customization?
4.
Is there a pointer somewhere in a data file that tells ALL-IN-1 where
to place customizations of an element?
(In CM$SDC the disk location is OA$LIB_DANISH:OAFORM.FLB, and Customized
Area is OA$SITE_DEV_DANISH:DEVELOP.FLB).
Elin
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1334.1 | A mytrious update of .LIVE_DISK_LOCATION? | CESARE::EIJS | All in 1 Piece | Wed Sep 02 1992 12:02 | 51 |
Hi Elin,
> 1.
> Why does ALL-IN-1 place form MAIN in SITEMEMRES and not in SITEOAFORM,
> when the form gets moved to live area?
Possible reason:
Someone/Something updated the information in CM$SITELOG.
Question(s):
1) Is this the flow?
- ADE, COpy to Development
- MLA, which moved the form to SITEOAFORM
- E(dit), again MLA, which moved the form to SITEMEMRES
2) If so, then:
- Check the value for CM$SITELOG.LIVE_DISK_LOCATION[$CM_KEY] after the
customer selected form MAIN in the CM menu. Is it .....SITEMEMRES...?
- Did the customer install some package which updated form MAIN (and updated
CM$SITELOG)?
- Did the customer (by any chance) change the value for LIVE_DISK_LOCATION?
(I presume not)
> 2.
> How can we correct this?
> Do we use FMS commands, extract MAIN from SITEMEMRES, insert the form
> into SITEOAFORM, and delete MAIN in SITEMEMRES?
If the LIVE_DISK_LOCATION value is set to .....SITEMEMRES..., perform:
- RFL (Remove from Live area). The element will be back in Development
- WRITE CHANGE CM$SITELOG %KEY = $CM_KEY, LIVE_DISK_LOCATION = ""
- Move to Live. It should recalculate the Live location according to the
value in CM$SDC
- Check the live location via:
<GET CM$SITELOG.LIVE_DISK_LOCATION[$CM_KEY]
It should indicate ....SITEOAFORM.... If not, then there is a problem in
one of the CM procedures (which would be the first time for standard
MLA).
- Recomile the Site form libaries (espcially SITEMEMRES to get rid of
MAIN).
Ciao,
Simon
| |||||