Tags:
create new tag
view all tags

.UTIL SUBR WRITE ILF

This subroutine writes ILF code to a subroutine in the Application. Added in 5.2.0


Usage:

      PASS         <ilf_verb>                 FIELD            SHARE? N
      PASS         <TF_flags>                 FIELD            SHARE? N
      PASS         <opt_fields_as_needed>     FIELD            SHARE? N
      GOSUB    --- .UTIL SUBR WRITE ILF
      *        Check for errors
      IF       --- .UTIL SUBR WRITE ILF       NE

Description:

This subroutine adds an ILF line to a subroutine. The <ilf_verb> parameter is required, if it is missing or an unknown verb, the subroutine will CANCEL.

<ilf_verb> is the name of the ILF statement you want to add (Required).

<tf_flags> are the TF flags for the ILF statement you want to add. If the statement normally has TF flags then <tf_flags> are required and you can just PASS blanks (i.e. --- SPACE) where no TF flags apply. For statements that donít have TF flags, like a * (comment) or LABEL statement, <tf_flags> are not required. For example, you would add a LABEL statement as follows:

      PASS         LABEL                      FIELD            SHARE? N
      PASS         :NEWLABEL                  FIELD            SHARE? N
      GOSUB    --- .UTIL SUBR WRITE ILF

<opt_fields_as_needed> are the fields that define the parameters for the statement to be created. Just pass all the field you would normally see as editable when adding the statement in left to right order. You can omit passing all blank fields past the last field you want a value in. For example, to SET --- TEMP 30 to --- TEMP 80 on a TRUE you would pass.

      PASS         SET                        FIELD            SHARE? N
      PASS         T                          FIELD            SHARE? N
      PASS         ---                        FIELD            SHARE? N
      PASS         TEMP 30                    FIELD            SHARE? N
      PASS     --- SPACE                      FIELD            SHARE? N
      PASS         ---                        FIELD            SHARE? N
      PASS         TEMP 80                    FIELD            SHARE? N
      PASS     --- SPACE                      FIELD            SHARE? N
      GOSUB    --- .UTIL SUBR WRITE ILF

Also see .UTIL SUBR CLOSE 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.

You must run the .UTIL SUBR CREATE before calling .UTIL SUBR WRITE ILF. Also consider using .UTIL SUBR DELETE to remove the subroutine from your design when finished.

To create a LABEL simply pass the verb LABEL and the label name. T/F indicators are not required in this statement.

-- JeffPrentice - 2013-10-17

-- PeteBrower - 2012-09-28

Edit | Attach | Watch | Print version | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r5 - 2016-02-25 - JeanNeron
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback