Modernization for IBM 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 IBM z/OS compile and promote processes intact.
- Contemporary versioning with Git or Subversion, 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 IBM 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, VS Code, Eclipse or any IDE for IBM z/OS. The sources are stored in a VCR (Git or Subversion) and then get scanned to generate a JCL, following your standards and naming conventions.
The generated JCL is submitted to IBM 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 IBM 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 DevOps solution for IBM z/OS 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.
IBM z/OS development, modernized and rejuvenated
Mainframe developers can use a 3270 terminal or an Eclipse-based workstation to edit and version (Git or Subversion) their code.
You can also use the external tool configurator feature from Eclipse to launch compile and promote jobs through IKAN ALM
The result of an IKAN ALM compile job is an archive, including sources, load modules, compile listing and all related info.
A phase for IBM z/OS 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).