Does Job scheduling functionality in EP 6.0 SP11 needs TREX installation??

Hi Friends
We're on EP 6.0 - SP11, we're implementing ESS on our portal environment, initially we planned for portal installation without the KM & TREX, now there is a requirement for our project due to which we need the job scheduler within EP 6.0 to schedule jobs, understand for that we need to install KM. Going through the "Installation of SAP EP on WAS 6.40" guide it looks like we need to install TREX as well if we want to install KM, can somebody confirm?, TREX will definitely consume much hardware resources & actually we don't need the search capabilities, all we need is the job scheduler. So appreciate if somebody can confirm if we need to install just the "Content Management & Colloboration" or we need to install TREX as well.
Thanks & Rgds,
Abhishek

Yes, the Scheduler service is part of CM and no TREX isn't required by the Scheduler service. TREX is mainly used as Search & Classification in KM.

Similar Messages

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

TIME FRAME IN JOB SCHEDULING

Hi all,
I am doing job scheduling in background.
But i am not able to do it twice a day, it means every 12 hours it should be done automatically.
Can anyone suggest me how to do with code.
Thanks in advance
Venkat

Hi venkat,
1. In that case ,
2. U can schedule TWO different jobs,
(with the same program name and variant)
3. DAILY
AT TWO DIFFERENT TIMES.
regards,
amit m.

Does different customized data in different clients affects job scheduling?

Hi All,
Does the job scheduling is client dependant or client independant.
We have 2 development test clients. Some customization settings are differenent in these two clients. Does this affect, if I run the job in one client, it will take the customization data in that client?
Thanks in advance,
Regds
Madhuri

job scheduling is client dependent....
Regards
Anbu B

Why does SCHDNEGACTION scheduler job have high CPU usage?

Hi,
In my embeded device(double CPU 1.5 G HZ ) SCHDNEGACTION scheduler job has 90% CPU usage. Why does the scheduler job have so high CPU usage? What is the job doing for?

Hi,
This job is not created by the scheduler. You will have to find out what component creates the job and what exactly it does to figure out why it is using high cpu and what would be the effects of disabling it (which would prevent it from running).
Hope this helps,
Ravi.

What is the spool, what is its role in background job scheduling

Hi,
I want to know what is meant by Spool request and spool number generated.
Tell about transaction SP01.
How it is linked to Background job scheduling.
thanks.
sam.

Hi,
Refer this link.
https://www.sdn.sap.com/irj/sdn/inf?rid=/library/uuid/7a5f4061-0a01-0010-c9bc-a4e4cb100438
About SP01.
Printing does not work in SAP. There is a printer definition for your local printer, but it does not work. Presuming that you use the program SAPLPD on your computer.
Boot your computer and start only the SAPLogon and the SAPLpd program.
Delete all of your old print jobs in the SAP system (Transaction SP01).Generate only one new print job.
Check that there is enough resource in your computer. Check the free memory (Win 3.1x) and the free disk space (The lists are temporarily saved on your disk).
Open the SAPLPD and read the print log in the window. The printer definition must correspond with the parameters shown here.
Check that the standard printer is on the same lpt (Win 3.1: Control panel, Printer) as defined for the printer (usually lpt1).
In Transaction SP01 read the protocol of your print job. Do not generate new print jobs! Wait till the SAP system changes the status of the print job.
If you can not find the print job in SP01 anymore, then the print job was successfully printed out. If it didn't come out on your printer and the SAPLpd didn't indicate an incoming print job, then the connection was realised with another PC. Then SAP printer definition you used, does not correspond with your computer.
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 u201CSend to SAP spooler Only for nowu201D
b.        Name u2013 abbreviated name to identify the job output
c.        Title u2013 free form description for the report output
d.        Authorization u2013 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 u2013 set to appropriate department/functional area name. This field can be used in
a search later.
f.        Retention period u2013 set to u201CDo not deleteu201D 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 jobu2019s 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 u201CParametersu201D button on a SAP Printer selection dialog, it
allows to specify all the parameters as described in p. 3 of
u201CScheduling background jobsu201D 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 u201CScheduling background jobsu201D section).
Access to reportu2019s 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 u201CFurther selection
criteriau2026u201D button (e.g. to bring u201CSpool request name (suffix 2)u201D 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 jobu2019s outputs)
a.        Spool request name (suffix 2) u2013 corresponds to a spool name in p. 3.b in
u201CScheduling background jobsu201D section above).
b.        Date created u2013 to find an output of a job that ran within a certain date range.
c.        Title u2013 corresponds to spool Title in p. 3.c in u201CScheduling background jobsu201D
section above).
d.        Department - corresponds to spool Department in p. 3.e in u201CScheduling
background jobsu201D 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 u201CPrint with changed attributedu201D button   to print the spool request
with the different attributes (e.g. changing the printer name).
c.        Click the u201CDisplay contentsu201D button   to preview the spool request contents. A
Print    and Download   functions are available from the preview mode.
Exporting the Contents of a Spool Request
Use
You want to export the contents of a spool request as a text file to the SAP GUI working directory or to a directory of your choice. The content of the spool request is downloaded as plain text without, for example, graphics, images, or specific fonts.
The following procedures are irrelevant for the PDF-based form printing integrated as of SAP Web Application Server 6.40, since the print data can be opened and stored as a PDF. See also Displaying and Printing PDF-Based Forms.
Procedure
Exporting to the SAP GUI Working Directory:
Choose Spool Request ® Forward® Export as Text.
The entire text is stored in your SAP GUI working directory in ASCII format.
A file of this type is named using the following pattern:
.txt
Example: ABC0000004327.txt
You require appropriate authorization for this function.
Exporting to a Directory of Your Choice:
With this method of exporting a spool request, the content of the spool request is first displayed and you then download the screen list as a text file to the directory of your choice.
       1.      Select the spool request to be exported and choose Display Contents.
       2.      In the case of SAPScript/Smart Forms documents, activate list display by choosing Goto.
       3.      Choose System ® List ® Save ® Local File.
       4.      Choose one of the available formats and confirm your choice.
       5.      Choose a directory and save the spool request.
