181
Content Navigator / Re: Start/Stop of ICN
« on: June 10, 2020, 01:42:21 PM »
I've always done it through websphere, restarted the JVM.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
182
Tips and Tricks / Re: Is there a way to find out the load date for a specific document in ondmeand?
« on: June 01, 2020, 06:04:57 AM »
what about using the system log? Can you view the document in the thick client?
Right click, take the partial load ID and search for it in the message field in the system log folder, along with msg num 88
Right click, take the partial load ID and search for it in the message field in the system log folder, along with msg num 88
183
Announcements & News / Re: z/OS Level 2 Support Changes - Hail and Farewell
« on: May 12, 2020, 09:22:37 AM »
I've worked with Marina for almost 10 years on several PMR's and general questions. Best of luck to her!
184
MP Server / Re: AWS S3 configuration with third party S3
« on: April 28, 2020, 08:56:46 AM »
However, there is bug in Dell/EMC ECS as well as in IBM CMOD; this is represented silently not removing / unloading documents from storage while index is removed. The only indication is arssockd trace or by using aws cli to observe that documents are not removed while indices are gone.
Heads up, this issue also exists in IBM Cloud Object Storage!
185
OD/WEK & JAVA API / Re: ODWEK 9.0/Server 10.1
« on: April 22, 2020, 12:51:24 PM »Oh yes I know. I've been begging for the web services group to get off 9.0 since last October. I'm even willing to let them go to 9.5 just so I get the Server software to 10.1. It's what has been holding me back. That's why I asked if anybody was possibly running 9.0 ODWEK against 10.1 Server.It's been a few months since I've referred to the compatibility matrix, but.
A fellow engineer I worked with was able to get it working.
Since our old 8.5 ODWEK servers were on Solaris, we couldn't goto 9.5 because solaris support was deprecated. (Or so they thought).
In our test lab, my manager successfully made calls from ODWEK 9.0 on Solaris to CMOD 10.5.0.4 on Linux. He's also convinced that 9.5 ODWEK ODIApi.jar can be successfully used on extremely old Solaris boxes.
I don't think ANY OF THIS WAS SUPPORTED BY IBM!
186
Other / Re: CMOD & RHEL
« on: April 10, 2020, 11:43:49 AM »
I've never seen that specific error, Did you run prereqcheck? I forget the name of the executable. It's in the /server directory. It will list out a bunch of yum packages required for db2.
https://www.ibm.com/support/pages/node/4738575
prereqSAM: Using default prerequisite checking on the following
rpm package: 'glibc-locale-32bit' 'x86_64'
prereqSAM: Error: The following rpm package is not installed:
'glibc-locale-32bit' 'x86_64'
https://www.ibm.com/support/pages/node/4738575
prereqSAM: Using default prerequisite checking on the following
rpm package: 'glibc-locale-32bit' 'x86_64'
prereqSAM: Error: The following rpm package is not installed:
'glibc-locale-32bit' 'x86_64'
188
Other / Re: CMOD & RHEL
« on: April 08, 2020, 01:22:19 PM »
I have it running on a VM that I use for testing and it runs with no issues.
189
MP Server / Re: arsdoc retrieve too slow AIX 7.1 CMOD 9.5 DB10.5
« on: March 26, 2020, 05:52:21 AM »Hi jsquizz,
Nothing really is observed, only the exaggerated recovery time for the documents for the application group PAN_EstadoCuentaRetail.
I attached the file from SystemLog where "Message" column can be filtered by:
PAN_EstadoCtaTC (fast retrival time)
CRI_EstadoCtaTC (fast retrival time)
PAN_EstadoCuentaRetail (slow retrival time)
thanks in advance!
Was looking down the path of excessive logging, an issue I've seen bite two clients in the past and cause tons of issues. Looks like you're not doing it and your system log is clean.
I removed the attachment because it had IP addresses listed, please remove them next time prior to uploading/posting any log messages. Thanks
190
MP Server / Re: arsdoc retrieve too slow AIX 7.1 CMOD 9.5 DB10.5
« on: March 24, 2020, 01:37:17 PM »Hi,
Sorry for refloating the thread, but we still have the problem.
We have detected that the arsdump program varies too much in the execution times, it does not matter if it is from the ICN, the Windows client or the arsdoc.
Search is fast for all applications, queries in DB apparently respond the same way for all applications. But it takes almost 3 times longer when recovery is invoked with the arsdump program (from ICN, Windows Client, arsdoc).
What can we do to investigate the cause of this? Is there a way to modify the execution parameters of arsdump?
Anything else happening in your system logs when these retrieves are slow?
191
MP Server / Migration question, each load is 1 doc + arsmaint segment date Question
« on: March 02, 2020, 09:04:52 PM »
got a 2 questions, hopefully quick.
I'm working on a migration (100 million docs..) and The client loads documents one by one. Each 87 record contains a single record.
It looks like this is the case for all of their documents after combing through their logs. My script I plan on writing will do an arsdoc and retrieve all files based on doc_name, but I am wondering since it's going to be running rapidly generating millions of files at a time, how bad this could get, taxing on resources.. This is my only option at the time.
I did this approach about a year ago and it worked perfect, but it was a mixture of documents like this and some single AFP files that had 30000 docs per, no issues there.
Next part of this going back to part 1, I'm going to be extracting this and reloading it into a 10.1 system. They are currently using "date loaded" as their segment date and that's what arsmaint is using to expire on.
Any suggestions on how to handle this since I am re-ingesting, and basically resetting the clock. They hinted to me that the last time they were going to try this they ran into this, So..they just stopped..
Thanks all!
I'm working on a migration (100 million docs..) and The client loads documents one by one. Each 87 record contains a single record.
It looks like this is the case for all of their documents after combing through their logs. My script I plan on writing will do an arsdoc and retrieve all files based on doc_name, but I am wondering since it's going to be running rapidly generating millions of files at a time, how bad this could get, taxing on resources.. This is my only option at the time.
I did this approach about a year ago and it worked perfect, but it was a mixture of documents like this and some single AFP files that had 30000 docs per, no issues there.
Next part of this going back to part 1, I'm going to be extracting this and reloading it into a 10.1 system. They are currently using "date loaded" as their segment date and that's what arsmaint is using to expire on.
Any suggestions on how to handle this since I am re-ingesting, and basically resetting the clock. They hinted to me that the last time they were going to try this they ran into this, So..they just stopped..
Thanks all!
192
Other / Re: Upgrading TSM using Centera
« on: February 27, 2020, 02:11:07 PM »Hi,
Perhaps a bit too late for your project now.
I did the TSM migration with Centera between Solaris TSM 5.5 and Linux (RHEL) TSM 7.1 (not in SSAM mode)
The TSM migration was done over the network using this https://www.ibm.com/support/knowledgecenter/en/SSGSG7_7.1.0/com.ibm.itsm.srv.upgrd.doc/t_srv_upgrd_dbmove_net_s4.html as guide. As this was my first migration I did have a few try and fail attempts, but at the end it worked.
Sure, you would need to take the same PEA file (the key file for your Centera pool). To migrate CMOD DB2 you could use db2move or write a simple script to do export to IXF and load from IXF. It is fast and does the endian conversion.
If you would prefer data export / import the method described by Alessandro is the right one in essence. You could consider running multi process/thread your export/import to gain speed.
Hope this helps,
N.
Hi Norbert, Just wondering about this post again, what approach did you use to migrate the database.
193
MP Server / Re: OnDemand Server Sizing help for Linux system
« on: February 27, 2020, 01:38:55 PM »We need to configure a CMOD system to run on Linux. It's a sizeable requirement with the system having to satisfy a number of CMOD queries/retrievals per second at peak times. We need to size this system; that is decide on how many hardware processors, which processors and how much memory is required to give satisfactory fast response for the users.
Can anyone kindly assist us with sizing advice, rules of thumb, tools, spreadsheets, etc...?
Many thanks in advance. Olivier Hayot / Chris Corfield
This may or may not be helpful.
https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=E877A7C04AB511E5BB33E7199C786195
Check the "Hardware" Tab
194
Report Indexing / Re: PDF Indexing - Page Piece Dictionary
« on: February 12, 2020, 08:13:34 AM »Just curious if anyone has performed some timing differences between normal PDF indexing (triggers and fields) versus CMOD indexes in the PDF Page Piece Dictionary?
We have some very large PDF files 500,000 - 1,000,000+ pages that currently take about 3-4 hours to index and load.
I've seen bud demo PPD's several times at workshops. He did it on a VM on his laptop and it was very very quick.
Assuming on a RHEL box with plenty of CPU/Memory, it will FLY. I myself, have not had the chance to play with it unfortunately.
195
MP Server / Re: Can CMOD v9.5 cooperate with TSM v8?
« on: February 03, 2020, 11:46:26 AM »Of course, I feel the need to re-iterate that CMOD v9.5 goes out of support April 30th, 2020 -- so you should be focusing on your move to v10.1, and not supporting a version that's going out of support!
That's why I created this topic - we are analyzing different scenarios of upgrade to 10.1
Thanks for replies
For what its worth, as far as using an "Old Version" of CMOD, and a "New Version" of TSM, I ran CMOD 8.5 and TSM 7.1 for a long time in a QA environment with no issues. CMOD was on AIX, TSM was on a remote RHEL server. I'm sure a lot of these scenarios will Work theoretically, even outside of the compatibility matrices-
Example- Somehow made ODWEK 10.1 work with a 8.5 Library server...against ALL my suggestions not to!
but most of them are not supported by IBM.