vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi, So far, I have not found a way how to find out the following from within a pre_i script : a) If the fileset is that is currently being installed, is already installed b) If it is already installed, with what version It seems that as soon as the pre_i script is executed, the ODM (both product and lpp repositories) is already updated with the new version of the fileset. Hopefully anyone can help me out in this one. Thanks! Mark |
| |||
| huijstee@hotmail.com wrote: > Hi, > > So far, I have not found a way how to find out the following from > within a pre_i script : > > a) If the fileset is that is currently being installed, is already > installed > b) If it is already installed, with what version > > It seems that as soon as the pre_i script is executed, the ODM (both > product and lpp repositories) is already updated with the new version > of the fileset. > Hopefully anyone can help me out in this one. > > Thanks! > > > Mark Have you considered using the pre_rm script instead of pre_i for those tests? See the section titled 'Processing for the Apply Operation' at: http://publib.boulder.ibm.com/infoce...cNode=int_9268 and you will see that the pre_rm comes early in the processing order. And the section titled 'Optional Executable Files Contained in the liblpp.a File' at that same URL implies the pre_rm happens before the pre_i. Paul Landay |
| |||
| On Jan 11, 2:03 pm, huijs...@hotmail.com wrote: > Hi, > > So far, I have not found a way how to find out the following from > within a pre_i script : > > a) If the fileset is that is currently being installed, is already > installed > b) If it is already installed, with what version > What is the reason for that requirement ? regards Hajo |
| |||
| "Paul Landay" <landay@attglobal.net> wrote in message news:47876EDE.2000808@attglobal.net... > huijstee@hotmail.com wrote: > >> Hi, >> >> So far, I have not found a way how to find out the following from >> within a pre_i script : >> >> a) If the fileset is that is currently being installed, is already >> installed >> b) If it is already installed, with what version >> >> It seems that as soon as the pre_i script is executed, the ODM (both >> product and lpp repositories) is already updated with the new version >> of the fileset. >> Hopefully anyone can help me out in this one. >> >> Thanks! >> >> >> Mark > > Have you considered using the pre_rm script instead > of pre_i for those tests? See the section titled > 'Processing for the Apply Operation' at: > http://publib.boulder.ibm.com/infoce...cNode=int_9268 > and you will see that the pre_rm comes early in the > processing order. And the section titled > 'Optional Executable Files Contained in the liblpp.a File' > at that same URL implies the pre_rm happens before > the pre_i. > > Paul Landay Paul, You were right, the pre_rm is run before changing the ODM. From within the pre_rm script, I am able to figure out the version which will be updated. Thanks! Cheers! Mark |
| ||||
| "Hajo Ehlers" <service@metamodul.com> wrote in message news:4a8e2418-93a9-4f86-8879-69cd36b3888f@n20g2000hsh.googlegroups.com... > On Jan 11, 2:03 pm, huijs...@hotmail.com wrote: >> Hi, >> >> So far, I have not found a way how to find out the following from >> within a pre_i script : >> >> a) If the fileset is that is currently being installed, is already >> installed >> b) If it is already installed, with what version >> > > What is the reason for that requirement ? > > regards > Hajo Hajo, Some of my filesets have several steps to be performed which can take up to minutes. When updating, I want to be able to run only those steps in the configuration process that need to be executed. So only configuration steps of which I added/changed/fixed between the installed version and the one I installing, need to be run. For this reason, I need to be able to figure out the version of the installed component. Mark |