Difference: 0LASubrUtilSubrClose (1 vs. 2)

Revision 22012-10-26 - SherriMcCormack

Line: 1 to 1
 
META TOPICPARENT name="520GenerateSubroutines"

.UTIL SUBR CLOSE

Changed:
<
<
This subroutine closes the subroutine you created.
>
>
This utility closes the subroutine you created.
 

Usage:

Line: 12 to 12
 

Description:

Changed:
<
<
This subroutine closes the subroutine you created. No parameters are required.
>
>
This utility closes and compiles the subroutine you created. No parameters are required.
 
Changed:
<
<
The subroutine will be compiled using .UTIL COMPILE PROC. To check for compile errors in your subroutine, read the --- PCERR file. If there are any records present, then there was a compile error and you can examine the records to see the specific errors or just look at the subroutine in Application Design.
>
>
The subroutine will be compiled using .UTIL COMPILE PROC. Be sure to check for errors as described in the Usage area above, which includes a compile error. If there are compile errors within your subroutine, read the --- PCERR file and examine the records to see the specific errors or just look at your subroutine in Application Design.
  Also see .UTIL SUBR CREATE and .UTIL SUBR DELETE.

Revision 12012-06-20 - JeanNeron

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="520GenerateSubroutines"

.UTIL SUBR CLOSE

This subroutine closes the subroutine you created.


Usage:

      GOSUB    --- .UTIL SUBR CLOSE
      *        Check for errors
      IF       --- .UTIL SUBR CLOSE           NE

Description:

This subroutine closes the subroutine you created. No parameters are required.

The subroutine will be compiled using .UTIL COMPILE PROC. To check for compile errors in your subroutine, read the --- PCERR file. If there are any records present, then there was a compile error and you can examine the records to see the specific errors or just look at the subroutine in Application Design.

Also see .UTIL SUBR CREATE and .UTIL SUBR DELETE.

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.

Comments:

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


<--/commentPlugin-->

-- JeanNeron - 2012-06-20

 
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