Workload Automation Release Notes

Transcription

1 Workload Automation Release Notes Version: Publication Date: Automic Software GmbH

2 ii Copyright Copyright Automic and the Automic logo are trademarks owned by Automic Software GmbH (Automic). All such trademarks can be used by permission only and are subject to the written license terms. This software/computer program is proprietary and confidential to Automic Software and is only available for access and use under approved written license terms. This software/computer program is further protected by copyright laws, international treaties and other domestic and international laws and any unauthorized access or use gives rise to civil and criminal penalties. Unauthorized copying or other reproduction of any form (in whole or in part), disassembly, decompilation, reverse engineering, modification, and development of any derivative works are all strictly prohibited, and any party or person engaging in such will be prosecuted by Automic Software. No liability is accepted for any changes, mistakes, printing or production errors. Reproduction in whole or in part without permission is prohibited. Copyright Automic Software GmbH. All rights reserved. Other names may be trademarks of their respective holders.

3 Workload Automation Release Notes iii Contents 1 Version New Features Variables in JMS Uproc Return Code Branch in a Session Ended Condition New Information on Jobs in Dollar Universe Explorer Restriction on OS/ Update Notes Evolutions Outage Deletion Dollar Universe Compatibility Default behavior of Dollar Universe Explorer SLA in Dollar Universe Explorer Corrections Dollar Universe UniViewer Management Server UniViewer Console Reporter Dollar Universe Upgrade Kit Known Issues Dollar Universe UniViewer Management Server UniViewer Console Reporter Dollar Universe Explorer Dollar Universe Web Services Dollar Universe Manager for SAP Solutions Dollar Universe Manager for Microsoft SQL Server Dollar Universe Manager for Oracle Applications Dollar Universe Manager for Java Dollar Universe Manager pour JD Edwards Enterprise One Dollar Universe SPI for HP Operations Manager Dollar Universe Manager for z/os Dollar Universe Upgrade Kit... 15

4

5 Chapter 1 Version Version Please refer to the compatibility matrix for details regarding OS versions pre-requisites and standard support. Please refer to the compatibility matrix for details regarding third-party versions pre-requisites and standard support. Please note that the compatibility matrix contains the most up-to-date information and supersedes any information contained in the product documentation. Please refer to EOS/EOL announcements for details about relevant dates regarding end of support and end of life of Automic products and OS/third party support. 1.1 New Features Variables in JMS Uproc Providing tools to make the jobs more generic is part of the DNA of Automic Dollar Universe. To reach this goal, the release 6.6 proposes a new improvement for variable usage. In the JMS Uproc, all fields can contain variables that are coming from the environment, the node, the MU or the Uproc. The new included in the message body of the JMS job, defines a file. The content of this file will be insert in the message body of the JMS message at the job run. That way, you can insert complex data or dynamic values in the message body Return Code Branch in a Session OK and KO branches (Completed/Aborted) are standard when defining a Session in Dollar Universe. As of version 6.6, we add a new type of branch: the Return Code" branch. That way, you are able to define the run of a branch according to the return code of the parent job, regardless of the status of that job (Completed or Aborted). The expression of the return code to activate the branch can include intervals, values and multiples. By default a new branch will be activated for all return codes and all statuses: * is the default value. To understand the execution of the session, the history trace of the parent Uproc contains details about the activation (or not) of a branch according to the return code Ended Condition Previously, in Dollar Universe, to wait for the end of a job, regardless of its status, you had to define an OR in the launch formula between the statuses Completed and Aborted for the same job. As of version 6.6, a new value has been added in the definition of the condition: ENDED. In this case, the job will wait for the end of the specified execution Completed or Aborted. This simplifies the launch formula and add some new possibilities like wait for the end of a set of jobs and start if one of them is aborted New Information on Jobs in Dollar Universe Explorer In version 6.6, new information on jobs are displayed in Dollar Universe Explorer:

6 6 Chapter 1 Version Uproc variables Uproc script, script location or command Management Unit variables Task variables The category CMD has been renamed SCRIPT to avoid a confusion with the CMD Uproc Type. The search on the Uproc type is now available Restriction on OS/400 Return Code Branch in a Session is not available on OS/400, as the execution of a Uproc does not return any code. 1.2 Update Notes The upgrade from DUAS v5 to v is possible only from a v5.6 node with the last mandatory patch level. For other configuration, the usage of an intermediate version prior to is necessary. The upgrade from DUAS v6.x.xx to v is possible only from a v or higher version. For other configuration, the usage of an intermediate version prior to is necessary. 1.3 Evolutions Outage Deletion The Outage allows the creation of a maintenance window in the production. This maintenance window will postpone all jobs included in. When the outage was deleted, postponed jobs were still postponed. As of version 6.6, all postponed jobs will be postponed after the deletion of the outage to the date of the deletion. In this case, jobs could start immediately. You can manage this situation by holding some or all postponed jobs before the deletion. In this case, all jobs will be postponed to the time of the deletion keeping the Hold status. So you will be able to choose which job can be launched by releasing it Dollar Universe Compatibility Manager for SAP: Replacement of the RFC integration layer by NetWeaver RFC 7.2.0: full version Manager for JDE: JDE v9 compatibility iseries 7 (AS400 V7R2) compatibility Default behavior of Dollar Universe Explorer The previous default behavior for extraction of information from Dollar Universe was the following: Only remote or local tasks deployed from the repository using a template task are extracted.

