Messages

1

MP Server / Re: arsrd failing with segmentation fault on v9.0 for AIX

« on: November 13, 2018, 04:27:51 PM »

Thank you, we're working on it and should be upgraded soon.  Looks like we've only got Fix Pack 1 installed so I'll work on the getting the rest in place.

2

MP Server / arsrd failing with segmentation fault on v9.0 for AIX

« on: November 13, 2018, 08:47:47 AM »

Good morning all,

We've been experiencing an issue these last few months that we haven't been able to track down the root cause. Our arsrd service occasionally fails due to a segmentation fault somewhere. Most of the time we're able to just restart and go on our merry way, but a few times now it has been stubborn and will crash again after running for maybe a minute. This continues until the next day, when we restart it again and magically it stays up and running.

We've tried clearing out the /temp/archive folder, running arsmaint -cdirsv, even rebooting the server, but the service would not stay up. Until the next day, that is.

We're running v9.0 on an AIX box. We're working on upgrading to the latest version on a separate box, but in the meantime I'm stuck trying to deal with this and wondering if anyone has any other troubleshooting suggestions. Any help is appreciated.

3

Report Indexing / Re: Needing to removing a leading zero from a PDF index

« on: May 03, 2016, 06:57:14 AM »

Unfortunately the store number is the last thing on the line. I went ahead and tried it with '#### ' and removing trailing spaces, but it failed.

4

Report Indexing / Needing to removing a leading zero from a PDF index

« on: May 02, 2016, 08:41:41 AM »

Hi all,

I'm using a PDF indexer to grab a store code from a report, which should be fairly straight-forward except the code is 5 characters in the report with a leading zero, and I only want to index the last 4 characters. The indexer won't let me choose just the 4, it only recognizes the whole chunk. I've tried using a mask of ####, but that grabs the first 4 characters. Using the character removal option under the Load Information tab won't work either, as I need the index to show as 0065 for example, not 65. What are my other options here? Thank you for any help.

5

MP Server / Updating Report Distributions in Batch

« on: October 08, 2013, 06:26:25 AM »

We're running v9 on AIX, and using Report Distribution with 8000+ distributions set up. I need to be able to update the application group on 1000+ of these distributions, and I'm really hoping there's a simple way to do this in batch. I've yet to fins any XML code to deal with this specifically. Any suggestions?

6

Report Indexing / Re: Automated process to create generic index for Excel file and load report

« on: August 21, 2013, 12:27:00 PM »

A shell script is the way I was thinking we's want to go. So are you parsing the report name for the index data?

7

MP Server / Automated Directory Maintenance

« on: August 19, 2013, 07:02:35 AM »

Hi all,

We're currently in the process of moving from OnDemand v8.0.4 on z/OS to v9 on AIX. I was wondering if anyone had any suggestions on best practices or scripts for keeping the processed and error directories cleaned up. We are using the ARSJESD process to upload reports from the mainframe to the server, and the ARSLOAD process gets triggered from there. It's been about a month now with just a few reports so far, and I can see the log files getting out of hand quick.

8

Report Indexing / Automated process to create generic index for Excel file and load report

« on: August 13, 2013, 05:22:30 AM »

Hi all,

We received a request to start loading Excel files into OnDemand, and I've successfully loaded some test reports with a generic indexer. Now I just need to figure out how to automate a process to create the indexer and load the report into OnDemand when the report land in a specific folder on our AIX server. The generic indexer would need to parse the report name for the department ID(ex., pull 2140 from INCOME_STATEMENT_2140.XLSX). Any suggestions or examples on how to set this up? Any help would be appreciated.

Thank you.