sas9.2安装问题：ERROR: Library WORK does not exist.

是 否 +2 论坛币

k人 参与回答

经管之家送您一份

应届毕业生专属福利!

求职就业群

赵安豆老师微信：zhaoandou666

经管之家联合CDA

送您一个全额奖学金名额~ !

立即领取

感谢您参与论坛问题回答

经管之家送您两个论坛币！

+2 论坛币

ERROR: Library WORK does not exist.   FATAL: Unable to initialize the options subsystem.   (SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED.   UNABLE TO INITIALIZE THE SAS KERNEL

系统时间，java都没问题,求解决办法

在网上找到：http://support.sas.com/kb/17/783.html
If you receive the following error at invocation,make sure that the directory being used as the WORKdirectory exists, and that you have both read andwrite permissions for that directory:   ERROR: Library WORK does not exist.   FATAL: Unable to initialize the options subsystem.   (SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED.   UNABLE TO INITIALIZE THE SAS KERNELThe default location for the WORK directory can befound in the !SASROOT/sasv9.cfg (or !SASROOT/sasv8.cfg)file. If you do not have permissions that allow youto modify this file, you can specify the -WORK optionat invocation:   sas -work /tmpor   sas myprogram.sas -work /tmpThe location you specify with the -WORK option at invocationwill be used only for that SAS process.Note that you cannot specify the -WORK option on anOPTIONS statement.

扫码加我 拉你入群

请注明：姓名-公司-职位

以便审核进群资格，未注明则拒绝

分享0 收藏0 回帖

关键词：Library BRARY Error exist Work Error Library Work Does exist

是在运行里面输入sas -work /tmp的意思么？

还有一个说是，        You did not set up LOADL_JOB_NAME to null
Set up to run SAS

    To run SAS, you have to set up the path where you can access SAS binary
    and the work area where SAS can put the temporary files there.

    1. Add /usr/local/packages/sas to the path environment varaible at your
    .profile or .cshrc files.

    2. Instruct SAS to use /scratch as your work area.

    If you use ksh shell, add the line below to your .profile
    export LOADL_JOB_NAME=""

    If you use csh or tcsh shells, add the line below to your .cshrc file:
    setenv LOADL_JOB_NAME ""

how to start a SAS session

    In Pelican, you can run SAS in the SAS windowing environment, in interactive
    line mode, or batch mode or submit your appliation to LoadLeveler queue.

    Windowing environment
    1. Start the X server application if it is not running. For example,
    if you have Exceed installed or any other X server software, you should
    start the X server first.

    2. Make sure that clients running on the Pelican node have permission to
    connect to your server. Most systems control this by using the xhost client. You
    can enter the xhost command system prompt on the system that is running
    your X server (your workstation or pc):

    jonedoe_PC$ xhost +

    3. Log in your Pelican account

    4. Identify your server as the target display for X clients that are run on the Pelican.
    You can do this in one of two ways:

    a. Set the DISPLAY environment variable.
    In the Korn shells, you can set the DISPLAY variable as follows:
    export DISPLAY=jonedoe_PC:0.0

    In the C shell, you must use the setenv command:
    setenv DISPLAY green:0.0
    b. Use the -display option. For example:
    sas -display green:0.0

    Examples:
    export DISPLAY=honggao.ocs.lsu.edu:0.0
    sas

    setenv DISPLAY honggao.ocs.lsu.edu:0.0
    sas

    sas -display honggao.ocs.lsu.edu:0.0

    Using SAS in Interactive Line Mode
    To start an interactive line mode session, invoke the SAS System with the NODMS
    or NODMSEXP system option:
    sas -nodms
    sas -nodmsexp
    You can end the session by pressing the EOF key (usually CTRL+D) or by issuing the ENDSAS statement:
    endsas;
    Using SAS in Batch Mode
    To invoke the SAS System in batch mode, you must specify a filename in the SAS
    command. For example, if mysas.sas executed:
    sas mysas.sas
    The command would run the program in the foreground. If you want to run the
    program in the background, add the ampersand to the end of the command:
    sas mysas.sas &

    Submit the SAS job to LoadLeveler queue
    You can submit your SAS job to LoadLeveler queue by using spsubmit. To use
    spsubmit, you have to add the /home/loadl/bin to your path environment varaible
    at your .profile or .cshrc files. To submit SAS job to LoadLevler batch queue:

    spsubmit -class job_class /usr/local/packages/sas/sas sas_program

    Examples:
    spsubmit -class LB4S -Email johndoe@hotmail.com /usr/local/packages/sas/sas mysas.sas
    spsubmit -class LB4L /usr/local/packages/sas/sas mysas.sas


Note: Pelican only allows 30 minutes interactive sessions. If you expect that
your SAS job runs longer than 30 minutes, please submit it to LoadLeveler queue.


Errors and Causes


    Eorr Message
           
    casuse
    sas: not found.        The PATH environment variable does not contain /usr/local/packages/sas
    ERROR: Cannot open X display. Check display name/server access authorization.
    ERROR: Cannot open X display. Check display name/server access authorization.
    ERROR: Explorer failed to initialize.
    ERROR: Device does not support full-screen.
    ERROR: Device does not support full-screen.
            Either the DISPLAY environment variable is not set or the X server is not running
    ERROR: Library WORK does not exist.
    FATAL: Unable to initialize the options subsystem.
    (SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED.
    UNABLE TO INITIALIZE THE SAS KERNEL
            You did not set up LOADL_JOB_NAME to null