What the h*** are Execution ID's?

I read the documentation and it's as clear as poorly made chicken stock. I read posting [SOLVED] Report Caster - Execution ID Configuration and this seems somehow related but I don't know how.

I have two WebFOCUS environments, Dev and QA. In QA, ReportCaster works - I can create and run schedules. In Dev, ReportCaster used to work. Some small tweak somewhere seems to have thrown a spanner in the works.

• I open a previously created schedule (that ran successfully some time ago).
  
• I open a task within this schedule. The task has the Server Name, Execution ID and Procedure Name. The Execution ID is "fmarian". The Procedure Name is "fmarian/demo1". demo1 is a fex in application folder fmarian.
  
• When I click on the Choose Procedure icon I get this message Please enter your execution ID and password for logging onto this server. What is this Execution ID and password? If I enter an MRE User ID "fmarian" and password, it does not work, I get the error invalid signal ABSQLOUT code 0 not allowed in state 5!!!! . In QA I enter an MRE User ID "fmarian" and password, which works.
  

I am confused about which user ID I need to use as an "Execution ID". It appears in our QA environment, I can use any MRE user ID that is flagged as a ReportCaster Schedule User ID. In our Dev environment these do not work - adding any User ID as Execution ID results in the ABSQLOUT error. Our environments are three-tier, Windows Client/Web Server, AIX Reporting/ReportCaster Server. Our MRE User IDs are not defined on the windows server nor on the AIX server. We do not use Realm Driver - I mention this because I found only one case regarding the ABSQLOUT error.

Help!

This message has been edited. Last edited by: Francis Mariani,

Francis,
I think it goes like this. The Execution ID equates to the ID that will run the job (and I think that populates the &DSTEDAUSER variable) and the other id (I forget which name) is the ID that created the job. The Execution ID should be the one that dictates the permissions to the table(s) and/or fex.

Check the user in your 'Managed Reporting/ReportCaster Credentials' and 'Data Servers' Environment Settings (Environment Properties in Dev Studio).

- ABT

What security are you running ? The execution id has to be an ID that is valid for that security method. For example we run with authentication WFRS and authorization is internal. Our reporting server uses LDAP therefore the execution id has to be a valid ldap ID.

There are really two different ID's, one for gaining access to the MRE which uses IBIMR_user and is generally also the ID that you use to gain access to RCaster. The other ID is the execution ID or IBIC_user. This ID is what is used on the reporting server for the execution of the report.

In secured environments, the ID must be a valid ID for the server and any data sources that it may need to access. In CLH's case, it needs to be a valid LDAP ID. On reporting servers that have been been setup as unsecured (security is either OFF or PTH), I like to set the execution ID in the RCaster job to an ID that is specific to the job since it does not have to be a valid ID. This way, when there are perfomance issues on the server, I can see the ID's on the reporting server console and easily be able to tell which agents are being used and from where they are comming from.

In your case, it appears that your QA server may not need a valid ID due to the way the data adapter has been configured, but you prod server may require that a valid ID be used for the data source that you are going after.

WebFOCUS Security Mode is PTH.

I verified MRE User Administration on both environments - my User ID is an administrator with rights to create schedules in ReportCaster.

I verified ReportCaster User Administrator on both environments - all MRE user ID's are defined there - I do get this message: "ReportCaster is configured with Managed Reporting. Please use Managed Reporting User Administrator Tool to add, delete, or update user/group information.".

I verified the ReportCaster console on both envrionments. On the QA environment, for Execution IDs - I can add anything - valid MRE User ID's or garbage User ID's - no errors. On the Dev environment, for Execution IDs, no matter what I add - valid MRE User ID's or garbage User ID's - I get the same message "The Execution ID and password specfified is not a valid user ID and password for the Server. Do you still want to continue?".