By default, only the first 10 pages of a spool request are saved in a file. You can increase the number of pages to be saved by choosing Goto ® Display Requests ® Settings and making the desired entries in the Display Area group box.

NWA Job scheduler, how to change parameters?

Dear guys,
moving to AEX (java-only) the ABAP Stack is gone.
Regarding job scheduling there is no more transaction sm37, but Job scheduler within NWA to be used for scheduling jobs.
I configured a job for the predefined job definition AlertConsumerJob to get emails in case of alerts.
Doing this the questions arises how to change parameters once a job is scheduled e.g. add additional email receiver.
So far is seems you have to stop the configured job and define a NEW one from scratch by providing all job parameters. It seems not possible to adjust a job.
This is not very comfortable?
Is there an workaround / solution for this?
Best regards
Jochen

Hello Gaurav
thanks for your reply.
It's a pity, but shows that there is still some room of improvement regarding AEX functionality (java only)
Best regards
Jochen

Rwrun reports stop working after a period of time using a job scheduler

Hello, I am having a strange issue. We use either Control-M or Windows Task scheduler to run a VBS script that calls rwrun to generate multiple reports for multiple properties. Initially everything worked without issues then after about 2 months the VB Script running through Control-M started Failing. I could still run them from command line on the same server without Issues. So I set them up in Windows Task Scheduler and again they worked for about 3 weeks then started to Fail. Again I could still run the same scripts from command line on the server and have no issues. So we moved the scripts to another App server and went back to Control-M. This time after about 3 months the jobs started to fail. Moved them to Windows TS and again after about 1 week they started to fail. The TRACEALL shows nothing but I am getting this error in the hs_err_pidxxxx.log files that it creates. Does anyone know if some type of Temp location needs to be cleared or what my issue might be? Stumped at this point. Also point out the the servers were rebooted and no patches or modifcations where done to them before they start to fail. Thanks for any suggestions.
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x64CA84F2
Function=utqks2q+0x90
Library=e:\oracle\10gdevr2\bin\UTL.dll
Current Java thread:
     at oracle.reports.engine.EngineImpl.CRunReport(Native Method)
     at oracle.reports.engine.EngineImpl.run(EngineImpl.java:437)
     at oracle.reports.server.JobManager.runJobInEngine(JobManager.java:916)
     - locked <0x100a0040> (a oracle.reports.engine.EngineImpl)
     at oracle.reports.server.ExecAsynchJobThread.run(ExecAsynchJobThread.java:54)
