[SOLVED] Looking for a linux ISPF editor, preferably ubuntu

Tem2 · 10-14-2020, 12:20 PM

Does anybody know if there is an ISPF editor for ubuntu or any other linux distro? I'm an old mainframer and I miss editing files as records as opposed to bytes.

I used to have a dos version 20 years ago, so I'm hoping that kind of text editor is still available.

Thanks!

pan64 · 10-14-2020, 01:31 PM

most probably you found this already: https://github.com/daniel64/lspf

Tem2 · 10-14-2020, 02:49 PM

Quote:

Originally Posted by pan64

most probably you found this already: https://github.com/daniel64/lspf

I saw this, but I don't know how to install it. I'm used to simple install commands like apt install [app name], or dpkg somefile.deb

Here are the files that I downloaded from that github page. Part of the description is "Open source Linux version of IBM's z/OS ISPF Dialogue Manager written in C++"

I'm guessing that this is the source code which needs to be compiled.

I don't know where to begin. I thought maybe somebody knew of another alternative. Or can anyone point me in the direction where to find documentation for the procedure to compile these files.

Thanks!

Code:

master@master-Latitude-E6440:~/Downloads/ispf$ tree
.
└── lspf-master
    ├── doc
    │** ├── Notes
    │** ├── Panels
    │** ├── Pools
    │** ├── Services
    │** └── Variables
    ├── INSTALL
    ├── LICENSE
    ├── mlib
    │** ├── DLGT01
    │** ├── FLST01
    │** ├── MAIN01
    │** ├── PBRO01
    │** ├── PEDM01
    │** ├── PEDT01
    │** ├── PPSP01
    │** ├── PSYE01
    │** ├── PSYE02
    │** ├── PSYE03
    │** ├── PSYE04
    │** ├── PSYS01
    │** └── PSYZ00
    ├── plib
    │** ├── help
    │** │** ├── HEDIT01
    │** │** ├── HEDITK1
    │** │** ├── HFLST01
    │** │** ├── HFLST02
    │** │** ├── HPMAIN1
    │** │** ├── HPSP01A
    │** │** ├── HPSPF01
    │** │** └── HPSPF02
    │** ├── HLP_PDC
    │** ├── ISRERROR
    │** ├── PBRO01A1
    │** ├── PBRO01A2
    │** ├── PCMD0A
    │** ├── PCMD0B
    │** ├── PCMD0E
    │** ├── PDLGTST1
    │** ├── PDLGTST2
    │** ├── PDLGTST3
    │** ├── PDLGTST5
    │** ├── PEDIT011
    │** ├── PEDIT012
    │** ├── PEDIT013
    │** ├── PEDIT014
    │** ├── PEDIT015
    │** ├── PEDIT016
    │** ├── PEDIT017
    │** ├── PEDIT018
    │** ├── PEDIT019
    │** ├── PEDIT01A
    │** ├── PEDIT01B
    │** ├── PEDIT01C
    │** ├── PEDIT01D
    │** ├── PEDIT01E
    │** ├── PEDIT01F
    │** ├── PFLST0A1
    │** ├── PFLST0A2
    │** ├── PFLST0A3
    │** ├── PFLST0A4
    │** ├── PFLST0A5
    │** ├── PFLST0A6
    │** ├── PFLST0A7
    │** ├── PFLST0A8
    │** ├── PFLST0A9
    │** ├── PLRFLST1
    │** ├── PLRFLST2
    │** ├── PLRFLST3
    │** ├── PLRFLST4
    │** ├── PLRFLST5
    │** ├── PLRFLST6
    │** ├── PLRFLST7
    │** ├── PMAINP01
    │** ├── PMAINP02
    │** ├── PPRUN01
    │** ├── PPSET0A
    │** ├── PPSP01AC
    │** ├── PPSP01AD
    │** ├── PPSP01AK
    │** ├── PPSP01AL
    │** ├── PPSP01AP
    │** ├── PPSP01AV
    │** ├── PPSP01CD
    │** ├── PPSP01CG
    │** ├── PPSP01CL
    │** ├── PPSP01CR
    │** ├── PPSP01CT
    │** ├── PPSP01FL
    │** ├── PPSP01GO
    │** ├── PPSP01K1
    │** ├── PPSP01K2
    │** ├── PPSP01K3
    │** ├── PPSP01K4
    │** ├── PPSP01K5
    │** ├── PPSP01K6
    │** ├── PPSP01K7
    │** ├── PPSP01LD
    │** ├── PPSP01ML
    │** ├── PPSP01O1
    │** ├── PPSP01TD
    │** ├── PPSP01TK
    │** ├── PPSP01UP
    │** ├── PPSUTIL1
    │** ├── PPTEST01
    │** ├── PSYSER1
    │** ├── PSYSER2
    │** ├── PSYSER3
    │** ├── PTEST01A
    │** ├── PTEST01B
    │** ├── PTEST01C
    │** ├── PTEST01D
    │** ├── PTEST01E
    │** ├── PTEST01F
    │** ├── PTUTORA1
    │** ├── REXERROR
    │** ├── RFL_PDC
    │** ├── RFS_PDC
    │** └── STD_PDC
    ├── README.md
    ├── rexx
    │** ├── cmds
    │** ├── cmdtab1
    │** ├── dcon
    │** ├── edittab1
    │** ├── edrecov
    │** ├── emac
    │** ├── ishell
    │** ├── keygen
    │** ├── oshell
    │** ├── porexx2
    │** ├── porexx3
    │** ├── porexx5
    │** ├── posline
    │** ├── runemac
    │** ├── setdest
    │** ├── showmsg
    │** ├── submit
    │** ├── tabsopen
    │** ├── time
    │** └── zapplid
    ├── src
    │** ├── Apps
    │** │** ├── compapps
    │** │** ├── eHilight.cpp
    │** │** ├── eHilight.h
    │** │** ├── PBRO01A.cpp
    │** │** ├── PBRO01A.h
    │** │** ├── PCMD0A.cpp
    │** │** ├── PCMD0A.h
    │** │** ├── PCMD0B.cpp
    │** │** ├── PCMD0B.h
    │** │** ├── PDLGTST.cpp
    │** │** ├── PDLGTST.h
    │** │** ├── PDPANLA.cpp
    │** │** ├── PDPANLA.h
    │** │** ├── PEDIT01.cpp
    │** │** ├── PEDIT01.h
    │** │** ├── PEDRXM1.cpp
    │** │** ├── PEDRXM1.h
    │** │** ├── PFLST0A.cpp
    │** │** ├── PFLST0A.h
    │** │** ├── PLRFLST1.cpp
    │** │** ├── PLRFLST1.h
    │** │** ├── PMAIN0A.cpp
    │** │** ├── PMAIN0A.h
    │** │** ├── POREXX1.cpp
    │** │** ├── POREXX1.h
    │** │** ├── PPSP01A.cpp
    │** │** ├── PPSP01A.h
    │** │** ├── PSHELL0.cpp
    │** │** ├── PSHELL0.h
    │** │** ├── PTEST01.cpp
    │** │** ├── PTEST01.h
    │** │** ├── PTUTORA.cpp
    │** │** └── PTUTORA.h
    │** ├── classes.cpp
    │** ├── classes.h
    │** ├── colours.h
    │** ├── comp1
    │** ├── compsetup
    │** ├── ispexeci.cpp
    │** ├── lspf.cpp
    │** ├── lspf.h
    │** ├── pApplication.cpp
    │** ├── pApplication.h
    │** ├── pLScreen.cpp
    │** ├── pLScreen.h
    │** ├── pPanel1.cpp
    │** ├── pPanel2.cpp
    │** ├── pPanel.h
    │** ├── pTable.cpp
    │** ├── pTable.h
    │** ├── pVPOOL.cpp
    │** ├── pVPOOL.h
    │** ├── pWidgets.cpp
    │** ├── pWidgets.h
    │** ├── setup.cpp
    │** ├── utilities.cpp
    │** └── utilities.h
    ├── tlib
    │** └── ISRKEYP
    └── tools
        └── docker
            ├── build.sh
            ├── copypaths.sh
            ├── Dockerfile
            └── mkdirs.sh

