[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | USG buildhelp questions/answers |
|
| Moderator: | SMURF::FILTER |
|
| Created: | Mon Apr 26 1993 |
| Last Modified: | Mon Jan 20 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2763 |
| Total number of notes: | 5802 |
1743.0. "pascal PTT -DIR /OUTPUT=enter_note.txt .LAST" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Mon Aug 21 1995 16:30
Date Of Receipt: 21-AUG-1995 15:00:53.17
From: SMURF::FLUME::"[email protected]"
To: odestaff@DEC:.zko.flume, flume::odehelp
CC:
Subj: pascal PTT --
PTT came in on merge info in history and using
pascal. See info below.
Just wanted to let you know, that I gave a reply with
a workaround, by setting in a custom file the following:
setenv save_ancestor_info FALSE
Tina
********************************************************************************
Action Problem Last
Number Status Status Prior Owner PRODUCT Flags Age Updated
====== ====== ====== ===== ===== ======= ===== === =======
ODE-00459 AK UN 1 ODE_ZSO ODE 0 21-AUG-1995
DEC -ODE 3.0's bmerge cannot deal with Pascal files.
(internal number: 00459)
Submitted by: MICHAEL RICKABAUGH of USG-ZK in USA
(DTN 381-2966 )
Mail address: RUST::"[email protected]"
Last accessed on: 21-AUG-1995 11:53 Number of days open: 0
(RC: 0.0 AK: 0.0 SB: 0.0 EL: 0.0 CL: 0.0)
Time spent in problem status: < >
Problem first entered on 21-AUG-1995
Summary last modified on 21-AUG-1995
PRODUCT: ODE
OS HARDWARE: UNIX/ALPHA 214
COMPONENT: BMERGE
OTHER:
Hardware: alpha DEC3000_500 System device:
Memory:
Abstract: ODE 3.0's bmerge cannot deal with Pascal files.
Customer company: DEC
[This update was sent from RUST::"[email protected]" on 21-AUG-1995 11:
[ODE responsible for next action, Problem is undefined]
Mail this report to: [email protected], mjr, [email protected]
Note: ALL CAPS=Mandatory field
Problem Submission Form Mon Aug 21 14:18:59 EDT 1995
Required Information
====================
YOUR NAME: Michael Rickabaugh
Your Email address: [email protected]
YOUR PHONE NUMBER: DTN 381-2966
Your FAX number: dtn 381-2257
Your company name: Digital
Your mailstop: ZKO3-3
YOUR ORGANIZATION'S NAME: USG-ZK
YOUR COST CENTER: t33
Your street address: Digital Equipment Corporation
OSF/1 UNIX Engineering
110 Spit Brook Rd.
Nashua, NH 03062
--------------------------------------
CUSTOMER'S COMPANY NAME: DEC
CUSTOMER COUNTRY: USA
--------------------------------------
PRODUCT: ODE
Product version (optional): V3.0
OS HARDWARE: UNIX/ALPHA
OS Hardware version: 214
Workstation soft version (optional): V3.2
COMPONENT: BMERGE
Component version (optional): DECodeIIv3_0bf:V-3.390:Prod-ver--V3.0
Other (optional):
OTHER Version (optional):
SYSTEM WHERE PROBLEM OCCURRED: schnausser.zk3.dec.com
CPU type: alpha DEC3000_500
Display type: 1 display of type=14
Memory size:
System disk:
Other hardware configuration information:
Other software configuration information:
DEC OSF/1 V3.2 (Rev. 214); Mon May 1 10:18:19 EDT 1995
DEC OSF/1 V3.2 Worksystem Software (Rev. 214)
--------------------------------------
PROBLEM ABSTRACT (80 characters or less):
ODE 3.0's bmerge cannot deal with Pascal files.
PROBLEM PRIORITY (1-5, 1 being most critical): 1
CAN THE CUSTOMER REPRODUCE THE PROBLEM [Y/N]: Y
CAN YOU REPRODUCE THE PROBLEM [Y/N]: Y
PROBLEM STATEMENT:
=================
When you do the 'bmerge' step on a file, bmerge now
inserts this at the top:
{
@DEC_COPYRIGHT@
HISTORY
{** Merge Information **}
{** Command used: bmerge **}
{** Ancestor revision: 4.2.19.7 **}
{** Merge revision: 4.2.19.9 **}
{** End **}
$Log: as1cobj.p,v $
...
This merge information was not there prior to ODE V3.0.
The problem is that this assumes that Pascal allows
comments to nest--it does not. How do I permanent turn this
off without going to ODE V2.0?
upas: Error: ../../../../../../src/usr/ccs/bin/as/as1cobj.p, line 10: outermost
level:
$Log: as1cobj.p,v $
-mike
Instructions to reproduce the problem:
======================================
--------------------------------------
DECode II product specific information:
====================================
WORKON=1
SANDBOX=as1_bss
BCSSET=
BCSPORT=549
BCSDIRECTORY=/usr/sde/ode3.0
BCSHEADERS=/usr/sde/osf1/headers
PRINCIPAL=Mike_Rickabaugh
EDITOR=emacs
PATH=.:~/b.alpha:/usr/staff/mjr/sand/as1_bss/tools/alpha/hostbin:/usr/staff/mjr/
sand/as1_bss/tools/alpha/bin:/usr/staff/mjr/sand/as1_bss/tools/alpha/acc:/usr/sd
e/osf1/build/ptos.nightly/tools/alpha_OSF1/alpha/hostbin:/usr/sde/osf1/build/pto
s.nightly/tools
Results from currentsb -all:
============================
as1_bss Mike_Rickabaugh_as1_bss /usr/staff/mjr/sand . /usr/staff/mjr/sand/as1_bs
s/rc_files/local /share/cia/build/ptos.dsk6/ptos.nightly0
Results from check_ode:
=======================
Check_ode for DECode II V3.0 -- $Revision: 1.1.4.31 $
Mon Aug 21 14:19:09 EDT 1995
Using logfile=tmp11529.logfile
Info -- Checking Client: schnausser.zk3.dec.com
Info -- schnausser.zk3.dec.com: DECode II client Load=0
Info -- Checking nfs locks on schnausser.zk3.dec.com
Info -- Checking sandbox: /usr/staff/mjr/sand/as1_bss
Info -- Checking network to a kerberos server kerberos1.zk3.dec.com.
Info -- Node schnausser.zk3.dec.com to kerberos1.zk3.dec.com
latency 5 ms, packet loss 0%.
Info -- Checking network secondary kerberos server kerberos2.zk3.dec.com.
Error No. 1 ---------- Mon Aug 21 14:20:01 EDT 1995
Can not ping from schnausser.zk3.dec.com to kerberos2.zk3.dec.com
Info -- Time diff schnausser.zk3.dec.com - kerberos1.zk3.dec.com is 61922 ms
.
Info -- Checking network connection to the rcs_host
Info -- Node schnausser.zk3.dec.com to buffer.zk3.dec.com
latency 3 ms, packet loss 0%.
Info -- Checking network connection to the submit_host
Info -- Node schnausser.zk3.dec.com to secret.zk3.dec.com
latency 3 ms, packet loss 0%.
Client/sandbox error count is 1
<<<<<<<<<<<<<<<<<<<<<<<PTT UNIT SEPARATION>>>>>>>>>>>>>>>>>>>>>>
[This update was sent from ODE_ZSO on 21-AUG-1995 11:53]
[ODE responsible for next action, Problem is undefined]
vi rc_files/custom
include local
setenv save_ancestor_info FALSE
save_ancestor_info
The setting of save_ancestor_info rc variable to TRUE, at a project
level, will enable the user to record in the history log, the command
name, bmerge, with [-j] or [-r] option, followed by the ancestor and
the merge versions of the file being merged and requiring user's
intervention. To set a value for save_ancestor_infor follow the for-
mat of variable_name value e.g. an entry would look like the follow-
ing:
save_ancestor_info TRUE
This feature can be disabled by setting the rc variable,
save_ancestor_info, to FALSE. (see below an example of a changed his-
tory log )
| T.R | Title | User | Personal
Name | Date | Lines
|
|---|