Instructions for installing the patch for the Warehouse Manager server component
Service Level 3.01.070 -- Upper English
May 2001

These instructions use terminology consistent with ShowCase STRATEGY.

Downloading the Patch

This patch will fix all problems described in the previous document. The patch must be applied only to the ShowCase STRATEGY 3.01, dated 12/08/99. Refer to the instructions below for downloading and applying the patch.

1. Download the patch, saving the file in any convenient directory on your PC.

 
2. In Windows Explorer, double-click WOD070PS.EXE. This will launch a MS DOS prompt, which will create and inflate WOD070PS.BIN file.

• Verify that the version of ShowCase STRATEGY Warehouse Manager installed is 3.01 by using the DSPSCAUT command to look at the RSC910C message in the job log. Type the following:


<Warehouse Manager Installation Library>/DSPSCAUT

• To find out if this patch has already been applied to 3.01, check if the ShowCase PTF user space exists.

 

 

DSPOBJD <warehouse manager installation library>/WOD070PS *USRSPC

If the following message appears, the patch has not been applied.

CPF9801 - Object WOD070PS in library <warehouse manager installation library> not found.

• Ensure that you can use FTP between your PC and your AS/400.
• You will be required to sign on to your AS/400 as QSECOFR to apply the patch.
• Ensure that you end ShowCase TCP/IP if it is active, using the following command:


<Warehouse Manager Installation Library>/ENDSCTCP

• If you use Analyzer, you must also end the AOS server using the ENDAOSSVR
• Ensure no one is currently using the server. You can issue the following command to detect current server users.


WRKOBJLCK OBJ(<warehouse manager installation library>/SCCONNECT) OBJTYPE(*USRSPC)

• Special Notes for users of Analyzer OLAP Sever(AOS)


If you are applying a Warehouse Manager patch to a library that has AOS installed and has already been connected to, the SQL server jobs (QSQSRVR) must be ended and restarted before you re-start the AOS server. To properly enable this patch for prestarted server jobs, you will need to stop and restart the SQL server jobs. Otherwise the prestarted server jobs may continue to use older versions of programs and unexpected results may occur. To stop and restart the SQL server jobs, run the following:

ENDPJ SBS(QSYSWRK) PGM(QSQSRVR) OPTION(*IMMED)

STRPJ SBS(QSYSWRK) PGM(QSQSRVR)

Note: ShowCase is not the only application that uses these jobs, so you must make sure that there are no other programs using these jobs. This may require that you dedicate your AS/400.

Installing the Patch

(At this point, please be sure that Item 2 from "Downloading the Patch" has completed. That item involves executing the file that was downloaded from the web, thus creating the larger .bin file that will be saved as an FTP file to the server.)

1. OS/400: Create a save file in QGPL


CRTSAVF QGPL/WOD070PS

2. PC: Use FTP to transfer WOD070PS.BIN to the AS/400:


C:\>FTP <AS/400 IP Address>
User (system:(none)): <userid>
331 Enter password.

Password: <password>
230 <userid> logged on.
ftp> binary
ftp> put c:...\WOD070PS.BIN QGPL/WOD070PS
ftp> quit
C:\>

3. OS/400: Run the following commands. If the ShowCase library is already in your library list, you may omit the first command.

 

 

ADDLIBLE <warehouse manager installation library>
APYSCPTF DEV(*SAVF) SAVF(QGPL/WOD070PS)

4. OS/400: If the restore is correct, the following message will appear:

 

 

PTF WOD070PS Successfully Loaded for <warehouse manager installation library>.

5. OS/400: A journal will be created during the apply process. The journal contains information about the apply process and the last entry in the journal contains the PTF level. There should not be any journal entries of type ER or CE.

 

 

DSPJRN JRN(<warehouse manager installation library>/SCPTFLOG)

6. If you are not using Analyzer for the Web, skip to Step 8. If you chose a AOS port other than the default of 23000 during the install, follow Step 7. To verify the AOS server port, use the following command:

 

 

WRKSRVTBLE SERVICE(SCOLAPSVR<warehouse manager library>)

  If the port is set to 23000, skip to Step 8.

7. Change the port number to the one set for your Analyzer Olap Server. Use the following command:

 

 

CHGAOSA KEYNAME(TCPIPPort) KEYVAL(<portnumber>) AOSLIB(<warehouse manager library>) UPHTML(*YES)

8. The patch process is now complete.

Summary of problems fixed

• The code was changed to prevent a buffer overflow error. (F6113)
• The code was changed to allow the creator of a data view to change the authority of the newly created data view. (F6268)

• The code was changed to apply any existing row security on the base physical file if no row security exists on the logical file or view. "(F1713) 
• The code was changed to properly check application passwords, thus preventing an "invalid password" error. "(F5316) 
• The code was changed to use the correct user indices for the JDE business unit files."(F5885)

