Working With VSE POWER

Introduction:

Now that we have navigated, or pointed, to where POWER entries reside, let's do file downloads and uploads.

If you are using a GUI client, then all you have to do is click your way around. If, on the other hand, you are using a line mode client, then you need to issue (M)GETs and (M)PUTs.

DownLoad Examples:

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

Example 1: Download a single entry:

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

Example 2: Download Multiple entries:

   Downloading multiple entries is just as simple as downloading a single entry. Just issue the MGET
   command with a POWER-ACCEPTABLE filter. For example, to down load all entries starting
   with L, issue MGET L*:

Please note that POWER entries have either ASA or machine codes, known as CC codes.
   You can have the server strip the cc byte, change it to blank, or pass it to the client as follows:

   To strip it:                               Issue SITE CC = OFF
   To replace with a blank:           Issue SITE CC = BLANK
   To pass it to client:                  Issue SITE CC = ON

    If you choose to pass the CC byte to the client, then remember that it goes through the translation table.
    This might be OK for ASA codes. But for Machine codes, well, who knows!

Upload Examples:

Example 1: Upload a single file to RDR Queue:

(We assume that we are in the RDR subdirectory!!!!!)

To upload a file to RDR queue, just issue PUT filename


     If your are thinking that we've just submitted a job to POWER, then
   you are absolutely correct!!

Example 2: Upload a single file to LST or PUN Queue:

    To upload a file to LST or PUN queue, just issue PUT filename

    The server creates filename (i.e., LIST) entry in LST/A. Notice that the
     server drops the file extension (i.e., JOB), if any.

Example 3: Upload multiple files:

   Uploading multiple files is just as simple as uploading a single file. You
   simply issue MPUT command and the server takes care of the rest!!

   Please note that uploading to LST or PUN queues, requires you to specify the "entry's" disposition.
   The admin can code TGT_DISP = d where d is the default disposition. The user, if so desires, can
   override the default disposition by issuing the SITE DISP = d command as well.

   In addition, uploading binary data requires you to set TGT_RECL, via SITE RECL = nnn.
   Uploading binary data makes sense only if your source records are fixed in length and are in the right
   character set (i.e., EBCDIC).

   Finally, please note that the server drops NULL ASCII lines, if any.

ftp> mget L*
200 Command okay.
150 File status okay, about to open data connection.
226-Records sent : 000000088
Bytes dropped: n/a
226 Closing data connection.
ftp: 1390 bytes received in 0.49Seconds 2.84Kbytes/sec.
200 Command okay.
150 File status okay, about to open data connection.
226-Records sent : 000000020
Bytes dropped: n/a
226 Closing data connection.
ftp: 694 bytes received in 0.33Seconds 2.10Kbytes/sec.
ftp>

ftp> cd /PWRSHELL/rdr
250 Requested file action okay, completed.
ftp> pwd
257 "/PWRSHELL/RDR"
ftp> put list.job
200 Command okay.
150 File status okay, about to open data connection.
226-Records rcvd : 000000008
Bytes dropped: 000000001 <<<--- very interesting!!!!!!!!
226 Closing data connection.
ftp: 165 bytes sent in 0.00Seconds 165000.00Kbytes/sec.
ftp>

ftp> cd /PWRSHELL/LST/A
250 Requested file action okay, completed.
ftp> pwd
257 "/PWRSHELL/LST/A"
ftp> put list.job
200 Command okay.
150 File status okay, about to open data connection.
226-Records rcvd : 000000008
Bytes dropped: 000000001
226 Closing data connection.
ftp: 165 bytes sent in 0.00Seconds 165000.00Kbytes/sec.
ftp>

ftp> mput xpc*.*
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.
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>