JAR replacements in PTFs

Just as replacements for JAR files can be delivered in an FMID, so can JAR file replacements be delivered in PTFs. Suppose that you decide to create a "level-set" PTF, which incorporates the updates from several previous APARs and PTFs. In this case, you want to replace the entire TicTacToe applet JAR file, rather then add or replace files within the archive.

You create the JAR file for the applet using the jar command as discussed previously and then package it as a ++JAR element in a PTF, as in the following example:

 
++PTF(UW87654).                                                      
++VER(Z038) FMID(fmid) SUP(UW12345 UW54321).                         
++JAR(ABCTTT) DISTLIB(AABCBIN) SYSLIB(SABCBIN)                       
     PARM(PATHMODE(0,6,4,4)) JARPARM(0M)                                
     LINK('../TicTacToe.jar')                                           
     SYMLINK('../../../../../usr/lib/TicTacToe.jar')                    
     SYMPATH('../../usr/lpp/abc/bin/TicTacToe.jar').

Notice this PTF supersedes both PTFs that supplied updates for the JAR file. Again, such relationships (either supersede or prerequisite) are required by SMP/E, because both PTFs provided updates for the JAR file contained in the current PTF.