Any experiences with MP CONNECT?

[deleted_user]

Looking for experiences with MP Connect.

More specifically with using libname SASESOCK "mypipe"; style of piping.
This requires use of an Open SAS Meta Data Server.
This is totally new to me, as I don't want to have to preconfigure pipes to use.

So, what options do I need to set where?
What do I need to know about setting up/using a SAS Metadata server for this?
any other details/gotcha's I should know about?

[deleted_user]

[pre]
ERROR: Unable to resolve pipe name, mypipe, in the SAS Meta Data Server. Error message from Name Server component of Meta Data
Server is:
Unable to bind to Domain Name Server. Check the values of META* options and check that the server is running.
[/pre]

I have specified all the options needed, I thought:

[pre]
options metaserver="sas_metaserver" metauser="&user" metapass="&password" metarepository="Foundation" metaport=8561 metaprotocol=bridge;

PROC METAOPERATE
SERVER="sas_metaserver"
PORT=8561
USERID="&user"
PASSWORD="&password"
PROTOCOL=BRIDGE
ACTION=STATUS;
RUN;

libname outLib sasesock "mypipe" timeout=20;
libname outlib list;

data outLib.Intermediate;
do i=1 to 5;
put 'Writing row ' i;
output;
end;
run;
quit;
[/pre]

The "PROC METAOPERATE" works just fine.
When I try to use "outlib" I get the above error.
So what am I missing?

The documentation for this use of SASESOCK is woefully lacking in how to make use of a metadata server for storing the autoassigned port.

[DanielSantos]

Hi Chuck.

No need of Metadata Server for pipe parallelism, just need an available network port to use and SAS/CONNECT product licensed.

The port can be explicitly specified, or you could assign it a name through the SERVICES file.

Check this paper:
http://support.sas.com/rnd/papers/sugi30/pipeline.pdf

Be aware that this technique relies totally on your system multitasking capabilities.

Cheers from Portugal.

Daniel Santos @ www.cgd.pt

[DanielSantos]

OK forget it.

I figured out what you are trying to do.

Have you set the connection options previously?
[pre]
options metaserver="a123.us.company.com"
metaport=9999
metauser="metaid"
metapass="metapwd"
metaprotocol=bridge
metarepository="myrepos";
[/pre]
Also the documentation states, that you shouldn't have the same alias in the SERVICES file.

Cheers from Portugal.

Daniel Santos @ www.cgd.pt

[deleted_user]

I've had metarepository=default and metarepository=Foundation.

As you can see from the code, I am setting the options prior to their use.

The METAOPERATE works fine and returns what it is supposed to, so the server, port, user, pass and protocol are all set properly.

[deleted_user]

SAS Support got me going, finally.

It was about specifying the right mix of options:

[pre]
options metaserver='local_meta_server';
options metaport=8561;
options metaprotocol='BRIDGE';
options metauser="&user";
options metapass="&password";
[/pre]

I was also getting confused by the timing/ordering of the log messages due to the asynchronous rsubmit(s).