Problem in vcc job scheduling

Hi All,
I am getting an error while executing the backgroung job analysis in VCC. The log is as follows.
Nov 23, 2007 10:32:48 AM com.virsa.cc.xsys.bg.BgJob run
WARNING: *** Job Exception: Missing IN or OUT parameter at index:: 13
com.virsa.cc.xsys.bg.BgJobException: Missing IN or OUT parameter at index:: 13
     at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:667)
     at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:787)
     at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:189)
     at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:149)
     at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:149)
     at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:79)
     at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:336)
     at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1135)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
     at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:480)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Nov 23, 2007 10:32:48 AM com.virsa.cc.xsys.bg.BgJob setStatus
INFO: Job ID: 9 Status: Error
Nov 23, 2007 10:32:48 AM com.virsa.cc.xsys.bg.BgJob updateJobHistory
FINEST: --- @@@@@@@@@@@ Updating the Job History -
2@@Msg is Error while executing the Job:Missing IN or OUT parameter at index:: 13
Nov 23, 2007 10:32:48 AM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
INFO: -
Background Job History: job id=9, status=2, message=Error while executing the Job:Missing IN or OUT parameter at index:: 13
Nov 23, 2007 10:32:48 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
INFO: -
Complted Job =>9----
Anubha

Hi,
I am trying to run risk analysis batch job in full synch.
My user/role/profile synchronization job has completed successfylly, But risk analysis job not.
I am getting the error "IN and OUT parameters are missing at index 13.
I have created proper JCO connectors with proper jco destination.
Batch mode = 'Full sync'
Rule Set = Global
Report type = action level and permission level analysis.
If any other info is required, please do ask.
Thanks,
Anubha

Similar Messages

Problem with background job schedule

Hi friends,
How to schedule more than one data loading jobs in backround??
When i try to schedule the second job,the first scheduled job is getting overwritten,and only this job is active.
I tried in infopack,scheduler...
How to overcome this???
Regards
sudhakar

Hello Ragu,
How r u ?
Use Process Chains for this multiple Job Scheduling.
I think u r teying to schedule the same InfoPackage !
Could u elobrate ur issue ?
Best Regards....
Sankar Kumar
+91 98403 47141

Problem in Background Job Scheduling in GRC 5.3

Dear All,
I am configuring GRC RAR 5.3 SP11. While scheduling background jobs, only one job is running at a time. If I am scheduling Management report for one client of system (XYZCLNT300) and another job for User, Role and Profile synchronization- Full Sync for other client of the same system (XYZCLNT400).
So, only one job is running at one time and other job remains in Ready state. I have done following Config in GRC System:
1) GRC system has 2 server nodes.
2) Each Server node has 3 background job workers and 5 web service workers.
While Running 2 job at sametime, one is in Running status and other is in Ready Status. But that time only 2 background job workers are occupied one from each node while others are in IDLE state.
I am wondering if I have free background job workers then why other job is in Ready Status. Is there nay parameter that needs to be changed to run multiple background jobs in parallel ?
Please suggest.
Thanks
Sunny

Hi,
As per SAP Note 1371501 - Multiple Batch Risk Analysis at a time, we cannot run multiple batch risk analysis at a time.
Batch Risk analysis will run only on server0 node.
Thanks
Sunny

Problem in periodic job scheduling in LBWE

hi,
i have activated the Material movements datasource 2LIS_03_BF. Filled up the set up table.
now when i try to schedula a job in jobcontrol, under the tab *immediate* the immediate start check box is checked and disabled. the periodic job check boxat the bottom is unchecked and disabled.
the periodic values button which has to be near the check button is not present.
i even tried for other datasources, the periodic job is disabled in all and periodic values button is not found.
could anyone suggest me on this issue.

