Warehouse Manager 3.01.070

Patch name: WOD070PS.EXE and WOD070US.EXE

Patch Installation Instructions-Upper English
Patch Installation Instructions-U.S. English
Print and read these first!

WARNING!
THESE EXEs MAY INFLATE TO OVER 100MEG. MAKE SURE YOU HAVE ENOUGH DISK SPACE ON YOUR PC.

Download the Patch (21.3 MB)-Upper English
Download the Patch (21.3 MB)-U.S. English

What is Upper English? - Upper English patches are intended for double-byte systems that require English commands to be in ALL UPPER CASE. These are typically systems that use Kanji characters.

Summary of problems fixed - Warehouse Manager

• 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)

In addition, this patch incorporates the 3.01.060 patch to resolve:

• 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)

 In addition, this patch incorporates the 3.01.050 patch to resolve:

• 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)

In addition, this patch incorporates the 3.01.040 patch to resolve:

• 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)

In addition, this patch resolves the following issues:

• 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.

In addition, this patch resolves the following issues:

• 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)

 

Summary of problems fixed - Analyzer OLAP Server

This patch resolves the following issue:

• Analyzer for the Web will no longer show views that are not active or not selectable when accessed through the Analyzer Desktop. (F4883)
• Form was not appearing in Analyzer for the Web when dynamic member selection was selected. The problem only occurred if the alias name had a qoute in it. (F6805)
• MCH3601 Pointer not set for location referenced error when trying to connect to Analyzer for the Web with an NLS PC with a non supported Code page. (F6360)
• The following error messages occured when trying to open or save a query/report to the ShowCase server, when per seat licensing is used:
  [ShowCase ODBC] ERROR OCCURRED DURING THE PER SEAT LICENSE CONNECT TIME PROCESSING - (1017).
  Error: MCH5804: (1033)
  Error RSC9129 THE MAXIMUM RUNTIME COUNT HAS BEEN REACHED FOR PER SEAT LICENSING IN LIBRARY SCWM300GA (1033)

In addition, this patch incorporates the 3.01.060 patch to resolve:

• The code was changed so that the "THE MAXIMUM RUNTIME COUNT HAS BEEN REACHED FOR PER SEAT LICENSING" message does not prevent further connections to the server. Previously, ending and restarting the AOS server was required. "(F5598)

In addition, this patch incorporates the 3.01.050 patch to resolve:

• AOS joblog did not contain any of the AOS specific log messages. "(F4456)
• "The following error messages occured when trying to open or save a query/report to the ShowCase server, when per seat licensing is used:
• [ShowCase ODBC] ERROR OCCURRED DURING THE PER SEAT LICENSE CONNECT TIME PROCESSING - (1017).
• Error: MCH5804: (1033)
• Error RSC9129 THE MAXIMUM RUNTIME COUNT HAS BEEN REACHED FOR PER SEAT LICENSING IN LIBRARY SCWM300GA (1033)" (F5312)
• "This is related to the issue of not having the proper security.    Since this problem has a work around, see resolution 9467, I would rather postpone any action on this until we have a strong business case. I went ahead and removed the *SECADM and *SAVSYS  special authorities requirements from STRSCTCP4.0 and STRAOSSVR 3.0/3.5" (F5998)

In addition, this patch incorporates the 3.01.040 patch to resolve:

• Analyzer For The Web locks up after view linking occurs and an Undo is attempted. " (F4896)
• Linking views in Analyzer for the Web, caused multiple copies of the linked view to be loaded when switching back and forth between views. " (F4897)
• Trying to open a view in Analyzer for the Web that contained UDAs, resulted in the following errors: Essbase error 1001071: Unmatched parenthesis in "LINK" command in Report. The requested analysis resulted in no data. The requested view could not be loaded (1009). " (F4975)
• Link information or traffic lighting from the previous loaded view appears in the information panel when the NEW view option is selected. " (F5010)
• 3.0 specific information was not preserved in the AOS CFG file during a restore with a 2.5 save. We now preserve that in formation.
  1. The problem: Some data in the 3.0 AOS CFG file does not exist in the 2.5 AOS CFG file. The data in question is the server CCSID. When we do a 3.0 restore using a 2.5 save, the AOS CFG file (3.0) is replaced the AOS CFG file saved from the 2.5 save which results in a AOS CFG file that does not have the server CCSID value. STRAOSSVR need to have this value present in order to function properly.
  2. The work around: If *YES is chosen for 'Restore AOS information', then choose *NO for 'Restore configuration file'. This will guarantee that the AOS CFG file does not get corrupt.
  If the restore operation has been performed and the 3.0 server lib is in a state where AOS will not start, then a SQL statement can be run to repair the AOS CFG file. At this point the AOS server should work just fine. This will need to be done if the first mentioned work around was not performed. " (F4796)
• After drilling down on a linked view in Analyzer for the Web and then undoing your drill action, you would occasionally receive an error message that the view could not be loaded. However, the view would be loaded anyway and you would occasionally end up with an extra tab for the view. This has been fixed. " (F5032)

In addition, this patch resolves the following issues:

• Fix the Analyzer Filter so that the Groups by owner option works. (F4051)
• Fix an issue in which the STRAOSSVR command would use corrupt space if it were run right after the install. (F3926)
• Change how connection requests on the AOS are handled to avoid hanging clients. (4122)
• Drill down and Link to a View, in Analyzer for the Web fails with an MCH3601 Pointer not set, error. " (F4725)
• Code was added to update the AOS information after a RSTSRVRINF while users were connected. (F1385)