Skip to main content

2024 October FeatureLog

View the various changes made to the FairCom documentation in the month of October

Description

Users can automate Replication Manager operations by creating JSON input files and sending them to the replutil command-line utility. Otherwise, these operations must be individually executed through the Replication Manager UI or through direct calls to the Replication HTTP API.

Documents updatedInitial products and versions
  • FairCom DB 13.0.0

  • FairCom Edge 4.0.0

  • FairCom MQ 4..0.0

  • FairCom RTG COBOL 4.0.0

  • FairCom RTG Btrieve 4.0.0

Audience

Users , Developers , and Administrators

Source references

D404

New replication CLI utility

replicationCLIutility
Description

You can run certinfo against a PKCS12 (.12) file to show the primary key, the primary certificate, and any additional certificates.

Documents updatedInitial products and versions
  • FairCom DB 13.0.1

  • FairCom Edge 4.2.1

  • FairCom MQ 4.2.1

  • FairCom RTG COBOL 4.2.1

  • FairCom RTG Btrieve 4.2.1

Audience

Administrators

Source references

D1257

You can run certinfo against a PKCS12 (.12) file to show the primary key, the primary certificate, and any additional certificates

certinfocertinfo.pyPKCS12primary keyprimary certificate
Description

The documentation now includes use cases for using replication for high availability, disaster recovery, and scalability.

Documents updatedInitial products and versions
  • FairCom DB 13.0.1

  • FairCom Edge 4.2.1

  • FairCom MQ 4.2.1

  • FairCom RTG COBOL 4.2.1

  • FairCom RTG Btrieve 4.2.1

Audience

Developers and Administrators

Source references

D1411

use cases for using replication for high availability, disaster recovery, and scalability

replicationuse caseshigh availabilitydisaster recoveryscalability
Description

FairCom enables applications to authorize JSON actions without the need for a username/password or client certificate using the permanentSession property. While it is slightly less secure, it allows many servers to use the same authToken (API key) to simplify session management.

Documents updatedInitial products and versions
  • FairCom DB 13.0.1

  • FairCom Edge 4.2.1

  • FairCom MQ 4.2.1

  • FairCom RTG COBOL 4.2.1

  • FairCom RTG Btrieve 4.2.1

Audience

Administrators

Source references

D1435 and D1454

persistent sessions permanentSession property

persistent sessionpermanent sessionpermanentSessionsession and services
Description

You can now reduce the variability in performance of a client application by setting the maximum number of spin operations that a shared memory connection can use.

Documents updatedInitial products and versions
  • FairCom DB 13.0.1

  • FairCom Edge 4.2.1

  • FairCom MQ 4.2.1

  • FairCom RTG COBOL 4.2.1

  • FairCom RTG Btrieve 4.2.1

Audience

Administrators

Source references

D1302

use SHMEM_MAX_SPIN and ctSetCommProtocolOption to control the number of spin operations that a shared memory connection can use

SHMEM_MAX_SPINctSetCommProtocolOptionmemoryspin operation
Description

The new variantFormat property allows you to specify the format in which variant fields are returned from JSON DB API "getRecords..." actions so that you can set the data format returned from a variant, such as hexadecimal, Base64, UTF-8, and the variant JSON object.

Documents updatedInitial products and versions
  • FairCom DB 13.0.1

  • FairCom Edge 4.2.1

  • FairCom MQ 4.2.1

  • FairCom RTG COBOL 4.2.1

  • FairCom RTG Btrieve 4.2.1

Audience

Developers and Administrators

Source references

D1437

variantFormat property get records actions

variantFormatgetRecordsvariant formatvariant fieldshexadecimalBase64UTF-8
Description

The new "authenticationMethods" property allows you to control which methods MQTT clients are allowed to use to authenticate. For example, you can limit client authentication to any combination of client certificate and/or username/password.

Documents updatedInitial products and versions
  • FairCom DB 13.0.1

  • FairCom Edge 4.2.1

  • FairCom MQ 4.2.1

  • FairCom RTG COBOL 4.2.1

  • FairCom RTG Btrieve 4.2.1

Audience

Developers Administrators

Source references

D1166

Improved MQTT communication security

MQTTsecuritycommunicationMQTT communicationsMQTT security
DB_FIPS_Ready.svg
Description

Faircom now supports FIPS 140.2 through OpenSSL 3.0 to ensure secure communications. FIPS 140.2 is an encryption standard established by the US federal government for verifying the implementation of OpenSSL.

Documents updatedInitial products and versions
  • FairCom DB 13.0.1

  • FairCom Edge 4.2.1

  • FairCom MQ 4.2.1

  • FairCom RTG COBOL 4.2.1

  • FairCom RTG Btrieve 4.2.1

Audience

Developers Administrators

Source references

D586

FIPS validation for secure communications

FIPSFIPS supportOpenSSLFIPS validationsecure communications
DB_FIPS_Ready.svg
Description

This feature migrates previously encrypted files into FIPS-140.2 format for enhanced security, compatibility and functionality.

Documents updatedInitial products and versions
  • FairCom DB 13.0.1

  • FairCom Edge 4.2.1

  • FairCom MQ 4.2.1

  • FairCom RTG COBOL 4.2.1

  • FairCom RTG Btrieve 4.2.1

Audience

Developers Administrators

Source references

D586

Enable FIPS validation of encrypted files

FIPSFIPS migrationOpenSSL
Description

This feature provides enhanced transaction log diagnostics capability when enabled using the CHECK_TRNLOG_BUFFER_WRITES configuration option. The DIAGNOSTICS TRNLOG_WRITES option writes transaction log entries that report when bytes are being skipped and when the transaction type is invalid.

Documents updatedInitial products and versions
  • FairCom DB 13.0.1

  • FairCom Edge 4.2.1

  • FairCom MQ 4.2.1

  • FairCom RTG COBOL 4.2.1

  • FairCom RTG Btrieve 4.2.1

Audience

Developers Administrators

Source references

D1433

Improved transaction log diagnostics using new configuration options

configuration optionstransaction logdiagnostics
Description

Quickly recover from a Pacemaker cluster failure state with our new tutorial on how to recover from cluster failure states with replication.

Documents updatedInitial products and versions
  • FairCom DB 13.0.1

  • FairCom Edge 4.2.1

  • FairCom MQ 4.2.1

  • FairCom RTG COBOL 4.2.1

  • FairCom RTG Btrieve 4.2.1

Audience

Administrators

Source references

D1456

Tutorial Pacemaker failover when using replication

TutorialPacemakerfailoverreplicationrecoveryrecover from a pacemaker cluster failure state
Description

You can now specify that DB Notify messages contain a whole record buffer instead of individual fields. This allows you to track changes to files that do not have field definitions or table names. Additionally, you can now use a pathname to specify non-SQL files that you want to track.

Documents updatedInitial products and versions
  • FairCom DB 13.0.1

  • FairCom Edge 4.2.1

  • FairCom MQ 4.2.1

  • FairCom RTG COBOL 4.2.1

  • FairCom RTG Btrieve 4.2.1

Audience

Developers

Source references

D1427 D1464

DB Notify ISAM records without fields and non-SQL data files

non-SQLISAMDB Notifybuffers
Description

You can use JavaScript to transform the output of all JSON DB "getRecords..." actions. You can add fields, change field values, and calculate aggregate values like min, max, and average.

Documents updatedInitial products and versions
  • FairCom DB 13.0.1

  • FairCom Edge 4.2.1

  • FairCom MQ 4.2.1

  • FairCom RTG COBOL 4.2.1

  • FairCom RTG Btrieve 4.2.1

Audience

Administrators

Source references

D1500

Transform outputs of "getRecords" actions

Transformcode packagegetRecordsjavascriptoutputJSON DBjsonAction