SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 45924: "ERROR: A lock is not available for RSKPARTS.SIMSTATE.DATA." when distributing the positions in a portfolio across nodes

DetailsDownloadsHotfixAboutRate It

When you run a spawning macro (for example, %RDCSPAWN) in SAS Risk Dimensions, you might encounter errors like the following in the SAS log:

ERROR: A lock is not available for RSKPARTS.SIMSTATE.DATA. ERROR: Errors occurred while the application was adding variables to the results data set <netPathTemp>/SIMSTATE. ERROR: A lock is not available for RSKPARTS.SIMRFS.DATA. ERROR: Errors occurred while the application was adding variables to the results data set <netPathTemp>/SIMRFS. ERROR: A lock is not available for RSKPARTS.SHOCKS.DATA. ERROR: Errors occurred while the application was adding variables to the results data set <netPathTemp>/SHOCKS.
These errors are known to occur when SPLITBY=INSTRUMENTS is specified and you request any of the output data sets that are listed in the error message (for example, by using the OPTIONS=(OUTALL) option).

To correct this problem for the %RDCSPAWN macro, replace your rdcspawn.sas file with the rdcspawn.sas file that is stored on the Downloads tab.

The default location for the %RDCSPAWN macro is:

  • Windows: !SASROOT\risk\sasmacro\rdcspawn.sas
  • UNIX: !SASROOT/sasautos/rdcspawn.sas
Back up your existing rdcspawn.sas file by renaming it with a filename that does not use a .sas file extension. For example, you can use rdcspawn.orig. Download the rdcspawn.sas file from the Downloads tab and save it as rdcspawn.sas in the directory where the original rdcspawn.sas file was stored. Use all lowercase letters in the filename (use rdcspawn.sas, not RDCSPAWN.sas, or some other variation that contains any uppercase).

To correct the problem for other spawning macros, do either of the following:

  • Do not specify the OPTIONS=(OUTALL) option when you call the spawning macro.
  • Edit the spawning macro such that the NOSIMSTATE, NOSIMRFS, NOSHOCKS, and NOMODCOV options are specified in PROC RISK when SPLITBY=INSTRUMENTS and when the portfolio part number is greater than 1. Note that the NOSIMSTATE, NOSIMRFS, NOSHOCKS, and NOMODCOV options need to be specified last in the list of options. This ensures that they are not overridden by subsequent options. For guidance, see the rdcspawn.sas file that is on the Downloads tab.

Click the Hot Fix tab in this note to access the hot fix for this issue.

The hot fix is for releases 5.3_M1 and 5.31 of SAS Risk Dimensions.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Risk Dimensions Enterprise EditionMicrosoft® Windows® for x645.25.49.2 TS2M09.3 TS1M2
Microsoft Windows Server 2003 Datacenter Edition5.25.49.2 TS2M09.3 TS1M2
Microsoft Windows Server 2003 Enterprise Edition5.25.49.2 TS2M09.3 TS1M2
Microsoft Windows Server 2003 Standard Edition5.25.49.2 TS2M09.3 TS1M2
Microsoft Windows Server 2003 for x645.25.49.2 TS2M09.3 TS1M2
Microsoft Windows Server 2008 for x645.25.49.2 TS2M09.3 TS1M2
Microsoft Windows XP Professional5.25.49.2 TS2M09.3 TS1M2
Windows Vista5.25.49.2 TS2M09.3 TS1M2
Windows Vista for x645.25.49.2 TS2M09.3 TS1M2
64-bit Enabled AIX5.25.49.2 TS2M09.3 TS1M2
64-bit Enabled HP-UX5.25.49.2 TS2M09.3 TS1M2
64-bit Enabled Solaris5.25.49.2 TS2M09.3 TS1M2
HP-UX IPF5.25.49.2 TS2M09.3 TS1M2
Linux5.25.49.2 TS2M09.3 TS1M2
Linux for x645.25.49.2 TS2M09.3 TS1M2
Solaris for x645.25.49.2 TS2M09.3 TS1M2
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.