Difference: 520GenerateSubroutines (1 vs. 3)

Revision 32012-10-26 - SherriMcCormack

Line: 1 to 1
 
META TOPICPARENT name="APPX520Features"

Generate Subroutines via ILF

Changed:
<
<		This Release adds the ability to create and run a subroutine via ILF.
>
>		New utilities have been added for the ability to create a subroutine process via ILF code.
 

Overview:

Changed:
<
<		This release adds the ability to create and and run a subroutine via ILF. There are 4 new API's that you use to accomplish this:
>
>		Four new utilities (API's) have been added to provide the ability to dynamically create a subroutine within your ILF code:
 
Line: 15 to 15
 

Usage

Changed:
<
<		First call .UTIL SUBR CREATE to create an empty subroutine. Next, call .UTIL SUBR WRITE ILF for each statement you want to add to the subroutine. You must pass the necessary parameters for each statement. When you have added all the statements, call .UTIL SUBR CLOSE to close the subroutine and compile it. Your subroutine is now ready to run, assuming there weren't any compilation errors.
>
>		First call .UTIL SUBR CREATE to create an empty subroutine. Next, call .UTIL SUBR WRITE ILF for each statement you want to add to the subroutine. You must pass all the necessary parameters for each statement. When you have added all the statements, call .UTIL SUBR CLOSE to close the subroutine and compile it. Your subroutine is now ready to run, assuming there weren't any compilation errors.
 
Changed:
<
<		If you no longer need the subroutine, you can call .UTIL SUBR DELETE to delete it. If you do not delete it, it will remain in your application just like any other subroutine.
>
>		Note that the .UTIL SUBR * group of routines share certain internal fields therefore you can only use them in a process family with share class SUBPROCESS. In other words, don't call .UTIL SUBR CREATE in one process, then .UTIL SUBR WRITE ILF in another process that you have invoked Related or Detached.

If you no longer need the subroutine, you can call .UTIL SUBR DELETE to delete it. If you do not delete it, it will remain within your application just like any other subroutine.

 

Comments:

Revision 22012-06-20 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="APPX520Features"

Generate Subroutines via ILF

Line: 10 to 10
 This release adds the ability to create and and run a subroutine via ILF. There are 4 new API's that you use to accomplish this:

Changed:
<
<
  • .UTIL SUBR WRITE ILF
  • .UTIL SUBR CLOSE
  • .UTIL SUBR DELETE
>
>
 

Usage

Changed:
<
<		First call .UTIL SUBR CREATE to create an empty subroutine. Next, call .UTIL SUBR WRITE ILF for each statement you want to add to the subroutine. You must pass the necessary parameters for each statement. When you have added all the statements, call .UTIL SUBR CLOSE to close the subroutine and compile it. Your subroutine is now ready to run, assuming there weren't any compilation errors.
>
>		First call .UTIL SUBR CREATE to create an empty subroutine. Next, call .UTIL SUBR WRITE ILF for each statement you want to add to the subroutine. You must pass the necessary parameters for each statement. When you have added all the statements, call .UTIL SUBR CLOSE to close the subroutine and compile it. Your subroutine is now ready to run, assuming there weren't any compilation errors.
 
Changed:
<
<		If you no longer need the subroutine, you can call .UTIL SUBR DELETE to delete it. If you do not delete it, it will remain in your application just like any other subroutine.
>
>		If you no longer need the subroutine, you can call .UTIL SUBR DELETE to delete it. If you do not delete it, it will remain in your application just like any other subroutine.
 

Comments:

Revision 12012-06-20 - JeanNeron

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="APPX520Features"

Generate Subroutines via ILF

This Release adds the ability to create and run a subroutine via ILF.


Overview:

This release adds the ability to create and and run a subroutine via ILF. There are 4 new API's that you use to accomplish this:

Usage

First call .UTIL SUBR CREATE to create an empty subroutine. Next, call .UTIL SUBR WRITE ILF for each statement you want to add to the subroutine. You must pass the necessary parameters for each statement. When you have added all the statements, call .UTIL SUBR CLOSE to close the subroutine and compile it. Your subroutine is now ready to run, assuming there weren't any compilation errors.

If you no longer need the subroutine, you can call .UTIL SUBR DELETE to delete it. If you do not delete it, it will remain in your application just like any other subroutine.

Comments:

Read what other users have said about this page or add your own comments. 


<--/commentPlugin-->

-- JeanNeron - 2012-06-20

View topic | History: r3 < r2 < r1 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback