.UTIL COMPILE PROC

This subroutine compiles the specified Process Type/Name or Application.

Usage:

      PASS         <application>              FIELD            SHARE? N
      PASS         <version>                  FIELD            SHARE? N
      PASS         <proc_type>                FIELD            SHARE? N
      PASS         <proc_name>                FIELD            SHARE? N
      GOSUB    --- .UTIL COMPILE PROC
      *        Check for errors
      IF       --- .UTIL COMPILE PROC         NE

Description:

This subroutine compiles the specified Process Type/Name or Application. The first 2 parameters are required. If any required parameters are missing, the subroutine will CANCEL.

<application> is the application that contains the processes to be compiled (Required).

<version> is the version of the above application (Required).

<proc_type> is the process type to be compiled (Optional). If PASSed, this must be a valid Process Type, INPUT, OUTPUT, JOB, SUBROUTINE, etc. If not PASSed, then all processes in <application> will be compiled.

<proc_name> is the process name to be compiled (Optional). You can only PASS this if you also PASS the <proc_type>. If not PASSed, then all processes of type <proc_type> will be compiled.

This subroutine performs the same function as 'Create Executable Modules' in application design. Only Em's that need to be rebuilt will be compiled. A message will appear in the status area when Appx is actually compiling an Em.

If .UTIL COMPILE PROC is blank, it means the compiler was successfully invoked, it does not mean that every process compiled successfully. You must check the --- PCERR file to see which processes had errors, if any. The --- PCERR ERR NO field can be used to read --- MESSAGE to get a readable error message:

      SET      --- MESSAGE ID                 =  --- PCERR ERR NO
      READ     --- MESSAGE                HOLD 0 FT 0 BY MESSAGE ID

The --- PCERR STMT field will contain the problem statement, in printable form.

Comments:

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

-- JeanNeron - 2012-03-08