• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Checking Inline Code
One of the major advantages of Gen is the ability to generate code for multiple target environments. Many customers have switched platforms over the life of their applications, for example from MVS/COBOL to UNIX/C or EJB/Java.

If external code is developed in external action blocks then it fairly obvious that the EAB source code needs to be modified when generating for a different target environment. But what about the inline code?

Adding inline code statements to a Gen action diagram is a useful alternative to coding external action blocks, but care has to be taken when switching environments or developing multi-platform code.

When inline code is developed, you specify on the statement what language the inline code should be generated for and optiionally further restrict the statement to specified OS, DBMS and even TP Monitor. 

However if the action block code is then generated for a different target environment, the inline code statements that do not match the specified environment are ignored. This means that the inline code is not executed, and unless there is some check further on in the action block, you might not ever be aware that the code is not executed.

To help with this potential issue, a new VerifIEr check (IET169) has been developed which will report on action blocks that contain inline code that does not match a specified environment
Darius Panahy, IET Ltd

Messages In This Thread
Checking Inline Code - by Darius Panahy - 2022-07-11, 11:25 AM

Forum Jump:

Users browsing this thread: 1 Guest(s)

   Visit the IET Web Site for product information and contact details and privacy policy. Visit the IET Support Centre for product support and downloads.