Job Schedule Management

Hi,
We recently upgraded our Sol Man system to EHP1 and we are in the process of Job Shedule Management. We imported few jobs from managed system and while monitoring ,getting error Business Proccess not created.
Could any one please tell me one thing, shall we need to setup Business Process Monitoring prior to setup Job Schedule Management? Please explain high level end to end Job Schedule Management steps.
Thanks & Regards
Srinivas.

Hi Srinivas,
please have a llok under https://service.sap.com/jsm to find further links to important SAP notes that explain a lot. You can also find iTutors about JSM under https://service.sap.com/rkt-solman.
Generally speaking BPMon is NO prerequisite for JSM. But as you probably saw during the import you have to assign your documented job either to a logical component (esp. meaningful for system related jobs like housekeeoing spool or dumps) or you assign to a business process step. An assignment to a logical component is a minimum requirement!
For a business process step assignment you need to maintain processes either in the project part or in the solution directory of SAP Solution Manager.
An active BPMon is only needed if you want to monitor background jobs and want to make use of the integration between JSM and BPMon.
You should also look for Blog and Forum entries of Martin Lauer in order to get further JSM insights.
By the way: If you should encounter some functional problems you can open an OSS message on SV-SMG-PSM.
Best Regards
Volker

Similar Messages

Configuration Guide Job Scheduling Management with SAP Solution Manager

Dear Gurus
Could you please help me with the configuration guide of the Job Scheduling Management with SAP Solution Manager
Best Regards

Hello Luis,
the configuration activities can be accessed via the "Implementatiopn Guide" by calling transaction SPRO in your SAP Solution Manager system.
In SPRO navigate to -> SAP Solution Manager -> Scenario-Specific Settings -> Job Scheduling Management -> Standard Configuration and execute the following two activities.
1. Activate Solution Manager Services
2. Set Up Work Center for Job Scheduling Management
Make sure that your user has role SAP_SM_SCHEDULER_EXE (or_ADMIN) assigned.
Afterwards you should be able to access the Job Management Work Center and to create Job Documentation or to import Jobs from a Managed System into new Job Documentations.
The following SAP notes might be usefuly as well:
1054005 - FAQ on Job Scheduling Management
1117355 - Work Center roles
Kind regards,
Martin
http://service.sap.com/jsm

Job Scheduling Management

Hi Experts,
Did any one have guide to schedule a job in solman 7.1 using Job Scheduling Management? I have created a job request from solman_workcenter job management. Now I want to know how to schedule the job in backend system. As I am not able find any document for Solman7.1 SP10 please suggest.
Thanks
Sajin

Hi Kamil,
Thanks for your quick response that document was quite helpful and while doing configuration I am facing an error while saving "Monitored Obj Name" could you please assist.
Thanks
Sajin

Job Scheduling Management vs SAP CPS

Hi Guys
I am trying to find out what are the differences between using the Job scheduling management tool in Solution manager and SAP CPS integrated into Solution manager. What are the benifits of using CPS as opposed to using the "standared" job scheduling tool.
santosh

