During a SAS 9.3 deployment, the SAS Framework Server might fail to start, and the following error is reported in the SAS^® Deployment Wizard and in the associated log: There are several potential causes of this error:

1. The number of characters in your home directory causes the combined length of all environment variables to exceed 250 characters. In this case, you would see the following messages in /configuration directory /Lev1/FrameworkServer/dffedsvcfg/Logs/FrameworkServer_FrameworkServer_console.log :

   CEE3608I The following messages pertain to the invocation command run-time options.
   CEE3633W The total length of the combined ENVAR strings exceeded 250 characters.
   
   LSCX041 **** ERROR ****
           ABEND occurred in  SKSPWN3(SKSPWN3),offset 0000AA
           Program terminated by operating system. ABEND code = S40A
   Calling trace:
       Function        Line    Offset    Context
    SKSPWN3(SKSPWN3)   ----    0000AA
       MAIN(TKESRV)    ----    000116

This 250-character limit is a language environment (LE) limit, which SAS cannot change. However, there are two ways to circumvent the problem:

• Use a configuration directory pathname that is fewer than 41 characters.
• Or create a symbolic link for the configuration directory that is fewer than 41 characters.
  Edit the configuration directory/Lev1/FrameworkServer/dffedsvrcfg/dfs_serv.xml file and change the following two lines to reference a shorter path using the link:

/configuration directory link/Lev1/FrameworkServer/dffedsvrcfg/Logs

And

/configuration directory link/Lev1/FrameworkServer/dffedssvrcfg

2. The layout of the SID file associated with the customer order might cause an error during configuration or after a license update. In this case, you might see an error like the following in the Framework Server console log:

LSCX041 **** ERROR ****
        C run-time storage has been overlaid by the program
        ABEND occurred in @@079547(TKVERIF),offset 000876 
        Extended name: verify_setinit3
        Program terminated by operating system. ABEND code = S0C4

To circumvent this error, modify the PROC SETINIT code in the file setinit.sas in the directory SASHOME directory/SASFoundation/9.3 so that all CPUs appear on the same line, and remove any trailing blanks. For example, if the PROC SETINIT code looked like this:

PROC SETINIT RELEASE='9.3';
SITEINFO NAME='SAS CUSTOMER' SITE=999900099 OSNAME='OS' RECREATE
BIRTHDAY='12JAN2012'D  EXPIRE='31DEC2012'D PASSWORD=nnnnnnnnn;
CPU MODEL='IBM' MODNUM='2817-710' SERIAL='cccccc' NAME=CPU000;
CPU MODEL='IBM' MODNUM='2817-504' SERIAL='dddddd' NAME=CPU001;
CPU MODEL='IBM' MODNUM='2817-604' SERIAL='ffffff' NAME=CPU002;
EXPIRE 'PRODNUM000' 'PRODNUM002' 'PRODNUM003' '31DEC2012'D / CPU=CPU000
       CPU001 CPU002;

Modify it to look like this:

PROC SETINIT RELEASE='9.3';
SITEINFO NAME='SAS CUSTOMER' SITE=999900099 OSNAME='OS' RECREATE
BIRTHDAY='12JAN2012'D  EXPIRE='31DEC2012'D PASSWORD=nnnnnnnnn;
CPU MODEL='IBM' MODNUM='2817-710' SERIAL='cccccc' NAME=CPU000;
CPU MODEL='IBM' MODNUM='2817-504' SERIAL='dddddd' NAME=CPU001;
CPU MODEL='IBM' MODNUM='2817-604' SERIAL='ffffff' NAME=CPU002;
EXPIRE 'PRODNUM000' 'PRODNUM002' 'PRODNUM003' '31DEC2012'D / 
       CPU=CPU000 CPU001 CPU002;

3. If after performing a license renewal of the SAS software the SAS Framework Data Server fails to start, and the following message is found in the Framework Data Server log file:

2013-09-30T08:04:18,442 ERROR [00000000] DataFlux.Licensing :SASUSR1 - License checkout failed for

 feature 'SAS Framework Data Server' due to the following: The feature is not licensed.

The license renewal process will not update the correct file if you used "Method 2" to update your license. The SAS Framework Data Server references SASHOME directory/SASFoundation/9.3/setinit.sas to obtain the licensing information.

The work around is to manually copy the proc setinit code from the renewal SAS Installation Data(SID) file into SASHOME directory/SASFoundation/9.3/setinit.sas

Below is an example of the proc setinit code block that needs to be copied into the setinit.sas file

PROC SETINIT RELEASE='9.3';
SITEINFO NAME='SAS CUSTOMER' SITE=999900099 OSNAME='OS' RECREATE
BIRTHDAY='12JAN2012'D  EXPIRE='31DEC2012'D PASSWORD=nnnnnnnnn;
CPU MODEL='IBM' MODNUM='2817-710' SERIAL='cccccc' NAME=CPU000;
CPU MODEL='IBM' MODNUM='2817-504' SERIAL='dddddd' NAME=CPU001;
CPU MODEL='IBM' MODNUM='2817-604' SERIAL='ffffff' NAME=CPU002;
EXPIRE 'PRODNUM000' 'PRODNUM002' 'PRODNUM003' '31DEC2012'D / 
      CPU=CPU000 CPU001 CPU002;

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS BI Server	z/OS	9.3		9.3 TS1M0

* 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.

---

Type:	Installation Note
Priority:	alert

Date Modified:	2014-01-14 11:21:36
Date Created:	2010-04-20 14:03:57