| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 65.1 | A return to the BAD old days? | NITTY::THORNE | Department of Redundancy Department | Wed Apr 24 1991 10:47 | 9 |
| While I only have the ESDP Course Specification to go by right now, I
couldn't help but notice a reference to the BAD utility in the section
on 'Preparing Volumes for Use'. Are we returning to the compatibility
mode utility days? I also wonder at the section on 'Transferring Files
Between VAX and PDP-11 Systems. There's probably a lot more interest
in the details involved in transferring files to/from ULTRIX systems or
to/from PCs than to PDP-11s.
Mark Thorne
|
| 65.2 | UK - a view from the east bank | UKEDU::SHONE | Keith Shone @RKA 830-4074 | Tue May 14 1991 04:03 | 43 |
| Module: Working With Queues
My views - not necessarily those of my colleagues.
This review amounts to a proof reading exercise with a
word by word sanity/sense check. I have limited technical
expertise on queues and their management.
Page Comment
1-6a Last line: typo courses -> course
1-6 Bullet 1: sub-bullet 2: ona -> on a
Bullet 2: sub-bullet 3: typo anyt -> any
Batch and Output Queues, line 1: second instance of
queues should not be italicised?
1-7 Penultimate line of Starting a Print Queue:
"When you start the the first..." should be:
"When you start the first..."
1-9 Sub-head 4. the VAX DOCUMENT non-tag <code-example>!
Sub-head 6 refers to "The second command is..." where is
the second command?
1-11 English query: last line:
"(none are automatically created)." is strictly, in
long form, -
"(not one are automatically created)." which doesn't
make sense. Please try:
"(none is automatically created)."
1-13a <Nit> Bullet 3: the SHOW ENTRY command WAS new not IS new
1-16a There's an inconsistency through this page when it refers
to pages when I believe it means blocks. A symbiont
can't know from a file size how many pages a file contains.
|
| 65.3 | view of holland | NWGEDU::WIERSMA | Drive a BENTLEY or walk... | Mon May 20 1991 18:37 | 38 |
| Review of chapter
WORKING WITH QUEUES
Page 1-6: last bullet:
Missing line - Print jobs are created by the PRINT command
Page 1-8a: last line
$INIT/Que etc (TTA1:,TTC7:) device names have a colon!
Page 1-8: same remark.
Page 1-9: LPA0 is a device name colon must be adjusted.
Number 6: Second command ????
Page 1-10 and 1-10a device names need a colon.
Page 1-14: queue name LPA0 and LPB) needs a colon.
Page 1-16a: Qualfier /BLOCK_SIZE is checking on blocks and not to pages. Not
even if your blocksize equals pagesize is 512 bytes. Then still
your physical pages can be different from your blocksize.
To check this use the following command:
$ACCOUNT/TYPE=PRINT/REPORT=PAGES/SUMMARY
|
+--- there is the confusing one
Page 1-16: Colon needed by the device names.
Page 1-19: Setting Job Attributes
Adjusment DELETE/ENTRY ----> DELETE/ENTRY=
So far this chapter.
Doei Arjen.
|
| 65.4 | | GOONS::BAKER | What does "ignorant" mean? | Wed May 22 1991 11:43 | 110 |
|
Here are some more review comments for Ch 14, Working with Queues. I feel the
content is about right, but wouldn't be too upset to see the "creating" part
disappear. We are assuming that "support" will be available to the student when
back at work.
Some info could be dropped, eg. 1-13 - Job Status codes. To mention these
really needs a discussion of all sort of command qualifiers (/HOLD /AFTER etc).
I think this chapter should allow students to (just) manage the queues that
they'll have - basically Operator functions rather than Sys Mgr functions. The
advanced stuff should be covered on the next course.
Stephen
----------------------------------------------------------------------------
1-4 RESOURCES. The sentence "To complete..." implies that the manuals
are needed, or else the student won't be able to acheive the
objectives. There may be cases where these manuals are
unavailable during the course. I suggest removing the sentence
and just listing relevant books (as with earlier chapters).
1-5 2nd bull Cluster start command implies a directory [SYSQUE] exists.
If JBCSYSQUE.DAT is located in SYS$COMMON:[SYSEXE] then no
file name is necessary for the START/QUEUE/MANA command.
1-6a The note Nit: Suggest last word, last sentence be changed to "nodes"
last sent Typos: Capital E for Ethernet, "courses" = "course"
1-6 1st bull, 2nd item Suggest "..execution ona..." becomes "..execution
queues on a.."
"Batch and Output Queues" section
1st line Italicized "queues"
1sr bull, 3rd item Suggest "Runs" = "Run" and "detached" = "batch"
or "detached (batch)"
2nd bull, 2nd item Suggest removing "to control the printer" from the
end. The symbiont's job is describes in the next
item.
1-7 Table Use of /FORM=WIDE in example. This would be a site-specific
feature. The text (sort of) implies that this would be
available on any system.
1-8a/8 P1-7a says that creating queues will be covered on a later
course. 1-8 and 1-8a now give commands on how to do this!
If "creating" is to be kept in this course, then the info on
1-8 is somewhat redundant. Some of it is duplicated on 1-9.
If 1-8 is kept, then the /xxx lines need to be indented.
Also, SET TERM /EDIT and /INSERT don;t seem relevant to printer
attributes.
1-9 entry 1 Typo: "selects" = "select"
entry 2 Suggest removing "or terminal" from text or adding a SET TERM
example as well.
entry 4 <code-example>
entry 5 SHOW QUEUE/ALL/DEVICE gives *every* queue (except batch) on
my system. Incl terminal, printer, server, generic - not just
execution queues.
entry6 No second command.
1-12a Table Has a reference table 1-4. This means that the student pages
jump from Table 1-3 to 1-5. Will this happen on the "student
book" build?
"Stopping" and "Stopped" entries. Suggest adding "/" before
REQUEUE and RESET.
1-12 Example We've already had example 1-2. I think this should be 1-3.
1-13a SHOW ENTRY arg is [entry-number] not [queue-name]
4th bull Suggest "SHOW ENTRY was new with VMS Version 5". Actually
this is three years old now. Is it worth highlighting these
"new" features?
1-13 Sent preceding table. "Queue" should be "Job" And Table 1-5 should
(possibly) be 1-4 (see above)
1-14 SHOW QUEUE/DEV/GENERIC command only lists generic queues on my
system, not printer and terminal queues.
1-15a Two missing <REFERENCE>s
1-16a Confuses block size and number of pages.
1-16 Example Query whether the PRINT command is required here.
1st para Talks about print job priority. Have to be careful here.
Students could confuse job priority with process priority and
with /BASE_PRIO of queue. All are different.
1-18 Table Orderly shutdown entry.
You don't need to stop a queue to move jobs from it (unless
the job's already active I suppose).
Immediate Shutdown entry
The text says that "..you have complete control.." A nit, but
a Sys Mgr has "complete control" even without stopping the
queue.
1-19 Summary. Table entry entitled "Creating...deleting queues". The text
didn't mention deleting and (sort of, maybe) mentioned
creating. The INIT command isn't in the summary.
Entry "Setting Job attributes" The PRINT and DELETE/ENTRY
commands don't really set job attributes.
|
| 65.5 | queue names and uses of them | TEACH::CHUCK | | Sat Jun 01 1991 02:02 | 27 |
| module 14: Page 1-6 You cannot just skip logical
queues because batch does not have them.
Just say "logical queue" explain it and
say "for printers only.
Also why call hardware queues "output queues"?
Why not hardware, device or printer?
Page 1-7 The names SYS$PRINT & SYS$BATCH should
be reserved for generic queues only.
Page 1-7.a Says creating queues will be covered
in a later course. Then starting on page 1-8
& running to page 1-11 we create queues.
Page 1-9 SYS$PRINT is being used to name a
execution queue. Please don't do this. It
causes problems for the students in understanding
the normally accepted use of the name as a
generic queue. Please, Please, Please!!!!!
Page 1-9 # 6, last sentence makes no sense.
What second command???
Page 1-11 SYS$BATCH used as execution queue
again. If we are going to teach that SYS$PRINT
& SYS$BATCH are generic queues lets be consistent.
|
| 65.7 | comments from DC Training Center | TEACH::WENDY | | Wed Jun 05 1991 09:50 | 49 |
|
Module 14
Working with Queues
Why not rename the module to WORKING WITH PRINT AND BATCH QUEUES
1-3 INTRODUCTION- maybe say as a system manager you are responsible for
setting up print and batch queues, you make it sound as they have to set up
all queues.
1-4 Creating a queue *(Maybe say print and batch)
Controlling queues *(Print and batch)
1-5.Start/Queue/Manager device:[sysque]jbcsysque.dat
This forces all nodes to access the same queue manager and queue list.
*(maybe mention that all nodes in the cluster would have to issue
this same command)
1-6 In a vaxcluster, jobs are directed to *(an execution queue on a) specific
node
1-9 1. $show device L
Lists the devices and selects one. *(how does this select one?)
4.
<code example> *(is this supposed to be there?)
1-10 3. This queue will recieve default print jobs and dispense them to any
execution print queues that do not use the /NOENABLE_GENERIC qualifier
*(at the time the execution queue is set up.)
4. $Initialize/Queue/Start/Generic=(LPA0,LPB0) sys$print
*(maybe take out the name LPB0 so they see how to direct traffic to
just one of the exection queues that you set up in step 2.
The last sentecnce on this page makes no sense to me.
1-19 Delete/Entry *(you mention this, but you never talked about this command
in the chapter, isnt it Delete/entry=)
Wendy Mullenhoff
|
| 65.8 | Capitol Ideas | TEACH::LYNN | | Sun Jul 07 1991 00:30 | 28 |
| Working With Queues
Chapter 14
Objectives: I am a bet confused. You have "create a queue" YET on page 1-7a
it states creation of queues will be covered in a later course YET
on page 1-8 they include the sequence for creating a print queue.
Please straighten this out.
1-8 You have in parentheses "see documentation." What documentation
do you mean. You can bet the students will ask this question.
1-9 You are creating and using an execution queue. Step 4 uses
SYS$PRINT that is not an execution but a generic queue.
Follow through on Step 6 with a better example that uses the
/QUEUE qualifier.
Also Step 6 talks about the "first and second command" but there
is only a single command example.
Summary You have listed $SET ENTRY and $DELETE/ENRTRY but they are not
mentioned in the module so how can it be a summary?
Overall When you do batch queues how about an example other than
SYS$BATCH. Just a suggestion.
Lynn White
Washington D.C.
|