Skip to Content
author's profile photo Former Member
Former Member

Spool recipient list not working in Redwood CPS - nothing received in SBWP

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

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Mar 18, 2009 at 12:34 PM

    Ross ,

    Check the parameter 'JOBRECIPIETNTYPE' for the script and see the default value for it . Is it is 'B' then remove it and make it blank .

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Frank

      Brilliant! You are a star. I did previously search OSS but that note was not there then... looks like it's pretty new - I see it's been valid since 21st April.

      Interestingly enough I have got a message raised with SAP, and they still haven't responded.

      Right - we'll get CPS patched then!! Fingers crossed.

      Many thanks for your help...

      Ross

  • author's profile photo Former Member
    Former Member
    Posted on Mar 15, 2009 at 09:05 PM

    HI Ross,

    Especially the fact that copying the job created through CPS results in a job in SAP which output does get sent is strange, because that means the values seem to be OK. Do you see any messages in the systemlog around the time when the original CPS job finished ? Maybe security related, because if you copy it, the owner of the job probably changes ?

    Regards,

    Anton.

    Edited by: Anton Goselink on Mar 15, 2009 10:05 PM

    - added security question

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Anton

      Thanks but doesn't seem to be down to security. User for CPS (REDWOOD) has SAP_ALL and SAP_NEW, and to double check I rescheduled the job manually in SM36 as REDWOOD and it ran ok and sent the spool to the intended recipient.

      Nothing in the system log either, no errors in Redwood CPS operator messages.

      One thing we did notice was that when we enter the spool recipient in Redwood it is displayed in red, as if it doesn't recognise it... however, it does this for the ABAP job name too - and this is a standard SAP reorg job, it does find it and run it successful.... but still the spool is not sent to the recipient.

      Redwood CPS has also now started producing an 'error' status on my job chain with no explanation of why; nothing in the operator logs, nothing has changed - worked previously - seems intermittent. Also, if it fails once, the submit frame seems to give up - i.e. the job next day doesn't run either!! Redwood CPS is making me loose my hair (if I had any!) and I've given up for now - gone back to scheduling through SM36!!!

      Regards

      Ross

  • author's profile photo Former Member
    Former Member
    Posted on May 27, 2009 at 12:12 PM

    The answer was supposedly to apply the patch M26.17 - which we have now done. Unfortunately, the spool recipient still does not work! It behaves exactly the same as before.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Ok, I now have spool recipient working!

      The problem was that I was using the job definition u201CSAP_AbapRunu201D. Using just u201CSAP_AbapRunu201D and completing the spool recipient field there will NOT work.

      What I needed to do was use job definition "SAP_AbapRunPrintExt".

      You then ignore the u2018Spool list recipientu2019 under the Print Parameters section u2013 this is not where spool recipient needs to be set. Using u201CSAP_AbapRunPrintExtu201D rather than u201CSAP_AbapRunu201D provides an extra section, Recipient Parameters u2013 need to complete this section with the user name and it works!

      Thanks for everyones help

      Ross

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.