Monthly Release Notes - February 2020

Jump to:

Core Security


Core Impact

Version: 19.1.7

Feb 29, 2020

Enhancements
  • Assorted Improvements for Exploits: This update contains minor improvements and fixes to several exploit modules. (CVE-2019-11581)

  • AV Evasion Improvements V13: HTTP connections started to get detected, this update is an improvement for those connections to be stealthier.
  • New Exploits:
    • Microsoft Windows Remote Desktop DejaBlue DoS: A denial of service vulnerability exists in Remote Desktop Services -formerly known as Terminal Services- when an unauthenticated attacker connects to the target system using RDP and sends specially crafted requests. (CVE-2019-1181)

    • Microsoft Windows CoreShellComServerRegistrar Open Process Local Privilege Escalation Exploit: An elevation of privilege vulnerability exists when Windows Core Shell COM Server Registrar improperly handles COM calls. An attacker who successfully exploited this vulnerability could potentially set certain items to run at a higher level and thereby elevate permissions. To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take control of an affected system. The update addresses this vulnerability by correcting unprotected COM calls. (CVE-2019-1184)

    • Viper RGB Driver Read Write IO Ports DoS: The IOCTL Codes 0x80102050 and 0x80102054 allow a low privileges user to read/write 1/2/4 bytes from/to an IO port. This could be leveraged in a number of ways to ultimately run code with elevated privileges. (NOCVE-9999-127139)

    • Viper RGB Driver Kernel Buffer Overflow Local Privilege Escalation Exploit: This module exploits a buffer overflow vulnerability in Viper RGB MsIo64.sys vulnerability allows unprivileged local users to execute code with SYSTEM privileges. (CVE-2019-19452)

Other Fixes
  • WebApps Vulnerability Test Module Output fixes:
  • Cisco Data Center Network Manager HostEnclHandler getVmHostData SQL Injection Vulnerability Exploit Update: This module uses an authentication bypass and a SQL injection vulnerability in order to upload and execute a JSP file in the Wildfly virtual file system webapps directory. This update fixes OS detection when detecting DCNM version. (CVE-2019-15976)

Back to Top

 

GoAnywhere


Version 6.4.1
  • Added support for the X-Forwarded-For header on Admin and Web Clients.
  • Fixed an issue where the language would display English and would not change to the selected language on the Admin Client.
  • Fixed an encoding issue when submitting large Agent projects where JVM file.encoding is not UTF-8.
  • Fixed the behavior of inputting a single variable into the From field for a Send Email Task.
  • Fixed an issue where Agents would fail to connect to the MFT server if RSA FIPS was enabled.
  • Fixed an issue that could cause a null pointer error to occur during Web User self-registration.
  • Fixed an incorrect label on the Switch Database configuration page.
  • Fixed an issue where deleting an Excel file fails after running the Write Excel task with append.
  • Fixed an issue where the 'Remove my Access' menu item would not appear for a file owner in GoDrive. This issue was introduced in 6.4.0.
Version 6.4.0 - Beta
New Features
  • Added a reception awareness feature to AS4 servers to monitor for asynchronous receipts.
  • Added Triggers for AS4 events.
  • Created a new GoAnywhere Command Get Job Status API. This includes new GoAnywhere Command Get Job Status SOAP and REST web services.
  • Added a file chooser to the Web Client Brand configuration page.
Enhancements
  • Added authentication type to Admin User templates.
  • Added the ability to use KMS for the Admin server certificates and trust.
  • Improved the AS4 server so attachment files are processed more efficiently.
  • Enhanced the UI PostgreSQL Switch Database steps. They now include an option for creating a schema.
  • Added support for routing unauthenticated AS4 messages to the anonymous Web User.
  • Updated the PGP Sign and Encrypt Task to not require that the key name be specified if there is only one PGP key in the KeyRing or Key Vault.
  • Added the ability to bypass routing rules on the Admin Client allowing users to login based upon their login method instead of routing rules in case of a misconfiguration.
  • Enhanced the LDAP Auto Creation logic when using Routing Rules to use the login method specified by routing rules first when user doesn't exist.
  • Enhanced French translations in the Web Client.
  • Updated the Trigger Call Project action - the Job Queue text field is now a drop-down list that displays all available Job Queues.
  • Improved error messages for sharing Secure Folders and made the Audit Log remarks more descriptive.
  • Enhanced the file name pattern field on Monitors to allow regular expressions of up to 255 characters.
  • Enhanced the license refresh process to log validation errors during startup of MFT.
