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 - mayank81089

Pages: [1] 2
1
Understood system is working as expected.

Cache expiration is run using the arsmaint -c command.
OnDemand will expire storage objects from cache if all of the following conditions are met:
The maximum cache threshold is reached for a cache file system. This is specified when you run arsmaint with the '-x' parameter. The default value is 80%.

2
Hello,

We have observed that since we have gone live with CMOD 10.5.0.5 which was an upgrade from CMOD 8.5 the arsmaint utility is not working. As the cache storage size has increased exponentially, we have TSM client node registered as our archive storage solution however we are also maintaining one copy of the documents inside cache folder as well that is for 90 days only. We tried opening documents which have been stored in CMOD for more than 90 days but still see them coming from cache node instead of TSM client node. are there any changes in the utility command parameters in new version?  prior to upgrade it was working fine

checked the permission and ownership of arscache/cache1 folder and everything seems correct as per IBM documentation.

parameters used in arsmaint command -cdrs

documents are not getting flushed from cache folder.

Thanks,
Mayank


3
Hi Russel,

We tried to use search with SQL but it was blocked at the firewall due to where , or & and keywords in the query is there any workaround it ?

Wa


4
Hello Members,

is there any possibility to allow AND and OR at the same time in the search ?

One way of doing it using SQL API in IBM CMOD REST but it is being blocked by the server firewalls as it contains where OR and AND keywords hence checking if someone has achieved it already through IBM CMOD REST search API

Warm Regards,
Mayank

5
MP Server / Re: OnDemand on Linux fails with Higher Version (CMOD 9.5)
« on: November 30, 2023, 03:34:24 AM »
Hi Justin,

When you say setup CMOD in container. Did you follow any guide to install CMOD in containers if you can please share some information?

Mayank

6
MP Server / Re: AFP2PDF conversion possibility using IBM CMOD REST APIs
« on: August 10, 2023, 12:55:01 AM »
Thanks Spond,

It worked really appreciate your suggestion.

Thanks,
Mayank

7
MP Server / Re: AFP2PDF conversion possibility using IBM CMOD REST APIs
« on: August 09, 2023, 02:36:19 PM »
Thanks Much Spond

Really great to hear from you and addressing my concern, I am gonna try this as next step

Thanks,
Mayank

8
MP Server / AFP2PDF conversion possibility using IBM CMOD REST APIs
« on: August 09, 2023, 11:39:21 AM »
Hi Team,

We are integrating CMOD 10.5 REST APIs into a custom application to retrieve AFP documents from CMOD and we want to transform these APF documents into PDFs before sending it to the caller of the document.

Has anyone tried anything like this before with REST APIs if you can suggest the possible options that will be great.
 I understand that this is possible with ODWEK APIs with generic transform interface which allows us to leverage RICOH afp2pdf to transform it but I am not sure how to achieve the same with CMOD REST APIs

Any suggestions will be greatly appreciated.

Thanks,
Mayank 

9
MP Server / Re: CMOD 8.5.0.1 performance issues post machine restart
« on: August 07, 2023, 08:47:14 AM »
Seriously?  They're not even on the latest fixpack for CMOD v8.5?

Use this as an example as to why they should upgrade and get support reinstated.

-JD.

Yeah I have given the suggestions  ;)

However I have figured out the problem with CMOD symbolic links.

10
MP Server / CMOD 8.5.0.1 performance issues post machine restart
« on: August 02, 2023, 10:11:53 AM »
Hello Everyone,

I have come across a very wired situation where in CMOD 8.5 has started responding very slowly post AIX LPAR reboot.
Document retrieval is taking 3-4 minutes to open the document.

I understand that it is out of support version but it seems customer is not in the mood of upgrade. Any suggestions would be greatly appreciated.

Can anyone suggest things to be checked in this case ?
 
Thanks,
Mayank

11
Hello All,

We have successfully moved on-prem TSM storage to OCI cloud successfully and it is also accessible through CMOD 10.5

Thanks

12
Thanks Lars,

Actually the problem was with the date format we figured it out and it resolved the problem

13
Hi Team,
We are currently facing issue with one of our scripts. The primary area in which we are seeing this issue is the "arsdoc" query when it gets/extracts the documents from disk.
The snippet goes like below:

 

    /opt/IBM/ondemand/V10.5/bin/arsdoc \
      get -h $HOSTNAME \
          -f "$FOLDER" \
          -i "WHERE tstcrt_number||cast_number in (select tstcrt_number||min(cast_number) from root.$TABLE group by tstcrt_number) AND ARCHIVE_DATE = '$PREVMAXEXT' AND BS_CSI_No = '$CSI'" \
          -a \
          -d $WORK_DIR \
          -o ctbodctc.afp \
          -u dsgrep \
          -p /opt/IBM/ondemand/V10.5/config/ars.stash \
          -v >> $LOG 2>&1

 

Note : This arsdoc function gets/extracts data based on a filter criteria that takes customer_number into consideration.

 

Please note that the sql query in above arsdoc function is using "concat" or "||". The exact same query is running perfectly fine on AIX in our current production system.
However, when running this in Linux system in our new production machine



Error in Linux :
2023-03-31 20:19:04.331935: ARS6117I Querying database with SQL string 'WHERE concat(tstcrt_number,cast_number) in (select concat(tstcrt_number,cast_number) from root.RQD1) AND ARCHIVE_DATE = '03/30/2023' AND BS_CSI_No = '3147843''

 

2023-03-31 20:19:04.354335: ARS6085E Search unsuccessful

 

2023-03-31 20:19:04.354406: ARS6034W No hits were found that matched search criteria.

 

2023-03-31 20:19:04.354406: ARS6011E The error occurred on line number 1.

 

2023-03-31 20:19:04.354971: ARS6026I arsdoc completed.
---------------------------------------------------------------------------------------------------
Error in ondemand client :
2023-03-31 23:49:04.238311    DSGREP      130835221    Error    No        13    DB Error: [IBM][CLI Driver][DB2/LINUXX8664] SQL0420N  Invalid character found in a character string argument of the function "DECFLOAT".  SQLSTATE=22018  -- SQLSTATE=22018, SQLCODE=-420, File=arsdoc.c, Line=3563    system

14
Thanks Justin 

We have deployed Spectrum protect running on RHEL VM which is in OCI cloud

We can load new documents and retrieve them  but when we moved history data from exiting on-prem TSM to cloud Spectrum protect it is failing with below error
TSM Error ANS1302E (RC2) No objects on server match query return code = 2
object > 9077466HAAA  in application group >UXB> not found in node >ODNODE>

did anyone come across such errors in the past
we have upgrade CMOD and TSM

15
Hello,

Did anyone try to use OCI with IBM CMOD 10.5 as its archive storage solution ? I checked in the documentation but did not see it as an option.

Mayank

Pages: [1] 2