Hi,
Did you initialize delta for 2LIS_03_BF from BI? If not, first initialize the delta and try to schedule V3 job from LBWE.
By default *Immediate start * check box will be in disable mode. If you want to run it immediately just click on Save button.
If you want to schedule it for future date and time then click on Date/time button then enter schedule start date and time and click on Save button.For more details about scheduling options please look at following link.
http://help.sap.com/saphelp_nw04/helpdata/EN/c4/3a7fae505211d189550000e829fbbd/frameset.htm
hope it works...
regards,
Raju
Edited by: VaraPrasadraju Potturi on Aug 3, 2009 8:54 AM
Edited by: VaraPrasadraju Potturi on Aug 3, 2009 9:02 AM

Background job scheduling problem in APO

Hi fellow SDNers,
i am going through this peculiar problem of background job scheduling:
scenario is like , i have an CSV (excel file) in aplication server which would load data into the infosource, which i have scheduled to run in backhround (in infopackage) ,after event is triggered (option in scheduling tab of infopackage...THE SCHEDULING OPTIONS)
now everything seems to be fine.. but the data is not getting loaded...?? could u lease help me out..how to load data from excel file (in background), after an event gets triggered.
thanks in advance,
Rohan

hi Alexander,
i am triggering the event from BP_EVENT_RAISE FM in APO by passing the event id... this would automaitically raise the event...just like sm64
Thanks
Rohan

Reporting Agent Job Scheduling problem

hi All,
I am trying to schedule reporting agent job. I have few pre calculated webtemplates in one reporting agent scheduling package. when i try to schedule it and go to "start condition" - I want to put "After Event". I am selecting Event and giving the parameter name. But when i save and go out the job is already scheduled (checked in sm37). so I tried to chk the job condition again and the event i selected is not there !!!!
I want to create after even condition and schedule that parameter via mainframe as our all job schedule through main frame only !!! can some one tell me why its not working with reporting agent ??
I will definately assign the points.

dinesh and SB,
thank you for your reply. understood your point. but what i m asking is when i put "after event" criteria in the start selection... wouldnt it show that always when ever i go to Reporting Agent scheduling Package --> right click --> schedule --> start condition (i meant the event name and parameter should be saved there)
but once i save it and get out from the scheduling package i can see the job has been scheduled but its not showing that its even controlled job !!!
is it possible to use "after event" option in Reproting agent's job ?
I have few queries under one Reporting Agent scheduling package which is added in one process chain - the PC is running once a month - i added RA at the end of the process chain and the variant will be schedule by mainframe once the process chain has completed successfully. now 2nd thing is: i need to run Reporting Agent job every single day. so need to schedule it twice. we schedule everything by main frame. so if i can save "after event" criteria then i can schedule that parameter by mainframe. the problem is the start condition is not saving my after event condition entries or parameter names.
I hope i m clear. pl. guide its kind a urgent.

Background job scheduling problem

Hai..Can anyone check the below program and correct it.
I am unable to see the output in SP01 (SPOOL REQUEST)
MY PROGRAM:-
REPORT zh_test4.
TABLES : mara, TBTCO.
DATA : BEGIN OF itab OCCURS 0,
      matnr LIKE mara-matnr,
      END OF itab.
****background data declarations
data : job_name like TBTCO-JOBNAME.
data : job_num like TBTCO-JOBCOUNT,
       rep like sy-repid.
***selection screen
PARAMETERS : p_matnr LIKE mara-matnr default '1500-610'.
SELECT matnr FROM mara INTO TABLE itab WHERE matnr EQ p_matnr.
job_name = 'HARI'.
CALL FUNCTION 'JOB_OPEN'
EXPORTING
DELANFREP              = ' '
JOBGROUP               = ' '
    jobname                = job_name
SDLSTRTDT              = NO_DATE
SDLSTRTTM              = NO_TIME
IMPORTING
   jobcount               = job_num
EXCEPTIONS
   CANT_CREATE_JOB        = 1
   INVALID_JOB_DATA       = 2
   JOBNAME_MISSING        = 3
   OTHERS                 = 4
