I have a business need to provide RUNDATE in the Subject Line of outgoing e-amil being distributed by ReportCaster. Schedules have been set up to run each report, and the Subject Line is defined as:

Report for '%BURST' on '&RUNDATE'

I have defined &RUNDATE as a parameter.

To avoid having to manually change the value for &RUNDATE before submitting the job, I have created another focexec that sets the value for &RUNDATE and calls DSTRUN to submit the job while passing &RUNDATE as a parameter.

So I have 2 schedules and 2 focexecs: the first job sets &RUNDATE and submits the 2nd job passing &RUNDATE as a parameter and making it available to ReportCaster.

This approach works beautifully in Development; when I move everything into Production I get Return Code = 11. Not much help there.

I can also create similar circumstances in Production (by cloning schedules and modifying them so they do not send out reports) and it runs just fine. I'm using the same userid/password combinations as the Production jobs.

Code to call DSTRUN:

-SET &DSTRUN =
- DSTRUN(
- '&RCUSER.EVAL',&RCUSER_LENGTH.EVAL,
- '&RCPASS.EVAL',&RCPASS_LENGTH.EVAL,
- '&RCSERVER.EVAL',&RCSERVER_LENGTH.EVAL,
- '&SCHEDULE.EVAL',12,
- '',0,
- 3,
- '&RCOWNER.EVAL',&RCOWNER_LENGTH,
- '&VALUE.EVAL',
- &VALUE_LENGTH.EVAL,
- '',0,
- 'I4' );

-----------------------------------
&RCUSER = 'admin'
&RCPASS = ''
&RCOWNER = 'admin'
&VALUE = 'RUNDATE=08/19/08'

Lengths are all calculated correctly.

-----------------------------------

I signed into ReportCaster as Admin and created the appropriate schedules in the Admin folder.

The Execution ID is a generic runtime userid and is different from &RCUSER and &RCOWNER.

Anyone have any ideas?

Alan