QC19348| Description of issue: Error message about invalid XML characters is written to the nohup.out file.Description of fix: Modified the code to strip invalid XML characters from PNODE ACCT INFO and SNODE ACCT INFO fields within the statistic notification before creating an XML string. QC19363| Description of issue: Stop engine script does not validate the password.Description of fix: Modified code to validate both user id and password when the script is invoked to stop the engine. QC19409| Description of issue: Creating or updating a user proxy local password with LCU=(.*) doesn't work.Description of fix: Modified the regular expression to account for changes that were made on the CDJAI parser, that now requires local password to be enclosed in double quotes. QC19406| Description of issue: The fields pertinent to local.node don't show up when comparing netmap objects.Description of fix: Added code to display the local.node fields that are not empty when comparing netmap objects. QC19525| Description of issue: Want negative return codes for monitored Processes to appear in hex when displayed in E-mails.Description of fix: Added code to display the return code value in hex any time it is less than zero or greater than 4095. QC19643| Description of issue: A restricted user can view data from other servers when searching for configuration objects.Description of fix: Added code to restrict a server group restricted user from viewing data that belongs to servers that are not part of his role. QC19663| Description of issue: Control Center shut itself down when the query used to populate the Completed Process Activity viewer for an SI server timed out rather than returning the data requested.Description of fix: Stopped trying to retrieve the data for previously completed Processes for SI servers the first time a Completed Process Activity viewer is opened for an SI server after Sterling Control Center starts. QC19667| Description of issue: Control Center is unable to obtain node and location values from SI server after connection established, which prevents valid statistics records from ever being generated from data collected.Description of fix: Control Center will continue to try obtaining the node and location values from SI until it succeeds, or if it has them from an earlier successful connection attempt, it will use the previously obtained values. QC19786| Description of issue: Control Center requires the user to plug in a value of to clear out a directory control.Description of fix: Added code that puts a value of if the user enters an empty string for any of the directory controls. QC19631| Description of issue: Cross site scripting vulnerability with jetty-6.1.21.Description of fix: Upgraded jetty to 6.1.26 QC19872| Description of issue: Cross referencing an e-mail list should display associated actions.Description of fix: Modified the code to display actions when cross referencing an e-mail list. QC19870| Description of issue: Duplicating a user proxy object populates the password fields.Description of fix: Emptied the password fields when duplicating a user proxy. QC19924| Description of issue: The method getUserObject when intercepted by a tool displays the password in clear text.Description of fix: Masked the password. QC19861| Description of issue: Cross frame scripting issue with web console.Description of fix: Added javascript from preventing cross frame scripting. QC19991| Description of issue: Server group changes are not captured by DVG rules.Description of fix: Added code that handles server group changes for DVGs. QC19992| Description of issue: Node configuration change events are not captured by the rules engine.Description of fix: Changed the event broadcaster that handles events. QC20151| Description of issue: Copying tcp.api parameters for a local.node record in UNIX fails.Description of fix: Modified code to format the tcp.api parameters in the form of ;, ; etc when copying the tcp.api parameters for a C:D UNIX local.node record. QC20154| Description of issue: An empty user name (CTNM KQV record) created by DMBATCH on z/OS is not honored by Control Center.Description of fix: For a functional authority on Connect: Direct z/OS that has empty contact name (CTNM KQV record or User Name as it appears on Control Center Functional Authority for z/OS console panels), Control Center will not be able to update the User Name unless the corresponding fix for this issue has been applied on the Connect: Direct z/OS node. Please contact C:D z/OS support for more information. QC20108| Description of issue: Control Center engine removes duplicate explorer nodes, if it receives a loopback address in the DtfAddress when enabled for discovery.Description of fix: Modified the code to set the address to that of the host name, if the DtfAddress returned is a loopback address. QC20324| Description of issue: Configuration jobs do not run, when certificate expiry check task runs in the background.Description of fix: Corrected the code that does certificate check to break out of the loop, when validating the certificate expiry. QC18035| Description of issue: Able to select multiple configuration objects to copy to one or more servers but only the first object gets copied.Description of fix: Corrected the code that invokes the copy logic to pass all objects to be copied to it, not just the first one. QC20447| Description of issue: Error occurs when duplicating a netmap node entry. Description of fix: Logic now using the new name specified for the duplicate instead of the originals name. QC20572| Description of issue: SQL exception (ORA-14400: inserted partition key does not map to any partition) when a queued job is cancelled twice.Description of fix: Event generated with message ID CCFG160E did not have a date/time set, and therefore when the event was attempted to be inserted into the database table, the exception occurred. Date/time is now set for the notification for message ID CCFG160E. QC20532| Description of issue: Optimize the node configuration service methods on the engine to be more efficient. Reduce the memory foot print for node configuration management on the console.Description of fix: Introduced new method that retrieves the version id, and added date/time for a given version, and returns to the client. This will reduce the overall time the console waits to get the last synchronized date/time. On the console side, objects are released from memory, when the node configuration manager, job viewer or compare panels are closed. QC20560| Description of issue: When navigating between versions for an Initparm object, the configuration manager would display empty screen.Description of fix: Added code to display the initparm object for a selected version within the node configuration manager. QC20561| Description of issue: Copy parameters to operation for initparms failed. Setting or clearing a filter for an initparm object threw a null pointer exception. A concurrent modification exception was thrown when copying initialization parameters to a large number of servers.Description of fix: This fix is a consolidation for different issues. Modified the code to use new methods that were introduced on the engine side while dealing with "Copy Parameters To", for initparms. Filter criteria always displays the initparm objects. Use the find option to search for objects instead. For the concurrent modification exception, a change on the engine side was maintain a copy of the configuration objects before manipulating the objects. QC20626| Description of issue: The BatchCreate utility is not setting the system return code value when it exits to a non zero value when a problem occurs.Description of fix: Setting the system return code to a non zero value if an error occurs when the BatchCreate utility is used. QC20671| Description of issue: Upgraded to new release and am unable to see any previously generated audit log records via report or viewer.Description of fix: Made it work as good as possible. There may still be situations where older records cannot be seen. It is advisable to run an audit log report, prior to installing any maintenance, in case older records cannot be seen. If this occurs, the audit_log database table will need to be cleared out in order to see any of the newer audit records. QC20163| Description of issue: Control Center requires the NAME in a functional authority. However, z/OS could set the NAME (CONTACT NAME) in z/OS to be blank using DMBATCH.Description of fix: Removed the restriction on the NAME field in Control Center, as well as added code to send an UNDERSCORE(_) when the user empties out the NAME field. QC20429| Description of issue: CCNCAPI does not return the available servers.Description of fix: Fixed the code that did not display the available servers for a restricted user. QC20447| Description of issue: Error received when duplicating a netmap node that says the duplicate already exists.Description of fix: Logic was incorrectly using the duplicated netmap node's name instead of the new one specified by the user. QC20474| Description of issue: SMUP150I trying to update NETMAP from SCC. Description of fix: Problem is that ENVIRONMENT values are specified up to 9 characters but the NETMAP field truncates at 6 characters. Netmap Update and Netmap Load only recognize the fully named values, not the truncated values. Need to change DMGUPNET and DMCNTMPL to accept truncated names for ENVIRONMENT. QC20515| Description of issue: Out of memory issues with Control Center console. Description of fix: Control Center console would run out of memory, if node configuration operations were performed and a large number of jobs submitted prior to logging in. The Parameter objects were never released from memory, and the code is changed to load the queued and completed jobs when the Configuration Job Viewer is launched, and the objects released once the Job Viewer is closed. QC20516| Description of issue: When there is not enough space available in the conf directory to save configuration changes, configuration files are left in the conf directory in a unusable state causing SCC's Engine to fail to start.Description of fix: When configuration files need to be udpated, write the configuration file first as a temporary file, then delete the original file and rename the temporary file to the original. Then if there is a space issue when the temporary is created, the error is reported to the user and the original configuraion object remains as is. QC20541| Description of issue: When deleting many versions of a configuration such as Functional Authorities, the list of versions to be deleted made the dialog too long to be able to see the OK or CANCEL buttons.Description of fix: Show a scrollable list of versions to be deleted in the detailed message area when the Show Details... button is clicked. QC20543| Description of issue: Spaces in the netmap node's IP Address field are not trimmed, eventually leading to a JAI parse exception.Description of fix: Added code to trim the IP Address values before sending across to the Connect: Direct Server. QC20544| Description of issue: Creating Netmap Node for CD z/OS server does not require that Class be set resulting in a failed create job. Also, when non-numeric value is in parallel session field and the OK button is selected on the advanced panel, an exception will be thrown. And the Cancel button on the Advanced panel does not restore fields to the previous values before any changes were made.Description of fix: Modified the UI to required Class to be set for new z/OS Netmap Nodes for all types (SNA, LU62, SNUF, CTCA, TCP). Cancel button on Advance panel now resets fields to values before any changes were made. And parallel sessions is validated on the Advance panel before it is used. QC20551| Description of issue: The update step for a failed copy parameters to job shows a return code of ZERO, although the final return code on the result is 8.Description of fix: Added code to display the message, message id, and return code for a failed copy parameters update step. QC20563| Description of issue: List of servers disappeared when Creating new functional authority and de-selecting a server and then going back to Server Groups and then next to Server list.Description of fix: Code changed to retain OS type so that server list can be re-built properly. QC20567| Description of issue: Error when creating netmap node and specifying operating system of OS/2 Warp or HP NonStop.Description of fix: Added code to allow all operating system types when creating netmap nodes. QC20568| Description of issue: Unmonitored CD UNIX servers stat files filling up with APKY records and unmonitored Blue washed servers that go down after SCC makes an initial connection are not detected as such.Description of fix: Rather than scheduling a periodic apkey check command, the node service is using a select functional authority command instead. CD UNIX does not log select functional authority commands that it handles, unlike apkey commands, and blue washed CD servers do not support an apkey check command at all. QC20573| Description of issue: When looking at the completed Node Configuration job viewer, some of the jobs did not have start time.Description of fix: When the Job objects are constructed from the database values, set the start time in the Job object. QC20571| Description of issue: Issues with setting the session type to "APPC and TCP/IP".Description of fix: Fixed issues related to setting the session type to "APPC and TCP/IP". The required fields are now marked red, based on the appropriate session type. Properties for a netmap node entry show the session type as "APPC and TCP/IP", if that is what is selected. QC20578| Description of issue: When duplicating a config object and not changing the name, no error was thrown about a duplicate name.Description of fix: List of current objects is now updated properly. QC20587| Description of issue: SCC Console did not display correct time of the engine's host on the console status bar.Description of fix: When the Console is started, engine's host machine time is retrieved and displayed and then the time updated every 15 seconds. QC20593| Description of issue: Error when adding netmap node with operating system of OS/2 Wrap.Description of fix: Added code to allow all different types of operating systems, including OS2, and remove OS/2 Wrap from list of operating systems. QC20599| Description of issue: When creating new node from existing node, the list of available nodes on servers is not updated with latest entries.Description of fix: Added code to retrieve the configuration objects from the latest version, and update the references that are held in the CCNode object. QC20609| Description of issue: Unable to revert to previous Secure+ Node version if alias nodes needed to be added. Steps for job would indicate there was no issue, but the job always had a return code of eight.Description of fix: Corrected the logic that builds the command to add Secure+ alias nodes so revert jobs no longer failed. QC20623| Description of issue: Secure+ Node Summary Panel show Cipher Suite as NULL when Default to Local Node Selected.Description of fix: Change Summary to display Cipher Suite of DefaultToLN when Default to Local Node selected. QC20630| Description of issue: Exception while viewing the steps for a queued job.Description of fix: Added code to always retreive the job results from the engine, if the View Steps button in the Step Viewer is clicked. A busy cursor is displayed when launching the step viewer for a job with large number of steps. QC20639| Description of issue: Create job fails with a invalid TCP CRC value of D when Unix Netmap Node created from Z/OS Netmap Node that has its TCP CRC setting set to Default.Description of fix: Change Z/OS TCP CRC Netmap Node value of D (Default) to N when using Z/OS Netmap Node to create a Unix Netmap Node. QC20650| Description of issue: Audit log entries are showing things that weren't changed as being changed and adding spurious characters - e.g. double quotes, around values and indicating that they were updated when they were not.Description of fix: Logic is now using before and after values as received from the Server as opposed to using the before from the server and the after value from elsewhere. QC20666| Description of issue: The console appears frozen when it waits for the engine to return a job id.Description of fix: Modified code to take advantage of a new method that takes in a list of servers, and build a map of config object ids for each server. Since the Control Center console no longer retains configuration objects in memory, it goes to the engine, gets the config object ids for the selected servers or servers with in a server group, and builds the parameters by getting the configuration objects from the engine again, and sends the configuration object built with parameters pertinent to the parameter that was intended to be copied to the servers that were selected. The user would notice multiple progress bars when the "Copy Parameters To" operation runs. QC20668| Description of issue: The job properties for a queued job would cause the console to freeze. The job was a "Copy Parameters To" operation for initialization parameters.Description of fix: Modified the code by using a new method that takes in a map of server ids and config objects, instead of a legacy method on the engine side that caused issues. QC20673| Description of issue: During a copy to operation, the modes that are displayed in the combobox are not the one's that are common across all the servers.Description of fix: Added code to display only the modes that are common across all the servers, for the "Copy To" operation only. QC20707| Description of issue: Copy Parameters To a server group that contains servers that are not running, does not work.Description of fix: Added code that checks to see if a node is running before waiting for the last synchronization to be filled. QC20708| Description of issue: When a configuration job on the Job Queue Viewer has a large number of steps, updates to the job properties made is nearly impossible to select the job to view the steps as the updates cleared the selection before there was time to select the View Steps button.Description of fix: Modified the code to only update the job properites on the Queue Job Viewer if the property values have changed instead of with every event on that job. QC20657| Description of issue: Saving of a configuration job with multiple servers and multiple objects needs to be sped up.Description of fix: Batched the inserts of the Job objects into the DB QC20717| Description of issue: Creating a new user proxy panel throws a "Server Groups/Servers" required error despite chosing a server group, with no servers selected.Description of fix: Added code that creates a set of OS types based on the servers tat are selected. QC20721| Description of issue: Report listing displays a subset of the reports when one of the existing reports is updated.Description of fix: Added code to write to the disk without writing to a temporary file and then renaming the temporary file, while dealing with reports from the console. QC20649| Description of issue: When configuration jobs are submitted that involve servers that are down, never contacted, or paused, an exception would be thrown and displayed by the GUI at job submission time.Description of fix: Server validation and user authentication checks for Configuration jobs are now made at job run time, and rather than not running the job at all. So the job will run with individual steps being failed instead of the whole job just not running. QC20709| Description of issue: When doing Netmap Node "Copy To" and "Create New" from existing Netmap Nodes, the Session Type is not always set.Description of fix: Made sure a servers Netmap Comm Paths are loaded before setting Session Type on new netmap node panels. QC20718| Description of issue: Unable to update Netmap modes. Seeing parser error when attempted.Description of fix: Pass appropriate value for CRC when updating Netmap modes. QC20733| Description of issue: Viewing an alert's properties fails in Web Client.Description of fix: Code was changed remove the invalid casting of ArrayList to CCChildren QC20734| Description of issue: Handling an alert from Web client fails.Description of fix: Code was changed to check for null R140582| Description of issue: Test Connection to a Connect: Direct z/OS node only works if the user's authority has a SELECT NETMAP authority.Description of fix: Modified the code so that the SELECT NETMAP authority is not checked except when discovering nodes. R148176| Description of issue: The server count on the node tree is not accurate in terms of the number of servers that are running.Description of fix: Added code that refreshes the node count across all the groups (user, typed) every 15 seconds, and repaints the tree. The client log now displays the previously running count versus the new count in case the size of the running nodes changes. R148183| Description of issue: Functional authorities do not get deleted although the return codes do not indicate an issue.Description of fix: Control Center console logic would prevent it from displaying user authorities on z/OS that were equal although the case was different. Fixed the code that would compare objects based on their ids while ignoring case. R140623| Description of issue: Control Center consoles freezes when the Please Wait progress bar is closed.Description of fix: Added code that checks to see if the task got cancelled, while the progress bar runs. R148182| Description of issue: Seeing UhOh message in log file when running Node Discovery on CD zOS 4.8 and above servers.Description of fix: Discovery logic now looking for both TCP.ADDR and TCP.LISTEN values in server's initialization parameter file for needed values. R140535| Description of issue: Control Center installer overrides the Jetty secure port. Description of fix: Modified the Control Center GUI installer in order for it to not override the Jetty secure port. R171945| Description of issue: After canceling an inprogress Node Discovery, you are unable to enable existing explorer nodes, see the properties of existing explorer nodes, or basically do anything but initiate a new Node Discovery run without having the system tell you there's a problem.Description of fix: Fix was to reset the attribute that indicates a cancellation of Node Discovery is in progress once the cancellation is complete. R152851| Description of issue: Engine experiences Out of Memory when multiple servers with large number of config objects are involved in a single report.Description of fix: Only retrieve the config objects when needed for the report and remove references afterwards. R138018| Description of issue: The progress bar waits indefinitely when a refresh job fails due to a command that fails on the Connect: Direct server.Description of fix: Added code that checks to see if the return code of the job is not a GOOD RC (0), before waiting for the lastSynchronization time to be set. R138083| Description of issue: Need an API for configuration management with Control Center.Description of fix: Control Center is now shipped with CCNCAPI, along with the documents pertinent to using the API. R138188| Description of issue: When building templates based on node's configuration objects, the referenced object memory was not released.Description of fix: No more than one config object is referenced at any time and when the dialogs are exited, all config objects are dereferenced. R171943| Description of issue: CRC values on Functional Authority and Netmap Node Configuration Reports are not listed.Description of fix: When getting CRC report data, specify the platform (Windows, Unix, or zOS) so that report labels can be the same for all platforms but the internal data keys can be different. R138057| Description of issue: When multiple server types are selected for a report, the various selectable fields was not complete.Description of fix: Change code to include all selectable fields for each platform. R138188| Description of issue: When building templates based on node's configuration objects, the referenced object memory was not released.Description of fix: No more than one config object is referenced at any time and when the dialogs are exited, all config objects are dereferenced. R171943| Description of issue: CRC values on Functional Authority and Netmap Node Configuration Reports are not listed.Description of fix: When getting CRC report data, specify the platform (Windows, Unix, or zOS) so that report labels can be the same for all platforms but the internal data keys can be different. R138127| Description of issue: Once a new version of Initparms for a server has been made and while still in config mgr, Copy Parameters To... does not build the update job step in the job.Description of fix: Corrected code to retain the pointer to the version in the Initparm object. R148172| Description of issue: One user performing Node Discovery (enabling a node for discovery) caused a "Please wait" dialog to popup on other GUIs.Description of fix: Cache Node Discovery data at logon time. R147952| Description of issue: Control Center requires the NAME in a functional authority. However, z/OS could set the NAME (CONTACT NAME) in z/OS to be blank using DMBATCH.Description of fix: Removed the restriction on the NAME field in Control Center, as well as added code to send an UNDERSCORE(_) when the user empties out the NAME field. R137885| Description of issue: Extraneous message in log caused by updating a non-C:D node (one that can't have File Agents).Description of fix: Recognize that node can't have File Agents and don't issue message. R137915| Description of issue: Sterling MIB missing some trap variables.Description of fix: Added all possible variables to the SCC trap definitions in the Sterling MIB R138243| Description of issue: The words "null," were separating Object IDs in the Queued/Completed Job Viewer.Description of fix: Recognize that "null" or "null," was being put into the list of Object IDs and eliminate it. R138257| Description of issue: The Confirm Choices panel for CTCA shows values that are not valid for CTCA.Description of fix: Prune confirm choices tags when dealing with CTCA R138186| Description of issue: When using "Copy To" for Windows Netmap Node in Configuration Manager, the TCPIP, APPC, and/or UDT33 Modes are not set.Description of fix: Modified code to save and set Mode after the target "Copy To" server has been selected. R138182| Description of issue: Changing the time to perform configuration change checks does not take affect until tomorrow.Description of fix: Have the system cancel any scheduled tasks whenever the time to perform configuration change checks is changed. R137860| Description of issue: CSNM004E SNMP Adaptor: No value specified for /service/trapElements/serverMetaData5, using default value of 0.Description of fix: Added the attribute serverMetaData5 to the xml file. R138012| Description of issue: Whenever tracing is enabled for a C:D 400 node, disabling it didn't turn the tracing values.Description of fix: Turn off the tracing values when not in DEBUG. R138177| Description of issue: When creating z/OS SNA/SNUF/LU62 Netmap Nodes, APPLID is required but not enforced by GUI. When creating z/OS LU62 Netmap Nodes, Logmode is required but not enforced by GUI. When creating z/OS SNUF Netmap Nodes, Remote Library is required but not enforced by GUI. Description of fix: Changed GUI to to require APPLID for SNA, SNUF and LU62 z/OS Netmap Nodes. Changed GUI to require Logmode for LU62 z/OS Netmap Nodes. And changed GUI to to require Remote Library SNUF z/OS Netmap Nodes. R138255| Description of issue: For C:D z/OS CTCA Netmap entries, Data Direction of SEND or RECEIVE should be the only valid values.Description of fix: Change pull-down list for CTCA node to include SEND and RECEIVE only. R153004| Description of issue: The hard coded limit of 5000 rows for reports needs to be exposed.Description of fix: Exposed the limit in ReportService.xml R138098| Description of issue: List of servers disappeared when Creating New FA and unselecting a server and then going back to Server Groups and then Next to Server list.Description of fix: Code changed to retain os type so that server list can be re-built properly. R138227| Description of issue: Secure+ Node Summary Panel show Cipher Suite as NULL when Default to Local Node is selected.Description of fix: Change Summary to display Cipher Suite of DefaultToLN when Default to Local Node is selected. R148180| Description of issue: User timezone preference not honored for Configuration Job Viewer/Filter.Description of fix: Honor user timezone preference in Configuration Job Viewer/Filter. R152997| Description of issue: Filter criteria for Initparms Reports was not being honored.Description of fix: Honor filter criteria for Initparms Reports. R311687| Description of issue: Node configuration management reports display empty values for the value column, irrespective of the type of node or the number of parameters that are selected.Description of fix: Added code with in the Browser Agent in order for it to wait until all the node services have initialized, before requesting the engine for node properties and status. R310794| Description of issue: Control Center user with permissions set to none for "Users" or "Roles" can execute the "Users-Roles Summary Report". Similarly, permissions set for SLCs to none, allow the user to execute the SLC Summary Report.Description of fix: Modified the code to prevent a user with permissions for "Users or Roles" set to none from executing the "Users-Roles Summary Report", and SLCs set to none from executing the SLC Summary Report.