Hallo SAS Community, I want to use Dynamic Locking on our SAS-SPD-Server to enable concurrent access to tables. I added DYNLOCK=YES to the existing domain definition in the libnames.parm file: libname=datahilf pathname=/daten_q/spds/index/datahilf owner=sas
roptions="metapath=('/daten_q/spds/index/datahilf')
datapath=('/daten_q/spds/data1/datahilf')
indexpath=('/daten_q/spds/index/datahilf')"
LIBACLINHERIT=YES
DYNLOCK=YES; I stopped und re-started the SPD-Server and ran the following programm in parallel from two instances of SAS-EG: data datahilf.test_concurr;
do i = 1 to 60;
a= 1; output;
call sleep(1,1);
end;
run; From one of the instances I still get the following ERROR in the Log: 19 data datahilf.test_concurr;
20 do i = 1 to 60;
21 a= 1; output;
22 call sleep(1,1);
23 end;
24 run;
ERROR: MEMBER lock is not available for DATAHILF.TEST_CONCURR.DATA, lock held by process 40042846.
NOTE: The SAS System stopped processing this step because of errors.
NOTE: DATA statement used (Total process time):
real time 0.00 seconds
cpu time 0.00 seconds So it seems as if the configuration change in libnames.parm was not successful. I also checked whether the SPD Start-Script uses the correct libnames.parm file. The SPD version is (unfortunately still) SAS Scalable Performance Data Server 5.4 (HF 1) Build(Tue Aug 14 11:45:18 EDT 2018) SPDS SNET Server My questions: - What is wrong in the domain definition? (I also ensured that record level locking ist not set.) - Is there anything else to configure? Thanks in advance Robert
... View more
