Background SNP processes

hello.
im trying to shedule an event to run everyday. The event (deletion of records according to sysdate) is automatically executed in the background.
i have submitted a job in the job queue using code:
variable jobno number;
execute DBMS_JOB.SUBMIT(:jobno, 'deleteexpiredads;', SYSDATE, 'SYSDATE + 1/96');
im aware that the system must be altered to disable the restriction on my session to allow background SNP processes to execute the jobs in queue. This is done using:
ALTER SYSTEM DISABLE RESTRICTED SESSION;
For some reason the job is never executed. If i force the job to run it works fine but otherwise its not picked up.
can anybody please help ?
null

thank you, got it working, much appretiated.
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by jlehman ([email protected]):
the job_queue_processes parameter must be set to a positive value in your init.ora file (bounce db reqd).
this parameter tells oracle how many oracle background processes to keep running.
the job_queue_interval parameter tells the processes how often to keep checking the queue for jobs to run.<HR></BLOCKQUOTE>
null

Similar Messages

Background schedule process

Hi
I am new to Oracle 9iAS. Can someone tell me if there is any
better way to implement a background scheduled process ?
Currently, I am doing it via AT command. Just wondering if
Oracle9iAS has any scheduler that I can make use of.
Thanks
CT

You can set up the different step while schedule the back ground job. Each step will have the program name, variant.
You can do his using transaction SM36 -> JOB WIZARD.
Thanks,
Srinivas

Error occurs in background work process.

