Joined: 31 Jan 2008 Posts: 148 Location: Chennai, India
I am having one question regarding IMS DC.
I am having tough time mapping what screen is for what program.
In my previous shop, the transaction code given on the menu screen will
be the program name.
Currently in new project, we will go to the main screen by giving
FIREMENU and from there respective screens will be browsed by just
giving the numbers.
Here even i can not able to find out what is the program for FIREMENU.
If we get user error in any particular screen it is tough to point out
which program it is related to.
If i do a search for that error code in the source library..i am seeing in more than one program.
Anything we have to search MOD name here?
Seeking your thoughts
Joined: 06 Jul 2010 Posts: 659 Location: Whitby, ON, Canada
I don't know of any magic bullet for this one. It depends on your shop naming conventions and application architecture. Some applications have a strict 1:1 correspondence between MOD names and programs, others do not. The IMS transaction code only gets you to the starting point for the transaction, which might initiate some sort of driver program that calls multiple subroutines to display the various screens. The MOD name might be generated by program logic, hard-coded, retrieved from an IMS data base or DB2 table, or from a copybook.
Typically however, once you have figured out how one or two screens are handled, the rest of the application will fall into the same pattern. No guarantees though.