UNICOM Systems :: Comet


Comet

Migrate with the Leader

Comet is the industry leading solution for migrating your macro level applications to CICS Transaction Server. We understand that your applications are complex and that you may not even have the source available. We have the experience and a proven track record to make your migration successful. Comet automatically intercepts the Macro level calls and dynamically translates them to the correct Command level calls without the need to waste valuable developer time with source code changes or program re-linking.

  • OVERVIEW
    OVERVIEW
    OVERVIEW
    OVERVIEW
    OVERVIEW
    OVERVIEW
  • AT-A-GLANCE
    AT-A-GLANCE
    AT-A-GLANCE
    AT-A-GLANCE
    AT-A-GLANCE
    AT-A-GLANCE
  • FEATURES
    FEATURES
    FEATURES
    FEATURES
    FEATURES
    FEATURES
  • RESOURCES
    RESOURCES
    RESOURCES
    RESOURCES
    RESOURCES
    RESOURCES
  • REQUIREMENTS
    REQUIREMENTS
    REQUIREMENTS
    REQUIREMENTS
    REQUIREMENTS
    REQUIREMENTS

OVERVIEW

Comet examines your applications when they are loaded into CICS and dynamically translates all Macro level calls into Command level calls without any source changes.

With Comet your Macro level programs can run with CEDF so programmers can see the exact Command level statements as they execute. They can see the exact Command level calls and parameters they need to use for even the most complicated Macro level programs. But why invest your precious resources now on the conversion to Command level? With Comet you can be in production immediately and convert your programs over time as you perform normal maintenance.

Comet requires a small stub (similar to the CICS command level stub-DFHEAI, DFHECI, or DFHEPI) to be appended to every program it translates. You could relink the program to include the stub, but relining is troublesome. Your relinked programs cannot run in versions of CICS below 3.1 without Comet. So, until you make the move to CICS/TS permanently, you have to maintain two libraries. When source code changes, you have to make those changes in both libraries. Comet eliminates this hassle by dynamically attaching its stub to programs. No relining is necessary.

CICS Comet Stub.pngSome software programs use the CICS exit XPCFTCH to dynamically attach themselves to user programs. This exit is called every time you use a program, whether that program is to be dynamically attached or not. On a normal system, the total number of program uses per day is extremely high – five, ten, fifteen million per day. (On the average, you will have 4.5 times more program uses than transactions run.)

AT-A-GLANCE

  • Dynamic macro level translation into command level
  • Application developer tools with command level view
  • Virtual Storage Constraint Relief
  • Program include / program exlude
  • Highly customizable
  • Also supports Assembler, PL/I, VS/COBOL, COBOL II, and BMS Mapsets
  • Supports the latest changes in IBM LE
  • Supports CICS Global User Exits (GLUE) and by Task-Related User Exits (TRUE)

FEATURES

  • Run Macro level programs under CICS/TS.
    Migrate to CICS/TS without the conversion cost, headaches or delay.
  • Immediate Assembler, PL/I, VS/COBOL, COBOL II, and BMS Mapsets application deployment
    Dynamically attaches itself to your macro level programs without relining. All standard and non-standard API Macro level calls are handled automatically.
  • Virtual storage constraint relief
    Automatically m ove programs and BMS map and map sets above the 16 meg line automatically freeing up more memory for your critical applications!
  • Mixed mode support
    Handles mixed-mode (Macro and Command level together) programs.
  • Application development tools
    Supports the use of IBM's CEDF for debugging your Macro level programs.
  • Macro level integrity analysis
    Handles all Macro level calls that access the FCT, DCT, PCT, and TCT chains directly.
  • User Exit support
    CICS Global User Exits (GLUE) and by Task-Related User Exits (TRUE)

RESOURCES

REQUIREMENTS

  • Mainframe
    IBM z/Architecture and compatible
  • Operating System
    MVS/ESA
    OS/390 2.10 or later
    z/OS 1.8 or later 
  • Host System
    CICS Transaction Server 3.2 or later