Copy PDS Members from z/OS to OpenVMS

This Process copies a PDS and all of its members from z/OS to a text library on OpenVMS. Note that the string of SYSOPTS parameters is enclosed in double quotation marks.

PDSCPY1  PROCESS      SNODE=CD.OS390.NODE
STEP01   COPY  FROM  (DSN=SMITH.INPUT83.MEMBERS SNODE)        -
               TO    (DSN=DUA0:[RJONES.CDTEST]PDSTEST.TLB     -
                      DISP=OLD                                -
                      DCB=(DSORG=PO)                          -
                      SYSOPTS="LIBRARY=’TEXT’ REPLACE" PNODE)

Copy PDS Members from z/OS to OpenVMS
This Process copies a PDS and all of its members from z/OS to a text library on OpenVMS. Note that the string of SYSOPTS parameters is enclosed in double quotation marks.
Copy a File from Disk to Tape (OpenVMS)
The following example copies an OpenVMS file from disk to tape. Specifying the /OVERRIDE qualifier causes the name of the tape volume to be ignored. The /OVERRIDE qualifier can be added either to the MOUNT command or to the tape label parameter. The example shows the qualifier added to the parameter.
Copy a File from Tape to Disk (OpenVMS)
The following example copies an OpenVMS file from tape to disk. Specifying the /OVERRIDE qualifier causes the name of the tape volume to be ignored.
Copy from z/OS to OpenVMS and Specifying a User-Defined Translation Table
This Process, submitted from the OpenVMS node, copies from a Sterling Connect:Direct for z/OS node to a Sterling Connect:Direct for OpenVMS node. It illustrates how a user can specify a user-defined translation table. Using the XLATE keyword in a Process overrides the default translation table; the Sterling Connect:Direct system will extract a module from the OpenVMS text library CD_1.TBL.
Copy a Single Entry from the OpenVMS Text Library to a z/OS Member
This Process sends a single entry from an OpenVMS text library to a member of a PDS on z/OS.
Copy All Entries from an OpenVMS Text Library to z/OS
This Process copies all the modules of a text library to respective members of a PDS on z/OS. Note the use of the asterisk (*) with the SELECT parameter.
Copy a Data Set from a z/OS Node to an Executable File on an OpenVMS Node
This Process, submitted from the OpenVMS node, copies the z/OS data set RSMITH.ACCTJAN to file specification DUC4:[ACCT.COM]JAN.EXE at the OpenVMS node. For the appropriate file attribute information, the SYSOPTS parameter TYPE=IMAGE must be specified. Also, BINARY must be specified as part of the SYSOPTS parameter so that EBCDIC to ASCII translation will not occur.
Copy an Executable File from an OpenVMS Node to a z/OS Node
This Process, submitted from the OpenVMS node, copies the OpenVMS file JAN.EXE in directory [ACCT.COM] on device DUC4 to data set RSMITH.ACCTJAN at the z/OS node. BINARY must be specified as part of the SYSOPTS parameter so that ASCII to EBCDIC translation will not occur.
Copy a Text File from OpenVMS to Microsoft Windows and Back to OpenVMS
In this example, a text file (TIME_TEST.TXT) is being copied from the OpenVMS platform to Microsoft Windows and being renamed VMS_TEST.TXT. In the next COPY statement, the VMS_TEST.TXT file is copied from the Microsoft Windows platform back to OpenVMS and being renamed WIN_TIME_TEST.TXT.
Copy between the z/OS and OpenVMS Platforms
In this example, the PNODE resides on an OpenVMS system while the SNODE is on a z/OS system. This is a two-step Process where in step 1 a file (CSDQA1.TESTFILE.BENCH.M100) is being copied from the SNODE to a file on the PNODE and being renamed test100.dat. In step 2 the OpenVMS file, test100.dat, is copied to a new z/OS dataset called CSDQA2.TEST.MB100. The SUB1 statement submits a Process that resides on the z/OS system.
Copy and Compare Files on OpenVMS
In this example Processes, two files are being copied and then compared. If the two files check out to be the same, the user is notified that the compare was good; if not, the user is notified that the compare failed.
Copy HFS and Text Files Back and Forth Between z/OS and OpenVMS
In this example. the PNODE is OpenVMS while the SNODE is z/OS. For each node, userids and passwords have been included. Step up1 copies a HFS text file from the z/OS USS to a text file on the OpenVMS system called hfsout.txt. The OpenVMS directory is disk$data:[qaalpha.q3a]. Step back1 is just the opposite but it names the HFS file unix2.txt. The sysopts="permission" gives read write authority to HFS files. The sysopts="binary" indicates the data is not to be converted from ASCII to EBCDIC.]
Copy a Text File from OpenVMS to UNIX and Back to OpenVMS
In this example, a text file (TIME_TEST.TXT) is being copied from the OpenVMS platform to UNIX. In the next COPY statement, the TIME_TEST.TXT file is copied from the UNIX platform back to OpenVMS and being renamed UX_TIME_TEST.TXT.
Copy a FB Text File to a z/OS PDS File and Pull Back to OpenVMS
In this example, a text file with fixed-length records on an OpenVMS node is being copied to a z/OS PDS file and then copied from the z/OS secondary node and pulled back to the OpenVMS primary node as a fixed-block text file.
Copy a Binary File from OpenVMS to Microsoft Windows and Back
In this example, a binary file (TEST.EXE) is being copied from the OpenVMS platform to Microsoft Windows. In the next COPY statement, the TEST.TXT file is copied from the Microsoft Windows platform back to OpenVMS.
Copy a Binary File from OpenVMS to UNIX and Back
In this example, a binary file (TEST.EXE) is being copied from the OpenVMS platform to UNIX. In the next COPY statement, the TEST.TXT file is copied from the UNIX platform back to OpenVMS (ux_test.exe).
Copy an OpenVMS Key-Sequenced File to an HP NonStop Node
This Process, submitted from the OpenVMS node, will copy a key-sequenced file to the Sterling Connect:Direct for HP NonStop node. When copying files from Sterling Connect:Direct for OpenVMS to Sterling Connect:Direct for HP NonStop nodes, include SET XLATE ON in the SYSOPTS parameter of the TO clause of the COPY statement. Because the Sterling Connect:Direct for OpenVMS system translates ASCII characters to EBCDIC, the XLATE subparameter will turn on the text conversion utility and translate from EBCDIC to ASCII. The FASTLOAD option is used to reduce disk I/O overhead.
Copy an OpenVMS File from Disk to Tape
The following example copies an OpenVMS file from disk to tape. Specifying the /OVERRIDE qualifier causes the name of the tape volume to be ignored. The /OVERRIDE qualifier can be added either to the MOUNT command or to the tape label parameter. The example shows the qualifier added to the parameter.
Copy an OpenVMS File from Tape to Disk
The following example copies an OpenVMS file from tape to disk. Specifying the /OVERRIDE qualifier causes the name of the tape volume to be ignored.
Use Symbolics in an OpenVMS COPY Statement
This example shows the basic use of symbolics in a Process. Both the FROM and TO files, as well as the file disposition, are resolved at Process submission.
Copy an OpenVMS Sequential File to a Text Library
This example shows the format for copying a sequential file to a text library.
Copy a File from OpenVMS to z/OS and Back to OpenVMS
These example COPY statements (STEP01 and STEP02) copy an executable file from a Sterling Connect:Direct for OpenVMS node to a Sterling Connect:Direct for z/OS node and then back to the Sterling Connect:Direct for OpenVMS node. Because BINARY is specified as part of the SYSOPTS parameter, ASCII-to-EBCDIC translation does not occur. Enclose the SYSOPTS string in double quotation marks.

Parent topic: Copy a File from Sterling Connect:Direct for HP NonStop to Sterling Connect:Direct for z/OS

Parent topic: Copy PDS Members from z/OS to OpenVMS