Schedule reorg/runstats jobs in BI using Control-M as scheduler not DB13

We would like to define the reorg/runstats jobs in a process chain in our BI system and use Control-M as scheduler .
Does anybody know how to define reorg/runstats jobs without using DB13?

Hi,
check following notes
Note 915398 - DB2-z/OS: BW: New algorithm for calling RUNSTATS
Note 1146378 - DB2-z/OS:CCMS: Changed RUNSTATS handling for BW tables
regards,
kaushal

Similar Messages

HT5858 When I swipe up from the bottom of the screen to use control center I am not able to use the music controls for music or podcasts and music controls do not work on the lock screen either is anybody else having this problem???????

When I swipe up from the bottom of the screen to use control center I am not able to use the music controls for music or podcasts and music controls do not work on the lock screen either is anybody else having this problem???????

Not really sur easy you would be having that problem. Mine works. You might try RESET DEVICE
Hold down the Sleep/Wake button and the home button together until the apple logo appears (ignore the ON/OFF slider) then let both buttons go and wait for device to restart (no data will be lost). Then try again and see if it makes a difference

How can we schedule the finished job in SM37 ?

Hi,
I need to schedule all the jobs which are running in Production to a common user (Ex. BWGURU). Presently the jobs are running on different users in SM37. My requirement is to schdule all the running / finished / scheduled /released / cancelled jobs to a common user. I am not manaage to schedule the finished / cancelled job. How can i do that ?
Please required ur inputs .
thanks
Praveen.

Hi Praveen.....
U can't never make a finished job to released............First a Job will be in Release state...........then it will be in Schedule.........then the Job will Start...........then either finish or Cancelled...........
To start a job...............u hav ti to take the Released state of the Job to schedule......
Hav u Clicked on immediate tab...........there just check the immediate box................then check and save...........
U hav said.......i am getting extra job running with the same name............u mean that the job is is running State .............right.........Look u cannot create two jobs in same name...............may be that job is running.............hav u scheduled the job ?............may be thats why it is running..............if u want to cancel the running job.............double click on the job.............from job details copy the PID and Application server.............come out...........click on Application Server...............double click on the desired server...search the PID.and cancel the job.............
Regards,
Debjani..........

Can we schedule Loader Jobs (SQL Loader) using Grid Control ?

Can we schedule SQL Loaders jobs/process using Grid Control for 11g database ?
Or
Is it good to schedule it as external jobs using DBMS_SCHEDULER ?
OS is LINUX. Database is 11g R1 Grid Control will be the latest, I believe 10gR3.
Any other suggestions... (I know it can be done using OS utilities like cron and others but that is not an option for now.)
Thanks in advance.

Try this
-> Create a shell script to execute sqlldr
-> On Grid, create an "OS COMMAND" job and pass this script as parameters. You'll have options to schedule this job.
Let us know how it works.

Scheduling an Export Job Using Grid Control

Hi,
I got a requirement to schedule export jobs in Oracle Grid Control 10.2.0.5 (Windows). Is this possible and have any one done this? If so please share the steps. The idea is to get alerts if the job fails.
Thanks.
GB

