Library management with pre-assigned user/pass

[ThomasH]

Hello all,

I am trying to do the following:

There is 1 implementation and 1integration environment. Both contain a DB/2 database with different user/pass settings. In the physical storage of my table I have set up a profile with user/pass, which is no longer valid, when I deploy my .sas files to the integration environment.

The user/pass are pre-assigned in the SAS config files per environment and would need to be accessed via &DBUSER and &DBPASS - is it possible to set up the profile like this in the Management Console or do I need to do it differently?

Thanks a lot,
Thomas

[LinusH]

Some information is unclear to me:

What do exactly mean by "In the physical storage of my table..."?

Do you wish to continue to use user/pass from config, or use the ones registered in the metadata?

If you wish to use metadata passwords, you have to them in sync, and the re-generate your code upon change.

/Linus

[ThomasH]

Hi Linus,

thanks for your reply.

With ph. storage I mean the "physical storage" tab of the table.

And I would like to use user/pass from the config, so I do not have to regenerate the code but only put another config to another environment.

Regards,
Thomas

[Patrick]

Hi Thomas

What I have seen working is:
- The metadata definitions use &DBUSER and &DBPASS (like that, as text string).
- The values are set in the autoexec -> %let DBUSER=....

The deployed code contains then something like ..password=&DBUSER... - which resolves at runtime and based on the value set in the autoexec used.

HTH
Patrick

And yes: use proc pwencode to mask the passwords at least a bit.


Message was edited by: Patrick