IBM MAINFRAME HELP & SUPPORT FORUMS

JagBrew · Joined: 29 Oct 2003 Posts: 2

I have been tasked with the great thing of taking a directory of MFS files and matching them to another directory of Cobol Programs. Is there a way to determine this just from these files, or is there something like a PCT table in IMS that I must get the cross reference from, and how if this is the case?

JagBrew · Joined: 29 Oct 2003 Posts: 2

JagBrew wrote: I have been tasked with the great thing of taking a directory of MFS files and matching them to another directory of Cobol Programs. Is there a way to determine this just from these files, or is there something like a PCT table in IMS that I must get the cross reference from, and how if this is the case?

maverick · Joined: 13 Nov 2003 Posts: 2

From the MFS you will be able to get the transaction ids .Look for TRANCODE under the MID & MOD sections. Transaction ids are generally created by adding I & O after the program name . So if the transaction id is XXXXI your program name should be XXXX .

If you know a program name and want to know what transaction it uses , look for the SPA section in the program . Alternatively you can use the following operator command '/display program pgm-name' to see what transaction is linked to the program in question.

muthuraamn · Joined: 26 Nov 2003 Posts: 7 Location: chennai

Hi!

Its a very good Question.

The transaction ID, PSB, MFS ID, SPA area and the databases used are defined by the System programmers in the backround ( Control region ). We need to provide these informations to the system programmers.

Regards,
Muthu

Sandy Zimmer · Joined: 13 Jun 2007 Posts: 443 Location: Wilmington, DE

I was not aware that anyone used SPA area anymore? True transaction processing is much faster. The SPA area was used in ancient systems that were basically converted from CICS. Who still uses the SPA area.

Anyway, someone else said look at the MID and the MOD. I once wrote a system where I was allocated 3 transactions for the entire system which consisted of approx 30 DC programs. The main transaction (for example) was HR100 - which linked to the main program HR100 and the MFS HR100. Within that program, I determined where the user wanted to go based on the menu selections in HR100. I then named the programs and HR100A, HR100B, etc. When the program HR100 determined which procedure was selected, it called the corresponding program - statically - dynamic calls were a big NO-NO in the IMS system.