Dynamic libraries:
0x00400000 - 0x00424000      e:\oracle\10gdevr2\bin\rwrun.exe
0x7D600000 - 0x7D6F0000      C:\WINDOWS\system32\ntdll.dll
0x7D4C0000 - 0x7D5F0000      C:\WINDOWS\syswow64\kernel32.dll
0x77BA0000 - 0x77BFA000      C:\WINDOWS\syswow64\MSVCRT.dll
0x7D930000 - 0x7DA00000      C:\WINDOWS\syswow64\USER32.dll
0x7D800000 - 0x7D890000      C:\WINDOWS\syswow64\GDI32.dll
0x004E0000 - 0x0057B000      C:\WINDOWS\syswow64\ADVAPI32.dll
0x7DA20000 - 0x7DB00000      C:\WINDOWS\syswow64\RPCRT4.dll
0x7D8D0000 - 0x7D920000      C:\WINDOWS\syswow64\Secur32.dll
0x66220000 - 0x6623C000      e:\oracle\10gdevr2\bin\nn.dll
0x64CE0000 - 0x64DBD000      e:\oracle\10gdevr2\bin\UIW.dll
0x64CA0000 - 0x64CB1000      e:\oracle\10gdevr2\bin\UTL.dll
0x64CD0000 - 0x64CD7000      e:\oracle\10gdevr2\bin\UTC.dll
0x60730000 - 0x607DC000      e:\oracle\10gdevr2\bin\oracore10.dll
0x608D0000 - 0x60963000      e:\oracle\10gdevr2\bin\oranls10.dll
0x62B40000 - 0x62B53000      e:\oracle\10gdevr2\bin\oraunls10.dll
0x60C40000 - 0x60C47000      e:\oracle\10gdevr2\bin\orauts.dll
0x71C00000 - 0x71C17000      C:\WINDOWS\system32\WS2_32.dll
0x71BF0000 - 0x71BF8000      C:\WINDOWS\system32\WS2HELP.dll
0x76AA0000 - 0x76ACD000      C:\WINDOWS\system32\WINMM.dll
0x77670000 - 0x777A9000      C:\WINDOWS\syswow64\ole32.dll
0x64CC0000 - 0x64CC9000      e:\oracle\10gdevr2\bin\UTJ.dll
0x64F10000 - 0x64F21000      e:\oracle\10gdevr2\bin\UIIM.dll
0x73070000 - 0x73097000      C:\WINDOWS\system32\WINSPOOL.DRV
0x77530000 - 0x775C7000      C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_5.82.3790.3959_x-ww_78FCF8D0\COMCTL32.dll
0x64ED0000 - 0x64EF6000      e:\oracle\10gdevr2\bin\UIOLE.dll
0x762B0000 - 0x762F9000      C:\WINDOWS\syswow64\comdlg32.dll
0x00580000 - 0x005D2000      C:\WINDOWS\syswow64\SHLWAPI.dll
0x7C8D0000 - 0x7D0CF000      C:\WINDOWS\syswow64\SHELL32.dll
0x663D0000 - 0x66414000      e:\oracle\10gdevr2\bin\CA.dll
0x66340000 - 0x6636A000      e:\oracle\10gdevr2\bin\mmc.dll
0x616B0000 - 0x61891000      e:\oracle\10gdevr2\bin\oraclient10.dll
0x62B60000 - 0x62B66000      e:\oracle\10gdevr2\bin\oravsn10.dll
0x60D30000 - 0x60DE8000      e:\oracle\10gdevr2\bin\oracommon10.dll
0x60300000 - 0x60720000      e:\oracle\10gdevr2\bin\orageneric10.dll
0x629C0000 - 0x629D2000      e:\oracle\10gdevr2\bin\orasnls10.dll
0x62B80000 - 0x62C86000      e:\oracle\10gdevr2\bin\oraxml10.dll
0x5C6C0000 - 0x5C6D1000      C:\WINDOWS\system32\MSVCIRT.dll
0x607E0000 - 0x608CC000      e:\oracle\10gdevr2\bin\oran10.dll
0x62000000 - 0x6202C000      e:\oracle\10gdevr2\bin\oranl10.dll
0x62030000 - 0x62042000      e:\oracle\10gdevr2\bin\oranldap10.dll
0x62090000 - 0x62184000      e:\oracle\10gdevr2\bin\orannzsbb10.dll
0x61E10000 - 0x61E52000      e:\oracle\10gdevr2\bin\oraldapclnt10.dll
0x61F30000 - 0x61F47000      e:\oracle\10gdevr2\bin\orancrypt10.dll
0x71BB0000 - 0x71BB9000      C:\WINDOWS\system32\WSOCK32.dll
0x76CF0000 - 0x76D0A000      C:\WINDOWS\system32\iphlpapi.dll
0x76B70000 - 0x76B7B000      C:\WINDOWS\system32\PSAPI.DLL
0x005E0000 - 0x0066B000      C:\WINDOWS\syswow64\OLEAUT32.dll
0x621A0000 - 0x621D7000      e:\oracle\10gdevr2\bin\oranro10.dll
0x621F0000 - 0x621FC000      e:\oracle\10gdevr2\bin\orantcp10.dll
0x61F70000 - 0x61F76000      e:\oracle\10gdevr2\bin\oranhost10.dll
0x61F20000 - 0x61F26000      e:\oracle\10gdevr2\bin\orancds10.dll
0x62210000 - 0x62216000      e:\oracle\10gdevr2\bin\orantns10.dll
0x60970000 - 0x60C31000      e:\oracle\10gdevr2\bin\orapls10.dll
0x62500000 - 0x62507000      e:\oracle\10gdevr2\bin\oraslax10.dll
0x627B0000 - 0x628B3000      e:\oracle\10gdevr2\bin\oraplp10.dll
0x618B0000 - 0x61905000      e:\oracle\10gdevr2\bin\orahasgen10.dll
0x622B0000 - 0x622E6000      e:\oracle\10gdevr2\bin\oraocr10.dll
0x622F0000 - 0x62315000      e:\oracle\10gdevr2\bin\oraocrb10.dll
0x71C40000 - 0x71C97000      C:\WINDOWS\syswow64\NETAPI32.dll
0x62A80000 - 0x62AF6000      e:\oracle\10gdevr2\bin\orasql10.dll
0x65050000 - 0x6576D000      e:\oracle\10gdevr2\bin\rw.dll
0x64AB0000 - 0x64AC4000      e:\oracle\10gdevr2\bin\ZRC.dll
0x66AC0000 - 0x66AC5000      e:\oracle\10gdevr2\bin\D2SC.dll
0x66810000 - 0x66A2B000      e:\oracle\10gdevr2\bin\DE.dll
0x627A0000 - 0x627AF000      e:\oracle\10gdevr2\bin\oraplc10.dll
0x64E30000 - 0x64E93000      e:\oracle\10gdevr2\bin\UIREM.dll
0x659A0000 - 0x659EE000      e:\oracle\10gdevr2\bin\ROS.dll
0x662F0000 - 0x66320000      e:\oracle\10gdevr2\bin\mmi.dll
0x64F50000 - 0x64F66000      e:\oracle\10gdevr2\bin\UICC.dll
0x662C0000 - 0x662DF000      e:\oracle\10gdevr2\bin\mms.dll
0x662A0000 - 0x662B0000      e:\oracle\10gdevr2\bin\mmv.dll
0x73AC0000 - 0x73AD8000      C:\WINDOWS\system32\AVIFIL32.dll
0x77B70000 - 0x77B84000      C:\WINDOWS\system32\MSACM32.dll
0x75FC0000 - 0x75FE2000      C:\WINDOWS\system32\MSVFW32.dll
0x66250000 - 0x6627E000      e:\oracle\10gdevr2\bin\mmw.dll
0x64FB0000 - 0x64FDA000      e:\oracle\10gdevr2\bin\UCOL.dll
0x665F0000 - 0x665F5000      e:\oracle\10gdevr2\bin\dfc.dll
0x66210000 - 0x66215000      e:\oracle\10gdevr2\bin\obs.dll
0x65010000 - 0x6503E000      e:\oracle\10gdevr2\bin\rws.dll
0x64AD0000 - 0x64C05000      e:\oracle\10gdevr2\bin\VGS.dll
0x7DBD0000 - 0x7DCD3000      C:\WINDOWS\WinSxS\WOW64_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.3959_x-ww_5FA17F4E\comctl32.dll
0x08000000 - 0x08139000      E:\oracle\10gdevr2\jdk\jre\bin\client\jvm.dll
0x10000000 - 0x10007000      E:\oracle\10gdevr2\jdk\jre\bin\hpi.dll
0x024E0000 - 0x024EE000      E:\oracle\10gdevr2\jdk\jre\bin\verify.dll
0x024F0000 - 0x02509000      E:\oracle\10gdevr2\jdk\jre\bin\java.dll
0x02510000 - 0x0251D000      E:\oracle\10gdevr2\jdk\jre\bin\zip.dll
0x05500000 - 0x0550F000      E:\oracle\10gdevr2\jdk\jre\bin\net.dll
0x7DB30000 - 0x7DBB0000      C:\WINDOWS\System32\mswsock.dll
0x76ED0000 - 0x76EFA000      C:\WINDOWS\system32\DNSAPI.dll
0x76F70000 - 0x76F77000      C:\WINDOWS\System32\winrnr.dll
0x76F10000 - 0x76F3E000      C:\WINDOWS\syswow64\WLDAP32.dll
0x76F80000 - 0x76F85000      C:\WINDOWS\system32\rasadhlp.dll
0x056C0000 - 0x056C6000      E:\oracle\10gdevr2\BIN\rwu.dll
0x5F270000 - 0x5F2CA000      C:\WINDOWS\system32\hnetcfg.dll
0x71AE0000 - 0x71AE8000      C:\WINDOWS\System32\wshtcpip.dll
0x06300000 - 0x06306000      E:\oracle\10gdevr2\jdk\jre\bin\ioser12.dll
0x76C10000 - 0x76C38000      C:\WINDOWS\syswow64\imagehlp.dll
0x6D580000 - 0x6D628000      C:\WINDOWS\syswow64\dbghelp.dll
0x77B90000 - 0x77B98000      C:\WINDOWS\syswow64\VERSION.dll
Heap at VM Abort:
Heap
def new generation total 576K, used 445K [0x10010000, 0x100b0000, 0x113c0000)
eden space 512K, 74% used [0x10010000, 0x1006f488, 0x10090000)
from space 64K, 100% used [0x100a0000, 0x100b0000, 0x100b0000)
to space 64K, 0% used [0x10090000, 0x10090000, 0x100a0000)
tenured generation total 2192K, used 1577K [0x113c0000, 0x115e4000, 0x20010000)
the space 2192K, 71% used [0x113c0000, 0x1154a448, 0x1154a600, 0x115e4000)
compacting perm gen total 4864K, used 4697K [0x20010000, 0x204d0000, 0x24010000)
the space 4864K, 96% used [0x20010000, 0x204a6670, 0x204a6800, 0x204d0000)
Local Time = Tue Dec 08 10:53:04 2009
Elapsed Time = 1
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) Client VM (1.4.2_06-b03 mixed mode)
#

