Power archiver 9.6X serial key or number

Product life cycle dates

Program number

• IBM i V7.4 (5770-SS1)
• IBM i Per Processor Billing V7.1 (5770-SSA)
• IBM i Application Server Billing V7.1 (5770-SSB)
• IBM i Per User Billing V7.1 (5770-SSC)
• IBM i operating system Value Pack (5722-IVP)
• DB2 Value Pack for i (5722-DVP)
• Operations Value Pack for i (5722-SVP)

Additional products

The following products are shipped with IBM i operating system (5770-SS1):

• IBM HTTP Server for i (5770-DG1)
• IBM Developer Kit for Java (5770-JV1)
• IBM Network Authentication Enablement for i (5770-NAE)
• IBM Portable Utilities for i (5733-SC1)
• IBM TC/IP Connectivity Utilities for i (5770-TC1)
• IBM Transform Services for i (5770-TS1)
• IBM Universal Manageability Enablement for i (5770-UME)
• IBM i Open Source Solutions (5733-OPS)
• Zend Server Community Edition for i (5639-ZC1)
• IBM i Access Client Solutions (5733-XJ1) *
• IBM i Access for Windows (5770-XE1) *
• IBM i Access for Web (5770-XH2) *

Abstract

IBM i 7.4

IBM i 7.4 updates span the entire breadth of the portfolio from the base operating system, Db2 for i, and application development through to availability. As always, the new functions are delivered while retaining the industry-leading securability features for which IBM i is known. In response to many user requests, updates and additions have been made to many other parts of the IBM i Portfolio.

The new enhancements and additions in IBM i 7.4 provide a strong foundation for the ongoing innovation being done by IBM i clients. Around the world, clients are extending IBM business applications to include technology such as AI and the Internet of Things. Many of these enhancements will support this continuous innovation.

IBM i 7.3

IBM i runs on Power Systems servers or on PurePower servers and offers a highly scalable and virus-resistant architecture with a proven reputation for exceptional business resiliency. Companies that run applications on IBM i running on a Power server are able to focus on innovation and delivering new value to their business, not on managing their data centre operations.

IBM i integrates a trusted combination of a DB2 relational database, industry-leading security, standards-based Internet technology, networking, and storage management capabilities. For example, IBM installs and integrates the SQL standards-based DB2 database for IBM i with advanced database management utilities, plus additional middleware components such as multiple file system options, directory capability, an HTTP web server powered by Apache, a web application server, and a web-services environment.

IBM develops, fully tests, and preloads these core middleware components of IBM i together. The preintegration and testing of IBM i is a key factor in enabling companies to realize lower operations costs by deploying applications faster and maintaining them with fewer staff.

Virtualization and workload management are also built into the i operating environment to enable businesses to consolidate and run multiple applications and components together on the same system, driving up system utilization and delivering a better return on IT investments. This broad and highly stable database and middleware foundation is ideal for efficiently deploying business processing applications.

Architecture for simplicity, stability, and security

Another key differentiator for IBM i is the underlying architecture of the operating system, which provides for simplicity, stability, and security. These are not add-on features, but inherent aspects of the operating system. For detailed information regarding the advantages of IBM i running on Power servers, see the "IBM i Strategy and Whitepaper," which is available from your IBM representative. This section describes a few examples.

Simplicity

As mentioned above, the relational database in IBM i is an integrated component, and it is built on integrated storage management capabilities unique to IBM i and its predecessors. This storage management is based on the "single-level storage" architecture that treats all of the storage managed by i as if it were one long stream of memory that encompasses the system memory and the storage on disks. This architecture makes it critical that the operating system decide where to store any given piece of data, and that, in turn, removes the necessity of the user to manage data placement. This makes management of storage and the database objects contained in that storage, significantly simpler.

Stability

IBM i also architecturally separates the address spaces of user applications and the operating system so it is difficult for poorly written or malicious software to intrude upon the underlying operating system support. This is one of several attributes that can help keep IBM i running for days, weeks, or months without unexpected restarting of the operating system.

Several architectural attributes of IBM i contribute to the stability of the system over the years. First, applications compiled on i are compiled to a set of intermediate code instructions defined as the TIMI. This allows i to fundamentally change the implementation of underlying hardware, firmware, and virtualization features, without requiring rewriting, changing, or even recompiling the applications written by users. This sort of forward compatibility is a tremendous business advantage and has allowed the movement of software developed and compiled several years to even decades previously to run on later generations of i.

Security

IBM i and its predecessors have an object-based architecture. Each entity on the system is an object, which has a set of prescribed operations that can be performed on it, and connections from the object to those other objects that are allowed to perform various operations. An object that does not have a legal "edit" operation cannot be edited. It cannot be renamed to another kind of object. If the object does have an "edit" operation (known as "change" for most objects), only a defined set of attributes can be edited, and then only by users who have authority to do that editing.

Objects can easily be "hidden" from other users by use of the library list objects, secured by the object-based security associated with all objects. And users who all have a similar role on the system can be grouped together for role-based security, again as part of the base architecture of the system.

While the i operating system supports open programming methods such as Java, PHP, web services, and so on, the underlying architecture provides a level of integration, stability, simplicity, and security that is a significant differentiator, and these aspects provide excellent business value to its users.

IBM i Enhancements announced:

IBM i 7.3 Technology Refresh 6 brings several enhancements to the IBM i Portfolio, including the base OS, selected Licensed Program Products (LPPs), hardware, and firmware. Some of the highlights are:

• IBM Db2 for i improves the functionality and performance of SQL and adds new function for database engineers.
• Application developers will see enhancements to RPG, Node.JS, and Python, and the addition of new tools and the R language.
• Rest APIs have been extended to now allow SQL to be called directly using the HTTP connection.
• In the IBM i Portfolio, many of the LPPs such as IBM Backup, Recovery and Media Services for i (BRMS), IBM PowerHA SystemMirror for i, and Administration Runtime Expert have had significant function added.
• Users of the desktop tools for application development, IBM Rational Developer for i (RDi),system management, and IBM i Access Client Solutions (ACS), will enjoy significant new functionality.
• New fast start with the new IBM Db2 Web Query for i EZ-Install package.
• ARCAD Observer for IBM i and ARCAD Converter for IBM i have been refreshed for traditional developers.
• Many additional features in the IBM i Portfolio have been updated.

IBM i Enhancements announced:

IBM i, the integrated operating environment that runs on IBM Power Systems with a reputation for robust architecture, exceptional security, and business resilience, is enhanced. IBM i 7.4 Technology Refresh (TR) 2 for the IBM i portfolio of products offers clients significant new features and enhancements across many of the components, such as:

• Improvements to the base operating system
  • The Integrated Web Service (IWS) server has improved status and error reporting across the HTTP interface and provides better controls for passing variables across the connection.
  • IBM Navigator for i has improved performance charting capabilities and supports the new industry-standard Transport Layer Security (TLS) Protocol Version 1.3 (TLSv1.3) encryption.
  • The clustering environments inside IBM i and used by products such as IBM PowerHA SystemMirror for i are enhanced.
  • IBM i Services, the SQL alternative to APIs and CL commands, continue to be a focal point for enhancements, providing enhanced productivity and insight to all IBM i users.
  • IBM Db2 for i, the integrated database for IBM i, known for containing the attributes valued by business computing solutions, includes new and improved SQL capabilities.
• Updates to IBM i Licensed Program Products (LPP) portfolio
  • IBM Db2 Mirror for i adds support for internal storage devices and improvement in the application analysis tool.
  • IBM PowerHA SystemMirror for i brings a new set of enhancements centred around security, integration, and usability that simplifies the management of high availability environments.
  • IBM Backup, Recovery and Media Services for i (BRMS) adds new functionality to many components, based on user requests.
  • IBM Administration Runtime Expert for i (ARE) is enhanced to provide a solution to maintain, distribute, and apply program temporary fixes (PTFs) to multiple IBM i partitions with diverse PTF apply requirements.
  • The HTTP server for IBM i is enhanced to support the latest levels of security and encryption.
  • IBM i Access Client Solutions (ACS) support is updated based on direct feedback from the user community.
  • Several new features are added to the RPG language of IBM Rational Development Studio for i (RDS) to enhance its appeal to modern programmers.
  • IBM Rational Developer for i (RDi) has enhanced features and usability, including significant improvements to refactoring and modernizing code.
• Updates to open source
  • Changes to the delivery set in the RPM ecosystem offer increased leverage of the latest security capabilities for storing or transferring data.
  • The new jq command makes it easy to consume and manipulate JSON data from the command line.
  • Python ecosystem improvements make it easier to integrate with Db2 for i.
• Enhancements related to IBM hardware and firmware
  • IBM i tape library virtualization allows automated sharing of SAS-attached and FC-attached tape library devices without requiring multiple adapters, a SAN switch, or a VIOS partition.
  • Hybrid network virtualization enables optimised performance in virtualized network configurations across LPARs, while still supporting Live Partition Mobility. (LPM)

IBM i Enhancements announced:

IBM i, the integrated operating environment that runs on IBM Power Systems with a reputation for robust architecture, exceptional security, and business resilience, is enhanced. IBM i 7.3 Technology Refresh 8 for the IBM i portfolio of products offers clients significant new features and enhancements across many of the components, such as:

• Improvements to the base operating system
  • The Integrated Web Service (IWS) server has improved status and error reporting across the HTTP interface and provides better controls for passing variables across the connection.
  • IBM i System TLS inow supports the new industry-standard Transport Layer Security (TLS) Protocol Version 1.3 (TLSv1.3) protocol.
  • IBM Navigator for i has improved performance charting capabilities and supports TLS v1.3 encryption.
  • The Digital Certificate Manager (DCM) has added a new GUI that simplifies and improves certificate management on IBM i.
  • IBM i Services, the SQL alternative to APIs and CL commands, continue to be a focal point for enhancements, providing enhanced productivity and insight to all IBM i users.
  • IBM Db2 for i, the integrated database for IBM i, known for containing the attributes valued by business computing solutions, includes new and improved SQL capabilities.
• Updates to IBM i Licensed Program Products (LPP) portfolio
  • IBM PowerHA SystemMirror for i brings a new set of enhancements centred around security, integration, and usability that simplifies the management of high availability environments.
  • IBM Backup, Recovery and Media Services for i (BRMS) adds new functionality to many components, based on user requests.
  • IBM Administration Runtime Expert for i (ARE) is enhanced to provide a solution to maintain, distribute, and apply program temporary fixes (PTFs) to multiple IBM i partitions with diverse PTF apply requirements.
  • The HTTP server for IBM i is enhanced to support the latest levels of security and encryption.
  • IBM i Access Client Solutions (ACS) support is updated based on direct feedback from the user community.
  • Several new features are added to the RPG language of IBM Rational Development Studio for i (RDS) to enhance its appeal to modern programmers.
  • IBM Rational Developer for i (RDi) has enhanced features and usability, including significant improvements to refactoring and modernizing code.
• Updates to open source
  • Changes to the delivery set in the RPM ecosystem offer increased leverage of the latest security capabilities for storing or transferring data.
  • The new jq command makes it easy to consume and manipulate JSON data from the command line.
  • Python ecosystem improvements make it easier to integrate with Db2 for i.
• Enhancements related to IBM hardware and firmware
  • IBM i tape library virtualization enables automated sharing of SAS-attached tape library devices and Fibre Channel-attached tape library devices without requiring multiple adapters, a SAN switch, or a VIOS partition.
  • Hybrid network virtualization allows optimised performance in virtualized network configurations across LPARs, while still supporting Live Partition Mobility (LPM).

Highlights

IBM i 7.4

IBM i 7.4 brings a wealth of enhancements to all areas of the IBM i Portfolio, including the base OS, selected Licensed Program Products (LPPs), hardware, and firmware. Some of the highlights are:

• Security enhancements include expanding the set of rules for SST user ID passwords, automating certificate management using DCM APIs, and extending Authority Collection to collect information for specific objects.
• Work Management has been enhanced with updates to workload groups, adding exit points to Job Queue job tracking, and adding new capabilities to retrieving Processor Multitasking information.
• Networking enhancements have been updated to include the latest industry standards for TLS, SNMPv3, SMB3, and SMTP.
• Clients interested in upgrading their availability environments will be interested in the enhancements for save and restore operations, and clustering.
• In this release, IBM Db2 for i is focused on improving the functionality and performance of SQL as well as adding new function for database engineers.
• Application developers in both traditional environments and open source will see enhancements to RPG IV, COBOL, the System Debugger, Node.JS, and Python, and the addition of new tools and the R language.
• Rest APIs have been extended to now allow SQL to be called directly using the HTTP connection.
• A new LPP, IBM Db2 Mirror for i, provides near-continuous availability.
• In the IBM i Portfolio, many of the LPPs such as IBM Backup, Recovery and Media Services for i (BRMS), IBM PowerHA SystemMirror for i, and Administration Runtime Expert have had significant function added.
• Users of the desktop tools for application development, IBM Rational Developer for i (RDi), system management, and IBM i Access Client Solutions (ACS), will enjoy significant new functionality.
• New fast start with the new IBM Db2 Web Query for i EZ-Install package.
• ARCAD Observer for IBM i and ARCAD Converter for IBM i have been refreshed for traditional developers.
• IBM Content Manager OnDemand for i 7.4 supports backing up to the cloud using Cloud Storage Solutions for i and provides enhancements to several commands.
• As with every release, many other enhancements have been made, driven by user requests.

IBM i 7.3

Adds functions and features to almost all components of the operating system and to many of the associated products from IBM Power Software and IBM Software. Additionally, new hardware I/O components are supported with the 7.3 release.

• DB2 for i now includes the long-awaited, highly requested temporal support and enhanced OLAP function. These new capabilities help you perform more advanced analytics on your data, to plan and forecast, to define gaps, and to build new strategies for business.
• IBM i 7.3 adds a new Security Authority Collection that tracks how applications and application users use an object. Inquiries against that collection provide advice on securing critical business data and applications from intrusion by identifying who needs to have access to data and in what context. This major enhancement to security management, unique to IBM i, was driven by client requests for better insight and management to secure their systems.
• IBM PowerHA SystemMirror for i 7.2 HyperSwap Cluster allows you to significantly reduce both planned and unplanned downtime.
• As with previous releases, IBM i 7.3 continues to extend both the traditional application development environment with new features and functions in RPG IV, but is also extending the open source environments that are available by adding Git and Orion. These environments give you more choices for selecting business solutions for your business challenges.
• The latest version of the popular data analytics tool IBM DB2 Web Query for i V2.2.0 has improved ease of use and numerous enhancements, providing richer environments for report development, data access, and output capabilities.
• As with each IBM i release, many other enhancements support client requirements, industry standards, and the latest technologies.

