External Job Scheduling on XI 3.0

Hi,
I have a technical requirement whereby I need to start a XI Interface after a Mainframe job is completed.
Have you come accross any scenario where an external agent can start an interface in XI. How can this be achieved, specifically when I have data files that need to be processed in XI.
I already checked File Poler, but do not think that is a good option in my case.
-Feroz

Hi Feroz,
Please look into Time Controlled Message processing in SAP. Its available in SXMB_ADM as one of the node. This is the scheduling algorithm available in XI.
http://help.sap.com/saphelp_nw04/helpdata/en/7a/00143f011f4b2ee10000000a114084/content.htm
But you want to schedule interfaces for out of XI box I think you have to look into some tools like Cronacle form www.redwood.com
Thanks and Regards
Andy

Similar Messages

Question on Job Scheduling in SAP

Hi Experts,
I want to schedule a job to run every half hour from 7 am to 5 pm on Mondays to Fridays. That is, the job should not run on Saturday or Sunday, or after 5 pm on the weekends. Any information on how I can do this will be greatly appreciated!

Deborah,
Solution 1:
Does your company use an external job scheduling software such as Control-M, AutoSys, or Maestro? If so, have them schedule the job for you. They have much more flexibility than what SAP's job scheduling allows.
Solution 2:
This is a laborious process, but can be implemented without doing any additional development. You have to create 22 separate jobs. Each job will run at a specific time on every working day according to your factory calendar. First one will run only at 7 AM, second one at 7:30 AM, and so on.
Solution 3:
Develop a wrapper ABAP program as suggested by others.

External tools for monitoring job scheduling

Hello All,
Please give me the infomation on third party tool used for monitoring the process chains, handling issues and job scheduling.
Also why do we need third party tools and what are the available third party tools..
Thanks
Regards
M.A

Hi,
Giving you a scenerio,
Data load from Oracle to BI. Flow is
Oracle 7.0 --> Oracle 10G Daily refresh
Oracle 10G --> BI 7.0 Daily load ones Oracle 10G refresh complete
how BI 7.0 will understand if 10G refresh is complete ?
Need a triggering/scheduling tool which triggers events that this step is complete.
These tools usually reads a small file usually kepts on servers using FTP ones one step is complete. Such tools read if the file is available ( based on conditions provided, like check between 2am to 3am if file has arrived etc.) and ones available they trigger an even and next process starts
E.g. MAESTRO is used in such case.
Regards,
Akshay

Guide to External Jobs on 10g with dbms_scheduler e.g. scripts,batch files

