RE: ASCII support in z/OS

2016-08-07 Thread Carroll, Sandra E (Sandra)
Sorry,  you're missing the key point.  We're not all working in USS.  We cannot 
chtag a dataset on zOS.  That can only be done to files in USS.   This is 
asking z/OS users to possibly completely recode jobs (JCL) that run. Possibly 
rewrite existing perl scripts as well.   I sometimes have mixed EBCDIC/BINARY 
datasets,  how do I deal with those?

For example we open to a read a dataset PSYS.CICS.LOG.A20160404 in perl, that 
is not a file in USS .   
That dataset will be in EBCDIC.  Not ASCII.   
_BPXK_AUTOCVT=ON only applies to USS Files, not Datasets.  

To be frank,   if I have to start coping and converting datasets to USS files 
in ASCII.  I will not use perl.  I will rewrite in rexx and pull down the regex 
support package out there.

I'm sorry to be blunt, but a perl on z/OS that cannot process native z/OS 
datasets is useless to me.   Again,  it's like asking everyone in the ASCII 
community to give up ASCII and live in a EBCDIC world.  That's not going to 
happen.

Others may feel different and have different opinions.

It's hard enough to get z/OS people to use perl over rexx as is.  
Tell them they'll have to copy files to USS and make sure to convert to ascii 
will put up a red flag to any z/OS person IMHO.

I highly suggest you reconsider doing this.   I've not read yet what compelling 
reason there is that is forcing this.  I read a choice being made.  I've not 
read the perl community is forcing EBCDIC to go away and be all ASCII.  
So why must we do this?  Why would you force end users to change to make coding 
easier especially for a fundamental issue like this.

Sorry for the long email and jumping around a bit.

Sandra

-Original Message-
From: Yaroslav Kuzmin [mailto:[email protected]] 
Sent: Friday, August 05, 2016 5:56 AM
To: Carroll, Sandra E (Sandra) ; [email protected]
Cc: [email protected]
Subject: Re: ASCII support in z/OS

В Ср., 27/07/2016 в 13:06 +, Carroll, Sandra E (Sandra) пишет:
> I hope I'm understanding you on this.
>
> Users of perl on z/OS, work almost exclusively in EBCDIC.
> I understand from a porting Point of view.  However if fixing a 
> porting issue introduces to USS
> (OMVS) that our files are ASCII encoded.
> I do not believe you'll find many users who will find that acceptable.   I do 
> not find it
> acceptable myself.
> I am talking purely from the end user POV,   ascii encoding is useless to 
> many if not all of
> us.  If it introduces the need for us to chtag files so we can encode 
> them basic to EBCDIC the way they should have been encoded by default. 
> The overhead of doing work on zOS jumps and the value of perl goes down.

Of course users in the z/OS are working exclusively whit encoded EBCDIC. But 
the new program does not support the encoding EBCDIC. But in new programs need 
is there on z/OS. Therefore, the use of ASCII support on z/OS makes it easy to 
running new programs with minimal modifications, you need only include the 
ASCII support system in the program.
Of course users on z/OS you want to control and set the tag for all files using 
chtag. But the more programs will use the ASCII support the less you need to 
install the tag in the manual mode using chtag. When using programs with ASCII 
support  so it tag  will be set automatically . Users need only turn on ASCII 
support system by setting environment variable (_BPXK_AUTOCVT=ON) in USS z/OS.

>
> Remember,  we don't exclusively work in OMVS.   Most of what we'll do is z/OS 
> datasets   those
> have no CHTAG option.
> Coping to USS is often not an option either due to size or 
> confidentiality/integrity of data especially in the financial industry.

>
> That said, what perl does internally, I don’t' care,   what perl does to 
> files and datasets I do
> care very much.
> A file with no chtag should be read as EBCDIC A file with a chtag of 
> ISO-885901 should be read as ASCII.
>
>
> Sandra
>
>
> -Original Message-
> From: Yaroslav Kuzmin [mailto:[email protected]]
> Sent: Wednesday, July 27, 2016 8:51 AM
> To: Carroll, Sandra E (Sandra) ; 
> [email protected]
> Cc: [email protected]
> Subject: Re: ASCII support in z/OS
>
> 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 · 

Re: ASCII support in z/OS

