System requirements for IBM® Content Manager OnDemand beginning with version 10.5.0.11

https://www.ibm.com/support/pages/node/7249695

Requires newer levels of pre-req and co-req products.

In addition, the following product components are not planned to ship with Content Manager OnDemand version 10.5.0.11 and later. Note that all of these components have supported 64-bit equivalents that will continue to be provided.
               - OnDemand Windows Client (32-bit)
               - OnDemand Windows Administrator (32-bit)
               - OnDemand Windows Monitor (32-bit)
               - Content Manager OnDemand Web Enablement Kit (ODWEK) Java APIs (32-bit)
               - ARSACIF (32-bit; Multiplatforms only)

Revised technical information: IBM Content Manager and IBM Content Manager OnDemand

https://www.ibm.com/docs/en/announcements/revised-technical-information-.

For CMOD, affects Full Text Search and CMOD 10.5.0.11 to be available 3Q26.

ARSEXOAM running slow?

UO03612 PH66598 ARSEXOAM may run long - A DELETE SQL statement was issued with a WHERE clause that may result in a tablespace scan.

Has anyone had to implement LDAP across multiple base DN's? (Since it's not supported OOB with cmod)

If so, what type of solution did you use? Global Catalog?

I actually tried doing this on a redhat system about 2-3 years ago and for whatever reason I couldnt get it to work, but- It was a POC.

I essentially backdoored it with a cronjob that would run every 5 minutes and also act as a monitoring script

Db2 Running? Good.. No? Start!..sleep
ARSSOCKD Running? Good.. No? check DB2-> Start
ARSLOAD(s)/ARSJESD Running? Good.. No? Check arssockd-> Start!

That was the best purpose because I also added logic to where if it failed a second time in X minutes, to send out an email/page. So within 5 min of a server being booted, it would come up.

My Unix guys are bugging me to use systemd instead of init.d to start and stop CMOD on my new RHEL8 server. I don't know what exactly I'm supposed to do and I figured I'd start here with the user group to see if anyone was successful in using systemd.
We currently have a script that starts the DB instance, then arssockd, then arsjesd, wait 60 seconds then start arsload as a daemon.
The stop part stops arssockd and end the DB instance.

If anybody has successfully done it, let me know and point me in the direction of resources.

Thankyou Justin.

Good point on the double filenames.

Regards

Michel

Only improvement I'd suggest is an if-statement that checks to see if the new filename already exists.  Otherwise, you have the same issue as arsdoc -- it will happily overwrite any existing file with a different file that has the same metadata.

Again, if you can do some pre-checking on your metadata to ensure there's only one document for your criteria, then you avoid the whole issue.

Otherwise, I'm glad to see you got something that works, and thanks for sharing your solution!

Take care.

-JD.

Thank you Justin,

Managed to do with this script:

for i in `ls TEST*|grep -v pdf`
do
/usr/lpp/ars/afp2pdf/afp2pdf -o /tmp/cmod/michel/$i.pdf /tmp/cmod/michel/$i 2>/dev/null
CONS=`arspdump -f /tmp/cmod/michel/$i.pdf |head -36|tail -1`
A=`arspdump -f /tmp/cmod/michel/$i.pdf|head -57|tail -1` (get part of the date)
B=`arspdump -f /tmp/cmod/michel/$i.pdf|head -60|tail -1` (get part of the date)
C=`arspdump -f /tmp/cmod/michel/$i.pdf|head -63|tail -1` (get part of the date)
NEWDATEFMT=`echo $A$B"20$C"|sed "s/\//_/g"`
echo $NEWDATEFMT
echo $CONS
mv $i.pdf "$CONS"_"$NEWDATEFMT".pdf
done

This is the output (extract)

-rw-r--r--    1 root     system         4025 Sep 18 10:40 SMK8042_4_07_2016.pdf
-rw-r--r--    1 root     system         4025 Sep 18 10:40 SMK8033_4_07_2016.pdf
-rw-r--r--    1 root     system         4010 Sep 18 10:40 SMB1597_9_07_2016.pdf
-rw-r--r--    1 root     system         4034 Sep 18 10:40 SMB1601_9_07_2016.pdf
-rw-r--r--    1 root     system         4044 Sep 18 10:40 SMK9775_8_07_2016.pdf
-rw-r--r--    1 root     system         4034 Sep 18 10:40 SMB1600_9_07_2016.pdf
-rw-r--r--    1 root     system         4077 Sep 18 10:41 SMK9814_8_07_2016.pdf
-rw-r--r--    1 root     system         4034 Sep 18 10:41 SMB1603_9_07_2016.pdf
-rw-r--r--    1 root     system         4034 Sep 18 10:41 SMB1514_9_07_2016.pdf
-rw-r--r--    1 root     system         4013 Sep 18 10:41 SMK8047_4_07_2016.pdf
-rw-r--r--    1 root     system         3932 Sep 18 10:41 SMK7924_3_07_2016.pdf
-rw-r--r--    1 root     system         4078 Sep 18 10:41 SMK9818_8_07_2016.pdf
-rw-r--r--    1 root     system         4077 Sep 18 10:41 SMK9824_8_07_2016.pdf


Regards

Michel

If you want custom filenames, I think your best bet is to do that after the fact with some custom code.  Writing it yourself allows you to do more error-checking, since arsdoc will silently over-write output files if you happen to have multiple documents with the same metadata.

If you can confirm that's not an issue, I think you can use field names in parenths to get what you want:
  arsdoc <options>   -o "(consignmentnr).(reportdate)"


-JD.