Obtaining the Latest Release Notes
Contacting Compuware Customer Support
If you accessed this document from the product CD or from the program shortcuts on your desktop, you may not be reading the latest release notes. For the most recent information, go to FrontLine, Compuware's customer support Web site. The first time you access FrontLine, you are required to register and obtain a password. After logging onto FrontLine, select your product from the drop-down list and click Go. On the left side of the page, click the Documentation link. You will find the latest release notes listed with the other product documentation.
QALoad has the following minimum system requirements:
The system requirements for each individual QALoad component follow:
Microsoft
Visual C++ 6.0 Service Pack 3 or higher, Visual Studio .NET 2002 (7.0),
Visual Studio .NET 2003 (7.1), or Visual Studio .NET 2005 for script compilation
and script validation.
Note: See the Technical
Notes section for more information about compiler compatibility.
cdo.dll must be installed on the
machine to use the send utility. CDO is an optional messaging component
of Microsoft Outlook. When you view the options for Office or Outlook
setup, CDO is listed under the options for Outlook. TCP/IP
communications
Note: The Server Analysis Agent must be installed on the same Workstation/Server
as the QALoad Player. It shares the same system requirements as
the Player workstation. The Server Analysis Agent is supported on Windows
platforms only.
The QALoad Player and associated utilities are supported on AIX, Linux, and Solaris. Compilers that are 32-bit compatible are required. The system requirements for each operating system follow:
AIX 5L Version 5.2 or 5.3
100 MB minimum available disk space
ANSI C compiler for compiling scripts. Compuware requires IBM’s VisualAge C and C++ compilers, version 6.0. Compuware also supports GNU GCC compiler version 3.3.2.
Note: The VisualAge compilers must be patched to the level indicated by the “September 2005 VisualAge C++ Professional V6.0 for AIX PTF”. For more information, refer to the IBM website.
Java Runtime Environment 1.3 or 1.4 for developing Java scripts
TCP/IP communications
Appropriate client application environment
Compuware requires the Linux system-provided GNU GCC version 3.2.3 compiler
Note: The system should be updated to the packages indicated in the Red Hat Advisory: RHBA-2005:661-11. Additional packages required to resolve dependencies also should be applied.
ANSI C compiler for compiling scripts. Compuware requires Sun Workshop compiler version 5.3 or Sun Forte 6.0. Compuware also supports GNU GCC compiler version 3.2.3.
In addition, your Windows system may need to meet specific requirements to support the middleware you will be testing. The Winsock and NetLoad middlewares do not have any additional QALoad Windows Player requirements.
QALoad supports load testing under Oracle Net8/Net9 when the following requirements are met:
QALoad supports load testing under ODBC when the following requirements are met:
QALoad supports load testing under Uniface when the following requirements are met:
QALoad supports load testing under Citrix when the following requirements are met:
QALoad supports load testing under SAP when the following requirements are met:
QALoad supports load testing under ADO when the following requirements are met:
QALoad supports load testing under Oracle Forms Server when the following requirements are met:
Note: Compuware recommends you use the Java HotSpot Client VM.
QALoad supports load testing of J2EE components when the following requirements are met:
QALoad supports load testing under WWW when the following requirements are met:
QALoad supports Streaming Media under WWW when the following requirements are met:
QALoad 05.05 supports integration with ApplicationVantage version 9.8 and 9.9.
Integration with ApplicationVantage is supported on the Windows platform only.
QALoad 05.05 supports integration with ServerVantage version 9.8 and 9.9.
The following environments, though supported in this release of QALoad, will not be supported in release 05.05.01:
SAP 4.6x client
Java Development Kit 1.3 requirement for the Java middleware
The following environments and middlewares will not be supported after QALoad release 05.05.01:
ADO
Oracle 2-tier
QARun
Multi-port player execution
Parameterization of the fields within the web middleware is greatly enhanced in this release. There is now a Wizard that guides you through the necessary steps to replace a field with datapool values, local variables, extracted strings, date/time fields, VU numbers, text, or any combination of these. The Wizard also enables you to parameterize all recurring instances of the target to be substituted in a single step, instead of manually repeating the process for every instance within your script.
The actions that are taken by the Wizard during this process are stored in a Parameterization Rules folder for future use. This is the greatest benefit of this feature. Future scripting efforts against an application can be considerably shortened by applying pre-defined rules against scripts that are known to require similar variable logic.
A utility called the QALoad Rule Library can be launched from the Workbench. You can use this to create, edit, delete, and organize Parameterization Rules within its folder system.
For WWW scripts, you can enable "Expert User Timings" in the Conductor's machine assignment tab. The players then gather additional timing information during a loadtest that you can view after the test has completed. It shows you the network and server times for the individual components of each web request, such as images, stylesheets, scripts, and so forth. This can help you identify areas within the technical infrastructure that can be related to the results of the test.
You can now collect additional performance data specific to packaged applications and application servers. These include, among others, new metrics for SAP, WebLogic, and WebSphere. This Remote Monitoring feature enables you to extract data from counters (Windows or UNIX) from the servers under test without requiring the installation of any software on the servers. While your test is running, QALoad collects the appropriate counter data and writes it to your timing file where it can be viewed within Analyze and correlated with other test results after the test.
To complement the new monitoring capabilities, QALoad also provides monitoring templates along with a utility that enables you to create your own.
QALoad integrates with ApplicationVantage to help you analyze network performance during a load test. ApplicationVantage provides granular thread details so that network managers can identify poorly performing applications. QALoad also provides test data that you can open in ApplicationVantage.
When Expert User data is collected (WWW only), the Analyze Workspace includes an Expert User tab. Using the new test information that is displayed here, you can create detailed graphs and reports that show the breakdown of the web requests, which can assist in pinpointing potential bottlenecks during the test.
When a timing file contains ApplicationVantage data, QALoad’s Analyze Workspace includes the ApplicationVantage group tab. From the ApplicationVantage group, you can export ApplicationVantage trace files to a working folder or launch ApplicationVantage in order to view the report details.
Analyze now includes three new pre-defined reports to help you identify performance problems:
Expert User report – Available when Expert User data is collected (WWW only). Displays timing data for each web request and its sub-components, such as images, stylesheets, and so forth. It includes average response time and what percent of that time was spent on the network versus the server. This can be very useful in identifying potential anomalies within load test results.
ApplicationVantage report – Displays information about the trace files collected by ApplicationVantage during the execution of a load test. A detailed graph allows for the correlation of transaction response time and the start and stop times of each AV trace.
Worst Performing Checkpoints and Counters report - Displays graphs and provides details about checkpoints and counters that had the worst performance during the test. Checkpoints with the worst performance are calculated using the average response time for each checkpoint. Counters with the worst performance are either those that furthest exceed their thresholds, when defined, or consume the most amount of time during the test. You can define thresholds in the new Results Analysis Wizard.
Use the new Results Analysis Wizard to define thresholds in QALoad Analyze. Thresholds are values that show the expected warning and critical limits for a counter or a checkpoint. Thresholds help identify problem areas in the test, such as checkpoints or counters that go above or below a specified value. They actively monitor response times by indicating whether data records are surpassing user-defined expected warning and critical levels. The information displays in graphs and detail reports in the detail data view and is used for the Worst-Performing Checkpoints and Counters report.
You can now create a template file that contains information about the current graphs, reports, and thresholds that you are viewing in an open timing file. This template can then be applied to other timing files, resulting in the initial view of those timing files being in a desired state with the expected graphs and reports already created and opened. When timing files are saved with a specific template, they open with that template applied as well. This allows for continuity in data presentation.
The ZipFile Wizard simplifies the task of collecting the files needed by the Technical Support team to analyze and assist in problem resolution in QALoad. It facilitates navigation through QALoad’s installation so you can easily select the required files without having to determine their various path names and locations.
A series of script samples is provided for the following middlewares: WWW, Winsock, SAP, Citrix, and Oracle Forms Server. In addition to the script sample itself, each sample includes a description of what it does and the type of problem it resolves.
An error code index with links to individual error codes is provided for the following middlewares: WWW, Winsock, SAP, Citrix, and Oracle Forms Server.
When you install QALoad on a Windows XP machine with Service Pack 2 applied, the Windows Firewall is automatically configured to include the QALoad Player agent as an allowed exception. This configuration is required for communication between the Conductor and Player machines during a load test.
If you are migrating from a previous version of QALoad, you must re-compile your existing scripts in the Script Development Workbench to use them in this release.
When load testing WWW scripts that use NTLM authorization, do not use the "Switch User" feature of Windows XP. Using this feature allows multiple user sessions to be active simultaneously, which can cause problems with script playback. If you need to use a different Windows profile, log off Windows and log on as a different user instead.
certdb.txt for OFS recordingFor the SSL support provided in this release, QALoad modifies
the client machine's JInitiator certdb.txt file to include
QALoad's CA certificate during the initial SSL recording process
for an Oracle Forms Server application. This certificate authority information
is internally validated by Oracle during the OFS-SSL session. If you want
to remove the QALoad CA certificate, delete the following text
from the certdb.txt file:
#qaload
-----BEGIN
CERTIFICATE-----
MIIC1jCCAj+gAwIBAgIBADANBgkqhkiG9w0BAQQFADBXMQswCQYDVQQGEwJVUzER
MA8GA1UECBMITWljaGlnYW4xEDAOBgNVBAcTB0RldHJvaXQxEjAQBgNVBAoTCUNv
bXB1d2FyZTEPMA0GA1UECxMGUUFMb2FkMB4XDTA1MDYyMzE3MDEyN1oXDTE1MDYy
MTE3MDEyN1owVzELMAkGA1UEBhMCVVMxETAPBgNVBAgTCE1pY2hpZ2FuMRAwDgYD
VQQHEwdEZXRyb2l0MRIwEAYDVQQKEwlDb21wdXdhcmUxDzANBgNVBAsTBlFBTG9h
ZDCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA07Q/tlwx4wQezY5UY92v+NdQ
WI1yjlbWrkFFBTVWtvb/M+SdHGHXntDxGF378058hHND95wQsADCnJmPQNIoqj1c
elHl+4hkMtioMSb8IiEMs4OCgOaoBTtFrRgffZxoWJHAlh2k/MUcbFc1oiSZGdcT
Ua7keQ5NtahHRputc0MCAwEAAaOBsTCBrjAdBgNVHQ4EFgQUXUtOUAp/U8TV4p75
AA8ybai1080wfwYDVR0jBHgwdoAUXUtOUAp/U8TV4p75AA8ybai1082hW6RZMFcx
CzAJBgNVBAYTAlVTMREwDwYDVQQIEwhNaWNoaWdhbjEQMA4GA1UEBxMHRGV0cm9p
dDESMBAGA1UEChMJQ29tcHV3YXJlMQ8wDQYDVQQLEwZRQUxvYWSCAQAwDAYDVR0T
BAUwAwEB/zANBgkqhkiG9w0BAQQFAAOBgQBEmh3S2ktyRu7pn9PaqgZS2v1o2PhH
5XYZI8YKs9ZeWJotebtgmu/5xJj4I48neWE45kA/akYbUsW491UEZ609Pf2cw3JO
xBZ8MOyT7z3RzAhBFe8CpHrQjmc6Vh8Mzcv6vVYRCDlIGlk2CguQ3WQWF8w3zNA/
I53OD9PZjisIlA==
-----END
CERTIFICATE-----
#qaload
To use the SAP or Citrix middlewares, you must ensure that the VC++ MFC and Template Libraries option is selected when you install Visual C++. This option installs the headers, libraries, sources, and browser database for MFC and ATL, which are required for both the SAP and Citrix middlewares.
To prevent performance issues, Compuware recommends that you increase your system paging file size to a fixed size of:
The Monitoring Options tab has replaced the Machine Configuration tab in the QALoad Conductor. All options on the Machine Configuration tab are now included in Monitoring Options, Monitoring Options tab, or Manage Player Machines dialog box.
QALoad 05.05 provides enhanced JavaScript support that gives a more accurate replay of complex Web sites that make heavy use of JavaScript. The new support enables QALoad WWW replay to work on a wide variety of sites without script modifications. This enhanced support is for Visual Navigator scripts and .c scripts.
The following list of deprecated commands are not supported in QALoad Release 05.05:
Common Functions
REPORT
REPORT_STATS
PROCESS
THINK_TIME
GET_DATA_NOREWIND
GET_DATA_REWIND
CHECK_POINT
CHECK_VALUE
END_CHECKPOINT
BEGIN_TIMER
BEGIN_CHECKPOINT
DEFINE_OP_ID
WWW Functions
DO_BuildFrameURLList
DO_GetProxyAuthorization
DO_RawLogging
DO_SocksProxyAuthorization
DO_SocksUseProxy
DO_SubRequestFrames
DO_UseSocksProxy
The following list of deprecated commands are used in QALoad Release 05.05, but they are not supported in QALoad Release 05.05.01 and later:
SAP Functions
Do_SAPCheckScreen
Do_SAPCheckStatus
Do_SAPCheckTitle
Do_SAPClearMessages
Do_SAPDumpEvent
Do_SAPExtractString
Do_SAPFrontEnd
Do_SAPFullMenu
Do_SAPGetControlValue
Do_SAPGetIt_Event
Do_SAPGetScreenTitle
Do_SAPGetStatusMsg
Do_SAPInit
Do_SAPLogging
Do_SAPLogin
Do_SAPLogoff
Do_SAPSendDblClick
Do_SAPSendEvent
Do_SAPSendMenu
Do_SAPSendOKCode
Do_SAPSendPFKey
Do_SAPSendReturn
Do_SAPSetCheckScreenWildcard
Do_SAPSetCtrlValue
Do_SAPSetCursor
To avoid timeouts during validation of Winsock scripts, filter IP traffic captured by the browser to exclude all traffic originating from localhost (127.0.0.1). In the Script Development Workbench, select Options>Record and click Set IP Addresses. The Add/Delete IP Addresses dialog box displays. Click Add to open the Add/Edit IP Addresses dialog box. In the Host Name or IP Address field, type localhost, then select All ports. Make sure the Status field is set to Exclude. Click OK.
On the Unix player platform, you must create a Certificates sub-directory in the QALoad directory before creating a client certificate. The directory name is case sensitive. For more information, refer to the topic, "Create Client Certificates in QALoad (SSL)" in the online help.
Because of changes and upgrades in QALoad 05.05, you must do the following to properly configure QALoad 05.02 session files in QALoad 05.05:
Use QALoad's new Monitoring Wizard to re-configure Server Monitoring performed through Remote Monitoring, Server Analysis Agents, and direct integration with ServerVantage. The Monitoring Wizard assists you in determining the servers and metrics that require monitoring. For more information, refer to the topic, "Overview of Remote Monitoring" in the online help.
Use the Conductor's Edit Player Machine dialog box to re-configure parameters for the ApplicationVantage integration. For more information, refer to the topic, "Configuring a Test to Use with ApplicationVantage" in the online help.
You must complete these configurations only once, then save the changes into the QALoad session file.
For QALoad scripts, .csv files are no longer supported as datapools. Only .dat file types are supported for datapool files.
After QALoad release 05.05.01, the CtxPing command is not supported.
This section describes known issues related to the current release of QALoad.
A known issue exists with the Microsoft Operating System that may cause new programs to appear behind other already open programs. When you start a program from another program, the new program window may appear behind all other open windows. Additionally, the new-window icon flashes on the taskbar. This symptom occurs on a Microsoft Windows 2000-based computer or on a Microsoft Windows XP-based computer. Microsoft has documented a procedure that details how users can modify the value of the ForegroundLockTimeout registry entry in Registry Editor to correct the issue. For specific instructions and more information on this issue, please refer to the following article located at the Microsoft Help and Support website for details: http://support.microsoft.com/default.aspx?scid=kb;en-us;886217
When a capture file is converted to a script, occasionally the wrong
Citrix Window Information object ID is referenced. For example, a Click,
MouseDown, MouseUp, or WaitForWindowCreate
action might be using the wrong CWI ID. The correct CWI ID can be determined
by inspecting the capture file to find the window handle that has focus.
SetTitle MethodDuring the conversion process, calls to the SetTitle method
are sometimes placed at an incorrect line in the script. Determine the
correct line by inspecting the capture file and moving the call to that
position in the script.
The SetTitle method is added by QALoad during conversion
and should otherwise not be modified or manually added to a script.
Uppercase characters are not captured when the CAPS LOCK key is on.
Manually modify the script to use uppercase characters or hold down the
SHIFT key during recording.
Similarly, the Windows logo key is not supported. Do not use the Windows
logo key to start applications while recording a Citrix script.
If you receive a type mismatch error when compiling an SAP script, you
must remove the quotation marks around the last parameter of the affected
command. For example:
error C2664: '<FuncName>' : cannot convert parameter n from
'char [n]' to 'long'
This compiler error, which can occur in commands that manipulate column
widths, indicates a data type error and can be corrected by removing the
quotation marks around the last parameter. The following example shows
the lines in a script that could cause an error, and the corrected version
of the same lines.
Script that produces the error:
SAPGuiPropIdStr("wnd[0]/shellcont[1]/shell");
SAPGuiCmd2(GuiCtrlTree, SetColumnWidth, "REPNAME",
"218");
Corrected script:
SAPGuiPropIdStr("wnd[0]/shellcont[1]/shell");
SAPGuiCmd2(GuiCtrlTree, SetColumnWidth, "REPNAME",
218);
During validation of SAP scripts, do not minimize the SAP window. If the window is minimized, the validation may fail. This problem does not occur if you select the Hide Graphical User Interface for SAP Users option by clicking the browse [...] button in the Type column of the Script Assignment tab in the Conductor. This SAPGUI option runs SAP on an alternate desktop that is not visible.
When loading a class by name in the QALoad Player during runtime, do not use a class name on the Enterprise Java Bean (EJB) InitialContext call. Instead, use a class instance or add a line of code before the JNDI lookup call. Refer to the following examples:
Replace the InitialContext properties and JNDI names in the following example with the values that are appropriate for your application.
Before:
java.util.Hashtable ht = new java.util.Hashtable();
ht.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
ht.put(javax.naming.Context.PROVIDER_URL, "fh12623:1099");
javax.naming.InitialContext ic = new javax.naming.InitialContext(ht);
Object ref = ic.lookup("AddressMSvc");
After:
org.jnp.interfaces.NamingContextFactory nf = new org.jnp.interfaces.NamingContextFactory();
java.util.Hashtable ht = new java.util.Hashtable();
ht.put(javax.naming.Context.PROVIDER_URL, "fh12623:1099");
javax.naming.Context ic = nf.getInitialContext(ht);
Object ref = ic.lookup("AddressMSvc");
Add the following line before the JNDI
lookup call:
Thread.currentThread().setContextClassLoader(getClass().getClassLoader());
If it is a static method, use the following
sample, replacing CLASSNAME with the class name of the code.
Thread.currentThread().setContextClassLoader(CLASSNAME.class.getClassLoader());
If you are running McAfee's VirusScan 8.0 with the "Buffer Overflow Protection" option enabled, Internet Explorer may fail to launch when you start a Winsock recording or when you record OFS socket mode. To prevent this issue, disable the "Buffer Overflow Protection" feature within McAfee VirusScan.
MS XML version 4.0 parser is required to view pre-defined or custom reports (relying on XML translations). Internet Explorer 5.5 ships with the MS XML version 3.0 parser. Compuware provides the MS XML 4.0 parser with this version of QALoad so that an upgrade to IE 6.0 is not required. It is automatically installed by QALoad but does not override any other version that may exist on the machine. QALoad Analyze looks for and loads this parser when using pre-defined or custom reports.
The Send utility in Analyze does not always work properly with Outlook 2003. If you experience problems when clicking the Send button in the email that is generated by the utility, you can instead use the utility to create a .zip file of the results and manually attach that file to an email you create directly in Outlook.
If you are using the QALoad Conductor on a machine that has Microsoft Office 2000 or XP installed, when launching Conductor, you may be prompted repeatedly to insert a Microsoft Office installation CD. This problem is a known issue with Microsoft Office and occurs during use with an account that is different from the account that was used during the Office installation, and if none of the Office components have been launched since installation. To avoid receiving the prompts, launch any Microsoft Office component under the user account that was used during installation, and close it. For more information about this Microsoft Office issue, refer to the Microsoft knowledge base article Q298385.
The DO_SQLFetch command in the online help shows lines in a script that could cause compile warnings and will not give the intended result during validation. Provided below is the example that could cause an error and the corrected version of the same lines.
Script that produces the error:
pReturnValue = DO_SQLGetData( S0, 1, SQL_C_LONG, 4 );
free(pReturnValue);
Correct script:
DO_SQLGetData( S0, 1, SQL_C_LONG, 4 );
strcpy(pReturnValue, GetFetchedData()); }
QALoad supports load testing of Traditional Chinese, Simplified Chinese, Japanese, and Korean Web applications that use Double Byte Character Sets (DBCS). Viewing timing files and Summary reports with International versions of Microsoft Windows is only possible if the timing file is viewed on the same Windows language platform on which the timing file was created.
When using the Server Analysis Agent to monitor the "Process->% Processor Time" counter on a multi-processor machine, values greater than 100% for any instance of the counter are reported as 100%. To ensure accurate results, Compuware recommends that you use Remote Monitoring or Top Processes Monitoring when monitoring any instance of the "Process->% Processor Time" counter.
A file descriptor limit exists on the Solaris platform if a script is running in threaded mode, logfile generation is turned on, and there are more than 250 virtual users. To avoid this limitation, modify the Logfile Generation parameters so that logfiles are not generated by all virtual users:
QALoad now supports the use of non-Administrator users on the Windows 2000 and Windows XP Professional Edition platforms. Administrative rights are still required to install the software and appropriate user privileges are required for QALoad to write files to its own directory (which by default is in the Program Files directory). Administrative rights are also required when using middlewares that require the Capture Initialization Phase option. This requirement applies to middlewares other than WWW.
If you have uninstalled all previous versions of QALoad but the installation process indicates that a previous version of the product is still installed, you may need to remove a registry key. In the Windows Registry Editor, delete the following registry key if it exists on your system:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{90C9114B-ED44-4AB9-B32F-1B9EA363FBEF}
Access field descriptions of Remote Monitoring dialog boxes through links in the procedural topics. For example, a description of the New Monitoring Task dialog boxes is available from the Elements of the New Monitoring Task Wizard link in the topic Creating a New Monitoring Task.
The Visual Navigator's Find/Replace functionality may not find and replace XML tree items.
The Checkpoint view may be blank when applying an existing saved template.
For Performance Monitoring of Application Servers for WebSphere, WebLogic, SAP, WMI, and WebSphere MQ, you must install the ServerVantage agent that is packaged with the QALoad software. The agent should be installed on a non-production machine that does not currently have a ServerVantage agent installed.
If you are using the ServerVantage agent during monitoring and retrieving data from a server that is being monitored with both a standard ServerVantage (Windows or Unix) and a remote collector, you may not see the counter data returned from the standard agent and may only retrieve data from the remote collector.
Subrequests in Old-Style WWW Scripts Invalid characters in the Conductor Runtime Graphs on Japanese Operating System If you are running a Japanese Operating System, you may see invalid characters in the file names in the drop-down list on the Series tab of the Conductor Runtime Graph. There is no known resolution at this time. The improper interpretation of the characters involves a third-party tool that the software uses to display this information. Check FrontLine for future updates to resolve this issue.
There are limitations to the size of a Central Datapool that the QALoad Conductor can handle when starting a test. When attempting to use a Central Datapool file that is approximately 20MB or greater, the QALoad Conductor may fail to start. To avoid this problem, create a smaller Central Datapool file, or use a local Datapool for the test instead.
If you are using MS Visual Studio .NET 2005, QALoad may not recognize the new compiler until you enter it in the Workbench compiler settings. On the Option menu, select Workbench, then select the Compiler settings tab. Select Microsoft Visual Studio .NET 2005, then click OK.
HTTP scripts fail to compile on AIX systems using GCC as the compiler after the QALoad SSL module is installed. You must manually install a different library for your scripts to compile properly.
When installing the SSL module, EasyScript for Secure WWW, on AIX using the package installation method, you must perform the following steps after the installation is complete:
Login to the AIX system as 'root'.
cd to /opt/QALoad/lib
Enter the following commands:
mv libqlHTTP.a orig.libqlHTTP.a
ln -s ./libqlHTTP128.a libqlHTTP.a
mv libg++qlHTTP.a orig.libg++qlHTTP.a
ln -s ./libg++qlHTTP128.a libg++qlHTTP.a
On AIX 5.3, the libraries needed to support the WWW middleware cannot be loaded at run-time if the GNU g++ compiler is used to compile the script. When this occurs, a message similar to the following is displayed:
pid(389168): ERROR: VU(0): Unable to load script '/home/QALoad//scripts/www.a' errno(8) 'Exec format error'
To avoid this problem, compile your script using the VisualAge C++ compiler, version 6.0. Note that the GNU GCC compiler does work on AIX 5.3.
A licensing failure may occur in any Compuware product using DLM 4.0 when DevPartner Enterprise Edition 8.0 or Xpediter Dev Enterprise 4.2 is installed after QALoad 05.05 and any of these products are subsequently uninstalled. This is due to a conflict in the DLM version number. To correct this problem, click Install QACenter Products and run Install License Manager from the QACenter Performance Edition CD.
Compuware Customer Support can assist you with all issues, from installation to troubleshooting.
Prior to contacting customer support, gather the following information:
800.538.7822
Refer to Compuware's FrontLine support web site for fast access to critical information about your product. You can read and print documentation, download product fixes, review frequently asked questions, or directly e-mail Compuware with questions or comments. The first time you access FrontLine, you are required to register and obtain a password.
Refer to Compuware's corporate web site at http://www.compuware.com/ for information about Compuware customer support policies and problem resolution process.
Customer Support
Compuware Corporation
One Campus Martius
Detroit, MI 48226-5099
End of QALoad Release Notes
(C) 2005 Compuware Corporation. All rights reserved. Unpublished rights
reserved under the Copyright Laws of the United States.