7 Chapter 1 Version As of version 6.6, the default behavior has changed: All tasks of the repository are extracted, plus, all remote tasks deployed from a template task of the repository. That way, even if you do not use the deployment, information is extracted from the repository to populate Dollar Universe Explorer SLA in Dollar Universe Explorer The SLA in Dollar Universe Explorer is based on a daily period. Alerts are created if a job is not present during the day in a SLA definition. So, if a job is not scheduled on a daily basis, alert would be wrongly created. As of version 6.6, Dollar Universe Explorer checks if a job is scheduled for the day in the SLA calculation to avoid inaccurate alerts. The new status NOT PLANNED is now available to give that information to the user interface. 1.4 Corrections The following problems have been corrected: Dollar Universe pb bug21477 pb bug21418 pb bug17963 pb bug21563 pb bug21409 pb bug21511 pb bug21520 pb bug21512 pb bug21317 Cancel SAP job is now available Performance improvement. On Solaris Sparc SMF implementation could cause issues. On Unix: In specific case, uxioserv did double free of same pointer (function k_cleansrvcli). On all Unix: After upgrading from a Dollar Universe lower than with user root, some files remained owned by root and not by the Company owner. The RSY engine is now automatically started after launcher startup. Processing date with offset might not be computed correctly.. TREX_GET_ENDIAN is no longer called by the manager for SAP Solutions. Target pathname in FTP_PUT Uprocs was truncated after 133 characters.

8 8 Chapter 1 Version pb bug21558 pb bug21572 pb bug21658 pb bug21667 pb bug21348 Script was not displayed with uxshw upr after a CL_EXT type Uproc was encountered. The upgrade v5.6 to v6 node did not upgrade hidden variables (command uxhideval) Node variable and MU variable values were truncated to the first special character starting from the end. The launcher might freeze in case of high activity during reorganization. Error might occur in simulation when using offset rule on a task UniViewer Management Server pb bug21366 pb bug21660 The usage of unicryptpasswd command was incorrect. uniimpsec could not import roles from one UVMS to another UniViewer Console pb bug21556 pb bug21656 pb bug21675 pb bug20788 pb bug21265 Special days are now set in calendar for years after 2020 UVC could not open more than 400 threads simultaneously. Monitoring: In specific case, when filter on date (offset or absolute) and status we could view jobs that did not match to status filter. Business views deployed from one area to another could not be opened. Unauthorized nodes might appear in Production Plan node list.

9 Chapter 1 Version pb bug21626 In job run, it was sometimes not possible to reselect a server Reporter pb bug21549 Extraction could fail after a switch of UVMS happened in a failover architecture Dollar Universe Upgrade Kit pb bug21522 When a MU had a dependency on another MU, present in the XML export file, but not yet created, the dependency creation with the command uniimp might fail.

