ibmi-brunch-learn

Announcement

Collapse
No announcement yet.

Sep

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Sep

    Hi Folks,

    Can anybody let me know wt is an SEP and it is used in debugging a job. I even came to knw tht there is no need to do a STRSRVJOB, if so let me knw wt is the procedure to debug a job.

    thanks & regards
    Giduturi S

  • #2
    Re: Sep

    SEP = Service Entry Point

    Debugging iSeries applications using service entry points

    The service entry point feature is designed to allow easy debugging of applications that invoke business logic written in ILE RPG, COBOL, CL, or even C or C++. The service entry point is a special kind of entry breakpoint that can be set directly from the Remote System Explorer. It is triggered when the first line of a specified procedure is executed in a job that is not under debug. Service entry points allow you to gain control of your job at that point. A new debug session gets started and execution is stopped at that location.

    While the original service entry point design was meant to assist with debugging Web applications, using the feature is also beneficial when debugging applications in an environment where the job name is not known ahead of time. Some sample scenarios include:

    * Debugging WebFacing applications: Typically you would want to debug your RPG or COBOL code that is driven by the JSP that is executing in the application server. You do not know the name of the job in which your RPG or COBOL program will run, ahead of time, so the use of service entry points is an ideal solution for this scenario.
    * Debugging any application that uses the Toolbox program or service program calls: When a program or service program is called and the code where the service entry point is set is about to execute, the debugger can take control of the application. With this technique, you can put the program or service program invoked by the Toolbox under debug although you do not know which job it will be running in.
    * If your application runs in a multi-job environment, service entry points will significantly simplify your life while debugging. You would set a service entry point in the program that is about to be spawned in a new job. When the program is spawned and the line where the service entry point is set is about to execute, the debugger will be able to gain control of the program and stop at that line.

    When a service entry point is triggered and the job which is running the application is not currently under debug, a message that allows you to launch a debug session will open. If you select Yes in the message, a debug session for the program will be launched in the Debug perspective. If you select No, you will resume the program without debugging it. If you do not want to be prompted to start a debug session right away when a service entry point is hit, select the check box in the prompt dialog or use the debugger preferences settings. For further information about debug preferences, see the related topic below.

    During a debug session, you can also set service entry points for a specific line in your program via the debugger user interface. This will require a program of interest to be under debug, as described in the related topic below.

    When working with service entry points, there are performance considerations that should be taken into account, as described in the Performance considerations section of Removing service entry points in the iSeries Service Entry Points view.
    "Time passes, but sometimes it beats the <crap> out of you as it goes."

    Comment


    • #3
      Re: Sep

      Hi littlepd,

      Thanks for the info regarding SEP.

      Could you also let me know the steps involved in debugging the job.

      regards
      Giduturi S

      Comment


      • #4
        Re: Sep

        http://publib.boulder.ibm.com/infoce...s/cbibsent.htm
        "Time passes, but sometimes it beats the <crap> out of you as it goes."

        Comment

        Working...
        X