IBM i 7.1

• DB2 for i enhancements including XML support and enablement of column-level encryption
• IBM i storage management enhancements for automatic data placement for Solid State Drives (SSDs)
• IBM i virtual partition enhancements via IBM i and PowerVM VIOS
• Enhancements to Web application serving technologies including Apache, Java, Integrated Web Application Server, Integrated Web Services Server, and Zend PHP environment
• Enhancements to Systems Director Navigator for i for management of IBM i
• IBM i integration with BladeCenter and System x via iSCSI technology enhancements with support for software target support

Description

IBM i 7.4

IBM i Operating System

IBM i 7.4 includes many enhancements and additions to the base operating system, including increased usability, security, and availability. For easier reference and understanding, these enhancements and additions have been grouped into the following operating system categories:

• Security
• System management
• Networking
• Availability
• Application development
• Miscellaneous

Security

Service tools enhancements

In response to many requests to provide consistency across IBM i, the service tools security options now support service tools user ID password composition rules similar to those allowed for operating system user profile passwords. The following password composition rules can be configured for service tools user IDs:

• Limit profile name
• Hours to block password change
• Minimum password length
• Maximum password length
• Use chars from three groups
• Limit adjacent characters
• Limit repeating characters
• Limit characters same position
• Minimum digits
• Maximum digits
• Limit adjacent digits
• Limit digit first position
• Limit digit last position
• Minimum letters
• Maximum letters
• Limit adjacent letters
• Limit letter first position
• Limit letter last position
• Number of mixed case letters
• Minimum special characters
• Maximum special characters
• Limit adjacent special characters
• Limit special character first position
• Limit special character last position

Service tools password composition rules can be configured using DST, SST, or the new SST Security Attribute commands:

• Change SST Security Attributes (CHGSSTSECA)
• Display SST Security Attributes (DSPSSTSECA)

In addition to password rule attributes, the commands support the "service tools password level" attribute and the "allow security- related system values to be changed" attribute.

New commands were added for service tools user ID management. These commands configure the same SST privileges managed through DST or SST:

• Create Service Tools User ID (CRTSSTUSR)
• Change Service Tools User ID (CHGSSTUSR)
• Delete Service Tools User ID (DLTSSTUSR)

For more information, see the Service Tools topic in IBM Knowledge Center.

Digital Certificate Manager

Digital Certificate Manager (DCM) APIs have been added to automate the management of certificates. An application that is written using one or more of these new APIs can renew a certificate residing in the system certificate store, update an application identifier to use the renewed certificate, and update the trust list with the Certificate Authority (CA) that issued the renewed certificate.

An Application Definition, also known as Application ID, is created and maintained in DCM for use by System TLS based applications. These three APIs provide Application Definition certificate assignment capabilities:

• Remove a certificate assignment from an application (QycdRemoveCertUsage).
• Add a certificate assignment to an application (QycdUpdateCertUsage).
• Retrieve information about the certificate currently assigned to an application (QycdRetrieveCertUsageInfo).

A Certificate Authority (CA) Trust List is an optional configuration for Application Definitions. The list allows individual applications to trust a different set of CAs from other applications. These three APIs provide CA Trust List configuration capabilities:

• Add a CA certificate to the CA certificate trust list (QycdAddCACertTrust).
• Remove a CA certificate from the CA certificate trust list (QycdRemoveCACertTrust).
• Check if CA certificate is in the CA certificate trust list (QycdCheckCACertTrust).

This API is used in a two-step process to renew an existing certificate residing in the system certificate store:

• Request a certificate renewal and import certificate into system store (QycdRenewCertificate).

With the first call, a CSR (Certificate Signing Request) is generated based on an existing certificate. After out-of-band processing of the CSR is complete, the second call imports the issued certificate into the system certificate store.

For more information, see the Digital Certificate Management APIs in IBM Knowledge Center.

IBM i Authority Collection

Authority Collection captures data that is associated with the runtime authority checking that is built into IBM i. This data is logged to a repository, and interfaces are available to display and analyze the data. A security administrator or application provider can analyze the captured data to determine the minimum authority that is required to the objects to allow the application to run successfully. Setting a minimum authority on the objects improves the security and provides more protection against possible access from outside the application.

Additionally, IBM i 7.4 Authority Collection support now allows the collection of authority information for specific objects when accessed by any user. Previously, the IBM i 7.3 version collected authority information for all objects accessed by a specific user.

New command:

• Change Authority Collection (CHGAUTCOL)

Updated interfaces:

• Start Authority Collection (STRAUTCOL).
• End Authority Collection (ENDAUTCOL).
• Delete Authority Collection (DLTAUTCOL).
• Display Security Attributes (DSPSECA) command and Retrieve Security Attributes (QSYRTVSA) API show if an Authority collection for objects is active.
• Interfaces that show object attributes now include the authority collection value for the object.

The Authority Collection value for an object can be set with the new Change Authority Collection (CHGAUTCOL) command. When Authority Collection for objects is started using the enhanced Start Authority Collection (STRAUTCOL) command, authority information is collected for the specific objects that have this value set. Any user access of these objects is then collected and written to the authority collection repository for objects.

New SQL views have been added to display and analyze the authority collection data for objects:

• QSYS2.AUTHORITY_COLLECTION_OBJECT view - for QSYS objects; use this when the number of entries in the authority collection is large and you are looking for a specific object or objects in a specific library.
• QSYS2.AUTHORITY_COLLECTION_LIBRARIES view - for QSYS objects; use this when the number of entries in the authority collection is small or you are looking for all, or most, objects in the authority collection.
• QSYS2.AUTHORITY_COLLECTION_FSOBJ view - for file system objects in the "root" (/), QOpenSys, and user-defined file systems
• QSYS2.AUTHORITY_COLLECTION_DLO view - for document and folder objects

For complete details on the enhanced authority collection support, see the Authority Collection section of the Security reference topic in IBM Knowledge Center.

System management

Workload groups

Workload groups, introduced in 2011, allow the isolation of specific workloads into a limited processing environment. Until now, workload groups were set at the subsystem level only, and every job in a subsystem ran in the same workload group. In IBM i 7.4, workload groups can now be configured by job description using the new WLCGRP parameter on Create Job Description (CRTJOBD) or Change Job Description (CHGJOBD) commands. Jobs can run in different workload groups within the same subsystem by setting a workload group name on the job description.

The workload group (WLCGRP) name can be viewed for a job description using the Display Job Description (DSPJOBD) command or the Retrieve Job Description (QWDRJOBD) API. If a workload group name has not been explicitly set in the job description, it will default to *SBSD, which means that jobs started with the job description will use the workload group defined in the subsystem description.

It is possible to change the workload group (WLCGRP) in the JOBD while the subsystem is active. New jobs will be able to use the new workload group without restarting the subsystem.

Processor Multitasking Information

In previous releases, the Retrieve Processor Multitasking Information (QWCRTVPR) API has been used to retrieve the maximum number of secondary hardware threads per processor. With IBM i 7.4, the Retrieve Processor Multitasking Information (QWCRTVPR) API now returns the current and maximum number of secondary hardware threads, in addition to the configured number of secondary hardware threads, per processor.

The Change Processor Multitasking Information (QWCCHGPR) API can be used to limit the number of processing threads on systems that are using simultaneous multithreading (QPRCMLTTSK system value). In previous releases, the QWCRTVPR API returned only the value set by the QWCCHGPR API with no way to determine the actual value used by the system or the maximum value supported by the hardware.

In IBM i 7.4, QWCRTVPR introduces two new parameters that can be used to retrieve the number of secondary threads that are currently active, as well as the maximum number of secondary hardware threads per processor that can be supported.

Managing / tracking jobs on a job queue

In response to user requests, two new exit points have been created to better track and manage jobs submitted to a job queue:

• The Submit Job exit point (QIBM_QWT_SBMJOB) can be used to call a user exit program in a job that calls the SBMJOB command, prior to the job being placed on the job queue.
• The Change Job exit point (QIBM_QWT_CHGJOB) can be used to call a user exit program when the CHGJOB command or API is called to change a job while the job is on a job queue. This allows the program to keep track of any changes made to the JOBQ job after it was submitted but before it becomes active.

These new exit points, along with the existing Job Notification exit point, can be used to keep track of the information needed to resubmit jobs to a JOBQ.

QHST job

The new system job QHST is started at IPL to perform message logging to the history log. This function was previously done by the SCPF job. This change has been made to move message logging out of the critical system job, which requires an IPL to restart it. In IBM i 7.4, this function runs in QHST, which is a separate job. If excessive messaging to the history log causes the QHST job to end unexpectedly, a new QHST job will automatically start and replace it.

Improved searching with DSPLOG command

Improved search capabilities have been added to the Display Log (DSPLOG) command when searching for messages in the history log by job name. The command now allows searching for messages by user name instead of requiring the three-part job name. The command also allows searching by job name or number, as well as generic support for the name.

The IBM i service qsys2.history_log_info provides a powerful way to understand the data in the history log by leveraging the power of SQL to sort, filter, and analyze the history data in ways the command is not capable. Examples of parsing this data can be found under 'Insert from Examples' in the Run SQL Scripts interface of Access Client Solutions.

Networking

TLSv1.3

Transport Layer Security (TLS) is an encryption method that is used to encrypt a communication channel between two systems. In this release, the latest in TLS standards are being implemented to ensure security of critical applications and data.

With IBM i 7.4, IBM i System TLS has been enhanced to support the latest industry standard of Transport Layer Security version 1.3 (TLSv1.3) protocol. TLSv1.3 is enabled and used by default for partitions with system value QSSLPCL set to *OPSYS. Applications designed to use the System TLS default protocols will immediately support TLSv1.3 if the system value settings allow TLSv1.3. Other applications may require configuration or code changes to enable TLSv1.3.

See the Transport Layer Security topic in IBM Knowledge Center for additional details.

To make working with TLS easier, IBM i 7.4 is providing a new Retrieve TLS Attributes (QsoRtvTLSA) API, allowing the retrieval of the system-wide System TLS current default properties. The properties can be changed and viewed with TLSCONFIG. The benefit of QsoRtvTLSA is that it can be included in programs or scripts for health check actions. See the QsoRtvTLSA topic in IBM Knowledge Center for more details on its use.

SNMPv3

The IBM i support for Simple Network Management Protocol version 3 (SNMPv3) has been enhanced with the ability to securely send SNMPv3 Trap and Inform messages. The IBM i local trap manager has been enhanced with the ability to securely receive and forward SNMPv3 Trap and Inform messages. Additionally, traps generated by third-party sub-agents can be sent as SNMPv3 Traps or Informs without any changes to the sub-agent code. See the Change SNMP Attributes (CHGSNMPA) topic in IBM Knowledge Center for additional information.

Server Message Block Version 3 (SMB3)

The IBM i QNTC file system and IBM i NetServer file system allow connectivity and sharing with clients on the network. In IBM i 7.4, both NetServer and QNTC have been upgraded to the latest industry standard for connectivity, SMB3. This new level includes many new features, such as:

• End-to-end data encryption for entire client/server conversations or just on access to specific shares.
• Support for larger read and write sizes (512 KB in IBM i 7.4), improving the performance in high latency networks.
• QNTC can now support share names longer than 15 characters.
• NetServer has been updated to improve the support for macOS.

SMTP

SMTP (Simple Mail Transfer Protocol) has been available on IBM i for many years. It is a TCP/IP protocol used when sending and receiving email. In IBM i 7.4, SMTP has been refreshed.

The SNDSMTPEMM command has been updated and now allows:

• Up to 255 characters for the subject of an email
• Up to 5,000 characters for the main body of an email

New CL commands have been added to support the creating, adding, editing, and removing of distribution lists for directory types *SMTP and *SMTPMSF.

Availability

Save and Restore

The SAVE and RESTORE menus have been enhanced with a new option to "Start controlling subsystem". Previously, the controlling subsystem always started automatically when the save or restore operation completed. In IBM i 7.4, it is now possible to leave the system in restricted state after the save or restore operation, by not starting the controlling subsystem. This can be helpful for installing PTFs, performing system maintenance, or IPLing the system. See the Backing up your system and Recovering your system topics in IBM Knowledge Center for more information.

Clustering

IBM is announcing some enhancements to the clustering technologies resident in the base operating system. Many of these technologies are seamlessly integrated into IBM PowerHA SystemMirror for i.

New usability enhancements to the IBM i clustering policies allow for more automation of an administrative domain. Resources may be automatically added to the cluster administrative domain when they are created or added on a node. Previously, this was a two-step process; each monitored resource entry (MRE) had to be added manually after it was created. Similarly, it is possible to automatically delete resources and remove them from the cluster administrative domain in one step. Previously, a delete needed to be issued on each system in the cluster. See the Cluster Policy APIs topic in IBM Knowledge Center for more information.

Enhancements have been made to the behavior of restore handling in a cluster administrative domain to honour the restored values. Previously, after a restore the administrative domain would essentially undo the restore operation.

In IBM i 7.4, if a new policy for cancel failover is defined for a cluster resource group, the IASP will no longer be varied off on the failing node when a failover is canceled. Prior to this policy, when a failover was canceled, the IASP would be varied off on the failing node.

This release introduces the Container CRG, which allows for management of a group of CRGs as a single entity for the purposes of operations.

A restriction has been removed, and an IASP may now be specified in more than one CRG. This function is especially useful in Db2 Mirror configurations. Previously, an IASP was limited to a single CRG. When an IASP appears in more than one CRG, the CRG recovery domains must have no nodes in common.

Application development

Integrated Web Services server

The Integrated Web Services (IWS) server support enables users to create APIs based on ILE programs and service programs. In IBM i 7.4, IWS API support has been enhanced to allow the creation of REST and SOAP APIs based on SQL statements. The SQL statements are processed against Db2 for i database management systems. The support enables the creation of APIs that can process XML, JSON, and user-defined media resources. This now means that the database on IBM i can be accessed directly using the HTTP REST support. No JDBC or ODBC connection is needed when using the IWS support.

For additional details, see the Integrated Web Services for IBM i web page.

System Debugger

The System Debugger is the tool used to debug programs written in both ILE and OPM languages as well as Java that run on the system. Program information stored with the object, along with the program observability, are used by the System Debugger. In IBM i 7.4, the System Debugger is enhanced with some limited ability to relocate the debug source.

The Change Program Data (QBNCHGPD) API is enhanced to update the debug source location. This relocation, the moving of source files to another location, can be done for both library physical files and IFS stream files. The steps are:

