Hi

If I set a spool recipient list in a Redwood job chain step, as either a valid username or distribution list, and submit the job, the intended recipient does NOT recieve anything in their SAP Office/SBWP inbox. Looking at the submitted job in SM37 I can see a successuful spool was created and the spool properties do actually show the recipient I specified - so Redwood DOES appear to be passing across the recipient to the job/the spool - but nothing is sent.

If I specify a job directly in SAP via Sm36 with this recipient or distribution list - or even copy the job that Redwood scheduled and reschedule/release via SM36 - then it DOES work.

Is this a problem in Redwood; do I need to define something somewhere else? We are on the latest patch, M26.12.

Thanks

Ross

L.S.,

I've installed CPS (M28.9-33972) on our test Solution Manager (dual stack) 7.0 SP20. I want to connect the abap stack of the Solution Manager to CPS. When I fill-out the form and save it, I get the error: An isolated SAP system can't be created in the GLOBAL partition.

So I created a new Isolation Group and partion. added my userid to the security of the newly created partion, logged off, logged on... now I cannot create the system in the created group as it is not active... How do I logon to a different group in order to connect to an SAP instance?

Regards,

Marcel Boschma

We are running v8 milestone m33.19 and when trying to import the SAP job EU_PUT via SAP_ImportCcmsJobs we get the following error which I can only assume that certain keywords are reserved but as we do not have controll over this I was wondering if anyone else has came accross it :-

Generating job definition EU_PUT for SAP job EU_PUT/00105300

Could not create job definition EU_PUT for SAP job EU_PUT/00105300

com.redwood.scheduler.api.exception.SchedulerAPIPersistenceException: JCS-122007: SAP_AbapRunPrint_REC_TYPE is not a valid name for object type Constraint Definition: Prefixes 'System_', 'SAP_' and 'ProcessMonitor_' are reserved for system objects

com.redwood.scheduler.persistence.api.PersistenceException$ModelModificationVetoException: JCS-XXXXX: Modification vetoed: Unexpected exception during listener execution

com.redwood.scheduler.api.exception.InvalidObjectNameException: JCS-122007: SAP_AbapRunPrint_REC_TYPE is not a valid name for object type Constraint Definition: Prefixes 'System_', 'SAP_' and 'ProcessMonitor_' are reserved for system objects

JCS-122035: Unable to persist: JCS-XXXXX: Modification vetoed: Unexpected exception during listener execution

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

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

     at com.redwood.scheduler.connector.sap.rfc.service.components.util.UserUnitOfWorkManager.perform(UserUnitOfWorkManager.java:141)

     at com.redwood.scheduler.connector.sap.rfc.service.components.util.UserUnitOfWorkManager.perform(UserUnitOfWorkManager.java:103)

     at com.redwood.scheduler.connector.sap.rfc.command.impl.GenerateCcmsJobDefinitionCommand.execute(GenerateCcmsJobDefinitionCommand.java:205)

     at com.redwood.scheduler.connector.sap.rfc.command.AbstractXbpCommand.doExecute(AbstractXbpCommand.java:85)

     at com.redwood.scheduler.connector.sap.rfc.command.AbstractCommand.execute(AbstractCommand.java:56)

     at com.redwood.scheduler.connector.sap.rfc.service.SapJobWork.doWork(SapJobWork.java:99)

     at com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:74)

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

Caused by: com.redwood.scheduler.persistence.api.PersistenceException$ModelModificationVetoException: JCS-XXXXX: Modification vetoed: Unexpected exception during listener execution

     at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.throwUnexpectedExceptionDuringListenerExecution(LowLevelPersistenceConfigurationImpl.java:605)

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

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

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

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

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

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

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

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

     ... 9 more