2016-08-05 Thread Yaroslav Kuzmin
Sandra, I understand your concern. Of course dataset is the basic structure of 
the information
storage in z/OS. And correct work with them will remain in the perl.

--

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: [email protected]
Web: www.rocketsoftware.com


В Пт., 05/08/2016 в 10:26 +, Carroll, Sandra E (Sandra) пишет:
> Sorry,  you're missing the key point.  We're not all working in USS.  We 
> cannot chtag a dataset on
> zOS.  That can only be done to files in USS.   This is asking z/OS users to 
> possibly completely
> recode jobs (JCL) that run. Possibly rewrite existing perl scripts as well.   
> I sometimes have
> mixed EBCDIC/BINARY datasets,  how do I deal with those?
>
> For example we open to a read a dataset PSYS.CICS.LOG.A20160404 in perl, that 
> is not a file in USS
> .
> That dataset will be in EBCDIC.  Not ASCII.
> _BPXK_AUTOCVT=ON only applies to USS Files, not Datasets.
>
> To be frank,   if I have to start coping and converting datasets to USS files 
> in ASCII.  I will
> not use perl.  I will rewrite in rexx and pull down the regex support package 
> out there.
>
> I'm sorry to be blunt, but a perl on z/OS that cannot process native z/OS 
> datasets is useless to
> me.   Again,  it's like asking everyone in the ASCII community to give up 
> ASCII and live in a
> EBCDIC world.  That's not going to happen.
>
> Others may feel different and have different opinions.
>
> It's hard enough to get z/OS people to use perl over rexx as is.
> Tell them they'll have to copy files to USS and make sure to convert to ascii 
> will put up a red
> flag to any z/OS person IMHO.
>
> I highly suggest you reconsider doing this.   I've not read yet what 
> compelling reason there is
> that is forcing this.  I read a choice being made.  I've not read the perl 
> community is forcing
> EBCDIC to go away and be all ASCII.
> So why must we do this?  Why would you force end users to change to make 
> coding easier especially
> for a fundamental issue like this.
>
> Sorry for the long email and jumping around a bit.
>
> Sandra
>
> -Original Message-
> From: Yaroslav Kuzmin [mailto:[email protected]]
> Sent: Friday, August 05, 2016 5:56 AM
> To: Carroll, Sandra E (Sandra) ; [email protected]
> Cc: [email protected]
> Subject: Re: ASCII support in z/OS
>
> В Ср., 27/07/2016 в 13:06 +, Carroll, Sandra E (Sandra) пишет:
> >
> > I hope I'm understanding you on this.
> >
> > Users of perl on z/OS, work almost exclusively in EBCDIC.
> > I understand from a porting Point of view.  However if fixing a
> > porting issue introduces to USS
> > (OMVS) that our files are ASCII encoded.
> > I do not believe you'll find many users who will find that acceptable.   I 
> > do not find it
> > acceptable myself.
> > I am talking purely from the end user POV,   ascii encoding is useless to 
> > many if not all of
> > us.  If it introduces the need for us to chtag files so we can encode
> > them basic to EBCDIC the way they should have been encoded by default.
> > The overhead of doing work on zOS jumps and the value of perl goes down.
> Of course users in the z/OS are working exclusively whit encoded EBCDIC. But 
> the new program does
> not support the encoding EBCDIC. But in new programs need is there on z/OS. 
> Therefore, the use of
> ASCII support on z/OS makes it easy to running new programs with minimal 
> modifications, you need
> only include the ASCII support system in the program.
> Of course users on z/OS you want to control and set the tag for all files 
> using chtag. But the
> more programs will use the ASCII support the less you need to install the tag 
> in the manual mode
> using chtag. When using programs with ASCII support  so it tag  will be set 
> automatically . Users
> need only turn on ASCII support system by setting environment variable 
> (_BPXK_AUTOCVT=ON) in USS
> z/OS.
>
> >
> >
> > Remember,  we don't exclusively work in OMVS.   Most of what we'll do is 
> > z/OS datasets   those
> > have no CHTAG option.
> > Coping to USS is often not an option either due to size or
> > confidentiality/integrity of data especially in the financial industry.
> >
> >
> > That said, what perl does internally, I don’t' care,   what perl does to 
> > files and datasets I do
> > care very much.
> > A file with no chtag should be read as EBCDIC A file with a chtag of
> > ISO-885901 should be read as ASCII.
> >
> >
&