• Compile a program from IFS stream source files or library physical files with DBGVIEW(*SOURCE).
• Move the source files to another location.
• Use API QBNCHGPD to update the old source location to the new one with new format CHGP0200.
• Debug the target program. System debugger will show the source files correctly from the new location.

Locating module source

The Display Module (DSPMOD) command now shows the location (path name) of a module's source code stored in a stream file (IFS). This will be very useful to C, C++, RPG, COBOL, and CL programmers because compilers for those languages all support compiling source from IFS.

TEXT options on CRTSRVPGM

Two new TEXT options are provided, in addition to *BLANK, for the Create Service Program (CRTSRVPGM) command. These new options allow propagation of the text from the export source file or the first module used to create the service program. See Create Service Program for more information.

Updated MI instructions

A couple of MI instructions have been enhanced:

• GENUUID can now generate a version 4 Universally Unique IDentifier (UUID), which is a randomly generated UUID that is consistent with the Internet Engineering Task Force (IETF) specification as described in RFC 4122. See the GENUUID MI Instruction topic in IBM Knowledge Center for more information.
• MODS can return the size of the modified space, avoiding a call to MATS to get the size of a modified space. See the MODS MI Instruction topic in IBM Knowledge Center for more information.

Easier retranslation of program objects

No retranslation of programs is required to work with IBM i 7.4. However, there are times when a retranslation may be beneficial to ensure that programs are using the latest technology updates for performance, efficiency, and so on. For this purpose, IBM is providing the new QBNCVTPGM tool. See the Simple IBM i program and module conversion technical article on developerWorks for more information.

Miscellaneous

Service Tool debug enhancements

The Mainstore Dump Copy screens now have a column that indicates the size of a dump to help plan for proper handling of a dump.

An option on the Remote Modem Support screens for configuring LANs makes it easier to set up access for remote support.

Limits for the Licensed Internal Code (LIC) log have been increased so important debug information does not wrap out of the log too soon. Note that the LIC Log sizes are selectable by the client, but have minimum, default, and maximum values. See the Licensed Internal Code log topic in IBM Knowledge Center for more information.

Selected operating system limits increased

• The maximum number of disk arms in all basic auxiliary storage pools has been increased to 3999.
• The maximum number of disk arms in all independent auxiliary storage pools has been increased to 5999.
• The maximum LUN size (for LUNs with 4160 or 4096 byte block sizes) has been increased to 16 TB.

For more information about these limits, and others, see the Miscellaneous Limits topic in IBM Knowledge Center.

Db2 for i

With IBM i 7.4, Db2 for i continues to focus on new and advanced SQL capabilities and the ability to use SQL to access IBM i operating system detail. Further, Db2 for i delivers new capabilities for the database engineer.

Database application developers have new capabilities for constructing data-centric SQL solutions:

• A new variant of INSERT can be used to populate rows using default values.
• The RPG SQL Precompiler is enhanced to support constants as host variables.
• The SYSTOOLS.SPLIT User Defined Table Function (UDTF) can be used to deconstruct aggregated lists of values using SQL.

In the tradition of recent Technology Refreshes, IBM i Services are added and enhanced, providing useful SQL-based alternatives to IBM i commands and APIs:

• The DATA_AREA_INFO view and UDTF enable SQL users to query the existence, attributes, and data within data areas (*DTAARA).
• The ASP_JOB_INFO view returns one row for each job that is currently using a specific ASP. This service is an SQL alternative to the Work with ASP Jobs (WRKASPJOB) CL command.
• The OBJECT_PRIVILEGES view is enhanced to return authorization list detail, bringing equivalent functionality to the SQL alternative to the Display Object Authority (DSPOBJAUT) CL command.
• The MESSAGE_FILE_DATA view returns data that can be found using the Display Message Description (DSPMSGD) CL command, opening up new options for managing messages using SQL.

Examples of these new services can be found in the latest versions of Access Client Solutions within the Run SQL Scripts interface under the category "Insert from Examples".

New capabilities are added for the database engineer:

• The CREATE INDEX statement has been enhanced to include result column names matching the behavior of the ALIAS and RENAME keywords that are supported for logical files.
• The PARSE_STATEMENT UDTF is enhanced to return detail for DROP statements and referential constraints, making it easier to deploy advanced impact analysis.
• System Limits processing has been extended to additionally track the growth of database files by size, providing the data needed for clients to proactively manage their IBM i.

These and other enhancements are delivered through Db2 PTF Group SF99704. See the IBM i Technology Updates wiki on developerWorks to learn more about these and other Db2 for i enhancements.

Open source

Node.js ecosystem enhancements

The idb-connector and idb-pconnector packages 1.x releases are now generally available and are no longer in technology preview status. The idb-connector package provides direct API access to Db2 using the conventional (callback-based) JavaScript conventions.

The itoolkit package, which allows a Node.js application to call IBM i functions, such as service programs, programs, commands, and so on, is enhanced to allow for new transport methods. With this enhancement, SSH or ODBC connections can be used to communicate with IBM i through the itoolkit package.

A Db2 for i dialect has been created for Sequelize.js. Sequelize is a popular, promise-based ORM for Node.js.

A new connector allows Db2 for i to be used as a data source for LoopBack applications. LoopBack is a JavaScript framework that allows for rapid creation and deployment of REST APIs. It comes with a built-in API explorer and the ability to define a robust data model for your application. It can also be used with IBM API Connect and several other tools.

Python ecosystem enhancements

A number of Python packages have been made available in RPM form. This enables the packages to be easily installed with the yum package manager. The new packages allow for security enhancements, and more options for application development, data science, and machine learning.

The updated Python Machine Learning and Data Science libraries are included in the following packages:

• Pillow
• asn1crypto
• bcrypt
• cffi
• cryptography
• devel
• ibm_db
• idna
• itoolkit
• lxml
• numpy
• pandas
• pip
• pycparser
• pynacl
• scikit-learn
• scipy
• tkinter

General connectivity enhancements

The delivery of SSL certificates through a ca-certificates RPM allows for easier SSL communication with standard sources. For instance, interactions with https-based APIs or websites may no longer need manual certificate setup.

The IBM i Access ODBC driver has been ported to IBM i. This allows any standard ODBC client to be able to communicate to the local database on i. It also allows an application to be developed using the IBM i Access ODBC driver for Windows/Linux and deployed to IBM i using the same ODBC driver.

R

R brings another programming language to IBM i. Although it has a wide variety of uses, R excels at statistical computing and data mining. Db2 can be accessed from R by installing the RODBC package and using the newly delivered ODBC driver.

Newly added tools

The number of developer and user tools available continues to grow rapidly. A few examples include the following packages, available in RPM form:

• Apache ActiveMQ, a robust message broker
• Apache Ant and Maven, build automation tools
• vim, a terminal-based editor
• yum-utils, a collection of tools and programs for managing yum repositories and installed software for more advanced users
• Midnight Commander, a terminal-based utility for exploring the filesystem and performing various tasks like FTP transfers, file compares, and much more

IBM i Portfolio: Licensed Program Products (LPP)

IBM Db2 Mirror for i

Today, in conjunction with the announcement of IBM i 7.4, IBM is announcing a new Licensed Program Product (LPP) for the IBM i Portfolio: IBM Db2 Mirror for i. This new product offering, available for IBM i 7.4 clients, enables near-continuous availability through an IBM i exclusive Db2 active-active two-system configuration.

Rational Development Studio for i

The Development Studio for i is being updated to transform the development languages of IBM i to meet the ever-changing world of modern development. The RPG language is evolving into a modern business language. In this release, COBOL is also being enhanced to include many requirements from the industry.

RPG

There are many enhancements to the RPG Language in this release (some of these were made available in earlier TRs through PTFs):

• A varying-dimension array is defined with DIM(*AUTO:maximum_elements) or DIM(*VAR:maximum_elements). The second parameter of the DIM keyword indicates the maximum number of elements in the array.
  • The dimension of a varying-dimension array can be changed by assigning a value to the %ELEM built-in function.
  • The dimension of a varying-dimension array defined with DIM(*AUTO) increases when there is an assignment statement to an element that is greater than the current number of elements.
  • You can specify *NEXT as the index for an array defined with DIM(*AUTO) when the array is modified by an assignment statement. The dimension of the array increases by one.
• Specify DIM(*CTDATA) to specify that the dimension of a compile- time array or table is determined by the number of records in the compile-time data.
• The SAMEPOS keyword positions a subfield at the same starting position as another subfield.
• New PSDS subfields:
  • Internal job ID, in positions 380 to 395
  • System name, in positions 396 - 403
• The ON-EXIT section runs every time that a procedure ends, whether the procedure ends normally or abnormally.
• When a qualified data structure is defined using free-form RPG syntax, a subfield can be directly defined as a nested data structure subfield using DCL-DS and END-DS to define the subfield.
• The new DATA-INTO operation code reads data from a structured document, such as JSON, into an RPG variable. It requires a parser to parse the document. The DATA-INTO operation calls the parser, and the parser passes the information in the document back to the DATA-INTO operation, which places the information into the RPG variable.
• Built-in function %PROC() returns the external name of the current procedure.
• Complex qualified names can be used in more places:
  • Built-in function %ELEM
  • Built-in function %SIZE
  • Operation code DEALLOC
  • Operation code RESET
• New built-in functions %MAX and %MIN can be used in definition statements and calculation statements.
• ALIGN(*FULL) defines the length of a data structure as a multiple of its alignment. This is important for avoiding storage-corruption problems when calling functions written in ILE C.
• The CRTBNDRPG and CRTRPGMOD commands now support compiling from Unicode source by specifying either an EBCDIC CCSID or *JOB for the new TGTCCSID parameter.

For more information about the RPG IV enhancements, including the PTFs that provide the enhancements, see the RPG Cafe.

COBOL

New enhancements are available for the COBOL compiler:

• The new ALLOCATE statement obtains dynamic storage, while the new FREE statement releases dynamic storage that was previously obtained with an ALLOCATE statement.
• The EXIT statement includes the following new formats, which provide a structured way to exit without using a GO TO statement:
  • Format 5, EXIT PERFORM statement for exiting from an inline PERFORM statement
  • Format 6, EXIT PARAGRAPH or EXIT SECTION statement for exiting from the middle of a paragraph or exiting from a section respectively
• Enhancements are made to the INITIALIZE statement:
  • A new FILLER phrase is added so that FILLER data items can be initialized with the INITIALIZE statement.
  • A new VALUE phrase is added so that elementary data items can be initialized to the literal specified in the VALUE clause.
  • The INITIALIZE statement supports NATIONAL-EDITED as a REPLACING category and can initialize national groups and numeric or numeric- edited data that has USAGE NATIONAL.
• A new format of the SORT statement, the table SORT statement, arranges table elements in a user-specified sequence.
• The following new compiler directives are added to support conditional compilation:
  • The DEFINE directive defines or undefines a compilation variable.
  • The EVALUATE directive provides a multibranch method of choosing the source lines to include in a compilation group.
  • The IF directive provides for a one-way or two-way conditional compilation.
  • The new DEFINE parameter for the CRTBNDCBL and CRTCBLMOD commands provides a way to define compilation variables before the compilation begins.
  • A new floating comment indicator (the character string '*>') can be coded to indicate that the ensuing text on a line is an inline comment.

IBM i Access Client Solutions (ACS) V1.1.8.2

IBM i Access Client Solutions is the strategic interface for accessing and managing IBM i. A new version (1.1.8.2) includes many new features and updates for both an IBM i system manager and a database engineer.

Run SQL Scripts

• Open and Save support to IFS and stream files extends the options for how scripts are maintained and used.
• When a "Database of Choice" has been selected, the information is retained, making it easier to resume work. Additionally, connections to an IASP are retained.
• The Insert from Examples capability is extended to include new SQL examples, making it easier and faster to include precoded examples.
• New JDBC Connection properties are available for assigning alternate server name and other attributes.
• The new design of the Formatter enables it to understand SQL syntax, creating more consistency for formatting, especially with complex SQL statements.
• The new formatter also provides the ability to verify the syntax of your SQL, highlighting error information, line numbers, and issues.
• Leveraging the new "for Update" option, users who have access can update and edit the data values within a database table directly from Run SQL Scripts.

Schemas

• To facilitate the creation of new projects, the ability to copy and paste schemas has been added.

Printer Output

• Most printed output displays the system name. Based on requests from clients, ACS 1.1.8.2 allows for removing the system name from the Printer Output download path.

Integrated File System

• Prompt for the location of the current IFS download location on the target PC.
• A new "Include" filter to improve performance by limiting the data returned from the server when viewing directories with a large number of files.

ODBC Driver for i

• The IBM i Access ODBC driver has been ported to IBM i. This allows any standard ODBC client to be able to communicate to the local database on i. It also allows an application to be developed using the IBM i Access ODBC driver for Windows/Linux and deployed to IBM i using the same ODBC driver.

System Configuration

• The System Configuration panel can now be leveraged as the primary location for launching ACS activities.
• Keyboard shortcuts have been added to menu options, improving navigation and simplifying the user's experience. Also, right- clicking on a system on the System Configuration panel will show a context menu of available actions.
• To accommodate different user preferences, you can sort the data within a column on the System Configuration panel.
• Easily see the specified description field to understand the system being selected.
• The Hardware Management Interface has undergone dramatic improvement. Some of these are:
  • A customized list of possible interfaces has been added.
  • It is possible to now specify more than two options.
  • The main ACS panel will be updated based on the configured Hardware Management Interfaces for the selected system.

Additional enhancements

• Japanese new era support has been added to ACS.
• Prior to ACS V1.1.7.2, when importing an ACS configuration to a target machine, it was necessary to have the user profile of the saved configuration already on the target. With ACS V1.1.8.2, this requirement is removed and the saved default user profile is not required to exist when importing a configuration.
• New ability to specify a list of included components, thereby excluding those not on the list.

Improved Entitled System Support (ESS) delivery

In response to client feedback regarding making Access Client Solutions easier to find and download on the ESS website, feature 6290 under 5770-SS1 will be automatically defaulted on orders of 5770-SS1 for version 7.2 and later releases. On the ESS website, under Software Downloads, select 5770-SS1 IBM i, then select your language group, then in the download packages, see the feature "6290: Access Client Solutions".

For the latest updates and access to the most recent version, see the IBM i Access Client Solutions web page.

Administration Runtime Expert

Administration Runtime Expert is used by system administrators to enhance the abilities to manage the systems in their environment. In IBM i 7.4, Administration Runtime Expert has made significant enhancements to the product. PTF management now includes the ability to manage PTFs with preconditions as well as handling delayed PTFs. With the ability of Administration Runtime Expert to compare and manage PTFs across multiple systems, this provides more usability. Additional enhancements are:

