About jklaverstijn

jklaverstijn · ‎05-16-2016

Hi Resa, Just got back from SGF and a subsequent vacation in SW USA. Still buzzing from the jetlag and all the impressions. I talked to several guys in the data management booth and they were all stumped. General advise was to raise the issue with tech support, which I will do asap. Cheers Jan.

jklaverstijn · ‎05-16-2016

Hi Peter, SAS still features the SAS/Access to IMS product. This would be the proper way to go. See the online doc. Hope this helps, - Jan.

jklaverstijn · ‎04-20-2016

Hi @SAS_inquisitive, It is indeed a full path. This is apparent because of the starting forward slash in the path. If that were missing the path would be relative to the current working directory. !SASROOT is a variable that is specified in the SAS config file (eg. sasv9.cfg) using the -set directive. It is expanded to whatever location SAS is installed into. Usually the directory containing the subdir SASFoundation. The variable refeference with an exclamation point will also expand when inside single quotes, unlike a macro variabel reference. Greetings from the Quad at SGF, - Jan.

jklaverstijn · ‎04-15-2016

If what I suspect is the case, that you have manually entered a person in metadata that matches an AD identity, you could edit the ExternalIdentity attribute of that person to match whatever you use for the sync process. This trics the code into thinking it was entered by the AD sync. It would open up the existing user for updates from the sync process and get rid of the errors. Hope this helps, - Jan.

jklaverstijn · ‎04-12-2016

Hi Paul, This is SAS 9.4M3 and LSF 9.1.3. I have seen the note. It does not apply: Job <1154>, Job Name <SAS Enterprise Guide_SASApp - Workspace Server node 01_F7 52E162-0AE0-0345-842F-EA85270DCC20>, User <klavj10>, Proje ct <default>, Command </srv/SASConfig/Lev1/SASApp/Workspac eServer/WorkspaceServer.sh -noterminal -netencryptalgorith m AES -encryptfips -metaserver osasigmdl03.ont.belastingdi enst.nl -metaport 8561 -metarepository Foundation -locale en_US -objectserver -objectserverparms "delayconn sph=osas igndl01.ont.belastingdienst.nl protocol=bridge spawned spp =36720 cid=18 pb classfactory=440196D4-90F0-11D0-9F41-00A0 24BB830C server=OMSOBJ:SERVERCOMPONENT/A52BHKER.AY00000Q c el=everything lb grid" -METAUSER '"klavj10@!*(generatedpas sworddomain)*!"' -METAPASS 7720093ab3A185107f65931940859c7 1 > Tue Apr 12 11:30:41: Submitted from host <osasigndl01.ont.belastingdienst.nl>, to Queue <eguide>, CWD <$HOME>, Specified Hosts <osasigcll 01.ont.belastingdienst.nl>, <osasigndl01.ont.belastingdien st.nl>; Tue Apr 12 11:30:41: Dispatched 1 Task(s) on Host(s) <osasigndl01.ont.belasting dienst.nl>, Allocated 1 Slot(s) on Host(s) <osasigndl01.on t.belastingdienst.nl>, Effective RES_REQ <select[type == a ny] order[r15s:pg] >; Tue Apr 12 11:30:41: Starting (Pid 4890); Tue Apr 12 11:30:42: Running with execution home </home/ONT/klavj10>, Execution CWD </home/ONT/klavj10>, Execution Pid <4890>; This shows what the note calls a "healthy grid" with a one second delay. I will continue investigating log files to sdee where the delay happens. We have an additional app server for SASEM that is not grid launched. There we see apporox. 5 seconds. So that's what we're aiming at. Minus of course some overhead. Cheers Jan.

jklaverstijn · ‎04-12-2016

Hi fellow admins, We are in the process of rolling out a multiple grid environments for a large population of data scientists. We use LSF for the grid management. One of the key components is the grid launched workspace server. Now I am struggling to bring down the time it takes to start a workspace server. The time is now at a minimum of 20 seconds. This is a big stumbling block in the acceptance by the users and I understand why. When using DI Sudio wss's are started all over the place. In EG one experiences an agonizing half minute of hourglass watching. I have already tweaked a few parameters in lsb.params according to a blog post from Edoardo Riva but I am now out of ideas. That's why I turn to you. Many thanks in advance, - Jan. lsb.params: Begin Parameters MAX_JOB_NUM=10000 NEWJOB_REFRESH=Y DEFAULT_QUEUE=normal ABS_RUNLIMIT=Y MIN_SWITCH_PERIOD=3600 JOB_SCHEDULING_INTERVAL=1 JOB_ACCEPT_INTERVAL=1 JOB_DEP_LAST_SUB=1 ENABLE_EVENT_STREAM=n MAX_CONCURRENT_QUERY=100 ENABLE_HOST_INTERSECTION=Y MBD_REFRESH_TIME=10 #MBD_SLEEP_TIME=10 MBD_SLEEP_TIME=1 #SBD_SLEEP_TIME=5 SBD_SLEEP_TIME=1 End Parameters

