Jun 16, 2020
No updates for this release.
Version 7.0 (PTF: 2020.044.1)
Jun 3, 2020
- Message Monitor was not ending the "Check cycle" as defined against the Rule Group if more messages were added to the queue while it was being processed. This has been fixed.
- A 'Not received' rule that spans midnight no longer gives a false alert.
Message Monitor could fail with a duplicate key error as part of BRMS monitoring under a specific circumstance. This has been fixed.
Version 7.0 (PTF 2020.044)
Feb 24, 2020
- "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.
- "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;
- 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.
Version 7.0 (PTF 2019.192)
- Customized rules for HA4i have been made available.
- Customized rules for IBM Webquery have been made available.
- Additional Object Monitor rules have been added to the M3 customization.
- The HALIMPORT command has been deprecated.
- A message has been added to warn user of a failed upgrade due to being HELD.
- The ability to add .ZIP email attachments has been added to Message Communicator.
- A *MONTHLY change period has been added to Rosters within Message Communicator.
- BRMS support has been added for V7R4.
- A substitution variable has been made available for Audit Entry data.
- Restricted Tasks Manager Task Groups now handle the running of a Halcyon Record and Playback Script.
- It is now possible to set the minimum number of auxiliary Object monitors.
- A fix has been applied so that the Override Remote Location Group at rule level now works as expected when using Auto-Export.
- When using Import Environment (IMPENV), the Work with Monitors display now reports the correct status for the listed monitors.
- Job Log Monitor no longer fails if there are lots of jobs in the system.
- Job Queue rules now ignore message CPF3330 if is encountered during a backup.
- Exit Points are now set to a default of ‘No’ for the restarting of servers.
- A fix has been applied so that all sub-console actions are invoked rather then just those of the first sub-console.
- SMS under *UCS2 for the Gemalto *NETGSM is now working as expected.
- When using SNDEMLMSG in Message Communicator, *SELECT now attaches the selected spooled files.
- When using the Output Queue, PDFs created by Halcyon are now correctly formatted.
- Performance *JOB EXISTS rules that use a User List in the ‘Job user’ field now work as expected.
- A fix has been applied so that Lock Display (LCKDSP) now allows the unlock without the user needing *USE permission to the user that initiated the Lock Display command.
- QTEMP data collection is now controlled by a new ‘Temporary Storage used in MB’ value within “Work with Performance Collection Levels“.
Version 7.0 (PTF 2018.248)
- The PowerHA Templates include two additional Device Rules to check for Cluster Node and Cluster Resource Group activity.
- Job Log Monitor now has the ability to monitor Autostart, Subsystem monitor, Spooled reader, System, Spooled writer and SCPF system jobs as part of *BATCH job monitoring.
- Display Web Log (DSPWEBLOG) and Print Web Log (PRTWEBLOG) now allow the subsetting of messages for just the Message Sender GUI via new value *QMM.
- The ability to lock an interactive display with a screen saver that requires the user to enter their password to unlock has been added.
- Work with Rules now allows the definition of auto-export settings at Monitor level.
- A fix has been applied to prevent Halcyon Network Receive Monitor failing on receipt of message CPE3406 from the operating system,
- A fix has been applied to prevent EMAILSPLF Action failing when system value QTIMSEP is set to 1.
- Message Communicator no longer fails when converting non-displayable characters as part of a response from a device, if it results in the data becoming very long.
- The CPTOSTMF action no longer fails when actioned if system value QTIMSEP is set to 1.
- A fix has been applied so that Audit Journal Manager Rules now correctly match against a defined user list.
- Performance *JOB rules have had a fix applied in order that 'Open alert' actions are processed as expected when the job ends.
- Performance *JOB rules using Job Lists now process Omissions as expected.
- Performance improvements have been made to the Halcyon Performance Monitor.
Version 7.0 (PTF 2018.044.2)
- In certain situations when running CCSID 65535, the SNDTXT Action and corresponding Alert Log entries could result in corrupt characters. This has been fixed.
Version 7.0 (PTF 2018.044.1)
- Performance improvements have been made to the Halcyon Performance Monitor.
Version 7.0 (PTF 2018.044)
- RobotHA customization templates have been updated to include Audit monitoring.
- Permanent license codes without maintenance (*NOMAINT) can be automtically removed using new system default HAL/CODEAUTODELETE.
- Job Lists now include the ability to specify 'User' and 'Subsystem' parameters.
- Performance improvements have been made to Open alert action processing.
- Work with Admin Alerts has had a message added warning of a redundant permanent license code being automatically deleted.
- Work with Alert Log has been enhanced with ASP and CCSID information via new F11=Message Information function key.
- The Monitor Supervisor now monitors Network Auxiliary Monitors.
- Work with Rules now allows the export of groups that contain wildcard symbols.
- A fix has been applied so that the Open alert action is processed regardless of rule status.
- A fix has been applied to Message Queue Monitor to handle QHST messages for the *LAST startup option when coming out of restricted state.
- Audit Journal Alerts now include the journal receiver name.
- Object *FILE rules can now raise an alert based on the number of members within a file.
- A fix has been applied so that a Command action in a Restricted Task rule no longer fails if the system is in a restricted state.
Version 7.0 (PTF 2017.311)
New system default HAL/SNMPSRCPORT has been made available to allow a default Port definition to be used when sending SNMP Traps. The purpose of this change is to allow control when applying firewall rules to outbound communications as the "source" Port will be fixed.
A fix has been applied so that a Console action to the Enterprise Console no longer fails if the source message contains corrupted data.
A fix has been applied so that a Send Text Message action no longer fails if the source message contains corrupted data.
Display Message Console (DSPMSGCON) now displays alerts from a remote system in the correct defined color.
A fix has been applied so that Display Message Console (DSPMSGCON) no longer fails when performing an auto-refresh.
A fix has been applied in order that the inclusion of substitution variables as part of a COMMAND Action which resolves to a non-displayable character such as &CR, no longer results in subsequent substitution variables being ignored.
Message Queue Rules now auto-resolves the IASP to be used using the message file library. In the event that the library is not found on *SYSBAS or on currently available IASPs, then *SYSBAS will be used and the message will be unable to be resolved.
A fix has been applied so that auto-exports now export Message Queue Global Exclusions.
Version 7.0 (PTF 2017.251)
- Work with Rules (WRKRULES) no longer allows an invalid value for "Job name" on Inactivity Rules.
- Work with Rules (WRKRULES) for Object *RCDCNT Rules now allows the use of F4=Prompt within "SQL select clause".
- Work with Rules (WRKRULES) now allows the use of F16=Subs Vars in an *OBJECT *RCDCNT Rule in the SQL Statement as part of the criteria.
- Performance *SYSTEM Rules now have a new SPLFS Statistic available which checks the total number of spooled files in the specified ASP Group.
- Efficiency improvements have been made to the Performance Monitor in relation to "Open alert action" processing.
Version 7.0 (PTF 2017.069.2)
- The Job Log Monitor had a very high I/O to some Halcyon files. This has been corrected.
- Export from 'Work with Rules' (WRKRULES) for an *ALL output Queue or Job Queue Group would fail as it incorrectly used *ALL for the Group rather than *GRPALL. This has been corrected.
- Message Communicator would reject an inbound email address if the system was set to a non-USA CCSID due to translation issues with the '@' symbol. This has been corrected.
- Message Monitor was incorrectly handling a message from a third party application. This has been corrected.
- Custom environment rule templates to monitor the Rocket iCluster product have been made available.
- Custom environment rule templates to monitor the Vision iTera v6.2 product have been made available.
- Custom environment rule templates to monitor the IBM PowerHA product have been made available.
- Custom environment rule templates to monitor the Robot HA product have been made available.
- Custom environment rule templates to monitor the M3/Movex product have been updated.
- Custom environment rule templates to monitor the MISYS Equation product have been updated.
- Device rules have the ability to monitor the status of Cluster Nodes and Groups.
- The upgrade routine warns you if you have not selected products that are suitable for upgrade
- The upgrade routine warns you if you are downgrading from a newer version of the software.
- An upgrade to Halcyon Message Manager (HMM) changes the scope of RSTRULE actions that reset a different rule from *REF to *RULE.
- An example rule has been added to Job Log rules.
- Job Queue rules have the ability to select jobs using a Job List.
- Job Queue rules provide IASP support for Job Queue monitoring.
- A warning is displayed if the required IBM PTFs for the Job Queue Monitoring API have not been applied.
- A fix has been applied so that Action Monitors operate correctly when used with temporary Product Authorization codes.
- Rule actions can now be delayed by up to 24 hours.
- Open alert action processing can be disabled via a new value of *DISABLE for System Default HAL/DFTOPNALTACTION.
- A command to enable NetServer Users; RSTNETUSR - Reset NetServer User has been made available.
- Auto-Export can be defined at Group level. This allows you to define a Monitor level Auto-Export policy but override at Group level.
- The EXTLOG (External Log) Action allows you to specify the Alert text that is sent to the external file. Substitution variables are supported.
- Print Alert Log (PRTALTLOG) includes a Save parameter which allows you to set whether the resulting spooled file should be saved after it has been printed.
- Replying to an IBM i Inquiry Alert within the Enterprise Console now records the user in message HAL0370 that is added to the Halcyon Message Log.
- Work with Substitution Variables (WRKSBSVAR) now allows you to define fixed length character variables via a new type of *FIXED.
- Substitution Variable &DFTALRSUB has been made available which contains the "Subject" defined for an email. This can be used in Actions within an Action Schedule if you want to use an external program/command to send emails and need to set/pass the email subject to be used.
- New Substitution Variables for rules have been made available:
- &RULEDESC The Rule Description
- &RULGRPDESC Description of the Rule Group the Rule is within
- New Substitution Variables relating to the closing of an alert have been made available:
- &ALRCLSDEV Alert close device if closed by SMS or Email
- &ALRCLSJOB Alert close job
- &ALRCLSMETH Alert close method
- &ALRCLSSYS Alert close system
- &ALRCLSUSER Alert close user
- Set LDA and Call Program (SETLDA) now includes the Message File ASP Group for Message Queue Alerts in the *LDA at position 923 for 10 characters.
- Set LDA and Call Program (SETLDA) now includes the Halcyon AlertID in the *LDA at position 914 for 9 characters.
- Set LDA and Call Program (SETLDA) was now sets the System Name into the *LDA when performed against non-Message Queue Alerts.
- Send Syslog Message (SNDSYSLOG) now includes the ability to specify the Port number to which syslog messages are sent.
- On clean installs, system default HAL/ALTAUTOCLOSE now ships with a value of 90 meaning Alerts are auto-closed after 90 days.
- On clean installs, system default HAL/DFTOPNALTACTION now ships with a value of *DISABLE meaning "Open alert action" processing is disabled.
- Work with Alert Log (WRKALTLOG) now allows you to Subset using a wildcard value for "Message ID" or by "Program name".
- Work with Alert Log (WRKALTLOG) now shows a status of WARNING against Alerts and SNDTXT Actions if all the devices to which the message is being sent are Held.
- Job Queue Lists must now have a name that is prefixed with * to keep it consistent with User Lists. On upgrade existing Performance *JOB Rules that use Job Lists will be changed to use the new format name.
- Work with Rules (WRKRULES) now includes the ability to create a new User List when prompting for "User" using F4=Prompt providing you have sufficient authority.
- Work with Rules (WRKRULES) now includes the ability to display a Calendar by using F4=Prompt in "Calendar". You can change an exisitng calendar here if you have sufficient authority.
- Work with Rules (WRKRULES) now includes the ability to display a User List. Within the criteria for a "User" set the value to * then use F4=Prompt.
- Work with Rules (WRKRULES) now loads the list of rules a page at a time to improve performance.
- Message Communicator now correctly configures a *SWTPP Modem.
- A fix has been applied so that Display Message Log (DSPMSGLOG) allows you to use "9=Comms log" against a message sent via a Broadcast Group.
- A fix has been applied so that emails sent via an SMTP Server respond correctly to the initial commands sent by Message Communicator.
- Message Communicator now supports more characters as part of sending an SMS.
- Message Communicator now supports sending emails with a subject line of up to 256 characters if sent via an external SMTP Server.
- Message Communicator Monitor now correctly handles subscript errors.
- The TAP - Telelocator Alphanumeric Protocol script has been modified to support additional service providers. On upgrade, a new version of script TAP will be installed. Any existing version of this script will be renamed to include a suffix of underscore. If you have made any changes to this script, you will have to re-apply them to the new version after upgrade.
- Send Email Message (SNDEMLMSG) now informs you as part of message HMC0271 that it does not support multi-level Broadcast Groups, Escalation Lists, Schedules or Rotas and that you must use Send Text Message (SNDTXTMSG) instead.
- The SNDTXT Action now includes an "Attach, if email" parameter which allows the following values. The selected attachment is added as a PDF and only if sending to an email device.
- *NONE Default. No attachments
- *ACTJOB Attach a copy of WRKACTJOB *PRINT
- *JOBINF Attach a copy of DSPJOB *PRINT for the alerting job
- *JOBLOG Attach a copy of DSPJOBLOG *PRINT for the alerting job
- *SYSSTS Attach a copy of WRKSYSSTS *PRINT.
- Send Text Message (SNDTXTMSG) now includes a "Service provider" parameter allowing you to override the Service Provider used for sending an SMS message.
- Message Communicator now allows you to specify the maximum size of attachments for emails. This has been made available via new system default HMC/EMAILATTMAX.
- Work with Communication Resources (WRKCMNRSC) now includes the ability to define, for directly attached devices, the type of "Flow control" that is required.
- Work with Email Addresses (WRKEMLADR), Work with Message Queue Recipients (WRKMSGQRCP), Work with Pagers (WRKPAGERS) and Work with Phones (WRKPHONES) now include a "Position to" parameter to allow for the easier retrieval of information.
- Work with Email Addresses (WRKEMLADR) now includes the ability to define the email format to be used via new parameter "Email send format".
- Message Queue Monitor now correctly handles rules containing lots of criteria with complex comparisons.
- Message Queue Monitor now cleans the message text from a generic message to remove undisplayable characters which would prevent processing.
- Message Queue Monitor now supports message queues on IASPs.
- Message Queue Monitor now includes the ability to change the Actions performed based on a count of the number of times triggered by the resolved message text.
- Send Test Message (SNDTSTMSG) now issues a warning if you provide details for a message which as a Severity greater than or equal to the value in new system default HMM/TSTMSGSEVWARN.
- Work with Messages Review (WRKMSGRVW) now shows the correct detail when "5=Display" is used against a generic message.
- Work with Rules (WRKRULES) for Message Queue criteria now sorts the summary list of criteria by Select/Omit then by the Message ID.
- Output Queue Monitor now supports the use of an Output Queue List to define the Output Queues to be monitored.
- Output Queue Monitor now supports output queues on IASPs.
- Output Queue *SPLF rules now support the use of a wildcard value for "User data". The wildcard value is case sensitive.
- A new "Delete after" flag has been added to the EMAILSPLF and EMAILSTMF Actions. On an Output Queue rule this deletes the spooled file once the email has been processed.
- Work with Rules (WRKRULES) for Output Queue Rule Groups now shows the last date and time the queue was checked and how long it took to process the queue by using "5=Display".
- TCPIP *PORT rules for *LCL *LCLLIST now allow you to set the "Remote system" parameter to *ANY meaning the rule checks for the Port being available or having a connection.
- TCPIP rules for *RMT *CALC now alert only if both the *IPV4 and the *IPV6 IP addresses fail to respond.
- TCPIP rules now correctly use an Inverse Calendar setting.
- Closing a TCPIP Alert now uses the "Check interval" setting rather than the Monitor cycle as the time since the last check setting is no longer reset.
- Audit Journal GR (Generic record) rules now support IPv6 address for "IP address".
- Audit Journal Manager now has the ability to use Auxiliary Monitors to help raise Alerts. New system default HAM/AUDMONMAX has been made available for this purpose.
- Print Audit Journal Entries (PRTAUDJRNE) now includes the ability to include data from a remote system. The data is extracted at the time the report is run and is therefore dependent
- on the audit journals existing on the remote system.
- Audit Journal Manager now supports audit codes "AX" (Row and Column Access Control), "PF" (PTF Operations), "PU" (PTF Object Change) and "X2" (Query Manager Profile Audit) on V7R2 and above.
- Custom Journal Monitor now supports a value of *OMITTED for "From program library".
- Restricted Tasks Manager now supports sending emails via an external SMTP server when in restricted state. This is only supported for SNDTXT, EMAILSPLF and EMAILSTMF Actions in a HRT rule. If you use the SNDEMLMSG, SNDTXTMSG or SNDPGRMSG commands you MUST manually start TCPIP first.
- Object *DIR, *IFS, and *OBJECT rules now allow a value of *ANY for "Object exists". This means that a single Alert will be raised regardless of how many matching objects are found.
- Object *DIR rules now allow a generic path to be specified.
- Object *FILE rules now allow you to check the age of the members from:
- *CREATE Date created
- *LASTUSED Date last used
- *LASTCHG Date last changed
- *LASTSAVE Date last saved.
- Object *FILE rules "Check member" now allows a value of *ALL so all members in a file can be checked by a single rule.
- Work with Rules (WRKRULES) for Object *IFS rules now list *DDIR type objects when using F4=Prompt.
- Work with Rules (WRKRULES) for Object *IFS rules now includes new function key F10=Verify path within the criteria. This allows a check of the path to be performed and information for "exists", "type" and "size" is shown.
- Object Monitor now includes the ability to raise a single Alert based on a count of matching IFS objects. This has been made available via a new *IFSCNT Rule Type.
- Object Monitor now supports checking the number of journaled objects for a Journal via new *JRN Rule Type.
- Object *OBJECT rules allow you to check how long it has been since an object was last saved via new "Object age from" value of *LASTSAVE. This only works if the save command was specified with UPDHST(*YES) which updates the date last saved on the object.
- Object Monitor now has the ability to use Auxiliary Monitors to help raise Alerts. System default HEM/OBJMONMAX has been made available for this purpose.
- Object Monitor now has the ability to delay an Alert unless the triggering situation is sustained for a period of time. New parameter "Alert delay" has been made available for this purpose. This specifies how long the triggering situation must continually trigger the rule before an Alert is raised.
- Object Monitor now supports objects on IASPs.
- The messages added to the Message Log when an Object rule is automatically held because of an object lock have been changed to improve clarity.
- A new "Delete after" flag has been added to the EMAILSPLF and EMAILSTMF Actions. On an Object *IFS Rule this deletes the stream file once the email has been processed.
- Performance *JOB Rules now reload Job Lists when they are changed to prevent incorrect alerting.
- The Performance Monitor would not accept a statistic size for DBLCKW greater than 9 digits.
- An upgrade of Message Manager now correctly sets the 'Scope' of RSTRULE actions.
- A fix has been applied to the Job Queue Monitor so that it now actions the 'Open Alert' action correctly.
- Message Communicator now removes attachments for *ARPA emails.
- Using Export Rule (EXPRULE) for a Message Queue rule now updates an interenal index number on the target environment to prevent issues arising when adding further criteria to the rule.
- Message Communicator now correctly processes any commands sent via emails.
- The specified time-out for data to be received from an external SMTP Server setting within Message Comunicator is now correctly applied.
- Message Monitor now correctly processes message queue messages if the system time has been moved back (such as end of daylight saving time). It no longer waits until the original time has been passed again.
- Output Queue and TCP/IP rules now have the ability to run an Action Schedule when an alert is closed. A new parameter, 'On-close action' has been made available on the respective Add/Change Rule display for this purpose.
- The SNDTXT action now includes an *ALERTED value for message devices. This sends a message to all Message Communicator devices that have been messaged about the alert. The text message is taken from the entry in new system default HAL/DFTCLSALTMSG.
- Output Queue rules now support the use of a User List instead of a fixed value for the 'Job user' parameter. This adds the ability to specify multiple select and omit criteria for the user.
- You can now resequence the rule numbers on TCP/IP rules by using new option 38=Resequence against the rule group. Actions which include the ability to define the rule number, such as CLOSE, DELETE, HLDRULE, RLSRULE and RSTRULE are not updated.
- You can now resequence the rule numbers on Audit and Object rules by using new option 38=Resequence against the rule group. Actions which include the ability to define the rule number, such as CLOSE, DELETE, HLDRULE, RLSRULE and RSTRULE are not updated.
- Object Monitor can now handle files that contain in excess of 1.5 billion records.
- Object Monitor now adds a QNTC error to the Halcyon Message Log in order to highlight problems when no such path or directory exists or when a path cannot be accessed due to error CPE3025.
- Halcyon Auto-Upgrade Configuration (HALINST/CONFIG) now includes the ability to define whether the Halcyon Monitors for the required Environment are restarted when the upgrade is complete.
- Halcyon now checks if IBM PTF SI60339 has been applied on V7R3. Access to the Auto-Upgrade Panel is refused if not.
- A fix has been applied to prevent Message Communicator failing when attempting to receive a large inbound email.
- A fix has been applied to prevent the TCPIP *RMT rules from triggering in situations where the monitor has been running for an extended period of time.
- A system default has been added to control the SMTP timeout period within Message Communicator.
- Job queue *JOB rules now allow the special value *SECOND for 'Job' which provides the ability to check the second job on the job queue.
- Message Communicator now allows the following special characters in a device name; Space ' ', Asterisk '*', Hash '#', Dash '-', Open bracket '(', Close bracket ')', Forward slash '/', Underscore '_'.
- Siemens and Gemalto Send and Receive scripts have been modified to improve the performance of sending/receivng an SMS via a GSM/NetGSM.
- A new DISPATCH script is now included in Message Communicator for use with GSMs when facilitating a 'mass send' of SMS messages.
- Message Communicator now includes an INZGSM script to initialize/reset a GSM.
- A fix has been applied to prevent the Inactivity Monitor failing if there are more than 40,000 inactive jobs on the system.
- Device, Job Log, Job Queue, Message Queue, Output Queue and TCP/IP rules now have the ability to run an Action Schedule when an alert is closed.
- Device, Job Log, Job Queue, Message Queue, Output Queue and TCP/IP rules within a group can be re-sequenced by use of new option 38=Resequence.
- Job Log, Job Queue, Message Queue and Output Queue rules now support the use of a user list instead of a single user profile.
- Job Queue *STS rules now display the number of jobs to be checked.
- A fix has been implemented to prevent the Job Queue Monitor from failing under a very specific circumstance.
- COMMAND actions include an iASP parameter to allow definition of which iASP should be used when the command is run.
- Work with User Lists supports the use of Select / Omit for individual user profiles.
- Option 8=Where Used has been added to Work with User Lists to allow the display of rules where the user list is deployed. Additionally, it is no longer possible to delete a user list that is in use.
- System default HMC/EMAILFORMAT has been added to define the format used for outbound emails sent using an external SMTP server.
- Send Text Message (SNDTXTMSG) allows a value of *ALERTED to send a message to all message devices that have already been sent a message for the specified alert.
- Create Email Address (CRTEMLADR) includes all the parameters available when creating the message device within Work with Email Addresses.
- System default HMC/SMTPSERVERRATE has been added to define the maximum number of emails that can be sent via an external SMTP server in the space of one minute.
- A communication script has been made available to allow the use of Multi-tech modems.
- Support has been added to allow the sending of messages to devices in a broadcast group that is already part of another broadcast group.
- Print Communications Log allows a value of *MSG in the Detail parameter. This includes the actual messages that have been sent and received.
- A fix has been implemented to clear the message review down to the number of days specified in system default HMM/LRMLOGLIFE.
- A fix has been implemented so that Message Queue Monitor alerts for messages received just after midnight.
- Output Queue *STS rules now display the number of spooled files to be checked.
- The Output Queue Monitor has been made more efficient.
- Audit Journal, Custom Journal, Distribution Queue, Restricted Tasks, Inactivity, Object, Performance and User rules now have the ability to run an Action Schedule when an alert is closed.
- Audit Journal, Custom Journal, Distribution Queue, Restricted Tasks, Inactivity, Object, Performance and User rules within a group can be re-sequenced by use of new option 38=Resequence.
- Audit Journal, Custom Journal, Inactivity, Performance and User rules now support the use of a user list instead of a single user profile.
- The Object Monitor now adds message CPE3025 - No such path or directory and HEM0255 - Path could not be accessed due to error CPE3025 to the Halcyon Message Log when QNTC related issues are detected.
- The alert severity level can now be overridden on an Action Schedule Action when processed by Console and SNMPTRAP actions.
- Work with Action Templates now includes an Action Template for Delete Journal Receiver.
- When an alert is acknowledged, the rule details are included on the message added to the Message Log.
- The ability to auto-export rule groups and rules to remote systems when any amendments have been made has been implemented.
- User lists can now be used wherever a user profile can be specified.
- Data areas within the product libraries are now locked *EXCLRD allowing them to be read while products are running.
- Device, Job Queue, Output Queue and TCP/IP rules now supports the automatic acknowledgment or close of open alerts when the trigger criteria is no longer valid.
- Message Queue, Device, Job Log, Job Queue, Output Queue and TCP/IP rules now support the use of a Calendar, rather than a Day/Time mask to define when rules should be checked.
- Message Communicator HMC MSGDEV authority to control the ability to send messages to message devices has been implemented.
- Display System Information can now be sent to *OUTFILE.
- Job and Output Queue rule logic has been changed to include specific queues with generic libraries.
- Support has been added for Message Sub-Consoles to give the ability to display multiple consoles with different alerts in each.
- Option 7=Messages has been added to Display Message Console to show relevant messages from the Message Log.
- Option 13=Actions has been added to Display Message Console to show Sub-Console actions performed for any given alert.
- Message Console can now retain closed alert history, including alerts sent from remote locations.
- A 'Sound alarm' option has been added to the Console action and SEND CONSOLE MESSAGE command.
- A new 'Display attribute' field has been added to the Console action to allow you to define the display color of the alert in the Message Console.
- Additional actions can be performed when an alert is added to a Sub-Console.
- User-defined options can be specified within Display Message Console and Work with Alert Log to allow the creation of bespoke options in addition to the standard options available for an alert.
- Display Message Console now shows 'No alerts to display' if no alerts exist.
- Message Manager rule counts can now be reset at midnight on each day.
- An underscore ('_') is now supported within a WatchID that is part of a 'Not received' Message Queue rule.
- Message Queue Monitor Start-up options now allow the setting of a time from which to process messages.
- Message Queue rules now support criteria for 'Accounting code' from the user profile that sent the message.
- Up to a maximum of 35 auxiliary Action Monitors can now be defined.
- Data transfer can now be actioned using the Halcyon Network Monitors rather than FTP.
- An 'Export name' can now be defined for the *SYSTEM remote location.
- New 'Time-out' default values for remote locations are shipped as standard.
- The Output Rule report now has the ability to include the rule criteria.
- Print System Status 'System available' field can now display Service Level Agreement (SLA) values.
- Job information can now be included when attaching spooled files in Send Email Message.
- Work with Rules now automatically holds rules that have been copied using option 3=Copy or the Copy Rule (CPYRULE) command.
- System default HMC/MSFTIMEOUT (Mail Server Framework Timeout) now ships set to 10 seconds.
- Support has been added for 2-way email via a Post Office Protocol (POP) email server.
- Message Communicator now supports numeric pagers.
- Message Communicator now supports sending messages to Message Queues on *LOCAL or to remote locations.
- Support for land line phones has been added to Message Communicator.
- Increased support for different line types on modems has been added.
- Work with Service Providers now includes a count of the number of High, Normal and Low priority outstanding messages to be sent.
- Work with Phones has a new field 'Tone dial time' which allows you to specify the length of ring time before hanging up.
- Support has been added for Simple Network Paging Protocol (SNPP).
- A warning message has been added to the Message Log if the required PTF level has not been applied in order to run service program QTMMCUTL.
- The ability to use SNMP as a message device when using the Send Pager Message (SNDPGRMSG) command has been added.
- Message Communicator now supports the use of an external SMTP Server for the sending of emails.
- Job log information can now be included when attaching spooled files in Send Email Message.
- Active job information can now be included when attaching spooled files in Send Email Message.
- Multi-part protected (&PROT) substitution variables can now be created.
- New substitution variable &RUNPTY has been made available to return the run priority of a job.
- Auto-export system defaults now include the time interval.
- SLA statistic functionality has been added to TCP/IP rules.
- TCP/IP rules now supports the use of a Master rule which can prevent the checking of other rules in the same group.
- A System Monitor option has been added to TCP/IP rules to check that monitors are active on an *i5 remote location.
- IPV6 addresses are now supported in TCP/IP rules.
- Remote connections to local ports can now be monitored using the *PORT rule class in TCP/IP rules.
- TCP/IP *SYSMON rules no longer raise alerts for monitors which are in a status of 'Held'.
- TCP/IP rules now allow the ability to specify a 'Hop limit'.
- Remote port status can now be checked using TCP/IP rules.
- System status information can now be included when attaching spooled files in Send Email Message.
- A fix has been applied so that PDFs created in QDLS are given the correct permissions to allow overwriting.
- A new Custom Journal Monitor has been added allowing the checking of entries in journals other than the system audit.
- Distribution Queue, Object, Performance, and User rules now support the automatic acknowledgment or close of open alerts when the trigger criteria is no longer valid.
- Audit Journal, Distribution Queue, Object, Performance, and User rules now support the use of a Calendar, rather than a Day/Time mask, to define when the rules should be checked.
- Performance Monitor now has the ability to check for cache battery warning and cache battery error messages (V7R2 and above).
- Performance *ASP rules now have the ability to monitor for growth in MB over a period of time.
- Performance *ASP 'Used %' rules no longer raise false alerts if the iASP is varied off.
- Print Audit Journal Entries report now includes the ability to include data from remote locations.
- Audit Journal rules now include the ability to specify a 'Generic select' within criteria.
- Audit Journal Entry Type Auditing Changes (AD) now includes the DLO path in the alert.
- Audit Journal Manager rules now include a 'From program' field on all audit journal entry types.
- Performance *SYSTEM rules now have the ability to monitor the current and maximum amount of unprotected storage used.
Archived Release Notes
Please check the following archive files for Level 2 Systems Operations Suite release information prior to 2015.