Respected Guru's,
error occurs in two background work process, i have displayed the trace files of both the bgd work process.
How to rectify this error ?
Further, can you please help me in identifying the problem, please suggest me good material which gives steps for troubleshooting such error in the developer's and system trace.
Thank you.
Dayanandan.a
Developer trace file for BGD WP 1
trc file: "dev_w12", trc level: 1, release: "620"
ACTIVE TRACE LEVEL           1
ACTIVE TRACE COMPONENTS      all, M
M systemid   560 (PC with Windows NT)
M relno      6200
M patchlevel 0
M patchno    251
M intno      20020600
M pid        2864
M
M ***LOG Q0Q=> tskh_init, WPStart (Workproc12 2864) [dpxxdisp.c   1016]
M <EsNT> Memory Reset enabled as NT default
M calling db_connect ...
M db_connect o.k.
M rdisp/reinitialize_code_page -> 0
M
M Tue Jul 30 10:22:53 2002
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020730.AUD
M
M Tue Jul 30 10:22:55 2002
M *** ERROR => SlicLockSema: sema locked [slicshm.c    89]
M *** ERROR => SlicShmInit: SlicLockSema failed [slicshm.c    231]
M *** ERROR => SlicValBufInit: cannot initialize SHM [slicshm.c    299]
M *** ERROR => SlicValBufRead: license buffer not initialized [slicshm.c    329]
M *** ERROR => SlicCheckBuf: some error reading license buffer contents [slicshm.c    419]
M
M Wed Jul 31 00:00:49 2002
M SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020730.AUD
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020731.AUD
M Thu Aug 01 00:00:49 2002
M SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020731.AUD
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020801.AUD
M
M Fri Aug 02 00:00:49 2002
M SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020801.AUD
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020802.AUD
M
M Fri Aug 02 00:14:09 2002
M *** ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_COMMIT failed [thxxtool3.c 235]
M ***LOG R38=> ThICommit3, db_commit98 ( 001024) [thxxhead.c   10641]
M ***LOG R18=> ThPrivCommit, ThICommit () [thxxhead.c   11307]
M in_ThErrHandle: 1
M *** ERROR => ThPrivCommit: ThICommit (step 4, th_errno 9, action 2, level 1) [thxxhead.c   8277]
M
M Info for wp 12
M
M    stat = 4
M    reqtype = 4
M    act_reqtype = 4
M    tid = 12
M    mode = 0
M    len = 24
M    rq_id = 6638
M    rq_source = 1
M    last_tid = 12
M    last_mode = 0
M    rfc_req = 0
M    report = >                                        <
M    action = 16
M    tab_name = >                              <
M
M
M Modeinfo for User T12/M0
M
M    tm state = 2
M    uid = 13
M    term type = 0x0
M    display = 0x0
M    cpic_no = 0
M    cpic_idx = -1
M    usr = >SAPUSER     <
M    terminal = >                    <
M    client = >800<
M    conversation_ID = >        <
M    appc_tm_conv_idx = -1
M    imode = 3
M    mode state = 0x42
M    th_errno = 9
M    async_receives = 0
M    cpic_receive = 0
M    em handle = 2
M    roll state = 4
M    abap state = 4
M    em state = 3
M    eg state = 1
M    lock = 0
Developer's trace file for BGD WP 2
trc file: "dev_w13", trc level: 1, release: "620"
ACTIVE TRACE LEVEL           1
ACTIVE TRACE COMPONENTS      all, M
M systemid   560 (PC with Windows NT)
M relno      6200
M patchlevel 0
M patchno    251
M intno      20020600
M pid        2872
M
M ***LOG Q0Q=> tskh_init, WPStart (Workproc13 2872) [dpxxdisp.c   1016]
M <EsNT> Memory Reset enabled as NT default
M
M Tue Jul 30 10:21:44 2002
M calling db_connect ...
M db_connect o.k.
M
M Tue Jul 30 10:22:25 2002
M rdisp/reinitialize_code_page -> 0
M
M Tue Jul 30 10:22:53 2002
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020730.AUD
M
M Wed Jul 31 00:00:52 2002
M SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020730.AUD
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020731.AUD
M
M Thu Aug 01 00:00:49 2002
M SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020731.AUD
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020801.AUD
M
M Fri Aug 02 00:00:51 2002
M SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020801.AUD
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020802.AUD
M
M Fri Aug 02 00:14:09 2002
M *** ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_COMMIT failed [thxxtool3.c 235]
M ***LOG R38=> ThICommit3, db_commit98 ( 001024) [thxxhead.c   10641]
M ***LOG R18=> ThPrivCommit, ThICommit () [thxxhead.c   11307]
M in_ThErrHandle: 1
M *** ERROR => ThPrivCommit: ThICommit (step 4, th_errno 9, action 2, level 1) [thxxhead.c   8277]
M
M Info for wp 13
M
M    stat = 4
M    reqtype = 4
M    act_reqtype = 4
M    tid = 13
M    mode = 0
M    len = 24
M    rq_id = 6643
M    rq_source = 1
M    last_tid = 13
M    last_mode = 0
M    rfc_req = 0
M    report = >                                        <
M    action = 16
M    tab_name = >                              <
M
M Modeinfo for User T13/M0
M
M    tm state = 2
M    uid = 14
M    term type = 0x0
M    display = 0x0
M    cpic_no = 0
M    cpic_idx = -1
M    usr = >SAPUSER     <
M    terminal = >                    <
M    client = >800<
M    conversation_ID = >        <
M    appc_tm_conv_idx = -1
M    imode = 3
M    mode state = 0x42
M    th_errno = 9
M    async_receives = 0
M    cpic_receive = 0
M    em handle = 3
M    roll state = 4
M    abap state = 4
M    em state = 3
M    eg state = 1
M    spa state = 3
M    enq state = 0
M    next hook = T-1/U-1/M255
M    master hook = T-1/U-1/M255
M    slave hook = T-1/U-1/M255
M    debug_tid = -1
M    mode type = 0x1
M    debug = 0
M    lock = 0
M
M
M Sat Aug 03 00:00:55 2002
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020803.AUD
M
M Sun Aug 04 00:00:49 2002
M SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020803.AUD
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020804.AUD
M
M Mon Aug 05 00:00:49 2002
M SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020804.AUD
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020805.AUD
M
M Tue Aug 06 00:00:49 2002
M SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020805.AUD
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020806.AUD

Thank you, Bhaskar,
I have performed consistency check for temse objects and all the comments are displayed in red color.
Does it mean that objects are inconsistent. But, no comments states that object are inconsistent.
I have attached the comments displayed,
Consistency check of table TST01 / TemSe objects
This comment occurs repeatedly, Unable to access the related file           Length = 0
Incorrect number of data lines in TST03
Object with part number 1 missing
Object reset                     Length = 0
The related file has an incorrect length
Consistency check of table TST03 / TemSe data
No object found in TST01
May i delete all objects, as all the comments are red in color.
Dayanandan.A

How to find out number of background work processe available in the system?

Hi All,
I have a FM that triggers a background job using JOB_OPEN, ABAP_SUBMIT and JOB_CLOSE. But the problem is if there are no background work processes available at that moment, it does not return error. Not sure whether the job is even scheduled!
Is there a way to find out if there are any background work processes available in the system? I know a FM SPBT_INITIALIZE which gives info about dialog work processes. Is there any other FM similar to this which gives info about background wp??
Regards,
Shailesh

