Hi All,

Can anyone suggest how to save spool by company code name automatically rather than i manually hard code the spool name for each step. I have a program which runs for 130+ company codes and each company code process the data and save a spool. Now we need to download those spools to a drive through redwood Cronacle. the first step in the chain triggers the SAP program which trigger the job in SAP and spools are generated for 130+ company codes.

Now i created second step to save the spool but its not saving all files.

The step1 gets spool in name like step1_spool1.text, step1_spool2.txt, step1_spool3.txt etc.

Now i tried to 'jgetfile -j -s "Step 1, job 1:step1_spool1.txt" -o "%destination%\spool1.txt" but now i have to create multiple lines like this and some time we will not have all company codes create spool because it will not have data to process.

Please advice how i can modify the above script to save all spools to a drive.

If its not easy to save spool with company code we are ok to save as is like step1_spool1.txt or spool1.txt.

Would be happy to share more information.

Thank you,

Arun

Hello,

Present steup:

We have connected 200+ ABAP systems( development & test systems) to SAP CPS system to run the normal 12 houskeeping jobs.

we have creatred the job chain to run these 12 ABAP jobs on all the 200+ ABAP systems.

now we have got a request to run the report(xyzzz) on ONLY in TEST ABAP systems.

is there any simply way to determine the DEV or TEST ABAP systems for the redwood at runtime.

i am thinking..     job1 : check for DEV or TEST

                           job2 : run the report xyzzz

logic, if the job1 output is TEST then run the Job2.

         if the job1 outpit is DEV then skip the Job2.

in ABAP system, i can find the DEV/test system by checking the RZ11 parameter "transport/systemtype"

Regards,

Shridhar Gowda

Hi All,

I am new to Redwood and here are the details of Redwood we are using.

Build M33.92-68971 and we dont have Alerting module.

We have a requirement that for some jobs if they are in post running/killing/cancelling/running for more than 15 minutes, we have to send email alert.

Here is what I have thought of:

1. Create a raise event for the job A to be notified and raise a custom job.

2. Custom job will also start running the moment job A is running.

3. Get the jobid from event and get the run time from the job table.

4. In Job A check if runtime > 15 minutes, then send a mail.

In step 4 how could I trigger a mail? I am not sure how could I do that

This custom job will be like a template so that it can used for more jobs.

I read through previous posts but could not really get the logic.

please advice and any help is highly appreciated.

Thanks,

Kasyap.

Hi Experts,

Need an advice how to setup a chain wherein one job has 2 dependencies. Pls refer to below. Appreciate any help. Thanks.

JobD should start if JobA and JobC is completed

Hi All,

In Redwood environment is it possible to find where an Event is used?

More exactly let's suppose to use the same Event in two Chains. Is there the possibility to display the name of the two Chains?

Thanks in advance for your kind support.

Regards,

    Giovanni

HI

I would to ask if anyone familiar with the below error which i encounter for one my job parameter. The way i setting this paramet is as below .

JCS-122021: Could not evaluate default value for parameter: Parameter waitEvents for job

JCS-122021: Could not evaluate default value for parameter: Parameter waitEvents for job 3365869

at com.redwood.scheduler.model.method.impl.JobParameterMethodImpl.evaluateDefaultValueInt(JobParameterMethodImpl.java:658)

at com.redwood.scheduler.model.method.impl.JobParameterMethodImpl.setInValueToDefault(JobParameterMethodImpl.java:141)

at com.redwood.scheduler.model.method.impl.JobParameterMethodImpl.prepareInt(JobParameterMethodImpl.java:93)

at com.redwood.scheduler.model.JobParameterImpl.prepareInt(JobParameterImpl.java:1129)

at com.redwood.scheduler.model.method.impl.JobMethodImpl.initializeParameters(JobMethodImpl.java:3384)

at com.redwood.scheduler.model.method.impl.JobMethodImpl.initializeNonStepJob(JobMethodImpl.java:3334)

at com.redwood.scheduler.model.method.impl.JobDefinitionMethodImpl.performPrepare(JobDefinitionMethodImpl.java:932)

at com.redwood.scheduler.model.method.impl.JobDefinitionMethodImpl.prepareInt(JobDefinitionMethodImpl.java:856)

at com.redwood.scheduler.model.JobDefinitionImpl.prepareInt(JobDefinitionImpl.java:2593)

at com.redwood.scheduler.model.method.impl.JobDefinitionMethodImpl.prepareInt(JobDefinitionMethodImpl.java:851)

