New post
AllAccepted answers
Robert Cemper · Sep 14, 2023

You can see 2 examples of the adoption of orphaned  OEX packages here:

Besides the pure bug fixes, I applied some other enhancements for comfort

  • pointer to the orphaned predecessor
  • fixed Dockerfile to be version-independent
  • fixed pending mapping of SuperServer
  • added support for IPM
  • added installation guide
  • added quality tag
  • added demo server
  • added screenshots
  • enhanced README

Case #1) https://openexchange.intersystems.com/package/JSONExportManyToMany
GitHub:  https://github.com/rcemper/JSONExport-ManyToMany-AD

Case #2) https://openexchange.intersystems.com/package/Samples-FHIR-Oximeter-Devices
GitHub:  https://github.com/rcemper/Samples-FHIR-Oximeter-Devices-AD

The packages on OEX are still pending for approval and not public yet.

Robert Cemper · Sep 9, 2023

Today I had to process a rather sad exercise. 😢

For about 15 recognized packages in OEX I had to cancel my previous reviews
because the packages were broken. 
They could have been fixéd easily as there were PRs ready.
But for more than 3 months these fixes were just ignored by their owners.

On top of it:
A significant part of them was highly awarded in previous contests

I'm deeply disappointed, as the Quality of Packages in OEX was a personal focus.
However, I have to accept that quality has lost importance also in this
narrow section of my life.

😞

Robert Cemper · Sep 5, 2023
  1. SMP > System Operation > Databases shows the size o your DB   8192 is the default you have to match te blocksize of your backup source
  2. /usr/lib/iris/mgr/ is IRISSYS or the HS equivalent a direct restore may destroy your running installation. restore it in a parallel DB and import only uncritical parts.
  3. in SMP > System Adnin > Config > Sys Config > Local DB  you can set the Blocksize of the DB before creation: Blocksize might be hardwired in Community Distribution 
Robert Cemper · Aug 28, 2023

The "L" in your Open makes me nervous.
From the description, it seems to hang and wait for unlock not In IRIS but at OS-FileSystem Level.
The description of "L" seems to give some chance for such a conflict. 

L   Locked Exclusive: Use this mode with the “W” (Write) mode to specify exclusive write access to a file. “WL” or “WRL” specifies that the current process has exclusive write access to the file. A file opened with “RL” may still have shared read access. The effects of the “L” mode on concurrent opens are different in Windows and UNIX®. Refer to the “OPEN Mode Locking” section, below, for further details. On UNIX® systems if one process specifies “WL” (or “WRL”) access to a file, other processes requesting read access to that file must specify “RL” so that UNIX® can coordinate file locking.

suggested testing:

  • Check the situation without "L"
  • If there is a difference: find out who else may lock at OS level  
Robert Cemper · Aug 26, 2023

Hi @Lorenzo Scalese 
I guess you are looking for class(%Utility).FormatString()

USER>set lb=$lb(1,"Lorenzo",2023,"RCC"_$c(13,10))
USER>write lb
      LorenzoçRCC
 
USER>zzdump lb
0000: 03 04 01 09 01 4C 6F 72 65 6E 7A 6F 04 04 E7 07         .....Lorenzo..ç.
0010: 07 01 52 43 43 0D 0A                                    ..RCC..
;;;;;  this is it
USER>set viewlb=##class(%Utility).FormatString(lb)
 
USER>write viewlb
$lb(1,"Lorenzo",2023,"RCC"_$c(13,10))
USER>zwrite viewlb
viewlb="$lb(1,""Lorenzo"",2023,""RCC""_$c(13,10))"