1. Transparent Development Demo Day May 2017
May 17th 2017

2. Disclaimer
HCL’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at HCL’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.
Do not use any Content provided on developerWorks to develop software or services that provide the same or similar functionality.
Please refer to the developerWorks terms of use for more information.

3. Agenda Beta Program Demo from the development organization
Revamped user experience of Plan Monitoring with the new Graphical Views
Enhanced monitoring
Enhanced dependency management
Enhanced impact management integration
Release management and condition-based workload automation enhancements
New options in managing workload applications
Job condition met
Workload Automation plug-in for IBM UrbanCode Deploy
DevOps: Export and Import Application definitions on z/OS

4. Agenda
Beta Program

5. Beta Program overview What Collaboration do we offer?
Beta Program for the Workload Scheduler for zOS product was launched on May 15
The program will give you the chance to:
Access new Workload Scheduler code in advance to test our new features
Provide your feedback to help us improve the functionalities
To participate, send an to one of the following contacts:
Within 24h, you’ll receive an with a link to access a download page.
All the libraries will be available for 24 hours for download. On the same download page, a Readme file will be available containing a description of the contents available in the Beta.
Any questions or feedback can be sent to the contacts listed above. We’ll provide support and answer any questions you may have.

6. Agenda
Demo from the development organization

7. Revamped user experience of plan monitoring with the new graphical views final demo

8. Agenda
Introduction Enhanced monitoring Enhanced dependency management Enhanced impact management integration ... and more....

9. Plan Dependecy Management
Introduction
During this demo, we will see the the new graphical views implementation delivered during this sprint, as well as what has been delivered for enhancing the user experience in the following scenarios:
Impact Analysis
Monitoring Workload
Plan Dependecy Management

10. Monitoring Workload
Monitoring Workload
Simultaneous monitoring of multiple job streams View same object arrangement as defined in the designer Endless navigation and plan exploration Live update Faster view exploration Faster action execution Rearrange objects in the view Quick status detection

11. Monitoring Workload
Monitoring Workload
Simultaneous monitoring of multiple job streams View same object arrangement as defined in the designer Endless navigation and plan exploration Live update Faster view exploration Faster action execution Rearrange objects in the view Quick status detection

12. Monitoring Workload
Monitoring Workload
Simultaneous monitoring of multiple job streams View same object arrangement as defined in the designer Endless navigation and plan exploration Live update Faster view exploration Faster action execution Rearrange objects in the view Quick status detection

13. Monitoring Workload
Monitoring Workload
Simultaneous monitoring of multiple job streams View same object arrangement as defined in the designer Endless navigation and plan exploration Live update Faster view exploration Faster action execution Rearrange objects in the view Quick status detection

14. Impact Analysis
Impact Analysis
Launching What-if on a single job stream Launching What-if on all of the job streams in the view Show impact on critical jobs Show all or multi-level predecessor and successor dependencies

15. Impact Analysis
Impact Analysis
Launching What-if on a single job stream Launching What-if on all of the job streams in the view Show impact on critical jobs Show all or multi-level predecessor and successor dependencies

16. Plan dependecy managment
Plan dependecy management
Plan dependecy managment
Monitoring Workload
Quick creation of dependencies even in different job streams Quick analysis of dependency graph with dependency highlights Highlight of dependency status Create dependency on other job/job stream with lookups

17. Plan dependecy managment
Plan dependecy management
Plan dependecy managment
Monitoring Workload
Quick creation of dependencies even in different job streams Quick analysis of dependency graph with dependency highlights Highlight of dependency status Create dependency on other job/job stream with lookups

18. Plan dependecy managment
Plan dependecy management
Plan dependecy managment
Monitoring Workload
Quick creation of dependencies even in different job streams Quick analysis of dependency graph with dependency highlights Highlight of dependency status Create dependency on other job/job stream with lookups

