The main problem, obtain new tools to z/OS. tools is  very outdated on USS z/OS.

This will leave the encoding EBCDIC and go to the encoding ISO-8859-1 on USS.
and is able to build newer versions of the tools with minimum work on porting.


If the community perl knows about encoding EBCDIC , the community git does not 
know about it.

turn on the system ASCII support is much easier than working with the encoding 
EBCDIC .

--

Regards,

Yaroslav Kuzmin
Developer C/C++ ,z/OS , Linux
3 Zhukovskiy Street · Miass, Chelyabinsk region 456318 · Russia
Tel:  +7.922.2.38.33.38
Email: ykuz...@rocketsoftware.com
Web: www.rocketsoftware.com

В Ср., 27/07/2016 в 12:30 +0000, Carroll, Sandra E (Sandra) пишет:
> 100% of what I do, and many (if not most all) on z/OS is EBCDIC based not 
> ASCII based.
> We do not want or need our files ascii encoded by default if that's what 
> you're suggesting.
> Being able to natively read a ascii file is a plus but native encoding needs 
> to remain EBCDIC.
>
> That would be like making EBCDIC the default encoding on Linux.
> what we do is parsing 5-10 million line per day per system log files (so over 
> 100 million lines)
> that are MVS (not USS) datasets.
>
> My question is what perceived problem are you trying to fix?
> Is this to make porting easier or is it to fix a problem accessing files on 
> zOS?
>
> Sandra



================================
Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ 
+1 877.328.2932 ■ +1 781.577.4321
Unsubscribe From Commercial Email – unsubscr...@rocketsoftware.com
Manage Your Subscription Preferences - 
http://info.rocketsoftware.com/GlobalSubscriptionManagementEmailFooter_SubscriptionCenter.html
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy
================================

This communication and any attachments may contain confidential information of 
Rocket Software, Inc. All unauthorized use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please notify Rocket 
Software immediately and destroy all copies of this communication. Thank you.

Reply via email to