SAS Institute. The Power to Know
Filter Results By:
Operating System

Applied Filters: (Reset All Filters)

Operating System: z/OS ( Reset Filter)

 
List:    – 10  of  16  > >|   Results per page:
Date Title Type
12/19/08 34237 - When installing SASŪ 9.2, if your SAS installation data file is expired, a warning appears
When you install SAS 9.2, if you select an expired SAS installation data file (SID file) in the Specify SAS Installation Data File dialog box of the SAS® Deployment Wizard, this error message appears: A ... http://support.sas.com/kb/34/237.html, 29KB
Installation Note

6/6/08 9713 - Expired site license generates warnings in the SAS log
SAS® software is licensed on an annual basis. When your license period has ended, SAS software is not required by contract to continue working. In order to help you maintain continuity in your work, SAS continues ... http://support.sas.com/kb/9/713.html, 19KB
Usage Note

2/21/08 21037 - Common error messges that might occur when you update SAS installation data
The following list contains common error messages that might occur when you attempt to update your SETINIT information. A corresponding solution is provided for each error. If you continue to receive errors after ... http://support.sas.com/kb/21/037.html, 19KB
Usage Note

10/5/07 17471 - Restart SASŪ servers and SAS spawners after renewing the SAS installation data file (SID file)
Restart all SAS servers and SAS spawners after you renew your software. In order to use any newly licensed products included in a new SID file and for new expiration dates to take effect, you must restart all SAS ... http://support.sas.com/kb/17/471.html, 19KB
Problem Note

10/1/07 16616 - You must edit the RENEW job JCL before you update a SETINIT/SID on a staged library (Action C) installation
If you use Action C for add-on products or for service pack updates, and if you intend to update the SETINIT/SID, then you must edit the DSN= option in the SASHELP statement in the RENEW job. Currently, the SASHELP ... http://support.sas.com/kb/16/616.html, 16KB
Usage Note

10/1/07 5796 - Update access to SASHELP library needed to renew SETINIT
If an attempt is made to renew a SETINIT/SID, the USERID associated with the job must have read/write or update access to the SASHELP library. If this is not the case, then the following messages are issued. These ... http://support.sas.com/kb/5/796.html, 17KB
Usage Note

10/1/07 14860 - Attempt to apply SETINIT/SID which results in message ERROR: WRITE ACCESS DENIED
If you applying a SETINIT/SID and receive the following message: ERROR: WRITE ACCESS TO MEMBER SASHELP.CORE.CATALOG IS DENIED. The problem is typically attributed to the SETINIT option not being set at invocation of ... http://support.sas.com/kb/14/860.html, 18KB
Usage Note

9/28/07 3065 - Phase 3 Kernel Initialization message if ERRORFLG is part of SETINIT
In Release 8.1 TS1M0, if ERRORFLG is part of the SETINIT, SAS abends with the following error on MVS: +(SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED. +UNABLE TO INITIALIZE THE SAS KERNEL IEF450I SASINSTA ... http://support.sas.com/kb/3/065.html, 19KB
Problem Note

1/24/07 15945 - SASLOG ERROR messages generated when ERRORFLG is part of the SETINIT
In Version 8 and beyond, SAS will generate the following ERROR if an unlicensed product is called and ERRORFLG is part of the SETINIT: ERROR: The SAS/XXXX product with which XXX is associated is either not ... http://support.sas.com/kb/15/945.html, 17KB
Usage Note

12/12/06 19165 - TS-DOC: Setting Up A Sub-Capacity SASŪ License
Released: 03JAN2007 Abstract: On newer mainframe systems, customers can subdivide the CPU capacity (using logical partitions, or LPAR) that they want to allow for SAS software. To accommodate this model, SAS offers ... http://support.sas.com/kb/19/165.html, 16KB
Usage Note

List:    – 10  of  16  > >|   Results per page: