IBM i PTF Guide, Volume 19, Numbers 33 And 34

August 30, 2017 Doug Bidwell

When I am distracted, I am costing my company money or one of my customers money, and the shortest path to a solution should be taken to get me back to focusing on the applications. Toward that end, I have developed the “15 Minute” rule: If I don’t have an answer or a direction on the problem in 15 minutes, I move it to the next level. This usually means someone in my circle of techs, but the same applies there. At 30 to 45 minutes after I am aware of the problem, I am usually fixing it or calling the last line of defense, which is the developers at IBM. I am a frequent user of support at IBM and usually find an answer with the techies there. (My 15 minute rule falls apart here, because I’m on IBM’s schedule at this point.) I use the IBM i PTF Guide as a tool to keep me abreast of the situation, and it a place where I check for answers to my problems in the first 15 minutes. Defective PTFs is one of the important checkpoints.

Defective PTFs that are new as of issue Number 33 are as follows:

My perspective on PTFs is that the development teams at IBM work with me and for me. They are part of my development team. They are there to help me over the rough spots and to keep me focused on the application side without distractions from the operating system and licensed internal code side. When I am distracted, I am costing my company money or one of my customers money, and the shortest path to a solution should be taken to get me back to focusing on the applications. Toward that end, I have developed the “15 Minute” rule: If I don’t have an answer or a direction on the problem in 15 minutes, I move it to the next level. This usually means someone in my circle of techs, but the same applies there. At 30 to 45 minutes after I am aware of the problem, I am usually fixing it or calling the last line of defense, which is the developers at IBM. I am a frequent user of support at IBM and usually find an answer with the techies there. (My 15 minute rule falls apart here, because I’m on IBM’s schedule at this point.) I use the IBM i PTF Guide as a tool to keep me abreast of the situation, and it a place where I check for answers to my problems in the first 15 minutes. Defective PTFs is one of the important checkpoints. Defective PTFs that are new as of issue Number 33 are as follows: CODE

16 Aug 2017 DEFECTIVE PTF: V7R3 MF63501
                           V7R2 MF63500   
                           V7R1 MF63499                                          
REASON DEFECTIVE: After applying the PTF, PCI card CCINs     
                   FC EN15, FC EN16, FC EN17, and FC EN18     
                   in dedicated SR-IOV mode may fail.         
RECOMMENDATION: Apply the fixing LIC PTF MF64002 for i 7.3.  
                 Apply the fixing LIC PTF MF64001 for i 7.2.  
                 Apply the fixing LIC PTF MF64000 for i 7.1.

In issue Number 34 of the IBM i PTF Guide, you will see that IBM has finally issued a new Security Group PTF for all releases. The pertinent PTFs are below: USE PRE CODING

SF99728 730 Group Security - level 17
  SI65336 - OSP-DNS/Refresh DNS BIND to fix CVE-2017-3142 and CVE-2017-3143
  SI65096 - OSP-Other Update Samba Support for IBM i PASE to 3.6.25e
  SI64751 - OSP-Other Update Samba Support for IBM i PASE to 3.6.25d
  SI64614 - OSP-DNS/Fix CVE-2017-3136 and CVE-2017-3137 for DNS bind
  SI63299 - Cloud-Init: Integrity changes

There are corresponding PTFs for release 7.2 and 7.1, see that group for details. Additionally, there are PTFs available for vulnerabilities not covered by the Group PTF: CODE2

Security Bulletin: Vulnerability CVE-2017-1000381 and CVE-2017-11499 in Node.js affects IBM i
Release 7.1, 7.2 & 7.3 (the same number PTF is applicable for all 3 OS releases):
  SI65482 5733OPS Option 5 (Node.js version 4.8.4) 
  SI65493 5733OPS Option 10 (Node.js version 6.11.2)

As always, we have an archive listing of all of the IBM i PTF Guide issues for the past several years in case you need to look back into the archive to see what is what:

In issue Number 34 of the IBM i PTF Guide, you will see that IBM has finally issued a new Security Group PTF for all releases. The pertinent PTFs are below:

SF99728 730 Group Security - level 17
  SI65336 - OSP-DNS/Refresh DNS BIND to fix CVE-2017-3142 and CVE-2017-3143
  SI65096 - OSP-Other Update Samba Support for IBM i PASE to 3.6.25e
  SI64751 - OSP-Other Update Samba Support for IBM i PASE to 3.6.25d
  SI64614 - OSP-DNS/Fix CVE-2017-3136 and CVE-2017-3137 for DNS bind
  SI63299 - Cloud-Init: Integrity changes

There are corresponding PTFs for release 7.2 and 7.1, see that group for details. Additionally, there are PTFs available for vulnerabilities not covered by the Group PTF:

Security Bulletin: Vulnerability CVE-2017-1000381 and CVE-2017-11499 in Node.js affects IBM i
Release 7.1, 7.2 & 7.3 (the same number PTF is applicable for all 3 OS releases):
  SI65482 5733OPS Option 5 (Node.js version 4.8.4) 
  SI65493 5733OPS Option 10 (Node.js version 6.11.2)

As always, we have an archive listing of all of the IBM i PTF Guide issues for the past several years in case you need to look back into the archive to see what is what:

IBM i PTF Guide, Volume 19, Numbers 33 And 34

Share this:

Share this:

Leave a Reply Cancel reply

This Issue Sponsored By

Table of Contents

Content archive

Recent Posts

Subscribe

Pages

Search