Re: ASCII support in z/OS

2016-08-05 Thread Yaroslav Kuzmin

Now perl inside working in the IBM-1047 encoding,  but we can build perl that 
he was working inside
in the ISO-8859 encoding.

There are two approaches using ASCII support in perl.

1
 Encoding IBM-1047 in inside perl.
 But add a check if the file is opened. And to determine the encoding of the 
file and tagging the
stream as an EBCDIC or ASCII. All files with the tag with ASCII set will 
automatically convert form
ISO-8859 to IBM-1047.
 When working perl all created files will be tagging by the IBM-1047

  plus: simply add new functionality to perl on z/OS.
is the opportunity to work with dataset
  con: able to work only with the ISO-8859


2
 Disable the EBCDIC support in perl and build perl that will work within the 
encoded ISO-8859
 add a check if the file is opened. And to determine the encoding of the file 
and tagging the stream
as an EBCDIC or ASCII. All files with the tag with EBCDIC set will 
automatically convert form IBM-
1047 to ISO-8859
 When working perl all created files will be tagging by the ISO-8859

 plus: the opportunity to work with UTF-8 encoding
it is not necessary to support the EBCDIC branch

 con: to work with dataset will need to do individual module


What are the proposals ?


--

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: [email protected]
Web: www.rocketsoftware.com

В Вт., 02/08/2016 в 21:53 -0600, Karl Williamson пишет:
> On 07/27/2016 09:18 AM, John Goodyear wrote:
> >
> > While it is valuable to get ASCII support for PERL on z/OS for reasons
> > such as git, I think other z/OS PERL users will have similar issues that
> > Sandra has voiced. Not everyone is reading/writing to Unix files on
> > z/OS, so chtag wouldn't help. Even if chtag is beneficial, it means
> > changing scripts/procedures to accommodate the new behavior. Also, if
> > the new PERL would wants to generate ASCII output by default, there is
> > further modification to scripts ect... to tell it to generate EBCDIC
> >
> > It seems the best solution from a usability standpoint is to be able to
> > build PERL so that it works on z/OS as before, or build it so that it
> > assumes the new behavior you are targeting to support git and other
> > software with PERL dependencies.
> >
> >
> > Regards,
> >
> > John Goodyear
> > z Systems Analytics zChampion
> > WSC z Systems Applied Technologies
> > Herndon, VA
> > [email protected]
> I agree with John about the need to continue to support the 1047-based
> perl.
>
> I suspect that it won't be too hard to get a Perl working in ASCII mode.
>   If you can figure out a way to get the hints file to work on both
> styles, that would be preferable, as a bunch of system information in it
> is applicable to the underlying operating system, and having two files
> would invite one getting updated and forgetting the other.
>
> Note that the perl Encode module can be used to translate to/from a data
> file in many many character sets/code pages to what perl is expecting.
> There are bugs with it on z/OS that I have not yet addressed, however.
>
> If I recall correctly, though, the ASCII/EBCDIC switch is not easily
> changeable per process or even per user.  I thought it was an everything
> on the machine or nothing type of deal, which, if so, is problematic.
> Hopefully, I'm wrong.
> >
> >
> > Inactive hide details for Yaroslav Kuzmin ---07/27/2016 08:51:20
> > AM---The main problem, obtain new tools to z/OS. tools is verYaroslav
> > Kuzmin ---07/27/2016 08:51:20 AM---The main problem, obtain new tools to
> > z/OS. tools is very outdated on USS z/OS. This will leave the
> >
> > From: Yaroslav Kuzmin 
> > To: "[email protected]" ,
> > "[email protected]" 
> > Cc: "[email protected]" 
> > Date: 07/27/2016 08:51 AM
> > Subject: Re: ASCII support in z/OS
> >
> > 
> >
> >
> >
> > 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++

Re: ASCII support in z/OS

