Skip to content
This repository has been archived by the owner on Apr 2, 2024. It is now read-only.

Providing startup parameters #277

Open
DenDuze opened this issue Feb 18, 2020 · 0 comments
Open

Providing startup parameters #277

DenDuze opened this issue Feb 18, 2020 · 0 comments

Comments

@DenDuze
Copy link

DenDuze commented Feb 18, 2020

Where can I add a pf-file where some startup parameters exists (next to DB connections) in 3P

In my normal development I use multipe pf-files for different environments
Some DB's are used in all environments, others are not
So I have 1 - let us call it shared - pf-file with 1 DB-connection defined in it
I have multiple other pf-files with some other DB-connections defined in them
Because we also have some startup parameters that we always want to use we put those in the first pf-file (because that one is always used).

In 3P I want to use the same startup parameters and the same DB-connections but I do not see where I can add startup-parameters (so I can not add there the pf-file as a startup-parameters).
I can only add that pf-file as a Database connection string (but then those other startup parameters are ignored (because they are no DB startup parameters)

I guess those startup parameters are not so important for usage in 3P but it would be handy that we can use the same pf-file in our normal development as in our 3p Session

NB: I know how to solve this --> put all startup-parameters under 'Prowin extra params'
==>but then I still need to maintain those startup-parameters in 2 places. I would like to use my existing pf-file where they are defined so I can mantain then in 1 place

Extra Issue: it looks like I need to provide the full path to my -swl-parameter (the path to that file is defined in my propath but it looks like '-swl ' does not work, it needs to be '-swl (while that does work in my normal development)

regards
Didier

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant