Difference: 0LASubrFileCopy (3 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:

View topic | History: r4 < r3 < r2 < r1 | More topic actions...