2016-08-05 Thread Yaroslav Kuzmin
В Ср., 27/07/2016 в 13:06 +, Carroll, Sandra E (Sandra) пишет:
> I hope I'm understanding you on this.
>
> Users of perl on z/OS, work almost exclusively in EBCDIC.
> I understand from a porting Point of view.  However if fixing a porting issue 
> introduces to USS
> (OMVS) that our files are ASCII encoded.
> I do not believe you'll find many users who will find that acceptable.   I do 
> not find it
> acceptable myself.
> I am talking purely from the end user POV,   ascii encoding is useless to 
> many if not all of
> us.  If it introduces the need for us to chtag files so we can encode them 
> basic to EBCDIC the way
> they should have been encoded by default. The overhead of doing work on zOS 
> jumps and the value of
> perl goes down.

Of course users in the z/OS are working exclusively whit encoded EBCDIC. But 
the new program does
not support the encoding EBCDIC. But in new programs need is there on z/OS. 
Therefore, the use of
ASCII support on z/OS makes it easy to running new programs with minimal 
modifications, you need
only include the ASCII support system in the program.
Of course users on z/OS you want to control and set the tag for all files using 
chtag. But the more
programs will use the ASCII support the less you need to install the tag in the 
manual mode using
chtag. When using programs with ASCII support  so it tag  will be set 
automatically . Users need
only turn on ASCII support system by setting environment variable 
(_BPXK_AUTOCVT=ON) in USS z/OS.

>
> Remember,  we don't exclusively work in OMVS.   Most of what we'll do is z/OS 
> datasets   those
> have no CHTAG option.
> Coping to USS is often not an option either due to size or 
> confidentiality/integrity of data
> especially in the financial industry.

>
> That said, what perl does internally, I don’t' care,   what perl does to 
> files and datasets I do
> care very much.
> A file with no chtag should be read as EBCDIC
> A file with a chtag of ISO-885901 should be read as ASCII.
>
>
> Sandra
>
>
> -Original Message-
> From: Yaroslav Kuzmin [mailto:[email protected]]
> Sent: Wednesday, July 27, 2016 8:51 AM
> To: Carroll, Sandra E (Sandra) ; [email protected]
> Cc: [email protected]
> Subject: Re: ASCII support in z/OS
>
> 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: [email protected]
> Web: www.rocketsoftware.com
>
> В Ср., 27/07/2016 в 12:30 +, 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 – 
> [email protected] 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.

Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenu

RE: ASCII support in z/OS

2016-08-03 Thread Carroll, Sandra E (Sandra)
Just want to Thank Yaroslav Kuzmin and Karl Williamson for you work on perl for 
z/OS.
It is very much appreciated

Sandra




-Original Message-
From: Karl Williamson [mailto:[email protected]] 
Sent: Tuesday, August 02, 2016 11:54 PM
To: John Goodyear ; Yaroslav Kuzmin 

Cc: Carroll, Sandra E (Sandra) ; [email protected]; 
[email protected]
Subject: Re: ASCII support in z/OS

On 07/27/2016 09:18 AM, John Goodyear wrote:
> While it is valuable to get ASCII support for PERL on z/OS for reasons 
> such as git, I think other z/OS PERL users will have similar issues 
> that Sandra has voiced. Not everyone is reading/writing to Unix files 
> on z/OS, so chtag wouldn't help. Even if chtag is beneficial, it means 
> changing scripts/procedures to accommodate the new behavior. Also, if 
> the new PERL would wants to generate ASCII output by default, there is 
> further modification to scripts ect... to tell it to generate EBCDIC
>
> It seems the best solution from a usability standpoint is to be able 
> to build PERL so that it works on z/OS as before, or build it so that 
> it assumes the new behavior you are targeting to support git and other 
> software with PERL dependencies.
>
>
> Regards,
>
> John Goodyear
> z Systems Analytics zChampion
> WSC z Systems Applied Technologies
> Herndon, VA
> [email protected]

I agree with John about the need to continue to support the 1047-based perl.

I suspect that it won't be too hard to get a Perl working in ASCII mode. 
  If you can figure out a way to get the hints file to work on both styles, 
that would be preferable, as a bunch of system information in it is applicable 
to the underlying operating system, and having two files would invite one 
getting updated and forgetting the other.

Note that the perl Encode module can be used to translate to/from a data file 
in many many character sets/code pages to what perl is expecting. 
There are bugs with it on z/OS that I have not yet addressed, however.

