Issues when using 3270

[lbdyck]

See these screen captures with annotations

[lbdyck]

Found the issue here - so do I need ncurses?

[IgorTodorovskiIBM]

Thanks @lbdyck , would it make sense to guard it like this?

if [ ! "${_BPX_TERMPATH-x}" = "OMVS" ]
  export TERM=xterm
 ...
fi

[lbdyck]

imho it would

[lbdyck]

I assume the test if it is not equal to OMVS then do the export

[IgorTodorovskiIBM]

Yep

[lbdyck]

I tried copy and paste and got this

/.env 29: .: FSUM7332 syntax error: got fi, expecting then

[lbdyck]

This worked

[IgorTodorovskiIBM]

oh yes, forgot the "; then" :) Thanks

[lbdyck]

Now I'm getting this on my work z/OS:

Comparing my .bootenv between work and the CBT system - I had removed different things.

this is what I have on the cbt that has no problems for p in meta curl git less perl bash diffutils findutils tar gzip bzip2 ncurses ; do
and this on my work system: for p in meta curl git less perl bash ncurses ; do

[IgorTodorovskiIBM]

A couple of questions:

• Did you pull in the latest ncurses? That changes TERMINFO to ASCII_TERMINFO (you'll also need to pull in less, git, etc if you did this)
• This happens after the above change? If TERM is set to dumb or some other value, does the less warning go away? Maybe we need to set TERM to legit value for OMVS

[lbdyck]

1. yes - it was a clean zopen-setup
2. yes

[lbdyck]

Test using a tn3270 and you should see it - unless it is just me :)

[lbdyck]

btw. my work system is z/OS 2.4 and the cbt system is z/OS 2.5

[lbdyck]

using the same .bootenv i still get the above error

[lbdyck]

Here is a word doc with the 2 environments - my work (bad) and cbt (good) in case you can see anything

envs.docx

[lbdyck]

Note: this problem does NOT occur accessing z/OS OMVS via ssh

[IgorTodorovskiIBM]

Hey Lionel, I'm not able to see the env content

[lbdyck]

Open the word doc and then click on the attachments and you can save them and view them in notepad or other text viewer.

[lbdyck]

I found the solution - see this:

[MikeFultonDev]

@IgorTodorovskiIBM i think you are rolling out a fix for this - can you point @lbdyck to the fix when it's available and then @lbdyck you can close this off?

[MikeFultonDev]

This is now working I believe. @lbdyck please open an issue if not.