• The dashboard interface has been updated to handle an independent workset for every user to easily allow the dashboard to be used for a call centre environment.
• Result history now shows the formatted view instead of just the text view.
• Support for case-sensitive template rename.
• Attach the zip file of a verification result to the notification mail.
• Restrict user's access by the role. If a user's role is "operator", the user has access only to console and has no ability to edit groups and systems.

Rational Developer for i, 9.6.x

Rational Developer for i (RDi), 9.6.x, is the strategic suite of tools for IBM i developers. This desktop environment gives developers an efficient and highly productive environment for writing business applications. The primary focus of these and other recent enhancements has been to provide continuous improvement in the areas of reliability, productivity, security, and currency.

• Added an API to allow SystemTextEditors to report an IBM i connection and member properties, thereby making actions and third- party vendors independent of the parser for this information.
• Users can zoom in and out in the editor using command keys.
• Settings are now available to allow free-form RPG comments to be repeated from a previous operation code.
• Code coverage has undergone two significant improvements:
  • Code coverage results have an improved web-faced view.
  • Code coverage source view now displays in Browse mode.
• PDM Perspective, brought to RDi users in 2018, has been refined and includes new enhancements to make the view even more compatible with PDM.
  • Added Alt-F13 to enable users to repeat options in a manner similar to PDM on the options field of the Member Object table view
  • Added new multiple entry actions to improve Object Table multiple object actions, enabling users to copy repeat options in one panel instead of a series of popup commands
• JTopen, ACS, and Java have been updated to be compatible with IBM i 7.4.
• The RPG verifier and syntax checker will support the new ILE RPG enhancements in IBM i 7.4.
• RPG ILE Parser includes the capability to search for code that appears to be out of place and reports these discoveries with annotations, allowing developers to quickly find anomalies in their code.
• Improved SQL formatting:
  • Smart enter key is included, allowing easier line splitting.
  • Developers can now choose either automatic formatting or to specifically request when formatting should occur.
• RDi has added a Toggle editor to the outline view, allowing the display of procedure and subroutine names while navigating in the editor.

For these new enhancements, additional updates, and APAR fixes, see the Fix list for Rational Developer for i website.

PowerHA SystemMirror for i

A key value proposition for PowerHA on IBM i is that it integrates the functionality of IBM SAN storage: in particular, the DS8000 and the IBM Storwize family of storage servers. This integration enables PowerHA for i to manage the storage operations as an integral part of clustering operations such as failover/fallback operations and FlashCopy operations. With PowerHA SystemMirror for i Enterprise Edition, the integration with the IBM Copy Services Manager for the DS8000 enables PowerHA to support HyperSwap with a Global Mirror link. HyperSwap is an active/active storage configuration whereby two of the DS8000s are linked through Metro Mirror, while at the user/application level, it actually appears as a single shared storage resource (switchable LUN configuration). If one of the storage servers in the HyperSwap configuration goes away, the application workload simply continues I/O operations to the alternate DS8000 in the HyperSwap pair without interruption. Adding the capability to support a Global Mirror link to the HyperSwap pair provides the third site for disaster recovery operations, all under the management of the PowerHA for i cluster.

In addition, PowerHA for i, 7.4 Enterprise Edition enables a Db2 Mirror disaster recovery capability.

PowerHA SystemMirror for i, 7.4 Standard Edition has been enhanced with ease-of-use and automation capabilities:

• New policies that automate adding monitored resource entries (MREs) upon object creation, the deletion of MREs upon object deletion, and restore operations for MREs.
• Improved control over administrative domain synchronisation options; for example, the capability to choose which node is to be the source of updates to push to the other nodes when using Start Cluster Administrative Domain. Previously, when resource changes were made to nodes in an inactive administrative domain, multiple nodes could change the same resource and there was no coordination for multiple different changes to the same resource.
• Integrated ability to cancel automatic CRG failovers with a new PowerHA policy.
• Support for replication of IFS data in a Db2 Mirror for i environment.

For more information, see the IBM PowerHA SystemMirror for i wiki page.

Backup, Recovery, and Media Services for i (BRMS)

The BRMS 7.4 enhancements include:

• Turn-key cloud control group deployment that enables clients to easily set up custom control groups for cloud.
• Ability to enable the green screen command to change control group attributes, which were previously available only in the GUI.
• Backup for changes to journaled objects is now the default setting; that is, the default for SAVLIBBRM command has been changed to OBJJRN(*YES).
• New *OBJ list named QALLSPLF to back up all spooled files, which improves restore performance.
• Support for the 3592-60F tape drive with *FMT3592A6 and FMT3592A6E densities.
• Enhanced log information that uses the system timestamp to preserve message order when messages are logged at the same second. They are displayed using DSPLOGBRM.

For more information, see the IBM Backup, Recovery & Media Services (BRMS) for i wiki page.

Db2 Web Query

Get a fast start to advanced, visual reporting and business intelligence with Db2 Web Query for i. Get running quickly using Web Query's newly enhanced EZ-Install package. Flatten the learning curve through readily available tutorials, a new Date Dimension table creation procedure, and new sample reports for the IBM i Systems Administrator. To learn more about EZ-Install, see the DB2 Web Query for i installation web page.

ARCAD Observer (Version 1.1.2)

ARCAD Observer for IBM i supports the understanding of business applications. It includes graphical diagramming, I/O diagramming, and other analysis capabilities to understand business applications.
Note: The latest version of ARCAD Observer (10.08.02) is being incorporated into this LPP.

ARCAD Converter (Version 1.1.2)

ARCAD RPG Converter for IBM i automates the conversion of any RPG IV source code to free-form RPG, achieving near 100% conversion accuracy. It supports unitary or mass conversion.
Note: The latest version of ARCAD Transformer (10.09.03) is being incorporated into this LPP.

Firmware and hardware

IBM i supports FW930, which provides the most up-to-date POWER9 functionality.

Additional I/O support includes several Power features:

• Enhanced support for the PCIe Gen4 dual port 100 Gb Ethernet adapter. IBM i adds both dedicated and native SR-IOV support for the Network Interface Card (NIC) function. This adapter is already available for use in IBM i configurations with Virtual I/O Server (VIOS). IBM i also adds both dedicated and native SR-IOV support for RDMA over Converged Ethernet (RoCE) to allow remote direct memory access (RDMA) in IBM Db2 Mirror for i configurations.
• Both dedicated and native SR-IOV support for RoCE for PCIe Gen3 Ethernet adapters. Sharing these adapters with SR-IOV allows more configuration flexibility. Multiple 2-port cards are available: 100 Gb, 25/10 Gb, and 10 Gb.
• New PCIe3 6-Slot Fanout Module for the PCIe3 Expansion Drawer.
• New optical cable cards for attaching the PCIe3 I/O Expansion drawer with the new PCIe3 6-Slot Fanout Module. The new cards for the Scale Out models are now single wide so they do not block the adjacent PCIe Gen4 x16 card slot.
• New 387 GB, 775 GB, and 1.55 TB Enterprise SAS 4k and 5xx SFF-3 and SFF-2 SSDs.
• New 931 GB, 1.86 TB, 3.72 TB, and 7.45 TB Mainstream SAS 4K SFF-3 and SFF-2 SSDs.

Other

IBM Content Manager OnDemand for i (5770-RD1)

IBM Content Manager OnDemand for i is providing significant new function in the latest release, exploiting new technologies available in IBM i. Some of the enhancements are listed below:

• Cloud storage for archive media: Cloud storage is now supported as an archive media for Content Manager OnDemand for i. Cloud support requires the IBM Cloud Storage Solutions for i (5733-ICC) licensed program product.
• 400 indexer enhancements: The OS/400 indexer has been renamed to the 400 indexer. The 400 indexer has been updated for improved performance and enhanced serviceability. In addition, the 400 indexer can now use AFP resources located in IFS directories.
• Content Manager OnDemand component of IBM Navigator for i enhancements: A new option has been added to create and manage cloud storage resources. The design of the Content Manager OnDemand component of IBM Navigator for i has also been updated to reflect a format similar to the operating system components.
• Start Archived Storage Management (STRASMOND) command enhancement: The Start Archived Storage Management (STRASMOND) command has a new Trace (TRACE) parameter to facilitate tracing when requested by software support.
• Start Disk Storage Management (STRDSMOND) command enhancement: The Start Disk Storage Management (STRDSMOND) command has a new Force ASM to end (ENDASM) parameter to enable you to end the Archived Storage Management (ASM) process (which, by default, runs after DSM completes) at a specified time or after a specified number of hours. Prior to version 7.4, the ENDASM parameter was only available on the Start Archived Storage Management (STRASMOND) command.
• Print Report (PRTRPTOND), Print document (PRTDOCOND), Query document (QRYDOCOND), and Retrieve document (RTVDOCOND) command enhancements: The Print Report (PRTRPTOND), Print document (PRTDOCOND), Query document (QRYDOCOND), and Retrieve document (RTVDOCOND) commands have a new Retrieve in load order (RTVLODORD) parameter to control which documents are included and in what order the documents are included. See the command help for the RTVLODORD parameter for more information.

See the Customer Notices and information - IBM i 7.3 website for additional Content Manager OnDemand for i 7.3 enhancements that are available through PTFs and are also included in Content Manager OnDemand for i for IBM i 7.4. These enhancements are related to encryption, managing documents, administering objects, and allowing coexistence of 32-bit and 64-bit clients and/or 9.5 and 10.1 clients on a single workstation.

Content Manager OnDemand's software requirements will depend on your implementation. See the Content Manager OnDemand for i topic in IBM Knowledge Center.

Content Manager OnDemand for i is available to order through Passport Advantage. See the Passport Advantage and Passport Advantage Express website.

Software progression

The following table is used to show the updates for various products.

Program updates

- indicates product is not orderable.

* indicates which products are not being refreshed for this release but are still available.

# indicates product was orderable but has become a bonus program with the operating system.

PN (part number) indicates product has moved to Passport ordering .

NA (not available) indicates product is no longer orderable with the operating system.

IBM i 7.3 TR4

Provides support for POWER9 hardware, enhanced security and adds a variety of new capabilities for programmers.

IBM i

• Developers can now compile their CL commands from source code stored in IFS files.
• Sending email to a group of users has been simplified with SMTP distributions list support.
• IBM i Integrated Web Services adds advanced features to help administrators and programmers leverage APIs in a safe secure manner.
• Extensions to the new installation process for LIC using USB 3.0 media

Licensed programs

• The RPG ILE Compiler in Rational Development Studio has been updated with new modernization capabilities.
• IBM i Access Client Solutions continues to be enhanced to meet the needs of our IBM i user community.
• IBM Access for Web 5770-XH2, the core for our mobile system access and management support has been updated to now run on the latest versions of WebSphere Application Server V9.
• IBM Access for Web can now leverage the latest web infrastructure.
• Backup, Recovery, and Media Services (BRMS) is enhanced with cloud remote system restore.
• ARCAD Observer for IBM i V1.1.0 includes a performance improving multi-job compile process and more.

IBM SW product Updates

• IBM Notes/Domino 901 Feature pack 10 with a number of fixes and enhancements will be delivered to continue to provide the secure robust support our customers expect on IBM i.

Hardware and Firmware

• IBM i 7.3 TR4 provides support for the following configurations:
  • Native and VIOS configurations for new IBM S914 and IBM S924 servers with POWER9 technology
  • Native and VIOS configurations for new IBM H924 server with POWER9 technology
  • VIOS configurations for new IBM S922 server with POWER9 technology
  • VIOS configurations for new IBM H922 server with POWER9 technology
• IBM PowerVM Enterprise is included with every POWER9 technology- based processor server, making every server Cloud-enabled

IBM i 7.3 TR3

• IBM Db2 for i adds new and enhanced SQL capabilities for database application developers, system administrators, and security auditors. With these enhancements, Db2 for i can be used to become more productive and effective at solving important business requirements.
• Installation of IBM i can now be done with a simple download, copy to USB flash drive, and D-mode IPL on managed systems.
• The IBM i Save System (SAVSYS) operation now includes the LAN console configuration data, eliminating a couple of complex steps that were previously needed to re-install an IBM i partition from a backup onto a new load source.
• IBM i supports the 4767 Cryptographic Co-processor. The 4767 is the follow-on to the 4765 Cryptographic Co-processor.
• IBM i supports an increase in the size of an external storage disk.
• IBM i can support up to 127 devices on both virtual and physical Fibre Channel ports.
• IBM i Integrated Web Services adds advanced features to help administrators and programmers leverage APIs in a safe, secure manner.
• IBM continues to expand the suite of functions available in the open source licensed program offering with benefits for many application scenarios. This includes new integration with the operating system, familiar IBM i Access tools, and IBM Bluemix.
• Access Client Solutions continues to be enhanced to meet the needs of the IBM i user community.
• The RPG ILE Compiler in Rational Development Studio has been updated with new modernization capabilities.
• Rational Developer for i, V9.6 delivers an updated version of the Eclipse workbench, in addition to features designed to enhance programmer productivity.
• IBM Cloud Storage Solutions for i, V1.2 includes new encryption techniques, adding to the security of data movement.
• Db2 Web Query for i has a new release, version 2.2.1, with many new advanced visualization, usability, and security features.
• Db2 Web Query DataMigrator now includes simplified functions, regular expression support, and improved scheduling.

IBM i 7.3 TR2 is focused primarily on adding significant function into DB2 for i, enhancing IBM i Access Client Solutions and adding binaries for new tools into the IBM Open Source offering. In addition to extending these software functions, IBM i 7.3 TR2 also provides the necessary capabilities for supporting the newly announced IBM S812 hardware model.

• IBM DB2 for i adds new and enhanced SQL capabilities for database application developers and system administrators. With these enhancements, SQL can be used to become more productive and effective at solving business requirements.
• The 5733-OPS offering has been enhanced to include more tools that serve both the system administrator and the application developer.
• IBM i Access Client Solutions continues to be enhanced to provide additional function and value to users, system administrators and database engineers. Providing them with the tools to work with their IBM i systems from the PC platform of their choice.
• Power Systems IBM i now supports a lower priced 1-core Power S812 for clients with modest processing and lower I/O needs.
• Serviceability improvements reduce the number of situations that require a Mainstore Dump and speed the analysis when a Mainstore Dump is required.

IBM i 7.3 TR1

As with every new Technology Refresh, IBM i adds a variety of function across the entire operating system, Licensed Program Products, and updates to the IBM Power hardware and firmware. The major highlights of IBM i 7.3 TR1 are:

