.FILE CREATE

This subroutine will create the specified file.

Usage:

      PASS         <error_msg>                FIELD            SHARE? Y
      PASS         <file_name>                FIELD            SHARE? N
      PASS         <application>              FIELD            SHARE? N
      PASS         <database>                 FIELD            SHARE? N
      PASS         <fms_type>                 FIELD            SHARE? N
      PASS         <fms_group>                FIELD            SHARE? N
      GOSUB    --- .FILE CREATE
      *        Check for errors
      IF       --- .FILE CREATE               NE

Description:

This subroutine will create the specified file. This is different from using the CREATE command, which only works if the file has previously been created using Data File Management. This routine performs the same function as 'Create' in Data File Management, so you may use it for newly defined databases and newly defined files.

It has the same restrictions as Data File Management, ie, the user running the command must be either a System Administrator, or have Database Management rights for the Database/Application. The file to be created must be a Disk Permanent file, the 'Create By Database Mgmt?' flag in the Data Dictionary must be "Y", and the 'Use DB' field must be blank.

For Files that where 'Create By Database Mgmt?' is set to "N", you can still call this routine. It will not create the files, but it will add the necessary SYSDIR records so that a CREATE statement will create the file.

<error_message> contains additional error information if the command fails (Required). Must be PASSed with Share "Y". Note that this message can be up to 500 characters in length.

<file_name> is the file to be created (Required). This must be a file defined in your Data Dictionary.

<application> is the application that contains the Data Dictionary for <file_name> (Optional). If not specified, it will default to the current application.

<database> is the database in which the file should be created (Optional). If not specified, it will default to the current Database.

<fms_type> and <fms_group> are the FMS group to use when creating the file (Optional). If not specified, it will default to an Appx I/O file in the default location. If PASSed, you must PASS both of these. This will only be effective the first time the file is created. If you SCRATCH the file & use this routine to create it, it will not change the existing FMS controls on the file.

If --- .FILE CREATE contains 'Unable to Create File', you can check the <error_message> field for more information on why the create failed.

Comments:

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

-- JeanNeron - 2012-03-01