About jakarman

jakarman · ‎08-06-2013

When you are used to program in the DMS / Base environment ...and have a lot of nodes in one long manual sas-code. The Eguide approach is a little bit different. You have your job-flow approach to segregate the process it in logical (smaller) steps. Advice: Split up you old code in smaller logical parts. This will make restarting en reviewing much more easier and you have solved the "stop at error" request, all is part of the job-flow approach. Normally a dependant (flow) source will not run when the first source generated errors. A lot more is possible: http://support.sas.com/resources/papers/proceedings09/320-2009.pdf To Run or Not to Run: Apply Conditions to Your Tasks

jakarman · ‎08-06-2013

The use of sasguest is confusing. It was introduced to be an anomyous user. serving the server the login webpage. At this web-page you have to make an autentication as no user is yet known. But this page has to be delivered by using a key. 34261 - The SAS Guest User's identity is required in metadata when you invoke the SAS® Information Delivery Portal You will find all of this back in java environment config files (ear/war) to be deployed to the JAVA part webcontainer of the webserver. Changing this is a lot work. So SASguest is no guest user... When you need to remove guest users as part of security policies this is to be explained. SASguest and sasanonym are still mentioned wit 9.4 SAS(R) 9.4 Intelligence Platform: Migration Guide I am missing a dedicated key (Original sasguest) of the logonmanager (SAS(R) 9.4 Intelligence Platform: Middle-Tier Administration Guide Looks the Original issue has been bypassed in an other way. Did have no chance to validate this. The details of users and groups is still changing SAS(R) 9.4 Intelligence Platform: System Administration Guide (Overview of Initial Roles, Groups, and Users). SAS(R) 9.4 Intelligence Platform: Web Application Administration Guide (Understanding Portal Authorization) all users are needing read and write access at the default ACT. This implies the need for a well designed security (ACT Acccess control templates) in the metadata. The name "unchallenged access" SAS(R) 9.4 Intelligence Platform: Installation and Configuration Guide SAS(R) 9.4 Intelligence Platform: Web Application Administration Guide (Enabling Unchallenged Portal Access) is used for "guest" access (no login).

jakarman · ‎08-06-2013

Tim, The web concept is build to be "stateless" no information is being held from to the next page. A Transactional approach would be impossible. To solve that the concept of sessions (like cookies) has been implemented. So sessions are bound to the web. With Eguide you are getting bound to a WS or a SP server. - When the WS is bound to your personal keys and handling your SP request this can be the same session (no mp-connect) - When the request is going to a SP server it will one that is often one of several for serving load-balancing. The best approach designing logic moving form 1 step (SP) to a next one would be a permanent like dataset defined to you project. You could call it "StagingArea" as an often used naming convention. Do not forget to add the logical checkings into your processing.

jakarman · ‎08-05-2013

Please explain why you do wat to have it as SAS-macro. I am missing the reason for that. As it could be having learned Word-macros. Thinking SAS programming is macros? You are describing the goal of a dataset having the filenames The easiest way is using the filename option and wildcarding with the infile statement. SAS(R) 9.4 Companion for Windows (infile wildcars) SAS(R) 9.4 Statements: Reference (infile filename). Having the filename you can use the datastepfunctions (no %sysfunc) delivering the additional fileinformation. The datastep is able to read all files and creating the SAS-dataset and the SAS-dataset containing just the filenames in one pass.

jakarman · ‎08-05-2013

Is it the same question as in https://communities.sas.com/message/176058#176058 ?

jakarman · ‎08-04-2013

