MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » August 2014

Re: IBM Content Manager for iSeries problem



fixed

Dave,

Did you get this worked out?

Years and years ago, I worked with a customer who was having a similar problem. We fixed it by changing the paging attributes of Windows.

There's a piece of the code in the VI client that relies on an old OS/2 module for memory management. That module allocates memory without using the Windows API. When Windows swaps memory pages to make room for, say, another program to be loaded, the pointers to the memory VI client allocated no longer point to valid locations. The old OS/2 module doesn't handle this well and it just stops. The rest of Windows will work okay, but the VI client won't do anything as it has locked out the Windows interreputs.

Paging can be initiated due to many different cicumstances. Installing a new start up program on your Windows machine might suddenly change the paging behavior. Changing the network protocol stack might do it.

On XP, you change the paging strategy by going to the System Properties dialog, choosing the "Advanced Tab", clicking "Settings" within the "Performance" box, choosing the "Performance" tab within that dialog, then clicking "Change" within the "Virtual Memory" box of the "Performance Options" dialog. Within the "Virtual Memory" dialog that pops up change from "System managed size" to "Custom size" and make the initial size and maximum size the same. This will allow paging, but stop Windows from expanding the paging file. Just set it big enough to accomodate all the pages that might roll out. I make it the same size as the system memory. This works well and I am able to run as many programs as I want without getting "out of memory" errors. For example, on this old Windows XP machine with 4GB of memory I have Initial and Maximum size set to 4092MB.

As an extra bonus, if you have more than one disk in your machine, put the paging file on a different disk than your Windows and Program Files paths. That'll give you a performance boost when paging occurs during a program load.

Dan Kimmel


----- Original Message ----- From: "Dave DeBoe" <DDeBoe@xxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, August 07, 2014 1:49 PM
Subject: RE: IBM Content Manager for iSeries problem


Below is the VI400 log that logs all connections to Content Manager. We diffidently have a communication issue. This user connected to Content manager at 09:08:53 and she was able to view documents. Then, at 11:01:27, she had the error that we have been seeing where the only way to get them to view documents again, is to re-boot their machine.


CM/400 5.1 Initialization (ekdws.dll created Jun 17 2004 09:04:43)
Environment Variables:
VI400_CONFIG_PATH (NULL)
VI400_LOG_PATH (NULL)
VI400_LOG_PERFORMANCE (NULL)
VI400_LOG_TRACE (NULL)
VI400_LOG_DATA (NULL)
VI400_LOG_STORAGE (NULL)
VI400_LOG_BUFFER (NULL)
VI400_LOG_LOCKS (NULL)
VI400_LOG_LOGON (NULL)
VI400_LOG_ALL (NULL)
VI400_DUMP_LIMIT (NULL)
CommInit ekdwscma.cpp 492 2014/08/07 09:08:53.977 T=3048
Connecting to HOST=172.20.1.51 PORT=31015
SimWmGetListWorkBasketInfo ekdwswm.cpp 1869 2014/08/07 09:08:54.290 T=3048
Malloc ItemNameExtStruct, 3
CommRecv ekdwscma.cpp 992 2014/08/07 11:01:27.472 T=3048
recv3 failed rc=10054
CommRecv ekdwscma.cpp 1079 2014/08/07 11:01:27.472 T=3048
WARNING: Extended length=0 Expected=65 Received=2
SimLibGetItemInfo_Snapshot ekdwsitm.cpp 709 2014/08/07 11:01:27.503 T=3048
ERROR: VI400 error code 6259 SIM_RC_COMMUNICATIONS_ERROR
SimLibGetItemInfo ekdwsitm.cpp 491 2014/08/07 11:01:27.503 T=3048
ERROR: VI400 error code 6259 SIM_RC_COMMUNICATIONS_ERROR

Dave DeBoe | Information Technology | Arapahoe County Government | ITIL Foundations V3 Certified
13101 East Broncos Parkway, Centennial, CO 80112 | p. 720.874.3982 | DDeBoe@xxxxxxxxxxxxxxx


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz
Sent: Thursday, August 07, 2014 9:40 AM
To: Midrange Systems Technical Discussion
Subject: Re: IBM Content Manager for iSeries problem

for PC Client, we are using IBM Content Manager for iSeries Client for Windows V5.1 version 5.1.0.14021 Even though the client says 5.1, the version on system is 5.3 I don't know if this client compatible with your version This is the fixpack site for the client
http://cp.mcafee.com/d/1jWVIg6xESyNssMCVtdYTsSDuWb5SkT7PqtXEInpj7e6QXIIcLTopKrjhpjojpvjodE8ugHUaSeHqjHV6FDBPuNRritv8RcYKruZ0QsI-O_R-j7efcLtuVtdeZ-ouvov7sJteOaqJQTel3PWApmU6CQjr1K_8I9LfzAm4PhOrKrtCIBCbdA3VmV0D_i8aYLCQoLv5ERgrJeCmH2vMCHId8_73bXdYIvbUjOk9_6iEw5x05DOFek2fb8eCRp8hS17OVVsxlK5LE0513O5veSeHqjHV6FDBMkH92eM8_OVIQsKfL6MnWhEw3hArd40Bm4_xcQg3uMQzYjh0Xm9EwAcv6nQd42QqA3_ldIcCYK74
Several fixes mention fixing pc "freeze".
Jim



On Thu, Aug 7, 2014 at 10:28 AM, Dave DeBoe <DDeBoe@xxxxxxxxxxxxxxx> wrote:

