Abstract: Certain example embodiments relate to techniques for use with mainframe computing systems that include both general-purpose processors (e.g., CPs) and special-purpose processors that can be used to perform only certain limited operations (e.g., zIIPs). Certain example embodiments automatically help these special-purpose processors perform user exits and other routines thereon, rather than requiring those operations to be performed on general-purpose processors. This approach advantageously can improve system performance when executing programs including these user exits and other routines, and in a preferred embodiment, it can be accomplished in connection with a suitably-configured user exit daemon. In a preferred embodiment, the daemon and its clients can use a user exit property table or the like to communicate with one another about the state of each user exit or other routine that has been analyzed, classified, and possibly modified.

Abstract: Certain example embodiments relate to techniques for use with mainframe computing systems that include both general-purpose processors (e.g., CPs) and special-purpose processors that can be used to perform only certain limited operations (e.g., zIIPs). Certain example embodiments automatically help these special-purpose processors perform user exits and other routines thereon, rather than requiring those operations to be performed on general-purpose processors. This approach advantageously can improve system performance when executing programs including these user exits and other routines, and in a preferred embodiment, it can be accomplished in connection with a suitably-configured user exit daemon. In a preferred embodiment, the daemon and its clients can use a user exit property table or the like to communicate with one another about the state of each user exit or other routine that has been analyzed, classified, and possibly modified.

Abstract: Certain example embodiments modify portions of a program, represented by object code stored in an executable, to be executed in a computing environment including general-purpose and special-purpose processors. Culprit calls in the object code deemed ineligible for execution by the special-purpose processor are identified. For each identified call: inserted into an allocated area are instructions that cause the program to temporarily cease executing calls using the special-purpose processor and instead execute an equivalent to the respective culprit call using the general-purpose processor, and return to executing calls using the special-purpose processor following execution of the respective culprit call using the general-purpose processor; and the respective identified culprit call is replaced with a branch instruction for the allocated area to cause the program to execute the inserted instructions rather than the replaced respective culprit call.

Abstract: Certain example embodiments modify portions of a program, represented by object code stored in an executable, to be executed in a computing environment including general-purpose and special-purpose processors. Culprit calls in the object code deemed ineligible for execution by the special-purpose processor are identified. For each identified call: inserted into an allocated area are instructions that cause the program to temporarily cease executing calls using the special-purpose processor and instead execute an equivalent to the respective culprit call using the general-purpose processor, and return to executing calls using the special-purpose processor following execution of the respective culprit call using the general-purpose processor; and the respective identified culprit call is replaced with a branch instruction for the allocated area to cause the program to execute the inserted instructions rather than the replaced respective culprit call.

Abstract: Certain example embodiments transform a third-generation language (3GL) and/or an Assembler program so that it can be executed within a fourth-generation language (4GL) runtime environment. Certain example embodiments include a method for transforming a 3GL and/or an Assembler program that is callable by a 4GL program so that the 3GL and/or Assembler program is executable upon call by the 4GL program and from within a 4GL runtime environment. For instance a 4GL identifier may be included in the executable of the 3GL and/or the Assembler program to facilitate execution of the 3GL and/or the Assembler program upon call of the fourth-generation language (4GL) program and within the 4GL runtime environment.

Abstract: The present invention relates the transformation of a 3GL and/or an Assembler program (230) so that it can be executed within a 4GL runtime environment (250). Certain example embodiments include a 4GL identifier (240, 310) in the executable of the 3GL and/or the Assembler program (230).