at com.redwood.scheduler.model.method.impl.JobDefinitionMethodImpl.prepareInt(JobDefinitionMethodImpl.java:833)

at com.redwood.scheduler.model.JobDefinitionImpl.prepare(JobDefinitionImpl.java:2577)

at com.redwood.scheduler.ui.submit.MetaSubmitPage.submitJobDefinition(MetaSubmitPage.java:743)

at com.redwood.scheduler.ui.meta.actions.MetaJobDefinitionSubmitAction.performModelAction(MetaJobDefinitionSubmitAction.java:112)

at com.redwood.scheduler.ui.meta.MetaModelAction.performModelAction(MetaModelAction.java:207)

at com.redwood.scheduler.ui.meta.actions.MetaMultiAction$MultiAction.performModelAction(MetaMultiAction.java:92)

at com.redwood.scheduler.ui.model.impl.FormImpl.modelActions(FormImpl.java:748)

at com.redwood.scheduler.ui.model.impl.LifeCycle.run(LifeCycle.java:226)

at com.redwood.scheduler.ui.servlet.Servlet.handleRequest(Servlet.java:98)

at com.redwood.scheduler.ui.servlet.Servlet.doPost(Servlet.java:54)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)

at com.redwood.scheduler.module.impl.ModuleFilter.doFilter(ModuleFilter.java:157)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

at com.redwood.scheduler.security.filter.SecurityFilter.doFilter(SecurityFilter.java:708)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

at com.redwood.scheduler.servlet.RequestCharsetFilter.doFilter(RequestCharsetFilter.java:197)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)

at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)

at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)

at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

Caused by: com.redwood.scheduler.script.api.ScriptEngineEvaluationException: Invalid identifier: waitEvents.EVT_EDI_ITSD_MAIL.raiserComment

at com.redwood.scheduler.script.rel.impl.RELScript.evaluate(RELScript.java:67)

at com.redwood.scheduler.apiint.model.script.ScriptRunner.runScript(ScriptRunner.java:32)

at com.redwood.scheduler.apiint.model.script.ScriptRunner.runREL(ScriptRunner.java:41)

at com.redwood.scheduler.model.method.impl.JobParameterMethodImpl.evaluateDefaultValue(JobParameterMethodImpl.java:701)

at com.redwood.scheduler.model.method.impl.JobParameterMethodImpl.evaluateDefaultValueInt(JobParameterMethodImpl.java:654)

... 66 more

Caused by: com.redwood.scheduler.script.rel.parser.RELException: Invalid identifier: waitEvents.EVT_EDI_ITSD_MAIL.raiserComment

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:183)

at com.redwood.scheduler.script.rel.parser.ASTIdentifier.jjtAccept(ASTIdentifier.java:22)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visitChildren(RELEvaluateVisitor.java:136)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:395)

at com.redwood.scheduler.script.rel.parser.ASTPrimaryExpression.jjtAccept(ASTPrimaryExpression.java:14)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.evaluateUnary(RELEvaluateVisitor.java:246)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:353)

at com.redwood.scheduler.script.rel.parser.ASTUnaryExpression.jjtAccept(ASTUnaryExpression.java:14)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.evaluateBinary(RELEvaluateVisitor.java:196)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:346)

at com.redwood.scheduler.script.rel.parser.ASTMultiplicativeExpression.jjtAccept(ASTMultiplicativeExpression.java:14)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.evaluateBinary(RELEvaluateVisitor.java:196)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:339)

at com.redwood.scheduler.script.rel.parser.ASTAdditiveExpression.jjtAccept(ASTAdditiveExpression.java:14)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.evaluateBinary(RELEvaluateVisitor.java:196)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:332)

at com.redwood.scheduler.script.rel.parser.ASTRelationalExpression.jjtAccept(ASTRelationalExpression.java:14)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.evaluateBinary(RELEvaluateVisitor.java:196)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:325)

at com.redwood.scheduler.script.rel.parser.ASTEqualityExpression.jjtAccept(ASTEqualityExpression.java:14)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.evaluateLogical(RELEvaluateVisitor.java:209)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:318)

at com.redwood.scheduler.script.rel.parser.ASTLogicalANDExpression.jjtAccept(ASTLogicalANDExpression.java:14)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.evaluateLogical(RELEvaluateVisitor.java:209)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:311)

at com.redwood.scheduler.script.rel.parser.ASTLogicalORExpression.jjtAccept(ASTLogicalORExpression.java:14)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visitChildren(RELEvaluateVisitor.java:136)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:304)

