Working With VSE Libraries

Introduction:

Now that we have navigated to the right sublibrary, we can issue GET/MGET and PUT/MPUT commands as we wish.

Download Snapshots:

The following two examples illustrate downloading concepts. The first example shows how to download a single member, while the second one shows how to download multiple members.

Example 1: Download a single member:

    To download a single member, or data file, we issue GET command:

Example 2: Download multiple members:

   To download multiple members, issue the MGET command as follows: MGET member_pattern
   where member_pattern is a generic specification (filter) for members we want to down load.

   For example, to download all members whose names start with XPC, issue MGET XPC*

ftp>
ftp> mget XPC*
200 Command okay.
200 Command okay.
150 File status okay, about to open data connection.
226-Records sent : 000000346
Bytes dropped: n/a
226 Closing data connection.
ftp: 28372 bytes received in 0.88Seconds 32.24Kbytes/sec.
200 Command okay.
150 File status okay, about to open data connection.
226-Records sent : 000000145
Bytes dropped: n/a
226 Closing data connection.
ftp: 11890 bytes received in 0.33Seconds 36.03Kbytes/sec.
ftp>

NOTES:

Forced Binary Mode:

    Members whose types are listed in FTP_LIBR_MEM_TYPE global statements are always up/down-loaded in
    BINARY MODE even if the current mode is otherwise. There is no way for the client to change this fact.
    This is just about the only case where the Admin can force you, the user, to do the right thing!

Upload Snapshots:

The following two examples illustrate uploading concepts. The first example shows how to upload a single
file, while the second one shows how to upload multiple files..

Example 1: Uplaod a single file:

    To upload a single file, issue the PUT command.

Example 2: Upload multiple members:

   To upload multiple members, issue the MPUT command as follows: MPUT member_pattern
   where member_pattern is a generic specification (filter) for members we want to upload.

   For example, to upload all members whose names start with XPC, issue MPUT XPC*

ftp>
ftp> get APPC.A APPC.TXT
200 Command okay.
150 File status okay, about to open data connection.
226-Records sent : 000000541
Bytes dropped: n/a
226 Closing data connection.
ftp: 45372 bytes received in 0.88Seconds 32.24Kbytes/sec.
ftp>

ftp>
ftp> put xpcc.mac xpcc.a
200 Command okay.
150 File status okay, about to open data connection.
226-Records rcvd : 000000269
Bytes dropped: 000000001
226 Closing data connection.
ftp: 9683 bytes sent in 0.00Seconds 9683000.00Kbytes/sec.
ftp>

ftp>
ftp>
ftp> mput xpc*.*
mput xpcc.mac? y              <<<== First file going up....
200 Command okay.
150 File status okay, about to open data connection.
226-Records rcvd : 000000269
      Bytes dropped: 000000001
226 Closing data connection.
ftp: 9683 bytes sent in 0.00Seconds 9683000.00Kbytes/sec.
mput xpccb.mac? y                <<=== Second file going up....
200 Command okay.
150 File status okay, about to open data connection.
226-Records rcvd : 000000097
      Bytes dropped: 000000001
226 Closing data connection.
ftp: 4484 bytes sent in 0.00Seconds 4484000.00Kbytes/sec.
ftp>