| A draft of this module is available for review in:
SUPER::ES$REVIEW:[RA0293]RA0293_CHAP_7_PROFILE.PS
It needs more examples, which I will continue to add as I find them.
Your contributions will be greatly appreciated.
Question:
Does passing parameters (P1-P8) belong in a course of this level,
or should it be in the more advanced command procedures course?
|
| A few more comments and some suggestions for additions/clarification.
Once again, I couldn't resist picking a few nits.
This module flows fine so far as I'm concerned.
Page Observation
---- -----------
1-8 The final bullet says to use an EXIT command then
the example immediately below doesn't use an
EXIT command! I know don't do as I do, do as I say!
1-14 Do you think we should include a real display showing
output from these commands?
1-18 Bullet 2: performs -> perform
Bullet 3: "...you may want a file to print..." - this
phrase makes amusing reading! How about:
"...you may want to print a file..."?
(let's hope that files are ever able to print themselves!)
1-19a Heading Labels appears twice - I think I see why
but it looks odd.
Bullet 1: first sub-bullet - label must be the first
item on a command line AFTER THE $
1-19 Example 1-2 - forgot that EXIT command again...!
1-21 Do we need a note here to place " " around strings
with spaces between words? E.G.
$ @REPORT YEAR_END PRINT
but...
$ @REPORT "YEAR END" PRINT
1-24a Perhaps a note on this page to remind us that the
/NOCOMMAND qualifier to Username input won't
work for captive accounts? (There shouldn't
be anything in a captive LOGIN.COM to generate
errors but...)
1-28 We might also include /NOPRINTER and /KEEP
in an effort to save paper.
-- Keith
|
| Hi Kristin,
I think writing command procedures doesn't belong in the course VMS for
application users. This students are application users, so they have to
know how to log in, a lot af DCL commands, directory structure,
communication with other users, getting HELP, creating and editing text
and data files, working with files, setting up a terminal, make
sure to be a secure user.
This is enough theory to tell in three day and also enough for an
application user to know.
Ed Janssen.
|