at com.redwood.scheduler.script.rel.impl.RELScript.evaluate(RELScript.java:59)

... 70 more

Caused by: com.redwood.scheduler.api.scripting.NoSuchIdentifierException: No such identifier :: raiserComment :: Event is not raised

at com.redwood.scheduler.apiint.model.script.JobWaitEventScriptObjectImpl.getMember(JobWaitEventScriptObjectImpl.java:24)

at com.redwood.scheduler.apiint.model.script.JobWaitEventsScriptObjectImpl.getMember(JobWaitEventsScriptObjectImpl.java:12)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.valueOf(RELEvaluateVisitor.java:483)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:179)

Just to relate our customer experience with Redwood 6.0.2 and multi-step job chains. We have been trying for 6 months or more to perform very basic job scheduling functionality, that is, submit one job and have it followed by another job. The suggested way is to create a multi-step job chain. Unfortunately, this functionality appears to be problematic with Redwood 6.0.2. We started at sp6 and are now at sp10 and the problem persists. As a result, our current alternative is to use time scheduling which is much less efficient while we anxiously await an answer to our problem.

At this point, I am just wondering if there is anyone out there using 6.0.2 sp 10 (free version) submitting multi-step job chains with success to SAP?

Dear All,

I checked our Netweaver log and find following messages:

User XXXX does not have AccessSchedulerBusiness permission: java.security.AccessControlException: No authorization

Category: /Applications/Scheduler
Place: com.redwood.scheduler.security.impl.sap.ume.UMEUser
Application: redwood.com/scheduler-ear

Username | ACCESS.ERROR | null | | Permission=[(com.redwood.scheduler.security.permissions.SchedulerAccessPermission business)]

Category: /System/Security/Audit
Place: com.sap.security.core.util.SecurityAudit  
Application: redwood.com/scheduler-ear
(Username =my Username)

These are my userroles in SAP Netweaver UME:

  scheduler-user Einfacher Zugriff, sieht keine Objekte, Ist Basis für andere Rollen. UME-Datenbank

  scheduler-isolation-administrator Create/Edit/Delete Isolation Groups and add users to these UME-Datenbank

  scheduler-administrator Kann alle Aktionen im SAP CPS ausführen UME-Datenbank

and here my userroles in SAP CPS

Redwood System     Administrator     

Redwood System     BAG:9:F:Scheduler_Manager

Redwood System     scheduler administrator     

Redwood System     scheduler user     

Redwood System     BAG:1:F:Scheduler_Manager_Isolation     

Redwood System     scheduler isolation administrator     

Redwood System     scheduler_administrator

Redwood System     scheduler it user     

We use SAP CPS Build: M33.42-54458

Anyone an idea?

Kind regards

Marc

Hello,

I had recently upgraded SAP version from 7.01 to 7.3 sps 07 including M33.58 CPS component . ( Older CPS component was M28.44).

Upgrade happened successfully .. JavA engine come up fine.. all the component are upgraded fine.. Did not have any issues during upgrade.

-All the scheduler components are green in Applications area in Java NWA page.