11 directories, 199 files
master@master-Latitude-E6440:~/Downloads/ispf$

ondoho · 10-14-2020, 03:44 PM

^ basically, you want to read the INSTALL file and take it from there.

sgosnell · 10-14-2020, 05:56 PM

Also read the README.md file. Those two should get you started.

Tem2 · 10-14-2020, 06:28 PM

Quote:

Originally Posted by ondoho

^ basically, you want to read the INSTALL file and take it from there.

I don't suppose you could walk me through the INSTALL file?

Here is an excerpt: MY COMMENTS ARE IN RED

Docker:
-------
There is a docker build in directory tools/docker kindly provided by Rene Jansen.
This will download and install both ooRexx and lspf.

THIS SOUNDS LIKE WHAT I'M LOOKING FOR.

Boost and ncurses required to compile lspf.cpp.

I INSTALLED BOOST AND NCURSES.

DIRECTORY OF TOOLS/DOCKER:

Code:

/home/master/ispf/lspf-master/tools/docker> ls
build.sh  copypaths.sh  Dockerfile  mkdirs.sh

MY NEXT STEP WAS TO MAKE THE .SH FILES EXECUTABLE

Code:

/home/master/ispf/lspf-master/tools/docker> ls
build.sh  copypaths.sh  Dockerfile  mkdirs.sh
/home/master/ispf/lspf-master/tools/docker> chmod +x build.sh
/home/master/ispf/lspf-master/tools/docker> chmod +x copypaths.sh
/home/master/ispf/lspf-master/tools/docker> chmod +x mkdirs.sh

