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.

Messages - Darrell Bryant

Pages: [1] 2 3 4 5 6
Which platform are you using?
Archived Storage Manager (ASM) is the native storage manager used by Content Manager OnDemand for i.
ASM supports NFS mounted drives for long term archive storage.

MP Server / Re: Loading reports online from the AS/400 to CMOD MP
« on: February 29, 2024, 07:34:06 AM »
Hello Olivier,
The ODi development team has documented the setup for archiving from IBM i to other platforms.
See support item:
You might consider signing up for the OnDemand Newsletter, the 2Q2023 issue referenced an update to that support item.
To sign up for the newsletter, drop me an email,

General / Re: Latest IBM OnDemand Training
« on: July 14, 2023, 05:24:07 AM »
IBM's education partner for Content Manager OnDemand is enChoice.  Information on their education offerings can be found at:

It is  messaging audit rule to store any data that to be encoded  . .  If there is No other option We should opt for loading original xml data  itself ,

Content Manager OnDemand supports encryption at rest.

« on: May 04, 2023, 08:13:27 AM »
The Content Manager OnDemand Best Practices Guide, found here:
recommends a setting of 120000.
Absent any newer information, I would start with that recommendation.

Report Indexing / Re: Failure with special character
« on: March 03, 2023, 02:11:56 PM »
Any change to ARS.CFG requires a restart of arssockd.

Report Indexing / Re: Failure with special character
« on: March 03, 2023, 06:10:41 AM »
If you have a test environment, you might experiment with the ARS_USE_OLD_STYLE_CASE parameter in the ARS.CFG file.

Use the following if upper casing expands the number of characters, for example the German Ezett () expands to SS with the new style (ICU) upper casing
In the ARS.CFG:
# Use old style upper casing to prevent character expansion

When value of ARS_USE_OLD_STYLE_CASE is:

(0) - then we do all upper/lower casing in UTF-16 (no change)
(1) - then we do all upper/lower casing in OS level codepage we are running under (no change)
this was really added just to prevent the german sharp s () character not expand to multiple bytes (which it does in UTF-8)
(2) - we now upper/lower case in UTF-16 (however we specifically prevent from being done).
We then convert this back to the native codepage (of the data) - then compare to the original string that was provided to us.
If we find any characters that are not found (e.g. ICU will change the char to be a substitution char),
we will put the original char back into the upper/lower case string. If for any reason this fails we will
default as if the ARS_USE_OLD_STYLE_CASE=1 for that string.

Report Indexing / Re: Character removal question
« on: February 22, 2023, 09:49:44 AM »
Character removal on the Application Group > Field Information tab is used to 'cleanup' search values entered by the end user before querying the database.
From the Administrator Client help text:

String Embedded. You can define from one to eight characters that Content Manager OnDemand removes from search values typed by the user before querying the database. Content Manager OnDemand can remove embedded, leading, and trailing characters. For example, suppose you define a field to store index values that contain phone numbers. The values in the database contain only numbers. That is, the values do not include the dash character. However, when users query the database with a phone number, they typically type search strings such as 303-555-1212. Since the database values do not include the dash character, Content Manager OnDemand would not find a document to match the query. However, you can use the Embedded field to enable users to type values that include the dash character. Simply type a dash character in the Embedded field. That way, the user can type 303-555-1212 (or 3035551212) in the search field. Content Manager OnDemand removes all occurrences of the character specified in the Embedded field from the search string typed by the user before querying the database.

z/OS Server / Re: z/OS CMOD Postprocessor documentation -- where is it?
« on: February 20, 2023, 01:46:13 PM »
The documentation for using postprocessor parameters with Content Manager OnDemand for i is available at:

Content Navigator / Re: ICN Architecture
« on: January 31, 2023, 06:06:15 AM »

Report Indexing / Re: Posting date issue
« on: October 03, 2022, 10:59:13 AM »
Are you running ACIF on MP or z/OS? ACIF on MP supports regular expressions to locate triggers and fields. This provides additional flexibility in locating them in your report. As I recall, ACIF on MP also support specification of a column range for triggers, but I have not found documentation on that.

Hi Helle,

The splash screen shows the major version (10.5) but not the fix pack level.
You need to create the product.inf file to prevent the standard About panel from displaying.
Also, when logged on the client displays the server version & fix pack on the Status bar at the bottom of the screen. This can be set on or off from the client. From the menu select Options > Display Server on Status Bar.

It is possible to customize the About dialog box. See the 2Q214 OnDemand Newsletter, page 4. The newsletters are available here:

It is also possible to not have the splash screen displayed when the client starts. See the OnDemand documentation for details:

MP Server / Re: log4j question within jars dir
« on: August 03, 2022, 10:20:16 AM »
Do you receive the OnDemand newsletter? The 2022Q1 newsletter contains details and links on the log4j issue and also lists which components of OnDemand are affected at each server version.  You can access the newsletters here:

Announcements & News / Re: SECURITY - IBM FLASH update on Log4j
« on: July 21, 2022, 11:56:54 AM »
Server level is the fixing level. As is Or any higher levels.

Or you can patch it manually if you don't want to run the current server level.

Pages: [1] 2 3 4 5 6