@SASKiwi :  I also suspected, that the file size of the Foundation folder of the metadata repository could be part of the explanation, but there is only a difference of 2 MB PROD:                                                                         TEST:     ... View more

Thank you! This worked!    I greatly appreciate the help!  ... View more

Hi! This is what is put in sas.service, it's working but I'm sure I need to refine it (Requires, WantedBy)   [Unit] Description=SAS Services Requires=network.target [Service] User=sasinst Group=sas ExecStart=/bin/bash -c '/sas/SAS_lsm/SAS_lsm -c /sas/SAS_lsm/va.cfg -a 1 -e' ExecStop=/bin/bash -c '/sas/SAS_lsm/SAS_lsm -c /sas/SAS_lsm/va.cfg -o 1 -e' RemainAfterExit=Yes [Install] WantedBy=multi-user.target   " RemainAfterExit=Yes " was tricky to find. Had to work a lot with  Any improvements are wellcome! 🙂 ... View more

Thank you, Kurt for your quick and clean answer! ... View more

A SASMACR entry is a compiled macro, which is created when the macro code (from %MACRO to %MEND) is executed. It is not the raw macro code! ... View more

@ChrisHemedinger :  Thank you, Chris, for your reply. I already opened a Case with Tech Support. Basically, they told me the same thing as you did: it is work in progress. Let's hope, they can come up with the new versions of libgit* as soon as possible. I'll keep you posted!   Thank's, FK21 ... View more

@FK21 wrote: Hi @DavidGhan , thank you for your remarks. I did properly set up the metadata rights, meaning: only those who are eligible, i.e. allowed to modify meta data via DIS can do so (let's call this group "developers"). However, what I am looking for is a way/method, that developers also do not have the means/possibility to alter/delete/update any metadata object, if the did not check it out in the first place, even though they are generally allowed to modify metadata objects. This, so it seems to me, is not realizable with DIS or metadata granting schemes, respectively.   I think you and I both misread David's response the same way.  If you read it again, you'll see that your Developers group should NOT have writemetadata permission to these objects.  The lack of writemetadata permission is what forces them to check out an object before editing it, presumably.  ... View more