Yes, OMVS is part of z/OS, but I m sure that by "to OMVS" he means "to a file 
in an OMVS file system".

You should be able to receive from an XMIT file in batch TSO without a prompt. 
AFAIK you can only receive from SPOOL in foreground.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


________________________________________
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of 
Paul Gilmartin <0000000433f07816-dmarc-requ...@listserv.ua.edu>
Sent: Monday, December 9, 2019 1:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Interchange best practice? (was: GIT ... length issue)

On Mon, 9 Dec 2019 05:44:08 -0600, Lionel B Dyck wrote:

>If you are trying to ftp the rocket git distribution then you should be
>ftp'ing it to OMVS and not to z/OS datasets.  If you are trying to work with
>the zigi (z/OS ISPF Git Interface) then again, ftp to OMVS files and use the
>install.sh script to get the files to z/OS for use.
>     "... to z/OS ..."?
Isn't OMVS already just part of z/OS?

What technique requires the least error-prone human interaction.

I believe the package should be a single file, transferred to z/OS as *binary*.

o cksum is your friend.  Is a checksum supplied with the package.

o CBTTAPE.org has some practices worth assimilating.

o The package might be a pax archive, extractable with "pax -r ..."

o Or a .zip, extractable with "jar -x ..."
  Is jar generally available on z/OS systems without optional installation?

o PDS[E]s can be TRANSMIT unloaded within the pax/zip.  Cf. CBTTAPE.org.
  RECEIVE has an INDD option which can accept allocated OMVS files.
  RECEIVE runs only under TSO, and getting to TSO from OMVS is a
  tedious extra step.

o It's a shame that:
  - RECEIVE can't run outside TSO.  JCL EXEC or Rexx ADDRESS LINKMVS
    would be great.
  - RECEIVE requires reply to a prompt.
  - IEBCOPY doesn't support OMVS files as PDSU.  SMP/E does
    an extra conversion step to make that work.
  - AMATERSE doesn't support OMVS files as archive SYSUT1.
    I can cheat this, but support would be lacking.
  - OMVS directories are not supported as STEPLIB catenands.
  - OMVS directories are not supported as SYSEXEC catenands.

o Accommodating site naming standards can be a PITA.

o What about the instructions?  An ASCII README file outside the archive?

o SMP/E?

Any suggestions?
-- gil

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to