Difference: 0LASubrFileCopy (1 vs. 4)

Revision 42013-05-01 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="APPXRuntimeSubroutineAPI"

.FILE COPY

Line: 25 to 25
  <dest_file> is the location where the file should be copied to (Required). This must include the destination file name, ie, you cannot just specifiy a target directory.
Changed:
<
<
If --- .FILE COPY contains 'File Copy Failed', you can check the <error_message> field for more information on why the copy failed.
>
>
If --- .FILE COPY contains 'File Copy Failed', you can check the <error_message> field for more information on why the copy failed. This routine will not overwrite an existing file, if you want to replace an existing file you can use .FILE DELETE to delete the destination first.
  This command is run by the appx engine, not by 'shelling out' to the O/S level, therefore the destination file will have the permissions of the engine. On Linux/Unix systems, if the 'setuid' bit is set, then those will be the permissions of user 'appx'. If you do not have the 'setuid' bit set, then the those will be the permissions of whatever user you have the engine configured to impersonate. On Windows the permissions will be that of the current user.

Comments:

Revision 32012-01-25 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="APPXRuntimeSubroutineAPI"

.FILE COPY

Line: 19 to 19
  This subroutine will copy a file from one location to another, creating any required directories. All parameters are required, if any are missing the subroutine will CANCEL.
Changed:
<
<
<error_message> contains additional error information if the copy fails (Required). Must be PASSed with Share "Y".
>
>
<error_message> contains additional error information if the command fails (Required). Must be PASSed with Share "Y".
  <source_file> is the source file to be copied (Required).

Revision 22012-01-25 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="APPXRuntimeSubroutineAPI"

.FILE COPY

Line: 19 to 19
  This subroutine will copy a file from one location to another, creating any required directories. All parameters are required, if any are missing the subroutine will CANCEL.
Changed:
<
<
<error_message> identifies the field that will contain additional error information if the copy fails (Required).
>
>
<error_message> contains additional error information if the copy fails (Required). Must be PASSed with Share "Y".
 
Changed:
<
<
<source_file> identifies the file to be copied (Required).
>
>
<source_file> is the source file to be copied (Required).
 
Changed:
<
<
<dest_file> identifies the location where the file should be copied to (Required). This must include the destination file name, ie, you cannot just specifiy a target directory.
>
>
<dest_file> is the location where the file should be copied to (Required). This must include the destination file name, ie, you cannot just specifiy a target directory.
  If --- .FILE COPY contains 'File Copy Failed', you can check the <error_message> field for more information on why the copy failed.

Revision 12012-01-24 - JeanNeron

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="APPXRuntimeSubroutineAPI"

.FILE COPY

This subroutine will copy a file from one location to another, creating any required directories.


Usage:

      PASS         <error_message>            FIELD            SHARE? Y
      PASS         <source_file>              FIELD            SHARE? N
      PASS         <dest_file>                FIELD            SHARE? N
      GOSUB    --- .FILE COPY
      *        check for errors
      IF       --- .FILE COPY                 NE

Description:

This subroutine will copy a file from one location to another, creating any required directories. All parameters are required, if any are missing the subroutine will CANCEL.

<error_message> identifies the field that will contain additional error information if the copy fails (Required).

<source_file> identifies the file to be copied (Required).

<dest_file> identifies the location where the file should be copied to (Required). This must include the destination file name, ie, you cannot just specifiy a target directory.

If --- .FILE COPY contains 'File Copy Failed', you can check the <error_message> field for more information on why the copy failed.

This command is run by the appx engine, not by 'shelling out' to the O/S level, therefore the destination file will have the permissions of the engine. On Linux/Unix systems, if the 'setuid' bit is set, then those will be the permissions of user 'appx'. If you do not have the 'setuid' bit set, then the those will be the permissions of whatever user you have the engine configured to impersonate. On Windows the permissions will be that of the current user.

Comments:

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


<--/commentPlugin-->

-- JeanNeron - 2012-01-24

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback