Rocket® OpenQM

Hi group! I have a client that replaced an HP with PCL language to an Epson ET-M3170 GDI (Graphical Device Interface)  printer. Now the new printer is cutting off the heading and truncation reports.  I do recall from many years ago that GDI printers are not recommended.  Fast forward a couple of decades and is that still the case?  Are there any new drivers that can emulate PCL commands to a GDI printer?     This is OpenQM on Windows. Thanks!------------------------------Peter GonzalezProgrammer/Systems Analyst/EDI DeveloperSelf RegisteredSt. Louis MO US------------------------------

Our devops team was  performing a system upgrade from Linux Ubuntu 18.04 to 22.04 late last night.  When they completed the migration, they discovered to their horror that the SystemID had changed.   Not knowing what to do at that hour of the night, they searched for a solution.  They found a link  posted by Martin on the Google Groups: www.openqm.com/emergency.htm   They provided the required information and received the following back: 1. We are concerned that after 7 days pass, this license will expire.  Can someone confirm?2. What is the correct action to take?  Our upgrades are going to take place off-hours, late in the evening.3. Is this expected behavior that an O/S upgrade will change the system ID? Any advice is appreciated.------------------------------Ben Cramer DSI Solutions LLCMansfield TX US------------------------------

We ran into this recently and I thought I'd share. In the legacy/character version of our software, we normally prompt for dates using a two digit year (mm-dd-yy), iconving and oconving as needed.  Recently, a user entered "12-31-33" as a date.  The iconv returned -12418 (12-31-1933) rather than the expected value of 24107 (12-31-2033).  After researching this we discovered that Pick/Rocket and QM both default to dates entered with 2 digit years greater than 30 to be in the 1900's, years less than 30 as assumed to be in the 2000's  Note: iconving a date with a 4 digit year always returns the correct value..  QM does have a config setting that will allow you to override the cutoff, however rather than remembering to change the config setting every few years on every user system, we opted to add code to our legacy system that checks the iconv'ed value and adjusts it as needed.------------------------------Ben CramerOwnerDealer Solutions LLCMansfield TX US------------------------------

We hope you can join us! The only way to learn about all that's to come in 2023 and beyond is by being there! Please note we don't record these roadmap livestreams, so you must tune in live if you want the inside scoop on all things MultiValue. Register now to join the MultiValue product management team as they host a livestream of our Rocket MV product roadmaps: Each Rocket product manager will present on both near-future and distant-future plans for his/her MV products, as well as the many possibilities they're still considering. Participate with us and each other using Slido, an easy-to-use Q&A app, to make the event more interactive. Hear more about eLearning, including our rollout in Q1 Get updates on our MV cloud roadmap, Rocket® UniVerse, Rocket® UniData®, Rocket® D3®, jBASE, OpenQM, AccuTerm, and MultiValue tools including MultiValue Integration Server (MVIS) and our MV Experiences (MVX). We know our roadmaps affect your application and that you must plan internal upgrad

Historically, multi-value environments have been somewhat lax in enforcing use of locks when updating files. The locking system is voluntary and, if applications choose not to use locks, data integrity issues may arise. Two processes performing a read/modify/write update of the same record may overlap with one overwriting the other.There is a simple rule that eliminates this problem. Never write or delete a record without locking it first. This could be a simple update lock that protects the specific record or a file lock that effectively locks all records in the file.It is important to understand the significance of the locking system being voluntary. A badly written program that updates a record without locking it is not affected by the locks set by well written programs that follow the rules.This situation should never have been allowed. Attempting to write or delete a record without a lock should lead to some form of application error, however, such a rule cannot be retrospectively

------------------------------Jill OrsiniInside Sales MVRocket Internal - All Brands------------------------------

------------------------------Jill OrsiniInside Sales MVRocket Internal - All Brands------------------------------