On Thu, 28 May 2015 14:23:05 -0700, Charles Mills wrote:

>... by real mainframe programmers, without benefit of documentation LOL.
>
>We tell them
>
>BINARY
>GET fmid.pax (REPLACE
>
Much the same here, except that by our Corporate Standard they
must first un-zip it or un-jar it.  Do any have restrictions on FTP?
Because of our Corporate Standard, we recommend

BINARY
PUT fmid.pax

... from the waystation.  There's no other way they could get
through the Javascript to our server.

(BTW, does anyone have "curl https://..."; working?  I tried it
yesterday and it couldn't find its certificate bundle with both
hands.  Works fine from Linux.)

>Everything is in that one piece and then we have them do
>
>pax -rv -f /blahblah/fmid.pax
>
>and then
>
>ogetx /blahblah/fmid/INSTJCL MY.PDS
>
(You could bypass that step with "UDLIST /blahblah/fmid/INSTJCL",
but we don't tell them that because real mainframe products
don't use UDLIST.)

>and they are off and running.

-- gil

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to