| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 74.1 | Chapter 1 draft available for review | SUPER::WTHOMAS | | Wed May 29 1991 11:19 | 10 |
| A draft of the first Sysnet II chapter entitled:
Preparing Data To Use In A Command Procedure
is available for review in:
SUPER::ES$REVIEW:[SYSNET_II]SYSNETII_CHAP1.PS
Wendy
|
| 74.2 | UK: looks OK for this level | DUCK::SHONEK | Keith Shone UK Edu 830-4074 | Mon Jun 03 1991 05:38 | 12 |
| Review comments on the chapter:
Preparing Data To Use In A Command Procedure
The content and technical level is OK.
One specific observation:
Page Comment
---- -------
1-7 /EXCLUDE qualifier states "...you can omit the
parentheses." but none is shown.
|
| 74.3 | no COMMAND PROCEDURE ties here | TEACH::CHUCK | | Fri Jun 07 1991 00:17 | 9 |
| SYSNET II- MODULE I
This is module 10 from utilities & commands II minus
the Set File command. I just taught it to day and the students
loved the content. I do not however think this title is proper.
Call it "Advanced DCL commands" or something like that. There is
no connection with these commands and command procedures. At
least take the words "command procedures" out of the title. Once
having done that, we can add the Set File which is very useful.
|
| 74.4 | Good point...I will talk to Wendy... | SUPER::REGNELL | Modularity Maven | Mon Jun 10 1991 16:52 | 21 |
|
Chuck,
The chapter can be renamed for SYSNET II if that is appropriate,
and SET FILE could be added.
Wanted to explain that the course this comes from (USER II) is
an introduction to writing command procedures and the chapters are
set up to follow a single process through to a final complete
command procedure. So, although from the view fo SYSNET II, these
command may have nothing to do with command procedures, in the
course they ccame from...it made sense to teach it that way.
I will take this to Wendy (The developer for SYSNET II) and see
if we can re-work the version of the chapter for this course
so it more closely reflects the SYSNET audience.
Thanks
Mel
|
| 74.5 | comments from D.C. | TEACH::RINE | | Wed Jun 12 1991 16:29 | 13 |
| The following are comments on Module 1 of SYSNET II
Page 1-3 2nd Paragraph's end sentence should end with something like
"Characters in columns 12 through 20"
Page 1-5 should probably say something about where we will display
by defulat sys$output.
Page 1-12 Why would we use /process
Page 1-16 Example should be in larger print
Page 1-17 Example should be in larger print
|
| 74.6 | review from Holland | NWGEDU::WIERSMA | Drive a BENTLEY or walk... | Thu Jun 13 1991 10:58 | 34 |
| Review of chapter:
PREPARING DATA TO USE IN A COMMAND PROCEDURE
(just read: HANDLING DATA IN A COMMAND PROCEDURE) <----- !!!!!
1-3: line 7: for example,......
for example, that the characters, in columns 12 through 20, are a
phone number
1-7: /EXCLUDE=file-spec[,...] must be /EXCLUDE=(file-spec[,...])
1-13: just kidding
Rob DeMaat his real name is Rob de Maat.
And he is living next to me in HOLLAND!!!!!!
Reaktion to: re 74.5.
Please keep the examples this way. Everybody has to look very good to them. So
nobody will mis understood them.
And for an explanation of page 1-12: cannot use /process.
MERGE opeartion are only allowed on sorted files. See further page 1-11a
Perhaps we can put this line (cannot /process...) to the instructor page 1-12a.
So far the review.
I like the idea to put the SET FILE in here as well.
Bye Arjen.
|
| 74.7 | | SUPER::WTHOMAS | | Thu Jun 20 1991 17:27 | 7 |
|
The two week time period for reviews is over.
Any comments entered after this note will be considered, time
permitting.
Wendy
|
| 74.8 | Capitol Ideas | TEACH::LYNN | | Fri Jun 28 1991 13:02 | 41 |
|
Preparing Data To Use In a Command Precedure
Chapter 1
Great - the objectives truly match the topics and also what is
taught for this chapter.
Nice to see the objectives and the topics on the same page in
order to save paper.
1-7 A few examples would be nice for the student to see.
If possible include more information for the /MATCH
qualifier.
1-7a I am unclear what is being said at the last bullet.
1-8 In the general format line is it possible to include the
/qualifier? This is also a thought for on page 1-7.
1-11 For the /STATISTICS qualifier it says "specifies that a
statistical summary" is displayed. What statistics are
displayed. Maybe you can write additional information
or better yet include an example coming from the system.
1-12 If the files were not sorted without the /CHECK_SEQUENCE
qualifier it still displays the same error message
- input out of order -
So why is this qualifier really needed?
1-15 I am not clear what is being said for the /IGNORE qualifier.
Maybe an example for how it is used.
Would it be possible to list the defaults for the following
qualifiers? /NUMBER /MATCH=size
1-16 Maybe a note on the instructors page about the /MERGED=1 that
is displayed from the system.
Lynn White
Washington D.C.
|
| 74.9 | Response to comments | SUPER::MATTHEWS | | Fri Jul 19 1991 18:32 | 11 |
| I think the revised draft answers all but a couple of issues:
SET FILE has been added to the module on disk management.
>1-8 In the general format line is it possible to include the
> /qualifier? This is also a thought for on page 1-7.
We are following the format used in the HELP output and in the DCL
dictionary. Since practically every command has qualifiers, we don't need
to keep saying that they do.
|
| 74.10 | First teach post mortem | MELKOR::SWIERKOWSKIS | | Mon Jan 20 1992 11:41 | 52 |
| This reply is limited to technical errors only. I'll refrain from making
comments one way or the other about content, style, etc....
Module 11 (Developing Command Procedures) in SYSNET II
p. 11-8 Please change "thing" to "token" at the bottom of the page
in the notes on bubble 2. (Let's use correct terminology
whenerver possible.)
"Because TUESDAY is the first thing on the command line after
the name of the command procedure, it becomes the value of P1."
Should read: "Because TUESDAY is the first token ....
p. 11-10 In the execution of REPORT3.COM at the bottom of the page,
we have no reason to see the first line of display, and the
second line of display will not contain the word TUESDAY.
$ @REPORT
Day to print a report for: TUESDAY ! There is no INQUIRE or
! READ/PROMPT in the
! command procedure.
Day to print report for: TUESDAY ! We do not pass in a
! P1 parameter when
! invoking the command
! procedure (we typed
! @REPORT instead of
! @REPORT TUESDAY).
Either change the command procedure example to include an
INQUIRE or READ/PROMPT command to prompt for the day of the
week, or change the execution example to @REPORT3 TUESDAY and
remove the first line of display.
p. 11-34 We should include an F$GETDVI example here as the last lexical
function. It's critical for system managers who write backup
command procedures that do destructive things like INIT a disk
to check for things like VOLNAM first. I know I said I would
stick to errors, but I lied! We had a disaster here in
Santa Clara years ago (and the instructor is still infamous)
in which a backup procedure wiped out the wrong disk. I'm
sure our customers would appreciate hints to prevent this from
happening to them.... (I know it's in the appendix, but by
12:00 on Friday no one will stay for "optional" material.)
Susan
|
| 74.11 | command procedures | TEACH::CHUCK | | Mon Mar 23 1992 17:10 | 45 |
| 1. the command procedures on page 11-8 and 11-10 do the same thing
in the same way. There are no new items on page 10. Just typo's.
I think the thought behind page 10 was to show the inquire command.
It does not have it. It is also early. Lets drop this page or
fix it and move it after the Inquire is taught.
If it is to remain as is the typo's are:
at the bottom add TUESDAY behind @reports
Drop the next line. There is no way for it to get there.
On page 11-16 At bullit 3- There is only 1 space before Fred Apon.
Bullit 3 & 6- Between Fred & Apon there should be
multiple spaces to show how the commands handle
it.
Bullit 6- There should be no spaces between name and
Fred Apon. Read does not supply them and Fred
did not type them because they are not in Bullit
7.
For lexicals- lets start with symple lexicals. F$mode()
and F$time(). The maybe f$locate, f$extract and
F$length and how we can use these three togeather. Then
f$enviornment() to geather information.
One last comment. All of the material in the Appendix is great
material. I would like to have this is a chapter in itself somewhere
in the string. It is too good to be just am appendix. Sure we
can teach it, but there already is too much in the course. There
is no place to fit it.
Chuck
Page 11-40 The /symbol qualifier is not needed here.
It may be valid but who cares.
|
| 74.12 | Advanced DCL should live! | MELKOR::SWIERKOWSKIS | | Mon Mar 23 1992 20:07 | 16 |
| > One last comment. All of the material in the Appendix is great
> material. I would like to have this is a chapter in itself somewhere
> in the string. It is too good to be just am appendix. Sure we
> can teach it, but there already is too much in the course. There
> is no place to fit it.
>
> Chuck
Boy do I ever agree with Chuck on this one!!!!!!!! We had a great course that
covered this material and I hate to see it die. Possibly we could rename
U & C II back to Advanced VMS Features and continue to offer it as an
alternative to people who want/need more than just a "cookbook." Or, maybe
we could come up with a three day class and call it Writing DCL Command
Procedures.
Susan
|