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

This Process copies a file from a Sterling Connect:Direct® for HP NonStop node to a new SMS-controlled file at a Sterling Connect:Direct for z/OS® node.

SMS1   PROCESS  PNODE=CD.HPNONSTOP                 -
                SNODE=CD.OS390.NODE
STEP1  COPY     FROM  (PNODE                       -
                       DSN=$VOL.SUBVOL.TANFILE     -
                       DISP=SHR                    -
                TO    (SNODE                       -
                       DISP=(NEW,CATLG)            -
                       DSN=DATA1.SEQ.OS390FILE     -
                       DCB=(DSORG=PS, LRECL=80)    -
                       SPACE=(80,(1500,100),RLSE)  -
                       UNIT=SYSDA                  -
                       SYSOPTS="AVGREC=U           -
                       MGMTCLAS=TEST01             -
                       STORCLAS=TEST01             -
                       DATACLAS=TEST01")

Copy a File from Sterling Connect:Direct for HP NonStop to Sterling Connect:Direct for z/OS
This Process copies a file from a Sterling Connect:Direct for HP NonStop node to a new SMS-controlled file at a Sterling Connect:Direct for z/OS node.
Copy an HP NonStop File to an i5/OS Node
This Process copies an HP NonStop file to a member of a physical data base file on i5/OS. The i5/OS file is created with maximum members specified as 100. The HP NonStop file is translated from ASCII to EBCDIC.
Copy a File from Microsoft Windows to z/OS
This Process copies a text file from a remote Microsoft Windows system (where Sterling Connect:Direct is not installed) to a z/OS partitioned data set (PDS). When copying a file to or from a remote Microsoft Windows computer, you must use the Universal Naming Convention (UNC) method for specifying the file name. Do not use a drive letter. The UNC consists of two backslashes, the computer name, a single backslash, and the share name. The share, ROOT_C, must be accessible to Sterling Connect:Direct for Microsoft Windows server. In this example, the computer name is WIN_SYS1 and the share name is ROOT_C.
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 Files Between UNIX and z/OS
This Process copies a file from UNIX to z/OS. The Process was initiated from the UNIX node. The ckpt parameter specifies that no checkpoints will be taken. The ckpt parameter is generally coded between the FROM and TO clauses of the COPY statement.
Copy a VSAM File from VM to an Entry-Sequenced HP NonStop File
The following Process copies a VM VSAM file to an entry-sequenced HP NonStop file. The entry-sequenced file with extents of 100 pages each is created as indicated by the SYSOPTS parameter. Note that the VM file name is not enclosed in single quotation marks. If the VM file name is not placed between quotation marks, the Sterling Connect:Direct system assumes the file is a VSAM file.
Copy a File from z/OS to VSE (DYNAM/T Tape Files)
This multi-step Process copies various sequential files from a z/OS node (the SNODE) to VSE DYNAM/T tape files at the PNODE. Different record formats are specified in the steps. Note that a TYPE file record is specified in STEP03. This record contains the DCB and UNIT information for this file. The TYPE record must be in the TYPE file at the destination (VSE node).
Use Defaults to Allocate a File (z/OS to z/OS)
This Process designates that the destination file is placed on a specified unit and volume. The SPACE information is also supplied. Because DCB information is not specified for the destination data set, DCB information from the source data set is used.
Submit a Process from a Sterling Connect:Direct for HP NonStop Node that Copies a File from z/OS to HP NonStop
This Process, submitted from Sterling Connect:Direct for HP NonStop, copies (pulls) a file from Sterling Connect:Direct for z/OS to the HP NonStop node. The TO file specification contains a "SET TYPE E" parameter in SYSOPTS, in case the file is not present and must be created. The FROM file normally needs no file attributes (DCB or SYSOPTS). The XLATE option is used to specify translation. This must always be specified in the SYSOPTS clause associated with the HP NonStop dataset. A checkpoint interval of 10 MB is specified.
Copy a Code 0 Unstructured file from HP NonStop to z/OS
This Process copies an unstructured file to a z/OS node. Because an Enscribe unstructured file has no intrinsic record length, the DCB parameter is used on the FROM file specification to define the record length with which the file is read.
Copy a File from HP NonStop to z/OS After Running DMRTDYN on z/OS
In this Process, STEP1 will invoke DMRTDYN to delete and unallocate DATA1.SEQ.KSDSFILE at the SNODE. Then $B.FILETEST.KSDSFILE will be copied from the HP NonStop node to DATA1.SEQ.VSAMKSDS at the HP NonStop node.
Copy a File from an HP NonStop Spooler to a z/OS Node
In this multi-step Process, STEP1 will execute a RUN TASK to invoke DMRTDYN at the SNODE to delete DATA1.SEQ.EXTOS390F. STEP2 will copy a file from the HP NonStop spooler to DATA1.SEQ.EXTOS390F at the SNODE. Because a spooler job number was not specified, the most recent job in the spooler for the job owner will be copied. A record format of FBA is used to maintain ANSI control characters.
Copy Between a z/OS Node and a Remote HP NonStop Spooler on an EXPAND Network
This multi-step Process copies between a z/OS node and a remote HP NonStop spooler on an EXPAND network. The Process is submitted from the HP NonStop node. STEP01 copies a file from a DSN on the z/OS node to the HP NonStop spooler. STEP02 copies a file from the HP NonStop spooler to a z/OS node.
Copy Files Between the HP NonStop Spooler System and a z/OS Node Using Job Number
This Process transfers a file from the HP NonStop spooler $S to a z/OS sequential file. The HP NonStop file has a job number of 3722 and a location (name) of #SPLFILE. The SPOOLER command is used to specify a supervisor other than the default of $SPLS. A record format of FBA is used to maintain ANSI control characters.
Copy a Disk File from HP NonStop to a Tape Device at z/OS
This Process is submitted on the HP NonStop node to copy a disk file on HP NonStop to a tape device at the z/OS node. Because NL (no labels) is specified, DCB attributes must be specified to identify the file on the volume.
Copy a Tape File from z/OS to a Disk File on HP NonStop
This Process is submitted at the HP NonStop node to copy a tape file from the z/OS node to a disk file on the HP NonStop node. Because NL (no labels) is specified, DCB attributes must be specified to identify the file on the volume. SYSOPTS is used to specify file creation parameters specific to HP NonStop.
Copy a File from z/OS to HP NonStop Using the FASTLOAD Option
This Process is submitted at the HP NonStop node to copy an entry-sequenced file from z/OS to a key-sequenced file at the HP NonStop node. The SYSOPTS subparameter SET FASTLOAD SORTED sets FASTLOAD and indicates to FUP that the data is sorted.
Allocate a VSAM Data Set and Copying a File from HP NonStop to z/OS
This Process invokes Sterling Connect:Direct DMRTAMS for VSAM file allocation. DMRTAMS (using IDCAMS commands specified in the Process) first deletes the old data set if it exists. It then defines and allocates it for use in the subsequent COPY statement. The file transmitted is an HP NonStop key-sequenced file.
Copy to an Entry-Sequenced File (HP NonStop to HP NonStop)
In this multi-step Process, STEP01 will execute FUP to purge $B.FILERESO.A11025 on the PNODE. A message will be sent to the spooler ($S.#FUPTEST) that indicates whether FUP executed successfully.
Copy Files Between HP NonStop Spooler Systems
This Process selects a spooler job by job number and copies it to another HP NonStop spooler system at a remote node. The HP NonStop file being copied has a job number of 3722 and a location (name) of #SPLFILA. The SPOOLER command is used to specify a supervisor other than the default of $SPLS.
Copy Text Files from HP NonStop to UNIX
This Process, submitted from the Sterling Connect:Direct for HP NonStop node, will copy datafile in $B.smith to /payroll/monthly/jan on the Sterling Connect:Direct for UNIX node. For Sterling Connect:Direct for UNIX nodes, the security user IDs and passwords are case sensitive.
Copy Binary Files from HP NonStop to UNIX
This Process, submitted from the Sterling Connect:Direct for HP NonStop node, will copy a file in $user.unixdata.cdcom to a binary file on the Sterling Connect:Direct for UNIX node.
Copy Binary Files from HP NonStop (OSS) to UNIX
This Process illustrates how to ensure data integrity when copying between a Sterling Connect:Direct HP NonStop (OSS) node and a UNIX node. The destination in STEP01 and source in STEP02 both have sysopts specified to denote a binary transfer.
Copy Files from HP NonStop to VM
This Process illustrates the transmission of a file from an HP NonStop node to a VM node. The Process is submitted on the HP NonStop node. EBCDIC-to-ASCII translation is requested with the SYSOPTS parameter SET XLATE ON. All SYSOPTS keyword values must be enclosed in parentheses, and the entire SYSOPTS string must be enclosed in double quotation marks.
Copy an HP NonStop Key-Sequenced File to a Sterling Connect:Direct for OpenVMS Node
This Process, submitted from the Sterling Connect:Direct for HP NonStop node, copies a key-sequenced file to the Sterling Connect:Direct for OpenVMS node. When Processes are submitted from Sterling Connect:Direct for HP NonStop to Sterling Connect:Direct for OpenVMS nodes, OpenVMS file names must be in single quotation marks. Note that COMPRESS is coded between the FROM and TO clauses of the COPY statement.
Copy Files from HP NonStop to VSE
This Process illustrates the transmission of files from an HP NonStop node to a VSE node. The parameter XLATE must be set to ON and positioned in the Process where the HP NonStop file is specified. XLATE translates the file from ASCII to EBCDIC. Symbolics will be resolved at submission.
Copy Binary Files from Microsoft Windows to HP NonStop (OSS)
This Process illustrates how to ensure data integrity when copying between a Microsoft Windows system and an HP NonStop (OSS) node. The destination in STEP01 and source in STEP02 both have sysopts specified to denote a binary transfer.
Copy a File from HP NonStop to VM
This example copies a file from HP NonStop to VM. It uses conditional statements to check the completion code from STEP01. If the completion code equals 0, then a message is issued to the operator that indicates that the transfer was successful. If the completion code is any value other than 0, then a message is issued to the operator that indicates that the transfer failed.
Copy a Data Set from a Spooler File on Sterling Connect:Direct HP NonStop to Sterling Connect:Direct z/OS
This example statement copies a data set from a spooler file on a Sterling Connect:Direct for HP NonStop node to a Sterling Connect:Direct z/OS node. In this example, the specified spooler supervisor name overrides the default of $SPLS. Job=253 specifies the spooler file uniquely.
Copy a File From HP NonStop to HP NonStop and Overriding SENDOPENFILE with OPENFILEXMT

Parent topic: Basic PROCESS Statement

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