| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 153.1 | Proposed outline for SysNet 1 | DBLDOG::DONHAM | Progress Through Tradition | Mon Jul 20 1992 15:54 | 280 |
| Mission statement for SYSNET I:
Perform day to day system management of an established system
participating in a
Chapter 1: Understanding the System Management Environment
Objectives:
In order to understand the system management environment,
a system and network manager student should be able to:
- Identify the responsibilities of a system manager
- Describe basic VMS system terminology
- Explain the basics concepts of a network
- Explain the basics concepts of a cluster
- Identify directories on a system disk
- Classify VMS processes
----------------------------------------------------------------------
1. Understanding the System Management Environment
- Responsibilities of the system manager
- Basic terminology
What does VAX mean?
What does VMS mean?
Hardware
VAX vs uVAX
System components
CPU classes
Software
DCL
Utilities
Systems
Standalone vs cluster
- VMS processes
What are they?
Process types
- Intro to networking
What is a network
Network Products
- Intro to Clusters
What is a cluster
Cluster processes
Cluster aliases
- Directories on the SYSTEM disk
Rooted directories
SYS$SPECIFIC vs SYS$COMMON (logical name table)
Chapter 2: Managing Users
In order to manage system users, a system and network manager student
should be able to:
- Understand the uses of the AUTHORIZE utility
- List the user accounts on a system
- Add a user account to the system
- Remove a user account from the system
- Monitor Disk space
- Manage and monitor user processes
- Identify and solve common user problems
----------------------------------------------------------------------
2. Managing Users
- Using the AUTHORIZE utility
UIC values
Privileges
- Listing user accounts on a system
- Adding a user account to the system
Adding the account
Creating the default directory
Entering disk quota
- Removing a user account from the system
Disabling the account
Deleting the default directory tree
Removing disk quota
- Modifying a user account
- Monitoring disk space
- Managing and monitoring user processes
Using SHOW SYSTEM
Using SHOW USER
Using SHOW PROCESS
Stopping user processes with STOP/ID
- Solving common user problems
Chapter 3: Maintaining Queues
In order to maintain queues, a system and network manager student
should be able to:
- Identify the different types of queues
- Start a queue
- Stop a queue
- Manage and monitor queue usage
----------------------------------------------------------------------
3. Maintaining Queues
- Review of queues
Generic
Execution
Priorities
Printer/Server/Terminal
- Starting a queue
- Stopping a queue
- Managing and monitoring queue usage
Using the SHOW QUEUE command
Manipulating entries
With SET ENTRY
With ASSIGN/MERGE
Manipulating queues with SET QUEUE
Chapter 4: Backing Up Files and Disks
In order to back up files and disks, a system and network manager
student should be able to:
- Identify reasons to back up files and disks
- Explain back ups to users
- Back up a set of files
- List a saveset
- Restore files from a saveset
- Back up a disk volume
- Restore a disk volume
----------------------------------------------------------------------
4. Backing Up Files and Disks
- Reasons to back up files and disks
- Explaining backups to users
- Backing up a set of files
- Listing a saveset
- Restoring files from a saveset
- Backing up disk volumes
Incremental
Full disk
- Restoring a disk volume
Chapter 5: Shutting Down and Starting Up a VMS System
In order to shut down and start up a VMS system, the system and network
manager student should be able to:
- Explain why system shutdowns and startups are used
- Shut down a system
- Explain the differences between CCL and DCL
- Start up a system
- Examine network status
----------------------------------------------------------------------
5. Shutting Down and Starting Up a VMS System
- Understanding when to shut down a system
- Shutting down a system
Using SHUTDOWN.COM
Understanding quorum issues
Using OPCCRASH
- Using console command language vs DCL
- Starting up a system
Using the BOOT command
- Examining network status
Using SHOW NET
- Enabling boot service for satellite nodes
|
| 153.2 | Some comments based on IPF | TEACH::SHERRY | Sherry Butler - DTN 341-2289 | Tue Jul 28 1992 00:00 | 333 |
|
My comments/additions/deletions are lines starting with > or |
-Sherry
--------------------------------------------------------------------------
Mission statement for SYSNET I:
Perform day to day system management of an established system
participating in a
> participating in a cluster/network.
Chapter 1: Understanding the System Management Environment
Objectives:
In order to understand the system management environment,
a system and network manager student should be able to:
- Identify the responsibilities of a system manager
> - Identify the responsibilities of a system and network manager
- Describe basic VMS system terminology
- Describe basic VMS and system terminology
- Explain the basics concepts of a network
- Explain the basics concepts of a cluster
- Identify directories on a system disk
- Classify VMS processes
----------------------------------------------------------------------
1. Understanding the System Management Environment
- Responsibilities of the system manager
> - Responsibilities of the system and network manager
- Basic terminology
What does VAX mean?
What does VMS mean?
Hardware
VAX vs uVAX
System components
CPU classes
Software
DCL
Utilities
Systems
Standalone vs cluster
> Standalone vs cluster vs network
> Multiprocessor (add)
> Vector Processor (add)
- VMS processes
What are they?
Process types
- Intro to networking
What is a network
Network Products
- Intro to Clusters
What is a cluster
Cluster processes
Cluster aliases
- Directories on the SYSTEM disk
Rooted directories
SYS$SPECIFIC vs SYS$COMMON (logical name table)
Chapter 2: Managing Users
In order to manage system users, a system and network manager student
should be able to:
- Understand the uses of the AUTHORIZE utility
> This won't really be the case for this chapter. All the uses will
> be mentioned. But, only manipulating the user account will be taught.
- List the user accounts on a system
- Add a user account to the system
- Remove a user account from the system
- Monitor Disk space
- Manage and monitor user processes
- Identify and solve common user problems
> - Identify common problems managing user accounts
> This was going to be a 'page of common errors' when adding a user-
> like getting a rightslist message. It was not going to talk about
> solving all the problems at this point.
----------------------------------------------------------------------
2. Managing Users
- Using the AUTHORIZE utility
UIC values
Privileges
- Listing user accounts on a system
- Adding a user account to the system
Adding the account
Creating the default directory
Entering disk quota
- Removing a user account from the system
Disabling the account
Deleting the default directory tree
Removing disk quota
- Modifying a user account
- Monitoring disk space
- Managing and monitoring user processes
Using SHOW SYSTEM
Using SHOW USER
Using SHOW PROCESS
Stopping user processes with STOP/ID
- Solving common user problems
Chapter 3: Maintaining Queues
In order to maintain queues, a system and network manager student
should be able to:
- Identify the different types of queues
- Start a queue
- Stop a queue
- Manage and monitor queue usage
----------------------------------------------------------------------
3. Maintaining Queues
- Review of queues
Generic
Execution
Priorities
> Priorities of Jobs
Printer/Server/Terminal
- Starting a queue
- Stopping a queue
- Managing and monitoring queue usage
Using the SHOW QUEUE command
Manipulating entries
With SET ENTRY
With ASSIGN/MERGE
Manipulating queues with SET QUEUE
Chapter 4: Backing Up Files and Disks
> Chapter 4: Backing Up Files and Volumes
In order to back up files and disks, a system and network manager
> In order to back up files and volumes,a system and network manager
student should be able to:
- Identify reasons to back up files and disks
> - Identify reasons to back up files and volumes
- Explain back ups to users
> - Explain backups to users
- Back up a set of files
- List a saveset
- Restore files from a saveset
- Back up a disk volume
> - Back up a disk volume in or out of a cluster
- Restore a disk volume
> - Restore a disk volume in or out of a cluster
----------------------------------------------------------------------
4. Backing Up Files and Disks
> 4. Backing Up Files and Volumes
- Reasons to back up files and disks
> - Reasons to back up files and volumes
- Explaining backups to users
> - Explaining backup procedures (schedule) to users
- Backing up a set of files
- Listing a saveset
- Restoring files from a saveset
- Backing up disk volumes
Incremental
Full disk
- Restoring a disk volume
Chapter 5: Shutting Down and Starting Up a VMS System
> Chapter 5: Shutting Down and Starting Up a VMS System and Network
In order to shut down and start up a VMS system, the system and network
manager student should be able to:
> In order to shut down and start up a VMS system and network, the
> system and network manager student should be able to:
- Explain why system shutdowns and startups are used
- Shut down a system
- Explain the differences between CCL and DCL
- Start up a system
- Examine network status
> (add) - Shut down the network
> (add) - Start the network
----------------------------------------------------------------------
5. Shutting Down and Starting Up a VMS System
> 5. Shutting Down and Starting Up a VMS System and Network
- Understanding when to shut down a system
- Shutting down a system
Using SHUTDOWN.COM
> (add) Specifying nodes to be notified of shutdown
Understanding quorum issues
Using OPCCRASH
> (delete) Using OPCCRASH
> This should be in SYSNET II
- Using console command language vs DCL
- Starting up a system
Using the BOOT command
- Examining network status
Using SHOW NET
> Using NCP SHOW NETWORK
- Enabling boot service for satellite nodes
> (delete) - Enabling boot service for satellite nodes
> This should be in SYSNET II
> (add) - Shutting down a network
>
> Using NCP .......
>
> - Starting up a network
>
> Using STARTNET.COM
|
| 153.3 | | DBLDOG::DONHAM | Progress Through Tradition | Tue Jul 28 1992 10:58 | 12 |
| > - Enabling boot service for satellite nodes
>> (delete) - Enabling boot service for satellite nodes
>> This should be in SYSNET II
My opinion:
When the student goes home and tries to boot a satellite, s/he needs to know
why the machine isn't booting (if service is disabled) and how to fix
the problem.
P
|
| 153.4 | Our remarks on the proposed outline | BRSTR3::MEERSMAN | All kids on dec | Wed Jul 29 1992 06:29 | 44 |
| Hi,
After reading this proposal, we would like to make the following remarks:
* chapter 1: - basic terminology, should be known by then...
- network products; do they include PATHWORKS products ?
- cluster processes = potential rathole ?
- rooted directories; too early to use this word; just introduce
all SYS$* logicals
* chapter 2: - Authorize needs more topics (like /flags, because an account is
created with disuser, etc...); Good guided exercises covering
most of the common errors beginning system managers make...
Also captive accounts should be mentioned; quite a lot of VAX
users seem to be captive...
- Privileges: fine in the context of authorize; we think there should
also have a separate topic on privileges and keep it as a kind
of "apotheosis" for the course. [You learned now some valuable
skills which need privileges to execute; but beware exercising
these privileges in other situations...they could be dangerous}
* chapter 3: - We'd like to see this topic merged with the chapter about "working
with files that introduces the print (+ submit ?) command in the
VMS Skills for users course (which we combine into 1 course)
- forms should be mentioned too; forms are one of the most common
troubles for beginning system managers.
* chapter 4: - Much better than in the old sysnet ! Hopefully backed up by good
exercises.
* chapter 5: - quorum issues could be a rathole...,
- this chapter should be kept short ("established system shouln't
have trouble in booting/shutting down)
- if we examine network status, why not the queue manager, pcsa,
rdb, dfs,...?
- enabling boot service should not be covered here (established
system)
Many regards,
Mia Dobbeni
Chris Klein
Christian Meersman
|
| 153.5 | Colo Spgs Comments | TEACH::SHERRY | Sherry Butler - (301)743-7160 | Thu Jul 30 1992 20:30 | 24 |
| This is from part of a mail message I received from Rich Vogel.
Mod 1:
Systems - has Standalone vs Cluster
Many be good to add in vs Network too.
Mod 2:
UIC values - may be best to insure that UIC protection
is covered here too. It becomes important when
setting up the users disk directory.
Mod 5:
Using the Console - may want to talk about the differences
between systems with and without a Console Subsystem.
Like when you need to use BOOT58>
Starting up the system - insure Roots are covered.
I'm sure once I start working with the material things will come up but
that will be a few months away for me. Right now when I look over the
outlines, I get locked on to the flow and it's difficult to see what might
be missing.
All and all it looks good and I'm looking forward to working with SYSNET.
Rich Vogel
NEURON::VOGEL
|
| 153.6 | Common problems | DBLDOG::DONHAM | Progress Through Tradition | Mon Aug 03 1992 16:03 | 16 |
|
I need some input on two topics:
1. What are the most common errors a new system manager
will encounter when trying to add a new user account?
2. What are the most common mistakes a new system manager
will make in managing a system?
Please include a solution to each problem...
Thanks!
Perry
|
| 153.7 | MY LAST 2-CENTS | DLO10::SAYERS | | Fri Aug 07 1992 12:02 | 73 |
| Perry,
In answer to your questions:
1. The first error a system manager would encounter while trying to
add a new user account is, in my opinion, that a disuser flag had not
been removed from the DEFAULT account and thus, the new account had a
disuser flag and the new person could not log in.
Here are some more:
- The system manager did not do a proper search of the UIC codes and
ended up assigning the same UIC that had previously been assigned
to another user.
- Same with last name....they have typed in all of the qualifiers only
to find out that the last name is a duplicate.
- They did not specify a /device= and the user ended up with
the device from the DEFAULT account.
- They do not have enough privileges to run authorize.
- They did not set default to SYS$SYSTEM or SYSUAF logical has not
been defined. Thus asking the user if they want to create a new
sysuaf.dat file.
- The system manager tried to use an 8 or 9 in the UIC group and/or
member field of the UIC. Octal only!!!!
2. What are the comman mistakes a new system manager will make in
managing a system?
- Giving too many privileges.
- Running only from the system account and not knowing what the
privileges actually do and what you need the privileges for (since you
have all of them, "things" happen and sometimes they don't know why).
- Setting MAXPROCESSCNT OR BALSETCNT too high, too low, or incorrectly
with relationship to the -2 offset.
- Not educating the users on $dir/size. Thus compromising the disk
space allocations.
- Assigning logical names, creating queues, etc. without putting
them in the startup command procedures, thus, when the system is
shutdown, queues and logical names are lost.
- IMPORTANT!!!!! (Alot of my system managers were NOT aware of this)
Being made aware of files that may grow and become very large, thus
using up much needed disk space. Examples: Accountng.dat,
operator.log, errorlog.sys
Hope these help. I would be willing to help you our more but today is
my last day. I got the TFSO package. I enjoyed working with you while
I was at the IPF. Just when I know the difference between a chapter
and a module, and a task and a non-task, I get the boot!!! :*)
Seriously, I would be happy to work with you on a consultant basis if
it is possible. The plus to this is, you could have my attention
full-time. What a concept, huh?
All the best to you. Good luck in developing this course. I was
saying just yesterday that we need a ERROR page for setting up accounts
through authorize and also for DISKQUOTA's.
Regards,
Dee Sayers
Dallas
|
| 153.8 | more | TEACH::CHUCK | and I am UNANIMOUS in that. | Fri Aug 14 1992 14:12 | 11 |
| I haven't learned the difference between task and non-task yet but
I have an addition to mistakes in adding users.
When setting up the disk for the user account they forget
to make the user the owner of his directory. Also they forget
at times, when adding diskquota, to use /device=.
Comment: It is sad to see someone who has added so much to this
conference/company as Dee has be let go!!!
|
| 153.9 | Managing Users chapter | SUPER::ROUNDS | Kristin Rounds | Tue Sep 08 1992 16:11 | 18 |
| The "Managing System Users" chapter is ready for review.
It is located in:
SUPER::ES$REVIEW:[SYSNET_I]MANAGE_USERS.PS
In addition to general review comments, please consider:
- Suggestions for filling the holes on pages 3.a, 13.a,
21.a, 38.a and 38.
- The lab exercises. We welcome your contributions,
particularly to the exercises on setting version limits
and monitoring disk space.
- Adding instructor notes wherever you think they are
appropriate.
Thanks for your help in making this a better course!
|
| 153.10 | Feedback on module 1, chapter 1 | NEURON::STAHLY | 10$: BRB 10$ | Mon Sep 21 1992 18:40 | 164 |
|
RE: Review of SYSNET I Module 1 Ron Stahly - Sept 21, 1992
Page 1-12.a and 1.12
Adding the UAF Record
The account will also have the flag DISUSER as it will inherit
this FLAG from the DEFAULT account(unless this flag has been
cleared from the UAF record for the DEFAULT account.
I suggest adding the qualifier /FLAG=NODISUSER to the student
page and additionally discuss this on the instructor Notes page.
Page 1-13.a Disk Quotas
You asked for feedback on: How much can we "overbook" a disk ?
In theory as much as you like, however users tend to get angry
if the disk becomes full and they have quota remaining.
In practice, you should NOT overbook a disk. There should be
enough free space so all users may use their quota fully.
In addition, there should be enough space so they may use
their allowed overdraft as well.
Discuss what the QUOTA and OVERDRAFT values allow either on
the student or instructor pages.
Page 1-14.a and 1.14 Creating a Default Directory
I would suggest you show using the IDENTIFIER when creating
the users directory rather than the UIC.
You could show both forms of the command:
CREATE/DIRECTORY DISK$USER:[USER1]/OWNER=[USER1]
CREATE/DIRECTORY DISK$USER:[USER1]/OWNER=[11,2]
Page 1-21
Discuss the use of a logical for SYSUAF on the student page, i.e.
If the system manager does not set default to SYS$SYSTEM before
running AUTHORIZE, the system UAF will not be found; unless a
logical name is defined for SYSUAF.
Also discuss the logical on the instructor page, as the instructor
page suggests will be done.
Page 1-22.a and 1-22 Duplicate UIC.
Discuss on the instructor page the method to correct the
problem. i.e creating the IDENTIFIER manually and modifying
the UIC for the users account.
Page 1-23.a and 1.23 Not specifying Account for a New UIC Group
As the instructor page points out, the are other ways of adding
the identifier. so document it: ADD/ID/VALUE=UIC:[500,*] FINANCE
Page 1-24 Error: Not specifying Owner of Directory
Since you are recommending using the logical name in UAF, make
of the logical name in the CREATE/DIRECTORY command, the
SET DIRECTORY/OWNER command, and the SET FILE/OWNER command.
Also, the identifier could be used instead of hard-coding the
UIC in the last two commands.
Page 1-25
The logical name should be used rather than the device
specification of $1$DUA1:
The identifier could be used instead of hard-coding the
UIC in the command to create the directory.
Page 1-31
The identifier could be used instead of hard-coding the
UIC in the DISKQUOTA command.
Page 1-35 Setting a version limit
The logical name should be used rather than the device
specification of $1$DUA1: for both creating the directory
and doing the DIRECTORY/FULL command
The identifier could be used instead of hard-coding the
UIC in the command to create the directory.
In the output for the DIRECTORY/FULL, notice the owner is
[FINANCE,FINANCE1] The correct identifier should be FIN_USER1
What happened to the IDENTIFIER created back on page 1-23 ?
Page 1-37 Example 1-11 Setting a Version Limit on an Existing Directory
The logical name should be used rather than the device
specification of $1$DUA1: when doing the DIRECTORY/FULL command(steps
1 and 4) and the SET DIRECTORY command(step 3)
*** Notice the Owner for the file *** - it is DEFAULT ! This
needs to be corrected.
Page 1-38 If the number of free blocks on a disk is low, [action
to take?]
1) Purge - however the affect may remove old versions of files a
user wants/needs
2) Move some user accounts off this disk
3) replace the disk with a larger capacity device
Page 1-50 Commands
show the IDENTIFIER could be used in in the CREATE/DIRECTORY command
Page 1-52
add the QUALIFIER /FLAG=NODISUSER to the command to ADD the
user record for JACKSON
Why is there no output for the identifier JACKSON being created ?
Kuddos ! - you used the identifier in the example command to create
the directory for JACKSON.
Page 1-58 Solution: Establish a Disk Quota
Step 4 (a, b, and e)
How does this user know their UIC is 320,10 ?
Why not show using an identifier instead ?
Page 1-59
Again, identifier instead of hard UIC
Page 1-60 Practice Session for Managing the Use of Disk Space
This exercise is missing.
Page 1-61
This exercise is missing.
Page 1-63
Omit the S from the SHOW DEVICES commands so it is just SHOW DEVICE
|
| 153.11 | Disks Should be Overbooked | SUPER::SUPER::TARRY | | Tue Sep 22 1992 12:56 | 41 |
| > Page 1-13.a Disk Quotas
>
> You asked for feedback on: How much can we "overbook" a disk ?
>
> In theory as much as you like, however users tend to get angry
> if the disk becomes full and they have quota remaining.
>
> In practice, you should NOT overbook a disk. There should be
> enough free space so all users may use their quota fully.
> In addition, there should be enough space so they may use
> their allowed overdraft as well.
I disagree with the statement that you should not overbook a disk. This could
result in inefficient use of disk space. Under utilized resources waste money.
The better way to manage disk space is to monitor all disks daily to
make sure they are not too full. Unless a disk contains a very volatile
account, keeping disks 80% full works quite well. Determining how much to
overbook a disk should be done by monitoring the space in use as a percentage
of the space booked.
Disk space should not be overbooked when both of the following are true:
Users do not have enough disk space and always use close to their quota
Disks are run very full. 90%+
In this circumstance the smart user keeps unneeded files around just to have
something to delete when he or she needs more disk space. This is wasteful
in two ways:
disk space
backup
Limiting disk quota is not the only way to manage disk space. Limiting file
versions is also important.
Making sure users know the backup schedule and know that the data center is
ready to restore a file when needed helps to persuade users to delete unneeded
files.
Teach users to purge directories daily and to delete .log files
|
| 153.12 | | NITTY::DIERCKS | We will have Peace! We must!!!! | Tue Sep 22 1992 18:29 | 19 |
|
Reading .10 caused a thought to flash through my mind: "I bet the
author has never been a system manager." 8-)
Lordy, if I hadn't overbooked my disks on a regular basis back in the
days when I was a REAL system manager instead of just teaching it, I
would have only been able to give each user a couple thousand blocks of
quota. Usually, that would have been sufficient, but there were
periods of time when certain users needed considerably more than that.
I've always said that one of the jobs of the system manager is that of
an "educator". One of the things that I always taught, and my users
learned, is that every night at midnight, I did a disk-wide purge of
all directories -- down to two versions. If they needed more versions
than that, they had to rename them. I agree with the comment in .11
that diskquota is only one of many ways to manage disk space.
GJD
|
| 153.13 | Keep it comming | NEURON::STAHLY | 10$: BRB 10$ | Tue Sep 22 1992 19:35 | 16 |
|
re: .12
> Reading .10 caused a thought to flash through my mind: "I bet the
> author has never been a system manager." 8-)
Sorry to disappoint you, but I have managed RSTS, RSX, and VMS systems.
When I give a user to right to have x amount of storage, it is
available to them. To a user, not being able to actually use their
full amount of quota at any given time shows a failure of the system
manager to perform the job correctly.
I am glad to see participation on this subject.
|
| 153.14 | | DBLDOG::DONHAM | Progress Through Tradition | Tue Sep 22 1992 20:27 | 12 |
|
Ron, are we talking about the same thing? When I think of overbooking,
I think of giving 140M worth of quota on a 100M disk, assuming that not
everyone is going to use all of their quota.
On a totally unrelated note: I'd like to move the discussion of command
procedures from SN2 into SN1. SN1 talks about various command procedures,
and I'd like for the student to be able to go home and write simple ones.
Anyone hate that idea?
Perry
|
| 153.15 | Book tells 'what' can be done, the teacher tells 'how and why' | SOAEDS::TRAYSER | Seniority means a bigger shovel! | Wed Sep 23 1992 00:32 | 11 |
| RE: .10-.last
Hey, if you've got the HW and the quotas offered are generous, I agree
with .10! However, in the real world this is a rare event. Overbooking
is a STRATEGY, not a policy. It depends on the applications, users,
available HW and expectations set by the system manager.
I have run systems both ways, but in today's tight-money environment
the overbooking scenario is more common (for me and my customers).
$
|
| 153.16 | Yes ! | NEURON::STAHLY | 10$: BRB 10$ | Wed Sep 23 1992 14:39 | 10 |
|
re: .14 & .15 Yes, I think we are on the same course of thinking.
I agree(.15) it can be done either way, and we should discuss
the associated tradeoffs keeping in mind(.14) what the word
"assume" means.
re: .14 and command procedures: I agree.
Ron
|
| 153.17 | Startup/Shutdown chapter for review | DBLDOG::DONHAM | Progress Through Tradition | Thu Sep 24 1992 11:36 | 7 |
|
"Shutting Down and Starting Up An OpenVMS System" is available for review at:
SUPER""::ES$REVIEW:[SYSNET_I]SN1_STARTUP.PS
Perry
|
| 153.18 | | DBLDOG::DONHAM | Progress Through Tradition | Thu Sep 24 1992 15:02 | 6 |
|
"Maintaining Queues" is available for review at:
SUPER""::ES$REVIEW:[SYSNET_I]sn1_queues.ps
Perry
|
| 153.19 | | DBLDOG::DONHAM | Progress Through Tradition | Fri Sep 25 1992 17:14 | 5 |
| "Backing Up Files and Disks" is available for review at:
SUPER""::ES$REVIEW:[SYSNET_I]sn1_backup.ps
Perry
|
| 153.20 | | DBLDOG::DONHAM | Progress Through Tradition | Sun Sep 27 1992 16:51 | 8 |
|
The entire SysNet 1 IG is ready for review at:
SUPER""::ES$REVIEW:[SYSNET_I]sn1_ig.ps
Regards,
Perry
|
| 153.21 | Sysnet I pilot results | SUPER::WTHOMAS | | Mon Oct 12 1992 16:48 | 12 |
|
The summary of the System and Network Management I pilot held in
Maynard MA during the week of September 28th is posted in:
SUPER::$1$DUA6:[ES$REVIEW.SYSNET_I]SYSNET_I_PILOT.PS
Please post any comments regarding the pilot results here or send
them to me by mail at SUPER::WTHOMAS
Wendy
|
| 153.22 | | NITTY::DIERCKS | We will have Peace! We must!!!! | Fri Nov 13 1992 15:38 | 9 |
|
I just opened the "new" Digest, December, 1992, - May, 1993. For SNI,
it is stated "There are no formal pre-requisites for this course."
Exsqueeeeeeze me? Help me understand, please, how we can state
something so bolding inaccurate to our customers.
GJD
|
| 153.23 | It will be in January's | TEACH::SHERRY | Sherry Butler - (301)743-7160 | Fri Nov 13 1992 15:42 | 6 |
| That is true for the December sessions. Unfortunately, by the time
we knew User Skills would be a prereq for SYSNET I it was too late
to put it in that Digest. There will be another Digest hitting
the streets the first of January with the new information.
|
| 153.24 | | NITTY::DIERCKS | We will have Peace! We must!!!! | Wed Nov 18 1992 18:08 | 10 |
|
Is the instructor guide mentioned in .20 still the latest and greatest?
Phil Skepnek, my manager, was told today that there will be no "bridge
course" for the students who take the "old" sysnet I and want to move
to the "new" sysnet II because their is an appendix to make up the
differences. Where is this appendix? (I must have missed something
somewhere?) GJD
|
| 153.25 | | DBLDOG::DONHAM | Progress Through Tradition | Wed Nov 18 1992 21:39 | 7 |
|
The appendix is in SN2; a 'close to final' version will be posted in the next
few days for those who want to prep.
The appendix is essentially the Command Procedures chapter from SN1.
Perry
|
| 153.26 | | NITTY::DIERCKS | We will have Peace! We must!!!! | Thu Nov 19 1992 08:49 | 27 |
|
So, help me understand this:
1. A customer takes the "current" SNI.
2. They decide to take SNII in Q3 (or later).
3. They arrive at SNII only to find that a substantial pre-requisite
(I think, anyway) for successful completion of SNII is in the
appendix to the SNII course.
How in the name of all that's sacred are they supposed to be able to
come up to speed on that material when they are not being presented the
material until they get to the course where it's assumed they already
know the material? (Huh, is that English?)
NOT!!NOT!!NOT!!NOT!!NOT!!NOT!!NOT!!NOT!!NOT!!NOT!!
I'm scared and frightened by these new materials. I like the contents
(more than the old materials, anyway), but the introduction of the
materials into the curriculum show lack of planning and insight, in my
opinion.
We need a bridge course -- if it's only the module on command
procedures. And it MUST be sent to any customer that's planning on
taking SNII starting in Q3.
Greg
|
| 153.27 | | TEACH::SHERRY | Sherry Butler - (301)743-7160 | Thu Nov 19 1992 12:11 | 18 |
| I agree that command procedures is an important topic. But, looking
back through the material in the new SYSNET II course, there are
only 2 places that depend on knowledge of command procedures. They
are the discussion of the system startup files and the examples
of the Monitor command procedures. These are in chapters 5 and
7. That should give the student enough time to study the appendix
to understand the examples. Or, if the instructor thinks it's
necessary, have a mini-optional lecture early in the week about
command procedures.
There was alot of time and thought (and sleepless nights!) put into
how to implement this stuff. We looked at the material that would
be 'missing' between the old and new courses to determine if it
was critical to understanding the new course information. The last
I looked at it (although some has changed) the missing information
wasn't deemed critical.
Sherry
|
| 153.28 | | NITTY::DIERCKS | We will have Peace! We must!!!! | Thu Nov 19 1992 13:05 | 8 |
|
We're going to have to agree to disagree on this one, Sherry.
Unfortunately, I (and the other instructors) are the ones who are going
to have to face customers with this issue. Can I have them call you if
they're unhappy? 8-)
GJD
|
| 153.29 | | TEACH::SHERRY | Sherry Butler - (301)743-7160 | Thu Nov 19 1992 16:05 | 4 |
| If the pilot is any indication..
The majority of the students in the SYSNET II pilot did not take
the SYSNET I pilot. So, they did not get the command procedure
lecture in the new SYSNET I. It was not a problem for them.
|
| 153.30 | | NITTY::DIERCKS | We will have Peace! We must!!!! | Thu Nov 19 1992 16:29 | 6 |
|
I hope you're right. We can't afford to have any more customers go to
our competitors.
GJD
|
| 153.31 | | NITTY::DIERCKS | We will have Peace! We must!!!! | Thu Nov 19 1992 16:31 | 12 |
|
The Chicago training facility has decided handle this "problem"
situation is the following manner: (Exact logistics not yet worked
out.) We are going to call every student that enrolls in SNII and ask
them if they are aware of the change in the courses. If they wish, we
will send them a copy of the command procedure module so they have time
to work on it prior to coming to the course.
I hope this is all moot, I'm just not convinced.
GJD
|
| 153.32 | | SOAEDS::TRAYSER | Seniority means a bigger shovel! | Thu Nov 19 1992 21:56 | 14 |
| Sounds like a good thing. Calling the students is a very thoughtful
approach. I've looked over the material and think that there is a
possibility that the material can be handled by the instructors the week
of the teach. There are some students that will need this material
before the course, but I don't think it will impact a significant
number of them.
There are other course organization issues that I'm more concerned about
right now (like where STARTNET and NETCONFIG are taught).
I'm going to be looking over the new material carefully during the
holiday week and will post my thoughts and reviews shortly afterwards.
$
|
| 153.33 | Pointer to SN1 'final' version | DBLDOG::DONHAM | Progress Through Tradition | Mon Nov 23 1992 13:58 | 9 |
|
For prep, you can copy the following PostScript files:
SUPER::ES$REVIEW:[SYSNET_I]EY-G986E-IG-0002.PS
EY-G986E-SG-0002.PS
This is the version that is currently on the shelf for January teaches.
Perry
|
| 153.34 | New vs Old additions | TEACH::SHERRY | Sherry Butler - (301)743-7160 | Tue Dec 08 1992 14:13 | 47 |
| I've tried to go through SYSNET I to see what is in the new version that
wasn't in the old one. If you find any that I missed, please post them
so others have the information.
The version of SYSNET I that will start in January can be copied from:
SUPER::ES$REVIEW:[SYSNET_I]EY-G986E-IG-0002.PS
SUPER::ES$REVIEW:[SYSNET_I]EY-G986E-SG-0002.PS
This is in the old lecture/lab format but is currently being converted to
the new format. There are also a few things that will be added. However,
it won't be done until the end of December. So, rather than have you have
about 3 days to see it!.. we won't be implementing the new formated version
until later in Q3. I've included here the extra topics that I hope will
be added.
---------------------------------------------------------------------------
New information that wasn't in the old SYSNET I (pre-January 1993)
(The page numbers are from the SG)
Page
DSSI VAXcluster configuration 1-14
Connection Manager - Quorum 1-16:18
Developing Command Procedures Chapter 2
Establishing a Diskquota 3-15
Setting a version limit on directories 3-35:38
Set Process /resume /suspend 3-44:45
Stop/ID 3-46
Priority of jobs in queue 4-7
Closing a queue 4-18
Incremental backup 5-11:12
Command procedures for backup 5-13:15
Restoring backups 5-16:21
Listing a saveset 5-22:24
Booting satellite nodes 6-16:20
-------------------------------------------------------------------------------
Additional information that will hopefully be added to the next version.
You may want to add this in your lecture until the next version comes out.
SYSMAN (DO, SET/SHOW ENVIRONMENT, SET/SHOW PROFILE)
Shutdown VAXcluster
Create QUOTA.SYS
Modifying diskquotas
Default records for AUTHORIZE and DISKQUOTA
Device names with format $allocation-class$device and node$device
ASSIGN/MERGE for queues
|
| 153.35 | Capitol Ideas | TEACH::LYNN | | Fri Jan 01 1993 08:50 | 24 |
|
Here are some errors I found in the 93 version of SYSNETI
1-34a last paragraph Principle not "principal"
2-19 after bullet 13 there should be a blank line before the dollar sign
2-65 You need to add in the command line
/ERROR=ERROR_OPEN and then a label defined as ERROR_OPEN
Chapter One Objectives
You list "display information about the active processes on
the system" but you failed to cover it within the chapter.
overall comments:
The objectives, not counting the above exception, do truly match what is in the
chapter. Very few errors make the material look great.
I suggest that you add a few blank lines between the actual command
procedure and when you display the results of the file being invoked.
Everythings runs together...
Lynn White
Washington D.C.
|
| 153.36 | SysNet 1: FEEDBACK | DV780::STEELE | | Mon Jan 25 1993 14:25 | 77 |
| SYSNET I FEEDBACK (JAN 1993)
First I want to say that I am pretty please with the quality of
the material in this new SYSNET I course. I think it is much better
than the pre-1993 course.
A few mistakes I found or just things that I feel should be changed or
added.
CHAPTER 1:
5TH Objective is not covered in the chapter. Need to add at least
SHOW SYSTEM command or delete the objective.
CHAPTER 2:
page 2-19 add a blank line before line indicated 7
2-25 add a blank line before line indicated 3
2-26 add a blank line before lines indicated 3 and 5
2-28 add a blank line before lines indicated 6 and 9
2-37 add a blank line before line indicated 5
2-38 add a blank line before line indicated 7
2-40 add a blank line before line indicated 4
2-62 Second bullet is misplaced, needs to be move to the
bottom of the page below READ/ERROR command
CHAPTER 3:
page 3-43 They should know how to display processes before they
can control them. SHOW USERS, SHOW USERS/FULL and
SHOW PROCESS commands should be added to this chapter.
CHAPTER 5:
This chapter teaches them how to do backup but they are
not taught how to create volumes. Yet the corresponding labs
asks them to ALLOCATE, INITIALIZE, MOUNT ,DISMOUNT and
DEALLOCATE so I feel it should be covered in this chapter.
Also in this chapter the examples use the reply command but
it is not covered anywhere. It certainly does not belong in
the user class since privileges are needed so maybe it needs
to be covered here.
page 5-15 The example does a backup from one disk to one tape. The
comment at the top of the page should be changed to:
The following command procedure performs an incremental
backup an a tape every other night at 11:00 p.m.
LABS:
page 2-28 In the solution 3rd command of the procedure, 'COMMAND'
the single quotes and the comment at the end of the line
should be removed, since it contradicts the automatic
substitution rules we teach them on page 2-9 of the lecture
chapter 2.
page 5-3 This exercise asks them to do stuff that was not covered
in the lecture (see above comments on chapter 5)
page 5-7 Backup should be used to create save-sets, COPY should be
used to copy files. Step 2 should be:
Using COPY , copy all the .com files from SYS$UPDATE
to your new subdirectory SUBA.
page 5-8 Step 2 solution should be changed to COPY instead of backup.
|
| 153.37 | | DBLDOG::DONHAM | Progress Through Tradition | Mon Jan 25 1993 16:23 | 4 |
|
Good feedback. Thanks!
Perry
|
| 153.38 | please help us prepare students w/ nec. materials | MELKOR::HENSLEY | | Mon Feb 15 1993 19:48 | 24 |
| I have voiced this concern in other course notes, but again, since I am
teaching the new Sysnet I material for the firtst time this week:
PLEASE tell the students (in the confirmation letter?) to bring their
VMS User's Manual (AA-LA98B-TE) to Sysnet I (and II and III...). They
really should have it for the command procedure sections.
I try and provide a few classroom copies (but students keep walking
away with them and I have fewer each time ;-).
Only 2 of 17 students in todays class took VMS Skills for Users.
1 person took U & C six years ago.
All the rest learned their user skills (we hope) OTJ.
They are miffed that they don't have the manual. They even asked if
they could buy it locally. But we no longer have a bookstore.
arggggh!
(otherwise -- not a bad first day - more feedback after I get thru it.)
irene
|
| 153.39 | VMS for Users | NITTY::DIERCKS | We will have Peace! We must!!!! | Wed Mar 31 1993 09:12 | 30 |
|
I didn't see a topic specific to the "new" OpenVMS for Users course,
so I will put the reply here. Moderators, please feel free to move it
if you feel it should be placed elsewhere.
**********
I taught this course for the first time last week. I had seven
customers. All seven of them were relatively new to VMS but had at
least moderate experience on some other platform.
I keep a rather detailed tally as to how much time I spent lecturing on
the material that is in the course proper and how much time I spent
adding to the course. My numbers were: I spent approximately 10.5
hours lecturing on the material which is *in* the materials and about
another 6 hours adding material which I think *should be* in the
course. Take into account, if you will, that when I teach this course
there is little if any lab because I do almost everything on-line
during lecture. My conclusions are two-fold. If the expectations are
that we really should only teach the material on the pages, the course
is *way* too long and should be only two days in length. My real
conclusion is that the materials as provided simply don't provide
enough information to truly prepare the students/customers as users.
It is especially the case that modules 8 and 9 *must* have move meat in
them in order form them to serve the intended purpose. When I have
time (I don't know when that will be), I'll post a list of
additions/substitutions that I think should be provided/included/added.
Greg
|
| 153.40 | | DBLDOG::DONHAM | Progress Through Tradition | Fri Apr 02 1993 12:40 | 10 |
|
Greg, it would have been nice if you had spoken to me about this during the week
that you were here at ZKO.
Please do post what you think should be added...we're just now starting on the
V6 updates to the course, so this is a good opportunity to talk about new
material. It would be *especially* good if you either already have the material
written, or could help us write it.
Perry
|
| 153.41 | the scooooooooop | NITTY::DIERCKS | We will have Peace! We must!!!! | Mon Apr 05 1993 13:02 | 97 |
|
All of the stuff I added to the user class was off-the-cuff, nothing
was written down, per se. And, it was all down in augment-mode.
Briefly, these are the things I added:
Module 1: No additions
Module 2: I spent some time in the documentation, especially the DCL
dictionary, so the students can "see" how to tell the
difference between command qualifiers, parameter qualifiers,
and positional qualifiers.
I, at the end of the module, spent probably most of an hour
demonstrating the various "show DCL commands" to give the
students an idea how they can determine, more or less, what
their particular system looks like. Such things as
$show system
$show users (with various optional parameters and
qualifiers)
$show device (")
$show mem (")
$show process(")
I also added a brief discussion of the $set message command
and its qualifiers. Many of these people, according to
their introductions, will ultimately be system managers.
I remember from my own system manager days spending most
of a morning trying to figure out why one of my users (a
college student) wasn't getting any error messages. He had,
of course, been messing around with this command!
Module 3: No real changes, but lots of "hands-on" time here. I spent
a couple of hours going through various scenarios of
creating a subdirectory tree, moving files around in it,
making sure the understand the difference between renaming
a file and copying a file (it's amazing how many people
*don't* understand the distinction). In particular, what
the course doesn't do enough of is discussing how to move
laterally in a directory tree. It also doesn't do very much
with how to get "back" after having set default into a
non-existent directory.
Module 7: Lots of on-line, hands-on stuff.
Module 4: Minimal additions, just some hands-on stuff
Module 5: I'd like to see this module combined with module 3. You
really can't discuss directory trees without including the
discussion of copying and renaming files. Thus, I had
covered most of module 5 by the time I got to it.
I added a brief discussion as to the definition/differences
between execution queues and generic queues.
I also added a brief discussion on each of the following
DCL commands which, from my experience, can be useful to a
"user".
$differences
$search
$create (without /dir)
$run
$set * (many of them)
$sort
And, this seemed like as good a place as any to introduce
them to the concept of "privilege", so had them do some
simple things which I knew would cause a privilege
violation.
Module 7: Lots of on-line stuff.
Module 8: There needs to be a more detailed discussion of UIC-groups.
There needs to be an awareness of *system* UIC-groups.
There needs to be a discussion of the short-falls of
UIC-based protection as a prelim to a bare-bones
introduction to ACL-based protection. I feel these things
need to be added to the user-course if for no other reason
that "users" need to understand, if only vaguely, what
they are seeing if they issure a dir/acl or dir/sec and
see acl's. Of course, their also needs to be a brief
introduction to the concept of identifiers.
Module 9: This is where the course needs LOTS of work. Missing topics
include:
-- logical name table details (names, why they exist,
privileges, search order)
-- search lists
-- differences between global and local symbols (this needs
to be done here so when the "you have to create
global symbols in your login command procedure" message
is sent, they have some idea as to why this is the case)
|
| 153.42 | | DBLDOG::DONHAM | Progress Through Tradition | Mon Apr 05 1993 15:07 | 17 |
|
I'd like to somehow capture the on-line stuff that you folks are doing
during lecture...I know it greatly enhances the course, but we don't do
a good job of providing that sort of material in the instructor guide. If
you've been teaching Sysnet for a while it wouldn't matter, but I'm really
concerned about the increasing number of contract instructors who perhaps
don't have the depth of experience that our full-time instructors have.
As you teach, could all of you try to jot down the things you are doing on-line?
A SET HOST/LOG might be all that we need.
The other stuff you mentioned, Greg, we'll definitely look at. Is there some
way we can work together on chapter 9? It sounds like you have a fair idea
of what needs to be done...if you had two or three free days over the next
two months we could probably do what needs to be done.
Perry
|
| 153.43 | | NITTY::DIERCKS | We will have Peace! We must!!!! | Mon Apr 05 1993 16:50 | 8 |
|
I'm actually off platform for the next two weeks, but the time is
scheduled for my V6.0 prep. If you can send me mail (my database is
out of wack and doesn't know your node name) to let me know how I can
help, and I'll give it a shot as I can.
GJD
|
| 153.44 | | BROWNY::DBLDOG::DONHAM | Progress Through Tradition | Tue Apr 06 1993 09:37 | 11 |
|
Buck yelled at me to fix my conference entry...a reply/author should work
now.
I'll take a look at chapter 9 and get back to you in a few days...if you don't
hear from me by Monday send mail or call (I sometimes get involved in stuff and
forget to return calls/mail, but I'm working on it...).
Later...
Perry
|
| 153.45 | dynamic courseware R us.... | MELKOR::HENSLEY | | Mon Apr 12 1993 21:24 | 22 |
| We received a new rev level this morning in class (surprise surprise,
it is Monday): -0003.
This appears to be cosmetic - tho some pagination changes will cause
confusion with the instructors who refer to a specific page and the
students look at them with quizzical expressions.
I do not recall this being noted in Dave Nelson's weekly listing (and
our JIT contact was caught by surprise also). I am now going thru page
by page to see what else may have changed.
As an instructor, I usually like to know this before I start class, but
we have straightened it out early in the class this time. For other
instructors, I would suggest that you request a new copy before your
next teach. So far, what I see are minor pagination changes, a new
typeface, and some paragraphs have been moved. The new copy will just
help you speak to the same material your customer is viewing (and the
same place in the material...)
I wish I knew who to thank for the warning ;-).
irene
|
| 153.46 | 0003 is for Sysnet I, *NOT* VMS Skills for Users | MELKOR::HENSLEY | | Mon Apr 12 1993 21:28 | 2 |
| BTW, the new revision of materials was for Sysnet I.
|
| 153.47 | | BROWNY::BROWNY::DONHAM | Progress Through Tradition | Mon Apr 12 1993 23:57 | 4 |
|
Irene, what's the copyright date?
Perry
|
| 153.48 | yes -0003 is the new version | TEACH::SHERRY | Sherry Butler - (301)743-7160 | Tue Apr 13 1993 10:57 | 14 |
| Irene, thanks for speaking up about the new version!
I've been checking into it, and yes, JIT did change the revision
of the student guide for SYSNET I starting this week... unfortunately
it was something that slipped through the cracks.
IDC (Course Development) actually finished -0003 the end of December.
But, because that didn't leave enough time to prep before the January
teaches, we decided to hold off releasing it. (Only now it was
done without anyone knowing!)
The main change was to put it in the corporate doctype (the same
as SYSNET II and III). There was talk of putting a few extra pieces
of information in too, but I'm not sure if that happened. Perry??
|
| 153.49 | thanks - at least this can't be called boring!! | MELKOR::HENSLEY | | Tue Apr 13 1993 12:56 | 53 |
| It does reflect December 1992, as Sherry Mentioned.
Some of the sections HAVE been reworked. Since I didn't really teach
the old Sysnet I very often and didn't mark up my old guide, I just
have to pay close attention - maybe some of the things I used to add or
enhance the topics with are now included.
Timing: so far I spent Monday morning (after intros. course
descriptions, location logistics ) getting thru System Config (up thru
1-14), and Monday afternoon went thru Cluster & Network configurations,
p1-38.
This morning (Tuesday) I will wrap up Software Concepts, System Files &
Directories, the "2� tour" of memory management, paging & swapping),
assign the second lab and spend the rest of the day on Command
Procedures.
-----
Something new I experimented with in this week's class was a worksheet
the students filled out before intros, to assess their experience and
their environment. The following questions were on the form I used:
System & Network Management I
12 April 1993
Name:
Job:
Company/Organization:
Previous Courses Taken from Digital
VMS:
Other:
Experience with VMS:
Hardware and Software Configuration that you are responsible for
supporting (including hw models, version of VMS, any significant
applications):
-----
I was very surprised and pleased that they were completed thoroughly.
It was mainly a tool to help them understand their systems, provide
meaningful information in the intros and ***to understand how to apply
the course information*** (especially starting with Chapter 1).
I will use the form for the next two classes (I am teaching Sysnet I II
and III sequentially this month).
Irene
|
| 153.50 | re the questionaire | MELKOR::HENSLEY | | Tue Apr 13 1993 12:58 | 5 |
| BTW, on the questionaire I developed, I deliberatly did not make it
multiple choice, listing the pre-req. courses. I wanted to leave it
open and see how they responded.
ih
|
| 153.51 | Suggested N448E mods | WARNUT::GRAVESG | Geoff Graves,LS(UK);DTN 851 2637 | Tue Mar 29 1994 06:15 | 72 |
|
Well, almost one year on from .50; here some suggestions based on
the experiences of some UK instructors with EY-N448E-SG.0001 (which the
UK still refers to as G986E).
1. Modify chapter 3 to include information on Identifiers, ACLs and
RIGHTSLIST.DAT. We suggest inserting this after p3-46 to include a
section with a title such as "The Rights Data Base" which then
describes:
RIGHTSLIST.DAT
IDENTIFIERS - creation, removal, granting etc. Mentioning the
standard identifiers only.
ACLS - need for, creation, deletion etc. on *top level files only*
ie. so we don't discuss ACLs on directories, queues etc.
(ACLs at the moment are mentioned only briefly on the user
course and some level of knowledge of them is assumed for Sysnet 2).
A demonstration by the instructor of allowing/denying file access
through ACLs would be needed (possibly an exercise?)
Page 48 starts to mention privileges but we must make the distinction
between default and authorized. Include a table of all the privileges
but make it clear that not all of them are discussed or mentioned in
this course and that it is for reference only. Mention SETPRV and the
ones introduced on this course, eg: OPER.
p.53 The SHOW SYSTEM command needs a bit more explanation, but don't
go into details on page fault fields etc.
We suggest inserting a section before p61 entitled something like
"Managing System Information Files" in which the following are
discussed in brief: (This will then lead into the section "Purging Old
Versions of Files")
OPERATOR.LOG
OPCOM
REPLY
ACCOUNTNG.DAT
SHOW/SET ACCOUNTING
ACCOUNTING
ERRLOG.SYS
ERRFMT
renaming ERRLOG.SYS
ANALYZE/ERROR
2. In chapter 4 include a section on creating *simple* queues; ie.
only execution queues without any special characteristics other than
default ones set. This is because many delegates on SYSNET1 have asked
about "how" queues are set up. We give them a *simple* example and
explain that the subject is covered comprehensively in SYSNET2.
$SET TERMINAL /NOBROAD /SPEED /DEV etc.
$SET DEVICE/SPOOLED
Mention only directly connected devices *NOT* LAT. (covered in
SYSNET2)
Give an example of setting up a print and batch queue.
Include an exercise on creating and using a *simple* batch queue.
3. In chapter 5 include a section on preparing volumes for use around
p5-14 to include INIT/SYSTEM, MOUNT/SYSTEM /CLUSTER /FOREIGN,
DISMOUNT, ALLOCATE, DEALLOCATE.
P5-14 include /IGNORE=LABEL
P5-15 include /JOURNAL & /VERIFY
Add Standalone Backup topic after p5-33 - why, booting, what
happens etc. but *NOT* STABACKIT as this is covered in SYSNET 3.
|