GUIDE TO RUNNING EXTERNAL JOBS ON 10g WITH DBMS_SCHEDULER
NOTE: Users using 11g should use the new method of specifying a credential which eliminates many of the issues mentioned in this note.
This guide covers several common questions and problems encountered when using
dbms_scheduler to run external jobs, either on Windows or on UNIX.
What operating system (OS) user does the job run as ?
External jobs which have a credential (available in 11g) run as the user
specified in the credential. But for jobs without credentials including
all jobs in 10gR1 and 10gR2 there are several cases.
- On UNIX systems, in releases including and after 10.2.0.2 there is a file $ORACLE_HOME/rdbms/admin/externaljob.ora . All external jobs not in the SYS schema and with no credential run as the user and group specified in this file. This should be nobody:nobody by default.
- On UNIX systems, in releases prior to 10.2.0.2 there was no "externaljob.ora" file. In this case all external jobs not in the SYS schema and with no credential run as the owner and group of the $ORACLE_HOME/bin/extjob file which should be setuid and setgid. By default extjob is owned by nobody:nobody except for oracle-xe where it is owned by oracle:oraclegroup and is not setuid/setgid.
- On Windows, external jobs not in the SYS schema and with no credential run as the user that the OracleJobScheduler Windows service runs as. This service must be started before these jobs can run.
- In all releases on both Windows and UNIX systems, external jobs in the SYS schema without a credential run as the oracle user.
What errors are reported in SCHEDULERJOB_RUN_DETAILS views ?
If a job fails, the first place to look for diagnostic information is the SCHEDULERJOB_RUN_DETAILS set of views. In 10gR2 and up the first 200 characters of the standard error stream is included in the additional_info column.
In all releases, the error number returned by the job is converted into a
system error message (e.g. errno.h on UNIX or net helpmsg on Windows) and that
system error message is recorded in the additional info column. If there is no
corresponding message the number is displayed.
In 11g and up the error number returned by the job is additionally recorded in
the error# column. In earlier releases 27369 would always be recorded in the
error# column.
Generic Issues Applicable to UNIX and Windows
- The job action (script or executable) must return 0 or the job run will be marked as failed.
- Always use the full pathname to executables and scripts.
- Do not count on environment variables being set in your job. Make sure that the script or executable that your jobs runs sets all required environment variables including ORACLE_HOME, ORACLE_SID, PATH etc.
- It is not recommended to pass in a complete command line including arguments as the action. Instead it is recommended to pass in only the path to and name of the executable and to pass in arguments as job argument values.
- Scripts with special characters in the execution path or script name may give problems.
- Ensure that the OS user your job runs as has the required privileges/permissions to run your job. See above for how to tell who the job runs as.
- External job actions cannot contain redirection operators e.g. > < >> | && ||
- In general try getting a simple external job working first e.g. /bin/echo or ipconfig.exe on Windows. Also try running the job action directly from the commandline as the OS user that the job will run as.
Windows-specific Issues
- The OracleJobScheduler Windows service must be started before external jobs will run (except for jobs in the SYS schema and jobs with credentials).
- The user that the OracleJobScheduler Windows service runs as must have the "Log on as batch job" Windows privilege.
- A batch file (ending in .bat) cannot be called directly by the Scheduler. Instead cmd.exe must be used and the name of the batch file passed in as an argument. For example
begin
dbms_scheduler.create_job('myjob',
   job_action=>'C:\WINDOWS\SYSTEM32\CMD.EXE',
   number_of_arguments=>3,
   job_type=>'executable', enabled=>false);