Caused by: JCS-122007: SAP_AbapRunPrint_REC_TYPE is not a valid name for object type Constraint Definition: @locale2@:(com.redwood.scheduler.exception.Help.InvalidObjectName.BannedPrefix)

     at com.redwood.scheduler.model.method.impl.NamedRootObjectMethodImpl.checkName(NamedRootObjectMethodImpl.java:89)

     at com.redwood.scheduler.model.method.impl.NamedRootObjectMethodImpl.checkNameInt(NamedRootObjectMethodImpl.java:66)

     at com.redwood.scheduler.model.NamedRootObjectImpl.checkNameInt(NamedRootObjectImpl.java:216)

     at com.redwood.scheduler.model.listeners.ModelInterfacesPrepareListener.modelModified(ModelInterfacesPrepareListener.java:111)

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

     ... 16 more

When we want to start a process chain via SAP_BW_ProcessChainRun we get the following error log:

-

-

Failed to start process chain /NSN/C_DSP_TR_GLOBAL_II. No logid was returned by the BW-SCH API.

com.redwood.scheduler.connector.sap.rfc.connection.exception.SapBapiException: BAPI exception while calling RSPC_API_CHAIN_START: E RSPC 022 Processes with Error Error occured when starting process chain

BAPI exception while calling RSPC_API_CHAIN_START: E RSPC 022 Processes with Error Error occured when starting process chain

     at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.ClientConnectionImpl.checkBapiReturnCode(ClientConnectionImpl.java:789)

     at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.ClientConnectionImpl.handleRscpApiErrors(ClientConnectionImpl.java:808)

     at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.ClientConnectionImpl.call(ClientConnectionImpl.java:505)

     at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection$4.doPerform(AbstractRfcConnection.java:296)

     at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall.perform(RemoteFunctionCall.java:120)

     at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection.perform(AbstractRfcConnection.java:461)

     at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection.execute(AbstractRfcConnection.java:289)

     at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.SapFunctionModuleWrapper.execute(SapFunctionModuleWrapper.java:200)

     at com.redwood.scheduler.connector.sap.rfc.jco.AbstractSapFunctionModule.execute(AbstractSapFunctionModule.java:109)

     at com.redwood.scheduler.connector.sap.rfc.command.impl.BwProcessChainCommand.execute(BwProcessChainCommand.java:98)

     at com.redwood.scheduler.connector.sap.rfc.command.AbstractXbpCommand.doExecute(AbstractXbpCommand.java:86)

     at com.redwood.scheduler.connector.sap.rfc.command.AbstractCommand.execute(AbstractCommand.java:56)

     at com.redwood.scheduler.connector.sap.rfc.service.operation.RunJobOperation.doWork(RunJobOperation.java:103)

     at com.redwood.scheduler.connector.sap.rfc.service.SapJobWork.doWork(SapJobWork.java:38)

     at com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:74)

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

-

-

What could be the reason?

Thanks

Br

Günter

CPS File Events via Platform Agent : file check issue

We are raising events using the file event option with integrated OS Platform Agent.

Our OS platform is RHEL 6u2.

The file events work, EXCEPT when you select the option to "Check if files is in use".

In this case we were getting an Operator Message saying:

"Could not check whether the file is in user: lsof "$(Filename)""

Some "Remote Inofrmation:.... Remote OS User: redwood"

So we figured that the redwood user simply didn't "know" about lsof.

However here are some tests that have led us to log a ticket about this:

1. if we sesu to redwood on the OS layer and run "lsof" it's fine. If you run "which lsof" you can see it knows that it's fuill path is /usr/sbin/lsof.

2. We created a new UNIX job.

  2a. 1st version gave a similar error: lsof: command not found

  2b. 2nd version we included the full path e.g. /usr/sbin/lsof <full path for filename>

But the second version still gave an error - but with no log and no operator message generated.

Has anyone seen this? Perhaps this could be a bug? Specific to Linux or not.

Hi Everyone,

