Hi All,
Many years ago there was an Installation Verification Procedure for VM.
This was mostly directed toward CMS tasks. We found that this was not very
useful and removed it from our product documentation. We have a list of
some items that we use as an IVP when we get a new release of VM. This is
not an official IBM IVP. This include things like:
CP IPL (MP) - stop if you cannot do this :-)
CMS IPL (190 and Segment) - needed to do many other things. 190 is needed
if the segment fails
GCS IPL - needed for RSCS and other applications
RSCS Initializes - needed for sending/receiving files
PVM Initializes - remote system access
SFS Initializes - file storage
TCP/IP Initializes
Able to logon to the system via telnet - remote system access
Able to FTP to and from VM - needed for sending/receiving files
NETSTAT command functions - needed for our environment
Run test workloads to reach 50-70% CPU load for 4 hours. - load that is
reasonable for us to ensure some stability. The test workloads vary.
Linux and z/OS each IPL second level. - needed for our environment
Workloads must run on both of these guest operating systems.
These are some of the things that we do to initially verify the installed
VM. If all of these work, then we have a good chance that we can continue
to use the new release. The items that are important to you might vary
from this list. I hope this list might act as one example.
Doug Breneman z/VM Development IBM Endicott, NY
Adam Thornton
<[EMAIL PROTECTED]
mine.net> To
Sent by: The IBM [email protected]
z/VM Operating cc
System
<[EMAIL PROTECTED] Subject
ARK.EDU> Re: Installation Verification
Procedures
02/15/2008 10:22
AM
Please respond to
The IBM z/VM
Operating System
<[EMAIL PROTECTED]
ARK.EDU>
On Feb 15, 2008, at 9:07 AM, Alan Altmark wrote:
> Program products have IVPs because .... I don't know. The great thing
> about computers, unlike people, is that they reliably do the same
> thing
> every time.
Here speaks a man who works in Endicott, not in Redmond.
Adam
