OnDemand User Group
Support Forums => MP Server => Topic started by: tjspencer2 on November 23, 2020, 05:27:06 PM
-
So we are loading some statement files via PDF Indexer and my loads are failing but presenting no messages in my System Log?!?!?
We're running 9.5.0.4 on AIX 7.2 and DB2 10.5 and TSM 7.1.4.
I AM seeing error message in my custom script log, as follows: return code of 137 received from /path/arsload, but that's it ?!?!?!
I'm asking my Unix Admins where that message is generated from, as I don't see it in any IBM documentation.
My custom load scripts are just korn shell scripts to run arsload commands with format files, which I have run successfully for years.
And many files have processed successfully but a couple have failed any thoughts on troubleshooting - and they're good size - in excess of 340MB?
It almost makes me think it's a file issue, but with no error message to go on that I can track down, I'm not sure where to go with this :( Any thoughts?
-
Two thoughts -
Saw a 137 error before and it was DSNAOINI not properly set.
The other thought is maybe a memory issue?
Ed Arnold
-
Thanks Ed - I'll try to run that down and see what I find on the DSNAOINI and will also poke my admins on memory - appreciate you!!
-
I don't think Ed knows you're running on AIX. :) Unless you have a mainframe as one of your source systems...
-JD.
-
Correct - running on AIX.
I'm not sure how a korn shell script running arsload commands on the command line would return anything but an arsload error - maybe it's capturing standard output from AIX?
Perhaps I need to capture standard output the next time my teammate attempts to load this particular file.
This is a strange use case that a load file fails with no Msg. 88.
-
If you're running inside a script you need to 'redirect' standard error into standard output by adding this at the end:
arsload <options> >arsload.log 2>&1
That will capture error messages as well as informational messages. I think this behaviour changed in Content Manager OnDemand v9.x -- I believe that previous versions sent all messages (info & error) to standard output.
-JD.
-
Ah - Justin jogged my memory on this item in my 9.5 Release Notes:
http://www.odusergroup.org/forums/index.php?topic=1543.msg6871#msg6871 (http://www.odusergroup.org/forums/index.php?topic=1543.msg6871#msg6871)
Ed Arnold
-
Yeah, I've actually got another customer with the same issue. They upgraded late last year to v9.5, and they've noticed that failed loads are missing the error messages in their scripts. They're looking at changing something like 600+ individual load scripts to incorporate the "2>&1" magic.
-JD.
-
Thanks Justin and Ed - appreciate you two!!
Also, in this Covid-19 age, we're running lots of things over VPN.
Does the following look how you'd recommend running a command line script:
nohup arsload <options> >arsload.log 2>&1
-
Yup, that should work. Try it out and report back. :)
-JD.