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



-----Original Message-----
From: Yaroslav Kuzmin [mailto:ykuz...@rocketsoftware.com] 
Sent: Wednesday, July 27, 2016 7:57 AM
To: Carroll, Sandra E (Sandra) <carr...@nationwide.com>; perl-mvs@perl.org
Cc: perl5-port...@perl.org
Subject: Re: ASCII support in z/OS

Hi Carroll

If you use scripts in encoding IBM-1047 on USS z/OS it is not a problem.
You can set filetag <text> encoding <IBM-1047> using tool (chtag -t -c IBM-1047 
<filename> )

--

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

В Вт., 26/07/2016 в 11:51 +0000, Carroll, Sandra E (Sandra) пишет:
> It depends,
> I know I use no ASCII in any scripts (no need for it)  I'm using perl for 
> system usage.   I'm
> working with z/OS EBCDIC Datasets, RACF and other files that are native 
> EBCDIC. I need my files
> stored and maintained as EBCDIC.  If it doesn't break that, I have no 
> opinion.   If it breaks that
> and starts creating files in in ASCII on z/OS then I have a problem.
>
> Websphere is a royal PITA due to its asci support.
>
> Sandra
>
>
>
> -----Original Message-----
> From: Yaroslav Kuzmin [mailto:ykuz...@rocketsoftware.com]
> Sent: Tuesday, July 26, 2016 7:44 AM
> To: perl-mvs@perl.org
> Cc: perl5-port...@perl.org
> Subject: ASCII support in z/OS
>
> Hi All,
>
> IBM offers  all tools  build with 'ASCII support' for  USS z/OS.
>
> Overview:
> Enhanced ASCII support is a collection of services and options for 
> dealing with the EBCDIC/ASCII problem. :
>
>     Files can be "tagged" (using chtag ) to indicate whether or not 
> they are pure text files, and if they are, the character set (CCSID) 
> used to encode them. The typical values will be "1047" (for
> ibm-
> 1047) or "819" (for iso8859-1).
>     C/C++ programs can be compiled such that all the character and 
> string constants in the program are compiled into ASCII (or other code page, 
> for that matter), rather than EBCDIC.
>     C/C++ programs are marked with a "program CCSID" that indicates 
> the character set the program uses internally. Note that all programs have a 
> program CCSID,
>     Given a tagged file, data can automatically be converted from one 
> code page to another when the file is read or written.
>
>
> Documentation:
>     Unix System Services Planning
>         Chapter 11 (Converting files between code pages), section 
> "Using Enhanced ASCII" (http://w ww 
> .ibm.com/support/knowledgecenter/en/SSLTBW_2.2.0/com.ibm.zos.v2r2.bpxb200/uenha.htm),
>  provides an overview of how to setup and use Enhanced ASCII support.
>     Unix System Services (USS z/OS) Command Reference contains details on 
> these commands:
>         chtag - query/change the file type (binary/text) and codeset 
> information for a file.
>         ls - the -T flag can be used to display file tag information.
>         pax - interchange portable archives. pax can record (on 
> archive) and honor (on restore) file tag information.
>         tar - similar to pax. z/OS tar supports processing of file tags.
>     XL C/C++ Programming Guide
>         Chapter 11 (Performing z/OS UNIX file system I/O operations), 
> section "File tagging and conversion" 
> (http://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.2.0/com.ibm.zo
> s.v2r2.cbcpx01/c
> bc
> 1p273.htm), discusses file tagging, the notion of a program's CCSID, 
> and various facilities related to enhanced ASCII support
>         Chapter 32 "Using environment variables" 
> (http://www.ibm.com/support/knowledgecenter/en/SS
> LT
> BW_2.2.0/com.ibm.zos.v2r2.cbcpx01/setenv.htm) has very good 
> information and descriptions of specific environment variables (see below).
>
>     XL C/C++ Runtime Library Reference
>         Appendix B (Function support table), section "Enhanced ASCII 
> support" (http://www.ibm.com/ su
> pport/knowledgecenter/en/SSLTBW_2.2.0/com.ibm.zos.v2r2.bpxbd00/enhasci
> i.htm) has a good discussion of the feature test macros defined for 
> various levels of enhanced ASCII support and a large table describing the 
> level of support for enhanced ASCII for nearly all runtime functions.
>      z/OS Language Environment Programming Reference
>         Chapter 2 (Using the Language Environment runtime options) 
> describes the FILETAG runtime option
>     z/OS Language Environment Programming Guide
>     This manual describes how to control runtime options using 
> environment variables
> (_CEE_RUNOPTS) and compile-time pragmas (#pragma runopts).
>
>     UNIX System Services z/OS Version 1 Release 7 Implementation 
> Redbook, Chapters 10.13 (Enhanced ASCII functionality), 10.14 
> (Automatic conversion) and 10.15 (File tagging) are good, but old (2006).
>
>
> If all tools will work with ASCII support system, the z/OS can use the 
> ISO-8859-1 character set
> (ASCII) instead of IBM-1047 (EBCDIC) and is VERY VERY GOOD.
>
> We are now build bash-4.3 and git-2.4.0 with ASCII support , we test 
> these tools. But to complete the work git needed  perl c ASCII support. And 
> so we want to build perl with ASCII support.
>
>
> So :
>  1 how to make a branch hints/os390-ascii.sh or in file hints/os390.sh  ?
>
>  2 Should to support two branches perl-zOS-ebcdic и perl-zOS-ascii or 
> only support one perl-zOS- ascii ?
>
>  3 I have the first progress for version perl-zOS-ascii.
>
>
>
> --
>
> 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
>
> ================================
> 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.

--

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

================================
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