• IBM DB2 for i offers new and advanced SQL capabilities, SQL Query Engine (SQE) performance, and the ability to use SQL to access details about the IBM i operating system.
• IBM i Open Source Solutions now includes Perl and the latest version of Node.js.
• IBM i Access Client Solutions has enhanced the end-user interaction to improve usability of many of the components.
• IBM Rational Developer for i, V9.5.1 includes support for the Mac OS X operating system and improved usability for developers using Mac technology.
• IBM PowerHA SystemMirror for i now supports SVC/Storwize HyperSwap with Independent Auxiliary Storage Pools (IASPs) and the new HMC interfaces for Advanced Cluster Node Failure Detection.
• Delivery simplification of selected IBM i LPPs and IBM i feature OptiConnect.
• IBM i Entitlement Transfer to P05 now supports upgrade to three- years SWMA.
• Power hardware and system firmware enhancements provide significant advantages to IBM i clients.
• Additional enhancements can be found in the following areas:
  • Containers make USB Flash and RDX look like a stack of DVDs
  • IBM i Integrated Web Services
  • IBM i HTTP Server (Powered by Apache) 5770-DG1
  • Rational Development Studio (5770-WDS)
  • WebSphere Application Server V9
  • DB2 Web Query
  • Hardware and System Firmware enhancements
  • EXP24SX SAS Storage Enclosure for high performance disks or SSDs
  • PCIe3 Cryptographic Coprocessor card
  • PCIe3 100 Gb Ethernet adapters
  • RDX USB Top Mount Docking Station on Power Systems S814
  • VNIC fail-over
  • Shared Ethernet Adapter (SEA)
  • NovaLink support for SR-IOV configurations
  • Tape device TS4500 R3
  • Power Systems firmware V8.6 enhancement for identifying a partition using a Universally Unique Identifier (UUID)

IBM i 7.2 TR8

Provides support for POWER9 hardware, enhanced security and adds a variety of new capabilities for programmers.

IBM i

• IBM i Integrated Web Services adds advanced features to help administrators and programmers leverage APIs in a safe secure manner.
• Extensions to the new installation process for LIC using USB 3.0 media

Licensed Program Products

• IBM i Access Client Solutions (ACS) continues to be enhanced to meet the needs of our IBM i user community.
• IBM Access for Web, the core for our mobile system access and management support has been updated to now run on the latest versions of WebSphere Application Server V9.
• IBM Access for Web can now leverage the latest web infrastructure.
• Backup, Recovery, and Media Services (BRMS) is enhanced with cloud remote system restore.
• ARCAD Observer for IBM i V1.1.0 includes a performance improving multi-job compile process and more.

Hardware and Firmware

• IBM i 7.2 TR8 provides support for the following configurations:
  • Native and VIOS configurations for new IBM S914 and IBM S924 servers with POWER9 technology
  • Native and VIOS configurations for new IBM H924 server with POWER9 technology
  • VIOS configurations for new IBM S922 server with POWER9 technology
  • VIOS configurations for new IBM H922 server with POWER9 technology
• PowerVM Enterprise is included with every POWER9 technology-based processor server, making every server Cloud-enabled

IBM i 7.2 TR7

• IBM Db2 for i adds new and enhanced SQL capabilities for database application developers, system administrators, and security auditors. With these enhancements, Db2 for i can be used to become more productive and effective at solving important business requirements.
• Installation of IBM i can now be done with a simple download, copy to USB flash drive, and D-mode IPL on managed systems.
• The IBM i Save System (SAVSYS) operation now includes the LAN console configuration data, eliminating a couple of complex steps that were previously needed to re-install an IBM i partition from a backup onto a new load source.
• IBM i will now support the 4767 Cryptographic Co-processor. The 4767 is the follow-on to the 4765 Cryptographic Co-processor.
• IBM i can support up to 127 devices on both virtual and physical Fibre Channel ports.
• IBM i Integrated Web Services adds advanced features to help administrators and programmers leverage APIs in a safe, secure manner.
• IBM continues to expand the suite of functions available in the open source licensed program offering with benefits for many application scenarios. This includes new integration with the operating system, familiar IBM i Access tools, and IBM Bluemix.
• Access Client Solutions continues to be enhanced to meet the needs of the IBM i user community.
• The RPG ILE Compiler in Rational Development Studio has been updated with new modernization capabilities.
• Rational Developer for i, V9.6 delivers an updated version of the Eclipse workbench, in addition to features designed to enhance programmer productivity.
• IBM Cloud Storage Solutions for i, V1.2 includes new encryption techniques, adding to the security of data movement.
• Db2 Web Query for i has a new release, version 2.2.1, with many new advanced visualization, usability, and security features.
• Db2 Web Query DataMigrator now includes simplified functions, regular expression support, and improved scheduling.

IBM i 7.2 TR6 is focused primarily on adding significant function into DB2 for i, enhancing IBM Access Client Solutions for I and adding binaries for new tools into the IBM Open Source offering. In addition to extending these software functions, IBM i 7.2 TR6 also provides the necessary capabilities for supporting the newly announced IBM S812 hardware model.

• IBM DB2 for i adds new and enhanced SQL capabilities for database application developers and system administrators. With these enhancements, SQL can be used to become more productive and effective at solving business requirements.
• The 5733-OPS offering has been enhanced to include more tools that serve both the system administrator and the application developer.
• IBM i Access Client Solutions continues to be enhanced to provide additional function and value to users, system administrators and database engineers, providing them with the tools to work with their IBM i systems from the PC platform of their choice.
• IBM i supports the newly announced lower priced 1-core Power S812 for clients with modest processing and lower I/O needs.
• Serviceability improvements reduce the number of situations that require a Mainstore Dump and speed the analysis when a Mainstore Dump is required.

IBM i 7.2 TR5

As with every new Technology Refresh, IBM i adds a variety of function across the entire operating system, Licensed Program Products, and updates to the IBM Power hardware and firmware. The major highlights of IBM i 7.2 TR5 are:

• IBM DB2 for i offers new and advanced SQL capabilities, SQL Query Engine (SQE) performance, and the ability to use SQL to access details about the IBM i operating system.
• IBM i Open Source Solutions now includes Perl and the latest version of Node.js.
• IBM i Access Client Solutions has enhanced the end-user interaction to improve usability of many of the components.
• Rational Developer for i, V9.5.1 includes support for the Mac OS X operating system support and improved usability for developers using Mac technology.
• IBM PowerHA SystemMirror for i now supports SVC/Storwize HyperSwap with Independent Auxiliary Storage Pools (IASPs), and the new HMC interfaces for Advanced Cluster Node Failure Detection.
• Delivery simplification of selected IBM i LPPs and IBM i feature OptiConnect.
• IBM i Entitlement Transfer to P05 now supports upgrade to three- years SWMA.
• Power hardware and system firmware enhancements provide significant advantages to IBM i clients.
• Additional enhancements can be found in the following areas:
  • Containers make USB Flash and RDX look like a stack of DVDs
  • IBM i Integrated Web Services
  • IBM i HTTP Server (Powered by Apache) 5770-DG1
  • Rational Development Studio (5770-WDS)
  • WebSphere Application Server V9
  • DB2 Web Query
  • Hardware and System Firmware enhancements
  • EXP24SX SAS Storage Enclosure for high performance disks or SSDs
  • PCIe3 Cryptographic Coprocessor card
  • PCIe3 100 Gb Ethernet adapters
  • RDX USB Top Mount Docking Station on Power Systems S814
  • VNIC fail-over
  • Shared Ethernet Adapter (SEA)
  • NovaLink support for SR-IOV configurations
  • Tape device TS4500 R3
  • Power Systems firmware V8.6 enhancement for identifying a partition using a Universally Unique Identifier (UUID)

IBM i 7.2 TR4

This is a complete, one-page listing of changes across all Postgres versions. All versions 9.4 and older are EOL (end of life) and unsupported. This page was generated on August 13, 2020 by a script (version 1.23) by Greg Sabino Mullane, and contains information for 415 versions of Postgres.

Release date: 2020-XX-XX, CURRENT AS OF 2020-08-09

 Overview

Major enhancements in PostgreSQL 13 include:

The above items are explained in more detail in the sections below.

 Migration to Version 13

A dump/restore using pg_dumpall or use of pg_upgrade or logical replication is required for those wishing to migrate data from any previous release. See Section 18.6 for general information on migrating to new major releases.

Version 13 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:

• Change to return (Tom Lane)

  This new behavior matches the

• Have properly check "string" parameter (Dominik Czarnota)

• In ltree, when using adjacent asterisks with braces, e.g. ".*{2}.*{3}", properly interpret that as ".*{5}" (Nikita Glukhov)

• Change the way non-default effective_io_concurrency values affect concurrency (Thomas Munro)

  Previously, this value was adjusted before effecting the number of concurrent requests. This value is now used directly. Conversion of old values to new ones can be done using:

  SELECT round(sum (OLD / n::float)) FROM generate_series(1, OLD) s(n);

• Prevent display of auxiliary processes in pg_stat_ssl and pg_stat_gssapi system views (Euler Taveira)

  Queries that join these views to pg_stat_activity and wish to see auxiliary processes will need to use left joins.

• Rename various wait events to improve consistency (Fujii Masao, Tom Lane)

• Fix to return a more appropriate command tag (Fujii Masao)

  Previously it returned , but now returns .

• Fix to return a more appropriate command tag (Fujii Masao)

  Previously it returned , but now returns .

• Rename configuration parameter to wal_keep_size (Fujii Masao)

  This determines how much WAL to retain for the standby server, specified in megabytes rather than number of files. If you previously used , the following formula will give you an approximately equivalent setting:

  wal_keep_size = wal_keep_segments * wal_segment_size (typically 16MB)

• Remove support for defining operator classes using pre-PostgreSQL 8.0 syntax (Daniel Gustafsson)

• Remove support for defining foreign key constraints using pre-PostgreSQL 7.3 syntax (Daniel Gustafsson)

• Remove support for "opaque" pseudo-types used by pre-PostgreSQL 7.3 servers (Daniel Gustafsson)

• Remove support for files in the timezone database (Tom Lane)

  IANA's timezone group has deprecated this feature, meaning that it will gradually disappear from systems' timezone databases over the next few years. Rather than have a behavioral change appear unexpectedly with a timezone data update, we have removed PostgreSQL's support for this feature as of version 13. This affects only the behavior of POSIX-style time zone specifications that lack an explicit daylight savings transition rule; formerly the transition rule could be determined by installing a custom file, but now it is hard-wired. The recommended fix for any affected installations is to start using a geographical time zone name.

• Fix pageinspect's to return more appropriate data types that are less likely to overflow (Peter Geoghegan)

 Changes

Below you will find a detailed account of the changes between PostgreSQL 13 and the previous major release.

 Server

 Partitioning

• Improve cases where pruning of partitions can happen (Yuzuko Hosoya, Amit Langote, Álvaro Herrera)

• Allow partitionwise joins to happen in more cases (Ashutosh Bapat, Etsuro Fujita, Amit Langote, Tom Lane)

  For example, partitionwise joins can now happen between partitioned tables even when their partition bounds do not match exactly.

• Allow row-level triggers on partitioned tables (Álvaro Herrera)

  These triggers cannot change which partition is the destination.

• Allow partitioned tables to be logically replicated via publications (Amit Langote)

  Previously, partitions had to be replicated individually. Now partitioned tables can be published explicitly causing all partitions to be automatically published. Addition/removal of partitions from partitioned tables are automatically added/removed from publications. The option controls whether changes to partitions are published as their own or their ancestor's.

• Allow logical replication into partitioned tables on subscribers (Amit Langote)

  Previously, subscribers could only receive rows into non-partitioned tables.

• Allow values to be used as partitioning expressions (Amit Langote)

 Indexes

• More efficiently store duplicates in btree indexes (Anastasia Lubennikova, Peter Geoghegan)

  This allows efficient btree indexing of low cardinality columns by storing duplicate keys only once. Users upgrading with pg_upgrade will need to use to make use of this feature.

• Allow GiST and SP-GiST indexes for box/point distance lookups (Nikita Glukhov)

• Allow indexes to more efficiently handle restrictions (Nikita Glukhov, Alexander Korotkov, Tom Lane, Julien Rouhaud)

• Allow index operator classes to take parameters (Nikita Glukhov)

• Allow to specify the GiST signature length and maximum number of integer ranges (Nikita Glukhov)

  Indexes created on four and eight-byte integer array, tsvector, pg_trgm, ltree, and hstore columns can now control these GiST index parameters, rather than using the defaults.

• Prevent indexes that use non-default collations from being added as a table's unique or primary key constraint (Tom Lane)

  The index and column collations must now match so the index's uniqueness matches the column's uniqueness.

 Optimizer

• Improve the optimizer's selectivity estimation for containment/match operators (Tom Lane)

• Allow setting statistics target for extended statistics (Tomas Vondra)

  This is controlled with the new command option . Previously this was computed based on more general statistics target settings.

• Allow use of multiple extended statistics objects in a single query (Tomas Vondra)

• Allow use of extended statistics objects for OR clauses and IN/ constant lists (Pierre Ducroquet, Tomas Vondra)

• Allow functions in clauses to be moved to their reference sites if they evaluate to constants (Alexander Kuzmenkov, Aleksandr Parfenov)

 General Performance

• Implement incremental sorting (James Coleman, Alexander Korotkov, Tomas Vondra)

  If a result is already sorted by several leading keys, this allows for batch sorting of additional trailing keys because the previous keys are already equal. This is controlled by enable_incremental_sort.

• Improve the performance of sorting inet values (Brandur Leach)

• Allow hash aggregation and grouping sets to use disk storage for large aggregation result sets (Jeff Davis)

  Previously, hash aggregation was avoided if it was expected to use more than work_mem memory. Now, a hash aggregation plan can be chosen despite that. The hash table will be spilled to disk if it exceeds times hash_mem_multiplier.

  This behavior is normally preferable to the old behavior. But if it is inferior for a particular query, behavior similar to previous Postgres releases can be obtained by increasing .

• Allow inserts to trigger autovacuum activity (Laurenz Albe, Darafei Praliaskouski)

  This new behavior reduces the work necessary when the table needs to be frozen and allows pages to be set as all-visible. All-visible pages allow index-only scans to access fewer heap rows.

• Add maintenance_io_concurrency to control I/O concurrency for maintenance operations (Thomas Munro)

• Allow skipping of

  Relations larger than wal_skip_threshold will have their files fsync'ed rather than generating

• Enable Unix-domain sockets support on Windows (Peter Eisentraut)

• Improve the performance when replaying commands when many tablespaces are in use (Fujii Masao)