your Job will remain in a queue by message handler. once workprocess is free, your job gets scheduled
by the way, you can use the functionality used in FM TH_DISPLAY_WORKPROCESS_LIST to read the workprocesses
the command which gets you the workprocess is:
CALL 'ThWpInfo' ID 'OPCODE' FIELD OPCODE_WP_LIST
ID 'TAB' FIELD LIST_STATE_WPLST-TABL
ID 'CPU' FIELD LIST_STATE_WPLST-CPU.
check how its written in include LSDEBF01, form SET_LIST_WPLST
Edited by: Soumyaprakash Mishra on Dec 12, 2011 12:17 PM

Function module in background work process

Hi All,
i'm using trfc for processing FM only in background work process
CALL FUNCTION 'FUNCTION_MODULE' IN BACKGROUND TASK
but when i execute FM it's occupying two work process one is dialog (running current FM )and another one is background( running SAPLERFC) .
so pls suugest me how to avaiod FM to occupy dialog workprocess.
Regards,
Anuj jain

Hi Anuj,
It unfortunately means:
start FM in a particular time in Dialog work process
The BACKGROUND word in abap syntax is misleading.
For true background processing, i.e. background WORK PROCESS (of type BGD in SM50)
ONLY ABAP PROGRAMS or Commands or External Programs
can be run under background work process. (as per SM36)
Here we are trying a function module, which is not supported. This is as per my understanding.
regards,
amit m.
Edited by: Amit Mittal on Aug 17, 2010 2:03 PM
Edited by: Amit Mittal on Aug 17, 2010 2:05 PM

Increase the number of background work processes for data load performance

Hi all,
There are 10 available background work processes in the BW system. We're doing some mass load to multiple ODS.But system uses only 3 background processes. How can i
increase the number of used background work processes for new data load.
I tried to change number of prosesses with RSODSO_SETTINGS. But no successes. Are there any other settings need to change?
thanks,
Yigit

Hi sankar,
I entered the max proc. number into ROIDOCPRMS. But it doesn't make difference. System still uses only 3 of background processes. RSCUSTA2 is replaced with
RSODSO_SETTINGS in BI 7.0 and this trans. can only change the processes for data activation, SID generation and rollback. I need to change the process numbers for data extraction.

Free background work process

Hi All,
how to check statistics of free background work process in the system.
Regards,
MK

Hello Manikandan,
RZ20 has a monitor for this under
RZ20 --> SAP CCMS Monitor Templates
               --> Background Processing
                    --> System Wide
                         --> Background
                             --> BackgroundService
                                  --> SystemWideFreeBPWP
If you need statistics for a longer time period you can activate collection of data for this MTE in CPH.
Regards,
Alwina

Calling subroutine perform background work process

Hi all,
Can we call a perform (subroutine)in background work process in a program.
if yes, pls specify.
regards,
Anuj

Anuj,
we can call the subroutine..whether it is foreground or background..if the perform statement is used the respective routine is called . Can you be specific on the requirement you are looking after..
Sagar.

Background work process On-hold

Hello,
There is a background job running in Production system for more that 10000ms.
Background work processes is on-hold and the resaon is ARFC.
Following is the log file:
X Thu Jun 11 07:31:10 2009
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
Can any one help.
Trupti

Hi,
In addition to above check below links. it speaks about same error message.
Re: Kernel upgrade to 700.175 UC incresing the dev_w0 log drastically
Re: RFC_VMC_COMMUNICATION_ERROR
Thanks
Sushil

Background work process

How to increase the background work processes on BW SYSTEM
Thanks your help in advance
Msr

- start transaction RZ10
- open your instance profile
- edit it using the "Basic Maintenance" radio button
- increase the background processes
- save
- confirm
- restart the instance
Markus

Update Work Process and Background work process

Hi Friends,
I have a doubt regarding the "Update Work Process and Background work process" ......
which one is used at what scenario ?????
If not wrong --> update work process is used when there is an update task .........??? and similarly If background work process is used when there a background task is given explicitly .........???
Can we can update anything through Background>????
If yes .... which workprocess will be selected at that time??????
Expecting your answers ??
Thanks in advance !!
Cheers
R.Kripa.

HI
GOOD
UPDATE WORK PROCESS->
http://help.sap.com/saphelp_nw04s/helpdata/en/e5/de86e135cd11d3acb00000e83539c3/content.htm
BACKGROUND WORK PROCESS->
http://help.sap.com/saphelp_nw2004s/helpdata/en/4a/2d513897110872e10000009b38f889/content.htm
THANKS
MRUTYUN

When connecting Apple devices to your iPhones wireless hotspot do those devices stop background data processes to conserve data?

