Previous topic |
Next topic |
Contents |
Index |
Contact z/OS |
Library |
PDF
JAR updates in PTFs SMP/E for z/OS User's Guide SA23-2277-01 |
|
Suppose some time after your FMID has been made available and is
being used, a defect is discovered (an APAR). The TicTacToe applet
requires a change because of the APAR. Specifically, you need to
add another image file (images/new.gif), and replace the class file
(TicTacToe.class) with an updated copy of the class file. Further,
suppose that the change team has placed the new image file and updated
class file in directories, as follows:
You can instruct SMP/E to add new files to a JAR file, and replace
files in an existing JAR file by using the ++JARUPD MCS. If files
TicTacToe.class and new.gif were to be packaged and archived together
in a JAR file of their own, then that file, in SMP/E terms, would
be considered a JAR update file. For example, given the preceding
directory structure for the new and updated files, the jar command
could be used to create the JAR update file as follows:
The resultant JAR file ABCTTT.jarupd would be packaged as a ++JARUPD
in a PTF as in the following example:
Suppose now another defect (APAR) is discovered against the TicTacToe
applet, and you must update the /audio/beep.au file within the archive.
Again, you can use the ++JARUPD MCS to describe an update to the
archive. Assuming the replacement audio file resides in a directory
as follows:
The following jar command could create the necessary JAR update:
The resulting JAR file ABCTTT.jarupd would be packaged as a ++JARUPD
in a PTF as in the following example:
Notice the second PTF has a prerequisite for the first PTF. Such a relationship is required by SMP/E because both PTFs update the same JAR file. |
Copyright IBM Corporation 1990, 2014
|