• Improve performance for truncation of very large relations (Kirk Jamison)

• Improve speed of decompression and the retrieval of only the leading bytes of

  Previously,

• Improve performance of / (Martijn van Oosterhout)

• Improve the efficiency of removing duplicate events (Tom Lane)

• Use lookup tables to speed up integer to text conversion (David Fetter)

• Reduce memory usage for query strings that contain multiple

 Monitoring

• Allow , auto_explain, autovacuum, and pg_stat_statements to track

• Allow a sample of statements to be logged (Adrien Nayrat)

  A log_statement_sample_rate ratio of statements taking over log_min_duration_sample duration will be logged.

• Add the backend type to csvlog and optionally log_line_prefix log output (Peter Eisentraut)

• Improve control of prepared statement parameter logging (Alexey Bashtanov, Álvaro Herrera)

  The

• Make vacuum buffer counters 64-bits wide to avoid overflow (Álvaro Herrera)

• Allow function call backtraces of errors to be logged (Peter Eisentraut, Álvaro Herrera)

  Server variable backtrace_functions specifies which C functions should generate backtraces on error.

• Add and aggregates for (Fabrízio de Royes Mello)

  This is useful for monitoring queries.

 System Views

 Wait Events

• Add wait event for (Thomas Munro)

• Add wait event VacuumDelay to report on cost-based vacuum delay (Justin Pryzby)

• Add wait events for

  The new events are BackupWaitWalArchive and RecoveryPause.

• Add wait events RecoveryConflictSnapshot and RecoveryConflictTablespace to monitor recovery conflicts (Masahiko Sawada)

• Improve performance of wait events on

• Only allow superusers to view the ssl_passphrase_command setting (Insung Moon)

  This was changed as a security precaution.

• Change the server's default minimum

  This is controlled by ssl_min_protocol_version.

 Server Configuration

• Tighten rules on which utility commands are possible in default_transaction_read_only mode (Robert Haas)

  This also increases the number of utility commands that can run in parallel queries.

• Allow allow_system_table_mods to be changed after server start (Peter Eisentraut)

• Disallow non-superusers from modifying system tables when allow_system_table_mods is set (Peter Eisentraut)

  Previously, if allow_system_table_mods was set at server start, non-superusers could issue // commands on system tables.

 Streaming Replication and Recovery

• Allow streaming replication configuration settings to be changed by reload (Sergei Kornilov)

  Previously, a server restart was required to change primary_conninfo and primary_slot_name.

• Allow

  This behavior can be enabled using wal_receiver_create_temp_slot.

• Allow replication slot storage to be limited by max_slot_wal_keep_size (Kyotaro Horiguchi)

  Replication slots that exceed this value are invalidated.

• Allow standby promotion to cancel any requested pause (Fujii Masao)

  Previously, promotion could not happen while the standby was in paused state.

• Generate an error if recovery does not reach the specified recovery target (Leif Gunnar Erlandsen, Peter Eisentraut)

  Previously, the end of the

• Allow control over how much memory is used by logical decoding before it is spilled to disk (Tomas Vondra, Dilip Kumar, Amit Kapila)

  This is controlled by logical_decoding_work_mem.

• Allow

  This is enabled using ignore_invalid_pages.

 Utility Commands

• Allow to process indexes in parallel (Masahiko Sawada, Amit Kapila)

  The new option controls this.

• Allow to use to return any additional rows that match the last result row (Surafel Temesgen)

• Report planning-time buffer usage in 's output (Julien Rouhaud)

• Have propagate 's property to created tables (Ildar Musin, Chris Travers)

• When using on a partitioned table, do not check permissions on the child tables (Amit Langote)

• Allow on inserts into identity columns (Dean Rasheed)

• Add clause to remove generated properties from columns (Peter Eisentraut)

• Fix bugs in when later clauses overlap changes made by earlier clauses in the same command (Tom Lane)

• Add syntax to rename view columns (Fujii Masao)

  This was previously possible only using .

• Add options useful for extensions, like

• Add option (Peter Eisentraut)

  This combines existing options and into a single option.

• Allow to disconnect users so drop succeeds (Pavel Stehule, Amit Kapila)

  This is enabled by .

• Add C structure member to record updated columns to C triggers (Peter Eisentraut)

 Data Types

• Add polymorphic data types for use by functions requiring compatible arguments (Pavel Stehule)

  The new data types are anycompatible, anycompatiblearray, anycompatiblenonarray, and anycompatiblerange.

• Add

  The xid data type is only four bytes so does not show the transaction epoch.

• Add data type regcollation and helper functions for system collations (Julien Rouhaud)

• Use the glibc version in some cases as the collation version (Thomas Munro)

  If the glibc version changes, a warning will be issued when a mismatching collation is used.

• Add support for collation versions on Windows (Thomas Munro)

• Allow values values to have their members extracted with suffix notation (Tom Lane)

  For example, returns 4.

 Functions

• Add alternate version of with special handling (Andrew Dunstan)

  The new function, , allows null new values to either set the specified key to

• Add jsonpath . method (Nikita Glukhov, Teodor Sigaev, Oleg Bartunov, Alexander Korotkov)

  This allows json values to be converted to timestamps, which can then be processed in jsonpath expressions. This also adds jsonpath functions that support time zone-aware output.

• Add

• Allow Unicode escapes, e.g., E'\u####', U&'\####', to specify any character available in the database encoding, even when the database encoding is not

  The Unicode characters must be available in the database encoding.

• Allow and to recognize non-English month/day names (Juan José Santamaría Flecha, Tom Lane)

  The names recognized are the same as those output by with the same format codes.

• Add format specifications FF1-FF6 to control display of 1-6 subsecond digits (Alexander Korotkov, Nikita Glukhov, Teodor Sigaev, Oleg Bartunov)

  These patterns can be used by , , and jsonpath's ..

• Add time format specification as an

• Add function to generate version 4 UUIDs (Peter Eisentraut)

  Previously

• Add greatest-common-denominator (gcd) and least-common-multiple (lcm) functions (Vik Fearing)

• Improve the performance and accuracy of square root and natural log (ln) output (Dean Rasheed)

• Add function that returns the number of digits to the right the decimal point that is required to represent the numeric value with full precision (Pavel Stehule)

• Add function to reduce the scale of a number by removing trailing zeros (Pavel Stehule)

• Add commutators of distance operators (Nikita Glukhov)

  For example, previously only point <-> line was supported, now line <-> point works too.

• Create xid8 versions of all transaction id functions (Thomas Munro)

  The old function names were kept for backward compatibility. DO WE HAVE NEW NAMES?

• Allow and to set bits beyond 256MB of bytea data (Movead Li)

• Allow advisory-lock functions to be used in some parallel operations (Tom Lane)

• Add the ability to remove an object's dependency on an extension (Álvaro Herrera)

  The object can be a function, materialized view, index, or trigger. The syntax is .

 PL/pgSQL

• Improve performance of simple PL/pgSQL expressions (Tom Lane, Amit Langote)

• Improve the performance of PL/pgSQL functions that use immutable expressions (Konstantin Knizhnik)

 Client Interfaces

• Allow libpq clients to require channel binding for encrypted connections (Jeff Davis)

  Using the libpq connection parameter forces the other end of the

• Add libpq connection parameters to control the min/max

  The settings are ssl_min_protocol_version and ssl_max_protocol_version. By default, the minimum

• Tighten libpq's overlength-line handling and comment detection for .pgpass files (Fujii Masao)

• Allow specification of passwords to unlock client certificates (Craig Ringer, Andrew Dunstan)

  This is specified by the sslpassword connection option.

• Allow

• Fix ecpg's directive to work correctly (Tom Lane)

  Previously it behaved the same as followed by , so that a successful previous branch of the same construct did not prevent expansion of the branch or following branches.

 Client Applications

 psql

• Add the transaction status (%x) to the default psql prompts (Vik Fearing)

• Allow the secondary psql prompt to be same number of spaces as the primary prompt (Thomas Munro)

  This is accomplished by setting PROMPT2 to %w.

• Allow \g and \gx to change any \pset output options for a single command (Tom Lane)

  This allows syntax like \g (expand=on), which is equivalent to \gx.

• Add psql commands to report operator classes and operator families (Sergey Cherkashin, Nikita Glukhov, Alexander Korotkov)

  The new commands are \dAc, \dAf, \dAo, and \dAp.

• Show table persistence in psql's \dt+ and related commands (David Fetter)

  In verbose mode, the table/index/view shows if the object is permanent, temporary, or unlogged.

• Improve output of psql\d for

• Adjust display of psql's \e query (Tom Lane)

  When exiting the editor, if the query doesn't end with a semicolon or \g, the query buffer contents will now be displayed.

• Add \warn command to psql (David Fetter)

  This is like \echo except that the text is sent to stderr instead of stdout.

• Add the PostgreSQL home page to command-line output (Peter Eisentraut)

 pgbench

• Allow pgbench to partition its 'accounts' table (Fabien Coelho)

  This allows performance testing of partitioning.

• Add pgbench command \aset, which behaves like \gset, but for multiple queries (Fabien Coelho)

• Allow pgbench to generate its data server-side, rather than client side (Fabien Coelho)

• Allow pgbench to dump script contents using (Fabien Coelho)

 Server Applications

• Generate backup manifests for base backups, and verify them (Robert Haas)

  A new tool pg_verifybackup can verify backups.

• Have pg_basebackup estimate the total backup size by default (Fujii Masao)

  This computation allows to show progress, and can be disabled by using the option. Previously, this computation happened only if was used.

• Add pg_rewind option to configure standbys (Paul Guo, Jimmy Yih, Ashwin Agrawal)

  This matches pg_basebackup's option.

• Allow pg_rewind to use the target cluster's restore_command to retrieve needed

  This is enabled using the / option.

• Have pg_rewind automatically run crash recovery before rewinding (Paul Guo, Jimmy Yih, Ashwin Agrawal)

  This can be disabled by using .

• Increase information reported by pg_waldump (Fujii Masao)

• Add pg_waldump option to suppress non-error output (Andres Freund, Robert Haas)

• Add pg_dump option to dump data from foreign servers (Luis Carril)

• Allow vacuum commands run by vacuumdb to operate in parallel mode (Masahiko Sawada)

  This is enabled with the new option.

• Allow reindexdb to operate in parallel (Julien Rouhaud)

  Parallel mode is enabled with the new option.

• Allow dropdb to force disconnections so the drop succeeds (Pavel Stehule)

  This is enabled with the option.

• Remove and from createuser (Alexander Lakhin)

  The long-supported options for this are called and .

• Use the directory of the pg_upgrade binary as the default new 'bindir' location when running pg_upgrade (Daniel Gustafsson)

 Documentation

• Add a glossary to the documentation (Corey Huinker, Jürgen Purtz, Roger Harkavy, Álvaro Herrera)

• Reformat tables containing function information for better clarity (Tom Lane)

• Upgrade to use DocBook 4.5 (Peter Eisentraut)

 Source Code

• Add support for building on Visual Studio 2019 (Haribabu Kommi)

• Add build support for MSYS2 (Peter Eisentraut)

• Add compare_exchange and fetch_add assembly language code for Power PC compilers (Noah Misch)

• Update Snowball stemmer dictionaries used by full text search (Panagiotis Mavrogiorgos)

  This adds Greek stemming and improves Danish and French stemming.

• Remove support for Windows 2000 (Michael Paquier)

• Remove support for non-

• Remove support for Python versions 2.5.X and earlier (Peter Eisentraut)

• Remove support for OpenSSL 0.9.8 and 1.0.0 (Michael Paquier)

• Remove support option (Peter Eisentraut)

  This was needed for previously supported version-zero functions.

• Remove configure option (Peter Eisentraut)

  This was needed for previously supported version-zero functions.

• Add the query string to planner hook functions (Pascal Legrand, Julien Rouhaud)

• Add command hook (Yuli Khodorkovskiy)

• Add

• Allow building with no predefined Unix-domain socket directory (Peter Eisentraut)

• Reduce the probability of SysV resource key collision on Unix platforms (Tom Lane)

• Use operating system functions to cleanly erase memory that contains sensitive information (Peter Eisentraut)

  For example, this is used for clearing passwords stored in memory.

• Add "headerscheck" script to test C header-file compatibility (Tom Lane)

• Implement internal lists as arrays, rather than a chain of structures (Tom Lane)

  This improves performance for queries that access many object. The internal List

• Update Windows build scripts to use the modern flag for

• Change the API for (Tom Lane, Pavel Borisov)

  callbacks must now provide ternary (yes/no/maybe) logic. Calculating NOT queries accurately is now the default.

 Additional Modules

• Allow extensions to be specified as trusted (Tom Lane)

  Such extensions can be installed in a database by users with creation rights, even if they are not superusers. This change also removes the system catalog.

• Remove support for upgrading "unpackaged" extensions (Tom Lane)

• Allow non-superusers to connect to postgres_fdw foreign servers without using a password (Craig Ringer)

  Specifically, allow to set to false. Care must still be taken to avoid non-superusers from using superuser credentials to connect to the foreign server.

• Allow postgres_fdw to use certificate authentication (Craig Ringer)

  Different users can use different certificates.

• Allow sepgsql to control access to the command (Yuli Khodorkovskiy)

• Add extension bool_plperl which transforms

• Have pg_stat_statements treat as distinct from those without (Andrew Gierth, Vik Fearing)

• Allow pg_stat_statements to optionally track the planning time of statements (Julien Rouhaud, Pascal Legrand, Thomas Munro, Fujii Masao)

  Previously only execution time was tracked.

• Overhaul ltree's lquery syntax to treat (!) more logically (Filip Rembialkowski, Tom Lane, Nikita Glukhov)

  Also allow non-* queries to use a numeric range ({}) of matches.

• Add support for binary I/O of ltree, lquery, and ltxtquery types (Nino Floris)

• Add option to dict_int extension to ignore the sign of integers (Jeff Janes)

• Add adminpack function to allow fsync'ing a file (Fujii Masao)

• Add pageinspect functions to output / values in human-readable format (Craig Ringer, Sawada Masahiko, Michael Paquier)

• Add btree index deduplication processing columns to pageinspect output (Peter Geoghegan)

 Acknowledgments

The following individuals (in alphabetical order) have contributed to this release as patch authors, committers, reviewers, testers, or reporters of issues.

