Yep. Doesn't make a difference.
Frank
On 4/11/2017 11:02 AM, Carmen Vitullo wrote:
Have you tried the translate options in the OCOPY command
one example I have
OCOPY INDD(EBCIN) OUTDD(ASCOUT) CONVERT((BPXFX311)) FROM1047
Carmen
----- Original Message -----
From: "Frank Chu"<[email protected]>
To:[email protected]
Sent: Tuesday, April 11, 2017 9:48:48 AM
Subject: Odd behavior with OCOPY
Please forgive me if this the wrong group to post this question to, I
Didn't find any dedicated USS/OMVS mailing list.
One of my colleagues is using the default sh shell and when he uses
OSHELL to run some USS utilities in batch, the output he is get gets
back is in ASCII. I run bash and using the same JCL, the output I
receive is in the expected EBCDIC.
I've poked around in OSHELL and have determined that it's the OCOPY that
is doing weird things. The output on the USS side of things is in
EBCDIC but after OCOPY does it's thing to copy it over to the MVS side
of things, it ends up in ASCII.
The command in the OSHELL script is: "Ocopy indd(STDOUT)
outdd(oshout1) TEXT PATHOPTS(OVERRIDE)" . The default behavior is to
not do any sort of conversion but there is obviously a conversion
happening. Any clues as to where or what is causing OCOPY to behave
this way?
Thanks
Frank
--
Development Programmer
ColeSoft Marketing
www.colesoft.com
Phone : 540.456.6164
Email :[email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