When connecting Apple devices to your iPhones wireless hotspot do those devices stop background data processes to conserve data?
In other words if you have a limited data plan on your iPhone will your other Apple devices such as an iPad automatically cease background data transfers to conserve data usage?

Nice trick to connect your Apple Devices to your wireless network.
Will help the users if they are facing the problem with the apple devices.

Background Job processing

After writing a report, I used this Function Module LIST_TO_ASCI to copy my report to an internal table (DOWNTAB) because Ill use that internal table to download a text file on the server using dataset.
Here is my code:
FORM DL_REP_SERVER.
   DATA: ABAP_LIST LIKE ABAPLIST OCCURS 1,
        MV_FILE2 LIKE RLGRAP-FILENAME.
DATA: BEGIN OF DOWNTAB OCCURS 1,
          LINE(150),
        END   OF DOWNTAB.
CLEAR: MV_FILE2.
MV_FILE2 = J:/Downloads/Report.txt.
CALL FUNCTION 'LIST_TO_ASCI'
       EXPORTING
            LIST_INDEX         = SY-LSIND
       TABLES
            LISTASCI           = DOWNTAB
            LISTOBJECT         = ABAP_LIST
       EXCEPTIONS
            LIST_INDEX_INVALID = 1
            OTHERS             = 2.
OPEN DATASET MV_FILE2 FOR OUTPUT IN TEXT MODE.
IF SY-SUBRC <> 0.
    IF SY-SUBRC = 8.
      MESSAGE E037 WITH 'File could not be opened'.
    ELSE.
      MESSAGE E037 WITH 'Error occurs in downloading the file'.
    ENDIF.
ENDIF.
LOOP AT DOWNTAB.
    TRANSFER DOWNTAB TO MV_FILE2.
ENDLOOP.
CLOSE DATASET MV_FILE2.
ENDFORM.                    " DL_REP_SERVER
My big problem is this, when Im running my program ordinarily (not as background job), Im getting all the pages downloaded correctly but when I run it as background job (using SM36), Im only getting the last page of my report being downloaded. Definitely, I cant debug it because its in background. I cant figure out why. Hope that I stated my problem clearly. Any help would be greatly appreciated. Thanks.

