Filter
Top Products
25.4.2.5 Setting Up Critical Operations Procedures
You should set up, test, and document procedures that are critical to the smooth
operation of your system. Here is a sampling:
•
System IPL, JES2 warm-start
•
JES2 checkpoint reconfiguration
•
JES2 ABEND and hot-start
•
System shutdown
•
VTAM startup and shutdown
•
VTAM vary node active and inactive
•
Switching devices between systems
•
System recovery, restart, and first-failure data capture
•
Stand-alone dumps
•
Managing spool space and spool full conditions
•
System backup (full and partial)
•
Emergency system restore
See Chapter 28, “Orientation to OS/390 Console Operation” on page 443 for
some examples of OS/390 console operation.
25.4.2.6 Managing Change
As you apply maintenance and make changes to your configuration, follow these
simple rules:
•
Make changes incrementally, not many at once.
•
Test the effects of each change to make sure you do not regress your
system.
•
Make sure you can back out changes in the event of a problem.
•
Document all changes, don′t rely on your memory.
•
Adhere to the age-old ″Keep it Simple (KISS)″ philosophy to minimize
unnecessary complexity in your system.
These guidelines are critical to the migration project, especially as you approach
the switch-over time.
25.4.2.7 Managing Problems
Staying on top of problems is important, especially with a project as massive as
converting from VSE to OS/390. Use a process and tools with which you are
familiar, perhaps what you are currently using with your VSE system. In addition,
you might want to set up a “strategy room” and large marker boards for
managing problems at switch-over time.
In addition, we recommend you keep your software service at a current level to
minimize the possibility of rediscovering old problems. See 25.5.1.2, “Applying
Preventive Service” on page 414.
Chapter 25. Prepare the Migration Environment 411