go to post Alexey Maslov · May 24, 2017 Thank you, Jon, you've answered my question.Frankly, I've noticed that CPUPct object still exists in 2017.1.0, but didn't notice that it's no longer being tracked.
go to post Alexey Maslov · May 24, 2017 Thank you, Jon, you answered my question.Frankly, I've noticed that CPUPct object still exists in 2017.1.0, but didn't notice that it's no longer being tracked.
go to post Alexey Maslov · May 19, 2017 Do you think that strange name is from MultiValue stuff?If so, not sure if it's possible to define macros in MultiValue .
go to post Alexey Maslov · May 19, 2017 Routines can't be named as "%zu2f%zt" because only the first letter of routine name can be "%". Maybe such "name" occured due to some encoding, having in mind that $char($zhex("2F"))="/"? If so, the original could look like:$$zt^%zu/%ztIf so, a macro can be defined as:#define YourMacro(%yourparam) $$zt^%zu/%yourparam
go to post Alexey Maslov · May 19, 2017 Looking at the console log I can see the following which I presume implies it is using large pages?Definetely yes.Graham, if you feel that your question is answered please don't hesitate to mark it answered
go to post Alexey Maslov · May 17, 2017 During Cache backup it appears that all the available memory on the server is being used.It's usually not a problem as the more memory is used for buffering the quicker file i/o operates. Only free memory is used for this purpose, so memory allocated by users' or system processes should not be swapped. Please add more details, why it turned to be a problem in your case?PS. Double check in console log whether Cache allocates its shared memory segment using large pages as it guaranties that it is totally allocated at Cache startup and will neither be expanded nor swapped afterwards.
go to post Alexey Maslov · Apr 28, 2017 Question may have more than one right answer.Several answers may add some useful info to each other.Complicated question may even collect several competiting answers. Who will be a judge?
go to post Alexey Maslov · Apr 28, 2017 If you are curious, you may try to do it following John's hint, but if you didn't catch the idea, better do not.
go to post Alexey Maslov · Apr 27, 2017 Raghuram,I wrote my answer before reading yoyr comment. In this very case it seems that it's nothing should be done with GUID.Happy testing!
go to post Alexey Maslov · Apr 27, 2017 While it's easy to change GUID following John's hint (if you understood the code, you already know which global node to kill, and it will be recreated on the next call), I wonder why do you want it? It seems that your instanse have migrated to another host, hense you may want to save all its requisites (including GUID) untouched. This GUID is not used by Cache itself, but may be used in some app data fields, so you may loose app level integrity.PS. If you didn't understand the code, or are cautious to change system globals, you'd better deinstall Cache and re-install it into the same folder. System DBs would be totally rewritten while your app DBs as well as cache.cpf would be left as is.
go to post Alexey Maslov · Apr 26, 2017 Neither MERGE nor ^GBLOCKCOPY move the global: they are only copy it, unless somebody KILL it's old instance after copying.
go to post Alexey Maslov · Apr 25, 2017 John, it seems that inquiring folks rarely accept answers, maybe because of their rare visits to this site.With voting feature (like some sites have) it would be possible to "auto-accept" the most voted answer(s) after some reasonable time, e.g. after two weeks.
go to post Alexey Maslov · Apr 25, 2017 Hi, Richard....to have cache run as a different user to access that macro...Running Caché for Windows using a dedicated user account (so called service account) may have some other advantages:Caché processes get ability to use MS network resources (shared folders), e.g. Caché Backup can be performed directly to remote folder; Kerberos authentication can be used.So long story short just going down the libre office route.Why do you expect that libre office route would be shorter? Do you plan to use another (not $zf(-1,...)) approach?
go to post Alexey Maslov · Apr 24, 2017 Thank you, John, for this reminder, while I prefer to deliberately enable auditing of all events for the simple reason: a few added-on disk IOPS, as well as 1GB+ of disk space for audit database (even on high loaded Caché instances) do not seem to be a great price for an ability to trace not predicted cases in production.We even met a prospect's requirement that any audit database write failure should be dealt as a critical error with a notification of admins by all means, even with shutting the Caché down!
go to post Alexey Maslov · Apr 21, 2017 Sagun, this code would fail with <WRITE> error as after opening the file for reading: ..o resfile:"RSK\CP874\" it tries to write into it: ...w $g(^ztonEDI("TXT","OUT-DATA",ind,fileno,"SEQ",seq))_$c(13),$c(10) What this code needs as the first remedy is a change of the Open command to: ..o resfile:"NWK\CP874\"
go to post Alexey Maslov · Apr 21, 2017 ... and second thing is to insert a Close command before the correspondent Open, e.g. ..c resfile o resfile:"NWK\CP874\" even if you are quite sure that the file is closed at the moment of opening. The reason is to avoid the cases when your program have failed with error without closing the file, so its open parameters (at least, the translation table setting) keep unchanged despite of subsequent Open command. Such cases often happen during development / debugging, when the error trap code is completely switched off or greatly simplified.
go to post Alexey Maslov · Apr 20, 2017 It's better to use stream wrappers instead of open/use directlyJust because of higher abstraction level of streams; nothing special inside: just the same Open/Use/etc COS commands. So, choosing one or another way of working with files can't be the source of errors itself.By the way, `open file:("NWK\table\")` is a proven and documented way of translation table setting. AFAIK, its only limitation is that it works with Open command only rather than with Use command.
go to post Alexey Maslov · Apr 20, 2017 Eduard, can you explain the main difference between Sagun's method of translation table setting: open file:"RSK\CP874\" and yours in this very case? The latter is a piece of code of %Stream.FileCharacter.cls which actually sets a table: If (table'=0) && (i%CurrFile'="") { Set io=$io Use i%CurrFile $$$SETIO(table) ; -> Do $zutil(96,18,2,table) Use io } It seems that it's some other problem, perhaps a bug. Sagun, if you provide us with a small piece of your code where you open the file, use it, and write it, it would be easier to say something.
go to post Alexey Maslov · Apr 19, 2017 Hello Eduard,Following your 1st link I've failed to find any info on 7-zip usage. It was about Libre Office stuff.No problems with 7-zip for Windows (its native OS), not worth to mention that 7z format compression method(s) of its last versions can be unsupported (and uncompressed) with old ones. If using zip format (even with 7-zip), your are quite safe.p7zip, its Linux branch, which I tried several years ago, performed very poor as it was not multi-threaded (as 7-zip was for years). So we decided to drop it mostly for this reason.One little hint about 7-zip for Windows: we use its 7za.exe build in our deployment and update procedures as it doesn't need installation and can be just dropped in any place before usage.