There is a program which runs in SAP triggered by Cronacle. Program generates two spools in SAP, one is for a team to send the PDF file and the other is for the report spool. Spool is not getting returned to Cronacle. Spool flag is set to yes in the parameters. Is there any configuration which can be made in Cronacle or SAP so that the report spool can be returned to Cronacle. For all other jobs spool is visible in Cronacle.

Thanks in advance for the help.

Regards,

Ramana

Hi All,

Recently i came across an issue where job failed with the error - " Failed to create the job in the SAP system".

Below is the log :

Failed to create the job in the SAP system
com.redwood.scheduler.api.exception.SchedulerAPIPersistenceException: JCS-XXXXX: Modification vetoed: Unexpected exception during listener execution
com.redwood.scheduler.persistence.api.PersistenceException$ModelModificationVetoException: JCS-XXXXX: Modification vetoed: Unexpected exception during listener execution
java.lang.NullPointerException: null

JCS-122035: Unable to persist: JCS-XXXXX: Modification vetoed: Unexpected exception during listener execution.

Please let me know what could be the cause for this issue and is there any fix.

thanks in advance.

Regards,

KN

Hi Guys,

I need to create some time windows based on our company's monthly cycles. Here is an example:

Monthly Cycles from August to December 2013 are:

Aug 24 - Sept 27

Sept 28 - Oct 25

Oct 26 - Nov 22

Nov 23 - Dec 27

Now based on the above monthly cycles, I want to create a time window that is open on 1st Monday of the monthly cycle only. So based on the above date ranges, the time window should be open on below dates only:

Aug 26

Sep 30

Oct 28

Nov 25

Dec 30

Can some please suggest how to come up with the above time window? Ideally we would like to keep one time window that is just the monthly cycle and then all other time windows will be based off of that, like 1st Monday or 3rd Tuesday or 2nd Wednesday of the  monthly cycle....Please advise. Thanks.

Hello,

is it possible with CPS to grant a user access rights, so he can only restart a failed process chain?

In the full version it is possible, but it looks like in CPS there are limits.

I am looking for the role/privileges documentation ...

Thanks for your help.

Best regards

Carlos Behlau

Hello,

The called process chains in SAP BW were finished but the CPS job, which started the BW process chains, stays in status Waiting.

I tried the kill the job, but now it stays in status Killing (not killed), it also has set a lock which causes that a new job chain with the same lock cannot be started because it comes in the status lock wait.

Also the removal of the lock in the job chain definition isn't the solution because that gives an error in SAP BW:

Chain run XXXXXXXX to be terminated as soon as possible due to user request

How can we set the status for this job from Killing to Killed and how can remove the set lock by this job?

Thanks in advance.

Hello,

I select jobs from database and want to display their ExpectedRunTime in a script.

it = jcsSession.executeObjectQuery("select j.* from Job j where j.Description like '%Test%' order by j.Description asc");

 

while(it.hasNext()) {

      Job j = (Job) it.next();

      jcsOut.println("Job: " + j.getDescription());

      jcsOut.println("Time: " + j.ForecastJob().getExpectedRunTime());

}

But it doesn't work. The jobs will be listed if I remark the last line.

How can I display the ExpectedRunTime of the jobs?

Best regards,

Dana Ullrich

Hello,

Due to a change of our HOSTNAME of process server (SAP), jobs still in status "Scheduled" and never pass to status "Running".

I did installation of SAP CPS Redwood on the new server and run redwood command line :

RS> startup <scheduler> local

In Redwood Explorer, the job “START RFC agent for instance” is in status “running”.

When I submit SAP Jobs they put in status “Scheduled” and don’t go to status running. My jobs still in status "scheduled"
with operator message : "RFC Agent still in starting phase, job is delayed 1 minute"

Version of SAP CPS Redwood :  7.0.4.1 SP1

When I execute on the process server (Unix) the command line

$ ./redwood.lsb status

Scheduler SYSJCS.CPSD11 has status: RUNNING

Any Idea for this issue ?

Thanks !

Hi, i am new on this.

