Hi there,   the process you are looking for should be similar to:   - copy migrate all lsf/ps calendars, then the schedules & flows (they may require some modifications, regarding uids and such, give it a look) - this can be automated or semi-automated   - ensure the groups and authentication domains are in place, with all the metadata permissions as expected   - migrate SAS metadata - this is automated   - Then re-deploy & re-schedule the flows - it is possible to automate this via scripts using the platform framework (and you will need the passwords of the users, so careful), but probably it will take you less overall time to do this manually, each user, and more in control. When you re-schedule the flows, the flows should have picked up the right calendar/schedule, or at least they will be in the list in SMC.   I hope this helps     ... View more

Hi @gwootton ,   I am sorry, but I believe they are actually stored. On one hand, lspasswd is needed to register some accounts passwords - which go into an LSF/EGO file. On the other hand, if you have the Scheduling service registered in the SAS Management Console with an Authorization Domain, you would have a SAS metadata group, and in this group's Account tab, the password of the account used for scheduling (very often lsfadmin or lsfuser).   Please correct me if I am wrong. Of course, there are setups of all flavours, but I find those 2 really often, if not always.   Leaving aside LSF / JS passwords, if you have SSO with Kerberos, and the account used as UPN for the keytab file needs to change the password, you would need to regenerate the keytab file again, else SSO authentications will fail.   If you will change any of the WIP passwords, you will need to update those passwords as well in the server.xml and some AuthDomain groups too - as you would do if any database user (any outbound authentication) would change. ... View more

Hi @PierreDupuisD ,   have you had a chance to look into the documentation: https://documentation.sas.com/doc/en/itopscdc/v_056/calbr/titlepage.htm This is what SAS supports, which has an open side to the kind of infrastructure and services to use, and you could build your own around it. If you have specific questions, feel free to address them! ... View more

Hi @GANESHR ,   thank you very much your reply. I want to say sorry if the "one liner" comment did not sit well. I hear you, and I understand your position. And I hope you understand that comment, it was not intended negatively, just aimed to know more to support you.   But! I am glad the issue is resolved! Feel free to mark your own last post as solution if you see it that way. I hope it will help others in the future. ... View more

Agreed. I would say this is an OS administration issue.   What changes happened? Recent patches/hotfixes? Update of packages (due to security or other reasons)? Has OpenSSL changed in any way?   https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/secref/secrefwhatsnew94.htm   You can share that link with your OS admin team. ... View more

Thanks. However perhaps we need more information. One liners don't help a lot.   An idea to get more information: extend the log information to debug or trace. ... View more

Hi there,   do you have the server and client software at the same hotfixes level? It seems to me as it might be related.   Some side questions: Have you tried the same but from the SMC on the server itself? What SAS Version/Maintenance do you have and over what OS on the server & SMC client? Have you changed anything in the metadata recently, e.g. the Option for Prompt User/Password Yes to No or the other way around? If you have M8, mind the change in encryption management, since M8, SAS relies on the OS setup.       ... View more

Hi there @drahorg ,   indeed, as @ronan said, I also think it is a very interesting question!   First things that come to my mind would be:   1- SAS Enterprise Session Monitor (ESM): which can help you to monitor all SAS sessions, the status, termination status, HW resource consumption, etc. It is pretty neat!    2- Create a wrap of the SAS process (sas.exe/sas.sh): I would not really recommend it, as it would not be a solution supported by SAS. However, from a programmer point of view, it would be the only option that comes to my mind to be able to add/modify features not included by default. Not saying it would be easy, and as I said, I would not recommend it. Plus it would force you to modify the SAS-provided images... again, I would not recommend it.   3- For batch calls, there are ways to put the chain of SAS calls and check termination of code and put code in between. For interactive processes, that would be more challenging.     ... View more

Have you got any progress or updates? Wondering what is the situation over there! ... View more

Hi there, @GANESHR    I think it would have helped if you would have provided more information.  Just from what you provided, it was very confusing. AGP is not related to SAS in the market, unless it is a name provided within your own company, which we do not have a way to know.  That being said, giving more information of your environment, when/how the issue happened, and more log information, can help to provide context and to have something to work with towards a solution.   Just imagine how you would feel if someone would ask you such technical question with a one-liner? Probably you would ask for more information as well....   Leaving that aside, and coming back to your last question: it is not necessarily a false positive, but something resolved either in time, or something only one user experienced. Again, we need more information.   I hope you understand. ... View more

Hi there,   indeed, it would be good to have the screenshot. Tools should be there, else you might have a serious problem. However, for all I see with other questions, is it possible that you are just a bit lost with the changes in the interface from previous SAS EG version.   I highly recommend to have a read to the User's guide for 8.3: https://documentation.sas.com/doc/en/egug/8.3/p1teiflqrhk7qnn16i4d6uburzlx.htm It will greatly help you to have a better grasp of the changes and how to work with the tool.   @ChrisHemedinger  suggestion will basically delete your profile and reset all to default indeed. I would suggest to use it only as last case scenario and when you are sure you do have an issue with SAS EG.     ... View more

Indeed, either a second stored process or a SAS/Connect execution. Anyways, a separate SAS process. ... View more

Hi @Ronein ,   for all I see with your other questions, not only here but in the other posts, you might not be new to SAS EG, but to this version.   I could agree with the other replies, that it would be interesting to receive some training or to look into the SAS EG documentation for the new version. It could reply a lot of your questions very quickly. Or asking a search engine or chatGPT/Claude/Copilot/etc.   For now, quick replies: - STOP: the button just near run, the running man, it is a square. - Libraries & SASWORK: this question I am most surprised, they are where they should be. If you dont find them in the usual location, please provide more details. - Fonts: where? your code/logs? The interface? In any case, https://documentation.sas.com/doc/en/egug/8.3/n0lih7kdsk4rgon137u5m37k23n0.htm    Recommended settings: the ones your company recommends, since it is more about standards than recommendations. ... View more

Hi @Ronein ,   just to add to what @Ksharp indicates and looking at your screenshot:   Try clicking on the "Share" option in your dataset tab. You Should be able to see the option you are missing to send the data to Excel. ... View more

I feel as there is something odd with the configuration of EG or SASWORK, since I have not seen that issue since really long times....   Try this: https://support.sas.com/kb/13/740.html  ... View more