IBM 990 - Manual (Page 239)

Chapter 8. Capacity upgrades 227
CB-S (Commercial Batch Short job steps - I/O-Intensive; formerly CB84)
The CB-S workload is a moderate commercial batch jobstream reflective of fairly I/O
processing. The work done by these jobs includes various combinations of compile,
link-edit, and execute steps. Utility jobs, primarily for data manipulation, are also included.
WASDB (WebSphere Application Serving and Data Base)
The WASDB workload reflects a new-e-business production environment that uses
WebSphere applications and a DB2 data base all running in z/OS.
WASDB is a collection of Java classes, Java Servlets, Java Server Pages, and Enterprise
Java Beans integrated into a single application. It is designed to emulate an online
brokerage firm. WASDB was developed using the VisualAge® for Java and WebSphere
Studio tools. Each of the components is written to open Web and Java Enterprise APIs,
making the WASDB application portable across J2EE-compliant application servers.
OLTP-W (Web-enabled On-line workload)
The OLTP-W workload reflects a production environment that has Web-enabled access to
a traditional data base. For the LSPR, this has been accomplished by placing a
WebSphere front end to connect to the LSPR CICS/DB2 workload.
The J2EE application for legacy CICS transactions was created using the CICS
Transaction Gateway (CTG) external call interface (ECI) connector enabled in a J2EE
server in WebSphere for z/OS V4.0.1. The application uses the J2EE architected
Common Client Interface (CCI). Clients access WebSphere services using HTTP
Transport Handler. Then the appropriate servlet is run through the Web container, which
calls EJBs in the EJB Container. Using the CTG external call interface (ECI,) CICS is
called to invoke DB2 to access the database and obtain the information for the client.
OLTP-T (Traditional On-line workload - formerly IMS)
The OLTP-T workload consists of light-to-moderate IMS transactions from DLI
applications covering diverse business functions. These applications all make use of IMS
functions, such as logging and recovery. Conversational and wait-for-input transactions
are included in the workload.
CMS1 (CMS workload used for z/VM)
The CMS workload is designed to represent a VM/CMS end-user community. Processor
time per command, I/Os per command, T/V ratio, and think time distribution are similar to
those observed for actual VM production systems running large numbers of CMS users.
WASDB/LVm (Linux guests under z/VM running WebSphere Application Serving and
Data Base)
The WASDB/LVm workload reflects a server consolidation environment where the servers
being consolidated were running a full function application. For LSPR, this was
accomplished by taking the WASDB workload, splitting it across a pair of Linux guests
(one guest for application and one guest for database), and then replicating the Linux pair
many times to reflect the consolidation of many independent servers. The software levels
used were Linux SLES 7, WebSphere Application Server 4.0.4, and UDB 7.0.
HSRV/LV (Linux guests under z/VM performing HTTP Serving)
The HSRV/LV workload reflects a server consolidation environment where the servers
being consolidated were performing HTTP serving.
The workload simulates browsers accessing Web pages of mainly HTML files and their
graphics. The bulk of the files range in size from 1 KB to 100 KB, with a small number of
files greater than 1 MB being accessed. This last set simulates a large file being
downloaded. A driving system is used to send requests to the system under test. Client
subprocesses, or threads, generate an independent stream of HTTP requests, pausing in