Hi Jim,
The error code we are seeing is FRN6259A, which according to the IBM
Content Manager for iSeries Messages and Codes book, this is a problem
with the communications isolator. The action for this code is to re-boot the pc.
Which is what we have to do now every time this error comes up. I
would have to say that the images that are being scanned in via Kofax
are good, because once the user re-boots the PC, they can view that
same document using Content Manager. I still keep coming back in my
mind that this problem has something to do with our firewall changes,
but if it were a problem with that, then I ask myself, after they
re-boot, why can they view the same document that they were getting
the error before the re boot. It seems that by re-booting the pc's, it
'clears' whatever problem there was, but only until the next time the
pc locks up again later in the day with the same error. We are having
this error on both Windows 7's and Windows XP machines.

Question, the product IBM Content Manager ImagePlus Workstation
Program, is that a replacement for IBM Content Manager?

Thanks.

Dave DeBoe | Information Technology | Arapahoe County Government |
ITIL Foundations V3 Certified
13101 East Broncos Parkway, Centennial, CO 80112 | p. 720.874.3982 |
DDeBoe@xxxxxxxxxxxxxxx


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
midrange
Sent: Wednesday, August 06, 2014 8:24 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: IBM Content Manager for iSeries problem

Dave,
Our company is still heavily using Content Manager (several Tb's of
images), and even use Kofax scanning for some of our input, but we
have managed to get to V5R3 (5722-VI), which is still a supported
version and occasionally ptf'd. I think it's the last version before
the On Demand versions.
We are at OS V7R1 with no problems with it. The Messages and Codes
manual
http://cp.mcafee.com/d/5fHCN0p3x0edEIn7czDASnPtPqtXEInpjsvdFTKyNtBcsUr
jKOMO_txCVJd5BdxdBZdwSwxV2LwHoWJFeLAqCundX7lJ9RYzkPOVJVBDQ_pvW_8IfICzB
7HTbFFzDejvpvspVqWtAkRrELYG7DR8OJMddECPhOrLOb2rPUV5xcQsCXCM0qPp0-h1RrA
2vZ8wHO-uISgFyO3Kmj78EIzHYIwWrlAx7o4vbDBO5mUm-w0k4f8lYXoWJFeLAqCun1iIA
8X0z_bCQmkXCzAS2NF8Qg1EOdCy0iH2vMCq81Loqh-9EwtH4Qgi6fzbW6y1qdi1_GCS6ju
gIz Has no mention of EKDVIDSP but multiple errors for "Invalid item"
all revolving around a similar issue: Invalid item or folder value.
To be more specific, it would help to have the "FRN" error code, like
FRN6223A.
My first guess, not knowing the underlying error code, is that a
folder has been deleted or damaged and your users only hit is
occasionally, and have the error.
2nd guess is the image itself - and I need to question "nothing has
changed except the firewall", but consider this:
Your OS release and ptfs have (hopefully) changed over 13 years.
Kofax has most likely changed. (see issue #2 below) Windows on the
desktop changed (every Windows Update, plus anti-virus, software
firewalls if used, Win 98SE, 2000, XP, Vista, 7, 8 (all with various service packs).
Are you getting the images from other sources besides Kofax? See issue
2 &
3

Where we have had (and resolved) issues is:
1. settings in the pc client as to which viewer is called first - our
CM client has 2 or the viewers and the order can be an issue (see 2
and 3) - IBM has several docs online for this issue - and it does
represent itself as a freezing program 2. tiff compression versions -
there are many tech discussions of tiff compressions (many times all
the postings we have for things not working as expected), working or
not working with various viewers (same for pdf) 3. color images
(similar to issue 2)

We import many images through edi like processes (medical bills), so
we don't have full control of the creation of the images. We've had to
write Win code (C# I think) to take tiff images, determine the
compression, and rewrite them in a compression we can view.

Btw- if you are still using the 3995 Optical jukebox, we just switched
to Virtual Optical and it works great (once you get the rules down).
Content Manager sees no difference between real optical and virtual.

Dave, if you need a longer discussion offline, we can do that.

Jim Franz
Key Risk Insurance



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://cp.mcafee.com/d/5fHCNESyNssMCVtdYTsSDuWb5SkT7PqtXEInpj7e6QXIIcLTopKrjhpjojpvjodE8ugHUaSeHqjHV6FDBPuNRritv8RcYKruZ0QsI-O_R-j7efcLtuVtdeZ-ouvov7sJteOaqJQTel3PWApmU6CQPr1K_8I9LfzAm4PhOrKr01DOFeDaOgzI2fYLwCHIcfBisEeRNmi4twhYKurlAx7o4vbDBO5mUm-w0k4f8lYXoWJFeLAqCun1iIA8X0z_bCPhOU-Yr1vF6y0d6hIQg2loj-4Ph0dX3ifNd43JoCy2gNYpvgQgbhGgfZkSMOrBepm
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://cp.mcafee.com/d/5fHCMUe4x8SyNssMCVtdYTsSDuWb5SkT7PqtXEInpj7e6QXIIcLTopKrjhpjojpvjodE8ugHUaSeHqjHV6FDBPuNRritv8RcYKruZ0QsI-O_R-j7efcLtuVtdeZ-ouvov7sJteOaqJQTel3PWApmU6CSjr1K_8I9LfzAm4PhOrKr01X6NehD-lAx7o4vVv5p8hS17OVVJmi4twhYKun8lrxrW01ggYxnPJzGSAW-hGpVs5aOgzI2fYKrd7bzXNI5-Aq80Qp6Ph09lxfUjd40TId8_4QgeRyq8937NBZ3h0J6F0_Rjr39JTtSdKgjN9PH.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact