Types of programs you can debug with Assembler
With Code Debug IMS, you can debug three types of programs:
- Message Processing Programs (MPPs)
- Batch Message Processing (BMP) Programs
- Message-driven Interactive Fast Path (IFP) Programs
These three types of programs can access various resources under Code Debug IMS. Available to them are full function databases, Db2, GSAM (BMP only), and Fast Path databases.
Message processing programs
The primary purpose of MPPs is to quickly process your requests from the terminal or from another application program. Ideally, the requests are small and processing is set up to respond to them quickly. MPPs process messages as their input and send messages as responses.
An MPP can access full function databases, Fast Path databases, and Db2 databases. An MPP cannot access GSAM databases.
In Code Debug IMS, multiple MPP transactions can be debugged in the same session.
Batch message processing programs
You might use a BMP program when processing time is long, but an immediate response is not required. There are two types of BMP programs—message-driven and non-message-driven. A message-driven BMP program is used to process information received from a terminal or other program, but held by IMS in a message queue.
A non-message-driven program is often used when no access to messages is required. It is also typically a long-running program, used when you have a large number of updates to do or when running a report.
Both types of BMP programs can access OS/VS files, GSAM databases, full function databases, Fast Path databases, and Db2 databases.
In Code Debug IMS, a BMP program is executed in its own region, and when the program is terminated, the region is also terminated.
Fast Path programs
An IFP program functions the same way an MPP does, but it is scheduled by IMS in a manner similar to a BMP program. An IFP program increases the performance of certain types of database applications. It provides efficient access to large volumes of data that are broken up into areas that can be accessed independently of each other.
In Code Debug IMS, an IFP program is executed in a Fast Path region, and when the program is terminated, so is the region.