Hi,

What command do we need to write at the BW Configuration->command option so that a session is run automatically upon baan startup. I understand it starts with -- (double hyphen) and something. Please advise the correct parameter

Rgds/scpcoon

session code, nothing more. I don't even think you need the "--'

Dave

Yeah, just the session code. Additionally you can give arguments for the session to be started, like specific field values for the session to start up with. Those you can then fetch in the program script using argv$(1), argv$(2) etc.

The -- are used for settings, for instance: -- -set AFSLOG=1 etc etc

Good luck!
En

a session is run automatically upon baan startup
If it meant for all users, then its better to use the Startup session ttaad2106m000 - which is server based instead of changing all the users BW command.

If the session you are starting has a blank form and only a Continue button, how to you configure the bwc file to not only start the session but to Continue as well, without having to be there to click continue with the mouse?

Roy

Roy,

If you have a session with no form then change the script type to 3-GL and you do not have to use a Continue button.

I would love to change the type but I can't. I don't have the code as it is not my session, so I guess I'm stuck with it just the way it is.

There is a lot of screens opening and closing with the session. As of now, we are running it as a Job which at times makes it difficult if not impossible to do anything on the console while it is running.

It was my hope to use windows scheduler to start a bshell out to run this on a regular basis.

Roy

Hi Roy,

just copy the session to a new one with say another ending for example m001 instead of m000. No need to copy forms, reports or the script. set the startup command for the session to "continue process" and put this session in bw command instead!

PS: Works as long as the session name is not hard coded in any of the scripts.

I changed start option to 38 on the session and tried it using the run command.

The session started immediately.

I then scheduled the task using windows scheduler on the remote server. When the time came, the session ran and exited when finished with no interaction needed.

Thanks for all of your help.

Roy :)