• Adam Lee
• Adam Scott
• Adé Heyward
• Adrien Nayrat
• Ahsan Hadi
• Alastair McKinley
• Aleksandr Parfenov
• Alex Aktsipetrov
• Alex Macy
• Alex Shulgin
• Alexander Korotkov
• Alexander Kukushkin
• Alexander Kuzmenkov
• Alexander Lakhin
• Alexey Bashtanov
• Alexey Kondratov
• Álvaro Herrera
• Amit Kapila
• Amit Khandekar
• Amit Langote
• Amul Sul
• Anastasia Lubennikova
• Andreas Joseph Krogh
• Andreas Karlsson
• Andreas Kunert
• Andreas Seltenreich
• Andrei Zubkov
• Andres Freund
• Andrew Dunstan
• Andrew Gierth
• Andrey Borodin
• Andrey Klychkov
• Andrey Lepikhov
• Anna Akenteva
• Anna Endo
• Anthony Nowocien
• Anton Vlasov
• Antonin Houska
• Ants Aasma
• Arne Roland
• Arnold Müller
• Arseny Sher
• Arthur Nascimento
• Arthur Zakirov
• Asaba Takanori
• Ashutosh Bapat
• Ashutosh Sharma
• Ashwin Agrawal
• Asif Rehman
• Asim Praveen
• Atsushi Torikoshi
• Augustinas Jokubauskas
• Austin Drenski
• Basil Bourque
• Beena Emerson
• Ben Cornett
• Benjie Gillam
• Benoît Lobréau
• Bernd Helmle
• Bharath Rupireddy
• Bhargav Kamineni
• Binguo Bao
• Brad DeJong
• Brandur Leach
• Brent Bates
• Brian Williams
• Bruce Momjian
• Cameron Ezell
• Cary Huang
• Chapman Flack
• Charles Offenbacher
• Chen Huajun
• Chenyang Lu
• Chris Bandy
• Chris Travers
• Christoph Berg
• Christophe Courtois
• Corey Huinker
• Craig Ringer
• Cuiping Lin
• Dagfinn Ilmari Mannsåker
• Daniel Fiori
• Daniel Gustafsson
• Daniel Vérité
• Daniel Westermann
• Darafei Praliaskouski
• Daryl Waycott
• Dave Cramer
• David Christensen
• David Fetter
• David G. Johnston
• David Gilman
• David Harper
• David Rowley
• David Steele
• David Zhang
• Davinder Singh
• Dean Rasheed
• Denis Stuchalin
• Dent John
• Didier Gautheron
• Dilip Kumar
• Dmitry Belyavsky
• Dmitry Dolgov
• Dmitry Ivanov
• Dmitry Telpt
• Dmitry Uspenskiy
• Dominik Czarnota
• Dongming Liu
• Ed Morley
• Edmund Horner
• Emre Hasegeli
• Eric Gillum
• Erik Rijkers
• Erwin Brandstetter
• Ethan Waldo
• Etsuro Fujita
• Eugen Konkov
• Euler Taveira
• Fabien Coelho
• Fabrízio de Royes Mello
• Felix Lechner
• Filip Janus
• Filip Rembialkowski
• Frank Gagnepain
• Georgios Kokolatos
• Gilles Darold
• Greg Nancarrow
• Grigory Smolkin
• Guancheng Luo
• Guillaume Lelarge
• Hadi Moshayedi
• Haiying Tang
• Hamid Akhtar
• Hans Buschmann
• Haribabu Kommi
• Heath Lord
• Heikki Linnakangas
• Hironobu Suzuki
• Hugh McMaster
• Hugh Ranalli
• Hugh Wang
• Ian Barwick
• Ibrar Ahmed
• Ildar Musin
• Insung Moon
• Ireneusz Pluta
• Isaac Morland
• Ivan Kartyshov
• Ivan Panchenko
• Ivan Sergio Borgonovo
• Jaime Casanova
• James Coleman
• James Gray
• James Inform
• James Lucas
• Jaroslav Sivy
• Jeevan Chalke
• Jeevan Ladhe
• Jeff Davis
• Jeff Janes
• Jehan-Guillaume de Rorthais
• Jeremy Schneider
• Jeremy Smith
• Jerry Sievers
• Jesper Pedersen
• Jesse Zhang
• Jian Zhang
• Jie Zhang
• Jim Nasby
• Jimmy Yih
• Jobin Augustine
• Joe Conway
• John Hsu
• John Naylor
• Jon Jensen
• Jonathan Katz
• Jorge Gustavo Rocha
• Josef Šimánek
• Joseph Nahmias
• Juan José Santamaría Flecha
• Julian Backes
• Julien Rouhaud
• Jürgen Purtz
• Justin King
• Justin Pryzby
• Karl O. Pinc
• Keisuke Kuroda
• Keith Fiske
• Ken Tanzer
• Kirill Bychik
• Kirk Jamison
• Konstantin Knizhnik
• Kuntal Ghosh
• Kyle Kingsbury
• Kyotaro Horiguchi
• Lars Kanis
• Laurenz Albe
• Leif Gunnar Erlandsen
• Li Japin
• Liudmila Mantrova
• Lucas Viecelli
• Luis M. Carril
• Lukáš Sobotka
• Maciek Sakrejda
• Magnus Hagander
• Mahadevan Ramachandran
• Mahendra Singh Thalor
• Manuel Rigger
• Marc Munro
• Marcos David
• Marina Polyakova
• Mark Dilger
• Mark Wong
• Marko Tiikkaja
• Markus Winand
• Marti Raudsepp
• Martijn van Oosterhout
• Masahiko Sawada
• Masahiro Ikeda
• Masao Fujii
• Mateusz Guzik
• Matt Jibson
• Matteo Beccati
• Maxence Ahlouche
• Melanie Plageman
• Michael Banck
• Michael Luo
• Michael Meskes
• Michael Paquier
• Michail Nikolaev
• Mike Palmiotto
• Mithun Cy
• Movead Li
• Nathan Bossart
• Nazli Ugur Koyluoglu
• Neha Sharma
• Nicola Contu
• Nicolás Alvarez
• Nikhil Sontakke
• Nikita Glukhov
• Nikolay Shaplov
• Nino Floris
• Noah Misch
• Noriyoshi Shinoda
• Oleg Bartunov
• Oleksii Kliukin
• Ondrej Jirman
• Panagiotis Mavrogiorgos
• Pascal Legrand
• Patrick McHardy
• Paul Guo
• Paul Jungwirth
• Paul Ramsey
• Paul Spencer
• Pavan Deolasee
• Pavel Borisov
• Pavel Luzanov
• Pavel Stehule
• Pavel Suderevsky
• Peifeng Qiu
• Pengzhou Tang
• Peter Billen
• Peter Eisentraut
• Peter Geoghegan
• Peter Smith
• Petr Fedorov
• Petr Jelínek
• Phil Bayer
• Philip Semanchuk
• Pierre Ducroquet
• Pierre Giraud
• Piotr Gabriel Kosinski
• Piotr Wlodarczyk
• Prabhat Sahu
• Quan Zongliang
• Quentin Rameau
• Rafael Castro
• Rafia Sabih
• Raj Mohite
• Rajkumar Raghuwanshi
• Ramanarayana M
• Ranier Vilela
• Rares Salcudean
• Raúl Marín Rodríguez
• Raymond Martin
• Reijo Suhonen
• Richard Guo
• Robert Ford
• Robert Haas
• Robert Treat
• Robins Tharakan
• Roger Harkavy
• Roman Peshkurov
• Rui DeSousa
• Rui Hai Jiang
• Rushabh Lathia
• Ryan Lambert
• Ryohei Takahashi
• Scott Ribe
• Sean Farrell
• Sehrope Sarkuni
• Sergei Agalakov
• Sergei Kornilov
• Sergey Cherkashin
• Shawn Debnath
• Shawn Wang
• Shay Rojansky
• Shenhao Wang
• Simon Riggs
• Slawomir Chodnicki
• Soumyadeep Chakraborty
• Stéphane Lorek
• Stephen Frost
• Steve Rogerson
• Steven Winfield
• Surafel Temesgen
• Suraj Kharage
• Takao Fujii
• Takatsuka Haruka
• Takayuki Tsunakawa
• Takuma Hoshiai
• Tatsuhito Kasahara
• Tatsuo Ishii
• Tatsuro Yamada
• Taylor Vesely
• Teodor Sigaev
• Tham Nguyen
• Thibaut Madelaine
• Thom Brown
• Thomas Kellerer
• Thomas Munro
• Tiago Anastacio
• Tim Clarke
• Tim Möhlmann
• Tom Ellis
• Tom Gottfried
• Tom Lane
• Tomas Vondra
• Tuomas Leikola
• Tushar Ahuja
• Victor Wagner
• Victor Yegorov
• Vignesh C
• Vik Fearing
• Vinay Banakar
• Vladimir Leskov
• Vladimir Sitnikov
• Vyacheslav Makarov
• Vyacheslav Shablistyy
• Will Leinweber
• William Crowell
• Wyatt Alt
• Yang Xiao
• Yaroslav Schekin
• Yi Huang
• Yigong Hu
• Yoann La Cancellera
• Yoshikazu Imai
• Yu Kimura
• Yugo Nagata
• Yuli Khodorkovskiy
• Yusuke Egashira
• Yuya Watari
• Yuzuko Hosoya
• ZhenHua Cai

Release date: 2020-08-13

This release contains a variety of fixes from 12.3. For information about new features in major release 12, see Version 12.0.

 Migration to Version 12.4

A dump/restore is not required for those running 12.X.

However, if you are upgrading from a version earlier than 12.2, see Version 12.2.

 Changes

