| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 77.1 | Chapter 4 draft available for review | SUPER::WTHOMAS | | Wed May 29 1991 14:22 | 9 |
| A draft of the fourth Sysnet II chapter entitled:
Using Logical Names and Symbols in Command Procedures
is available for review in:
SUPER::ES$REVIEW:[SYSNET_II]SYSNETII_CHAP4.PS
Wendy
|
| 77.2 | UK: looks OK | DUCK::SHONEK | Keith Shone UK Edu 830-4074 | Mon Jun 03 1991 06:18 | 30 |
| Review comments on the chapter:
Using Logical Names and Symbols in Command Procedures
Page Comment
---- -------
1-3 End line 4: too many "you may have"
Four lines from end: type - altar -> alter
Three lines from end: typo tramslation -> translation
1-9a Four lines from end: "...which accesses files on
different again disks;..." - doesn't make sense
1-13 Line 6: typo - reprt -> report
1-15a Penultimate line: typo - conversation -> conversion
unless we intend to shout!)
1-15 Line 8: procedures -> procedure
1-17 Final line of table: wrap the dollar signs to precede the
commands
1-19 I got confused with the final bullet - Foreign commands.
I thought that the purpose of this sort of definition was
to enable an _image_ to collect command line arguments.
The C language supports this feature as standard but
other languages must call LIB$GET_FOREIGN. In other
words its for images not command procedures.
|
| 77.3 | Comments from DC Training Center | TEACH::WENDY | | Wed Jun 05 1991 15:44 | 72 |
|
Module 4
Logical names and Symbols
1-10 The course fails to go over what a process and job logical
name table are. SYSNETI never addressed this either. The table is good for
telling them what each name is used for, but not what process
and job logical names are used for.
1-13 second paragraph there is a typo- reprt should be report.
Also in your example after
$DEASSIGN MYFILE.LIS
maybe add the command
$TYPE MYFILE.LIS
so they can see how the redirected output is accessable.
1-14
Never explained job logical names.
Also no where has the group logical name table been mentioned or addressed
in any detail and then its mentioned all the sudden here.Maybe put a table
in here
Process Job Group SYStem
Who can use Breif description
the logical:
How to set up: $assign $assign/job etc.
To See: $show log/job/all etc.
$show log/job logical-name
To delete: $deassign $deassign/job etc.
That way they can see very clearly the commands to put a logical on each
table, how to see each table etc.
1-15
When you log into a VMS system you are at what is called DCL command level.
*(I would mention that this is command level 0, the highest command level.)
If the command procedure that you run in turn, runs another command
procedures, then yet it creates another command level. *(bad sentence, typo
after procedure(s).
The structure is not unlike an outline...
*(Maybe draw a structure on the page with one command procedure
calling another, and show dcl level as command level 0, and the first
procedure you execute as command level 1, and it calls another
procedure to create command level 2.
1-18
This is a very good example and I like how it is enlarged-because
its not in the current sysmgtII course.
1-19
.Parameters to command procedure
Here you are talking about p1 and p2 but the course has not addressed
parameters yet. They won't know what you are talking about.
The same with setting up a foreign command. Parameters arent until the next
chapter, Designing Command Procedures. If you leave these examples in the course
maybe put a note that these are discussed in the next chapter.
|
| 77.4 | comments from D.C. | TEACH::RINE | | Wed Jun 12 1991 16:30 | 20 |
| The following are comments on Module 4 of SYSNET II
GENERAL Symbols and translation shold be in module 3 with symbols
should mention in here somewhere about define maybe include
define in wone of the examples just to show that it can be
used also.
I think the tables and their durations should be mentioned
near the beginning of the module not the end.
Page 1-14 Should list on the instructor page the idea of a job.
Page 1-14 Job could be a detached process that starts up some
subprocesses of is own. In this case the job table would
stay around untl the last process in the job tree exits
Page 1-18 #4 looks like level -1 (Should be command level 1)
Page 1-18 #8 looks like level -2 (Should be command level 2)
|
| 77.5 | review from Holland | NWGEDU::WIERSMA | Drive a BENTLEY or walk... | Fri Jun 14 1991 05:40 | 59 |
| Review of chapter:
USING LOGICAL NAMES AND SYMBOLS IN COMMAND PROCEDURES
Page 1-6: the line above .... the following output:...
you forgot the dollar sign before the command
show translation start ---> $ show translation start
Page 1-9a: fourth line from the bottom.
for users on different disks to use which accesses files ?????
better way of saying this
for users to use, which accesses files on different disks.
Page 1-9: I love this one.
System Message %DCL-I-TIDYSEDE, .......
----
|
+---- I believe this is SUPER.
And this is not the node name SUPER.
Page 1-10: I agree with Wendy (re 77.3). Let's tell them something about
Process and Job logical name table.
May be we can take something out of the Utilities and Command I
course. Chapter 6. Page 6/7 will do. The figure number is
TTB_X0333_88_S
Page 1-13: Example: $DEASSIGN MYFILE.LIS
$DEASSIGN SYS$OUTPUT
Page 1-16: third dot:
Are created with a single equal sign (=)
AND :=
sixth dot: The same
please mention also :==
This is for the instructor page 1-16a
I explain this always as follows.
a = "Hello" draw a circle around the quotation marks
so you have two circles.
put the circles in front of the equal sign
and then you get
a := Hello
And they never forget it.
Page 1-18: This is a better layout then I've ever see before.
Thanx.
Wendy it is in the sysmgtII course aswell. Page 1-13. Only worse
layout.
So far See you in topic 78,
Arjen.
|
| 77.6 | | SUPER::WTHOMAS | | Thu Jun 20 1991 17:32 | 7 |
|
The two week time period for reviews is over.
Any comments entered after this note will be considered, time
permitting.
Wendy
|
| 77.7 | Capitol Ideas | TEACH::LYNN | | Sat Jul 06 1991 10:22 | 41 |
| Using Logical Names and Symbols in Command Procedures
Chapter 4
Introduction - Fourth line remove the "have"
Last paragraph, Second sentence "altar" should be "alter"
1-9 Good page. Clearly shows the difference.
1-11 Under the equivalence name for SYS$SHARE
Should you use the word "shareable"? I can't find it in the
dictionary and it really doesn't sound right. Maybe change the
phrase to read: Device and directory name of system images that
are shared.
1-13 Second sentence has "the results are" should be "result is" I think.
Second paragraph second line has a typo "reprt" should be "report".
Then you have "To that" maybe should be "to do that
Add an example of showing ASSIGN/USER_MODE
$ASSIGN/USER_MODE MYFILE.LIS SYS$OUTPUT
1-15a Maybe define a process-private.
1-15 Last sentence in the second paragraph is very confusing.
Maybe use "If the command procedure you run invokes another
command procedure then it creates another command level.
1-18 GREAT EXAMPLE!!! The only thing I have a problem with is the minus.
1-19a Very good including what a foreign command is for the instructor.
You may want to add a note that the "$" is needed as part of the
syntax when you define a foreign symbol.
1-19 Item two - You may want to add an example showing the incrementation.
COUNT=COUNT+1
Leave more space between elements in the command line
[email protected] DATA.DAT DATA_DONE.DAT
Lynn White
Washington D.C.
|
| 77.8 | Response to comments | SUPER::MATTHEWS | | Fri Jul 19 1991 18:43 | 18 |
| >1-11 Under the equivalence name for SYS$SHARE
> Should you use the word "shareable"? I can't find it in the
> dictionary and it really doesn't sound right. Maybe change the
> phrase to read: Device and directory name of system images that
> are shared.
(This is now in module 1A) The DCL Concepts manual describes the job,
group, & system tables as shareable, rather than the names themselves, so I
reworded the instructor notes accordingly. We still use the word
"shareable" but we're consistent with the documentation (which uses
the word "shareable" in several different contexts).
>(Maybe draw a structure on the page with one command procedure
>calling another, and show dcl level as command level 0, and the first
>procedure you execute as command level 1, and it calls another
>procedure to create command level 2.
Didn't have time to do this; will keep it in mind for next pass.
|