M3 ERP , Lawson Infor : Help - Guide : functional and technical approach with SCAN400 WELCOME in « SCAN400 » Cross References Practical observation Tool for AS400/iSeries applications - Specialized M3/ Movex CLICK HERE to RETURN to the original PICTURE-Page CONTAINING this TEXT SLIDE SHOW : How to consult the Cross references of Inter- Programs processes in M3 application : M3SEE To start, run the command : ADDLIBLE SCAN400 M3SEE The element to observe on its context is typed on the main selector. The selector can contain : The Selector can contain : A java program existing in M3 App A java class A java method of class A PHYSICAL File (The programs displayed are relating to the physical file and all its associated logical files) A LOGICAL File (The programs displayed are only relating to the logical file according to the index number typed in the sub selector) An ID message used in M3 The SUB – SELECTOR is optional , It can specify : The TYPE of the element entered in the main selector The kind of request If two elements with different type have the same NAME, the sub selector helps you to resolve any ambiguity about the identity of these elements. Most of time, you will not provide any information in this sub selector, because M3SEE identifies itself the type of the element entered in the main selector. The sub selector car contain the following values : FILE, PGM, MSG, NEW, METH , HER or a logical File index number FILE : The element entered in the main selector is a File ( PF or LF) PGM : The element entered is a Programme, or a java Class MSG : The element entered is an ID Message (specific to M3) NEW : The element is an instantiation of Class (java operator ‘New’) METH : The element in the main selector is a Method of java Class HER : To visualize all programs or Class having a link by inheritance with the super-element entered in the main selector Index : Example : if the main selector contains MITMAS, enter « 10 » in the sub selector if you want to observe all programs concerning MITMAS10 (LF) In the case of a Physical file, The observation always concerns this physical file but also ALL Its associated indexes (PF and LF) first, are shown Programs which update, delete, or write, in the physical file or one of its logical file Then, are shown Programs which read only, the physical file or one of its logical file you can also decide to make appear immediatly the identity card of the program typed in the main selector, namely : - The wording of the program (line 1) - Informations about the creation of this program (ligne 2) - Informations about the source code of this program (ligne 3) This setting is defined with the button "F5 = see" and remains active at each use of JDSEE as long as the user will not modify it again (see next page). The letter « M » indicates that the element called by CRS395 si a Java METHOD of CLASS, and not an program directly called with ApCall ou JobCall syntax. In this sample, CRS395 instantiate the java class CPLCHKAI (with operator java ‘new’), and then, Call one of its methods (with a syntax like « CPLCHKAI.Method) » . Three samples of use with the sub-Selector : NEW : to search and display all programs using an instantiation of the class « CPXMNS920 » HER : to search and display all sub classes inheriting from the super class « MVX.APP.PGM.MMS001 » Index 10 : to search and display all programs using the logical file named « MITMAS10 » Indication of location In this Sample, MMS001 is in the directory CUSTOMER, (MVX/APP/PGM/CUSTOMER) It is therefore a specific Program Kinds of Update, That MMS001 uses on the Database files : D = Delet U = Updat O = Write (Output) F5 = Runs the Visualization of the Program Source code entered in the selector The Java source code is got back by copy from M3 into a SEU source isolated in QTEMP (the original source MAK located in IFS is of course protected/ not modified) Important : If the source is a sub Class, all the sources of the SUPER-CLASS are also got back by addition in a same global source code. The central Subfile informs us about the program contained in the main selector : First about its "DataBase content" : DB Files on update DB files on read only Then, informs us about other elements used in this program : Inhéritance (Super Class) Instantiations of classes (with operator « New ») ID Messages used (Example : XIT003, XBA0003..) Internal Methods In the case of a Physical file, The observation always concerns this physical file but also ALL Its associated indexes, (PF and LF) first, are shown Programs which update, delete, or write, in the physical file or one of its logical file Then, are shown Programs which read only, the physical file or one of its logical file