I need to get a list of the Basis jobs running in our instances (PBI, PR3, DBI, DRP, etc).

I know how to get that list.

Also, i need to look for the meaning of those Basis jobs, i need to know what each one of them do.

Where can i find that information?

For example, this is one of the jobs: RSAL_BATCH_TOOL_STARTUPDISP, i need to know what this job doese on the system.

How could i find the meaning of each job? i mean, what it is working for on the system.

Thank you so much.

Daniela.

Hi everyone,

I have imported the ABAP program and variant definition from SAP ECC to Redwood.

The technical name of the variable is P_GJAHR and so i have added a parameter PAR_P_GJAHR and given the value =Time.formatNow('yyyy').

When i submit the job, i set the Create Temporary Variant? to Yes and also i can see that value of the parameter is correct (2012). But i get the following error as soon as i submit.

Failed to create the job in the SAP system

com.redwood.scheduler.connector.sap.rfc.connection.exception.SapRfcSystemFailureException:      More than one radio button active                                  

com.redwood.scheduler.connector.sap.rfc.connection.exception.SapRfcException:      More than one radio button active                                  

com.sap.mw.jco.JCO$Exception:      More than one radio button active                                  

Can someone please help me solve this issue?

We are running v8 milestone m33.19 and when trying to import the SAP job EU_PUT via SAP_ImportCcmsJobs we get the following error which I can only assume that certain keywords are reserved but as we do not have controll over this I was wondering if anyone else has came accross it :-

Generating job definition EU_PUT for SAP job EU_PUT/00105300

Could not create job definition EU_PUT for SAP job EU_PUT/00105300

com.redwood.scheduler.api.exception.SchedulerAPIPersistenceException: JCS-122007: SAP_AbapRunPrint_REC_TYPE is not a valid name for object type Constraint Definition: Prefixes 'System_', 'SAP_' and 'ProcessMonitor_' are reserved for system objects

com.redwood.scheduler.persistence.api.PersistenceException$ModelModificationVetoException: JCS-XXXXX: Modification vetoed: Unexpected exception during listener execution

com.redwood.scheduler.api.exception.InvalidObjectNameException: JCS-122007: SAP_AbapRunPrint_REC_TYPE is not a valid name for object type Constraint Definition: Prefixes 'System_', 'SAP_' and 'ProcessMonitor_' are reserved for system objects

JCS-122035: Unable to persist: JCS-XXXXX: Modification vetoed: Unexpected exception during listener execution

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

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

     at com.redwood.scheduler.connector.sap.rfc.service.components.util.UserUnitOfWorkManager.perform(UserUnitOfWorkManager.java:141)

     at com.redwood.scheduler.connector.sap.rfc.service.components.util.UserUnitOfWorkManager.perform(UserUnitOfWorkManager.java:103)

     at com.redwood.scheduler.connector.sap.rfc.command.impl.GenerateCcmsJobDefinitionCommand.execute(GenerateCcmsJobDefinitionCommand.java:205)

     at com.redwood.scheduler.connector.sap.rfc.command.AbstractXbpCommand.doExecute(AbstractXbpCommand.java:85)

     at com.redwood.scheduler.connector.sap.rfc.command.AbstractCommand.execute(AbstractCommand.java:56)

     at com.redwood.scheduler.connector.sap.rfc.service.SapJobWork.doWork(SapJobWork.java:99)

     at com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:74)

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

Caused by: com.redwood.scheduler.persistence.api.PersistenceException$ModelModificationVetoException: JCS-XXXXX: Modification vetoed: Unexpected exception during listener execution

     at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.throwUnexpectedExceptionDuringListenerExecution(LowLevelPersistenceConfigurationImpl.java:605)

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

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

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

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

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

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

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

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

     ... 9 more

