OnDemand User Group

Support Forums => Other => Topic started by: j4jims on September 28, 2015, 05:32:29 AM

Title: ARS6085E in System Log
Post by: j4jims on September 28, 2015, 05:32:29 AM

Hi All,

     Am executing arsdoc command from bin directory. I get the error code as ARS6085E and it prompts me to check it in SystemLog for more details.

Is there a way I can find the SystemLog file in the Unix server rather checking in the CMOD client.

Thanks in advance for the assistance.

- Jim.

Title: Re: ARS6085E in System Log
Post by: Alessandro Perucchi on September 28, 2015, 06:02:36 AM

Nope... that's one of the un-nice thing...
For that you have at least 2 ways:

• If you have the rights, edit the file "arslog" which is in the bin directory of CMOD installation directory. You could add quite at the beginning something like
  
  
  Quote

  echo "$@" >> /tmp/odlog.txt

  
  You don't need to restart CMOD, that is dynamically changed. And then you will be able to see the output in /tmp/odlog.txt.
  
• Go in the database, if you can with "db2" or "sqlplus" in order to check the SL% tables.

I don't have anything else to help you by being 100% in Unix. Maybe someone has another tip for you.

---
Alessandro

Title: Re: ARS6085E in System Log
Post by: Justin Derrick on September 28, 2015, 02:52:44 PM

The irony is that you could read the System Log with another arsdoc command.  :)

Alessandro is (as always) right in that using arslog is a great way to write messages to a UNIX file -- but be aware that on exceptionally busy systems, it can cause bottlenecks (high thread counts in arssockd -pv) and consume an enormous amount of space very quickly.

Also, you need to turn on User Exit Logging options inside the System Parameters pane in the CMOD Admin client, to determine what type of messages go into arslog.

Good luck!

-JD.

Title: Re: ARS6085E in System Log
Post by: j4jims on September 28, 2015, 07:46:34 PM

@ Alessandro,

   Unfortunately I don't have permission to edit the arslog file :(

-Jim

Title: Re: ARS6085E in System Log
Post by: j4jims on September 28, 2015, 07:50:39 PM

 Yep...That helped JD. I had written an arsdoc command to get the details from System Log folder.

Thanks !!!

-Jim.

Title: Re: ARS6085E in System Log
Post by: Alessandro Perucchi on September 28, 2015, 11:58:48 PM

*Bummer* !!!!

arsdoc query from System Log !!!

I've forgot about it!! :-) Thanks Justin to save my face here !!!  ;D

Title: Re: ARS6085E in System Log
Post by: Justin Derrick on September 29, 2015, 02:06:45 AM

Except that, if the error he's experiencing is preventing CMOD from working properly, he won't get anything back!  Alessandro's suggestion of using arslog is the "most correct", and my arsdoc idea is a distant second.  :)

But really, at the end of the day, if you're a CMOD admin, you shouldn't have any unnecessary restrictions against having access to the CMOD Admin Client, and Windows 'Thick' Client.

-JD.