10 10 Chapter 2 Known Issues 2 Known Issues Java 1.7 is supported from update 45. In case of a new installation performed with a Dollar Universe kit version or earlier, if UVMS is already updated to version or higher, the registration during the installation will not be possible and the installation will fail. Please contact Technical Support if you have this configuration for a specific workaround. 2.1 Dollar Universe Uproc: a dependency condition on a remote MU and either: - Absent status - Excluded property - Fatal condition is not taken into account. Workaround: either define the conditioning on local MU, or change the conditioning on Completed/Aborted/Ended status, Expected property and/or not Fatal condition Windows only: An alert which monitors the excessively long execution time (based on absolute duration) for a Uproc, is not triggered, in Area A only Under certain condition Dollar Universe recognizes no more its UVMS in the UVMS upgrade context from cluster v6.2 to failover v6.3. Workaround: Launch following commands from the DU node in question (can be done before upgrade or after upgrade, but it's recommended to do before upgrade): unims -unregister -mshost <Host_of_upgraded_UVMS> -msport <uvms_port> -login <uvms_login> -pwd <uvms_pwd> unims -register -mshost <Host_of_upgraded_UVMS> -msport <uvms_port> -login <uvms_login> -pwd <uvms_pwd> The archiving feature of job logs does not work properly On Windows only. Due to an issue with system functionality, if a port is reserved on the very last line of the services file, the upgrade will not detect it as unavailable, and may try to assign it to one of the services used by the temporary v6. Workaround: The services file must not end by a line containing an actual used port number The duplicate permission only controls permission for the target object, not the source Non-simultaneity conditions may apply when the conditioning Uproc is in Event Wait and Running status In case of a Session that contains several occurrences of the same Uproc, if a jump exception is created on this Uproc (and the Session), the exception will only apply on the first occurrence of the Uproc. The position declared in the exception will not be taken into account When you create a Hold type exception with the CLI and option NUMLANC on a launch in Event Wait status, even though the launch will appear as Disabled right away, it is still in Event Wait status (display the exception to view the correct status) If the condition is satisfied, the job will switch to Disabled status as expected Under certain conditions, a bypass condition feature may fail in a network Session with network logical queues. Workaround: Set the variable DQM_TERM_JOB to N On Solaris: IO cannot use more than 256 FD. Specifically on a Solaris server, the IO is limited (as well as any other processes) in the

11 Chapter 2 Known Issues 11 number of FD it can use. Even if ulimit -n is set to a higher value, IO cannot use more than 256 FD (concerns FD for studio streams only). Workaround: Set a job limit in the batch queue to avoid reaching a high number of FD used by the IO engine. Set the limit to Under certain circumstances, the IO server may stop working after a call to the uxiotrclck command unigetvar/unisetvar do not apply the security check Cannot access a provoked task after an update to a scheduled task in the CLI When DUAS V6 is installed in a cluster configuration, the deployment of the submission account "administrator" damages the user service. Under certain configurations of Sun Solaris Sparc 11, the unibackup command may create empty compressed files if it is submitted in batch mode This is due to a system limitation related to the tar command. Workaround: Use the tool in interactive mode 2.2 UniViewer Management Server Some parameters of the uniimpsec and uniexpsec commands are meant to be used without any arguments, and are documented as such: - for uniexpsec : -full, -overwrite, -grpall, -grplogin, -grprole, -grpuserpattern - for uniimpsec : -full, -dependency, -merge and -overwrite The standard output of the two commands might be misleading in that a Boolean value (true or false) is appended after each of these parameters, while they do not accept any argument. In the example below, only the first command is valid: uniimpsec -file <arg> -full overwrite correct syntax uniimpsec -file <arg> -full true -overwrite false the same behavior as the command above incorrect syntax; effectively results in When the LDAP authentication mode is set to "L" and the auto-registration is activated, if the user tries to log in using the wrong letter case, a new login with the wrong letter case will be created on UVMS. This will duplicate the original login. Example: user01 & USER01 Workaround: - Deactivate the auto-registration - Only connect using right letter case - Use authentication mode "S" (LDAP Group synchronization) which will refuse the connection if the letter case is wrong. 2.3 UniViewer Console When a Web Console is run in load-balancing mode, user settings that are loaded are associated to the gateway chosen by the primary Web Console ("Master"). Two connections to the same primary Web Console may therefore load different user settings (view settings, language, favorites,...) If the java version on the desktop is older than the version on the servers, an error message may be displayed if a user is logging into UVMS with Web Console. The error message can

12 12 Chapter 2 Known Issues be ignored Under certain conditions, the actions in the UVC job runs will not work for a task with a Uproc (without a Session) created in Areas I or A in UVC. Workaround: When creating a task in UVC, save it as disabled then update the task and save it as enabled UVC is not able to handle separate DQM s for each Area With remote conditioning, if you delete a job in Event Wait status on the local node, the XA entry in the u_fmev file of the local node will be deleted but the related XA entry in the u_fmev file of the remote node will not be deleted Under certain circumstances, the node status stays in "Unknown Status" after upgrading from Dollar Universe V5.6 to V6.1, when the node is in Upgrade finished (pre-commit) status While creating a new UniJob job, the validity date may change from 01/01/2014 to 01/01/2000 and cause scheduling issues. Make sure the validity date of the jobs is 01/01/2014 or higher when saving new UniJob jobs. 2.4 Reporter It's not possible to create a keystore for a Reporter Client There is a discrepancy on how the Start Time is referenced under Reporter and Monitoring Mode>Job Runs. In some locations under Reporter the Start Time is referenced as Running Time It is not possible to install Reporter to a MSSQL database when the value of the instance is different from the default (MSSQLSERVER) On Reporter, for executions starting before the DST Winter Time Change and ending after the DST Winter Time Change, the execution time will be incorrect (In some cases, the execution time may be negative, ex: -1:00hr). This means that the report's results will not be accurate Scheduled extraction will abort if any node is unreachable or invalid; the Job Log message will return an Error Code of 1 without any further clarifications. Workaround: deleting the unreachable node or creating a node view which only contains functional nodes. 2.5 Dollar Universe Explorer The creation of a business application after the deadline time will lead to an unwanted empty failed execution for the current day. The monitoring will work correctly for the next valid monitoring window of this business application During the installation Dollar Universe Explorer does not check if the ports are available. Make sure the ports are available before installing During the first extraction, if a task is created without template task on the repository, it will be never extracted by Dollar Universe Explorer even if the user adds its template task later on If a specific task (optional or provoked) was upgraded from Dollar Universe v5 and was not associated with its main task, it will not be present in the Dollar Universe Explorer data The Export Image feature is not working on Android Browser and Internet Explorer v11. Workaround: Use other browsers, such as Chrome or Firefox

13 Chapter 2 Known Issues If the remaining memory is not more than the amount specified in DUXMAXJVMMEM (default value defined in variable.xml and can be reset by command unisetvar), Dollar Universe Explorer may have memory issue during the startup or extraction procedures. Workaround: add more memory or reduce the value of DUXMAXJVMMEM by unisetvar command Sometimes Dollar Universe Explorer s page cannot be loaded by Internet Explorer due to Internet Explorer s security policy. Workaround: The Dollar Universe Explorer URL should be added to the list of trusted sites ( In Internet Explorer: Internet options > Security > Trusted sites) Dollar Universe Explorer may generate a decode error exception in its log during its extraction If several tasks have the same name, Dollar Universe Explorer cannot distinguish them. It will take the first one it finds for the definition of all task with the same name. Workaround: Use a different task name 2.6 Dollar Universe Web Services The request purgeexecution does not purge more than one execution. 2.7 Dollar Universe Manager for SAP Solutions The variable UXSAP_EVENT_LINK is not taken into account. Workaround : Define the value using the variable UXBW_EVENT_LINK The variable UX_BAPI_ISREQUEST_GETSTATUS_TIMEOUT is not taken into account anymore If the node name has more than 10 characters, the Manager for SAP Solutions settings cannot be modified from UVC after the activation. Workaround: Modify the uxjcs.ini file manually or input all information via UVC during the activation The file dev_rfc.trc in log/rfc is not purged.. Workaround: monitor the space disk and purge manually this file when needed In the Interception Criteria, some characters are not correctly handled: - All characters with accent: à é è ù etc. - Some exotic characters: ç µ Workaround: Use of those characters is not recommended 2.8 Dollar Universe Manager for Microsoft SQL Server [Security] Permission "Manager SQL Server Configuration" doesn't apply on System User Patterns when creating a Uproc.

14 14 Chapter 2 Known Issues 2.9 Dollar Universe Manager for Oracle Applications When the manager is in debug mode, the following log error message may be displayed: Error UTL_FILE: the directory alias [alias_name] cannot be created. Workaround: Set the Dollar Universe node setting "Alias in the database for the output directory" to a value containing only uppercases characters and no specials characters An unwanted error message appears in universe.log when a Request Set is launched with DUAS although the job complete correctly Dollar Universe Manager for Java DUAS Windows 64 bits only If the java path for the Manager for Java is only accessible to 32-bit applications, and DUAS is upgraded to version or higher, the java environment for DUAS will not work anymore. Workaround: Define the java environment in a path accessible to 64-bits environment A "Read time out" error might be met during the upload of internal jar files of the manager for EJB or the manager for JMS. Workaround: copy manually the jar file on the server and register it as an external jar file in the manager settings EJB job submission may fail after a couple of submissions with version 6 and 7 of JBOSS This is linked to a JBOSS known issue Dollar Universe Manager pour JD Edwards Enterprise One Problème n A JDE Uproc ends in Aborted status when the Uproc's variable JDE_PRINT_NOW is set to Y. Workaround: Set the variable JDE_PRINT_NOW to N Dollar Universe SPI for HP Operations Manager The alarm message is not displayed on HP-OM Console when the calculator is stopped on Area A.

15 Chapter 2 Known Issues Dollar Universe Manager for z/os $UORDRE JCL ends with error when SSL mode is activated. Workaround: Don't use SSL with $UORDRE Dollar Universe Upgrade Kit Running jobs in DQM makes the uniupgrade procedure fail. Workaround: as for interactive upgrade (v5 to v6) make sure no jobs are currently running The check procedure may have warning message like : "File xxxx will not be migrated" when : - The file is U_ALR_JOB(.bat/.cmd) and the variable U_ALR_JOB is not declared in uxsetenv file - The file is the value of variable UXSPV_MSGJOB, when this variable has been declared in uxsetenv file with "export" before the variable name.

16

17