You can debug batch jobs by going to 'SM37', type in 'JDBG' in the
command line ( no '/' ), put the cursor on the job and press enter - will
take you to the job in debug mode.
You can do this only after the job has finished execution. This will simulate the exact background scenario with the same selection screen values as used in the job also sy-batch will set to 'X'.
So type in the transaction code 'JDBG' and place your cursor on the job after It has finished. It will take you to a SAP program in debug mode. Step through this program which is about 10 lines, after this your program will be executed in the debug mode.
Steps
1. Create variant called BACKGROUND for program to be debugged.
2. Execute ZDEBUGBG (pgm code below) in background for immediate processing.
3. Execute transaction SM50.
4. Select process that runs ZDEBUGBG.
5. Goto 'Program/Session' 'Program' 'Debugging'.
A se80 debug session will open.
6. Change variable W_EXIT to 'E'.
7. Step thru (F6) until ZWBTEST comes up.
1. Go to Transaction SM66 and find your work porocess.
Select the line work process is on and click on the Debugging button.
If this is a custom program, you can put a wait statement in the code to buy yourself sometime.
2. Go to Transaction SM50. From the tool bar "Program/session"->Program->Debugging.
goto SM37 and from Program menu(not sure.. try other menu's)
-->Catchjob . it will goto the active job in debugging mode.

Background Job Processing Spool Retention period

Hi ,
In my program i am calling another ABAP program and sumitting the same as a background job(using Job_Submit,Close etc.)
In this case i can view the Spool generated by the called program(using sm37).
But this spool exists for a very less period in the system.Is it possible to specify a retention period,as 90 days in my case.?
Pls Help !!!
Answers will be rewarded.
Regards,
Rohan

hi Roahn,
You must set print parameters before the printing process starts.
When printing lists after creating them, the system uses the print format specified in the print parameters to split the completed list and fit it onto the print pages, truncating it if necessary.
When printing lists while creating them, the system uses the print format to actually format the list in the program.
Print parameters are set either interactively by the user or from within the program.
For each print process, the spool system needs a complete and consistent set of print parameters. In ABAP, the structure PRI_PARAMS (ABAP Dictionary) represent a set of print parameters.
When passing the print parameters interactively, the system displays a dialog box after starting the report, on which the user has to enter the most important print parameters.
It's shown below which input field of the Print List Output dialog window conform to which PRI_PARAMS component.
Input field----
Retention period
Component-------PEXPI
Meaning----
Number of days for which the system holds the spool request before deleting it. (Default value: 8).

JOB_CLOSE and Background Job Process a FM

HI Guys,
I have my code like this:
data: jobname like tbtcjob-jobname value
                             'TESTJOB'.
data: jobcount like tbtcjob-jobcount,
      host like msxxlist-host.
data: begin of starttime.
        include structure tbtcstrt.
data: end of starttime.
data: starttimeimmediate like btch0000-char1.
Job open
call function 'JOB_OPEN'
       exporting
            delanfrep        = ' '
            jobgroup         = ' '
            jobname          = jobname
            sdlstrtdt        = sy-datum
            sdlstrttm        = sy-uzeit
       importing
            jobcount         = jobcount
       exceptions
            cant_create_job = 01
            invalid_job_data = 02
            jobname_missing = 03.
if sy-subrc ne 0.
                                       "error processing
endif.
data: lv_weekday type WEEK_DAY.
CALL FUNCTION 'DATE_TO_DAY'
EXPORTING
    DATE          = sy-datum
IMPORTING
   WEEKDAY       = lv_weekday.
Close job
starttime-sdlstrtdt = sy-datum.
starttime-sdlstrttm = SY-UZEIT.
call function 'JOB_CLOSE'
       exporting
            event_id             = starttime-eventid
            event_param          = starttime-eventparm
            event_periodic       = starttime-periodic
            jobcount             = jobcount
            jobname              = jobname
            laststrtdt           = starttime-laststrtdt
            laststrttm           = starttime-laststrttm
            prddays              = 1
            prdhours             = 0
            prdmins              = 0
            prdmonths            = 0
            prdweeks             = 0
            sdlstrtdt            = starttime-sdlstrtdt
            sdlstrttm            = starttime-sdlstrttm
            strtimmed = 'X'                  "starttimeimmediate
           targetsystem         = host
       exceptions
            cant_start_immediate = 01
            invalid_startdate    = 02
            jobname_missing      = 03
            job_close_failed     = 04
            job_nosteps          = 05
            job_notex            = 06
            lock_failed          = 07
            others               = 99.
if sy-subrc eq 0.
                                       "error processing
endif.
This is the Program I want the Batch Job to Execute a BAPI Function Module in the Place of DATE_TO_DAY function module. Is it Possible ??????
And also I get an error at the JOB_CLOSE Function Module with SY-SUBRC = 5.
Can anyone know why this is happening and what should be done to overcome this.
Thanks & Regards,
YJR.

Hi Ravi,
The below code which has an EXPORT and IMPORT commands
The IMPORT does'nt work in Background.
Do I need to do anything else.
REPORT ZTEST_LM22.
DATA: LV_NAME(10) TYPE C.
LV_NAME = 'HELLO'.
export lv_name to memory id 'ZNAM'.
submit ztest_lm22_a.
REPORT ZTEST_LM22_A.
DATA: GV_JOBNAME TYPE BTCJOB VALUE 'TEST_UNPACK',
      GV_JOBCOUNT TYPE BTCJOBCNT.
data: lv_date type SYDATUM,
      lv_time type SYUZEIT.
lv_date = SY-datum.
lv_time = sy-uzeit.
CALL FUNCTION 'JOB_OPEN'
EXPORTING
    JOBNAME          = GV_JOBNAME
    SDLSTRTDT        = lv_date
    SDLSTRTTM        = lv_time
IMPORTING
    JOBCOUNT         = GV_JOBCOUNT
EXCEPTIONS
    CANT_CREATE_JOB = 1
    INVALID_JOB_DATA = 2
    JOBNAME_MISSING = 3
    OTHERS           = 4.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
          WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
SUBMIT ztest_lm22_b AND RETURN
                               VIA JOB GV_JOBNAME
                               NUMBER GV_JOBCOUNT.
CALL FUNCTION 'JOB_CLOSE'
EXPORTING
    JOBCOUNT             = GV_JOBCOUNT
    JOBNAME              = GV_JOBNAME
    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
    INVALID_TARGET       = 8
    OTHERS               = 9.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
          WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
REPORT ZTEST_LM22_B.
DATA: LV_NAME(10) TYPE C,
      GV_NAME(10) TYPE C.
IMPORT LV_NAME = GV_NAME FROM MEMORY ID 'ZNAM'.
WRITE: GV_NAME.
If you see in SM37 the Spool does'nt have this value.
Could you just run a quick test and see what else should be done...
Thanks & Regards,
YJR.

Background SNP processes

Similar Messages

Maybe you are looking for