If I recall correctly, though, the ASCII/EBCDIC switch is not easily changeable 
per process or even per user.  I thought it was an everything on the machine or 
nothing type of deal, which, if so, is problematic. 
Hopefully, I'm wrong.
>
> Inactive hide details for Yaroslav Kuzmin ---07/27/2016 08:51:20 
> AM---The main problem, obtain new tools to z/OS. tools is verYaroslav 
> Kuzmin ---07/27/2016 08:51:20 AM---The main problem, obtain new tools 
> to z/OS. tools is very outdated on USS z/OS. This will leave the
>
> From: Yaroslav Kuzmin 
> To: "[email protected]" , 
> "[email protected]" 
> Cc: "[email protected]" 
> Date: 07/27/2016 08:51 AM
> Subject: Re: ASCII support in z/OS
>
> --
> --
>
>
>
> 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: [email protected]
> Web: www.rocketsoftware.com
>
> В Ср., 27/07/2016 в 12:30 +, 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 - [email protected] Manage Your Subscription 
> Preferences - 
> http://info.rocketsoftware.com/GlobalSubscriptionManagementEmailFooter
> _SubscriptionCenter.html Privacy Policy - 
> http://www.rocketsoft

Re: ASCII support in z/OS

2016-08-02 Thread Karl Williamson

On 07/27/2016 09:18 AM, John Goodyear wrote:

While it is valuable to get ASCII support for PERL on z/OS for reasons
such as git, I think other z/OS PERL users will have similar issues that
Sandra has voiced. Not everyone is reading/writing to Unix files on
z/OS, so chtag wouldn't help. Even if chtag is beneficial, it means
changing scripts/procedures to accommodate the new behavior. Also, if
the new PERL would wants to generate ASCII output by default, there is
further modification to scripts ect... to tell it to generate EBCDIC

It seems the best solution from a usability standpoint is to be able to
build PERL so that it works on z/OS as before, or build it so that it
assumes the new behavior you are targeting to support git and other
software with PERL dependencies.


Regards,

John Goodyear
z Systems Analytics zChampion
WSC z Systems Applied Technologies
Herndon, VA
[email protected]


I agree with John about the need to continue to support the 1047-based 
perl.


I suspect that it won't be too hard to get a Perl working in ASCII mode. 
 If you can figure out a way to get the hints file to work on both 
styles, that would be preferable, as a bunch of system information in it 
is applicable to the underlying operating system, and having two files 
would invite one getting updated and forgetting the other.


Note that the perl Encode module can be used to translate to/from a data 
file in many many character sets/code pages to what perl is expecting. 
There are bugs with it on z/OS that I have not yet addressed, however.


If I recall correctly, though, the ASCII/EBCDIC switch is not easily 
changeable per process or even per user.  I thought it was an everything 
on the machine or nothing type of deal, which, if so, is problematic. 
Hopefully, I'm wrong.


Inactive hide details for Yaroslav Kuzmin ---07/27/2016 08:51:20
AM---The main problem, obtain new tools to z/OS. tools is verYaroslav
Kuzmin ---07/27/2016 08:51:20 AM---The main problem, obtain new tools to
z/OS. tools is very outdated on USS z/OS. This will leave the

From: Yaroslav Kuzmin 
To: "[email protected]" ,
"[email protected]" 
Cc: "[email protected]" 
Date: 07/27/2016 08:51 AM
Subject: Re: ASCII support in z/OS





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: [email protected]
Web: www.rocketsoftware.com

В Ср., 27/07/2016 в 12:30 +, 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 – [email protected]
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.







RE: ASCII support in z/OS

2016-07-27 Thread 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



-Original Message-
From: Yaroslav Kuzmin [mailto:[email protected]] 
Sent: Wednesday, July 27, 2016 7:57 AM
To: Carroll, Sandra E (Sandra) ; [email protected]
Cc: [email protected]
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  encoding  using tool (chtag -t -c IBM-1047 
 )

--

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: [email protected]
Web: www.rocketsoftware.com

В Вт., 26/07/2016 в 11:51 +, 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:[email protected]]
> Sent: Tuesday, July 26, 2016 7:44 AM
> To: [email protected]
> Cc: [email protected]
> 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 
> var

RE: ASCII support in z/OS

2016-07-27 Thread Carroll, Sandra E (Sandra)
I hope I'm understanding you on this.