I realize this is an old post, however I've had the exact same issue over the last week with the same UTL.dll showing in the hs_err_pidxxxx file.
Our VB6 app ran as a Windows 2003 scheduled task for almost two years before stopping all of a sudden. It ran fine when logged on, but would fail when we logged off. The task would run, but the program would fail. While we never did get the scheduled task working properly, I did find an alternate solution.
Instead of using rwrun.exe I updated the code in our app to use rwclient.exe. The command for rwrun and rwclient are very similar with rwclient requiring a server= setting.
Oracle Reports Components Overview

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

Job Schedule Sun thru Thurs only via TVARV using variant

Can someone tell me how to use TVARV to setup my job to run only on Sunday thru Thursday using my variant?

Hi,
Please check the below links.
http://help.sap.com/saphelp_nw04/helpdata/en/c0/9803aae58611d194cc00a0c94260a5/content.htm
Some sample code from seachsap site.
Have you ever wondered where your TVARV variables are being used in your batch jobs? How do you know if they change, and the impact it may have on your interfaces? The program below will provide a listing for you.
The program uses Job Count (job id) as the key versus Job Name as job names can be redundant. The code was written in R/3 v.4.6C, but should work in 3.x versions as well.
Code
PROGRAM: ZCAUS_EXTRACT_REPORT_VARIABLES
AUTHOR: DYLAN HACK
CREATE DATE: 10/09/2002
PURPOSE: This program was developed to extract all jobs based on the
         "Job Status" selection criteria and find the relevant TVARV
         variable entries. Then the report can be downloaded and
         sorted on selection variables. Ultimate purpose is to know
         what jobs are affected by the individual TVARV variables.
         If a job exists but does not have a corresponding entry/use
         of a TVARV variable, it will not get listed.
