T.R | Title | User | Personal Name | Date | Lines |
---|
89.1 | CART can report them, for a start... | CESARE::EIJS | All in 1 Piece | Tue Feb 25 1992 08:28 | 16 |
|
Hi Sunil,
Thanks for the support of using CM. If only all...
Anyway, with V3.0 comes CART, the Conflict analysis and
reporting/resolution tool. When run from the ALL-IN-1 V3.0
installation, it will generate a report on elements which are found the
Site areas (Both live and development) which don't have an entry in
CM$SITELOG. This could be of help identifying these 'undocumented'
customizations. Also, CM offers an option Reveive from VMS, which will
copy an element from VMS and include it into the CM environment.
Thanks,
Simon
|
89.2 | Modifications to Digital area | UTRTSC::BOSMAN | We're just sugar mice in the rain | Tue Feb 25 1992 08:58 | 7 |
| Hi,
Simon, that's nice. But what happens when they customized Digital
elements in the Digital area?? Does the CART recognizes that kind of
modifications?? (using CHECKSUM or something else).
Sjaak.
|
89.3 | Scanning | SIOG::T_REDMOND | Thoughts of an Idle Mind | Tue Feb 25 1992 09:19 | 19 |
| CART depends utterly on the contents of CM$SITELOG to be able to
recognize customized elements. If people have customized base elements
without going through CM (for example, by editing a script directly in
OA$DO_SHARE:), then all bets are off and CART will not be able to scan
the edited elements for conflicts with ALL-IN-1 V3.0.
A VAX SCAN program is used by CART when it checks elements registered
in CM. This program looks at the contents of scripts, command
procedures, boilerplates, and form named data for references to
obsolete messages and other base components that have been changed in
V3.0.
The site elements report is merely a list of files that have been
detected in the site directory structure and are not registered in CM.
The intention is that people review the report and import those
elements into CM and then rerun the CART. If they choose not to do this
then that's their problem.
Tony
|
89.4 | I hit HELP by accident and ... | AIMTEC::WICKS_A | Vote Bill'n'Opus for a weirder USA | Tue Feb 25 1992 20:07 | 9 |
| A little off the main topic I know but ... it is kind of related to
finding out about how to practice safe CM+.
has anyone pressed the HELP key whilst on the CM menu?
(BL122D of course)
Regards,
Andrew.D.Wicks
|
89.5 | Is there any help for CM+ ? | IOSG::STANDAGE | Oink...Oink...Mooooooooooooooooooooooooooooooooo | Tue Feb 25 1992 22:15 | 14 |
|
Andy,
I remember hearing Mike (which isn't difficult) screaming when he did
this not too long ago...but I can't remember exactly the message he got
back !!
Ho-hum,
Kevin.
~~~~~~
|
89.6 | Yes there is help | IOSG::BILSBOROUGH | Just testing. Please ignore!!! | Wed Feb 26 1992 09:42 | 10 |
|
Ok, I shall say this quietly.
YES there is help. But only as an application maintainer and
application manager. There is NO help as a CM programmer as there
wasn't enough resource to do it.
Andrew, were you trying to press HELP somewhere else?
Mike
|
89.7 | One .HLP into the kit? | AIMTEC::WICKS_A | Vote Bill'n'Opus for a weirder USA | Wed Feb 26 1992 16:23 | 20 |
| Dear Kev/Mike,
No I like many customers was pressing the HELP key at the CM$MAIN menu
and was surprised at the results. If I were a customer I would
immediately pick up the phone and dial 1-800-dec-8000.
Of course as nobody took out the help for CM1, CM2, CM3 you can use
CM ABE, Copy them to the development area, Merge them together, edit
them a little and then copy them to a new SITE element called CM$MAIN
Make that live and then there is HELP for CM. That took me about an hour
- someone competent could do it much quicker i'm sure.
Can nothing be done about this? I would have thought it was really
embarrassing for us all - surely there is still time left in the
schedule for this?
Regards,
Andrew.D.Wicks
|
89.8 | Sorry - not in the DIAMOND schedule.... | SIOG::T_REDMOND | Thoughts of an Idle Mind | Wed Feb 26 1992 16:49 | 6 |
| No, there is no more time left in the schedule to do this. The help for
CM1 etc is obsolete (and we will remove it), but it's not really valid
for CM$MAIN. It doesn't cater for the context-senstive menu options,
for instance. I agree, however, that any help is better than none.
Tony
|