Re: [ansible-devel] Support for IBM z/OS on ansible nodes

2019-01-22 Thread Aaron Surty
Pipelining is not required for me because I am able to execute untagged ASCII python modules, however, it seems that others are not. I'm still scratching my head trying to determine what is different for me that makes that work. On Mon., Jan. 21, 2019, 9:46 p.m. Toshio Kuratomi On Mon, Jan 21, 2

Re: [ansible-devel] Support for IBM z/OS on ansible nodes

2019-01-21 Thread Toshio Kuratomi
On Mon, Jan 21, 2019 at 9:41 AM Vitezslav Vit Vlcek wrote: > > I can summarize outcome of my research. Could you point me to right direction? > > I found faq for windows > https://github.com/ansible/ansible/blob/d1c0b7a597944baed20af28c8833d51451791f69/docs/docsite/rst/user_guide/windows_faq.rst

Re: [ansible-devel] Support for IBM z/OS on ansible nodes

2019-01-21 Thread Toshio Kuratomi
On Mon, Jan 21, 2019 at 9:05 AM Aaron Surty wrote: > > It seems like Vitek's issue of executing untagged ASCII python modules on > z/OS is not unique. I'm going to try and investigate why that works for me > and not others, but in the meantime perhaps there should be a blurb in the > FAQ that

Re: [ansible-devel] Support for IBM z/OS on ansible nodes

2019-01-21 Thread Aaron Surty
It seems like Vitek's issue of executing untagged ASCII python modules on z/OS is not unique. I'm going to try and investigate why that works for me and not others, but in the meantime perhaps there should be a blurb in the FAQ that suggests enabling pipelining for z/OS? See here for more deta

Re: [ansible-devel] Support for IBM z/OS on ansible nodes

2019-01-21 Thread Vitezslav Vit Vlcek
For sake of record. I had offline discussion with Surty he proposed activate pipelining (pipelining = True in /etc/ansible/ansible.cfg). This resolves my problems with encoding therefore code change is not needed. Ansible modules are in proper encoding on z/OS and copy module transfers files in bin

Re: [ansible-devel] Support for IBM z/OS on ansible nodes

2019-01-21 Thread Aaron Surty
Hi Vitek, You should not need to tag the python modules after transfer. Sorry I should have mentioned that executing python modules encoded in both ASCII and EBCDIC that are untagged also works. There must be some sort of mechanism that first looks at the tag and if that does not exist then it t

Re: [ansible-devel] Support for IBM z/OS on ansible nodes

2019-01-20 Thread Vitezslav Vit Vlcek
Hi Aaron, how do you tag python modules after they were transferred from windows driving workstation to zos node? Vitek po 21. 1. 2019 4:02 odesílatel Aaron Surty napsal: > Hi Vitek, > > I don't have a problem executing python modules encoded as ASCII on z/OS. > The only time I run into an issue

Re: [ansible-devel] Support for IBM z/OS on ansible nodes

2019-01-20 Thread Aaron Surty
Hi Vitek, I don't have a problem executing python modules encoded as ASCII on z/OS. The only time I run into an issue is if the python module's code page is ASCII but the module is tagged as EBCDIC. I am running version 2.7.13, however, I believe Rocket's port of python 3.6.1 should have the

Re: [ansible-devel] Support for IBM z/OS on ansible nodes

2019-01-18 Thread Vitezslav Vit Vlcek
I'm running Python 3.6.1 (heads/v3.6.1-anaconda:7960479, Aug 25 2017, 14:12:10) [C] on zos You don't have to declare full/official support for z/OS. What I need for z/OS is an ascii ebcdic translation for ansible modules that is carried out by ssh server on z/OS when using scp or sftp in ascii

Re: [ansible-devel] Support for IBM z/OS on ansible nodes

2019-01-18 Thread James Tanner
Hi Vitek, I'm curious if you are using 2.7.13+ from rocketsoftware per our FAQ entry ... https://docs.ansible.com/ansible/devel/reference_appendices/faq.html#running-on-z-os The challenge for us is that we don't have testing infrastructure with EBCDIC to test against, so we're never able to full