Here is the easy steps (There might be slight differences as I am posting it based on 11g screen)
1. On grid control console, click on the relevant database
2. click on 'Data Movement' tab
3. Click on 'Export to Export Files'
4. chose the Export type (Database / Schema / Tables/ Tablespace)
5. Provide Host credentials (OS username and Password) and click on 'Continue'. You will get a new screen called 'Export: Options'
6. Click the checkbox called 'Generate Log File' and select the Directory object where you wants to create the dump files. (You need to create a directory object in database, if you don't have one)
7. Chose the contents option as you required, and click '*Next*'. You will get a new page called 'Export: Files'
8. Select the directory object from the drop-down box and provide a name format for file name, and click 'Next'
9. Here you provide the Job name and description, and chose repeat options (daily, weekly etc), and click 'Next'
10. You will get a summary screen called 'Export: Schedule'. review your job details and click on 'Submit'.
This is the solution, and it works well.

How can i schedule jobs daily by using fm's

hi all,
am using open job ,submit job,close job fm's to schedule back ground jobs,
want to schedule it daily which parameter i need to pass in close_job for daily job scheduling

you can get the clear documentation by using ABAPDOCU transaction.
Regards
Mani.

Schedule a daily job using JOB_CLOSE

Hello,
I want to schedule a daily job using job_open, job_submit & job_close.
This job should run everyday at 22:00 hrs.
What are the parameters I need to set for the FM JOB_CLOSE?
Thanks,
A Pothuneedi

Look at this sample provided by SAP : <a href="http://help.sap.com/saphelp_sm32/helpdata/en/fa/096d8e543b11d1898e0000e8322d00/content.htm">Sample Program: Start-Time Window with JOB_CLOSE</a>
Sample Program: Start-Time Window with JOB_CLOSE Locate the document in its SAP
<b>Library structure</b>
* Submit job: start-time window defined, with periodic repeat and
* with target system upon which the job is to run.
* In this case, you must provide start date settings. You can
* have the job started immediately with a JOB_CLOSE parameter,
* set the start date yourself, or ask the user with
* BP_START_DATE_EDITOR.
* Example: Provide start-date specifications yourself.
STARTDATE = '19970101'.
STARTTIME = '160000'.
LASTSTARTDATE = '19970101'.
LASTSTARTTIME = '180000'.
CALL FUNCTION 'JOB_CLOSE'
EXPORTING
JOBCOUNT = JOBNUMBER " Job identification: number
JOBNAME = JOBNAME " and name.
SDLSTRTDT = STARTDATE " Start of start-time...
SDLSTRTTM = STARTTIME " window
LASTSTRTDT = LASTSTARTDATE " Optional: end of...
LASTSTRTTM = LASTSTARTTIME " start-time window
PRDMONTHS = '1' " Restart at intervals of
PRDWEEKS = '1' " the sum of the PRD*
PRDDAYS = '1' " parameters
PRDHOURS = '1'
PRDMINS = '1'
STARTDATE_RESTRICTION = BTC_DONT_PROCESS_ON_HOLIDAY
" Restrict job start to work
" days; don't start job if
" scheduled on holiday.
" Other values:
" BTC_PROCESS_BEFORE_HOLIDAY
" BTC_PROCESS_AFTER_HOLIDAY
CALENDAR_ID = '01' " ID of R/3 factory calendar
" for determining workdays
TARGETSYSTEM = 'hs0011' " Optional: name of the host
" system on which the job is
" to run. Set only if
" absolutely required.
" Example: A required tape
" drive is accessible only
" from a single host system.
IMPORTING
JOB_WAS_RELEASED = JOB_RELEASED " If user has authorization
" to release jobs to run, job
" is automatically released
" when it is scheduled. This
" field is set to 'x' if the
" job has been released.
" Otherwise, the job is sche-
" duled but must be released
" by an administrator before
" it can be started.
EXCEPTIONS
INVALID_STARTDATE = 01
JOBNAME_MISSING = 02
JOB_CLOSE_FAILED = 03
JOB_NOSTEPS = 04
JOB_NOTEX = 05
LOCK_FAILED = 06
OTHERS = 99.
IF SY-SUBRC > 0.
<Error processing>
ENDIF.
Regards

Schedule a background job for a program using ABAP code.

Hi,
I have to write a program to schedule a background job for another program.
Need your help to understand how we can achieve this functionality.Any example of an abap code would be of great help.
Need it urgently.
Thanks in advance.
Sandeep.

Hi Sandeep,
Here is the demo program regarding the BDC For the background job.
report zprprbdc1
       no standard page heading line-size 255.
include bdcrecx1.
parameters: dataset(132) lower case.
***    DO NOT CHANGE - the generated data section - DO NOT CHANGE    ***
*   If it is nessesary to change the data section use the rules:
*   1.) Each definition of a field exists of two lines
*   2.) The first line shows exactly the comment
*       '* data element: ' followed with the data element
*       which describes the field.
*       If you don't have a data element use the
*       comment without a data element name
*   3.) The second line shows the fieldname of the
*       structure, the fieldname must consist of
*       a fieldname and optional the character '_' and
*       three numbers and the field length in brackets
*   4.) Each field must be type C.
*** Generated data section with specific formatting - DO NOT CHANGE ***
***data: begin of itab occurs 0 ,
***       matnr(20) type c,
***       mbrsh(30) type c,
***       mtart(30) type c,
***       kzsel(20) type c,
***       maktx(40) type c,
***       meins(5) type c,
***       end of itab.
data: begin of record occurs 0,
* data element: MATNR
        matnr_001(018),