IF sy-subrc <> 0.
write :/ ' Job opening problem'.
else.
write :/ 'Job succesfully opened', sy-subrc.
ENDIF.
MOVE SY-UNAME TO TBTCO-AUTHCKNAM.
rep = sy-repid.
job_name = 'HARI'.
CALL FUNCTION 'JOB_SUBMIT'
EXPORTING
ARCPARAMS                         =
    authcknam                         = SY-UNAME
    jobcount                          = job_num
    jobname                           = job_name
LANGUAGE                          = SY-LANGU
PRIPARAMS                         = ' '
   REPORT                            = 'ZH_TEST4'
VARIANT                           = 'VAR'
IMPORTING
STEP_NUMBER                       =
EXCEPTIONS
   BAD_PRIPARAMS                     = 1
   BAD_XPGFLAGS                      = 2
   INVALID_JOBDATA                   = 3
   JOBNAME_MISSING                   = 4
   JOB_NOTEX                         = 5
   JOB_SUBMIT_FAILED                 = 6
   LOCK_FAILED                       = 7
   PROGRAM_MISSING                   = 8
   PROG_ABAP_AND_EXTPG_SET           = 9
   OTHERS                            = 10
IF sy-subrc <> 0.
WRITE :/ 'JOB SUBMIT PROBLEM',
          job_name,
          job_num,
          rep,
          sy-subrc.
else.
write :/ 'Job succesfully submitted in background', sy-subrc.
ENDIF.
CALL FUNCTION 'JOB_CLOSE'
EXPORTING
    jobcount                          = job_num
    jobname                           = job_name
LASTSTRTDT                        = NO_DATE
LASTSTRTTM                        = NO_TIME
PRDDAYS                           = 0
PRDHOURS                          = 0
PRDMINS                           = 0
PRDMONTHS                         = 0
PRDWEEKS                          = 0
PREDJOB_CHECKSTAT                 = ' '
PRED_JOBCOUNT                     = ' '
PRED_JOBNAME                      = ' '
SDLSTRTDT                         = datum
SDLSTRTTM                         = uzeit
STARTDATE_RESTRICTION             = BTC_PROCESS_ALWAYS
   STRTIMMED                         = 'X'
TARGETSYSTEM                      = ' '
START_ON_WORKDAY_NOT_BEFORE       = SY-DATUM
START_ON_WORKDAY_NR               = 0
WORKDAY_COUNT_DIRECTION           = 0
RECIPIENT_OBJ                     =
TARGETSERVER                      = ' '
DONT_RELEASE                      = ' '
TARGETGROUP                       = ' '
IMPORTING
JOB_WAS_RELEASED                  = 'X'.
EXCEPTIONS
   CANT_START_IMMEDIATE              = 1
   INVALID_STARTDATE                 = 2
   JOBNAME_MISSING                   = 3
   JOB_CLOSE_FAILED                  = 4
   JOB_NOSTEPS                       = 5
   JOB_NOTEX                         = 6
   LOCK_FAILED                       = 7
   INVALID_TARGET                    = 8
   OTHERS                            = 9
IF sy-subrc <> 0.
write :/ 'Unable to close the Job', rep, sy-subrc.
else.
write :/ 'Succesfully closed the job', sy-subrc.
ENDIF.

Here is an example, slightly different from your version.
REPORT ztest.
PARAMETERS: p_vbeln LIKE vbak-vbeln,
            p_bkrun NO-DISPLAY.
DATA: ls_vbak LIKE vbak.
DATA: v_answer,
      v_jobcount LIKE tbtcjob-jobcount.
IF p_bkrun IS INITIAL.
*-- not background processing
    CALL FUNCTION 'POPUP_TO_CONFIRM_STEP'
         EXPORTING
              textline1      = 'This may time out.'
              textline2      = 'Do you want to run in background?'
              titel          = 'Warning!!!'
              cancel_display = space
         IMPORTING
              answer         = v_answer.
    IF v_answer = 'J'.