Caused by: JCS-122007: SAP_AbapRunPrint_REC_TYPE is not a valid name for object type Constraint Definition: @locale2@:(com.redwood.scheduler.exception.Help.InvalidObjectName.BannedPrefix)

     at com.redwood.scheduler.model.method.impl.NamedRootObjectMethodImpl.checkName(NamedRootObjectMethodImpl.java:89)

     at com.redwood.scheduler.model.method.impl.NamedRootObjectMethodImpl.checkNameInt(NamedRootObjectMethodImpl.java:66)

     at com.redwood.scheduler.model.NamedRootObjectImpl.checkNameInt(NamedRootObjectImpl.java:216)

     at com.redwood.scheduler.model.listeners.ModelInterfacesPrepareListener.modelModified(ModelInterfacesPrepareListener.java:111)

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

     ... 16 more

Redwood recommend 1 Java server node for running CPS on

However you lose the extra mitigation for failure of a node that you'd get by having 2 (or more)

Has anyone got more than 1 server node on NetWeaver AS Java running SAP CPS on top?

NB Looking at recent documents I wonder if recommendations have changed to support multi-node installations more?

Hi All,

I am trying to create report on runtime of a jobchain for last 30 days but I also need the run time of each job in the job chain.

How should I proceed to do that?

Thanks,

Tanmay Suri

Hello All,

I am trying to schedule process chains of SAP BI (BW).

A process chain named "CDE_TEST" has been created in BI in order to test the scheduling via Cronacle.

So we have done the following actions:

  - submit successfully the RFC Agent on BI system

  - submit successfully (?) the RSI_IMPORT_BW_CHAINS script: it had a completed status with a small output file (that contains only one line: "CDE_TEST                 /CDE_TEST")

  - submit the the RSI_IMPORT_BW_CHAINS_DEFINITION script: it submitted by itself 2 others jobs: the first one was successful (it was the same as the one launched by RSI_IMPORT_BW_CHAINS) but not the second which shows either errors on RFC ("erreur RFCÂ : FAILED" and "Message RFCÂ : FAILED") or systems ("erreur RFCÂ : RFC_ERROR_SYSTEM_FAILURE" and 'Message RFCÂ : Function module "/SCJS/XBP_VERSIONS_GET_INT" not found.")

  - submit the RSI_RUN_BW_CHAIN script, with default values, to run the "CDE_TEST" process chain. Then I get differents errors :

         => "erreur RFCÂ : RFC_ERROR_SYSTEM_FAILURE" and "Message RFCÂ : Message type 1 is unknown."

         => "erreur RFCÂ : FAILED" and "Message RFCÂ : FAILED"

         => "Exception : SYSTEM_FAILURE"

So I would like to know the pre requisites for these kind of functionnality. I mean, for example, it is mandatory to load the transport files in the BI systems to make this works ? or does this transport files have any effects on process chains functionnalities ?

Thanks you in advance for your help.

Regards,

Yi Jiang

Hi,

I am new to SAP, Redwood and this forum so if this topic has been covered earlier I apologize.

My problem is that I have a SAP job with a VARIANT in SAP that I want to have working in Redwood.

I import the job with RSI_IMPORT_ABAP_PROGRAMS and the variant with RSI_IMPORT_VARIANTS. At this

stage I am relatively sure I was able to run the job once by submit RSI_ABAP_RUN with variant.

I use the RSI_GENERATE_VARIANT to generate the VAREDIT script to be able to change the parameters

for the ABAP job. Modify the parameters, run the VAREDIT script.

When I now try to run the RSI_ABAP_RUN with the variant I enters values for instance, client, jobclass,

ABAP program (from dropdown list), ABAP variant (from dropdown list), Job name (get filled automatically)

then tries to goto "next" or "submit" I get a popup window.

-

Error

Enter a valid value for the ABAP_VARIANT_NAME.

-

I am still able to run the job in SAP with VARIANT and in background.

Does anyone have any ideas?

Hello to all,

Do you guys know how to change the default directory where the output files and logs of CPS are store? Is this possible?

Thanks in advance,

Sabin L