Updates
  • Upgraded the TinyRadius API to version 1.1 to fix an issue with passwords greater than 16 characters.
  • Updated the Write EDI X12 task so that the sender and receiver no longer receive extra padding in the GS segment.
  • Updated the Read EDI X12 and Read EDIFACT tasks to optionally handle repeating segments as loop type data.
  • Updated the Global Logging to ensure all IndexReaders are closed after searching.
  • Updated the View Certificate page to display the certificate serial number when viewing a KMS certificate.
  • Updated some Japanese messages in the Admin client with correct context.
  • Updated existing French translations to be more accurate.
  • Improved error logging for incoming AS4 messages.
  • Added the ability to configure the Admin Site URL for Admin Single Sign on settings.
  • Upgraded Apache Tomcat from version 7.0.96 to 7.0.99.
  • Upgraded the commons-beanutils library from version 1.9.3 to 1.9.4.
Fixes
  • Fixed an issue with Job File Auditing where Host and User Name information wasn't being tracked.
  • Fixed an issue that allowed users to enter the Master Encryption Key name with leading spaces.
  • Fixed an issue where the PGP Sign task would sometimes throw a Null Pointer.
  • Fixed an issue where a large session timeout caused logout to occur.
  • Fixed an issue where certain fields were being logged incorrectly in the AS4 Audit Logs.
  • Fixed an issue where a Web User could not be deleted unless all AS4 messages on their subchannels were deleted.
  • Fixed an issue where the expression descriptions in the Project Designer Expression Wizard would not display in the selected language.
  • Fixed an issue where the Write Excel Format background and foreground color options were displaying two 'Olive Green' options. One of the options is now labeled 'Maroon'.
  • Fixed an issue with the FTP service where listing files and directories with -a option resulted in a null pointer exception.
  • Fixed an issue with Schedules where certain repeat conditions would prevent saving.
  • Fixed an error authenticating Users before running an Agent Scheduler or Agent Monitor.
  • Fixed an issue with EDI X12 where the maximum number of loop iterations was not being validated when the loop was required.
  • Fixed an issue where the AS4 Push task did not correctly validate receipts in certain scenarios.
  • Fixed an issue where a bad response was returned when an a decryption key was not specified on an AS4 Processing Mode.
  • Removed an unnecessary edit icon on the Custom Tasks page.
  • Corrected the Japanese translation of the word 'Japanese'.
  • Fixed an issue where audit logs would load Service Level Agreement Log View modules without the Admin User having Service Level Agreement Log View permissions.
  • Fixed an issue where changes to non-password fields in Global Settings would incorrectly trigger an admin log "password changed" entry after rotating master keys.
  • Fixed an issue where deactivating a domain would not check use by Agents, Agent groups, and Agent templates.
  • Fixed an issue that when using the PGP Encrypt task, the file sizes in the File Audit log details were incorrect.
  • Fixed an issue where the Send Email task would add extra brackets to the From field when other fields were updated.
  • Fixed an issue where Request Files would try to send a password to a mobile number. This is not an option for Request Files.
  • Fixed an issue where users would follow the SAML Logout URL when they should be returned to the Login page instead.
  • Fixed the display of certificate attributes when editing a signed certificate in KMS.
  • Fixed an issue where the Retrieve Email task failed on attachments with Chinese characters in the file name.
  • Removed unnecessary table columns for Monitors in the Agent console.
  • Fixed an issue that when an Admin User failed Two-Factor Authentication (2FA) on login, a Web User with the same user name would be locked out.
  • Fixed an issue where an error was thrown when adding a variable in the GACMD Cloud Connector Run Project action.
  • Fixed an issue where Web Users could have AS4 processing modes without an AS4 Partner ID.
  • Fixed an issue where the Admin Client and Web Client were not setting the language cookie to secure when connecting over HTTPS.
  • Fixed an issue where the Web Client was not setting the language cookie correctly over HTTP.
  • Fixed an issue that prevented the license from refreshing in certain scenarios.

Back to Top

 

Halcyon


Level 1 - Message Management Suite

Version 7.0 (PTF: 2020.044)

Feb 24, 2020