*-- run in the background
      CALL FUNCTION 'JOB_OPEN'
           EXPORTING
                jobname          = 'ZTEST'
           IMPORTING
                jobcount         = v_jobcount
           EXCEPTIONS
                cant_create_job = 1
                invalid_job_data = 2
                jobname_missing = 3
                OTHERS           = 4.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE 'E' NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        EXIT.
      ENDIF.
*-- submit the program in the background
      SUBMIT ztest
        WITH p_bkrun = 'X'
        WITH p_vbeln = p_vbeln
        USER sy-uname
        VIA JOB 'ZTEST' NUMBER v_jobcount AND RETURN.
*-- close the job
      CALL FUNCTION 'JOB_CLOSE'
           EXPORTING
                jobcount             = v_jobcount
                jobname              = 'ZTEST'
                strtimmed            = 'X'
           EXCEPTIONS
                cant_start_immediate = 1
                invalid_startdate    = 2
                jobname_missing      = 3
                job_close_failed     = 4
                job_nosteps          = 5
                job_notex            = 6
                lock_failed          = 7
                OTHERS               = 8.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE 'W' NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
      EXIT.
    ELSE.
      CLEAR v_answer.
    ENDIF.
ENDIF.
CHECK v_answer IS INITIAL.
SELECT SINGLE * FROM vbak
                  INTO ls_vbak
                 WHERE vbeln = p_vbeln.
IF sy-subrc <> 0.
    WRITE:/ 'Invalid Order Id.'.
ENDIF.
END-OF-SELECTION.
CHECK v_answer IS INITIAL.
IF p_bkrun IS INITIAL.
    WRITE:/ 'Here is the result running the program in foreground.'.
ELSE.
    WRITE:/ 'Here is the result running the program in background.'.
ENDIF.
WRITE:/ ls_vbak-vbeln,
          ls_vbak-vkorg.

Job scheduling tutorial - problem

Hi
I'm recognizing job scheduling mechanizm in NW 7.11. I have followed this tutorial:
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/90a95132-8785-2b10-bda5-90d82a76431e&overridelayout=true
And so far I cannot see job definition in NWA. Any suggestions will be appreciated.
Best Regards
Maciej

I've found the reason. In tutorial there is job-definitions.xml file suggested instead of job-definition.xml
Regards
Maciej

Job scheduling

Hi Friends,
i have a problem with job scheduling.
two jobs need to be scheduled. (job1 and job2)
i used
job_open.
submit job1 using parameters.
job_close.
then for second job.
job_open.
submit job2 using parameter2.
job_close.
when i go and look in sm37. i see when job1 is running the job2 is in release status.
but what we need is when job1 is running job2 should be in schedule status. it should start only after job1 is completed.
in the job2 job_close i used job1 as the PRED_JOBNAME.
but i when i run the program job2 is in released status , not in schedule mode.
is there any way we can make the job2 in scheduled mode instead of release.
can we use event to control this. if yes please let me know how we can do it.
Thanks

Hi,
As Appana wrote - i'm not sure there's a problem, but why don't u make one job with 2 steps? this way u will be perfectly sure that job2 (2nd step in the new job) will run only after job1 (1st step n the new job)...
Good luck
Igal

Background Job Scheduling

Hi,
I am scheduling a report to run in background.
In this report it is creating background jobs automatically for different company codes.
It submits the 1st background job and waits until it finishes.
Then 2nd job starts in background and continues with other jobs.
At end it finishes all the jobs and closes.
Now my problem is.
1.       Whether is it possible for us to submit all the jobs at 1 time. And execute at same time. Ie., 1st, 2nd job will start at same time.
2.       If possible how can we do that.
What I have written is
loop at companycode.
Create job name.
call fun 'Job_Open'.
submit xxxx user sy-uname via job job_name numer job_count
to sap-spool
spool parameters l_spool_parameter
without spool dynpro
with companycode
with ......
and return.
endloop.
Please help ASAP, urgent.