* data element: MBRSH
        mbrsh_002(001),
* data element: MTART
        mtart_003(004),
* data element: XFELD
        kzsel_01_004(001),
* data element: MAKTX
        maktx_005(040),
* data element: MEINS
        meins_006(003),
* data element: MTPOS_MARA
        mtpos_mara_007(004),
      end of record.
*** End generated data section ***
start-of-selection.
*perform open_dataset using dataset.
perform open_group.
**do.
**read dataset dataset into record.
**if sy-subrc <> 0. exit. endif.
call function 'GUI_UPLOAD'
exporting
    filename                      = 'c:\jitu\bdc\10002.txt'
   filetype                      = 'ASC'
   has_field_separator           = 'x'
*   HEADER_LENGTH                 = 0
*   READ_BY_LINE                  = 'X'
*   DAT_MODE                      = ' '
*   CODEPAGE                      = ' '
*   IGNORE_CERR                   = ABAP_TRUE
*   REPLACEMENT                   = '#'
*   CHECK_BOM                     = ' '
*   VIRUS_SCAN_PROFILE            =
*   NO_AUTH_CHECK                 = ' '
* IMPORTING
*   FILELENGTH                    =
*   HEADER                        =
tables
    data_tab                      = record
* EXCEPTIONS
*   FILE_OPEN_ERROR               = 1
*   FILE_READ_ERROR               = 2
*   NO_BATCH                      = 3
*   GUI_REFUSE_FILETRANSFER       = 4
*   INVALID_TYPE                  = 5
*   NO_AUTHORITY                  = 6
*   UNKNOWN_ERROR                 = 7
*   BAD_DATA_FORMAT               = 8
*   HEADER_NOT_ALLOWED            = 9
*   SEPARATOR_NOT_ALLOWED         = 10
*   HEADER_TOO_LONG               = 11
*   UNKNOWN_DP_ERROR              = 12
*   ACCESS_DENIED                 = 13
*   DP_OUT_OF_MEMORY              = 14
*   DISK_FULL                     = 15
*   DP_TIMEOUT                    = 16
*   OTHERS                        = 17
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
loop at record .
perform bdc_dynpro      using 'SAPLMGMM' '0060'.
perform bdc_field       using 'BDC_CURSOR'
                              'RMMG1-MATNR'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'RMMG1-MATNR'
                              record-matnr_001.
perform bdc_field       using 'RMMG1-MBRSH'
                              record-mbrsh_002.
perform bdc_field       using 'RMMG1-MTART'
                              record-mtart_003.
perform bdc_dynpro      using 'SAPLMGMM' '0070'.
perform bdc_field       using 'BDC_CURSOR'
                              'MSICHTAUSW-DYTXT(01)'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(01)'
                              record-kzsel_01_004.
perform bdc_dynpro      using 'SAPLMGMM' '4004'.
perform bdc_field       using 'BDC_OKCODE'
                              '=BU'.
perform bdc_field       using 'MAKT-MAKTX'
                              record-maktx_005.
perform bdc_field       using 'BDC_CURSOR'
                              'MARA-MEINS'.
perform bdc_field       using 'MARA-MEINS'
                              record-meins_006.
perform bdc_field       using 'MARA-MTPOS_MARA'
                              record-mtpos_mara_007.
perform bdc_transaction using 'MM01'.
**enddo.
endloop.
perform close_group.
*perform close_dataset using dataset.
&*****************Reward point if helpful************&

How to schedule a background job using the Event concept..?

Hi Folks,
I have a requirement that, I need a schedule a background job.
Once after the previous job successful only, new job should get triggered. How to go ahead with this..?
For Eg, I am scheduling a job called ZTEST periodically for 1 minute. If the job is not get completing with in 1 minute, I dont want to start my new job. Only after the success of my old job, I want my new job to run.
Waiting for ur replies.
Regards,
Savi.