• Set a secure in logical replication walsenders and apply workers (Noah Misch)

  A malicious user of either the publisher or subscriber database could potentially cause execution of arbitrary SQL code by the role running replication, which is often a superuser. Some of the risks here are equivalent to those described in CVE-2018-1058 or CVE-2018-1058, and are mitigated in this patch by ensuring that the replication sender and receiver execute with empty settings. (As with CVE-2018-1058 or CVE-2018-1058, that change might cause problems for under-qualified names used in replicated tables' DDL.) Other risks are inherent in replicating objects that belong to untrusted roles; the most we can do is document that there is a hazard to consider. (CVE-2020-14349 or CVE-2020-14349)

• Make contrib modules' installation scripts more secure (Tom Lane)

  Attacks similar to those described in CVE-2018-1058 or CVE-2018-1058 could be carried out against an extension installation script, if the attacker can create objects in either the extension's target schema or the schema of some prerequisite extension. Since extensions often require superuser privilege to install, this can open a path to obtaining superuser privilege. To mitigate this risk, be more careful about the used to run an installation script; disable within the script; and fix catalog-adjustment queries used in some contrib modules to ensure they are secure. Also provide documentation to help third-party extension authors make their installation scripts secure. This is not a complete solution; extensions that depend on other extensions can still be at risk if installed carelessly. (CVE-2020-14350 or CVE-2020-14350)

• Fix edge cases in partition pruning (Etsuro Fujita, Dmitry Dolgov)

  When there are multiple partition key columns, generation of pruning tests could misbehave if some columns had no constraining clauses or multiple constraining clauses. This could lead to server crashes, incorrect query results, or assertion failures.

• Fix construction of parameterized BitmapAnd and BitmapOr index scans on the inside of partition-wise nestloop joins (Tom Lane)

  A plan in which such a scan needed to use a value from the outside of the join would usually crash at execution.

• Fix incorrect plan execution when a partitioned table is subject to both static and run-time partition pruning in the same query, and a new partition is added concurrently with the query (Amit Langote, Tom Lane)

• In logical replication walsender, fix failure to send feedback messages after sending a keepalive message (Álvaro Herrera)

  This is a relatively minor problem when using built-in logical replication, because the built-in walreceiver will send a feedback reply (which clears the incorrect state) fairly frequently anyway. But with some other replication systems, such as pglogical, it causes significant performance issues.

• Fix firing of column-specific triggers in logical replication subscribers (Tom Lane)

  The code neglected to account for the possibility of column numbers being different between the publisher and subscriber tables, so that if those were indeed different, wrong decisions might be made about which triggers to fire.

• Update oldest xmin and LSN values during (Michael Paquier)

  This function previously failed to do that, possibly preventing resource cleanup (such as removal of no-longer-needed WAL segments) after manual advancement of a replication slot.

• Fix slow execution of (Tom Lane)

  The phrase-search fix added in our previous set of minor releases could cause to take unreasonable amounts of time for long documents; to make matters worse, the query was not cancellable within the troublesome loop.

• Ensure the function can be interrupted by query cancel (Joe Conway)

• Fix to not include a carriage return () in its result on Windows (Tom Lane)

• Ensure that and related functions read until EOF is reached (Joe Conway)

  Previously, if not given a specific data length to read, these functions would stop at whatever file length was reported by . That's unhelpful for pipes and other sorts of virtual files.

• Forbid numeric values in computations (Alexander Korotkov)

  Neither SQL nor JSON have the concept of (not-a-number), but the code attempted to allow such values anyway. This necessarily leads to nonstandard behavior, so it seems better to reject such values at the outset.

• Handle single or inputs correctly in floating-point aggregates (Tom Lane)

  The affected aggregates are , , , , , , , , , and . The correct answer in such cases is , but an algorithmic change introduced in PostgreSQL v12 had caused these aggregates to produce zero instead.

• Fix mis-handling of inputs during parallel aggregation on -type columns (Tom Lane)

  If some partial aggregation workers found only s while others found only non-s, the results were combined incorrectly, possibly leading to the wrong overall result (i.e., not when it should be).

• Reject time-of-day values greater than 24 hours (Tom Lane)

  The intention of the datetime input code is to allow “24:00:00” or equivalently “23:59:60”, but no larger value. However, the range check was miscoded so that it would accept “23:59:60.” with nonzero fractional-second . In timestamp values this would result in wrapping into the first second of the next day. In and values, the stored value would actually be more than 24 hours, causing dump/reload failures and possibly other misbehavior.

• Undo double-quoting of index names in 's non-text output formats (Tom Lane, Euler Taveira)

• Fix 's accounting for resource usage, particularly buffer accesses, in parallel workers in a plan using nodes (Jehan-Guillaume de Rorthais)

• Fix timing of constraint revalidation in (David Rowley)

• At-a-Glance

• Command References

• Configuration Examples and TechNotes

  • Add Domain-Specific Disclaimers on the ESA
  • Administrative details on 'trailblazer' CLI command for Cisco Security Management Appliance (SMA)
  • Are content filters and message filters case insensitive?
  • Best Practices Guide for Anti-Spoofing
  • Best Practices Guide for Incoming and Outgoing Content Filters
  • Best Practices for Centralized Policy, Virus and Outbreak Quarantines Setup and Migration from ESA to SMA
  • Best Practices to Secure an ESA
  • Blacklist a Malicious or Problem Sender on the ESA
  • Bypass SBRS for Specific Hosts and Continue to Scan for SPAM
  • Can I whitelist or blacklist individual users via email addresses in the HAT?
  • Can a Message Filter divert messages to the Cisco Email Security Appliance (ESA) Spam Quarantine?
  • Can the ESA deliver SMTP traffic to a different port number other than 25?
  • Can the smtproutes command be used for load balancing?
  • Cisco Email Security Appliance (ESA) Anti-Spam Efficacy Checklist
  • Cisco Email Security Plug-In Installation Using Custom Configuration Files
  • Cisco RES: Account Provisioning for Virtual, Hosted, and Hardware ESA Configuration Example
  • Cisco Success Network (CSN) on Cisco Email Security
  • Cloud Web Security: Configure user/group attributes with PingFederate and ADFS Whilst using SAML.
  • Common Configuration Errors on the ESA
  • Comprehensive Spam Quarantine Setup Guide on Email Security Appliance (ESA) and Security Management Appliance (SMA)
  • Configuration Best Practices for CES ESA
  • Configuration Change for Content Filters acting on WBRS Neutral Reputation
  • Configure Beta ESA to Accept Production ESA Traffic
  • Configure Cisco Email Security and Security Management for Staging Updates
  • Configure ESA to Prefer PFS
  • Configure LDAP SMTPAUTH To Authenticate External Users and Relay Mail
  • Configure Static File Reputation Host or an Alternate File Reputation Cloud Server Pool on ESA
  • Configure TLS for Inbound Connection Encryption on an ESA Listener
  • Configuring SCP push of mail logs on ESA
  • Content Security FAQ: How do you access the CLI on a Content Security appliance?
  • Create a Certificate Signing Request on an ESA
  • Create or join ESAs to a cluster without PTR records
  • Customize Cisco Email Security Reporting and Encryption Plug-In Buttons in Outlook
  • DLP HIPAA Policy Does Not Match a SSN
  • DMARC Architecture - Identifier Alignment
  • Decrease MTU on the Cisco ESA
  • Detect Spoofed Email Messages on the ESA and Create Exceptions For Senders That Are Allowed to Spoof
  • Does SenderBase function correctly behind NAT?
  • Does adjusting the retention period on a system quarantine affect messages already in the quarantine?
  • Does the ESA hardware platform support Fiber network interfaces?
  • ESA - Configure DKIM Signing
  • ESA - Replace Existing DKIM Key with no downtime
  • ESA - Using a message filter to take action on large messages with no attachments
  • ESA Block Blank From: Addresses Configuration Example
  • ESA Cluster Requirements and Setup
  • ESA Domain Debug Logs Configuration Example
  • ESA Email Encryption Configuration Example
  • ESA FAQ: How do I force a download of Sophos or McAfee Anti-Virus updates immediately?
  • ESA FAQ: How do you import a configuration file into a new appliance?
  • ESA FAQ: How do you whitelist recipient or sender emails?
  • ESA FAQ: What are the levels of administrative access available on the ESA?
  • ESA FAQ: What are the requirements for setting up a cluster?
  • ESA FAQ: What does it mean when my ESA system indicator light blinks orange?
  • ESA FAQ: What does the SBRS value of "none" mean, and how can you detect these scores?
  • ESA FAQ: What is a mail flow policy?
  • ESA FAQ: What is debounce timeout?
  • ESA FAQ: What is the maximum number of appliances supported in a Centralized Management Cluster?
  • ESA Outbound Traffic Relay Configuration Example
  • Email Security Appliance Round-Robins to the Next SMTP Route If a Destination Mail Server is Still Responsive
  • Exclude Words When Using Dictionary Message Filters
  • Exempt IP Addresses/Domains/Email Addresses from the ESA Bounce Configuration
  • HAT Delayed Rejection FAQ
  • How Can I Automate or Script Configuration File Backups?
  • How Do I Customize the End User Notification Pages?
  • How Do I Verify that the ESA is Accepting Email?
  • How are SMTP authentication events logged?
  • How can I alter what ciphers are used with the Graphical User Interface (GUI)? Can I disable SSL v2 for the GUI?
  • How can I configure round robin style outbound connections in Cisco Email Security Appliance?
  • How can I identify and address a mail loop situation on the ESA?
  • How can I limit the delivery rate on my Cisco Email Security Appliance (ESA) to certain domains or hosts?
  • How can I prevent the backend infrastructure from being exposed in outbound messages?
  • How can I rate limit email based on the sender's email address?
  • How can I verify that my TCPREFUSE or REJECT access rule is working?
  • How do I add a new message filter to my Cisco Email Security Appliance (ESA)?
  • How do I allow some messages from a sender with a low SBRS score, but block all other messages?
  • How do I backup the configuration on a Cisco Web or Email Security Appliance?
  • How do I blacklist and reject an email server based on geolocation?
  • How do I blacklist or drop a sending domain using Incoming Mail Policy and Content Filter?
  • How do I block recipient address with wildcards?
  • How do I bypass encryption in a content filter and DLP?
  • How do I capture and block embedded hyperlinks that have executables?
  • How do I change the media speed settings on my Cisco Content Security Appliance
  • How do I configure a relay host on the ESA for outbound mail?
  • How do I configure my Cisco Email Security Appliance (ESA) to query public DNS-based Block Lists (DNSBL)?
  • How do I configure the ESA to route incoming email to my corporate email servers?
  • How do I configure the ESA to skip anti-spam and/or anti-virus scanning for my trusted senders?
  • How do I connect to my appliance using a serial cable?
  • How do I control body and attachment scanning in filters?
  • How do I control the IP interface used for message delivery?
  • How do I create a content filter that applies to *all* incoming or outgoing mail ... ?
  • How do I create and configure logs on a Cisco Email Security Appliance (ESA)?
  • How do I delete entries from the Recipient Access Table (RAT)?
  • How do I determine which version of software is running on my Cisco Web/Email/Management Security Appliance?
  • How do I determine which viruses Cisco Email Security Appliance (ESA) is protecting against?
  • How do I email a copy of the configuration on a Cisco Content Security Appliance?
  • How do I filter messages that are too large?
  • How do I install feature keys on a Cisco Email or Web Security Appliance?
  • How do I keep copies of messages matched by my message filter?
  • How do I log message headers?
  • How do I monitor the health of the ESA?
  • How do I prevent my ESA from being used as an open relay?
  • How do I stamp a footer / disclaimer on email messages leaving my network?
  • How do I stop duplicate disclaimer stamping?
  • How do I stop the ESA from adding a received header to my outgoing email messages?
  • How do I test a message or content filter to ensure it is working as designed?
  • How do I test if my domain supports TLS with CRES?
  • How do I trigger CRES encryption in Microsoft Outlook using the confidential flag?
  • How do I write more efficient message filters?
  • How do you Whitelist a Trusted Sender?
  • How do you automate log transfers?
  • How do you create an LDAP group query on the ESA?
  • How do you use LDAP Accept Query to validate the sender of relayed messages?
  • How do you use Softerra LDAP browser to view LDAP information for company or individuals?
  • How do you use pscp on Microsoft Windows?
  • How does the Exception Table on the ESA work?
  • How to Block Content Type Based Character Sets
  • How to Import Partial Configurations Into the ESA?
  • How to accept mail for additional internal domains on the ESA?
  • How to add or modify NTP on ESA/WSA/SMA
  • How to add the Company Logo to the secure envelope on the Cisco Encryption Appliance (formerly IEA)
  • How to allow simulated phishing platform campaigns through the Cisco Email Security Appliance
  • How to configure SSH Public Key Authentication for login to the ESA without a password
  • How to configure Virtual Gateways?
  • How to use LDAP Accept Query to validate the recipients of inbound messages using Microsoft Active Directory (LDAP)?
  • I have added the domain example.com to the WHITELIST sender group, why is it not working?
  • IEA Release 6.3 License Keys
  • Image Analysis Feature
  • Is SenderBase on the ESA another DNS RBL?
  • Is it possible to apply multiple certificates on an ESA and assign them to different interfaces or listeners?
  • Is there a filter condition matching on the file size of single attachment(s) instead of message size?
  • Is there a way to provide for failover or load balancing of LDAP servers?
  • Mailbox Auto Remediation features 13.0 AsyncOS and newer: On-Premise Exchange, Hybrid Multi-tenant and Chained Queries
  • Message Content that Matches the Word on a Content Filter
  • On the ESA, What is the Difference between REJECT and TCPREFUSE?
  • Rate Limit Your Own Outbound Mail with Destination Control Settings
  • Reset Your Administrator Password and Unlock the Administrator User Account
  • Safe Print for Email Security Appliance
  • Set Up a Custom DLP Policy to Detect Formatted and Unformatted Social Security Numbers
  • Simple Mail Filter on How to Quarantine a Message
  • Sophos Anti-virus Updates on Cisco Security Appliance are Different from Those Available on the Sophos Web Site
  • Spam Quarantine Notifications
  • Spoof Protection using Sender Verification
  • Transfer the License from the Current Cisco Content Security Appliance to an RMA Appliance
  • Troubleshooting winmail.dat Attachments
  • URL Filtering DNS lookups function and the impact of disabling DNS lookups
  • Using TLSVERIFY to Troubleshoot TLS Delivery Issues
  • Using Virtual Gateway Technology on the Cisco Email Security Appliance (ESA)
  • Verify That DKIM Works
  • What can I do about spam with no subject or message body
  • What causes "collision error" alerts?
  • What does "ICID lost" or "ICID close" mean?
  • What does DNS Lame Delegation error mean in my mail logs?
  • What happens to ESA reporting and tracking data collected on a SMA after the ESA is replaced?
  • What happens to log files on the Cisco Content Security Appliance that are pushed via FTP or SCP?
  • What happens to messages in the ISQ when the retention time is changed?
  • What international or multilingual capabilities does AsyncOS for Email provide on the ESA?
  • What is Cisco Anti-Spam's catch rate, false-positive rate, and throughput?
  • What is centralized management for and how can a centralized management cluster be created?
  • What is the relationship between "initial... wait" and "maximum... wait" values in bounceconfig
  • What kind of actions can I apply to an email message using message filters?
  • What types of encryption does the encrypted() filter rule detect?
  • What's the difference between the Outbreak and Virus quarantines?
  • What's the shortest period of time you can configure Sophos Anti-Virus IDE updates?
  • Which custom SMTP banner codes can be configured on the Cisco Email Security Appliance (ESA)?
  • Which messaging platforms does the Cisco Email Security Appliance (ESA) support?
  • Why am I receiving an error when loading a Cisco Email Security Appliance (ESA) C350 configuration file to a C370?
  • Why are disclaimers in footer displayed as attachments?
  • Why aren't encrypted Microsoft Word documents flagged by Sophos Anti-Virus?
  • Why do messages get delivered even if SPF verification fails?
  • Why is there no new version of AsyncOS shown when performing an upgrade?
  • Working with Message Filters

• Data Sheets

• End-of-Life and End-of-Sale Notices

  • English

    • End-of-Sale and End-of-Life Announcement for the Cisco ESA 12.0, 12.1,12.5 & SMA 12.0,12.5 releases
    • End-of-Sale and End-of-Life Announcement for the Cisco ESA 11.0.x, 11.1.x & SMA 11.0.x, 11.5.x
    • End-of-Sale and End-of-Life Announcement for the Cisco Email and Web Security Promotional PIDs
    • End-of-Sale and End-of-Life Announcement for the Cisco Email, Web and Security Management x90 Hardware Appliances
    • End-of-Sale and End-of-Life Announcement for the Cisco ESA AsyncOS 9.8.x
    • End-of-Sale and End-of-Life Announcement for the Cisco Email Cloudmark Anti-Spam
    • End-of-Sale and End-of-Life Announcement for the Cisco x170 and x80 Email, Web, and Content Security Management Hardware Appliances
    • End-of-Sale and End-of-Life Announcement for the Cisco ESA 10.x.x, SMA 10.0.x, 10.1.x
    • End-of-Sale and End-of-Life Announcement for the Cisco AsyncOS 9.5.x, 9.6.x, and 9.7.x for the Cisco Email Security Appliance
    • End-of-Sale and End-of-Life Announcement for the Cisco Email, Web, and Security Management x70 Appliances
    • End-of-Sale and End-of-Life Announcement for the AsyncOS 8.0.2 and 9.1.x for the Cisco Email Security Appliance
    • End-of-Sale and End-of-Life Announcement for the AsyncOS 7.8 and 8.5.x for the Cisco Email Security Appliance and AsyncOS 9.0.x and 9.1.x for the Cisco Content Security Management Appliance
    • End-of-Sale and End-of-Life Announcement for the AsyncOS 8.0.1 for Cisco Email Security Appliance, and AsyncOS 8.1.1 for Cisco Content Security Management Appliance
    • End-of-Sale and End-of-Life Announcement for the Cisco IronPort x50 Appliance
    • End-of-Sale and End-of-Life Announcement for the Cisco IronPort x60 Appliance
    • End-of-Sale and End-of-Life Announcement for the AsyncOS 7.6.x for Cisco Email Security Appliance
    • End-of-Sale and End-of-Life Announcement for the Cisco Email, Web, and Security Management x70 Accessories

  • French - Canadian

    • Annonce d’arrêt de commercialisation et de fin de vie de Cisco ESA 12.0, 12.1,12.5 & SMA 12.0,12.5 releases
    • Annonce d’arrêt de commercialisation et de fin de vie de Cisco ESA 11.0.x,11.1.x & SMA 11.0.x, 11.5.x
    • Annonce d’arrêt de commercialisation et de fin de vie de Cisco Email, Web and Security Management x90 Hardware Appliances
    • Annonce d’arrêt de commercialisation et de fin de vie de Cisco ESA AsyncOS 9.8.x
    • Annonce d’arrêt de commercialisation et de fin de vie de Cisco Email Cloudmark Anti-Spam
    • Annonce d’arrêt de commercialisation et de fin de vie de Cisco ESA 10.x.x, SMA 10.0.x, 10.1.x
    • Annonce d’arrêt de commercialisation et de fin de vie des dispositifs de sécurité de messagerie courriel Cisco AsyncOS 7.8 et 8.5.x et des dispositifs Cisco AsyncOS de gestion de la sécurité des contenus 9.0.x et 9.1.x
    • Annonce d’arrêt de commercialisation et de fin de vie de Cisco AsyncOS 9.5.x, 9.6.x et 9.7.x pour le dispositif de sécurité de la messagerie Cisco Email Security Appliance
    • Annonce d’arrêt de commercialisation et de fin de vie de AsyncOS 8.0.2 et 9.1.x pour le dispositif de sécurité de messagerie Cisco

• End-User Guides