hi praveen,
Job Scheduling Explained
Definition
Before any background processing can actually begin, background jobs must be defined and scheduled. The scheduled time for when a job runs is one part of the jobs definition. There are several ways to schedule jobs:
From Transaction SM36 (Define Background Job)
With the "start program in the background" option of either Transaction SA38 (ABAP: Execute Program) or Transaction SE38 (the ABAP editor)
Through the background processing systems own programming interface. (Many SAP applications use the internal programming interface to schedule long-running reports for background processing.)
Through an external interface.
Scheduling Background Jobs
Use
You can define and schedule background jobs in two ways from the Job Overview:
·         Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
·         The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
Procedure
       1.      Call Transaction SM36 or choose CCMS ® Jobs ® Definition.
       2.      Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
       3.      Set the jobs priority, or Job Class:
·         High priority:      Class A
·         Medium priority: Class B
·         Low priority: Class C
       4.      In the Target server field, indicate whether to use system load balancing.
·         For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
·         To use a particular application server to run the job, enter a specific target server.
       5.      If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
       6.      Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
       7.      Define the jobs steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
       8.      Save the fully defined job to submit it to the background processing system.
       9.      When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
Note: Release the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.
Specifying Job Start Conditions
Use
When scheduling a background job (either from Transaction SM36, Define Background Job or CCMS ® Jobs ® Definition), you must specify conditions that will trigger the job to start.
Procedure
Choose the Start condition button at the top of the Define Background Job screen.
Choose the button at the top of the Start Time screen for the type of start condition you want to use (Immediate, Date/Time, After job, After event, or At operation mode) and complete the start time definition in the screen that appears.
For the job to repeat, check the Periodic job box at the bottom of the Start Time screen and choose the Period values button below it to define the frequency of repetition (hourly, daily, weekly, monthly, or another specific time-related period). Then choose the Save button in the Period values screen to accept the periodicity and return to the Start Time screen.
Once youve completed specifying the job start conditions, choose the Save button at the bottom of the Start Time screen to return to the Define Background Job screen.
No job can be started until it is released, including jobs scheduled to start immediately. Since releasing jobs can be done only by a system administrator from the job management screen (Transaction SM37) or by other users who have been granted the appropriate Authorizations for Background Processing, no unauthorized user can start a job without explicit permission
Managing Jobs from the Job Overview
Use
The Job Overview, or Job Maintenance, screen is the single, central area for completing a wide range of tasks related to monitoring and managing jobs, including defining jobs; scheduling, rescheduling, and copying existing jobs; rescheduling and editing jobs and job steps; repeating a job; debugging an active job; reviewing information about a job; canceling a job's release status; canceling and deleting jobs; comparing the specifications of several jobs; checking the status of jobs; reviewing job logs; and releasing a job so it can run.
Procedures
To display the Job Overview screen, choose CCMS ® Jobs ® Maintenance or call Transaction SM37. Before entering the Job Overview screen, the system first displays the Select Background Jobs screen. You'll need to complete this Job Selection screen to define the criteria for the jobs you want to manage. Once you've selected jobs to manage, you can choose from a wide range of management tasks:
To copy a single existing job, choose Job ® Copy.
To reschedule or edit job steps or attributes of a single job, choose Job ® Change. A job step is an independent unit of work within a background job. Each job step can execute an ABAP or external program. Other variants or authorizations may be used for each job step. The system allows you to display ABAP programs and variants. You can scan a program for syntax errors. You can also display the authorizations for an authorized user of an ABAP job step.
To repeat a single job, choose Job ® Repeat scheduling.
To debug an active job, choose Job ® Capture: active job. Only a single selection is allowed. If an active job seems to be running incorrectly (e.g., running for an excessively long time), you can interrupt and analyze it in debugging mode in a background process, and then either release it again or stop it altogether.
You will be able to capture a background job only if you are logged on to the SAP server on which the job is running. To find server information in the Job Overview, select and mark the job, then choose Job ® Job details.
To review information about a job, choose Job ® Job details. Details displayed can include:
current job status
periodicity, or the repetition interval
other jobs linked to the current job, either as previous or subsequent jobs
defined job steps
spool requests generated by the current job
To cancel a job's "Released" status, select the job or jobs from the Job Overview list and choose Job ® Release -> Scheduled.
To cancel a job from running but keep the job definition available, select the job or jobs from the Job Overview list and choose Job ® Cancel active job.
To delete a job entirely, select the job or jobs from the Job Overview list and choose Job ® Delete. Jobs with the status of Ready or Running cannot be deleted.
To compare the specifications of more than one job, select the jobs from the Job Overview list and choose Job ® Compare jobs.
To check the status of jobs, select the job or jobs from the Overview Job list and choose Job ® Check status. This allows you to either change the job status back to Planned or cancel the job altogether. This is especially useful when a job has malfunctioned.
To review job logs, select a job or jobs with the status Completed or Canceled from the Job Overview list and
regards
karthik
reward me points if helpfull