19. Plan dependecy managment
Monitoring Workload
Quick creation of dependencies even in different job streams Quick analysis of dependency graph with dependency highlights Highlight of dependency status Create dependency on other job/job stream with lookups (available also on the plan view)

20. .. and more
Share views easily with launch-in- context for any view Export to PNG and SVG Direct print YouTube playlist integration with additional help Quick find action Touch-ready interface

21. Release management and condition-based workload automation enhancements
Lorenzo Amorosa
May, 2017

22. New options in managing workload applications:
Release management and condition-based workload automation enhancements
New options in managing workload applications:
During the import process, automatically modify the mapping file according to the rules defined using regular expressions
Optionally rename a workload application during the import process
Job condition met:
Rerun successful jobs until the specified output condition is met

23. Using regular expressions to modify the mapping file
Release management and condition-based workload automation enhancements
Using regular expressions to modify the mapping file
The mapping file produced by the export process of a workload application contains a list of elements, some of which are dependent on the topology of the environment in which it is used.
These elements need to be customized to match the target environment.
When the import process is performed from the wappman command line, you can optionally request that the mapping file is automatically modified according to rules defined using regular expressions.

24. Using regular expressions to modify the mapping file
Release management and condition-based workload automation enhancements
Using regular expressions to modify the mapping file
The rules can be specified in one of the following ad-hoc files:
workload applicationname_BasicRegExpMapping.UTF8.rules
This file contains rules defined using basic regular expressions that include only '*' and '?' wildcard characters.
workload applicationname_AdvancedRegExpMapping.UTF8.rules
This file contains rules defined using advanced regular expressions according to Java standards.
These files are produced by the export process and, if used, must be properly customized.

25. Using regular expressions to modify the mapping file
Release management and condition-based workload automation enhancements
Using regular expressions to modify the mapping file
[JOBSTREAM]
*_DEV=*_PRD
According to the above rule the job stream CCB_DEV is renamed as CCB_PRD
wappman -import <definition_xml_file> <mapping_properties_file> -translationRules <translation_rules_file>

26. Rename a workload application during the import process
Release management and condition-based workload automation enhancements
Rename a workload application during the import process
During the import process (both from the DWC and wappman) you can optionally use a new workload application name.
-workloadApplicationName
The name of the workload application, in case you want to import it with a new name.
wappman -import <definition_xml_file> <mapping_properties_file> -workloadApplicationName <newWAName>

27. Rename a workload application during the import process
Release management and condition-based workload automation enhancements
Rename a workload application during the import process

28. Release management and condition-based workload automation enhancements
Job Condition met
Use this section to specify the output condition to be monitored. The job is rerun until the specified condition is met or the job's deadline expires.
You can specify the following properties of a job inside a job stream:
Output condition value
Specify the value of the condition to be monitored. For example, if you are monitoring a job which extracts data from a database and want the related job stream to start when the number of rows in the database is greater than zero, then type the following string: ${this.NumberOfRows} > 0
Interval (ss)
A period of time in seconds between two consecutive checks on the condition.

29. Release management and condition-based workload automation enhancements
Job Condition met
SCHEDULE S_AGT#JS_JOB_COND_MET :
S_AGT#JOB_COND_MET
OUTCOND "RC=60" INTERVAL 20
END

30. Release management and condition-based workload automation enhancements
Job Condition met
The job is rerun until the condition is satisfied (RC=60)

31. Release management and condition-based workload automation enhancements
Job Condition met
The same information can be displayed by conman using show job and stdlist.

32. Workload Automation plug-in for IBM UrbanCode Deploy
Maria Elena Massino

33. The context
Rob, an application developer, has developed a web application that includes a Workload Automation job stream that is subbmited at the user’s request.
The application is already in production, but now he needs to modify it.
The change involves also the Workload Automation job stream definition.
The source code for the application and the job stream definition are stored in Eclipse that is configured to check in to Rational Team Concert (RTC), his software development tool.
Rob uses IBM UrbanCode Deploy to automate the deployment process into production.

34. IBM UrbanCode Deploy definitions

