Implemented Objects Overview




Kudos to Plex_Upgrade_Wizard which this unashamedly borrows/steals/copies but adds AS400 query.

This tool enables you to query what DLLs are in a windows directory or Objects in an AS400 Library, once this is known a comparison is made with what currently exists in your current local model. With the view of highlighting the following:

  • DLL/AS400 Object names not found in your CA Plex models
  • DLL/AS400 Object names that Exist in your CA Plex models but have No Usage 
  • DLL/AS400 Object names that Exist in your CA Plex models and are used by a function but the function is Not Generatable under the current config. 

Finally a Plex list can be created which represents all the DLL/AS400 Object in the query directory/library found in your local model.

Please view current rules for what objects are considered "Object Generatable?"


Add-In Setting

Instructions

Launch application from Plex Add-In tool bar.

If you are unable to see the Add-In toolbar from View, Toolbars… menu option choose Show toolbar.

Choose Variant Winc or AS400


In order for the tool to get a list of objects from the AS400 it calls OBAS400\Get objects.List attributes.Get sequential. So you must have pgm OYeF built and in your library list. Secondly StellaImpObjs.INI must have the appropriate Remote settings added.       

WinC Mode

  • FullPath Promptable Edit box for the directory containing the DLL you want to interrogate.

RPG Mode

  • Object type Combo is defaulted to *PGM. 
  • Library Name Combo allows you to enter or select the library location of the pgms. See Qualified Object Name 
  • Object Name Combo can be a simple name, a qualified generic object name, or a qualified object name with the special value *ALL. See Qualified Object Name 

For more information on these 3 fields please see OBAS400\Get objects.List attributes.Get sequential

Press OK button or Enter button to start the search

Understanding the Results


1 - PGM/DLL name from the source library/directory could not be found in the current local model as a Name object. 
  • Maybe the object name exists in another Library or Application model not attached to the current local model 
  • Maybe the object name did exist in the Plex model(s) but has been deleted over time and this PGM/DLL should be investigated for deletion 
  • Maybe the object name correctly does not exist in the Plex model(s) as the PGM/DLL is a third party object or runtime object etc 
  • Maybe the object name did exist in a local model that failed in a group model update and the Plex function was simply regen and built under the another name 
2 - PGM/DLL name was found in the local model and is being used as a file name for a function object But the function is not generatable under the current local model configuration. 
  • Functions that have been deprecated in the Plex models using Implement No triples but have not been deleted from the application library/directory 
  • Maybe a change of inheritance has made the Plex object unintentionally not generatable under the current local model configuration and should be investigated 
  • A function that was initially an External function but since created as Internal function 
3- PGM/DLL name was found in the local model but is not being used as a file name for a function object. 
  • Maybe the object name is used by a function as a file name in another Library or Application model not attached to the current local model 
  • During development a function was gen and built but latter on given a new name but not by renaming the existing Name object but deleting the triple 
4 - PGM/DLL name was found in the local mode and is being used by a generatable function under the current local model configuration. 

5 - You can multi select the Type 4 grid rows to create a Plex list. You will be prompted with an enquiry message detailing the List name to be created. Only Type 4 rows (PGM/DLL name was found in the local model and is being used by a generatable function under the current local model configuration.) can be added to a List. 

Considering Multiple Objects Found or Usage. 


  • When PGM/DLL name was found in the local model multiple times as the same object name defined in multiple models then the owning library name is post fixed enclosed in square brackets and Multiple Objects Found column check box is checked to allow easier sorting.  
  • It is possible for the 'same object name' to be used as a 'file name to a function' multiple times if an object name is created in a library then used in a host model, followed by the owning library then using the object name but this is an uncommon event but was had been causing a bug, so 'Multiple Usage of Object' column is present to cater for this infrequent occurrence