Error occured while posting the job schedule for JDBCAdapter

Hi Experts,
In Application Log in Path: "/usr/sap/<SID>/DVExxxx/j2ee/cluster/server1/log", I see the error:
#/Applications/ExchangeInfrastructure/AdapterFramework/Services/Util
##com.sap.aii.af.service.scheduler.SchedulerManagerImpl.postJobScheduleOthers(String, int)
#J2EE_GUEST#0##n/a##f7956e1f6b4711e0b851001e0b5d3ac8#SAPEngine_Application_Thread[impl:3]_23##0#0
#Error#1#com.sap.aii.af.service.scheduler.SchedulerManagerImpl#Plain
###error occured while posting the job schedule for JDBCAdapter_9f0584b1bcb33b94b67ada456233bcb8 with 2#
Frequently are created Lock's and I need remove them in Visual Admin.
Any idea about this error?
Tks in advance.

Hi,
After applying the SP 23 Patch Level 08, LOCK JDBC problems stopped.
But now when a network error or database error, the JDBC Sender Communication channels that were open to connection, are blocked.
Even following the instructions in [SAP Note 1083488 - XI FTP_JDBC sender channel stop polling indefinitely (04_04S)|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1083488] the problem continues.
I've already set the parameter "taskTimeout" and selected the option "Disconnect from Database After Each Message Processing" but not resolved.
Any ideas?
Thanks in advance.

SSIS Package compiled successful, in SQL Server Integration Service package executed sucessful, But fail to run in MS SQL Job Scheduler

Hi Everyone,
I having a problem to transfer data from MS SQL 2005 to IBMAS400. Previously my SSIS was running perfectly but there is some changes I need to be done in order for the system to work well. Considers my changes are minimal & just for upgrades (but I did
include DELETE statements to truncate AS400 table before I insert fresh data from MS SQL table to the same AS400 table), so I compile my SSIS package & it run successfully & I passed it into MS SQL Integrated Service as 1 of the packages & manually
executed the package & the result is the same, that mean it was successful again but when I try to run it in a MS SQL Job Scheduler, the job failed with these message shown below as extracted from the job View history.
Date today
Log Job History (MSSQLToAS400)
Step ID 1
Server MSSQLServer
Job Name MSSQLToAS400
Step Name pumptoAS400
Duration 00:00:36
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
Executed as user: MSSQLServer\SYSTEM. ... 9.00.4035.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: today time
Error: on today time
Code: 0xC0202009 Source: SSISMSSQLToAS400 Connection manager "SourceToDestinationOLEDB"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred.
Error code: 0x80004005. An OLE DB record is available.
Source: "IBMDA400 Session"
Hresult: 0x80004005
Description: "CWBSY0002 - Password for user AS400ADMIN on system AS400SYSTEM is not correct ". End Error
Error: today
Code: 0xC020801C
Source: Data Flow Task OLE DB Destination [5160]
Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "DestinationClearData" failed with error code 0xC0202009. There may be error messages posted before
this with more information on why the AcquireConnection method ca... The package execution fa... The step failed.
So I hope somebody can shed some hints or tips for me to overcome time problem of mine. Thanks for your help in advance. As I had scoured thoroughout MSDN forums & found none solution for my problem yet.
PS: In the SQL Integrated Services when I deployed the package I set the security of the packages to Rely on server...
Hope this will help.

