Stored Process should not use username and password to access Info map

[deleted_user]

Hi,
I have a Stored Process that was created from an Enterprise Guide project. The project uses an Information Map. Issue is that the Stored Process that gets created uses the username and password to access the Information Map.

When the Stored Process is run through any SAS application (like WRS, EG, Stored Process Server) the user credentials are passed through the SAS global variables that store the username and password.

But when the Stored Process is executed i.e. scheduled though non SAS applications like LSF the user credentials are not passed and hence the Stored Process fails.

Is there any way by which we can suppress the use of username and password to access Information Map

Stored Process Code is shown below.

/* --- Start of code for "Import Quarterly_summary". --- */
/* Save off the current value of the validvarname option */
%let _imapValidVarName=%sysfunc(getoption(validvarname,keyword));

/* need for proper data column names in the InfoMap Libname Engine */
options validvarname=v7;

libname _egmle sasioime
user="&_InfoMapUser"
pw="&_InfoMapPassword"
metaserver="msr008.bsil.com"
metaport=8561
metarepository="Foundation"
mappath="/BIP Tree/ReportStudio/Maps"
PRESERVE_TAB_NAMES=YES;

data WORK.Quarterly_summary (label='Selected Data from Quarterly_summary');
length
Act_Expect_Bonus_Diff_Perc 8
Actual_Qtd 8
Actual_Ytd 8
Bonus 8
Bonus_Expected 8
;
set _egmle."Quarterly_summary"n (keep=Act_Expect_Bonus_Diff_Perc Actual_Qtd Actual_Ytd Bonus Bonus_Expected );
run;

/* clear the libname when complete */
libname _egmle clear;

/* restore the validvarname option */
/* NOTE: Might cause a warning if value is VALIDVARNAME=ANY */
options &_imapValidVarName;

/* --- End of code for "Import Quarterly_summary". --- */

[ChrisHemedinger]

Sunil,

Unfortunately, this is a limitation of the INFOMAPS library engine that won't be addressed until SAS 9.2.

EG "promoted" the user/password values for the Information Map task to hidden parameters in the stored process. You could change the stored process to prompt for those parameters instead, but that might not offer the best user experience either.

Chris

[SanjayM]

Hi Chris

Issue here is that when the stored process is scheduled through LSF the Username and password is not passed.

So should we modify the Stored Process and

1. Hardcode the username and password or
2. Can we remove the code of username and password.

GrassHopper

[ChrisHemedinger]

Ah Grasshopper,

You'll have to hard code the user/password for now in order to use the INFOMAPS (sasioime) libname engine. You can at least use PROC PWENCODE to encode the password so it isn't clear text.

Chris