Basic considerations
The cicsML product was developed as part of the migration of assembler programs.
- For those who start with this focus, it is a much smaller challenge to convert CICS COBOL programs to Command Level.
- When transitioning to CICS Command Level, we can take full advantage of the entire range of possibilities offered by the Njema Framework. Renaming, removing unused code, restructuring, transforming code sequences, and much more.
- Our goal is not simply to “get the programs running again somehow.” Instead, we do everything we can to create programs that are easy to read and maintain.
- We only start a cicsML project after a detailed examination of the entire code. This makes it clear before the project begins how much effort will be required for the entire project: whether for testing on the customer’s system or at ITM in relation to situations that require special transformation rules.
- Of course, after the successful conversion to Command Level, the assembler program can be converted to Cobol using asmToCob. However, these should always remain two separate steps.
- Our goal is not simply to “get the programs running again somehow.” Instead, we do everything we can to create programs that are easy to read and maintain.
- We only start a cicsML project after a detailed examination of the entire code. This makes it clear before the project begins how much effort will be required for the entire project: whether for testing on the customer’s system or at ITM in relation to situations that require special transformation rules.
- Of course, after the successful conversion to command level, the assembler program can be converted to Cobol using asmToCob. However, these should always remain two separate steps.The cicsML product was developed as part of the migration of assembler programs.
cicsML projects are highly individual
Even more so than with other technology-driven migrations, we have to consider cicsML projects on a highly individual basis:
- Which CICS macros were used?
- Are the operands of the macros filled in (1) directly, (2) via CICS name references, (3) indirectly via registers, or (4) via intermediate fields?
- Are functions used that are no longer supported?
- How high is the quality of the code: readability, comments, structure, self-modifying code, or other tricks?
- Which CICS fields are addressed that are no longer “visible” at the command level?
- Are statements used that are no longer permitted in CICS?
- Are there DL/I file control calls? If so, this must be planned as a subproject, e.g., for replacing IMS.
- Which code can simply be omitted instead of being converted or emulated?
Accordingly, the Njema Transformation Factory will vary greatly from case to case: This is the only way we can achieve results that are sustainable for our customers in the long term.
Procedure, next steps
We need the entire code to perform an assessment. This will give you a clear picture of your CICS application system within a short period of time – typically 6 to 8 weeks. We show the interaction of programs, data, and fields and explain the points mentioned above.
Another result is, of course, an assessment of a possible migration, the project duration, the effort required on both sides, and the prerequisites under which such a project can be carried out.
On this basis, we will be happy to provide you with a quote for replacing your CICS macro-level programs.
This gives you a sound basis for your decision.