THEN I TRIED THE BUILD.SH COMMAND:

Code:

/home/master/ispf/lspf-master/tools/docker> sudo ./build.sh
[sudo] password for master: 
./build.sh: 1: ./build.sh: docker: not found

IT DIDN'T LIKE THE DOCKER COMMAND. SO I DID A SEARCH FOR WHERE DOCKER SHOWS UP IN THE WHOLE TREE:

Code:

/home/master/ispf> tree -d
.
└── lspf-master
    ├── doc
    ├── mlib
    ├── plib
    │** └── help
    ├── rexx
    ├── src
    │** └── Apps
    ├── tlib
    └── tools
        └── docker

11 directories
/home/master/ispf>  grep -R 'docker' 
lspf-master/INSTALL:There is a docker build in directory tools/docker kindly provided by Rene Jansen.
lspf-master/tools/docker/build.sh:docker build . -t lspf:test
/home/master/ispf>

I CAN'T TELL WHERE THE DOCKER COMMAND GETS EXECUTED. I WAS HOPING THE GREP WOULD SHOW WHAT IS SUPPOSED TO BE TRIGGERED BY THE BUILD.SH FILE, BUT THERE ARE NO MORE REFERENCES.

I AM AT A LOSS FOR WHAT TO DO NEXT. I REALIZE THAT I AM ASKING FOR A LOT, BUT IF ANYONE CAN WALK ME THROUGH THIS I WOULD GREATLY APPRECIATE IT. I APOLOGIZE FOR THE UPPERCASE (OR ANY OTHER BREACH OF FORUM PROTOCOL). JUST TRYING TO MAKE MY COMMENTS READABLE.

THIS IS MORE OF THE INSTALL FILE RELATED TO THE DOCKER BUILD.

Environmental variables HOME and LOGNAME are required to be setup. lspf will fail to start without them.
SHELL is also used, but not a requirement. .SHELL command will not work if this variable is not set.

OOREXX required for POREXX1.cpp (OOREXX interface module for writing lspf applications in REXX) and PEDRXM1.cpp (edit
macro interface module for writing edit macros in REXX).

file required for PBRO01A.cpp as it is linked with -lmagic.
grep required for PFLST0A.cpp for the SRCHFOR command.

Run lspf in a terminal.

Works with:
linux 5.5.4
gcc 9.2.1
ncurses 6.2
boost 1.72.0

syg00 · 10-14-2020, 06:31 PM

I gave up looking years ago - I really missed things like block exclude.
I looked at adding some support to the original nedit, but it was a bit of a pain, especially Motif, so I decided to move on.

pan64 · 10-15-2020, 01:58 AM

you do not need to use bold, red and other tricks to make your post more readable.
Otherwise it looks like you need to install docker.

Tem2 · 10-15-2020, 03:06 AM

Quote:

Originally Posted by pan64

you do not need to use bold, red and other tricks to make your post more readable.
Otherwise it looks like you need to install docker.

Thanks for the protocol tips. I installed docker and here is the result from executing build.sh:

Code:

 >docker $sudo ./build.sh
Sending build context to Docker daemon  5.632kB
Step 1/29 : FROM arch-devel
pull access denied for arch-devel, repository does not exist or may require 'docker login'

Here is the code in Dockerfile. It looks like it doesn't like the first line. I don't see any references anywhere to 'arch-devel' in the grep that follows:

Code:

FROM arch-devel
LABEL maintainer="rvjansen@xs4all.nl"
WORKDIR /
RUN svn co https://svn.code.sf.net/p/oorexx/code-0/main/trunk oorexx-code-0
WORKDIR /oorexx-code-0
RUN cmake .
RUN make install
WORKDIR /
RUN git clone https://github.com/daniel64/lspf.git
ADD mkdirs.sh /lspf
WORKDIR /lspf
RUN chmod +x mkdirs.sh
RUN /lspf/mkdirs.sh
WORKDIR /lspf/src
# Copy the current directory contents into the container at /app
ADD copypaths.sh /lspf
RUN sed -i 's/#define ZSYSPATH        "\/home\/daniel\/lspf"/#define ZSYSPATH        "\/root\/.lspf"/g' lspf.h
RUN ./compsetup
RUN ./setup
RUN ./comp1
WORKDIR /lspf/src/Apps
RUN    ./compapps
WORKDIR /lspf/
RUN    chmod +x copypaths.sh
RUN    ./copypaths.sh