Hi,
You can use events that have already been defined, or you can create new events for scheduling background jobs.
If you wish to use new events, do the following to implement the event scheduling:
Define and transport the event as a user event with transaction SM62.
You must define only event IDs; event arguments are not defined in the R/3 System. Instead, you specify event arguments when you schedule a job to wait for an event and when you trigger the event.
If you define a new event, you must also transport it to your production systems. The event transaction does not have a connection to the transport system. Instead, you must create a transport request for the event yourself.
Do this to transport an event:
Create a transport request.
Start the editor in the transport request and enter the following:
R3TR TABU <table name> where table name is BTCSEV for a system event ID, BTCUEV for a user event ID.
Press F2 with the cursor on the table name to call up the screen for specifying the table entries to transport. In this screen, enter the event IDs that you have created.
Save and release the transport request. Ensure that it is imported into your production system(s).
To trigger an event, add:
the function module BP_EVENT_RAISE to your ABAP program, or
the program SAPEVT to your external script, batch file, or program.
When your programs execute these keywords, an event will be triggered in the R/3 background processing system. The event-based scheduler is started immediately. It in turn starts all jobs that were waiting upon the event, subject to normal background processing restrictions, such as the requirement that the job has been released to start.
Schedule the jobs that are to run when your events are triggered.
You can schedule jobs for one-time start or to be started whenever an event is triggered.
Regards,
Raj.

How to schedule the background job using current selection screen field val

Hello Friends,
How to schedule the background job using current selection screen field values.
after completion of the job the spool should be sent as a mail to SAP Inbox.
Is there any way to create the variant dynamically by reading the current selection screen values.
Thanks,
Ravi

Hi,
To get the variant details you can use teh following FM.
'RS_VARIANT_CONTENTS'.
Regards,
Ankur Parab

CCM schedule job and OCI used

Hi all,
We are using Requisite BugsEye 4.0.5.6 with SRM 4.0. I'm studying CCM 2.0 to replace BugsEye and need helps from all of you:
Q1: I saw a screen in service marketplace presentation, schedule upload catalog job in CCM need to specify Catalog ID and Supplier ID. Are these IDs mandatory and what if we have 20 catalog and 500 suppliers, thus in worst case I need to run 20x500 jobs. It this true?
Q2: Can CCM schedule daily job to run at specific time?
Q3: In Requisite, OCI-HTML document will be posted to SRM. What OCI document is posted back by CCM, OCI-HTML or OCI-XML?
Q4: On the same presentation there is a statement "SAP CCM does not support exporting of content as files ...". Since we have other application polling export file from BugsEye catalog content. Is there any other way to export CCM catalog content?
Thanks in advance.
Regards,
Donald Lee

Hi,
Q1: Yes
Q2: CCM is an SAP WAS 640 Add-on, the job schedduling is made manually, There is no CCM customizing point that automatically creates jobs, so you can scheddule them whenever you want, and specify the time.
Q3: OCI is an SAP norm, you can use OCI-XML for asynchronous process, it should also be possible with CCM (depends on the catalog link definition)
Q4: There is no sytandard exporting tool within CCM, but, once again, CCM is a SAP WAS addon developed in BSP and the data are stored in the WAS database. So you canmake whatever development you want, especially for exporting purposes.
Regards.
VAdim

How to schedule the background job daily twice?

Hi,
How to schedule the background job daily twice? any conditions?
Regards,
Srihitha

