Skip to Content
author's profile photo Former Member
Former Member

Changes of Job Chain logs in SAP CPS

Hello Experts,

Do you have any way for knowing what all the changes done on one particular job chain and when there are done. As we have SLG1 T-code in SAP BW for checking the system logs, do we have any such facility in SAP CPS for checking logs of the system/server.

Hoping for the sooner response. Thanks in advance 😊

Regards,

Bharadhwaz

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jan 06, 2014 at 04:46 PM

    @h.Carpenter & @Jamie Neilan : a lot for the valuable response...

    Is there any other way to get this details? By scripting or filtering the logs?

    Regards,

    Bharadhwaz

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Bharadhwaz,

      The documentation has a trigger example for you (at the bottom of the topic):

      http://<server>:<port>/scheduler/help/user_guide/environment/triggers/triggers.html

      That trigger fires when job definitions or job chains are edited and forces users to specify applications ... what you could do is remove the logic regarding applications and enable logging, log the information you want.

      You could then create a job definition that sends you that file on a weekly basis ...

      There are some more trigger examples here: http://<server>:<port>/scheduler/help/user_guide/environment/triggers/trigger_action_examples.html

      Ina "Before Definition Change" trigger, remember to set the Action Subject field, this allows you to use the jcsSession object.

      I hope this helps ...

      HP

  • Posted on Dec 27, 2013 at 03:49 PM

    Hi Bharadhwaz,

    You have the auditing module that audits object changes. This module even allows you to revert changes. If you have the Auditing Module, you will see an Auditing group on the left-hand side of CPS user interface.

    You can also write your own system with the OnChange trigger, although the auditing module does everything for you.

    Regards,

    HP

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Nanda,

      Not really. It will take up more space in the database when you use full audit, as that keeps a backup copy of the definition that was modified, sort of.

      I guess it all depends, though ... if 50 people change objects on a regular basis and you audit all those objects, it might ... but, we have never seen slowdowns due to auditing ... and we audit job definitions, job chains, time windows and submit frames.

      Sometimes, when I want to test something, I enable auditing for the object in question so that I can quickly revert it back ... handy for coding triggers, for example ... ;-)

      Regards,

      HP

  • author's profile photo Former Member
    Former Member
    Posted on Jan 07, 2014 at 11:10 AM

    Hello HP,

    Thanks a lot for the alternative without auditing. As a BW admin, I can go with triggers from the server. The triggers which I get as notification surely helps me. I should do the same for weekly basis. Thanks for the help.😊

    Regards,
    Bharadhwaz

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Bharadhwaz,

      Just a little boring warning and some best practices taken from my notes ... triggers can become performance bottlenecks, so code wisely. If you only want to audit job chains, then that is fine, however, auditing multiple object types via triggers quickly becomes a maintenance nightmare and resource hog.

      A short list of best practices for triggers; this list is not exhaustive:

      * code wisely and test your triggers extensively, make sure all the null checks are in

      * try to match the object as soon as possible, triggers fire all the time, so you should single out the objects you want before doing anything else, code before the check will be executed for each object change (in this case), which means pretty often ;-)

      * avoid working with big or remote (NAS, file server) files in triggers, or anything else that can potentially take a long time ... imagine trying to open a 15mb file from a trigger (the trigger might fire multiple times per second), that is bad, no? now imagine that over the network ;-)

      * store the maximum amount of your code logic in libraries, that way the code can be easily reused and maintained

      * In this specific case, monitor the size of the log file of the trigger

      Also, not sure I pointed this out: the auditing module has the power to revert changes in one click; similar functionality can be done in triggers as well, however, at a performance cost that I would not recommend.

      Regards,

      HP

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.