Page 1 of 1

Analysing MFS

PostPosted: Tue Mar 26, 2013 12:28 pm
by Md Shahid
Hi All,

I am trying to understand that is there any other way to establish a link between MFS fields (MOD layout) and the database, without going through the cobol codes.

I think we can certainly find some information in the message layout defined under the WS section.

BTW, I am more more interested to see if there is any technique with the help of which I can say that it is this IMS database from where the information is coming to the 3270 termainal. The ultimate goal is to minimise the dependency on the CBL programs.

Any help or suggestions will be highly appreaciated!

Re: Analysing MFS

PostPosted: Tue Mar 26, 2013 12:41 pm
by enrico-sorichetti
just think about the rules used to

define a database
define a psb
define a MID/MOD

where no naming convention of <objects> is enforced

and You will see that there is NO way to achieve what You want,
unless Your organization is willing to define a very STRICT naming convention for things

Re: Analysing MFS

PostPosted: Tue Mar 26, 2013 12:57 pm
by Md Shahid
Enrico,

Thanks for these comments.

No, the organization is NOT inclined towards rigid naming conventions. Under these circumstances, I am thinking to have some technique to help track these MFS fields back to the segments/database. Is it possible?

If yes, where shall I rely to start!

Re: Analysing MFS

PostPosted: Tue Mar 26, 2013 1:08 pm
by enrico-sorichetti
NO !

Re: Analysing MFS

PostPosted: Tue Mar 26, 2013 1:18 pm
by Md Shahid
Enrico,

Ok.

This means we have to rely on the Cobol MPP programs to determine which database/segements is holding the data for any particular Screen fields.

Re: Analysing MFS

PostPosted: Tue Mar 26, 2013 1:35 pm
by enrico-sorichetti
seems that there is language barrier here, that You keep asking the same think over and over ...

IMS is aware only of the NAMES for the fields IMS needs for its <internal> processing

e.g

EXEC DLI GU
SEGMENT(SEGMENT)
WHERE(KEY=<name of the cobol field which contains the key>)
INTO(<record area>)

as You see IMS DOES NOT know ANYTHING about the record layout and structure

so again what You ask for cannot be done!

in how many ways do You have to be told

Re: Analysing MFS

PostPosted: Tue Mar 26, 2013 1:43 pm
by Md Shahid
There is nothing like Language barrier here!

Anyway, thanks.

Re: Analysing MFS

PostPosted: Tue Mar 26, 2013 2:16 pm
by enrico-sorichetti
There is nothing like Language barrier here!

then You can chose as an alternative
Your poor knowledge of IMS basics
:twisted: