Skip to main content

Send a file to an OS/390 Remote Access System


Table of Contents

Send a file to an OS/390 Remote Access System

Send a file to an OS/390 Remote Access System (Last Revised: 06/19/03 -A-)

Use the procedure outlined below to move a file from any OS/390 system by FTP to SVSCVMA. The file is then moved to an OS/390 Remote Access system through the JES card reader. (With minor adjustments a similar process could be used for OS/390 using JES3 or VM systems.)

For assistance with this procedure, please contact the DTSC using the process describe under the "Contact" locator in the left column.


  1. Package the information using the TSO XMIT command with the OUTDATASET parameter. This will create a fixed block, sequential file with a logical record length of 80. For example, to package SYS1.PARMLIB in dataset MVS1.PARMLIB.XMIT, use the command below.

    XMIT NODE1.USER1 DA('SYS1.PARMLIB') OUTDATASET('MVS1.PARMLIB.XMIT')
  2. Send the sequential file created by XMIT to the DTSC data center as described in the following steps.
    1. Point an FTP Client to SVSCVMA.DAL-EBIS.IHOST.COM
    2. Logon at the FTP prompt from SVSCVMA.
      The userid for SVSCVMA is a valid ETP personal userid. That is, use the same userid you might use to control a guest operating system or access online publications.
    3. Answer the password prompt to complete the logon.
    4. The default disk is userid.191. For example, if the ETP personal userid is ETPCCWW the default disk where the information will be stored is ETPCCWW.191. The ETPCCWW.191 disk will work fine as long as it is large enough to hold the file packaged by XMIT. Usually, these disks are small and only viable for the smallest of transfers. When the disk is not large enough please contact the DTSC for assistance. With an approved request (there could be a charge for the disk space), for FTP transfers to ETP personal userids, the DTSC usually provides a 195 disk.
    5. Use the the FTP Client change directory command to access the ETP personal userid 195 disk.
      This may be different depending on the FTP Client used. For example, on Windows NT, for a userid of ETPCCWW, at the FTP prompt type: If the response is similar to "Working directory is ETPCCWW 195" proceed to the next step.
      If the response is similar to "Working directory ETPCCWW 195 is ReadOnly, due to other links" then the ETPCCWW 195 disk is usually linked to ETPCCWW. Follow the steps below to release the disk from ETPCCWW. (This example will continue to use ETPCCWW as the ETP personal userid. Substitute the ETP personal userid assigned to you for ETPCCWW.)
      1. Logon to ETPCCWW
      2. Type DETACH 195
      3. At this point you can remain on ETPCCWW or disconnect depending on your other needs.
      Issue the FTP Client change directory command again. The response should be similar to "Working directory is ETPCCWW 195" so you can proceed to the next step.
    6. Do not proceed until you receive a message similar to "Working directory is ETPCCWW 195".
    7. Set the transfer to binary so there is no translation of characters. This may be different depending on the FTP Client used. For example, on Windows NT at the FTP prompt type: FTP will respond with Representation type is IMAGE.
    8. The FTP Server is running on VM. Use the SITE command to set the logical record length and record format. The format of the SITE command when using Windows NT is shown below. FTP will respond with Site command was accepted.
    9. Verify the binary file transfer and the file attributes with the STAT command. The format of the STAT command when using Windows NT is shown below. FTP will respond with the Status information. Verify the working directory is as expected (using the example, ETPCCWW 195), the transfer is type IMAGE, the record format is F and the record length is 80.
    10. Upload the file using the FTP Client PUT command. This may be different depending on the FTP Client used. For example, on Windows NT at the FTP prompt type: where yourfile is the name of the file you want to upload. The format of yourfile is dependent on the platform where the FTP Client is running. where etpfile.etptype is an EIGHT character (or less) name you assign to the file, followed by a period, followed by an EIGHT character (or less) name you assign.
      For example, if a file called DELETE.DAT should go to the DTSC, the PUT command might be:
    11. End the FTP session with the FTP Client QUIT command. This may be different depending on the FTP Client used. For example, on Windows NT at the FTP prompt type:
    12. See Figure 1 for an example of an exchange to upload a file.
  3. At this point the data for OS/390 is on a VM disk. Follow the steps below to move it to OS/390.
    1. Logon to the ETP personal userid on the system where the OS/390 system runs -- it is the system where you would issue the SVXLOG command to start OS/390 -- usually SVSCDR2 or SVSCSY4. For example, if you have IPL'd your OS/390 system on SVSCDR2, logon to the ETP personal userid on the SVSCDR2 system. (The example with ETP personal userid ETPCCWW will continue below. Substitute your the ETP personal userid for ETPCCWW.)
    2. Obtain access to the ETPCCWW 195 disk using the VM commands below. (This example is robust -- under many circumstances all of the commands are not required.) Be sure the lower right hand corner of the screen says VM READ or Running. Use the following commands from VM READ or Running to access to the ETPCCWW 195 disk from ETP personal userid ETPCCWW.
      1. REL D (DET
      2. DET 195
      3. VMLINK * 195 <195 D MR>
      4. To see a listing of the files on the D disk, type FILEL * * D. (Exit the FILEL list with PF3.)
      5. Proceed to the next step when the the lower right hand corner of the screen says VM READ or Running again.
    3. Send the file to OS/390 using the SJCL command. Type SJCL and press the enter key when VM READ or Running is in the right hand corner of your VM session. This command will prompt you for the name of the system which should receive the file you sent by FTP -- this is the name of the system which runs OS/390; it is the name you used with the SVXLOG command to start OS/390. The SJCL command will also prompt you for the file name -- this is the name etpfile.etptype referenced above for FTP; using the example MYDUMP.MYDATA would be entered as MYDUMP MYDATA (no intervening period) when SJCL prompts for the name of the input file. Depending on the size of the file, it might take several seconds for SJCL to end. Messages similar to those below will be produced when SJCL ends.
      PUN FILE 7982 SENT TO ETPCCUU RDR AS 0008 RECS 0092 CPY 001 A
      SJCL is ending.
    4. Release the D disk (which is known as address 195) so it is available for another FTP with the REL D (DET command.
    5. Disconnect from the ETP personal userid if you do not have other activities for it.
  4. At this point, the data for OS/390 is located in the OS/390 JES2 card reader. The data will be moved from the JES2 card reader to a cataloged data set called suserid.etpfile.etptype (these terms are explained in detail below.) Be sure a data set with the name suserid.etpfile.etptype does not exist in the OS/390 system.
  5. Use the JES2 start reader command shown below to move the data from the JES2 card reader to the JES2 spool. The data will be placed in a cataloged data set called suserid.etpfile.etptype. (Be sure suserid.etpfile.etptype does not exist in the OS/390 system.)
  6. The data resides in the JES2 spool as a batch job. The job name is SJCL. The batch job will attempt to execute in CLASS A. The output of the job uses MSGCLASS H and can be viewed using ISPF SD;H ALL Option. Depending on the activities in the OS/390 system, you may need to adjust the JES2 initiators to allow the SJCL batch job to run.
  7. When the SJCL batch job completes execution, the data resides in the ETP OS/390 system in data set which has the name in the format of suserid.etpfile.etptype where: Unpackage the data in suserid.etpfile.etptype using the TSO RECEIVE command with the INDATASET parameter. Using ISPF Option 6, enter the RECEIVE command shown below. All of the documented features of TSO RECEIVE are available at the TSO RECEIVE prompt.
  8. The original data is now available on the OS/390 Remote Access ETP system with the exact attributes as the original dataset.
  9. Delete data set suserid.etpfile.etptype since it is no longer required.
  10. End of process.

Figure 1. Example of FTP Uploading a file to SVSCVMA.

F:\>ftp svscvma.dal-ebis.ihost.com
Connected to svscvma.dal-ebis.ihost.com
220-FTPSERVE IBM VM Level 310 at SVSCVMA, 23:01:57 CDT SUNDAY 07/02/00
220 Connection will close if idle for more than 5 minutes.
User (svscvma.dal-ebis.ihost.com:(none)): ETPCCWW
331 Send password please.
Password:
230 ETPCCWW logged in; working directory = ETPCCWW 191

ftp> cd etpccww.195
250 Working directory ETPCCWW 195 is ReadOnly, due to other links

ftp> cd etpccww.195
250 Working directory is ETPCCWW 195

ftp> type binary
200 Representation type is IMAGE.

ftp> quote site fix 80
200 Site command was accepted.

ftp> quote stat
211-Server FTP talking to host 32.101.152.171, port 1327
211-User: ETPCCWW  Working directory: ETPCCWW 195
211-The control connection has transferred 499 bytes.
211-There is no current data connection.
211-The next data connection will be actively opened
211-to host 32.101.152.171, port 1327, using
211-mode Stream, structure File, type Image, byte-size 8.
211-record format is F, record length 80
211 FTPSERVE Translate Table: STANDARD

ftp> put delete.dat mydump.mydata
200 Port request OK.
150 Storing file 'mydump.mydata'
250 Transfer completed successfully.
5360 bytes sent in 0.03 seconds (178.67 Kbytes/sec)

ftp> quit
221 Quit command received. Goodbye.
   

If you have any feedback or questions, please respond to: sdohelp@svscvm1.vnet.ibm.com