| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 23.1 | draft ready for review | HARDY::BUNNELL | | Mon Dec 10 1990 12:28 | 5 |
| A draft of this module is available for review in:
super::es$review:[ra0294]ra0294_chap_4_profile.ps
Hannah
|
| 23.2 | Reading, UK - first pass | UKEDU::SHONE | Keith Shone @RKA 830-4074 | Thu Dec 13 1990 10:32 | 39 |
| I found the flow of this chapter OK.
My nits, typos and other observations are below.
NOTE: These are my feelings etc. not of the UK as a whole.
I comment on typos etc on instructor pages as well as customer pages.
Instructors deserve to have unambiguous, correctly spelled and
technically accurate information too! :-)
Instructors will need to be careful delivering this session. Lists of
information don't always make exciting listening, especially first
thing after lunch!
Some text missing, especially in introductory pages.
Not sure that escape sequences are best placed in this chapter.
Page Observation
---- -----------
1-11 No Figure 1-1
1-14a Line 4: Typo: F$SETPRIV -> F$SETPRV
1-14 Last line: Typo: TMPRMBX -> TMPMBX
1-18 No Figure 1-2
1-24 Bullet 6: Example: PHRASE should be preceded by a dollar
sign as it's an assignment. The call to F$FAO doesn't
work anyway! There should be four spaces between "IS and
"HUMAN" too! Correct version is
$ PHRASE = F$FAO ("TO !#(#AS)", 3, 6, A, B, C)
$ SHO SYMBOL PHRASE
PHRASE = "TO ERR IS HUMAN "
Shouldn't we find a new example rather than stealing one
from the VMS HELP Library ;-)
|
| 23.3 | Appendix? | SUPER::REGNELL | Smile!--Payback is a MOTHER! | Thu Dec 13 1990 18:21 | 16 |
|
Keith,
Much of the lexical function listings were placed in an
appendix for V5.4 of SYSMAN II...we could do the same here,
but it makes the chapter very slim.
What do you think?
It removes the possibility that some instructors will try to talk
their way through the entire listings...
Just a thought?
Mel
|
| 23.4 | %ME-W-NOTCRE, Not being creative | UKEDU::SHONE | Keith Shone @RKA 830-4074 | Fri Dec 14 1990 09:11 | 18 |
| Hum.....
I guess what I'm trying to say is - this is probably the way I'd have
done it and I don't like myself for doing it this way!
I've tried to be creative - note, tried - and wasn't successful.
What I would like to have is a guide to getting information out of VMS.
For example I need information about working sets, so where do I look?
One answer would be lexical function, another would be SHOW WORKING_SET
and so on. But that doesn't solve the present problem of a list.
I could deliver from this chapter OK. It has been grouped functionally
and the demos are short and to the point.
Perhaps someone else out there has some ideas? (nudge nudge wink wink...)
Keith
|
| 23.5 | What we need is... | SUPER::REGNELL | Smile!--Payback is a MOTHER! | Fri Dec 14 1990 11:20 | 21 |
|
Well,
What I would like to see is this whole two-day session
as a hands-on experience developing a series of dcl
command procedures that do a series of 'tasks'...and
introduce the different topics as an outcome of needing
to do a specific task.
My problem is that I can't seem to come up with a believable
series of tasks to hang it on. So, we are stuck with this kind
of presentation.
If someone could come up with a really believable series of tasks
or problems ot solev that we could structure these two days
around I would jump for it.
Any takers?
M_
|