35. IBM UrbanCode Deploy - Component
Rob has a UCD component that extracts new versions of a Workload Automation job stream definition from Rational Team Concert

36. IBM UrbanCode Deploy – The Component process
Rob’s deploy process uses the Workload Automation for UCD plug-in to deploy new versions of the Workload Automation job stream definition into the Workload Automation distributed production environment of his company.

37. IBM UrbanCode Deploy – The Application Environment
In the production environment, Rob has defined the environment properties to map Workload Automation objects in the test environment to Workload Automation objects in the production environment (1).
He also uses a regular expression to modify the job stream name (2). 2 1

38. The scenario

39. The scenario – Download the new job stream definition
Rob makes the necessary changes in the job stream definition from the Workload Designer opened in the test environment and tests the new definition by submitting it into the current plan.
Then he extracts the job stream definition using the new action «Download Job Stream Definition»

40. The scenario – Check in the job stream definition into RTC
Rob copies the zip file to Rational Team Concert and makes changes to his application.
He then delivers all the changes on the server.

41. The scenario – Import the new version of job stream definition into uDeploy
Rob imports the new version of the application into IBM UrbanCode Deploy.
Version 2.0 is created containing the new zip file.

42. The scenario – Deploy the application into the production environment (1/4)
Rob starts the deploy process for the production environment on IBM UrbanCode Deploy

43. The scenario – Deploy the application into the production environment (2/4)

44. The scenario – Deploy the application into the production environment (3/4)

45. The scenario – Deploy the application into the production environment (4/4)

46. The scenario – The deployed application
The application has been deployed into the production environment.
Objects have been correctly mapped.
The regular expression for the name has been applied.

47. Environment Properties for
Workload Automation plug-in
for UCD

48. Mapping objects PAYROLL_Mapping.UTF8.properties Name:
<PREFIX>_<OBJECT-TYPE>_<OLDVALUE>
Value:
<NEWVALUE>

49. Apply regular expressions to objects
PAYROLL_AdvancedRegExpMapping.UTF8.rules
Name:
<PREFIX>_REGEX_<OBJECT-TYPE>_<SELECTIONREGEX>
Value:
<REPLACEREGEX>

50. Deploy on z/OS

51. The deploy process for z/OS

52. The Application Environment for z/OS
Name:
<PREFIX>_<OBJECT-TYPE>_<OLDNAME>
Value:
<NEWNAME>

53. DevOps Export and Import Application Definitions on z/OS

54. DevOps - Export and Import application definitions overview
Applications can be exported and imported so that they can be shared with other IBM Workload Scheduler for z/OS environments. In the new environment, the application can be subsequently updated, replaced, or deleted.
To promote an application from one environment to another, you can use either the ISPF panels or the Dynamic Workload Console V9.4, Fix Pack 1.
Next slides describe the ISPF panel flow to Export and Import application definitions. 54

55. DevOps Export/Import (1)
The EXPORT/IMPORT feature can be invoked directly by the LIST OF APPLICATIONS PANEL (EQQALSTL) using the new X - DevOps command: 55

56. DevOps Export/Import(2)
Or by a new option in the panel MAINTAINING APPLICATION DESCRIPTIONS (EQQASUBP):

57. EXPORT (1)
Identify the application to export from one environment to another:

58. EXPORT (2)
A JCL is automatically generated to submit a WAPL exec that exports the definitions of our application and of all the objects that it uses (Calendars, workstations, special resources...)
The object definitions are WAPL statements that are stored in a dataset

59. EXPORT (3)
An example of exported statements in WAPL format:

60. IMPORT (1)
Before importing application definitions you can set up «Translate» rules in the TRANSLATE DATASET:

61. IMPORT (2)
A JCL is automatically generated to submit a WAPL exec that imports the definitions of our application and of all the objects that it uses (Calendars, workstations, special resources...):

62. IMPORT (3)
The application has been imported based on the «Translate» rules previously set up:

63. Thanks for participating!