see the step by step procedure.
Scheduling Background Jobs:
1. Background jobs are scheduled by Basis administrators using transaction SM36.
2. To run a report in a background, a job needs to be created with a step using the report name
and a variant for selection parameters. It is recommended to create a separate variant for each
scheduled job to produce results for specific dates (e.g. previous month) or organizational units (e.g.
company codes).
3. While defining the step, the spool parameters needs to be specified
(Step-> Print Specifications->Properties) to secure the output of the report and help authorized users
to find the spool request. The following parameters needs to be maintained:
a. Time of printing: set to Send to SAP spooler Only for now
b. Name abbreviated name to identify the job output
c. Title free form description for the report output
d. Authorization a value defined by Security in user profiles to allow those users to access
this spool request (authorization object S_SPO_ACT, value SPOAUTH). Only users with matching
authorization value in their profiles will be able to see the output.
e. Department set to appropriate department/functional area name. This field can be used in
a search later.
f. Retention period set to Do not delete if the report output needs to be retained for more
than 8 days. Once the archiving/document repository solution is in place the spool requests could
be automatically moved to the archive/repository. Storage Mode parameter on the same screen
could be used to immediately send the output to archive instead of creating a spool request.
Configuring user access:
1. To access a report output created by a background job, a user must have at
least access to SP01 (Spool requests) transaction without restriction on the user
name (however by itself it will not let the user to see all spool requests). To have
that access the user must have S_ADMI_FCD authorization object in the profile with
SPOR (or SP01) value of S_ADMI_FCD parameter (maintained by Security).
2. To access a particular jobs output in the spool, the user must have
S_SPO_ACT object in the profile with SPOAUTH parameter matching the value used
in the Print Specifications of the job (see p. 3.d above).
3. Levels of access to the spool (display, print once, reprint, download, etc) are
controlled by SPOACTION parameter of S_SPO_ACT. The user must have at least
BASE access (display).
On-line reports:
1. Exactly the same configuration can be maintained for any output produced
from R/3. If a user clicks Parameters button on a SAP Printer selection dialog, it
allows to specify all the parameters as described in p. 3 of
Scheduling background jobs section. Thus any output created by an online report
can be saved and accessed by any user authorized to access that spool request
(access restriction provided by the Authorization field of the spool request
attributes, see p. 3.d of Scheduling background jobs section).
Access to reports output:
1. A user that had proper access (see Configuring user access above) can
retrieve a job/report output through transaction SP01.
2. The selection screen can be configured by clicking Further selection
criteria button (e.g. to bring Spool request name (suffix 2) field or hide other
fields).
3. The following fields can be used to search for a specific output (Note that
Created By must be blank when searching for scheduled jobs outputs)
a. Spool request name (suffix 2) corresponds to a spool name in p. 3.b in
Scheduling background jobs section above).
b. Date created to find an output of a job that ran within a certain date range.
c. Title corresponds to spool Title in p. 3.c in Scheduling background jobs
section above).
d. Department - corresponds to spool Department in p. 3.e in Scheduling
background jobs section above).
4. Upon entering selection criteria, the user clicks the Execute button to
retrieve the list of matching spool requests.
5. From the spool list the user can use several function such as view the
content of a spool request, print the spool request, view attributed of the spool
request, etc. (some functions may need special authorization, see p.3 in
Configuring user access)
a. Click the Print button to print the spool request with the default attributes
(usually defined with the job definition). It will print it on a printer that was
specified when a job was created.
b. Click the Print with changed attributed button to print the spool request
with the different attributes (e.g. changing the printer name).
c. Click the Display contents button to preview the spool request contents. A
Print and Download functions are available from the preview mode.

How to Schedule a V3 Job

Hi
How to schedule a V3 job in ECC to execute at reqular intervals
Thanks

Hi
As already answered it could be scheduled using job control option relating to datasource in R/3 system.
In addition to these you can also set the V3 jobs if you have an external job controlling system which would execute V3 programs are regular interval as desired.
Various V3 programs as as:
RMBWV303     V3 job for Inventory
RMBWV312     V3 job for Deliveries
RMBWV313     V3 job for Invoices
RMBWV308     V3 job for Shipments
RMBWV318     V3 Job for Services
RMBWV311     V3 Job for Orders
RMBWV302     V3 Job for Purchase
Regards
Ashish

Schedule periodic Dunning job in SAP

When i execute the program: RF150SMS
I am getting the message:
Dunning run 08/04/2009 DUNNI for template not found
Message no. FM016
I am not sure If i am executing the correct program
Could you please tell how would it be possible to schedule a periodic job for printing dunning ?
Or Any advise on how to schedule the dunning job in SAP
Thank you

Hi ,
U don't need to schedule a server proxy ...as the proxy will kick in automatically as soon as the message is processed by file adapter .
Since yours is File to proxy scenario...
and you want to execute it overnight ..
You will have to control when the file is processed by XI file adapter.
Here what you can do ..
Let's just say your file gets placed in a Folder 'A' ...and your file communication channel is configured to pick files from folder B.
Write an abap code on xi box ..(or you can use a V.B. script)
which will move the file from folder A to Folder B.This code can easily be scheduled..so that it you can get files in folder B from where XI processig will kick in .
(job scheduling can be done sm36 ..use the wizard)

How to schedule the back job scheduling

how to schedule the back job for bdc , can we use it for both call transaction and session method . how to schedule the back job schedulinng for lsmw

hi,
Use t-code SM36 for scheduling.
<b>Do reward.</b>

Schedule reorg/runstats jobs in BI using Control-M as scheduler not DB13

Similar Messages

Maybe you are looking for