Jason, Shivas did make a good description of the need to know the backgrounds of web environment. All docs are here as index: SAS Intelligence Platform (9.3) Your qusiton is touching the deployment (installation) and configuration. Some of the web-part are: SAS(R) 9.3 Intelligence Platform: Web Application Administration Guide, Third Edition (adding content)\ SAS(R) 9.3 Intelligence Platform: Middle-Tier Administration Guide, Third Edition (Using the SAS Anonymous Web User with SAS Authentication) You see the remarks on the choice of deployment (sassetup) choices. That steps are filling up the metadata and adding If you do not see anything, it could be - the deployment of the installation is not complete either metdatadata records are missing or you are using an incomplete installation of the SMC. - The way these kind of settings are maintained are changing every release of SAS. A workshop document and your current SAS version may differ. Your original post/request is saying you should add a SP in an webenvironment. If you have access to a full eductional SAS environment (Orion Star) go to the IDP. The solutions are some pages further in the lessons guides of the workshop. If you do that at home or at an other location, the deployments/installations may be very different. Seen is 9.2 versus 9.3 but also think about your SMC installation.

jakarman · ‎08-04-2013

As you are not having IDP (the web parts) .... You are stating not installed/using. Why should the SMC having something you don not have. In reality it are the SAS metadatabase and additional javaclasses (smc as tool) being adjusted by the installationsteps.

jakarman · ‎08-03-2013

Sandy, I am puzzeld what your intention is. Because: - The SASwork will get random names normally (windows) below the %temp% user environment. This area will be cleaned up when SAS normally stops. The Windows clean up should be extended at installation time to clean up left rubbish of abended processes. Are you a Windows admininstrator the user %temp% should be cleaned regular in generic as of possible leaking data. This is normally not c:\temp as Windows has become a multi-user OS. - If your problem is cleaning up SASwork as part of your logical processing the best way is use the SAS facilties, as there are; Base SAS(R) 9.4 Procedures Guide (PROC DATASETS) with kill all or delete a selection of the datasets. With 9.4 the Base SAS(R) 9.4 Procedures Guide the delete procedure is added to make this easier. If you would prefer SAS(R) 9.4 SQL Procedure User's Guide PROC SQL you have drop table. - There are a lot more SAS statements to access and maintain OS files bypassing all X statement requitement of batch scripting. This is one of the oldest parts of SAS and mostly got hiddem in all datastep processing capabilities and fucntions. An handy one is the SAS(R) Component Language 9.4: Reference pathname function. Returning the physical name of a logical one, like SASwork SASuser. - Just wanting to cleanup SAS-datasets or files like using Windows-Explorer? All is possible with SAS Explorer and the Eguide file-list. Just use the mouse. - There are situations to imagine an OS scritp is giving advantages, That is when there are no SAS functions/logic and/or needing specific features of the OS like Xcacls (security administration). As said the SASuser is the standard for the personal settings. Sometimes it is used to drop all kind of data in it because of missing conventions where the data should be stored. Sometimes it is used for samples and educational files. @Tom, normally the SASuser in a WS / SP is set as readonly (the -rsasuser option) as being set up to run to server multiple processes. The only exception with that is the DMS base-sas approach as the only one knowing he is starting a second one or not, is the operator. The operator, that is the person starting SAS, the sas-user.

jakarman · ‎08-02-2013

Sandy, These files are normally the personal user settings loacted in the %USerprofile% hierarchy (appdata). SAS has his own registry procedure like the Windows registry. They can get corrupted and when this happens the repair action is the delete. New fresh copies will be made at next startup. By that losing all settings that have been made as custom/personal. They are appearing at saswork because of multiple usage requiring an update access, to avoid locking /write issues a fresh copy at work is used. When there are modified settings explicitly placed you have to adress that. Work folders can be cleaned totally when no related process is running. Not only ""sas-"" datasets can reside at saswork but almost every type.

jakarman · ‎08-02-2013

is it a dynamic prompt using a dataset as input (9.2 and later)? In that case there are undocumented requirements possible indicating a design/coding error by SAS institute.

jakarman · ‎08-02-2013