Now when i launch scheduler page . Scheduler link opens with a message on screen as "" Startup Failure """ .

Default Trace file has following enteries:

#2.0 #2012 05 25 19:47:30:821#+00#Error#com.redwood.scheduler.module.helper.ForwardingModuleEventListener#

#XX-PART-REDWOOD#redwood.com/scheduler-ear#C00099589C28008C0000000000005A36#477974450000000004#redwood.com/scheduler-ear#com.redwood.scheduler.module.helper.ForwardingModuleEventListener#Guest#0##9AD15FADA6A111E1BDA500001C7D4FB2#76e11dd3a6a211e1aaf900001c7d4fb2#76e11dd3a6a211e1aaf900001c7d4fb2#0#Thread[HTTP Worker [@1380431624],5,Dedicated_Application_Thread]#Plain##

Error registering event listener JCS-107002: Component manager currently unavailable#

#2.0 #2012 05 25 19:47:30:822#+00#Error#com.redwood.scheduler.module.helper.ForwardingModuleEventListener#

Error registering event listener JCS-107002: Component manager currently unavailable#XX-PART-REDWOOD#redwood.com/scheduler-ear#C00099589C28008C0000000200005A36#477974450000000004#redwood.com/scheduler-ear#com.redwood.scheduler.module.helper.ForwardingModuleEventListener#Guest#0##9AD15FADA6A111E1BDA500001C7D4FB2#76e11dd3a6a211e1aaf900001c7d4fb2#76e11dd3a6a211e1aaf900001c7d4fb2#0#Thread[HTTP Worker [@1380431624],5,Dedicated_Application_Thread]#Plain##

Error registering event listener JCS-107002: Component manager currently unavailable#

#2.0 #2012 05 25 19:47:30:831#+00#Error#com.redwood.scheduler.module.helper.ForwardingModuleEventListener#

JCS-MULTI: Multiple errors occurred#XX-PART-REDWOOD#redwood.com/scheduler-ear#C00099589C28008C0000000400005A36#477974450000000004#redwood.com/scheduler-ear#com.redwood.scheduler.module.helper.ForwardingModuleEventListener#Guest#0##9AD15FADA6A111E1BDA500001C7D4FB2#76e11dd3a6a211e1aaf900001c7d4fb2#76e11dd3a6a211e1aaf900001c7d4fb2#0#Thread[HTTP Worker [@1380431624],5,Dedicated_Application_Thread]#Plain##

JCS-MULTI: Multiple errors occurred#

#2.0 #2012 05 25 19:47:30:831#+00#Error#com.redwood.scheduler.module.helper.ForwardingModuleEventListener#

#XX-PART-REDWOOD#redwood.com/scheduler-ear#C00099589C28008C0000000500005A36#477974450000000004#redwood.com/scheduler-ear#com.redwood.scheduler.module.helper.ForwardingModuleEventListener#Guest#0##9AD15FADA6A111E1BDA500001C7D4FB2#76e11dd3a6a211e1aaf900001c7d4fb2#76e11dd3a6a211e1aaf900001c7d4fb2#0#Thread[HTTP Worker [@1380431624],5,Dedicated_Application_Thread]#Plain##

Error registering event listener

[EXCEPTION]

JCS-107002: Component manager currently unavailable

    at com.redwood.scheduler.lifecycle.api.ComponentManagerLocator.lookupComponentManager(ComponentManagerLocator.java:58)

    at com.redwood.scheduler.module.helper.ForwardingModuleEventListener.registerEventListener(ForwardingModuleEventListener.java:55)

    at com.redwood.scheduler.module.impl.ModuleFilter.doFilter(ModuleFilter.java:123)

    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

    at com.redwood.scheduler.security.filter.SecurityFilter.doFilter(SecurityFilter.java:621)

    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

    at com.redwood.scheduler.servlet.RequestCharsetFilter.doFilter(RequestCharsetFilter.java:197)

    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)

    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)

    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)

    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)

    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)

    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)

    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)

    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)

    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

    at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)

    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)

    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)

    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)

    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)

    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)

    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

Caused by: JCS-112012: Cannot execute epoch initializer: com.redwood.scheduler.db.epoch.m30.M30Initializer

    at com.redwood.scheduler.db.DatabaseInitializer.initializeEpochs(DatabaseInitializer.java:670)

    at com.redwood.scheduler.db.DatabaseInitializer.initializeDatabase(DatabaseInitializer.java:381)

    at com.redwood.scheduler.db.DatabaseInitializer.start(DatabaseInitializer.java:210)

    at com.redwood.scheduler.lifecycle.impl.StartComponentVisitor.visit(StartComponentVisitor.java:34)

    at com.redwood.scheduler.lifecycle.impl.DefaultComponentLifecycleManager.visitAllComponents(DefaultComponentLifecycleManager.java:106)

    at com.redwood.scheduler.lifecycle.impl.DefaultComponentLifecycleManager.startComponents(DefaultComponentLifecycleManager.java:207)

    at com.redwood.scheduler.lifecycle.impl.DefaultComponentLifecycleManager.startComponents(DefaultComponentLifecycleManager.java:166)

    at com.redwood.scheduler.lifecycle.impl.DefaultStartup.start(DefaultStartup.java:146)

    at com.redwood.scheduler.lifecycle.impl.DefaultStartup$1.run(DefaultStartup.java:128)

    at java.lang.Thread.run(Thread.java:722)

Caused by: JCS-122035: Unable to persist: JCS-MULTI: Modification vetoed: JCS-XXXXX: Modification vetoed: Conflict propagating to job group, recurrence job attribute: Priority

    at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal(SchedulerSessionImpl.java:907)

    at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSessionImpl.java:848)

    at com.redwood.scheduler.db.DatabaseInitializer.initializeEpochs(DatabaseInitializer.java:665)

    ... 9 more

Caused by: com.redwood.scheduler.persistence.impl.MultipleCauseException: JCS-MULTI: Modification vetoed: JCS-XXXXX: Modification vetoed: Conflict propagating to job group, recurrence job attribute: Priority

    at com.redwood.scheduler.persistence.impl.PersistenceListenerContextImpl.throwException(PersistenceListenerContextImpl.java:194)

    at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeDirtyObjectListRetry(LowLevelPersistenceImpl.java:254)

    at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access$0(LowLevelPersistenceImpl.java:164)

    at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteDirtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103)

    at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkManager.execute(OuterPersistenceUnitOfWorkManager.java:38)

    at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeDirtyObjectList(LowLevelPersistenceImpl.java:160)

    at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistence.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90)

    at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal(SchedulerSessionImpl.java:886)

    ... 11 more

Caused by: com.redwood.scheduler.persistence.api.PersistenceException$ModelModificationVetoException: JCS-XXXXX: Modification vetoed: Conflict propagating to job group, recurrence job attribute: Priority

    at com.redwood.scheduler.model.method.impl.JobMethodImpl.copyRecurrenceFields(JobMethodImpl.java:621)

    at com.redwood.scheduler.model.method.impl.JobMethodImpl.preparePhaseHandler(JobMethodImpl.java:526)

    at com.redwood.scheduler.model.BaseSchedulerEntityImpl.preparePhaseHandler(BaseSchedulerEntityImpl.java:927)

    at com.redwood.scheduler.model.listeners.ConstraintCheckPrepareListener.modelModified(ConstraintCheckPrepareListener.java:48)

    at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.informListeners(LowLevelPersistenceImpl.java:970)

    at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeDirtyObjectListRetry(LowLevelPersistenceImpl.java:245)

    ... 17 more

I am not sure if any one has tried upgrade like this.. All i know is we can deploy CPS file/patchs/new versions  via JSPM. But what exactly takes place when we do SAP Version upgrade to 7.3 including CPS component upgrade????

There is no spcefic note yet released which i could find out..

Please help me out/??

Thanks

Best Regards

Deepak Shamra

Hi Guys,

anyone familir with the redwood CPS Dashboard?  i cannot find much documentation regarding the dashbaord on it full functionality, appreciate if anyone fimiliar with the Redwood Dashboard to share some thought/info on that. Thanks.

Regards,

Chris

Hi Folks,

We have a production CPS system with 5000+ jobs running. We have some performance issue related to Garbage Colelctor Values, below is the system technical information.

We are on Version 8.0

Build Id: M33.92-68971

Database Driver Version: Microsoft SQL Server JDBC Driver 3.0 3.0.1301.101

RAM = 32 GB

Cluster on Server0

Java version=1.6.0_51

OS=Windows Server 2008 R2

Memory info:

totalMemory: 4116054016

freeMemory : 1752108128

maxMemory  : 4116054016

-XX:PermSize=1024m

-Xmx4096m

-XX:MaxNewSize=1365m

-XX:MaxPermSize=1024m

-Xms4096m

-XX:NewSize=1365m

-XX:+UseConcMarkSweepGC

-XX:TargetSurvivorRatio=90

-verbose:gc

-XX:+DumpDetailedClassStatisticOnOutOfMemory

-XX:+PrintGCDetails

-XX:MaxErrorQueueLength=200

-XX:+PrintGCTimeStamps

-XX:+DisableExplicitGC

-XX:SoftRefLRUPolicyMSPerMB=1

-XX:-StringInternTableInPermGen

-XX:SurvivorRatio=6

-Xss2m

-XX:+HeapDumpOnOutOfMemoryError

-XX:HeapDumpPath=OOM.hprof

-XX:-TraceClassUnloading

Can you please suggest the recommended changes and values which are need to be adopted for fine tuning the garbage collection in our landscape from above information?

Hi :

           I am getting the following error(screen shot attached) "404 Not Found"  Error: Cannot define forward location.

Error occurs on our new version of Sap cps version M33.116-80989.

This error never occurred on the old sap cps version M33.85-65736

I get the redwood logon screen, but after entering the userid and password I get this error.

Can anyone help on this ?

Patrick Donnelly

patrick.donnelly@agr.gc.ca

Hi All,

I got stuck in writing query to fetch 100 records at a time.

Here is what I have tried.

select JobDefinition.* from JobDefinition LIMIT 100

select Top 100 JobDefinition.* from JobDefinition

select JobDefinition.* from JobDefinition FETCH FIRST 100 ROWS ONLY

All the above queries ended with sql exception.

Any pointers are really helpful.

Hello,

I wonder if there is a possibility to mass change the user entered in the steps overview of a released job.

I know that in the Table TBTCS the Jobowner is saved and in TBTCP I can view the user entered in the steps overview but only for jobs which have already been executed, does anyone of you know which table keeps the steps user for a released job?

Kind regards

Florian Wittmann

Hi everyone,

Our SAP production system runs on two application servers serverA and serverB, and they both are added in the logon group SVRGRP.

Now the sap system has a fully qualified domain name - sapprdecc.domain.com and i am able to connect using the string:

ASHOST=sapprdecc.domain.com SYSNR=00 TRACE=0

I understand that we can connect to the msgserver as well. I have tried the following connection strings but none of them work:

MSHOST=sapprdecc.domain.com R3NAME=XX1 GROUP=SVRGRP

MSHOST=xxx.xxx.xxx.xxx R3NAME=XX1 GROUP=SVRGRP

So, i am thinking of going with the ASHOST string(since this works). I have two questions:

1. Can someone please let me know whether i should go for the MSHOST string for my scenario or ASHOST string is enough?
2. Why did my MSHOST string fail, what i am doing wrong?

PS: I am able to open the GUI with the command SAPGUI xxx.xxx.xxx.xxx 00 (so the ipaddress i am using is correct)

Hello,

I'm new to CPS and have a job chain that needs to wait for jobs in SAP to finish. On step in the job chain runs a job in SAP that spawns up to 50 instances of a program. I'm looking for a way to determine when all child jobs finish before continuing to the next step in the CPS job chain. The job that launches all the programs in SAP completes in just seconds and CPS moves to the next step. I'm using a time delay in the job chain to wait a set amount of time but looking for a way to monitor SAP within CPS without using the delay. Any ideas?

Hi All,

Can you please clarify the below query.

How can I force all SAP jobs into 'Completed' which are running on ECC process server for the return codes '0-4' for  whatever is the message class, message number and message type.

Thank you in advance.

Regards,
Ramana

I want to make a connection to a ORACLE DB and use a ProcessDefinition with Type SQLPLUS.

This Process Definition has following Parameters:

JCS_REMOTE_USER

JCS_REMOTE_PASSWORD

JCS_REMOTE_ENDPOINT

But unfortunately I get allways following error message:

SP2-0306: Invalid option. Usage: CONN[ECT] [{logon|/|proxy} [AS {SYSDBA|SYSOPER|SYSASM}] [edition=value]] where ::= [/][@]       ::= [][/][@] SP2-0306: Invalid option. Usage: CONN[ECT] [{logon|/|proxy} [AS {SYSDBA|SYSOPER|SYSASM}] [edition=value]] where ::= [/][@]       ::= [][/][@] SP2-0306: Invalid option. Usage: CONN[ECT] [{logon|/|proxy} [AS {SYSDBA|SYSOPER|SYSASM}] [edition=value]] where ::= [/][@]       ::= [][/][@] SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus

This script is running with Ran As User

This user has set the ORACLE Environment and this one can also be seen in the script with command env.

In the other case I will get a different error message.

I was also trying to use Remote Run As User without the parameter but with the same result.

On OS level the user can connect to the database.

Any idea what is wrong in my situation?

Hi,

In the previous version of CPS, we were using the following in the Alert Source Email to indicate the system name and system type to the recipient of the email.  The below code would result in something like "CPS OQ9 (Non-Prod)" being placed in the email.  The variables THIS.SYSTEM.NAME and THIS.SYSTEM.TYPE are defined in the System_Variables table.  This worked great in the prior version of CPS.

CPS [?=Variable.getString('THIS.SYSTEM.NAME')?] ([?=Variable.getString('THIS.SYSTEM.TYPE')?])

In BPA 9, the above code still allows the email to send, but we get this in the email:

CPS ERROR:20160425150411CST/5b3d0dc5 (ERROR:20160425150411CST/5b3d0dc5)

Any ideas?  Did the format of the code change?  The Administrator Guide seems to indicate that the above should still work...

Thanks,

Dallas

I want to have CPS event monitor different folders depending on which system the job in.

There is no way to use parameters like the normal batch jobs and CMD jobs.

So wondering how to achieve a dynamic move directory setup for events?