CICS

Basic considerations

  • The cicsML product originated as part of the migration of assembly programs.
  • For those starting with this focus, converting CICS COBOL programs to the command level is a significantly smaller challenge.
  • When transitioning to the CICS command level, we can fully utilize the entire range of possibilities offered by the Rashid framework: renaming, removing unused code, restructuring, transforming code sequences, and more.
  • Our goal isn’t simply to „get the programs running again somehow.“ Instead, we focus on creating highly readable and maintainable programs.
  • We only begin a cicsML project after a detailed analysis of the entire codebase. This ensures that the required effort for the entire project is clear even before the project starts: whether for testing on the customer’s system or for ITM (Integrated Technology Management) regarding situations that require specific transformation rules.
  • Of course, after successful conversion to the command level, the assembly program can be converted to COBOL using asmToCob. These should always remain two separate steps.

cicsML Projects are very individual

Even more so than with other technologically driven migrations, we need to consider cicsML projects very individually:

  • Which CICS macros were used?
  • Are the macro operands (1) directly, (2) via CICS name references, (3) indirectly via registers, or (4) via intermediate fields?
  • Are any functions used that are no longer supported?
  • What is the quality of the code: readability, comments, structure, self-modifying code, or other workarounds?
  • Which CICS fields are being accessed that are no longer visible at the command level?
  • Are any statements being used that are no longer permitted in CICS?
  • Are there any DL/I file control calls? If so, this needs to be planned as a subproject, e.g., to replace IMS.
  • Which code can simply be removed instead of being restructured or emulated?

Accordingly, the Rashid 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 complete code to conduct an assessment. This will give you a clear picture of your CICS application system within a short timeframe—typically 6 to 8 weeks. We will demonstrate the interaction of programs, data, and fields and explain the points mentioned above.

Another outcome is, of course, an assessment of a potential migration, the project duration, the effort required from both sides, and the prerequisites for carrying out such a project.

Based on this, we would be happy to provide you with a quote for replacing your CICS Macro Level programs.

This gives you a sound basis for your decision.