KB Article 7940

Contact Tech Support

 Email Tech Support
 (250) 655-1766
 [7:30 - 5:00 PST]
Your Meeting ID will be Provided by a Rep.
Tech Support
Tech Support Home
Software Updates
Knowledge Base Search
Recent KB Articles
Product FAQs
Code Samples
Tech Blog
System Requirements
Installation Instructions
Support Testimonials
Contact us to...
Create a Ticket
Request a Free Demo
Suggest a New Feature
Submit Feedback
Upload a Large File
Other Services
Software Training
Professional Services

While working with a WebSmart program, I'm getting an error that a file is full (The maximum size has been reached for member). How can I address this problem?

Product: WebSmart ILE Type: Troubleshooting

WebSmart version 7.2 and earlier shipped with a number of files (mostly in XL_WEBSPT) where the maximum record limit was set to the default of about 13,000 records. Depending on how long you run WebSmart, the types of programs your create, and how many people use your programs, it's possible that at some point you may hit that upper limit.
The files on which you could hit this limit include:
  • XL_EXODUS/EXLOGF - Exodus log file.
  • XL_WEBSPT/PW_IDNF, PW_IDWF - Index files, used by WebSmart search index functions (and Nexus search).
  • XL_WEBSPT/PW_SESSF, PW_SVARF - Smurf files.
  • XL_WEBSPT/PW_TRNF - Transaction file.
  • XL_WEBLIB/PW_ARCF - WCM (WebSmart Change Management) archive file.
  • XL_WEBLIB/PW_LOGF - WCM log file.
The typical errors you could get look something like this:
I/O is not allowed because the program device or member PW_SVARF file PW_SVARF in library XL_WEBSPT is in error.
I/O error CPF5129 was detected in file PW_SVARF.
CPA5305 The maximum size has been reached for member
You can use the command DSPFD (e.g. DSPFD XL_WEBSPT/PW_SVARF) to confirm the current settings for your files.
At WebSmart 8.2 and higher, these files are shipped with a higher limit. However, IF YOU ARE UPGRADING FROM AN EARLIER RELEASE, THE FILES ARE NOT CHANGED AUTOMATICALLY BY THE UPGRADE PROCESS.
Solution 1:
The simplest, and probably the fastest solution to this issue is for you to change the files yourself. This is an example of the command you can use:
Some of the files may be locked by jobs or the Exodus subsystem, but keep track of which ones they are and try again when people are off the system, or just after an IPL. The other option is that you can selectively delete old records from these files, using SQL similar to this:
delete from xl_exodus/exlogf where exdate <20100101
If you feel you need to implement this solution, but aren't sure how to proceed, please contact Technical Support for guidance.
Solution 2:
If you have been using WebSmart since version 7.2 or earlier you can  avoid running into these limits by following these steps to increase the maximum file size to 10,000,000 records:
  1. Download and apply update W7200007P (this update has no prerequisites, and can be applied to any version of WebSmart higher than 7.2).
  2. To ensure all locks are released:
    2. End all web server instances that call WebSmart programs.
    3. WRKOBJLCK QSYS/XL_WEBLIB *LIB - End any jobs that have locks on files in XL_WEBLIB.
    4. WRKOBJLCK QSYS/XL_WEBSPT *LIB - End any jobs that have locks on files in XL_WEBSPT.
    5. WKROBJLCK XL_EXODUS/EXLOGF *FILE - End any jobs that have locks on EXLOGF.
  3. Run the command ADDLIBLE XL_WEBLIB
  4. Run the command UPDPFSIZE
If you are concerned about a particular file and don't want to shut everything down, you may be able to get away with just clearing locks on the problematic file and then doing (3) and (4). You may get a message saying that some files were not updated, and you can review the job log to determine if the files you are concerned about were updated or not.

Rate This Article

Did this example help you to achieve your goal?
 Yes  No  Don't Know

Enter additional comments below.   If you want to hear back from us, include your contact information.

Email Address:
Please enable JavaScript in order to rate this page.