# Define environment variables
ENV HOME=/root
ENV LOGNAME=root
ENV SHELL=/usr/sbin/bash
ENV PATH=/lspf/src:$PATH

# Default command  when the container launches
CMD bash

Here is my grep looking for arch-devel in this directory tree:

Code:

 >ispf $tree -d
.
└── lspf-master
    ├── doc
    ├── mlib
    ├── plib
    │** └── help
    ├── rexx
    ├── src
    │** └── Apps
    ├── tlib
    └── tools
        └── docker

11 directories
 >ispf $grep -R 'arch-devel'
lspf-master/tools/docker/Dockerfile:FROM arch-devel

Here is the INSTALL file instructions:

==================================================================================================== ========

Docker:
-------
There is a docker build in directory tools/docker kindly provided by Rene Jansen.
This will download and install both ooRexx and lspf.

Boost and ncurses required to compile lspf.cpp.

Environmental variables HOME and LOGNAME are required to be setup. lspf will fail to start without them.
SHELL is also used, but not a requirement. .SHELL command will not work if this variable is not set.

OOREXX required for POREXX1.cpp (OOREXX interface module for writing lspf applications in REXX) and PEDRXM1.cpp (edit
macro interface module for writing edit macros in REXX).

file required for PBRO01A.cpp as it is linked with -lmagic.
grep required for PFLST0A.cpp for the SRCHFOR command.

Run lspf in a terminal.

Works with:
linux 5.5.4
gcc 9.2.1
ncurses 6.2
boost 1.72.0

On upgrade:
-----------

Recompile application programs in case header files have changed (use applications that come with that
version of lspf).

Recompile and rerun setup in case variables have been added to the ISPS profile. You will get segfaults
if required variables are missing.

==================================================================

What am I missing?

And many thanks for the help!

pan64 · 10-15-2020, 04:15 AM

I don't think you need sudo for build.sh. But that is more or less irrelevant, because:

Quote:

pull access denied for arch-devel, repository does not exist or may require 'docker login'

this is the way to create that docker image if you cannot download it: https://github.com/binhex/arch-devel

Probably would be better to build it without docker....

it started to be utterly complicated.

Tem2 · 10-15-2020, 01:19 PM

I think it is time to give up on this. Many thanks again for all of your help.

dje64 · 11-27-2020, 04:27 AM

The docker image is only really for systems where you cannot compile the programs natively, eg Mac. For UBUNTU, lspf compiles without problems once the relevant libraries have been installed so it is better to follow the MANUAL install section in the INSTALL documentation and ignore the DOCKER section.

The easiest way to get this done is to move all the source in the lspf/src/ directory up one level and use the compsetup, comp1 and compapps scripts to compile everything.

djw · 12-29-2020, 09:12 PM

Can you advise what the compile error for lspf is here? I too would like to get lspf going on CentOS7

[root@localhost lspf-master]# ./compsetup

/tmp/cc7tFQzG.o: In function `boost::filesystem::copy_file(boost::filesystem:

ath const&, boost::filesystem:

ath const&, boost::filesystem::copy_option, boost::system::error_code&)':
setup.cpp

.text._ZN5boost10filesystem9copy_fileERKNS0_4pathES3_NS0_11copy_optionERNS_6system10error _codeE[_ZN5boost10filesystem9copy_fileERKNS0_4pathES3_NS0_11copy_optionERNS_6system10error_codeE]+0x2a): undefined reference to `boost::filesystem::detail::copy_file(boost::filesystem:

ath const&, boost::filesystem:

ath const&, boost::filesystem::copy_option, boost::system::error_code*)'
collect2: error: ld returned 1 exit status

pan64 · 12-30-2020, 10:00 AM

Quote:

Originally Posted by djw

Can you advise what the compile error for lspf is here? I too would like to get lspf going on CentOS7

Please do not hide other threads. Click on report and ask moderators to move this post.

Also please use code tags, otherwise your post is [more or less] unreadable.

dje64 · 12-30-2020, 11:17 AM

This isn't a compile error but a link error. Check you have all the libraries installed as mentioned in the INSTALL file at the required level, especially boost_filesystem (it may be packaged differently on centOS).