JOB STATUS LEGEND:
R: job step running.
Y: job step ready (eligible to run, waiting for a work process).
P: job step scheduled.
S: job step released (eligible to run when the start condition of the
   job is fulfilled).
A: job step aborted.
F: job step successfully finished.
Z: system upgrade in progress, only upgrade-related jobs are allowed
   to run. Jobs and job steps with this status are ignored by the
   scheduler.
X: unknown status detected.
REPORT ZCAUS_EXTRACT_REPORT_VARIABLES .
tables: tbtcp, tbtco.
data: var like RSVARVAR occurs 0 with header line,
      begin of report_tmp occurs 0,
        jobname   like tbtcp-jobname,
        jobcount like tbtcp-jobcount,
        stepcount type tbtcp-stepcount,
        progname type syrepid,
        variant   type syslset,
      end of report_tmp,
      report like report_tmp occurs 0 with header line,
      begin of listing occurs 0,
        jobname type tbtcp-jobname,
        jobcount like tbtcp-jobcount,
        stepcount type tbtcp-stepcount,
        progname type syrepid,
        variant   type syslset,
        variable type rsvarvar-variable,
      end of listing.
selection-screen begin of block a1 with frame title text-001.
selection-screen begin of block b1 with frame.
select-options: s_status for tbtco-status.
selection-screen end of block b1.
selection-screen begin of block b2 with frame.
selection-screen comment /5(75) com1.
selection-screen comment /5(75) com2.
selection-screen comment /5(75) com3.
selection-screen comment /5(75) com4.
selection-screen comment /5(75) com5.
selection-screen comment /5(75) com6.
selection-screen comment /5(75) com7.
selection-screen comment /5(75) com8.
selection-screen end of block b2.
selection-screen end of block a1.
initialization.
move:
'R: Job Running' to com1,
'Y: Job Ready (Eligible to run, waiting for process)' to com2,
'P: Job Scheduled' to com3,
'S: Job Released (Eligible to run when start condition is trigerred)'
to
com4,
'A: Job Aborted' to com5,
'F: Job Successfully Finished' to com6,
'Z: Upgrade in process, job being ignored' to com7,
'X: Unknown Status Detected' to com8.
start-of-selection.
get all jobs in released status
select jobcount from tbtco into report_tmp-jobcount
    where status in s_status.
    append report_tmp.
