| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 63.1 | | AWARD::MAGNI | Lois, 237-5548 | Wed Feb 01 1995 13:32 | 41 |
| Martin,
> o After the installation the TPAS logicals appear in the LNM$PROCESS_TABLE
> logical name table. After executing the TPAS$STARTUP.COM procedure, the
> TPAS logicals are also created in the LNM$TPAS logical name table. Why
> are the logicals required in both the LNM$PROCESS_TABLE and the TPAS$LNM
> logical name tables?
>
> o After executing the TPAS$REMOVE.COM procedure the TPAS logicals in the
> LNM$PROCESS_TABLE are not removed.
In the installation I create both the TPAS$XCLDD_DB and TPAS$NOR$DB.
As many sites installing TPAS V3 already have TPAS V2 up and
running, I did not want to overwrite their system logicals, if they
happen to be installing on the same node. So I execute the
TPAS_LOGICALS.COM to create the process logicals and let the site
decide when to execute the TPAS$STARTUP, creating the Logicals Name
table. Seeing these are process logicals, when the process that
has executed VMSINSTAL logs out, the process logicals go away.
> o During the installation the following DCL warning message appears:-
>
> >> %DCL-W-IVVERB, unrecognized command verb - check validity and spelling
> >> \
Can you run in K mode ? I do not get that error on either
machine I have tested the kit.
> o A minor point, the example program TPAS_DEMOSITE_BASIC.BAS provided in
> the [TPAS.DOC] area of the kit contains comment headings for a
> 'PROCEDURE DIVISION'. As far as I am aware, VAX BASIC does not support
> this feature! :-)
>
That's what happens when you flip between COBOL, BASIC, DECforms,
SQLMOD, SQL, DCL, DOCUMENT and English. At least you can look as
see where real code starts VS the data definitions !
Lois
|
| 63.2 | | MOEUR8::BROOK | | Thu Feb 02 1995 12:59 | 25 |
| Lois,
Thanks for the explanation around the V3.1 setting of the TPAS logical
names.
Regarding the DCL warning:-
> >> %DCL-W-IVVERB, unrecognized command verb - check validity and spelling
> >> \
>
> Can you run in K mode ? I do not get that error on either
> machine I have tested the kit.
If you mean by K mode, Kernel mode, I.e. having CMKRNL privilege then
the answer is Yes, I can run in K mode. In fact, I have tried installing
the kit with all privileges set and I still get the above warning.
After further investigation I discovered that the warning occurs when
I install the kit on our DECStep 6 platform but not when I install on
our DECStep 5 platform. Have you tried installing the kit on a DECStep 6
platform?
Regards
Martin Brook, BOPS Development
|
| 63.3 | INSTAL mode | AWARD::MAGNI | Lois, 237-5548 | Mon Feb 06 1995 09:03 | 14 |
| Martin,
By 'K' mode, I meant when you run INSTAL you can run it in different modes.
'K' is the developers tool that overrides the set noverify and gives youy
a play by play description of the action happening. Then you could see
exactly which line of code you are getting the %DCL warning on.
By DECStep 5, DECStep 6, do you mean the VMS level ? If so we still only
have VMS 5 although we are starting the plan to move forward. Our production
and development systems are a little slow to move forward.
Lois
|
| 63.4 | | MOEUR8::BROOK | | Wed Feb 15 1995 04:48 | 24 |
| Lois,
Just got back from a short break and read your reply.
> By 'K' mode, I meant when you run INSTAL you can run it in different modes.
> 'K' is the developers tool that overrides the set noverify and gives youy
> a play by play description of the action happening. Then you could see
> exactly which line of code you are getting the %DCL warning on.
Thanks, I didn't know that. I'll give it a try.
> By DECStep 5, DECStep 6, do you mean the VMS level ? If so we still only
> have VMS 5 although we are starting the plan to move forward. Our production
> and development systems are a little slow to move forward.
Yes. Many of our production BOPS systems are already running DECStep 6,
so when we fully implement TPAS II we would need a DECStep 6 compliant
kit. I believe the window for DECStep 6 migration of production systems
is Jan/Feb 95.
Regards
Martin Brook, BOPS Development
|
| 63.5 | in the states its call PASE | AWARD::MAGNI | Lois, 237-5548 | Wed Feb 15 1995 10:00 | 16 |
| Martin,
Thanks for the input. Our cluster has just started to look at VMS 6 and
all the layered products. Here in the states it is called PASE. Hard to
believe we all work for the same company sometimes.
Anyway, we are currently looking at the testing to be done to come up with
a schedule to move to VMS 6. As our development and production clusters have
many,many other systems I do not anticipate us moving for 3-4 months. In the
meantime, I hope you VMS 6 users can support each other (and me) as you run
TPAS. It has already been noted by Ayr that RMU has a problem with the ACLs.
The RMU LOAD and VERIFY commands are found in the TPAS*LOAD*.COM and
TPAS*IMPORT.COM streams. So you will have to adjust the database ACLs
accordingly.
Lois
|
| 63.6 | DCL Warning during installation | MOEUR6::BROOK | | Tue Feb 21 1995 06:35 | 134 |
| Lois,
I installed the TPAS II kit using 'K' mode as you suggested. I have
included extracts of the installation scripts for both MOEUR1 (DECstep 5)
and MOEUR6 (DECstep 6). It's worth noting that MOEUR1 is a cluster and
MOEUR6 isn't, so VMS install is using different procedural logic.
Regards
Martin Brook, BOPS Development
Start - DECstep 5 extract
********************************************************************************
$ if TST_CLUSTER .EQ. 0 THEN goto non_cluster
$ type sys$input
*****************************************************************************
*****************************************************************************
* *
* *
* Please add the following line into the *
* Please add the following line into the *
* SYS$COMMON:[SYSMGR]COMMON_STARTUP.COM : *
* SYS$COMMON:[SYSMGR]COMMON_STARTUP.COM : *
* *
* *
* >>@SYS$MANAGER:TPAS$STARTUP.COM<< *
* >>@SYS$MANAGER:TPAS$STARTUP.COM<< *
* *
* *
*****************************************************************************
*****************************************************************************
$!
$
$ RETURN 1
$!
$!++
$! Create the MAIL message that is to be sent back to us.
$! Create the MAIL message that is to be sent back to us.
$!--
$ VMI$CALLBACK SET POSTINSTALL
$! Copyright (c) 1992 Digital Equipment Corporation. All rights reserved.
$vmi_id = "V5-087"
$set nocontrol=y
$if f$type(vmi$installing) .eqs. "" then goto STEP_1
$vmi$save_verify = f$verify(vmi$debug)
$exit vmi$_success
$ gosub TPAS_SEND_MAIL
$TPAS_SEND_MAIL:
$!
$!++
$! Display a message to the user -- let them know what we are doing.
$!--
$ vmi$callback MESSAGE I CREATEMAIL -
"Creating/sending installation information to APPIX Organization."
$! Copyright (c) 1992 Digital Equipment Corporation. All rights reserved.
$vmi_id = "V5-087"
$set nocontrol=y
$if f$type(vmi$installing) .eqs. "" then goto STEP_1
$vmi$save_verify = f$verify(vmi$debug)
%TPAS-I-CREATEMAIL, Creating/sending installation information to APPIX Organiza.
$exit vmi$_success
********************************************************************************
DECstep 6 extract
********************************************************************************
$ if TST_CLUSTER .EQ. 0 THEN goto non_cluster
$ non_cluster:
$ type sys$input
*****************************************************************************
*****************************************************************************
* *
* *
* Please add the following line into the *
* Please add the following line into the *
* SYS$MANAGER:SYSSTARTUP.COM *
* SYS$MANAGER:SYSSTARTUP.COM *
* *
* *
* >>@SYS$MANAGER:TPAS$STARTUP.COM<< *
* >>@SYS$MANAGER:TPAS$STARTUP.COM<< *
* *
* *
*****************************************************************************
*****************************************************************************
$!
$!
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
\
\
$!
$!++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
$!
$! TPAS_SET_ACLS
$! Set the ACLs and Owners if the files and directories.
$!
$!----------------------------------------------------------------------------
$TPAS_SET_ACLS:
$!
$ sodx_acl = -
"((IDENTIFIER=TPAS$SUPPORT,option=default,ACCESS=READ+WRITE+DELETE+" + -
"EXECUTE+CONTROL)," + -
"(IDENTIFIER=TPAS$DB_OWNER,option=default,ACCESS=READ+EXECUTE)," + -
"(IDENTIFIER=TPAS$DB_READ,option=default,ACCESS=READ+EXECUTE)," + -
"(IDENTIFIER=TPAS_XCLDD$DB_WRITE,option=default,ACCESS=READ+EXECUTE)," + -
"(IDENTIFIER=[*,*],option=default,ACCESS=NONE))"
$!
.
.
.
********************************************************************************
|
| 63.7 | DCL Warning during installation | MOEUR8::BROOK | | Tue Feb 21 1995 12:15 | 10 |
| Lois,
The DCL warning is caused by a form feed character embedded in the data
of your KITINSTAL.COM when doing a 'type sys$input'. I can now see that
the warning has nothing to do with DECstep5/DECstep6. It will always
occur when the kit is installed on a non-clustered machine.
Regards
Martin Brook, BOPS Development
|