Users of perl on z/OS, work almost exclusively in EBCDIC.
I understand from a porting Point of view.  However if fixing a porting issue 
introduces to USS (OMVS) that our files are ASCII encoded.
I do not believe you'll find many users who will find that acceptable.   I do 
not find it acceptable myself.

I am talking purely from the end user POV,   ascii encoding is useless to many 
if not all of us.  If it introduces the need for us to chtag files so we can 
encode them basic to EBCDIC the way they should have been encoded by default. 
The overhead of doing work on zOS jumps and the value of perl goes down.

Remember,  we don't exclusively work in OMVS.   Most of what we'll do is z/OS 
datasets   those have no CHTAG option.  
Coping to USS is often not an option either due to size or 
confidentiality/integrity of data especially in the financial industry.

That said, what perl does internally, I don’t' care,   what perl does to files 
and datasets I do care very much.
A file with no chtag should be read as EBCDIC
A file with a chtag of ISO-885901 should be read as ASCII.


Sandra


-Original Message-
From: Yaroslav Kuzmin [mailto:[email protected]] 
Sent: Wednesday, July 27, 2016 8:51 AM
To: Carroll, Sandra E (Sandra) ; [email protected]
Cc: [email protected]
Subject: Re: ASCII support in z/OS

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: [email protected]
Web: www.rocketsoftware.com

В Ср., 27/07/2016 в 12:30 +, 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 – 
[email protected] 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.


Re: ASCII support in z/OS

2016-07-27 Thread John Goodyear
While it is valuable to get ASCII support for PERL on z/OS for reasons such
as git, I think other z/OS PERL users will have similar issues that Sandra
has voiced.Not everyone is reading/writing to Unix files on z/OS, so
chtag wouldn't help.  Even if chtag is beneficial, it means changing
scripts/procedures to accommodate the new behavior.   Also, if the new PERL
would wants to generate ASCII output by default, there is further
modification to scripts ect... to tell it to generate EBCDIC

It seems the best solution from a usability standpoint is to be able to
build PERL so that it works on z/OS as before, or build it so that it
assumes the new behavior you are targeting to support git and other
software with PERL dependencies.


Regards,

John Goodyear
z Systems Analytics zChampion
WSC  z Systems Applied Technologies
Herndon, VA
[email protected]



From:   Yaroslav Kuzmin 
To: "[email protected]" ,
"[email protected]" 
Cc: "[email protected]" 
Date:   07/27/2016 08:51 AM
Subject:Re: ASCII support in z/OS



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: [email protected]
Web: www.rocketsoftware.com

В Ср., 27/07/2016 в 12:30 +, 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 �C [email protected]
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.




Re: ASCII support in z/OS

2016-07-27 Thread Yaroslav Kuzmin
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: [email protected]
Web: www.rocketsoftware.com

В Ср., 27/07/2016 в 12:30 +, 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 – [email protected]
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.


Re: ASCII support in z/OS

2016-07-27 Thread Yaroslav Kuzmin
Hi Carroll

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

--

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: [email protected]
Web: www.rocketsoftware.com

В Вт., 26/07/2016 в 11:51 +, 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:[email protected]]
> Sent: Tuesday, July 26, 2016 7:44 AM
> To: [email protected]
> Cc: [email protected]
> 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.zos.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/enhascii.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 

RE: ASCII support in z/OS

2016-07-26 Thread John Alvord
Just a side note... IBM Tivoli Monitoring has some SQL type tables with
mixed ASCII and EBCDIC columns. Really had to grind some Perl logic to dump
the data.

John Alvord

On Jul 26, 2016 6:32 AM, "Carroll, Sandra E (Sandra)" <
[email protected]> wrote:

> 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:[email protected]]
> Sent: Tuesday, July 26, 2016 7:44 AM
> To: [email protected]
> Cc: [email protected]
> 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://www .
> 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.zos.v2r2.cbcpx01/cbc
> 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/SSLT
> 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/enhascii.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, 

RE: ASCII support in z/OS

2016-07-26 Thread 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:[email protected]] 
Sent: Tuesday, July 26, 2016 7:44 AM
To: [email protected]
Cc: [email protected]
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://www 
.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.zos.v2r2.cbcpx01/cbc
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/SSLT
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/enhascii.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: [email protected]
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 – 
[email protected] Manage Your Subscription Preferences -