About JuanS_OCS

JuanS_OCS · ‎11-12-2014

jackhost, good observations. SAS provides some standard deployment plans, in your software depot and/or the support.sas.com page. As not all the deployments are standard, you can: - Create your own plan (plan.xml): if your are not used to it, I would not advise this option. - Ask SAS/SAS Consultant to create a plan for you, according to your requirements. (probably the best option) - You can also install individual software, after your initial and standard deployment, as the SAS PC Files Server... but I think this would not configure some components, as the Operating System Services Scheduling Server 9.4 and SAS DATA Step Batch Server 9.4. - But you can configure by yourself those servers from the SAS Management Console, after your installation and initial configuration.

JuanS_OCS · ‎11-12-2014

Hi, if your job works on DI but not from LSF, I would focus for now in the differences between them. First differences that you can find: - Even though they share the binaries and configuration from the SAS base installation + the SASApp, DI runs with the Workspace Server (usually) and LSF runs with the Batch Server. I would check the configuration for both servers (metadata + configuration files). - Check it they are running under the same SASApp. It is what I would expect, but that is not always the case... check to which workspace server do you connec with DI and with sasbatch command are you running with LSF (the easiest way is to check to which Batch server did you scheduled the Flow. My guess: As you are working wth the Work, and Work can be configured to different location on the workspace and batch, maybe it is a good idea to check the configuration for the work you are using on the workspace server configuration and which work are you using on the batch. (sasv9 and sasv9_usermods).

JuanS_OCS · ‎11-12-2014

Thanks for the correction Jaap... probably I missed to say that LSF and Process Manager are the officially supported 3rd party scheduling software (IBM develops this software), it can be purchased as separate product or included in some SAS Solutions, and if so, it would be included in the installation depot and license, includind an additional features to the Scheduler Manager plug-in in SAS Management Console, to be more exact and complete on the statement. Probably we can be even more complete. My point with this remark is to say that I appreciate the correction/remark, hopefully jackhost also does. And my intention was to simplify the explanation and bring to the table only the specifics he required to know, including the option of the creative and business integration solutions , with some documentation for his/the community reference, that probably will bring more concerns (as the installation of differences between operating systems!). I like your extra link for the schedule of reports, as special suggestion from the main Scheduling document: Scheduling in SAS(R) 9.4 Even though it is just an additional scheduled "job"from the technical point of view, I think it is interesting to know it in front, for the business/functional listeners. I recommend to read that one.

JuanS_OCS · ‎11-11-2014

I am not sure if there is an specific option for what you are asking for. I will check it. What I can tell right now is that you can have 2 approaches: 1- Instruct your users to work on the way you require for performance/best practices purposes (I think it is preferable) 2- If you cannot trust your users behaviour, you can always play with permission in the Operating System and in the metadata. Setting the visibility on or off a couple of times per day. But I strongly believe that is not the best way to work. And you can have always an overview of the performance with the log and some options like fullstimer.

JuanS_OCS · ‎11-11-2014

Kurt, I suppose jackhost was expecting to be able to try the schedule from the SAS MC. jackhost, remember that you have different option for the scheduling. Process Manager is only of the tool available for you. Btw: if you want to test simple scheduling from SAS MC, you don need Process Manager, just your Operating System services registered on your metadata (see under Server Manager), and make use of the Schedule Manager plug-in in the metadata. Here I write for you some documentation from the SAS technical support: Scheduling in SAS(R) 9.3 https://support.sas.com/rnd/scalability/platform/PSS6.1/pm8.1_using.pdf http://support.sas.com/documentation/cdl/en/scheduleug/64110/PDF/default/scheduleug.pdf An intresting overview that I quickly found googling: http://scorpiosoftware.blogspot.nl/2011/04/platform-suite-for-sas-devtestprod-tips.html For your second question, I would advise to open a new thread so it will have more visibility to all the SAS community

JuanS_OCS · ‎11-10-2014

In order to schedule you have different options, please choose the one that it fits more into your needs: - SAS provides an out-of-the-box Scheduler server that you can configure within your SAS Management Console. By default, this Scheduler server will schedule on your OS task scheduler (windows task scheduler, cron, etc), with simple options. In this case, if you want to implement triggers and advanced scheduling options, you would want to implement them with batch code yourself. - SAS also provides their own job scheduler, called Process Manager, and can also run with LSF. This will include new options into your SAS Management Console and a couple of new programs on your server (the Flow manager and calendar editor). This option have an extra cost on license and additional software will be installed and configured on your server and clients. And will include special scheduling features and triggers (file and time events, and conditionals AND/OR, etc). - You can also include the calls to your SAS programs inside your company's scheduler (many options), or implement a new one of your choice. This will provide you the option to integrate your SAS processes with other processes in your company and you can make use of the same kind of triggers. Even though this will not be integrated in your SAS Management Console and you will still need to do some manual work, it is a possible option to consider. - You have also the "hardcore" option. You can implement the calls to SAS, the triggers and everything and do the manual scheduling on your OS! Hope you won't chose this option, but, still, it is very plausible and you will have full control. I hope I am not missing any option... as you can see, may options, with pros and cons for your and your business purposes. If you need some additional information and support, please share, or also you can contact your local SAS Support office. I am sure they will be happy to feed you with the information you need.

JuanS_OCS · ‎11-10-2014

Yes, there is. Do you have licensed Process Manager and/or LSF? If not, maybe you would want to use one of your company's schedulers to run SAS code and implement triggers like the one I commented before

JuanS_OCS · ‎11-10-2014

Hi, I am unsure about your point with the clients and the server on the deployment. In other hand, maybe there is something that can help you with the scheduling of the jobs. One option that you can try is to make Job1 to wait until a file appears in a single location. Then, Job1 will be waiting until the file in created in the location. What you need to do with this option is: to make sure Job2 creates the file at the end of its execution. And to make sure Job1 deletes the file, also, along the execution (I would advice to do it just when Job1 starts to execute. In this way, you don;t need to be concerned about multiple Job1 execution, or dependencies with other jobs). There are other options, but I hope this one can help you with the basics.

JuanS_OCS · ‎11-07-2014

Good and elaborate initial guideline for me, Jaap. You have my appreciation for it. Many things to think about And also some others that I already realized. All those remarks look like a good objective for the future and also a lot of work for SAS developers (and rest of departments). I also think there are some current good improvements that creates a good path (the new env manager, the new backup tool) that makes me wonder what will come next. The complexity of all those changes also brings to my mind the idea that, maybe and only maybe, that objective is already there, but it takes time to implement everything, prioritize and keep selling by versions.

JuanS_OCS · ‎11-07-2014

Agreed. Some time ago, I also built a custom life cycle management system for SAS, but of course it is not the most desirable option. As far as I can guess or imagine, probably there are many interesting solutions for SAS around the world, trying to fill this gap on the SAS offer for the IT (business!) demand. Also, most probably the real situation is that all of those solutions are: custom, proprietary (Amazon AWS?) and not standardized/centralized by SAS Institute. I would bet that if many voices raise demanding an specific functionality, SAS Institute will implement in the future an initial approach to it, or purchase an existing one and then centralize it (as some times before). Is any of those ideas on the wish-list for the next releases? it will have my vote!

JuanS_OCS · ‎11-07-2014

Indeed, I should. My apologies and thanks. Probably with remark jenefa can have the complete answer to the question.

JuanS_OCS · ‎11-07-2014

I also would like to know!

JuanS_OCS · ‎11-07-2014

Only one additional remark: to run that code product_status (any code) will create a report over the products on the server side, what it is OK if you are on a single tier installation or what you need is to know the info from the server side. If you want to know the information from the client installation or a more complete information, that is not the option you are looking for.

JuanS_OCS · ‎11-07-2014

Hi.kuo, I like your comment, that is a good one. Even though, I still think that the more complete report is coming from the view.registry option

JuanS_OCS · ‎11-07-2014

Hi jenefa, the easiest and more complete way is to run C:\Program Files\SASHome\deploymntreg\sas.tools.viewregistry.jar with a command similar like java -jar sas.tools.viewregistry.jar. Then, you will get a complete report of your components installed and which versions/hotfixes are applied for them.

Online Status	Offline
Date Last Visited	3 weeks ago