Hello Santosh,
the link that you already got is good. Perhaps you also want to check out [http://wiki.sdn.sap.com/wiki/display/SM/FAQJobSchedulingManagement|http://wiki.sdn.sap.com/wiki/display/SM/FAQJobSchedulingManagement] and [SAP is first vendor to provide a comprehensive Job Management Suite |SAP is first vendor to provide a comprehensive Job Management Suite] for further information.
In short SAP CPS is an advanced scheduling tool like which competes against other like UC4, Control-M from BMC etc. But all these tools do not provide any real job documentation or job request functionality in order to get the process governance right. That's where the SolMan gets into the game.
Best Regards
Volker

Job Scheduling in Solution Manager - Error creating Periodic Job

Hi all,
I am in the process of testing the Job Scheduling functionality using the Solution Manager. I have setup the criteria manager, ec. in the satellite system, and done the config in Solman as well.
I am able to successfully setup up a 'on-time' job.
it's only when I try to setup a periodic job, I end up getting following error
Any thoughts? Is there any piece of config that's missing? All the SICF services needed for this functionality are running fine.
Thanks for the help.
500 Internal Server Error
Error when processing your request
What has happened?
The URL https://fsspsm.target.com:/sap/bc/webdynpro/sap/wd_ags_ejr_job_req_gaf_app was not called due to an error.
Note
The following error text was processed in the system PSM : Message was not created
The error occurred on the application server fsspsmap01_PSM_00 and in the work process 1 .
The termination type was: ERROR_MESSAGE_STATE
The ABAP call stack was:
Function: BAPI_NOTIFICATION_CREATE of program SAPLDSWP_NOTIF
Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
Method: SUBMIT_REQ_CRM_DATA of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
Method: SUBMIT of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
Method: PROCESS_SCENARIO_PERIODIC of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: PROCESS_JOB_SCENARIO of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: IF_AGS_EJR_JSM_PROC_FPM_CTRL~AFTER_PROCESS_EVENT of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
Method: IWCI_IF_FPM_APP_CONTROLLER~AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
Method: CALL_UIBB_PROCESS_EVENT of program CL_FPM========================CP

Hello,
This is the basic Job Scheduling functionality and not the Redwood Job scheduling, correct?
Have you performed the IMG Activiteis in SPRO?
See the following Help link:
http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/c5/7edcbd58ce4e29bc1baf1c4761d71f/frameset.htm
Change a job
You can change the scheduling of a job as long as it has not been completed. Proceed as follows:
Make changes.
Note
When you change a periodic job, the system searches for the changeable successor and only changes this successor.
If there is more than one changeable job with the same name, the system does not change any of these jobs.
End of the note.
Save your entries.
To release the job in the target system, select Release.
You go to the transaction SM37 in the target system.
You just may want to ensure HTTP Services have been enabled. I realize you said the services workin SICF, but this needs to be verified as 500 Internal Server Error most often means the HTTP services are not activated.
Regards,
Paul

Scheduling job perodically vs schedule manager

Dear SAP expert
I would like to run the report fbl1n(PRogram RFITEMAP ) and email to users.
I have 2 option:-
1.Schedule the job periodically and email it through SM36.
2. customise the report in schedule manager in flow definition and email to users.
option 1 i am able to execute.
option 2 i am not fully through. Please clarify how option 2 can be done.
How i should decide pros and cons of schedule the job periodically through SM36 OR THROUGH SCHEDULE MANAGER
PLS CLARIFY
thanks
S AP

Hello Santosh,
the link that you already got is good. Perhaps you also want to check out [http://wiki.sdn.sap.com/wiki/display/SM/FAQJobSchedulingManagement|http://wiki.sdn.sap.com/wiki/display/SM/FAQJobSchedulingManagement] and [SAP is first vendor to provide a comprehensive Job Management Suite |SAP is first vendor to provide a comprehensive Job Management Suite] for further information.
In short SAP CPS is an advanced scheduling tool like which competes against other like UC4, Control-M from BMC etc. But all these tools do not provide any real job documentation or job request functionality in order to get the process governance right. That's where the SolMan gets into the game.
Best Regards
Volker

Information Managment Policy Timer Job Schedule

I have created an information management policy on one of my libraries and set the retention to daily. I was not getting results on a daily basis so researched and found that there are two timer jobs that manage the policies: Information Management Policy
and Expiration Policy. I have found that these are both defaulted to run weekly, which is why I was not getting the results that I expected.
Would you be able to let me know if there are any repercussions of changing the schedule of these jobs to daily such as resource concerns? Thanks.

Setting them to daily is a routine activity. There shouldn't be any reprecussions as long as you make sure they run in the right sequence.
They will use a bit of resource but if you set up some perfmon traces you can compare a time period before you set the jobs up with one afterwards and see what the impact is.

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 in background job scheduling in Solman 7.0

Hi Experts,
I am working with Solman 7.0 configuration. In the IMG node for Scheduling background jobs (Solution manager-> General Settings), while following the documentation to schedule the jobs, I am facing issues with the following jobs:
1. *SEND_SYSTEM_RELATIONSHIP_TO_SUPPORT *
This job got cancelled on immediate scheduling, however has been scheduled for next day. What could be the reason by which it got cancelled?
2. AI_SDK_FILL_FILE_TYPE_TABLE
I cant find a job of this name in the system (while all other jobs are already available in the system by default). But, there is a program with the same name. Should I schedule the same in SM36?
Regards,
Arun.

Hi,
Yes schedule a job with program AI_SDK_FILL_FILE_TYPE_TABLE. Hope this solves your problem.
Feel free to revert back.
--Ragu

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

Indexing Schedule Manager on Server Failed!!!

Hi All,
Below is the error message from the ULS logs regarding the Indexing service. As a result of this, I'm unable to see the Content Sources and Crawl History on Central Admin. I further found out that one of the server in our farm is in Converging Status under
NLB (Network Load Balancer). Could this be the issue? But why would it say access denied. The search service account has not been modified or the permissions have never changed. Thanks in advance for any pointers.
Entering monitored scope (Timer Job Indexing Schedule Manager on WCRSPT02) 8a76f83b-9c75-48d4-8764-61fb0d93ca49
executing job Indexing Schedule Manager on <Server> 8a76f83b-9c75-48d4-8764-61fb0d93ca49
CContentSourceCollection::ValidateTrigger in m_pScheduler -> Activate or NewWorkItem, Error is 0x80070005 [contentsource.cxx:1126] d:\office\source\search\native\gather\server\contentsource.cxx
<Exception><HR>0x80070005</HR><eip>000007FEE2929257</eip><module>d:\office\source\search\native\gather\server\contentsource.cxx</module><line>1127</line></Exception>
The Execute method of job definition Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (ID 0141a0f4-9c0a-4aa3-901f-f0bd5bb7f51d) threw an exception. More information is included below. Access is denied. (Exception from HRESULT:
0x80070005 (E_ACCESSDENIED)) 8a76f83b-9c75-48d4-8764-61fb0d93ca49
Exception stack trace:    at Microsoft.Office.Server.Search.Administration.SearchApi.RunOnServer[T](CodeToRun`1 remoteCode, CodeToRun`1 localCode, Boolean useCurrentSecurityContext, Int32 versionIn)     at Microsoft.Office.Server.Search.Administration.SearchApi.GetContentSources(Int32
versionIn)     at Microsoft.Office.Server.Search.Administration.ContentSourceCollection..ctor(Content parent)     at Microsoft.Office.Server.Search.Administration.Content.get_ContentSources()
at Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition.Execute(Guid targetInstanceId)     at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean
isTimerService, Int32& result) 8a76f83b-9c75-48d4-8764-61fb0d93ca49
Leaving Monitored Scope (Timer Job Indexing Schedule Manager on WCRSPT02). Execution Time=50.1862666903196
Regards, Kapil ***Please mark answer as Helpful or Answered after consideration***

Hi,
According to your post, my understanding is that Indexing Schedule Manager on Server Failed.
I recommend to reset Index and have a full Crawl. Please refer to:
Unable to view content sources or crawl history in Search server 2010 Central Administration: share point
You need to check whether you have an additional Search Service Application and is stuck in an error state. If so, please run the configuration wizard to remove the previously mentioned Search Service Application that was corrupted.
In addition, please follow the instructions to check whether it works:
stsadm -o osearch -action stop
stsadm -o osearch -action start -role index
Open Central Admin - select your SSP
Check / validate your search service configuration.
Here are some similar articles for your reference:
http://social.technet.microsoft.com/Forums/en-US/a2f749bf-5d8b-4c0e-8fdd-464bd21d0e0a/indexing-schedule-manager-failing?forum=sharepointadminprevious
http://bruteforcesharepoint.blogspot.com/2009/04/event-log-errors-6481-and-6398.html
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Schedule Manager selection variables

I want to schedule a job for all 12 months of the year in Schedule Manager. For posting period and fiscal year i am using TVARV variables.The problem am facing is explained in the example below. Today's date assumed to be 08th June, 2006:
Variant with posting period 4 scheduled on 10th June, 2006
After the above i change the TVARV variable of posting period to 5 and schedule on 12th June, 2006
Unfortunately after the above step, the parameter of '4' posting period of the job scheduled on 10th june, 2006 changes to 5. I dont want this to happen. I want the program to run with posting period '4'
Of course i can create a new variant but it would then require 12 variants for 12 mnths of the year
Can someone please help me on the above?
Thanks in advance

Hi Prabha,
After you have finished maintaining your variant, you would have to click on the "<b>Attributes</b>" button just below the title and maintain the description for your variant. Save this entry and press the back <b>green arrow</b>. Your save button would now be activated and you can save your settings now.
I hope this helps.
Do not forget to award the point please.
Regards,
Jacob

Schedule Manager SCMA

Dear All,
Is there any way to schedule the sub task after completion of a task automatically in schedule manager SCMA??as we execute the step one by one, so once the job is comepleted it should automatically trigger the step assign to that task.
How flow definition works?

Hi All
So far I know tasks doesn´t have this feature, but there are workflows where you can set it.
Try to create a workflow. It work for example for some transaction that have some steps to be executed. Eg. CKMLCP.
Regards.

How to see DBMS_OUTPUT error when pl/sql proc runs in the EM job scheduler?

I have a pl/sql package that uses DBMS_OUTPUT to handle exceptions. When I run the package in sql*plus:
set serveroutput on;
begin
mypkg.myproc;
end;
and there is an exception, I see the output from my DBMS_OUTPUT.PUT_LINE.
However, when I use the job scheduler in Enterprise Manager... if there is an error, I do not see the output from my exception handling code (i.e., the output from DBMS_OUTPUT.PUT_LINE).

Using DBMS_OUTPUT to handle exceptions is generally not considered good form. At a minimum, you would want to log the exception to a table (or a file). If you are catching an exception that you cannot handle, you would really want to let that propagate back up to the caller so that Oracle knows that the job failed and can take appropriate action (i.e. retrying, not running dependent jobs, notifying a DBA, etc).
Justin

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

Job Schedule Management

Similar Messages

Maybe you are looking for