Interim fix file components

Edit online

The following interim fix control-file components are related to specific files. The maximum number of interim fix files for each interim fix that the epkg and emgr commands support is 200.

EFIX_FILE_NUM

Number of the given file (1 - 200).

SHIP_FILE

Local file location that the epkg command is archiving into the interim fix package. Specify either an absolute or relative path to this file. The ship file is the interim fix that is delivered.

TARGET_FILE

Target file location where the SHIP_FILE is installed. This location is located on the system where the interim fix package is installed. Specify the absolute path to this file. If this file is part of a registered package, such as an RPM or installp package, you must specify the tracked location.

INSTALLER

This variable represents the type of installer that owns the interim fix package. Valid integer choices are as follows:

1 Tracked by installp

2 Tracked by RPM

3 Tracked by ISMP

4 Tracked by another installer

5 New file that will be tracked by installp

6 New file that will be tracked by RPM

7 New file that will be tracked by ISMP

8 New file that will be tracked by another installer

9 Not tracked by any installer

TYPE

This is the type of file that is being installed. The valid choices are as follows:

1 Standard file or executable file

2 Library or archive member

An example of TYPE 1 is the /usr/bin/ls file or the /usr/bin/rm file. An example of TYPE 2 is the shr.o archive member as a member of the libc.a library.

ACL

Specifies the access attributes (mode and ownership) for a given file. If this attribute is set to DEFAULT, the emgr command maintains the current permissions of the file to be replaced. However, if the target file is a new file or the user wants to specify permissions using the -v flag, the ACL attribute can be entered with the Owner:Group:OctalModes syntax, similar to the following:

 ACL= root:system:555

AR_MEM

Specifies the name of the archive member. This option is only valid if TYPE=2. In this case, SHIP_FILE represents the local location of the archive member that is being shipped, TARGET_FILE represents the target archive, and ACL applies to the archive member. For example, the following attributes ship the myshr.o local file to the shr.o member in the /usr/ccs/lib/libc.a target archive:

TYPE=2
SHIP_FILE=/home/myshr.o
TARGET_FILE=/usr/ccs/lib/libc.a
AR_MEM=shr.o