• The following components types do not show the dynamic members selection correctly in Analyzer for the Web, when the hint is larger than 64 characters; Radio Button, Combo Box, and Tab Sets.

If the form view is the first thing that you load in Analyzer for the web and you are prompted to for an Essbase userid and password, you will need to do a reload view to get the components propagated with the correct members. "(F5251) 
• The APYSCPTF patch logic for IFS files has been modified to allow the application of a patch when running under CCSID 5026. " (F5339) 
• The code was changed for the file read to use the record format from SCROWSEC, not SCFILSEC, when reading from the SCROWSEC file. " (F1360) 
• Resolved the problem where users were getting errors trying to create definitions. They would get a table or column reference error. This occured when WM security limitations had been put into place such as 'Return only libraries in the user portion of the library list' or the 'Exclude users from libraries by default'. Only fails when users do not have *ALLOBJ authority.

NOTE:
This fix has been placed into patches 2.51.030 and 3.01.060. The patch apply process will place a program called P3868UPD in the server library to which the patch is applied. Any time after the patch has been applied the program can be run. To run this program simply enter the commands:
ADDLIBLE (server lib)
CALL P3868UPD PARM(server lib)
This program will create the necessary stored procedure and register it within the proper caches. If this program is not run, FLR3868 will not be fixed. Any other functionality of the ShowCase server will not be affected by either running or not running this program. This program can only be run after patches 2.51.030 or 3.01.060 or higher have been successfully applied. This program only needs to be installed once into a server library, though calling it multiple time will NOT have any adverse effects on the ShowCase server. " (F3868) 
• The code will be changed to allow file names to begin with a numeric character. " (F5317) 
• The code was changed to parse the UDC field data properly so that descriptions are correctly retrieved. " (F5407) 
• A variable to indicate the number of third party SPs was not getting set in the mainline code if a batch query was the first query to run during a given session. The fix is to set that variable if the EnvRowSecInd is set to "S"." (F5426) 
• The code was changed to allow JDE users to query data views (built over JDE files) that do not reside in the same library as the JDE base physical file. " (F5563) 
• Initialized some objects so they are loaded from the same library as the first servlet call is made. " (F5313) 
• Resolved the memory corruption problem that resulted in inability to start the AOS server or the error message "i_specialAuthori not found in SCUser class". " (F5562) 
• Websphere changed how it processes a URL, so we had to change how we dynamically generate the various URLs created within the Information Directory for the Web. " (F5603)

• Filters are not showing up correctly in the information panel when substitution variables are used. " (F4335)
• The wizard was trying to generate passwords for WHM when WHM was not installed. Added code to not generate passwords for WHM when WHM is not installed. " (F4757)
• Seems there was debug residue left in INSTSC.CLP that didn't allow the SCSAMPL30 lib to be installed when Essbase was to be installed along with WHM. " (F4804)
• Resolved a problem whereby select statements greater the 6K would fail when submitted as a batch query. The limit will now be 16-18K. (F1504)
• The size of the ENTRY variable was increased so that memory would not be overwritten. " (F2016)
• Checking for functions in a Left Outer Join (parentheses checking) was added. We were not properly skipping over the functions. " (F4154)
• The code was changed to properly update the SQL packages on the remote systems. SQL packages need to be updated when multiple versions of STRATEGY are in use when migrating to a newer release of STRATEGY. " (F4171)
• The server code has been changed to send the correct job status. " (F4465)
• The code was changed to return the same amount of records from a temporary space and a result file when executing queries in batch. " (F4553)
• The code was changed to return the complete result set for column descriptions. " (F4662)
• The QDATFMT system value is now used to determine which work variable to hold the QDATE value and the method to build the date string that is returned. " (F4960)
• The code was changed to prevent a "file exists" error if the target table already exists before saving a Warehouse Builder definition. " (F5002)
• The code was changed so that setting the AS/400 Test Connection Host Log Level to "2" would force a spooled file to the STRATEGY user's spool file list. The spooled file (named SCSQLSTMT) contains the SQL statement that was used for all queries and reports (using Query and Report Writer). The spooled file is generated for interactive and batch modes. " (F5108)
• The code was changed to inherit the JD Edwards Business Unit Security settings from the base physical file when querying a logical file that was built over the base physical file. " (F5235)
• The code was changed to resolve the problem with batch queries that failed with the error message "Batch job failed due to SQL error, prepared statement E1 not found". " (F5291)
• There is a commitment control conflict that is preventing the COMMIT and the ENDCMTCTL from completing inp3868upd. Will have to issue a RCLRSC command in p3868upd to get the COMMIT and ENDCMTCTL to function correctly. " (F5300)
• Corrected a database problem that prevented the clear history operation from working if the user had previously updated information on the server. This fix will require a PTF from IBM to work. This PTF should be included with the latest CUM or database group PTF." (F4447)