jklaverstijn · ‎04-11-2016

I use the app on Android phone on a regular basis. Recently I also started using the app on my brandspanking new tablet (Google Pixel C). So only now I realized that the app does not rotate on the landscape oriented tablet. So it seems a headturner, but not in a good way. Is this the same on Apple devices? May be hard to fix but I have my hopes for next year. Regards, Jan

jklaverstijn · ‎04-11-2016

Hi @junlue, The @ holds the inpout for the next INPUT statement in the same datastep iteration. A special case @@ holds the record even for the next iteration. If the input is spread over consecutive records in the input you can choose to use multiple input statements but without the @. Or you use the '/' in INPUT that instructs to load the next record and start reading at pos 1. Have (more than) a look at the doc as the INPUT statement is very rich and also fundamental. Regards, - Jan.

jklaverstijn · ‎04-11-2016

@junlue did any of responses help in any way?

jklaverstijn · ‎04-09-2016

Oh rats. I did it the other way round. Looks like @Reeza has the proper solution. - Jan.

jklaverstijn · ‎04-09-2016

This seems like an excellent oppportunity to use arrays. Image to arrays, one temporary with 'A', 'B', etc. The other one with XA, XB, ... The loop up the index of TYPE in the first and use that index to assign the value of X to the variable in the second array with the found index. data want; array types[4] $ _temporary_ ('A' 'B' 'C' 'D'); array xs[*] xa xb xc xd; type='D'; x=100; do i=1 to dim(types); if type=types[i] then xs[i]=x; end; put _all_; run; Hope this gets you on your way, - Jan

jklaverstijn · ‎04-09-2016

Hi @ilikesas no problem. I have done many a file- and directory manipulation in my life. What proved the most efficient, reliable and auditable (a big thing in the branches I work) is the following: Design a dataset that keeps track of files and their properties, status in the process (new, done, error, ...) with corrsponding timestamps etc Run a macro that generates a directory listing. Update above dataset and det4ermine what files need work (status new) based on whatever criteria you desire. In a datastep you can eg. read files with names like fh* by using a set statement of above dataset; WHERE status=new Read the selected files using the INPUT/PUT statements and the FILEVAR option. This way you can have a data driven process of reading and writing files in a single datastep. You can also use CALL EXECUTE on each individual file to run macro's using the name as a parameter. The datastep creates a table of files processed. Use the generated dataset to update the dataset used to keep track of work done. Update status to whatever is next. Many macros exist on the web that create directory listings. The gist of my suggestion is using the powerful FILEVAR option to cycle through a list of files. TS-DOC 581 gives a good idea of the possibilities. Hope this helps, - Jan.

jklaverstijn · ‎04-09-2016

How about "type fh*.* > allfhfiles". But don't you have a SAS question? Those are more fun. - Jan.

jklaverstijn · ‎04-09-2016

Hi @Ramanuj_Khatri please avoid cross-posting. Answering the question is so much harder for a community. Please consider removing one version. Regards, Jan.

jklaverstijn · ‎04-09-2016

Hi @Ramanuj_Khatri please avoid cross-posting. Answering the question is so much harder for a community. Please consider removing one version. Regards, Jan.

Online Status	Offline
Date Last Visited	‎09-22-2025 12:07 PM

Re: Why does SAS randomly report "Library WORK does not exist" during ...

Empty Web App Servers

Re: Email notifications from subflows

Re: Email notifications from subflows

Re: Automating SAS Package deployment using Import/Export Batch Tool

Re: Automating SAS Package deployment using Import/Export Batch Tool

Email notifications from subflows

Re: Wolfensäs: The FPS game that was written in SAS

Re: SAS Upgrade from 9.4 M7 to 9.4 M8 failing

Re: How to attach a file from a server in SAS Email

Re: Before you update to RHEL 8.8, please read.....

Re: Reference column type in data step OR suppress invalid numeric dat...

Re: How to set the umask for CAS?

Re: Convert Character ISO datetime into datatime

Re: SAS EG Stored Process wont update table

Re: Email notifications from subflows

Re: SAS Enterprise Guide to point to Unicode SAS

Re: SAS Upgrade from 9.4 M7 to 9.4 M8 failing

Re: Which element of the architecture effectively sends an e-mail when...

Re: How to set the umask for CAS?

Re: Output Directory in Batch Server properties

Re: How to connect to IMS database using SAS on mainframe

Re: specifying file path and autocall macros in Unix SAS

Re: SAS ImportAD error

Re: Long delay in starting a grid launched workspace server

Long delay in starting a grid launched workspace server

Re: We've got an app for that!

Re: What does this Retain statement do in this Data Step?

Re: What does this Retain statement do in this Data Step?

Re: Inserting a datastep variable value within another variable name

Re: Inserting a datastep variable value within another variable name

Re: concatenating external files based on file name

Re: concatenating external files based on file name

Re: Output Statement & Out= procedure option.

Re: Output statement and Out= Procedure option

SAS Global Forum 2017

SAS Global Forum 2018

SAS Global Forum 2016