Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
.UTIL SUBR WRITE ILF | ||||||||
Changed: | ||||||||
< < | This subroutine adds a statement to the subroutine you just created. | |||||||
> > | This utility adds a statement to the subroutine you just created. | |||||||
Usage: | ||||||||
Line: 15 to 15 | ||||||||
Description: | ||||||||
Changed: | ||||||||
< < | This subroutine adds a statement to the subroutine you just created. You must have created the subroutine with .UTIL SUBR CREATE first. | |||||||
> > | This utility adds a ILF statement to the subroutine you just created. You must have created the subroutine with .UTIL SUBR CREATE first. | |||||||
Changed: | ||||||||
< < | <ILF_Verb> is the command you want to add, in uppercase. If the verb is not recognized, the subroutine will cancel. | |||||||
> > | <ILF_Verb> is the ILF command you want to add, in uppercase (Required). If the verb is not recognized, the subroutine will cancel. | |||||||
Changed: | ||||||||
< < | <TF Flags> are the TF flags you want set on this command. If the <ILF_Verb> is * or ** (comments), there are no TF flags. | |||||||
> > | <TF Flags> are the True/False flags you want set on this ILF command. If the <ILF_Verb> is * or ** (comments), there are no TF flags. | |||||||
Changed: | ||||||||
< < | <Addn fields as req'd> is the rest of the ILF command, field by field. | |||||||
> > | <Addn fields as req'd> is the rest of the ILF command, field by field as necessary. | |||||||
Changed: | ||||||||
< < | For example, a comment would require 2 PASS statements, one to PASS the *, and a second to PASS the comment itself. | |||||||
> > | For example, a comment would require 2 PASS statements: one to PASS the *, and a second to PASS the comment itself. | |||||||
A SET statement would require 8 PASS statements: | ||||||||
Line: 35 to 35 | ||||||||
| ||||||||
Changed: | ||||||||
< < | There is minimal editting done on the data you pass, any errors will be discovered when you close the subroutine and compile it. | |||||||
> > | There is minimal editting done on the data you pass to this utility, any errors will be discovered when you close/compile the subroutine. | |||||||
Changed: | ||||||||
< < | When you are finished adding statements, close the routine via .UTIL SUBR CLOSE | |||||||
> > | When you are finished adding the ILF statements, close the subroutine via .UTIL SUBR CLOSE | |||||||
Also see .UTIL SUBR DELETE. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
.UTIL SUBR WRITE ILFThis subroutine adds a statement to the subroutine you just created.Usage:PASS <ILF_Verb> FIELD SHARE? N PASS <TF Flags> FIELD SHARE? N PASS <Addn fields as req'd> FIELD SHARE? N GOSUB --- .UTIL SUBR WRITE ILF * Check for errors IF --- .UTIL SUBR WRITE ILF NE Description:This subroutine adds a statement to the subroutine you just created. You must have created the subroutine with .UTIL SUBR CREATE first. <ILF_Verb> is the command you want to add, in uppercase. If the verb is not recognized, the subroutine will cancel. <TF Flags> are the TF flags you want set on this command. If the <ILF_Verb> is * or ** (comments), there are no TF flags. <Addn fields as req'd> is the rest of the ILF command, field by field. For example, a comment would require 2 PASS statements, one to PASS the *, and a second to PASS the comment itself. A SET statement would require 8 PASS statements:
Comments:Read what other users have said about this page or add your own comments.-- JeanNeron - 2012-06-20 |