Features

Dynamic Stub Attachment.

Unlike Command level or Mixed mode programs, Macro level programs did not need a CICS stub to be linkedited with the programs. In order for MLI to handle a macro level program, a stub must be present.

You can have MLI attach a stub automatically (recommended for simplicity) at program load time by turning on the dynamic loader function.

Storage Reserved Option

This can affect transaction performance positively. When the option is used, MLI will keep freemained storage on an internal free storage chain for the life of the transaction and up to the maximum limit set in the MLI control parameters.

For any subsequent getmain calls by the transaction, MLI will verify on its free storage chain, if the requested storage is available. If the storage is available, MLI will honor the request from its pool without issuing the getmain request to CICS. If storage is not available on the MLI chain then the getmain request will be passed to CICS.

This allows for better performance for MLI handled transactions specifically when the task is issuing a lot getmains and freemains requests.

ISAM Compatibility

ISAM compatibility was provided under CICS version 2 by setting the 'RECFORM' parameter to 'UNBLOCKED' on the FCT entry. This is no longer available in RDO for CICS/ESA. You can still code a FCT for CICS version 3 but you have to migrate to RDO for CICS version 4.

Macro level programs accessing UNBLOCKED defined files are returned with a FIOA instead of a FWA for certain types of file operations. Your macro level program is already coded with this expectation.

If you have such defined files in your CICS 2.1.2 FCT, and these files are used by your macro level application, you will need to code the DDNAMEs of these files in the ISAM compatibility menu when running MLI under a CICS/ESA region. (If you are running CICS version 3 and are using the FCT definition, you do net need this feature.)

Direct Link

This option is used to gain important performance improvements for macro level or command level applications. Applications calling frequently used programs by LINK or XCTL will see their CPU consumption reduce from 10-60% if this option is used.

The Direct Link menu supports assembler written programs only.

Programs defined under the DIRECT-LINK menu will be Branch and Linked (BALR) to instead of the traditional CICS link processing, therefore bypassing all the overhead of issuing a CICS LINK or XCTL. MLI maintains all the necessary program levels for the task. If your application issues the EXEC CICS ASSIGN PROGRAM command call, MLI will return the correct program name.

M31 - 31 bits Programs

MLI offers the capability to run programs, written in any languages using either macro level or command level, above the 16 megabyte line. For any programs using 31 bits support, MLI will tell CICS the program is RMODE ANY. When the program is given control, it will have its AMODE set to 31 by MLI.

VS/COBOL programs compiled with or without the RESIDENT option are also supported above the line. The samples supplied with MLI are VS/COBOL and can be entered in 31 bits support for testing the option.

BMS mapsets can be moved above the line without any problems.

Assembler programs that are not 31 bits compatible cannot be moved above the line (asis) if they use the hi-order byte of the address to store data or a flag. Some modifications might be required to the source.

When you are going to run assembler macro level programs under MLI, you can turn ON the "Remove FCI from TCAFCAAA" option in the MLI control parameters. This will help you to pass assembler macro level program above the 16 meg. line by removing the FCI byte in the hi-order byte of the TCAFCAAA.

This is a separately priced option in MLI. It is controlled by the product code mechanism. If you are not licensed for this option, you not will able to register program names for 31 Bits support.