I upgraded our Prognosis on NonStop from 11.4 to 11.5 a year ago.
Today, after I was checking how the security is set on OSS files, I just found out, that on our development system the solution folders is still an old one, so 11.4. On our production servers it is 11.5, as it should be.
/etc/prognosis silci: ll
drwxr-xr-x 1 PROGNOSI.MANAGER PROGNOSI 4096 Jul 19 2018 11.4
I have a two questions:
How can I manually install 11.5 "solutions"?
Why all files within "solutions" are secured in a way, that have a write permission?
An example from our production (v 11.5):
/etc/prognosis/11.5/solutions/infrastructure/nonstop/cpu silci: ll
-rw-rw-rw- 1 SUPER.SUPER SUPER 99670 Oct 14 2018 cpu.defsrec
When upgrading Prognosis, did you run the upgrade process as super or prognosis?
As far as the upgrade process goes, our documentation for the upgrade procedure writes:
"Prognosis uses an OSS folder to store record definitions in folders designated by the product or solution that they are part of. This arrangement makes it easier to deploy solutions delivered by the Integrated Research Consulting Group as well as custom ADI solutions, and will be further utilized in later releases. The base folder needs to be chosen at upgrade time. The default location is /etc/Prognosis/<version_number>/solutions. If it is not possible to use OSS on this system, there is an option to store record definitions in the base Prognosis folder."
It could be that the folder was not specified during the upgrade? I will check for a manual option.
I did a double check on "solutions" folder content (I checked timestamps of directories and files), and it is the same as it is on our production systems. So this is OK, but it is also strange, why upgrade procedure use folder name 11.4 instead of 11.5?
In PRGNINI file the reference is correct, since it is pointing to 11.4 directory (folder) name:
I've checked the installation guide for a reference note but the logic behind creating the directory structure is not explained. What matters is that the directory does match the configured entry and that installed solutions are placed into the defined location.
So, it's good that you have confirmed the directory and configuration are matching.
what about my second question about security:
Why all files within "solutions" are secured in a way, that all have a write permission for all users?