Today, version 3.0 of the SAS_lsm utility provides consistent management of single or multi-tiered SAS-related services for UNIX/Linux deployments from a single shell script. Consistent management includes tier dependency checking, starting, stopping, status checking (tier- and deployment-based), error log collection, analysis, and potential resolution recommendations. See blogpost The SAS_lsm Utility Makes it Easy to Control SAS Servers in a Multi-Tier UNIX/Linux Deployment for additional detail.
We are now in the process of defining potential version 4.0 line items. Currently under consideration:
Feel free to reach out here if you have any additional functionality that you would like to have considered for version 4.0 and/or if you have feedback on the items currently being considered.
Thanks a lot for asking !
I'd like having SAS_lsm next version being able, selectively (y/n=Default) perhaps, to
the old log files generated by the services (servers) to be stopped,
This being done conditionally with a retention policy of,say, 30 days by default.
The zip archive naming rule could be based upon the Server own folder name (grand-parent folder),
though sometimes it must be adjusted in the case of MidTier specific folder hierarchies, sometimes deeper.
The variable suffix could be based upon ISO 8601 date format - completed by any random number if necessary.
2019-04-16 if daily
2019W16 (if weekly : Week 16 of 2019)
2019-04 (if monthly)
In addition to that, maybe also having meaningful Return Codes after the completion, like
RC_LSM=2 (SSH Error)
This would be useful to pass on to the launcher tool (usually a scheduler, I suppose).
Absolutely number 1 for us is Windows support. All our SAS infrastructure runs on Windows Server so we can't use SAS_lsm and have to resort to custom shell scripting done by IT administrators not familiar with SAS. As a result our server starting and stopping procedures are not as robust and reliable as they could and should be. It would be great to have the same automation capability under Windows that is already available for Unix.
Thanks for your patience. We are still working through the backlog:
... and not yet ready to release. Will keep everyone posted via this thread.
Hi Cliff / @clmeye ,
thanks for your reply. I was hoping to see some more items than in the initial post of a year ago, perhaps some inclusions of what has been asked for input and discussed in this thread!
Will definitely keep attention to this thread.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.
Find more tutorials on the SAS Users YouTube channel.