Hi Ironmaidenroxz,
From the message “Executed as user: MSSQLServer\SYSTEM”, we can see that the SQL Server Agent job ran under the Local System account. However, a Local System account doesn’t have the network rights natively, therefore, the job failed to communicate with
the remote IBMAS400 server.
To address this issue, you need to create a proxy account for SQL Server Agent to run the job. When creating the credentials for the proxy account, you can use the Windows domain account under which you executed the package manually.
References:
How to: Create a Credential
How to: Create a Proxy
Regards,
Mike Yin
TechNet Community Support

Problem with event based scheduling

Hi,
We are having a ETL job running everynight, so i need to have daily
report as soon as my ETL job is finished. For that we have run some
script to create a event file after completion of ETL job. And by using
this event file we have scheduled a report that runs after this event
file is created. Now the problem is that the scheduled report is
generated before the ETL job is finished. This seems to be working fine
till last month, but this month we are facing this issue. my question
is why the scheduler is triggered before the event file is created
(event file is created after the completion of ETL job)
Do anybody faced this iss
FYI
We are on BO XI 3.1 with no SP's and FP's and on windows environment.
Do anybody faced this issue?Any advise is appreciated.
Thanks,

Hi,
We are also on BO XI 3.1 with no SP's and FP's. We create Event files after the ETL jobs are completed. These files are used to create BO Events (File), which are used as scheduling criteria before the Reports can run. These files are deleted daily before the next files are created, something you might want check.
Mike

How to deactivate Filter and Job in Job scheduling?

Hi,
My scenario is:
XI will poll the file from 3rd party system and wil send to R/3 via IDOC adapter.
On every sunday , R/3 will be down for 3-4 hrs for maintenance purpose.
I need to create job scheduling in such a way that XI sould collect all the message coming on sunday during that period
of time and after endtime has reached , it should process those message and should send the message to R/3 system.
I have created Sender/Receiver ID ..also create Filter and a JOBID.
while creating Job ID i specified the following
1: Start Date    = 18.08.2009
2:Start Time     = 11.00.00
3:End Date      = 18.08.2009
4:End Time      = 15.00.00
5:Period          = 7
6:Period Unit   = D (Days)
Job should be scheduled at 11.00.00 and end at 15.00.00 ,filter and Job both should deactivate and after 15.00.00 it should process those messages.
But the problem is it doesnt deactivate the filter.
I tried using SXMS_JOB_DEACTIVATE and SXMS_START_JOB_AT_ONCE
Both deacitvtes the JOB but not filter.
Can any body tell me , how to go with it.
Also if I have to write a report, what all things are required.
regards,
Mayank

Hi Volker,
Down time for R/3 is more ..so i am not sure whether XI will trying till that time or not.
And XI is not able to than all the incoming messages in XI during that period of time will be Red Flag.
can we write a report in XI such a way that .. all the queued messages should be processed ..thorugh Job scheduling.

Deduplication error: there was a problem retrieving data deduplication schedule

Hi,
After changing dedup schedule once we are receiving this error and not able to change it any more.
there was a problem retrieving data deduplication schedule

Hi,
After changing dedup schedule once we are receiving this error and not able to change it any more.
there was a problem retrieving data deduplication schedule
Take a look @ PowerShell cmdlets for dedupe here:
PowerShell dedupe cmdlets
http://technet.microsoft.com/en-us/library/hh848450.aspx
Of your interest are Remove-DedupeSchedule and New-DedupSchedule ones. Try removing set schedule
you have now, making sure the status is "no jobs" and then create new schedule to see would it make the difference.
Good luck!
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Problem in vcc job scheduling

Similar Messages

Maybe you are looking for