endselect.
get all related variants for those jobs that meet the where clause.
loop at report_tmp.
    select jobname jobcount stepcount progname variant
    into corresponding fields of report
    from tbtcp where jobcount = report_tmp-jobcount and
                     variant not like '&%' and
                     variant <> space.
    append report.
    endselect.
endloop.
sort and delete duplicates (if any)
sort report by jobname jobcount stepcount progname variant.
delete adjacent duplicates from report comparing all fields.
get TVARV selection variables
loop at report.
clear var. refresh var.
call FUNCTION 'RS_VARIANT_VARIABLES'
    EXPORTING
       PROGRAM = report-progname
       VARIANT = report-variant
    TABLES
     VAR = var
    EXCEPTIONS
        VARINT_NOT_EXISTENT.
move the data to a listing table
if var-variable <> space.
   loop at var.
    move: report-jobname   to listing-jobname,
          report-jobcount to listing-jobcount,
          report-stepcount to listing-stepcount,
          report-progname to listing-progname,
          report-variant   to listing-variant,
          var-variable     to listing-variable.
    append listing.
   endloop.
endif.
endloop.
sort and delete dups from listing
sort listing by jobname jobcount stepcount progname variant variable.
delete adjacent duplicates from listing comparing all fields.
data: count type i. loop at listing. count = count + 1. endloop.
write out the listing
write: 'Count', count. skip.
write: 2   'Job Name',
       36 'Job #',
       48 'Step',
       54 'Program name',
       95 'Variant',
       110 'Variable'.
