Yes, David makes a good point.
And from a non-sysadmin user perspective that *should* be the case.
I've encountered too many IBM Unix environments where "installed" did
not automatically render the package usable as a command. (That is,
executables found via un-augmented $PATH.)
There's a lot to like about their/usr/lpp scheme. (Chicory uses similar
trickery.) But someone's got to either modify/etc/profile (not
recommended) or sym-link the commands under/usr/bin (not recommended) or
under/usr/local/bin (prolly best).
On VM/CMS, *all* add-on produces get their own minidisk which must be
linked and accessed before the thing can be used. One wonders if IBM
simply decided that's how things should be: It's there if you need it
(after "install"), but we won't make it usable by default.
Just observing. Not complaining.
Here's another point which is easily missed: versioning.
The Python community made versioning a bigger deal when they deprecated
Python 2 a couple years ago. Too many existing scripts depend on Python
2, but Python 3 is the future.
Thankfully it's usually invoked as 'python3', but did you mean Python
3.12 or 3.11 when you entered that? Off the top of my head, I don't
remember how to differentiate under /usr/lpp, but with Chicory it's
/usr/opt/python-3.12/bin versus /usr/opt/python-3.11/bin. Works.
On 7/5/24 9:34 AM, David Crayford wrote:
If it’s not in your PATH there’s an argument to be made that it’s not properly
installed, even if the file system has been mounted. On this list there’s
probably very few folks who know how to setup a user profile in USS.
On 5 Jul 2024, at 21:26, Farley,
Peter<0000031df298a9da-dmarc-requ...@listserv.ua.edu> wrote:
True, if you use “type python3” it CAN find it, but the success of that
command depends on your $PATH already having the python directory listed in it.
If you don’t already know what the python3 directory is and have added it to
your $PATH, the “type” command will not find it.
Of course if your friendly (FSVO “friendly”) sysprog has already put that
directory into your $PATH via the /etc/profile script you are GTG.
Peter
From: IBM Mainframe Discussion List<IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of
MANCINI Frédéric (80)
Sent: Friday, July 5, 2024 8:52 AM
To:IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: About Python and REXX
Hello,
To check if Python is available in the cli environment, go into OMVS,
either from ISPF (TSO OMVS) or through a SSH connection (if the sshd
server is running), and do
type python
It should return the complete PATH to the python executable.
------------------------------------------------------------------------
*De :* [mailto:Thomas] <Berg>
<00000619bfe39560-dmarc-requ...@listserv.ua.edu<mailto:00000619bfe39560-dmarc-requ...@listserv.ua.edu>>
*Envoyé :* jeudi 4 juillet 2024 à 00:02
*Pour :*IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>
*Objet :* About Python and REXX
A question:
* How do I check if Python is installed/availible in an existing z/OS? (I
can't ask anyone for the moment due to an organisational mess at this site.)
* Regarding REXX:
- If performance is a priority and concern for the task I use a proper tool
delivered by IBM or third party vendor (the latter if portability is not
important).
- If a proper tool is not avalible or usable and performance is a priority etc
for the task I code a COBOL or assembler program. But I very seldom have had a
need to do that, at least the latest 20 years or so.
- If performance is NOT a priority I use REXX.
- I would use langs like Python if they are as easy and fast to code as REXX.
If not they are irrellevant for me. And here portability may probably be a
concern.
- I have never felt limited by REXX functionality in z/OS (other than regarding
performance sometimes, but then you can easily use tools from REXX!).
Thomas Berg
--
This message and any attachments are intended only for the use of the addressee
and may contain information that is privileged and confidential. If the reader
of the message is not the intended recipient or an authorized representative of
the intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication
in error, please notify us immediately by e-mail and delete the message and any
attachments from your system.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email tolists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email tolists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
