Re: 7.2 Python PTFs FYI

Justin

You have hit on the strategy the IBM i open source team is using - since 5733-OPS is an official licensed product, they can and do distribute fixes in a way that is familiar to IBM i folks - as you said, to "bless" them. That is a stated strategy.

As to seeing what is there - is they are SAVFs, one can list them in PDM, then put a 5 on the first one, press F13 and then Enter and you'll see what is in each one.

That's pretty easy - there are programmatic ways, too.

Regards
Vern

On 1/11/2016 2:13 PM, Justin Dearing wrote:

Buck,

Is it possible a the PTFs were all python pip modules? IBM might have
wanted to bless a hundred modules or so as official by makingthem PTFs
instead of fhaving you install via "pip install" Most of the linux distos
do that for many perl and python modules.

Is there an easy way to go throughthe PTFs and list the stream files
installing them will create on the IFS?

Justin

On Mon, Jan 11, 2016 at 2:49 PM Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

The developerWorks wiki for Python has a new page for Python PTFs:

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/page/Python%20PTFs

I see that there are some new ones, SI58191 - SI58195. So I ordered
them: SNDPTFORD PTFID((SI58191) (SI58192) (SI58193) (SI58194) (SI58195))

I was a bit surprised when I saw what looked like hundreds of PTFs for
V7R1M0 to be pulled down. When the SNDPTFORD had completed, I counted
the *SAVF objects which have V7R1M0 in the description and there are
more than 600 of them!

DSPPTFAPYI only shows the 5 PTFs I ordered plus a pre-req, SI58278.
LODPTF and APYPTF seemed to go fine. So I deleted all those 7.1 save
files. There were some for 5770-999, 5770-SS1, 5770-SC1, and 5770-SC1.

The LPAR seems fine but it sure is curious that it downloaded all that
7.1 stuff. CALL QP2TERM, python3 --version responds with 'Python
3.4.2', which is exactly the same as the LPAR without those PTFs so I'm
not sure I really got anything accomplished.

--
--buck

Visit wiki.midrange.com and register for an account. Edit a page that
helps you, and because it's public, you'll help someone else, too!

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.