We are interested to see SAS z/OS 9.4 provide technology support for new-function added with IBM z15 Integrated Accelerator for Z Sort (new SORT LISTS / SORTL instruction.)    Please click LIKE / VOTE-UP for this ballot item, or contact your SAS sales or product manager directly to voice your enterprise's interest with adding ISV-interface support for Z Sort functionality, new with the IBM z15.   Benchmark performance-improvement results with native IBM DFSORT SORT execution, where compatibility is exploited, have demonstrated up to 50% CPU-time reduction and also some improved elapsed time.   IBM has communicated that ISV-interface support is available as well, but this technology-extension requires significant ISV R&D effort.  While some IBM technical documentation mentions that "IBM is currently working with Independent Software Vendors (ISVs) to take advantage of the new feature as well", it is evident that SAS INSTITUTE is looking to customer-input for direction with prioritizing new-function support.   Scott Barry SBBTech LLC   ... View more

Request to SAS: Please provide, in every SAS version, a tool to convert files/catalogs between 32 and 64 bit (without the need to buy a licence for a new 'SAS module'). This should not be a problem for experienced (SAS) programmer. Thanks. ... View more

Hi,   The idea is to allow to use hyphen(-) notation in the DATA statement. So the following code would work: data b1-b10 ; set sashelp.class ; run ; and create 10 data sets b1 to b10. The idea is to make it symmetric to SET statement behavior such as: data a1 a2 a3 a4 a5 a6 a7 a8 a9 a10 ; do value1 = 1 to 10; output; end; run ; data All_a1_to_a10 ; set a1-a10; run ; All the best Bart   ... View more

It would be nice to have a CAT_() type function that uses the format applied to the variables rather than Best for numeric variables.    For example, I would have preferred if the WANT_STRING was the same as the output from the HAVE_STRING code, since a format is applied to the variables already.    data have; format date1-date20 date9.; format datec1-datec20 $9.; length datec1-datec20 $9. x_string y_string $256.; array _date(*) date1-date20; array _datec(*) $ datec1-datec20; do i=1 to dim(_date); _date(I)=floor(ranuni(25)*365+1); _datec(I)=trim(put(_date(I), date9.)); end; have_string=catx(", ", of _date(*)); want_string=catx(", ", of _datec(*)); run; proc print ; run; ... View more

Please add a toggle switch that would alternate between displaying formatted and unformatted values in SAS data viewers.  Similar to the existing option to view Variable Names versus Variable Labels.  The current display always hows value labels and one has to resort to time-consuming tricks to unmask the relationship between value and format.  A simple toggle would permit a quick access to information hidden by the formatted values. ... View more

Hi,   the idea is to allow for the SET statement to use observation's number(curobs) in the where clause and where=() dataset option. So the following query on the data set's engine level would be possible:   data out1; set sashelp.class curobs=co; where age>12 and co<10; run; data out2; set sashelp.class(curobs=co where=(age>12 and co<10)); run; with expected output equivalent to: data out3; set sashelp.class curobs=co; if age>12 and co<10; put (_ALL_) (=); run; The key idea is that it would be possible on data engine level, so before PDV.   All the best Bart     ... View more

Following from thread https://communities.sas.com/t5/SAS-Programming/Optimize-SAS-Code/m-p/532716#M145990 When SAS sees this code:   data CLASS(index=(AGE)); set SASHELP.CLASS; run; proc sql; select * from CLASS where AGE=12 or (AGE=11 & NAME='Alice'); quit; it decides to not use indexes (because the OR operator is used). It would of course be beneficial that only ages 11 and 12 be selected using an index, and then the NAME filter applied.   ... View more

As part of security compliance, the cyber team is looking to encode all the SAS Stored/transmitted passwords using SAS005.Several Java and .NET based SAS components cannot decode SAS005 passwords. This is a deliberate limitation that reduces security exposures Also the SAS Private JRE is version 1.8.0_232 will you be updating this to a more current version such as 1.11. and what type of Java is being used such as Open JDK or IBM etc   We are checking the feasibility to apply SAS005 encoding to all the internal SAS Java and .Net applications/files ... View more

