Modernization for z/OS mainframes
Mainframes are a vital part of today's software ecosystem, alongside mobile -and web applications. The digital world expects agility, Continuous Integration and Continuous Deployment. IKAN ALM brings the same agility to the mainframe while leaving the vital z/OS compile and promote processes intact.
- Contemporary versioning safeguards your code and makes parallel development and the use of modern IDE's possible
- Automated Compile JCL's are generated. We run the job, collect the compile listing and load modules in an archive.
- Automated Promote (Deploy) JCL's are generated. JCL steps are available for DB2 binds, running test software, CICS updates,...
- Optional approvals can be added Promote (Deploy) jobs.
- Languages support:
Assembler, COBOL, PL/1, 4GL’s, IDMS ADSO.
- Databases support:
vsam, ims, db2, Datacom, IDMS,...
- Tools support:
BMC, Compuware, IBM, ASG,...
View all features...
Orchestrate your z/OS toolchain
IKAN ALM uses standardized JCL to automate your existing tools, there's no need to change anything. The only difference is that you will be using a web-based interface to launch Compile and Promote (Deploy) actions.
Every (JCL) step is logged, including Compile (sources, listing, load modules,..) and Promote, to be consulted at any time.
Impact Analysis and an Audit module to detect out-of-sync situations, are also included.
All you need to do is enter the related ticket (identifier) from your favorite requirements or issue tracking tool when commiting code.
IKAN ALM will commence the process flow, update the ticket in your requirement or issue tracking tool, and inform you about which builds and deploys the ticket is part of.
Source code can be written in a 3270 terminal, Eclipse or any IDE for z/OS. The sources are stored in a VCR and then get scanned to generate a JCL, following your standards and naming conventions.
The generated JCL is submitted to z/OS for compilation. When finished, the results are retrieved by IKAN ALM and collected in an archive. Every step of this process is logged.
As part of the process you can promote code to test libraries or you can generate a JCL step to run tools like Compuware Xpeditor, Smartest,...
Based on the load modules in the archive (created in the "Create" step), IKAN ALM adds the necessary JCL steps. These steps include having the correct library names and doing the necessary DB2 binds or CICS updates.
The generated JCL is submitted to z/OS for Promotion (Deploy). This entire process is logged.
Leading you from idea to implementation in 3 simple steps
Together we analyze your current development and release process and define the optimal z/OS DevOps solution for your company. We clearly draw the roadmap on how to get there.
Next we proof that the proposed solution works, by example. It takes only one week to deliver our proof-of-concept!
After the POC is finished we have your business case ready, give you a commercial proposal and begin implementing the solution.
z/OS development, modernized and rejuvenated
Mainframe developers can use a 3270 terminal or an Eclipse-based workstation to edit and version their code.
You can also use the external tool configurator feature from Eclipse to launch compile and promote jobs through IKAN ALM
Get free insight!
Let us give you personal insight on how DevOps can make your z/OS development -and release process much faster and reliable.Yes, give me insight
The result of an IKAN ALM compile job is an archive, including sources, load modules, compile listing and all related info.
A z/OS phase to configure a debugger: Abendaid, Smartest, Xpeditor...
IKAN ALM will then generate the necesssary JCL steps, according to your conventions (company name,...)
Every single action is logged. In this example: the requirements and the link to an external Issue Tracking system (Atlassian JIRA).
What our customers are saying
Antonio Motta - ICT infrastructure manager, RMA (Italy)
"Our goal was to have one product, that managed the whole build and deploy process for all the platforms we used to deliver our IT services. We saved more than 2/3 on the software maintenance cost."
Jim McGrath - Data Warehouse Manager, Constellation Brands (USA)
"My internal team was excited about the possibilities your software offers and is anxious to hear next steps. Additionally, you should know that I have ensured my team knows the level of effort and support your team has provided.
It is hands down the best support I have seen from any vendor I’ve worked with."
Willy Mutsaerts - Technology Architect and Software asset management, P&V (Belgium)
"IKAN ALM allowed us to modernize our mainframe development as we wanted to use an eclipse based development environment and needed to have a compatible life cycle management solution to replace our current mainframe only version control software.
And IKAN ALM allowed us to interface with the mainframe and has extensive customization possibilities."
Watch Mr. Mutsaerts talk about IKAN ALM:
Jerome Rouil - IT Team Manager, GMF COVEA group (France)
"We did a POC to verify if IKAN ALM could support our different ways of deploying (on different types of platforms), our current way of doing development and the build and deploy scripts we were currently using.
IKAN ALM allows us to work from everywhere, and to reuse existing scripts. We could use our existing security system (LDAP), SMTP for messaging and notifications.
We use IKAN ALM for all our JAVA applications and SAS reporting that are deployed to 30 different locations"
Guido Klopper - IT Manager Business Intelligence, Tata Steel Group (Europe)
"After a detailed comparison and a successful POC, we concluded that IKAN ALM would be the best option for us.
Installation and customization took about a week. Now we have not only obtained significant savings, but also more frequent, faster and reliable deploys, and happy business users"
People are choosing DevOps because they want
As developers will version their code and as parallel development is supported you will have a more sound code base. Managing the many different releases and hot fixes becomes fast, transparent and reliable.
More frequent deploys
A complete and automated process (build, deploy, approval and notification) is triggered once a developer commits his code to the version control repository. This process is reliable, repeatable and auditable so you can you can deploy more frequently.
Lower development costs
More frequent and qualitative deploys means happy business people since they'll have their desired functionality available faster. The automated process eliminates human mistakes and allows people to do more interesting work. A true win/win.