| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 60.1 | Chapter 9 Views | DLO10::TARLING | | Wed May 08 1991 18:27 | 12 |
| Val Kristin;
1. Page 1-16a, I see no reason why a more complete definition of a
process could not be used (ie "The environment in which an image
executes").
2. The first 9 chapters look pretty good.
Also please note that my reply 58.2 should have been 59.1.
Arnold.
|
| 60.2 | The view from the UK | UKEDU::SHONE | Keith Shone @RKA 830-4074 | Fri May 10 1991 07:35 | 43 |
| Module: Customizing Your Working Environment
My views - not necessarily those of my colleagues.
Some of these comments I've made elsewhere - I think.
Flow and content is just right for me.
Page Comment
1-3 Para following fourth bullet: typos:
funtionally -> functionally
emply -> employ
1-12a A directory listing for future reference?
What's wrong with $ DIRECTORY /OUTPUT=filespec ?
1-13 The SHOW PROCESS command permits /OUTPUT so why
use a logical assignment?
Could try SHOW KEY - that's not got an /OUTPUT qualifier
or SHOW TIME?
1-16 Line 2: Better if it reads: "A command procedure..."
1-19a Bullet 2: sub-bullet 3: the product is VAX Notes not
VAXnotes - product managers get upset about these
things - especially where trade marks are involved!
1-26 last line: instead of main-level why not:
o Usually resides in SYS$LOGIN ?
1-27 Sub-head 5. bullet 1: substitute author for writer
1-28 I thought blank comments where: $! yet the sample
LOGIN.COM shows several blank lines without the
! character.
1-31 Similar comment as 1-28 above
|
| 60.3 | view of holland | NWGEDU::WIERSMA | Drive a BENTLEY or walk... | Tue May 14 1991 19:30 | 100 |
| Review chapter
CUSTOMIZING YOUR WORKING ENVIRONMENT
Page 1-4 TOPICS
I think it is a better way to teach the first three topics in reverse
order. Most of my collegues do. Because keypad definitons are easy to
make. A symbol is also very easy to understand, but logicals.
That is not so LOGIC. There fore we would like to see this order
changed.
Page 1-6: In the example I'm missing the following line after the two assign's
$SHOW LOGICAL TRAVEL,EQUIP
Page 1-10: $DEASSIGN/ALL doesn't cancel ALL your process logical names. Only
the ones you defined or assigned during this process.
Think also about process permanent logicals (blz 1-11 table 1-3)
Page 1-18: Where tell you something about deleting a symbol.
$DELETE/SYMBOL symbol name /LOCAL
/GLOBAL
/ALL
Page 1-20: example second line:
$DEFINE/KEY COMMA "RECALL/ALL" /TERMINATE change this line
into
$DEFINE/KEY/TERMINATE COMMA "RECALL/ERASE"
because /terminate is part of the define/key (qualifier)
Page 1-21 same
Page 1-23 same
Page 1-31 same
Page 1-26: Mention $HELP HINTS topic command-procedures.
Powerfull way for helping to create a command-procedure
Page 1-30: Last bullet, an other solution is
/COMMAND=ALT_LOGIN.COM a alternative login.com
Page 1-30a: Tell /NOCOMMAND is not allowed in captive and restricted accounts.
Page 1-31: Example of login.com needs a better layout and improvements.
Here it is.
$!
$! This is a login procedure
$!
$! Logical name assignments
$!
$ ASSIGN sys$login_device:[rounds.travel] travel
$ ASSIGN sys$login_device:[rounds.equipment] equipment
$!
$! logicals name assigments for using mail
$!
$ ASSIGN sloppy::piccadaci cp
$ ASSIGN sys$login_device:[rounds.lists]user_project.dis user
$ ASSIGN "bunnell,duffy,marsh,regnell,rounds" friends
$!
$! symbol definitions
$!
$ da :== DIRECTORY/DATE ! list creation date files
$ home :== SET DEFAULT sys$login ! set default top-level directory
$ whe*re :== SHOW DEFAULT ! display current directory
$ del*ete :== DELETE/LOG/CONFIRM ! change action DELETE command
$!
$! key definitions
$!
$ DEFINE/KEY/TERMINATE/NOLOG/NOECHO pf1 "SET TERMINAL/NONUMERIC"
$ DEFINE/KEY/TERMINATE/NOLOG/NOECHO pf2 "SHOW KEY/FULL/ALL" ! key definitions
$ DEFINE/KEY/TERMINATE/NOLOG/NOECHO comma "RECALL/ALL" ! recent commands
$ DEFINE/KEY/TERMINATE/NOLOG/NOECHO minus "SET DEFAULT [-]" ! up one level
$ DEFINE/KEY/TERMINATE/NOLOG/NOECHO pf4 "TYPE/PAGE nl:" ! clear screen
$!
$! change prompt
$!
$ SET PROMPT = "Ready> "
$!
$! end procedure
$!
$ EXIT
All the DCL commands are UPPERCASE. Because then you can check easyer on syntax
mistakes.
Blank lines are with --> $! <--
The use of TABS in an efficient way.
The same syntax on other lines are equal in layout.
I hope you like this first 8 chapter review. The rest is coming very soon. 2
more days to go.
Bye and see you all soon.
Arjen.
|
| 60.4 | Thanks! | SUPER::REGNELL | Modularity Maven | Tue May 14 1991 23:03 | 9 |
|
Thank you to everyone who is reviewing these chapters!
We will start putting the edits in next week and will post the revised
chapters as we get them done.
Really appreciate the time and energy, this helps us a lot!
Mel
|
| 60.5 | /user & refer to user manual | TEACH::CHUCK | | Sat Jun 01 1991 01:48 | 86 |
|
module 9: PAGE 1-13 I think it would be useful to
demo the /user qualifier here also. Both
concepts are important and useful.
Page 1-19 This would be a good place to
reference the user manual to see the chart
listing the keys that can be defined on
different terminals. Have them open to
DEFINE/KEY command. This will help to
get them to use that book.
Page 1-19 The second bullet is not totally
correct. You CAN define those keys without
enabling them. Then, you can later enable
them to USE them. I think this is important
because some users define the keys when
they log in, but do not "turn them on" until
they want to use them.
They are probably going to ask "can we have
1 key equal more than one command like the
editor does?" We may as well tell them
about /set_state and /if_state.
Page 1-26 Add to the first bullet "... or
the create command."
Add a bullet to the first group of 3
something like:
"A command procedure is nothing
more than a file that contains
DCL commands that you would like
to run as a unit."
In bullet 4 I would add:
"call other command procedures."
Last 2 bullets. Doesn't login.com have to
be called login.com and doesn't it have
to be in your ufd. If I am correct, remove
the word "usually" from these bullets.
In the last bullet, I would use "UFD" rather
than "main-level directory" to reinforce
the use of these terms.
Page 1-27.a What is pseudo-code?
Page 1-28 Bullet 3. To be a totally
correct statement, it may read:
"Precede comments with an
exclamation point. The comment
con be on a line by itself and
this line must start with a "$"
or it can follow another at the
end of a command line. (see ex.
1-14)."
Add bullet explaining how date does not
start with a dollar ($).
In bullet 7 it says "use blank comment lines ..."
but in example 1-14 they use just "$" and not
"$ !". Just the $ may work but I think proper
format should be "$ !". At least, let us be
consistent on the same page.
Page 1-30 The system manager can use lgicmd
to run a special login file for each user.
This is not that users login.com. If the
system manager does this, the users login.com
will not run unless the system manager adds
the command "@sys$login:login" to HIS command
procedure. This page is misleading. If left
as is, it implies that /nocommand, which is
there so the user can bypass his own login.com,
can bypass the command procedure the system
manager set up with lgicmd. It does not.
Page 1-31 In ex. 1-15 use "$ !" instead of
" $ " for blank lines.
|
| 60.6 | comments from DC Training Center | TEACH::WENDY | | Mon Jun 03 1991 13:19 | 16 |
|
Module 9
Customizing your working enviornment
1-5 .Logical name are stored in logical name tables
*(you should mention the 4 logical name tables)
1-6,1-7 Maybe tell them that these commands are putting logical names on the
process table.
*(we could maybe mention that their are 4 logical name tables
and that the course SYSNETII covers the other tables if it does)
Wendy Mullenhoff
|
| 60.7 | lev 0 local symbols use in command procedures | TEACH::CHUCK | | Wed Feb 26 1992 16:56 | 34 |
| Mel,
Mod 9 page 18- Third "-" under "a local symbol" is wrong.
You can use a local symbol created at the dcl prompt in a command
procedure. To prove this I wrote the following .com
ME.COM
$ show symbol me
$ my := This is a local symbol created at level 1
$ show symbol my
$ Show symbol/local/all
$ exit
Now at $ prompt create the symbol
me := I am a local symbol created at level 0
Then @me
The symbol is there. You can see it if you ask for it by name or
use it. You cannot see it if you do show symbol/local because
all you see is the local table at the level you are at.
Chuck
|
| 60.8 | Update to note 7 | TEACH::CHUCK | | Wed Feb 26 1992 17:07 | 8 |
| Add to the previous command procedure:
$ Write sys$output me
This will show you can indeed use it also.
Chuck
|
| 60.9 | ...working... | SUPER::REGNELL | Modularity Maven | Thu Feb 27 1992 18:52 | 14 |
|
Ouch...
Yup...seems to me that local symbols are available downwards...
just not upwards...[sigh]
I will go check to make sure we caught it in the TBI...I think
I remember having a tech reviewer point it out...but I will
make sure. And we will make the change in the next rev.
Thanks, Chuck.
Mel
|