• Resolved the problem with batch queries that received the error message "Batch job failed due to SQL error, prepared statement E1 not found " (F5291)
• Essbase error 1001097: Report parser error. Illegal command operations near<)>. Cannot continue processing. was issued when trying to load a view that uses the 'Restrict Data' option. " (F4546)
• The code was changed to trim the library name string from the end because a DBCS system could have a space in the middle of the name. (F1635) 
• The code has been changed to correctly reflect the user authority. (F3456) 
• Change RSTSRVRINF to restore the correct authorities to the IFS files and directories. (F3982) 
• End SCDIST job smoothly after an error. (F4078) 
• Improved performance for batch output to a table in some cases. (F4289) 
• RSTSRVRINF has been fixed to restore the folders with correct authorities. (F3541) 
• In a normal installation, the Analyzer for the Web opens a connection directly to the application server on the AS/400 using a standard TCP/IP socket. Most of the time when using a firewall or a proxy, this is not possible. (F4385) Configuring Analyzer for the Web to use this new servlet interface enables Analyzer for the Web to use the standard HTTP protocol when connecting to the application server on the AS/400.

 

 
 
 

Before you can use the new servlet interface, it must first be configured. To complete the configuration, you first configure the new servlet with your Web server then configure the HTML documents used to access Analyzer for the Web.  Follow the configuration instructions below.

The new servlet is actually packaged with the ShowCase Information Directory. In order to configure the new servlet, you must follow the instructions in your ShowCase STRATEGY Administrator's Guide for configuring the ShowCase Information Directory with a few minor changes.

In Step 11 where you are to enter the Servlet Name, use a name such as AOSServlet. This is the name that is used when configuring your HTML documents.
In Step 12 where you are to enter the Servlet Class name, enter "com.showcasecorp.aosservlet.AOSServlet". There are no additional servlet properties required.

In order to configure the usage of the servlet interface in your HTML documents, you must add two new APPLET parameters. In a typical STRATEGY installation, you will need to change the "applet.html" document. The "applet.html" document can be found in the IFS folder called "/install_library/ProdData/Analyzer/javaClient" Where install_library is the name of the library where Analyzer OLAP Server is installed.

Change or add the following parameters:
PARAM name=UseCGI value="Truequot"
PARAM name=CGIURL value="ServletURL"

Be sure the UseCGI parameter is set to True and the CGIURL is set to the URL for your servlet. For example, "http://AS400/servlet/AOSServlet" where AS400 is the IP address of your AS/400 Web server or the name of your proxy server and AOSServlet is the name you gave the servlet when you configured it above.

To test if the servlet is configured correctly, enter the CGIURL directly into your browser. You should see a message indicating that you have connected to the Analyzer for the Web servlet. If you do not get the message, then your servlet is either not configured correctly or the URL is incorrect.

If the servlet is configured correctly and Analyzer for the Web still is unable to connect to the server, then you may have to configure the "ServerIP"parameter to the applet in your html documents (for example, "applet.html") as follows:

PARAM name=ServerIP value="LOCAL_AS400_IP"

where LOCAL_AS400_IP is the native IP address of your AS400 where your Analyzer OLAP Server is running.

Note: The Analyzer for the Web servlet is packaged as part of the ShowCase Information Directory. All requirements of the ShowCase Information Directory that apply to servlets and WebSphere also apply to the Analyzer for the Web servlet.

• Fix a noticeable slow down in the view load time that might occur after migrating views from a pre-2.0 release to 2.0 or above. (F4165) 
• Create a file if it doesn't exist when specifying a change target connection or change target library or change target table. (F4004) 
• Trim the library name string from the end in case a DBCS system contains a space in the middle of the name. (F1635) 
• Return the correct table and library system names that appear on the properties sheets of member aliases in Warehouse Manager Client. (F3938) 
• Fix the code that allowed the user exit program associated with the Showcase exit point to be called if a exit program is specified for PCSACC. (F3958) 
• Change the restoration logic of the JOBMSGS file to follow the file structure. (F4003) 
• Change the operations list SQL statement to be ordered by the statement number, not arrival sequence access. (F4080) 
• Not return an error to the PC stating that there had been an access violation, or a not enough authority violation. Previously, if the PCSACC value is set to *REGFAC, a user without *ALLOBJ authority wouldn't be able to use Query or Warehouse Builder. (F4121) 
• Fix Servlet code so that an exception is not generated by the Websphere 2.0 Servlet engine. (F4176)