0LASubrUtilProcssDd < Main

Tags: view all tags
---+ .UTIL PROCESS DD

_This subroutine processes the Data Dictionary for the selected Application or File._

<br />%TOC%
---++ Usage:
<pre>      PASS         &lt;application&gt;              FIELD            SHARE? N
      PASS         &lt;version&gt;                  FIELD            SHARE? N
      PASS         &lt;work_fields&gt;              FIELD            SHARE? N
      PASS         &lt;file_name&gt;                FIELD            SHARE? N
      GOSUB    --- .UTIL PROCESS DD
      *        Check for errors
      IF       --- .UTIL PROCESS DD           NE


</pre>
---++ Description:

This subroutine processes the Data Dictionary for the selected Application or File. The first 2 parameters are required. If any required parameters are missing, the subroutine will CANCEL.

&lt;application&gt; is the application that contains the files to be processed (Required).

&lt;version&gt; is the version of the above application (Required).

&lt;work_fields&gt; is a Y/N flag that indicates whether or not work fields should also be processed (Optional). If not passed, defaults to Y.

&lt;file_name&gt; is the specific file in &lt;application&gt; you want processed (Optional). If not PASSed, then all files in &lt;application&gt; will be processed.

This subroutine performs the same function as 'Process Data Dictionary' in application design.

If .UTIL PROCESS DD is blank, it means the Data Dictionary compiler was successfully invoked, it does not mean that every file processed successfully. You must check the --- PDERR file to see which processes had errors, if any. The --- PDERR TEXT field will contain the error message in printable form. You can also use the --- PDERR ERR NO field to read --- MESSAGE to get the readable error message:

<pre>      SET      --- MESSAGE ID                 =  --- PDERR ERR NO
      READ     --- MESSAGE                HOLD 0 FT 0 BY MESSAGE ID

</pre>

---++ Comments:

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

<br />%COMMENT%

-- Main.JeanNeron - 2012-03-09
Topic revision: r3 - 2014-01-28 - GaryRogers