The best thing about proc SQL multithreading.... You don't need to do anything for it, it will work. Look at your results IF you do not care about the ordening (left out order in the sql) you could notice it are different sets taken out of the Original datasets and than being appended. By the way Eguide flow is also supporting parallel processing, see: https://communities.sas.com/thread/39741?start=0&tstart=0 Your are in the performance and tuning area now. That is measuring (OS and SAS) with different scenarios

jakarman · ‎08-02-2013

Bruce, The most easy way to use multithreading is using procedures that support it. That are: - Proc SQL , Sort - HP versions of stat etc SAS(R) 9.4 Language Reference: Concepts (Support for Parallel Processing ) Some SAS options are controlling the limits. The nature of a sas-data-step (retain lag) knowing the order is blocking a parallelized (threaded) approach. SQL Queries and Sorting on the other hand are ideal for threading. When you want to use MP-Connect (or just Conect) you have to plan by yourself wich datasteps can run parallel and wich ones have to wait on another. The waitfor is statement is important for that. The others are rsubmit/endrsubmit and the communcation syslput/sysrput , signon/signoff SAS/CONNECT(R) 9.2 User's Guide (Example 5: Using MP CONNECT and the WAITFOR Statement) Tips and Tricks for Scalability and Performance

jakarman · ‎08-01-2013

Hi Question, Te message is strange. All code looks well but after the Segment an invisable or blank is taken into the name. ERROR: The value 'EXPERIAN_FSS_SEGMENT 'n is not a valid SAS name. Having copied (cut/paste) code form eg Word sometimes weird character are included (UTF), see Scott. removing that and retyping making sure normal chars are in your code and not a lost binary-zero or something like that.

jakarman · ‎08-01-2013

mrustemoglulearner_sas It would be nice to hear from you how you are proceeding with TS When a solution is found that being shared to the community so we all learn off it.

jakarman · ‎08-01-2013

mrustemoglu It would be nice to hear from you how you are proceeding with TS When a solution is found that being shared to the community so we all learn off it.

Online Status	Offline
Date Last Visited	‎08-02-2025 01:39 AM

Betreff: Einlesen einer (verdammt) kleinen Zahl

Betreff: ERROR: A parallel process did not start. Exiting loop.

Betreff: Export to STATA, in der Textvariablen werden die Umlaute nich...

Betreff: Format umwandeln - Text in Zahl

Betreff: XML Struktur in SAs einlesen

Betreff: XML Struktur in SAs einlesen

Betreff: ERROR: A parallel process did not start. Exiting loop.

Re: Which SAS9 Permission Wins?

Re: Which SAS9 Permission Wins?

Re: AD Account is locked at SAS Server

Activate Properties for Files and Folders in Enterprise Guide

Ability to Identify User Defined Macro variables in a SAS Code

Re: slow renaming sas7bdat.lck to sas7bdat

Re: slow renaming sas7bdat.lck to sas7bdat

Re: Use SAS-provided PostgreSQL instance for my own data?

Re: How to setup notepad++ as SAS text editor

Re: Convert EPOCH date

Re: Suppress Automatic PDF File Opening

Re: How to test for zero observations and still be in control

Betreff: Einlesen einer (verdammt) kleinen Zahl

How does memory management work in SAS?

Re: Checklist of SAS Platform Administration Tasks

Re: stop EG upon first error

Re: Creating a SAS Stored Process web page

Re: Stored process sessions in enterprise guide

Re: Trying to get file properties using macros and put them in a data ...

Re: CPU Utilization issue in Enterprise Guide 4.3

Re: Creating a SAS Stored Process web page

Re: Creating a SAS Stored Process web page

Re: making BAT file to delete SAS dataset

Re: making BAT file to delete SAS dataset

Re: Can not create Store Process from an EG-project with prompts

Re: MP Connect introduction?

Re: MP Connect introduction?

Re: SAS Error, Please Help. Many Thanks

Re: SAS EG very slow

Re: SAS EG 4.3 Slow Interface

SAS Analytics Explorers

CoDe SAS German