loop at listing.
    write: / listing-jobname,
             listing-jobcount,
             listing-stepcount,
             listing-progname,
             listing-variant,
             listing-variable.
endloop.
Thanks,
Ramakrishna

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?

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

Background job scheduling for report

Hi can any one explain me how to do background job scheduling for report periodically for every 15 min.

Hi Rajesh thanks for your brief explanation.
but I am new to abap so I can't understand exactly will you please make it clear for the below program
REPORT zklj.
data: begin of itab occurs 0,
      partner type but000-partner,
      type     type but000-type,
      BU_SORT1 type but000-BU_SORT1,
      end of itab.
select partner type from but000 into table itab.
CALL FUNCTION 'GUI_DOWNLOAD'
EXPORTING
BIN_FILESIZE                    =
    FILENAME                        = 'd:\al1\ahaj.xls'
    FILETYPE                        = 'DAT'
APPEND                          = ' '
WRITE_FIELD_SEPARATOR           = ' '
HEADER                          = '00'
TRUNC_TRAILING_BLANKS           = ' '
WRITE_LF                        = 'X'
COL_SELECT                      = ' '
COL_SELECT_MASK                 = ' '
DAT_MODE                        = ' '
CONFIRM_OVERWRITE               = ' '
NO_AUTH_CHECK                   = ' '
CODEPAGE                        = '400'
IGNORE_CERR                     = ABAP_TRUE
REPLACEMENT                     = '#'
WRITE_BOM                       = ' '
TRUNC_TRAILING_BLANKS_EOL       = 'X'
WK1_N_FORMAT                    = ' '
WK1_N_SIZE                      = ' '
WK1_T_FORMAT                    = ' '
WK1_T_SIZE                      = ' '
WRITE_LF_AFTER_LAST_LINE        = ABAP_TRUE
SHOW_TRANSFER_STATUS            = ABAP_TRUE
IMPORTING
FILELENGTH                      =
TABLES
    DATA_TAB                        = itab.

Background job scheduling edit

Hi
i have a program which executing as a background job for every 3 minuts. but some times the job which is in process is taking a long time like up to 5 minuts and as per job scheduling after 3 minuts of first scheduled job, it is starting another same job. like that sometimes it is going upto 4 to 5 same job is processing.
Is there any solution like : only one of that job should be in the job execution process . but once the job is running the same job should not start. but if it is completed with in 3 minuts the job should be start as scheduled.
Thanks in advance

Hi,
I think there is a way in Job scheduling itself to define the next job only when the current one is complete (irrespective of how the execution takes place).
I recently recd help on this topic.. if you are triggering jobs from a program, you can add the foll code to make the second job (or further progm processing) to wait till the current job is over..
        WHILE v_fin IS INITIAL.
              CALL FUNCTION 'SHOW_JOBSTATE'
                EXPORTING
                  jobcount         = l_jobcount
                  jobname          = l_jobname
                IMPORTING
                  finished         = v_fin
                EXCEPTIONS
                  jobcount_missing = 1
                  jobname_missing = 2
                  job_notex        = 3
                  OTHERS           = 4.
              IF sy-subrc <> 0.
                ERROR_JOB = '1'.
                v_fin = 'X'.
              ENDIF.
         ENDWHILE.
Hope this helps.. Regards, Liz

Error in tabstrip control progtram while in Background job scheduling

Hi ABAPer's,
I need some help...I developed one tabstriip control program with 3 tabs. while excute it in foregroung it is executing nice..but while i am job scheduling the same program in background it was getting error's like .........
Control Framework: Fatal error - GUI cannot be reached
SET SCREEN not allowed in subscreens (screen: <Report Name> 0100)
so..if any body know the solution ...plz help me...
Thanks & Regards
Srinivas-SAP,

Hi,
please go through the functionality of tabstrips.
basically they are placed on tabstrips.
so they dont have their own ok codes and call screen and set screen ( to best of my knowledge )
can not be used.
if you are using set screen remove them.
even without using set screen if you are gettig the error, please let us know.
regards
Ramchander rao.K

Does Job scheduling functionality in EP 6.0 SP11 needs TREX installation??

Similar Messages

Maybe you are looking for