Enhancements
  • "Hold Rule" (HLDRULE) and "Release Rule" (RLSRULE) now issue *ESCAPE message HAL0154 if the Group/Queue specified cannot be found.
  • "Work with User Authority" (WRKUSRAUT) now has new option "3=Copy" which can be used to copy the authorities from an existing user to a new user.
  • System Default HMM/DFTMAXPERAPI, "Maximum messages to retrieve per API call", now allows a value of *NOMAX. Setting a high number or *NOMAX could result in the Message Monitor not checking message queues frequently if a message queue is being rapidly populated with messages.
  • The Message Communicator script for retrieving the GSM status, RTVGSMSTS, has been modified to work with more GSMs. IMPORTANT: A new version of script RTVGSMSTS will be installed, with the existing script renamed to a suffix of underscore.
  • Message Communicator now supports retrieving the signal strength for a 4G capable GSM.
Other Fixes
  • "Retrieve System Default" (RTVSYSDFT) would incorrectly truncate the name of the system default to 10 characters and then return an error if the name was longer as it was not found. This has been fixed in this release.
  • "Work with Alert Log" (WRKALTLOG) for "11=Omit" was not allowing wildcards for Job, User or Program. This has been fixed in this release.
  • "Work with Rules (WRKRULES)" would fail if "10=Reset" was used against Monitor or Group. This has been fixed in this release.
  • "Work with Rules" (WRKRULES) was not retaining the cursor position after changing criteria. This has been fixed in this release.
  • "Work with Rules" (WRKRULES) within a Message Queue Rule would incorrectly show a "not found" error when defining a message from a message file on an IASP. This has been fixed in this release.
  • "Work with Rules" (WRKRULES) would incorrectly show an error within a TCP/IP rule on the criteria for a problem on the first page of the Rule definition. This has been fixed in this release.
  • A Job Log Rule with a Held Group would continue to Alert. This has been fixed in this release.
  • A Job Queue *ALL/*ALL Rule Group that included a *JOB Rule to check for "time on queue" would correctly raise alerts but then incorrectly close them immediately. This has been fixed in this release.
  • A SNDTXT Action that specified the inclusion of a *JOBINF spooled file would fail. This has been fixed in this release.
  • After using CSTENV *EXAMPLE some example rules incorrectly had values including %HALCYON and %HMCLIB. This has been fixed in this release.
  • Job Log Monitor was incorrectly looking for a "Not received" rule on a day that was set not to be monitored. This has been fixed in this release.
  • Job Queue Monitor example Rule Group Q1ABRMNET did not have the criteria set correctly on Rule "0900 - Check job queue is ready". This has been fixed in this release.
  • Message Communicator scripts for modems did not include a "time-out" specification on initialization which meant the script could hang if the modem was not responding correctly. This has been fixed in this release. IMPORTANT: New versions of the following scripts will be installed, with the existing script renamed to a suffix of underscore;
    • ACCURA56K
    • AUTOSYNC
    • DT
    • INTMODDIAL
    • INTMODSMS
    • MULTITECH
    • NULLMODEM
    • O2MOBILE
    • TAP
    • UCP
    • VODAPAGE
    • VODASMS
  • Message Communicator was returning bad information for the "Service Provider" on a *UCS2 GSM/NetGSM. This has been fixed in this release.
  • Message Monitor was incorrectly alerting for a BRMS "Not received" Rule. This has been fixed in this release.
  • Message Queue Monitor was not resetting "Counts" against Actions correctly. This has been fixed in this release.
  • Message Queue Monitor would incorrectly raise an alert that had already been raised for a message queue set to *LAST "startup option" each time it was started. This has been fixed in this release.
  • PDFs generated by Halcyon IBM i incorrectly included some escape characters. This has been fixed in this release.
  • SNMP Traps sent from Halcyon IBM i are now logged within the Halcyon Message Log (DSPMSGLOG).
  • Sending emails on V5R3 and V5R4 failed as clean-up would attempt to use a parameter on a command that does not exist at those OS Levels. This has been fixed in this release.
  • Substitution Variable &MSGHLP was incorrectly being truncated to 240 characters. This has been fixed in this release.

Level 2 - Systems Operations Suite

Version 7.0 (PTF 2020.044)

Feb 24, 2020

Enhancements
  • "Hold Rule" (HLDRULE) and "Release Rule" (RLSRULE) now issue *ESCAPE message HAL0154 if the Group/Queue specified cannot be found.
  • "Work with User Authority" (WRKUSRAUT) now has new option "3=Copy" which can be used to copy the authorities from an existing user to a new user.
  • System Default HMM/DFTMAXPERAPI, "Maximum messages to retrieve per API call", now allows a value of *NOMAX. Setting a high number or *NOMAX could result in the Message Monitor not checking message queues frequently if a message queue is being rapidly populated with messages.
  • The Message Communicator script for retrieving the GSM status, RTVGSMSTS, has been modified to work with more GSMs. IMPORTANT: A new version of script RTVGSMSTS will be installed, with the existing script renamed to a suffix of underscore.
  • Message Communicator now supports retrieving the signal strength for a 4G capable GSM.
  • New Substitution Variables have been made available for use in Performance *JOB Rules:

    • &FUNTYPE - the "Function type" of the Job.

    • &FUNNAME - the "Function name" of the Job.

  • Additional shipped example Performance Rules have been made available within the BRMS Rule Group.

Other Fixes
  • "Retrieve System Default" (RTVSYSDFT) would incorrectly truncate the name of the system default to 10 characters and then return an error if the name was longer as it was not found. This has been fixed in this release.
  • "Work with Alert Log" (WRKALTLOG) for "11=Omit" was not allowing wildcards for Job, User or Program. This has been fixed in this release.
  • "Work with Rules (WRKRULES)" would fail if "10=Reset" was used against Monitor or Group. This has been fixed in this release.
  • "Work with Rules" (WRKRULES) was not retaining the cursor position after changing criteria. This has been fixed in this release.
  • "Work with Rules" (WRKRULES) within a Message Queue Rule would incorrectly show a "not found" error when defining a message from a message file on an IASP. This has been fixed in this release.
  • "Work with Rules" (WRKRULES) would incorrectly show an error within a TCP/IP rule on the criteria for a problem on the first page of the Rule definition. This has been fixed in this release.
  • A Job Log Rule with a Held Group would continue to Alert. This has been fixed in this release.
  • A Job Queue *ALL/*ALL Rule Group that included a *JOB Rule to check for "time on queue" would correctly raise alerts but then incorrectly close them immediately. This has been fixed in this release.
  • A SNDTXT Action that specified the inclusion of a *JOBINF spooled file would fail. This has been fixed in this release.
  • After using CSTENV *EXAMPLE some example rules incorrectly had values including %HALCYON and %HMCLIB. This has been fixed in this release.
  • Job Log Monitor was incorrectly looking for a "Not received" rule on a day that was set not to be monitored. This has been fixed in this release.
  • Job Queue Monitor example Rule Group Q1ABRMNET did not have the criteria set correctly on Rule "0900 - Check job queue is ready". This has been fixed in this release.
  • Message Communicator scripts for modems did not include a "time-out" specification on initialization which meant the script could hang if the modem was not responding correctly. This has been fixed in this release. IMPORTANT: New versions of the following scripts will be installed, with the existing script renamed to a suffix of underscore;
    • ACCURA56K
    • AUTOSYNC
    • DT
    • INTMODDIAL
    • INTMODSMS
    • MULTITECH
    • NULLMODEM
    • O2MOBILE
    • TAP
    • UCP
    • VODAPAGE
    • VODASMS
  • Message Communicator was returning bad information for the "Service Provider" on a *UCS2 GSM/NetGSM. This has been fixed in this release.
  • Message Monitor was incorrectly alerting for a BRMS "Not received" Rule. This has been fixed in this release.
  • Message Queue Monitor was not resetting "Counts" against Actions correctly. This has been fixed in this release.
  • Message Queue Monitor would incorrectly raise an alert that had already been raised for a message queue set to *LAST "startup option" each time it was started. This has been fixed in this release.
  • PDFs generated by Halcyon IBM i incorrectly included some escape characters. This has been fixed in this release.
  • SNMP Traps sent from Halcyon IBM i are now logged within the Halcyon Message Log (DSPMSGLOG).
  • Sending emails on V5R3 and V5R4 failed as clean-up would attempt to use a parameter on a command that does not exist at those OS Levels. This has been fixed in this release.
  • Substitution Variable &MSGHLP was incorrectly being truncated to 240 characters. This has been fixed in this release.
  • "Print Audit Journal Entries" (PRTAUDJRNE) would not allow editing of "Other criteria" for some Audit Journal types. This has been fixed in this release.

  • Performance *JOB Rules would not allow use of the "/" (forward slash) character within "Function name". This has been fixed in this release.

  • Performance Monitor was incorrectly alerting and reporting if the system had more than 30,000 active jobs. This has been fixed in this release.

  • The Halcyon Setup Wizard (HEMINZRUL) was incorrectly setting the *JOB *JOBCOUNT Rules to have comparison *EQ 0 instead of *LT number of Jobs. This has been fixed in this release.

  • The Halcyon Setup Wizard (HEMINZRUL) was not setting the value for "On-close action" on the rules it created. This has been fixed in this release.

  • The Object Monitor would fail with a User Space Overflow problem if there was a lot of open alerts and "Open alert action" was not disabled. This has been fixed in this release.

  • Various shipped example Performance rules had some missing parameters on the ACTSCH Action. This has been fixed in this release.

Level 3 - Advanced Automation Suite

Version 7.0 (PTF 2020.044)

Feb 24, 2020

Enhancements
  • "Hold Rule" (HLDRULE) and "Release Rule" (RLSRULE) now issue *ESCAPE message HAL0154 if the Group/Queue specified cannot be found.
  • "Work with User Authority" (WRKUSRAUT) now has new option "3=Copy" which can be used to copy the authorities from an existing user to a new user.
  • System Default HMM/DFTMAXPERAPI, "Maximum messages to retrieve per API call", now allows a value of *NOMAX. Setting a high number or *NOMAX could result in the Message Monitor not checking message queues frequently if a message queue is being rapidly populated with messages.
  • The Message Communicator script for retrieving the GSM status, RTVGSMSTS, has been modified to work with more GSMs. IMPORTANT: A new version of script RTVGSMSTS will be installed, with the existing script renamed to a suffix of underscore.
  • Message Communicator now supports retrieving the signal strength for a 4G capable GSM.
  • New Substitution Variables have been made available for use in Performance *JOB Rules:

    • &FUNTYPE - the "Function type" of the Job.

    • &FUNNAME - the "Function name" of the Job.

  • Additional shipped example Performance Rules have been made available within the BRMS Rule Group.

Other Fixes
  • "Retrieve System Default" (RTVSYSDFT) would incorrectly truncate the name of the system default to 10 characters and then return an error if the name was longer as it was not found. This has been fixed in this release.
  • "Work with Alert Log" (WRKALTLOG) for "11=Omit" was not allowing wildcards for Job, User or Program. This has been fixed in this release.
  • "Work with Rules (WRKRULES)" would fail if "10=Reset" was used against Monitor or Group. This has been fixed in this release.
  • "Work with Rules" (WRKRULES) was not retaining the cursor position after changing criteria. This has been fixed in this release.
  • "Work with Rules" (WRKRULES) within a Message Queue Rule would incorrectly show a "not found" error when defining a message from a message file on an IASP. This has been fixed in this release.
  • "Work with Rules" (WRKRULES) would incorrectly show an error within a TCP/IP rule on the criteria for a problem on the first page of the Rule definition. This has been fixed in this release.
  • A Job Log Rule with a Held Group would continue to Alert. This has been fixed in this release.
  • A Job Queue *ALL/*ALL Rule Group that included a *JOB Rule to check for "time on queue" would correctly raise alerts but then incorrectly close them immediately. This has been fixed in this release.
  • A SNDTXT Action that specified the inclusion of a *JOBINF spooled file would fail. This has been fixed in this release.
  • After using CSTENV *EXAMPLE some example rules incorrectly had values including %HALCYON and %HMCLIB. This has been fixed in this release.
  • Job Log Monitor was incorrectly looking for a "Not received" rule on a day that was set not to be monitored. This has been fixed in this release.
  • Job Queue Monitor example Rule Group Q1ABRMNET did not have the criteria set correctly on Rule "0900 - Check job queue is ready". This has been fixed in this release.
  • Message Communicator scripts for modems did not include a "time-out" specification on initialization which meant the script could hang if the modem was not responding correctly. This has been fixed in this release. IMPORTANT: New versions of the following scripts will be installed, with the existing script renamed to a suffix of underscore;
    • ACCURA56K
    • AUTOSYNC
    • DT
    • INTMODDIAL
    • INTMODSMS
    • MULTITECH
    • NULLMODEM
    • O2MOBILE
    • TAP
    • UCP
    • VODAPAGE
    • VODASMS
  • Message Communicator was returning bad information for the "Service Provider" on a *UCS2 GSM/NetGSM. This has been fixed in this release.
  • Message Monitor was incorrectly alerting for a BRMS "Not received" Rule. This has been fixed in this release.
  • Message Queue Monitor was not resetting "Counts" against Actions correctly. This has been fixed in this release.
  • Message Queue Monitor would incorrectly raise an alert that had already been raised for a message queue set to *LAST "startup option" each time it was started. This has been fixed in this release.
  • PDFs generated by Halcyon IBM i incorrectly included some escape characters. This has been fixed in this release.
  • SNMP Traps sent from Halcyon IBM i are now logged within the Halcyon Message Log (DSPMSGLOG).
  • Sending emails on V5R3 and V5R4 failed as clean-up would attempt to use a parameter on a command that does not exist at those OS Levels. This has been fixed in this release.
  • Substitution Variable &MSGHLP was incorrectly being truncated to 240 characters. This has been fixed in this release.
  • "Print Audit Journal Entries" (PRTAUDJRNE) would not allow editing of "Other criteria" for some Audit Journal types. This has been fixed in this release.

  • Performance *JOB Rules would not allow use of the "/" (forward slash) character within "Function name". This has been fixed in this release.

  • Performance Monitor was incorrectly alerting and reporting if the system had more than 30,000 active jobs. This has been fixed in this release.

  • The Halcyon Setup Wizard (HEMINZRUL) was incorrectly setting the *JOB *JOBCOUNT Rules to have comparison *EQ 0 instead of *LT number of Jobs. This has been fixed in this release.

  • The Halcyon Setup Wizard (HEMINZRUL) was not setting the value for "On-close action" on the rules it created. This has been fixed in this release.

  • The Object Monitor would fail with a User Space Overflow problem if there was a lot of open alerts and "Open alert action" was not disabled. This has been fixed in this release.

  • Various shipped example Performance rules had some missing parameters on the ACTSCH Action. This has been fixed in this release.

  • "Analyze Disk" (ANZDSK) would fail when a library contained over 32,000 objects. This has been fixed in this release.
  • "Print System Performance Data" (PRTPFMSYS) was incorrectly allowing values *DBIO and *DBIOMAX for the "Statistic type" parameter. These statistics have been deprecated in this release.
  • Log File Monitor example Rule Group EX_CERT incorrectly had a CONSOLE Action instead of an ACTSCH AS1 Action on the rule. This has been fixed in this release.
  • Log File Monitor was not handling special characters within the password entered against a rule for processing web pages. This has been fixed in this release.

Operations Center Suite

Version 7.0

(PTF 2020.044)

Feb 24, 2020

  • No specific updates in this release. Please see the Level 3 - Advanced Automation Suite release notes.

Record and Playback

Version 15.0 (PTF: 2020.044)

Feb 24, 2020

Other Fixes
  • "Clear Playback Log" (CLRPLBLOG) was not clearing Sessions with a status of *INIT or *WARN. This has been fixed in this release.
  • "Run HRP Script" (RUNHRPSCR) could error with a "Range of subscript value or character string error" when attempting to save Screen Templates. This has been fixed in this release.

Network Server Suite

Version 11.0.5 (PTF 11.0.2020.042)

Feb 18, 2020

Enhancements
  • Error handling during network outages has been improved in this release.
  • Alerts now support UTC dates and times.
  • The Android App now supports alert paging by way of the 'Load More' action.
Other Fixes
  • An issue with the installer running on SUSE Linux 64-bit platforms has been fixed.
  • An SQL Injection vulnerability has been fixed in this release.
  • Special characters are now fully supported within comments.
  • Default values for all items in the Preferences section, such as Connection and Read Timeouts have been added.
  • The number format of certain languages sometimes raised an error when the Enterprise Console client tried to connect to the Enterprise Server. This has now been fixed.
Version 11.0.4 (PTF 11.0.2020.031)

Feb 04, 2020

New Features
  • New MQ Monitor templates for AIX and Linux have been made available in the Central Configuration Manager (CCM).
  • An advanced filtering feature for closed alerts has been added within the Enterprise Console client.
  • New alert archiving settings have been made available in Enterprise Server Options to manage closed and purged alerts. Alerts were previously written to an archive file, but now remain in the database. Periodic purging will take place depending on these settings.
  • The Enterprise Console is now able to capture user statistics such as the number of alerts acknowledged, closed and replied to.
  • Enterprise Console now captures alert statistics such as the number of minutes taken to close or reply to an alert.
  • Alert text statistics, such as number of alerts by frequency of text message, are now being captured.
  • A user can now search for alert within a panel by entering a partial match of text
  • Enterprise Console layouts are now stored in the SQL database. Users wanting to import a layout from version 10.3 can do so from the Enterprise Console client. Any user can create a 'Private' layout which is only visible to them. 'Public' layouts are created by users with administration rights and these are available to all users.
  • It is now possible to report on Enterprise Console archived alerts.
Enhancements
  • An updated version of the 'Infor M3 Grid Monitoring' template has been made available within CCM.
  • A new AIX VIOS template has been made available in the CCM.
  • A new Source Type has been added to the Enterprise Console to recognize alerts received from the IBMi Log File Monitor.
  • Customers can now use database names that are different to the Halcyon defaults. this enables the hosting of multiple installations of Network Server Suite on the same SQL Server instance.
  • The ability to report on Enterprise Console alerts, such as Monthly Alert Summary by Platform, Top 10 Alerts, Alert Summary by Device Group and Alert Summary by Product, has been made available.
  • 'Alert Selection' has been improved for each alert panel shown in the Enterprise Console client so you can, for example, filter alerts based on one or more conditions of Alert Type, Source Type and Alert Status.
  • It is now possible to enter comments against closed alerts.
  • The REST action now supports JSON.
  • The REST action now allows use of both GET and PUT.
  • Network Server Suite now includes an IMAP Monitor.
  • Online product help is now available from within all Network Server Suite applications.
  • CCM now includes an action that has the ability to Hold and Release rules from within a different Monitor.
  • Windows agent TCP Monitor rules now include firewall proxy settings
  • An SNMP Trap action for an IBMi alert now includes additional information such as the alert ID, Action ID, Alert severity and Rule information.
Other Fixes
  • In certain circumstances, monitoring steps on the Windows agent when settings get updated. This has been fixed.
  • Processing large log files within the Windows Log File Monitor meant that Network Server Suite could become unresponsive. This has been fixed.
  • The Windows agent would fail while refreshing some services. This has been fixed.
  • The System Monitor would not raise alerts for an IBMi environment being completely down. This has been fixed.
  • A fix has been applied so that forwarded alerts on a secondary Enterprise Console now have pending actions canceled when the alert is acknowledged on the primary Enterprise Console.

Advanced Reporting Suite

Version 11.0.4 (PTF 11.0.2020.014)

Feb 04, 2020

New Features
  • A new Enterprise Console plugin has been created in Advanced Reporting Suite to collect data from an Enterprise Server database. The data includes user, alert and alert text statistics.

Back to Top

 

IBM Partnership


Rational Developer for i

Version: 9.6.0.7
New Features
  • New extract procedure refactoring feature can be used to convert business rules into reusable procedures.
  • New library list view to easily modify a library list from any RDi perspective.
  • Provide a simple way to search for RDi preferences with the preferences keyword filter.
Enhancements
  • Show variables larger than 4,095 characters in the RDi debugger (RFE77798).
  • Service Entry Points now allow conditional entries for breakpoints (RFE102060).
  • Persist display hover text for procedure parameters (RFE116542).
  • Double-click of source elements to include * symbol when appropriate (RFE120965).
  • Sort by name control in outline should not affect sorting of key fields (RFE121191).
  • RPG language update: Editor support for the new DATA-GEN opcode.
  • RPG language update: Editor support for OPTIONS(*EXACT) for prototyped parameters.
  • RPG language update: Editor support for the new OVERLOAD keyword.
  • Enable editor navigation for marked occurrences of variables.
  • SQL formatter improvements.
  • Improved Copy To dialog reduces the chances of a user copying to an unintended location.
Other Fixes
  • ILE RPG outline incorrectly shows VARCHAR(0:2) for sub-procedure for varchar return value defined with a constant (APAR SE69406 - RDI 9.6.0.2).
  • Opening PNLGRP source in RDi leads to a StringIndexOutOfBoundsException (APAR SE71614 - RDI 9.6.0.6).
  • Option 2 (edit) in the object table should open members in edit mode even if the default mode is open as browse (APAR SE71721 - RDI 9.6.0.6).
  • ILE RPG content assist fails due to IllegalArgumentException: Comparison method violates its general contract (APAR SE72030 - RDI 9.6.0.6).
  • New procedure wizard does not show keywords for a passed parameter that has been modified (APAR SE72031 - RDI 9.6.0.6).
  • Setting SBMJOB additional parms in RSE connections may result in duplicated parms in compile commands and compilation failures (APAR SE72032 - RDI 9.6.0.6).
  • Source may become corrupted when i Projects are configured to add or remove sequence numbers and dates (APAR SE72289 - RDI 9.6.0.6).
  • Correctly tokenize literals in fixed form source.
  • %ELEM(x) line references in the outline should be marked as modified.
  • Fixed Visualize Application Diagram only works for the last member opened from the source menu.
  • Fixed port range preferences input for RSE to correctly handle ports 1-65535.
  • The default communications port number now specifies the beginning of a port range rather than a specific static port. If a port is unavailable, RDi will increment to the next port in the range and try again to connect.
  • Update Java to eliminate legacy Java requirement to run RDi on macOS.

Back to Top

 

Powertech


Authority Broker

Version 4.22

Feb 12, 2020

  • An issue that could cause missing switch details on Event Reports has been resolved.
  • Erroneous "Cursor PABR060G not open" messages have been removed from the Profile Switch and Profile Release processes.
  • Password Masking is now supported in English, French, German, Spanish, and Italian.
  • A typo in the help for the System User Report panel has been fixed.

BoKS SSH Client for Windows

Version 8.0

Feb 19, 2020

NOTE: For system requirements including supported platforms, see the BoKS SSH Client for Windows 8.0 Administration Guide.
New Features
  • Updated to be based on PuTTY 0.73 and to use OpenSSL 1.1.1d.
Enhancements
  • Added the ability to specify stricter security rules for connecting to servers when using BoKS Client for Windows with BoKS Manager.
  • Added history list to the BoKS SFTP graphical interface for easier browsing.
Other Updates
  • Added the ability to delete items that are selected in the BoKS SFTP graphical interface by pressing the Delete key, in addition to being able to delete using the context menu.
  • Removed the ability to undock the session tab out of the main window and into a window of its own. The checkboxes "Restrict Content to Document Tabs" and "Restrict Floating Windows" are removed from the Tools > Options window.
  • Added the ability to configure whether a confirmation dialog is displayed when closing sessions in the BoKS SFTP graphical interface.
  • CAS-0010175125: fixed an issue whereby network locations were displayed in the BoKS SFTP graphical interface even though it was not possible to transfer files to and from these locations.

Compliance Monitor

Version 4.0

Feb 26, 2020

New Features
  • Compliance Monitor's new National Institute of Standards and Technology (NIST) report group now provides security control recommendations based on an interpretation of the NIST standard by HelpSystems' IBM i security experts. The reports were generated to help facilitate compliance with NIST controls.
  • Compliance Monitor's new General Data Protection Regulation (GDPR) report group now provides appropriate measures for compliance based on an interpretation of the GDPR standard by HelpSystems' IBM i experts. Portions of the GDPR that apply include articles 5, 6, 24, 25, 28, and 32.
Enhancements
  • The DB Password is now automatically set when installed and when using CHGPCM2PWD when the user is PLCM2ADM.
  • Branding updates have been made to the UI.
Other Fixes
  • Gaming (MICS) reports have been moved to the Regulatory Recommendations report group.
  • Assessment data now displays correctly in the browser for multiple systems with Automatic collected data.
  • A problem preventing the Consolidator from starting when the job has an iASP set has been resolved.
  • An issue causing inconsistent display of user profile descriptions has been resolved.
  • System(s) Requested details is no longer missing from reports generated using harvested data.
  • PLCM2ADM is now included as an authorized user in the QPWFSERVER authorization list.
  • An issue causing incorrect From dates on Authority Broker reports has been resolved.
  • Failures to create reports when a logo includes text with commas has been resolved.

Back to Top

 

Robot


Robot Save

Version 13.01

Feb 18, 2020

  • Fixed issue with encrypted backups receiving MCH3601 error.

Back to Top