dbms_scheduler.set_job_argument_value('myjob',1,'/q');
dbms_scheduler.set_job_argument_value('myjob',2,'/c');
dbms_scheduler.set_job_argument_value('myjob',3,'c:\temp\test.bat');
dbms_scheduler.enable('myjob');
end;
/- In 10gR1 external jobs that wrote to standard output or standard error streams would sometimes return errors. Redirect to files or suppress all output and error messages when using 10gR1 to run external jobs.
UNIX-specific Issues
- When running scripts, make sure that the executable bit is set.
- When running scripts directly, make sure that the first line of the script in a valid shebang line - starting with "#!" and containing the interpreter for the script.
- In release 10.2.0.1, jobs creating a large amount of standard error text may hang when running (this was fixed in the first 10.2.0.2 patchset). If you are seeing this issue, redirect standard error to a file in your job. This issue has been seen when running the expdp utility which may produce large amounts of standard error text.
- the user that the job runs as (see above section) must have execute access on $ORACLE_HOME/bin and all parent directories. If this is not the case the job may be reported as failed or hang in a running state. For example if your $ORACLE_HOME is /opt/oracle/db then you would have to make sure that
chmod a+rx /opt
chmod a+rx /opt/oracle
chmod a+rx /opt/oracle/db
chmod a+rx /opt/oracle/db/bin
- On oracle-xe, the primary group of your oracle user (if it exists) must be dba before you install oracle-xe for external jobs to work. If you have an oracle user from a regular Oracle installation it may have the primary group set to oinstall.
- On oracle-xe, the extjobo executable is missing so external jobs in the SYS schema will not work properly. This can be fixed by copying the extjob executable to extjobo in the same directory ($ORACLE_HOME/bin).
- Check that correct permissions are set for external job files - extjob and externaljob.ora (see below)
Correct permissions for extjob and externaljob.ora on UNIX
There is some confusion as to what correct permissions are for external job related files.
In 10gR1 and 10.2.0.1 :
- rdbms/admin/externaljob.ora should not exist
- bin/extjob should be setuid and setgid 6550 (r-sr-s---). It should be owned by the user that jobs should run as and by the group that jobs should run as.
- bin/extjobo should have normal 755 (rwxr-xr-x) permissions and be owned by oracle:oraclegroup
In 10.2.0.2 and higher
- rdbms/admin/externaljob.ora file must must be owned by root:oraclegroup and be writable only by the owner i.e. 644 (rw-r--r--) It must contain at least two lines: one specifying the run-user and one specifying the run-group.
- bin/extjob file must be also owned by root:oraclegroup but must be setuid i.e. 4750 (-rwsr-x---)
- bin/extjobo should have normal 755 (rwxr-xr-x) permissions and be owned by oracle:oraclegroup
In 11g and higher
Same as 10.2.0.2 but additionally bin/jssu should exist with root setuid
permissions i.e. owned by root:oraclegroup with 4750 (-rwsr-x---)
Internal Error numbers for UNIX on 10.2.0.2 or 10.1.0.6 or higher
If you are not using a credential and are using version 10.2.0.2 or higher or 10.1.0.6 or higher you may come across an internal error number. Here are the meanings for the internal error numbers.
274661 - can't get owner of or permissions of externaljob.ora file
274662 - not running as root or externaljob.ora file is writable by group or other or externaljob.ora file not owned by root (can't switch user)
274663 - setting the group or effective group failed
274664 - setting the user or effective user failed
274665 - a user or group id was not changed successfully
274666 - cannot access or open externaljob.ora file
274667 - invalid run_user specified in externaljob.ora file
274668 - invalid run_group specified in externaljob.ora file
274669 - error parsing externaljob.ora file
274670 - extjobo is running as root user or group

Hi Ravi,
Can you help me...
Hi All,
I planned to create a job to do rman backup daily at 04:00 AM.
1. I created a program as follows
BEGIN
DBMS_SCHEDULER.CREATE_PROGRAM(
program_name => 'rman_backup_prg',
program_action => '/u02/rmanback/rman.sh',
program_type => 'EXECUTABLE',
comments => 'RMAN BACKUP');
END;
my rman script is
#!/usr/bin/ksh
export ORACLE_HOME=/u01/app/oracle/product/10.2.0/db_1
export PATH=$PATH:/u01/app/oracle/product/10.2.0/db_1/bin
/u01/app/oracle/product/10.2.0/db_1/bin/exp rman/cat@catdb file=/u02/rmanback/rm
an_220108.dmp log=/u02/rmanback/rman_220108.log owner=rman statistics=none comp
ress=n buffer=400000
compress *.dmp
exit
2. I created a schedule as follows
BEGIN
DBMS_SCHEDULER.CREATE_SCHEDULE(
schedule_name => 'rman_backup_schedule',
start_date => SYSTIMESTAMP,
end_date => '31-DEC-16 05.00.00 AM',
repeat_interval => 'FREQ=DAILY; BYHOUR=4',
comments => 'Every day at 4 am');
END;
3. I created ajob as follows.
BEGIN
DBMS_SCHEDULER.CREATE_JOB (
job_name => 'rman_backup_job',
program_name => 'rman_backup_prg',
schedule_name => 'rman_backup_schedule',
enabled=> true,
auto_drop=> false
END;
While I am running the job I am getting the following error anybody help me.
ORA-27369: job of type EXECUTABLE failed with exit code: Not owner
ORA-06512: at "SYS.DBMS_ISCHED", line 150
ORA-06512: at "SYS.DBMS_SCHEDULER", line 441
ORA-06512: at line 2
If I removed "compress *.dmp" line in rman script it is working fine.
/* additional Info from dba_scheduler_job_run_details as follows */
ORA-27369: job of type EXECUTABLE failed with exit code: Not owner
STANDARD_ERROR="
Export: Release 10.2.0.3.0 - Production on Tue Jan 22 14:30:08 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Release 10.2.0.3.0 - Production
Export"
Regards,
Kiran

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 Backup job scheduling in DB13

Hi All
Backup job scheduled in DB13 kicks error ,I am using Oracle as database and ERP6.0
database and application are on diffrent servers.Before it was working fine,I didn't changed any password
I can run backupjob sucessfully directly from BRtools on database server.Please provide any hint
Job started
Step 001 started (program RSDBAJOB, variant &0000000000060, user )
No application server found on database host - rsh/gateway will be used
Execute logical command BRBACKUP On host DLcSapOraG08
Parameters:-u / -jid INLOG20090120204230 -c force -t online -m incr -p initerd.sap -w use_dbv -a -c force -p in
iterd.sap -cds -w use_rmv
BR0051I BRBACKUP 7.00 (31)
BR0128I Option 'use_dbv' ignored for 'incr'
BR0055I Start of database backup: bdztcorv.ind 2009-01-20 20.42.31
BR0484I BRBACKUP log file: D:\oracle\ERD\sapbackup\bdztcorv.ind
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance ERD failed
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance ERD failed
BR0056I End of database backup: bdztcorv.ind 2009-01-20 20.42.32
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
BR0054I BRBACKUP terminated with errors
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
BR0291I BRARCHIVE will be started with options '-U -jid INLOG20090120204230 -d disk -c force -p initerd.sap -cds -w use_rmv'
BR0002I BRARCHIVE 7.00 (31)
BR0181E Option '-cds' not supported for 'disk'
BR0280I BRARCHIVE time stamp: 2009-01-20 20.42.33
BR0301W SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
BR0310W Connect to database instance ERD failed
BR0007I End of offline redo log processing: adztcorw.log 2009-01-20 20.42.32
BR0280I BRARCHIVE time stamp: 2009-01-20 20.42.33
BR0005I BRARCHIVE terminated with errors
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.33
BR0292I Execution of BRARCHIVE finished with return code 3
External program terminated with exit code 3
BRBACKUP returned error status E
Job finished

Hi,
not sure if the recommendations given will address this issue.
You are getting this error:
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
the log file indicates:
> No application server found on database host - rsh/gateway will be used
This indicated that the user that is connecting from the AS to the DB server is not properly configured to perform the DB tasks on it.
So, first question would be to know if you have configured a gateway on the DB server and how, or if you are using remote shell.
Second question, you can do backups on the DB server.
> I can run backupjob sucessfully directly from BRtools on database server
How did you run exactly the backup job (what is the exact command line, what is the exact OS user that executed it)?
What is the OS of the DB server?
I have reread your post, your OS is windows therefore you fall in the "typical" error in Windows.
You have executed your backup as <sid>ADM and it works. Unfortunatelly, in windows, SAP is exectuted by SAPSERVICE<sid>, and this is the user who should be connecting to your DB server, and this is the user who cannot execute the backup.
The fact that you can run the backup with <sid>ADM in Windows does not means that you have SAPService<sid> properly configured.
For the error (see before) I think your ops$ user for this user is not properly configured in the DB server. take a look at the note mentioned by KT and pay attention to the SAPSERVICE<sid> configuration
Edited by: Fidel Vales on Jan 24, 2009 12:45 AM

Running External jobs in Oracle 10g using a different user ID

Hi,
i would like to run an external job ( shell script ) in oracle scheduler using a Unix user id other than nobody and oracle. is it possible to do that? if so please provide more information. I am currently using oracle version 10.2.0.4.0

Sure,
no problem at all, if you have no problem with the fact that all jobs that run from your ORACLE_HOME use the same account. I would prefer to upgrade to 11.1.0.7 and use the new remote exteral jobs with credentials.
For oracle 10g you have to modify $ORACLE_HOME/rdbms/admin/externaljob.ora and change the run_user and run_group to what ever you want to use.
regards,
Ronald
(also see:
http://www.packtpub.com/mastering-oracle-scheduler-in-oracle-11g-databases)

Integration wth outide Job Scheduler.

We are looking at integrating the Vinizant Global ECS Job scheduler with SAP. We need to know how to start and monitor sap jobs and chains from unix level. Any suggestions would be appreciated.

How do you on unix level without actually getting into the SAP GUI start and monitor SAP jobs?
There is no standard SAP tool to schedule jobs from the command line. A control program called sapxpg is used to execute external commands(which is scheduled internally). You can monitor the execution of external commands by setting up a trace for sapxpg and the data is written to the files dev_xpg(output of external command) and dev_cp(control program).
Nelis

Windows external job user

When running an external job on Oracle 10g in Windows, it seems that the external job username is no name at all. In the file which is kicked off by the scheduler job I put this line:
echo "%username%" >> %SI_HOME%\lib\imp_data.log
which produces just "" in the log file. It is supposed to log in with an externally authenticated account to run datapump imports, but it fails.
I read that for Oracle 10g the external job in Windows runs as the owner of the OracleJobScheduler service. In the properties it says it logs on as "Local System Account" which I thought would be username I want, but apparently it is not. I also tried to specify the account to run under but it won't take it, saying the account doesn't exist.
How can the username for external jobs be set to what I want?
Thanks.

I received the same results when running the OracleJobScheduler service under the 'Local System' credentials. I don't have an explanation for that. Here is some Microsoft documentation on it:
LocalSystem Account
However, you should have no problem specifying another account to run this service under. I do this on my systems. Remember this is an OS account not a database account. It can either be a Local User or Domain User.
If you want more help figuring out how to specify a custom account please provide more details.

ASE 15.7 Job Scheduler won´t start again

Hi,
we encoutered the following problem in our ECC6.0 / EHP5 on ASE 15.7 PL 122 System:
DBACockpit / Collector Configuration shows the warning "The ASE-Job Scheduler is not active". The log SID_JSAGENT shows the following entries:
00:11704:12104:2014/09/01 08:00:35.78 jamain Opening jsagent connection.
00:11704:12104:2014/09/01 08:00:35.78 jamain Agent will listen on <IP>
00:11704:12104:2014/09/01 08:00:35.78 jamain SYB_JSAGENT waiting for connection
00:11704:12104:2014/09/01 08:00:36.72 jamain Job Scheduler Agent connected with Job Scheduler Task on port 4903
00:11704:12104:2014/09/01 08:00:36.72 jamain Initializing SYB_JSAGENT
00:11704:12104:2014/09/01 08:00:36.72 jamain Allocating list resources.
00:11704:12104:2014/09/01 08:00:36.72 jamain Allocating queue resources.
00:11704:12104:2014/09/01 08:00:36.72 jamain Allocating thread resources.
00:11704:12104:2014/09/01 08:00:36.72 jamain Initializing connection pool.
00:11704:12104:2014/09/01 08:00:36.99 jamain Client message: ct_connect(): user api layer: external error: The connection failed because of invalid or missing external configuration data.
00:11704:12104:2014/09/01 08:00:36.99 jamain ct_connect() failed.
00:11704:12104:2014/09/01 08:00:36.99 jamain jsj_AddConxs: jsd_MakeConnection() failed for user jstask to server SID
00:11704:12104:2014/09/01 08:00:36.99 jamain jsj_CreateConxPool: jsj_AddConxs() failed
00:11704:12104:2014/09/01 08:00:36.99 jamain Initialization failed initializing connection pool
00:11704:12104:2014/09/01 08:00:36.99 jamain Jsagent failed to handle INIT message.
00:11704:12104:2014/09/01 08:00:36.99 jamain JS Agent aborting. Cancel all running jobs.
00:11704:12104:2014/09/01 08:00:36.99 jamain Job Processing failed.
00:11704:12104:2014/09/01 08:00:36.99 jamain JS Agent exiting.
Restarting the scheduler on ISQL doesn´t seem to work. Any ideas?
Many thanks & greetings
Vierengel Stefan

Hi,
thank you. Problem was solved by performing the following steps
1.     deleting the following file: DRIVE:\sybase\SID\OCS-15_0\ini\ocs.cfg
2.     Stop / Start Job Scheduler
         exec sybmgmtdb..sp_sjobcontrol '','stop_js'
        go
         exec sybmgmtdb..sp_sjobcontrol '','start_js'
        go
3.     Refresh DBACockpit
Greetings
Vierengel Stefan

Job Scheduling by Redwood workcenter

Hello ,
I want to do Job Scheduling by Redwood workcenter i already imported ST-PSM Add-on in SM-system(SM007-system name) Is it necessary to do this in child system (BI008-system name)?
Problem:
When i try to creat "Job Request" in workcenter i am get this problem "Business partner SWAROOP does not exist "but i already created BP SWAROOP in SM007(Solution Manager system).
Please let me know what are the other confi i have to do ?
Regards,
Swaroop

Hi,
first of all: The Add-On ST-PSM has to be installed on the Solution Manager system only. After the installation you can activate the additional IMG activities, see SAP note 1122497.
How to create a valid business partner for Job Requests:
1. Easy Solution: Create BP for an user in a remote system automatically (as decribed in IMG activity "Create Business partner"):
Two possibilties
a) Call menu function "Edit -> Create business partner" from within any solution of transaction DSWP
b) Run report DSWP_USER_PROPAGATION_TO_CRM directly (you need to know the solution ID that gets displayed directly after creation of a new solution)
2. Create BP manually (as decribed in IMG activity "Create Business partner"):
- Start transaction BP and create a new business partner and save it
- Go to tab "Identification" and add an External System Identifier (type CRM001) in the format <system ID><space><installation number><space><client><space><user name>
- save
- Add role "Employee" to your business partner and go to tab "Identification" and enter the corresponding user name.
- save
Please also review SAP note 1229982.
Kind regards,
Martin

Any reason why external jobs hang?

Hi
I'm in two minds as to whether this as an XE database problem or a general Scheduler problem so I'm trying my luck on this forum first.
Details: Database XE, Centos O/S
Problem
I can schedule all the different types of jobs and all except external jobs(job_type EXECUTABLE) do run. With external jobs, they just never complete running. It's not like they are doing anything either.
- Selecting from USER_SCHEDULER_RUNNING_JOBS while an external job is running just never comes back.
- Checking what's going on in v$session reveals an ACTIVE status and EVENT "JS external job".
- The xe_J00X os process doesn't seem to be doing anything. However, if I terminate(kill) it, it won't die except with kill -9, which frees up the database.
I have searched and tried a number of ideas but I haven't been able to resolve this.
So far
- I have tried the Metalink notes for setting permissions to nobody user.
- I have added #!/bin/ksh or #!/bin/bash to the shell scripts
- Implemented externaljob.ora
The results are the same. External jobs just hang, no error message, nothing.
I'd appreciate help if you can.
Thank you.
Siphiwe

Hi,
This is helpful and I can add some further comments.
- The Metalink notes were intended for normal SE/EE Oracle installs, there is no guarantee that they will work on XE. In fact your experiment shows that setting the permissions as in the Metalink note does not work on XE since nobody does not have access to the libclntsh.so.10.1 library (file and directory permissions are slightly different in XE) . You should ignore the Metalink notes and leave the original install permissions.
- because there is no extjobo executable, external jobs in the SYS schema will not work (although doing "cp extjob extjobo" should fix this) . This is a known filed bug.
- because the Metalink note does not work, all external jobs will run as the Oracle user. This is a security risk that should be taken into account whenever granting the CREATE EXTERNAL JOB system privilege to a user.
I can confirm that on an rpm installation of oracle-xe the following works for me when run as sys
-- test case for an external job on Oracle XE
create user testusr identified by testusr ;
grant create session, resource, create job, create external job to testusr;
connect testusr/testusr
begin
dbms_scheduler.create_job('job1','executable','/bin/sleep',1,
enabled=>false);
dbms_scheduler.set_job_argument_value('job1',1,'10');
dbms_scheduler.enable('job1');
end;
select * from all_scheduler_running_jobs;
select * from all_scheduler_job_run_details;
The job does run successfully and runs for 10 seconds as expected. I suggest you try this test case out after removing the pj files and fixing the permissions on extjob back to
-r-xr-xr-x 1 oracle dba 32068 Feb 19 2006 extjob*
Hope this helps,
Ravi.
null

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

Internal error occurs in background job scheduling

Hi Experts,
We are facing an error message "Internal error occurs in background job scheduling" while trying to execute a custom report(Z report) in background in SA38.
Please find the following observation on our side on this message.
1) This message is not coming for only one report not for others.
2) SU53 screen shot shows that SE38 check is failed, but the weird thing is not happening for other report.
3) Persons having SE38 auhtorization are able to run this report.
Please advise.
Thanks in advance,
Viven

What is the message ID and number? Have you tried OSS search and debugging?
What does this program do, in a nutshell?

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

External Job Scheduling on XI 3.0

Similar Messages

Maybe you are looking for