Hi team,   We have a AWS IAM Compliance while uploading a file into S3 bucket of adding tag. Would like you to add this as feature for PROC S3 below is example from AWS CLI aws s3api put-object --bucket <bucket_name> --server-side-encryption aws:kms --ssekms-key-id <arn_key_id> --key <filename> --region us-east-1 --tagging <value>   Thanks Harry ... View more

Dear SAS teams,   Request: I would like to propose to include a simple spell check in the BDN web application, during the creation of a Term, to align with other checks across the BDN app.   Details / Problem:   When exporting a Term Definition with spaces an error message is displayed saying that the Term is not valid since the entity type may be max 23 characters". And this is correct. As documented in the Business Data Network User Guide, Export Terms to an Entity Definition creates an entity definition file suitable for import to Master Data Foundation projects or SAS MDM. As such, it must meet the requirements in MDM as stated in the SAS MDM Administrator's Guide. Note: Because of the addition of relationship type attributes, values in the MDM_REL_TYPE table must be sized to 23 characters or less to run the schema evolve process successfully. If you have values in the MDM_REL_TYPE table larger than 23, change the column size before attempting to run the schema evolve script. Only the underscore special character is allowed. Remove any other special characters in the MDM_REL_TYPE table before attempting to execute the schema evolve script. But the process to create a term allows spaces and other chars.   Export to XML is a workaround, but still only a workaround for a functionality that is already implemented, the Export Definition.   Thank you in advance for your attention. I would like to hear the progress about this feature/hotfix request. Kind regards, Juan     ... View more

Often I get this:   NOTE: There were 63 observations read from the data set LIB.TOTALDRUGRX. NOTE: The data set LIB.TOTALDRUGRX has 63 observations and 5 variables. NOTE: Compressing data set LIB.TOTALDRUGRX increased size by 100.00 percent.       Compressed is 2 pages; un-compressed would require 1 pages.     So the compressed dataset is bigger than the uncompressed version?!?   How about not compressing it if the result is bigger? ... View more

SAS ABM exportaba la tabla con formato de campo 64 caracteres. Tras el cambio del producto(migración), SAS CPM exporta la tabla con formato de campo 260 caracteres siendo necesario aplicar una conversión para formatearla en 64 caracteres y poder manejarla más fácilmente. Eso en cifras significa que, con SAS ABM generábamos una tabla de unos 45/50Gb, mientras que con CPM partimos de una tabla de más de 200Gb que es necesario formatear, necesitando por tanto más de 150Gb que finalmente son liberados.   Adjunto el código del formateo que se le aplica en SAS Guide: se cogen todos los campos (columnas) de la tabla STL_ASSIGNMENT, se convierten a 64 caracteres y se sobreescribe la misma tabla. Tras esa transformación pasamos de una tabla de 204Gb a otra de 50Gb que es la que finalmente usamos para continuar el proceso. Es una tabla de 12 millones de filas y no es fácil trabajar con ella.       Necesitariamos una investigacion y se proporciona alguna alternativa dado que es brutal el tamaño que se genera. ... View more

During the recent delivery of the SAS Visual Analytics 8.3: Basics course, I did a demo highlighting how Data Views can now be used to provide a "business layer" between the CAS Table and the Report, which would be used as the basis for future reports.   The functionality is great but, as far as I can tell, the only way to determine if there is a view associated with a CAS Table is to add the data source to a report, then click Data Options and select "Data View..." from the menu.   Suggestion(s):   Minimum: If there ARE data views, indicate how many in parenthesis beside the Data View... menu option in VA.  e.g.  Data Views (2)...   Better: Suggestion above, and change the behavior of the menu so that the Data View... option is disabled if there are NO data views associated with a selected data source (similar to how the Data Source Filter only shows Edit/Delete Data Source Filter options if there are data source filters currently in effect.   Ideal: Both of the above techniques, plus an indication in the Manage Data application and the Add Data Source dialog box within VA, which allows expanding the Available list for tables with Views, to see the views.  If clicked, the Details shows the structure of the view (Sample Data and Profile would disappear).         ... View more