Difference: 0LASubrFileExtractArchive (1 vs. 4)

Revision 42017-12-05 - JeanNeron

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

.FILE EXTRACT ARCHIVE

Line: 6 to 6
 

Usage:

Changed:
<
<
      PASS         <error_message>            FIELD            SHARE? N

>
>
      PASS         <error_message>            FIELD            SHARE? Y

  PASS <archive_file> FIELD SHARE? N PASS <dest_directory> FIELD SHARE? N GOSUB --- .FILE EXTRACT ARCHIVE
Line: 28 to 27
  If --- .FILE EXTRACT ARCHIVE contains 'Archive extract failed', you can check the <error_message> field for more information on why the extract failed.
Changed:
<
<
This command is run by the appx engine, not by 'shelling out' to the O/S level, therefore the extracted files 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. The extracted files will be owned by the current user, who must have sufficient permission in the destination directory to take ownership of the files.
>
>
This command is run by the appx engine, not by 'shelling out' to the O/S level, therefore the extracted files 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. The extracted files will be owned by the current user, who must have sufficient permission in the destination directory to take ownership of the files.
 

Comments:

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

Revision 32013-05-02 - JeanNeron

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

.FILE EXTRACT ARCHIVE

Line: 28 to 28
  If --- .FILE EXTRACT ARCHIVE contains 'Archive extract failed', you can check the <error_message> field for more information on why the extract failed.
Changed:
<
<
This command is run by the appx engine, not by 'shelling out' to the O/S level, therefore the extracted files 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.
>
>
This command is run by the appx engine, not by 'shelling out' to the O/S level, therefore the extracted files 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. The extracted files will be owned by the current user, who must have sufficient permission in the destination directory to take ownership of the files.
 

Comments:

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

Revision 22013-05-02 - JeanNeron

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

.FILE EXTRACT ARCHIVE

Line: 26 to 26
  <dest_directory> is the target directory where the files should be extracted (Required). Any required directories will be created.
Changed:
<
<
If --- .FILE EXTRACT ARCHIVE contains 'Archive create failed', you can check the <error_message> field for more information on why the extract failed.
>
>
If --- .FILE EXTRACT ARCHIVE contains 'Archive extract failed', you can check the <error_message> field for more information on why the extract failed.
  This command is run by the appx engine, not by 'shelling out' to the O/S level, therefore the extracted files 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 12012-01-25 - JeanNeron

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

.FILE EXTRACT ARCHIVE

This subroutine extracts all the files from a previously created archive.

Usage:

      PASS         <error_message>            FIELD            SHARE? N
      PASS         <archive_file>             FIELD            SHARE? N
      PASS         <dest_directory>           FIELD            SHARE? N
      GOSUB    --- .FILE EXTRACT ARCHIVE
      *        check for errors
      IF       --- .FILE EXTRACT ARCHIVE      NE

Description:

This subroutine extracts all the files from a previously created archive (see .FILE CREATE ARCHIVE). All parameters are required, if any are missing the subroutine will CANCEL.

<error_message> contains additional error information if the command fails (Required). Must be PASSed with Share "Y".

<archive_file> is the archive to be extracted (Required). This should include the full path to the file.

<dest_directory> is the target directory where the files should be extracted (Required). Any required directories will be created.

If --- .FILE EXTRACT ARCHIVE contains 'Archive create failed', you can check the <error_message> field for more information on why the extract failed.

This command is run by the appx engine, not by 'shelling out' to the O/S level, therefore the extracted files 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-25

 
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