I am trying to create a second engine for a parallel task on my computer. Normally the process works fine, however when I try to open a queue in the same App that I am current in, I get SYS1003. Should I worry?

Wayne

Wayne,

This is doable. Are you specifying a queue or are you letting the CreateQueue function assign it for you? Can you post some sample code?

[email protected]

SRP Computer Solutions, Inc.

Here's the code I'm using (pretty basic stuff):

App=@AppID

Station=@Station

Server=\\.\":Station

Error=CreateEngine(Engine,Server,App, CREATE_ENGINE_OPEN_ALWAYS$,1)

if (Error) then

  Status=Unable to create OI Engine.  Error ':error

  debug

  return

end

* Create a queue on that engine.

Error=CreateQueue(Queue, Engine, '', App, "SYSPROG")

if (Error) then

CloseEngine(Engine)

Engine='

Status=Unable to open Version Control Queue - Error ':Error

return

end

===================

This works fine as long as I don't use the APP i'm in. In other words the line of code that causes it to fail is APP=@APPID. Any other app is okay.

Wayne

Wayne,

Well SYS1003 means there was an error in the logon. I noticed that in your CreateQueue function you are hardcoding SYSPROG as the user, regardless of the application. I doubt that SYSPROG is a valid user for all applications (i.e. databases) so that might be your problem. I realized you said "any other app okay" but how many other apps have you actually tried?

FWIW, I have successfully created an engine for the same application I was in and made a request through it. So I know it can be done.

[email protected]

SRP Computer Solutions, Inc.

Okay, I have three apps arranged hierarchically as follows:

SYSPROG

– | –

APPPARENT

– | –

APPCHILD

– | –

APPGRANDKID

Sysprog is the user with System Admin rights and Create Permission in all three applications. I have been sitting in APPGRANDKID starting local engines in APPCHILD and APPPARENT with no trouble. But it refuses to start a local engine in APPGRANDKID.

However, I just went into APPCHILD and started a local engine in APPCHILD with no problem, so you seem to be correct that it has something to do with the APPGRANDKID application itself. I tried using another user besides SYSPROG, but it still doesn't work.

Any other thoughts?

Wayne

Continuing Story:

I tried running it from another app that is at the same level as APPGRANDKID. It had the same result. This seems lame, but could it be that there is an issue with being three layers away from SYSPROG?

Wayne

Wayne,

Sysprog is the user with System Admin rights and Create Permission in all three applications.

How did you go about doing this? Did you make SYSPROG the default author of each application or did you use the Database Manager to create a SYSPROG user with the appropriate rights?

I'm not sure if any of the above really matters. I create those applications and even went one further (APPGREATGRANDKID) just for good measure. I used SYSPROG to be the author of the application so it would have full rights. It gave me no problems in connecting to a dynamic engine in the same application. I assumed you were also creating dynamic engines as well. What happens if you attempt to connect to a static engine? (E.g., C:\OIPATH\OENGINE /AP=TEST APPGRANDKID)

If you send me your email address I will try and send to you a self-contained testing program that we designed and presented at the NOLA conference. It gives you an interface to input your variables and then displays a log of the results so you can easily trace down your problems:

[email protected]

SRP Computer Solutions, Inc.

My email is [email protected].

I've been having problems trying to kick off an engine on another server as well. It keeps starting the engine locally and returning an error status of 3. Maybe this module will help with that as well. Thanks,

Wayne

Oh, yes. Regarding your other question, the applications were originally created by sysprog, then modified to create the hierarchy shown. So sysprog was always the user with create permission.

The application definition on the APPGRANDKID was further modified to use the database of the APPCHILD app (it's immediate superior), rather than it's own. That does make it different from the other two. Could that be causing the problem?

Wayne

Wayne,

The RDK is on its way. At first I thought you might have stumbled onto something when you indicated that the database ID for the APPGRANDKID application belonged to APPCHILD. So I recreated my applications accordingly and re-tested. However, everything still worked fine for me.

I'm sure you've already done this but I would confirm that the APPCHILD does, in fact, have SYSPROG as a valid user.

[email protected]

SRP Computer Solutions, Inc.

On the contrary, I was onto something. You'll notice I'm sending the application name to CreateEngine, not the database name. This is left over from when I first worked with this and they were, in fact the same. But the APPGRANDKID database does not exist.

So this solves the problem! Thanks for your help. I have another problem now, but I'll use your module for a while to see if I can solve it before I post another thread.

Thanks, again!

Wayne

View this thread on the Works forum...