Patch-ID# 101432-02 Keywords: mandatory SunLink 8.0 BSC3270 stopbsc ASCII enterstr zsb newline Synopsis: SunLink BSC3270 8.0: Jumbo patch Date: Apr/21/94 Solaris Release: 2.1, 2.2, 2.3 SunOS Release: 5.1, 5.2, 5.3 Unbundled Product: SunLink BSC3270 Unbundled Release: 8.0 Relevant Architectures: sparc BugId's fixed with this patch: 1122891 1145905 1147412 1151201 1154760 1158980 1159424 Changes incorporated in this version: 1154760 1158980 1159424 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: SUNWbsccu/reloc/SUNWconn/bsc3270/stopbsc SUNWbscdr/root/kernel/drv/zsb SUNWbscdr/root/kernel/strmod/bsclm Problem Description: (Rev 01) 1122891: "bsclm_timer" system errors at console when test against an ASCII line BSC3270 8.0 does not support ASCII character set transmission on the line. 1145905: enterstr leavestr were removed from 1093 causing BSC3270 8.0 failure Entry points enterstr and leavestr were removed from Solaris 2.3 causing the BSC3270 8.0 installation process to fail in the zsb driver. 1147412: stopsna and stopsnarje commands will not find any gateways The "stopbsc" command will not find any gateways, even if a BSC3270 gateway is active. The problem is that the output of the "ps -ef" command was modified in Solaris 2.3. 1151201: BSC3270 fails on Sun4 due to older version of SCC serial comm IC (Rev 02) 1154760: get status >402< when try to connect over bsc3270 8.0 ascii When more than 128 bytes was written to a 3270 terminal over an ASCII Bisync line, only the first 128 bytes were translated from ASCII to EBCDIC. This caused the 3270 data stream to conain invalid characters, resulting in an error code of 402 (invalid address for 3270 order). 1158980: SC1000 running 2.3 is crashing in zsb driver An SC1000 with 4 cpus was getting a kernel panic in zsb_softint(), which is in the ZSB driver for BSC3270 8.0. Two threads were updating a field at the same time, resulting in a data fault. 1159424: pe3287 converts ebcdic 0x25 (LineFeed) to 0x2d (dash) This is an ASCII Bisync line bug. A mainframe file (in EBCDIC) sent to the printer contains a x'15' NL character. The mainframe's 370x will translate that to an ASCII x'0A' LF, because there is no NL character defined in ASCII and LF is the closest equivalent. Note that the EBCDIC x'25' LF also is translated to ASCII x'0A' LF. The 8.0 BSC3270 line driver translates ASCII Bisync line data to EBCDIC. The ASCII x'0A' LF is translated to EBCDIC x'25' LF. This is desirable if the original EBCDIC character was a LF, but not if it was a NL. When pe3287 is formatting the printer data, it acts upon the control codes, and translates the normal data from EBCDIC to ASCII. Characters that are not supported by an IBM 3287 are translated to the '-' (dash) character. The EBCDIC x'25' LF character is neither a valid 3287 DSC mode printer control code nor a valid 3287 printable character. The Bisync line driver has been changed to translate ASCII x'0A' LF/NL to EBCDIC x'15' NL. Patch Installation Instructions: -------------------------------- Generic 'installpatch' and 'backoutpatch' scripts are provided within each patch package with instructions appended to this section. Other specific or unique installation instructions may also be necessary and should be described below. Special Install Instructions: ----------------------------- Note: Please don't use the "ibmftp" function as described under bug id 1150305. It will crash and cause kernel panics quite often. It may be fixed by the next patch. BSC 3270 8.0 ASCII Line Support - Installation and Release Notes: This upgrade allows the BSC 3270 8.0 gateway to communicate with the host in ASCII as well as EBCDIC. The ASCII protocol is defined by IBM in their publication "IBM 3270 Information Display System - 3274 Control Unit Description and Programmer's Guide", document # GA23-0061-1. The ASCII line uses seven data bits, odd parity, with a single byte LRC (exclusive or) check character. Because transparency is not supported on the ASCII line, IBM 3270 operations requiring "Structured Field" records are not supported. See notes below concerning the ASCII to/from EBCDIC character set translations. Configure the gateway per instructions in Chapter 2 of the "SunLink BSC 3270 8.0 System Administrators Guide. The following variations apply: a. The control unit poll and select address are the same with ASCII as with EBCDIC, since the decoding is done after the line data is translated from ASCII to EBCDIC. These addresses are described in the IBM 3274 Control Unit Description manual stated above and are repeated here for reference. Note that the actual ASCII characters on the line are different, but cannot be used when configuring the gateway. Use the EBCDIC codes instead. ASCII Code EBCDIC code (use for configuration) Control Unit # Poll Select Poll Select -------------- ---- ------ ---- ------ 0 20 2D 40 60 1 41 2F C1 61 2 42 53 C2 E2 3 43 54 C3 E3 4 44 55 C4 E4 5 45 56 C5 E5 6 46 57 C6 E6 7 47 58 C7 E7 8 48 59 C8 E8 9 49 5A C9 E9 10 5B 7C 4A 6A 11 2E 2C 4B 6B 12 3C 25 4C 6C 13 28 5F 4D 6D 14 2B 3E 4E 6E 15 21 3F 4F 6F 16 26 30 50 F0 17 4A 31 D1 F1 18 4B 32 D2 F2 19 4C 33 D3 F3 20 4D 34 D4 F4 21 4E 35 D5 F5 22 4F 36 D6 F6 23 50 37 D7 F7 24 51 38 D8 F8 25 52 39 D9 F9 26 5D 3A 5A 7A 27 24 23 5B 7B 28 2A 40 5C 7C 29 29 27 5D 7D 30 3B 3D 5E 7E 31 5E 22 5F 7F b. Choose the ASCII character set. c. Ignore the parity choice or use "don't care". The parity is defined by IBM to be odd parity, and the parity choice is ignored by the gateway. d. Choose at least 3, preferably 5 leading SYNC characters. The default is two, and the default choice leads to erratic operation in some environments. e. All other options are the same with ASCII as with EBCDIC code. After configuring the gateway, proceed to start the gateway as described in chapter 3 of the System Administrator's Guide. CHARACTER SET: Some notes about the character set translations are in order here. Most BSC 3270 applications use EBCDIC code on the transmission line, and the SunLink BSC 3270 gateway internally processes all data using the EBCDIC character set. The client processes, such as TE-3278, CG-3270, or PE-3287, then translate the EBCDIC code data from the gateway to ASCII for presentation to the user via terminal emulation window, keyboard data entry or printing. The client processes each have a way to customize the EBCDIC to ASCII translation, so that character set differences and internationalization can be accomodated. For instance, chapter 9 "Localizing Client 3270" of the "SunLink Client 3270 8.0 User's Guide" describes how to modify the EBCDIC to ASCII character set translations for Client 3270 processes. Similar techniques exist for CG-3270 8.0. The translation from ASCII character set used on the transmission line to the EBCDIC code used internally by the BSC 3270 gateway is done by a fixed set of tables that cannot be modified by the user. No modification of these tables is allowed, because modifications could impact how buffer addresses and other control items are decoded in the 3270 data stream. The ASCII on the transmission line to gateway internal EBCDIC translation is defined by IBM for the 3270 and SunLink BSC 3270 conforms to that definition. This translation is less than optimum, in that, for instance, the "!" character gets translated into a "]" rather than into another "!" character, but these cannot be changed without upsetting the 3270 data stream interpretations. The user, however, is free to adjust the EBCDIC to ASCII translations as desired, and any changes to the character set translations must be made at that level. The ASCII line code to gateway internal EBCDIC translation tables coded into the BSC 3270 8.0 gateway are provided below for reference. EBCDIC characters undefined in ASCII are translated into "-", hex 2D as defined in IBM 3270 specification. /* ASCII to EBCDIC translation table*/ /* 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |*/ /* 00 */ 0x00, 0x01, 0x02, 0x03, 0x37, 0x2d, 0x2e, 0x2f, /* 08 */ 0x16, 0x05, 0x15, 0x0b, 0x0c, 0x0d, 0x0e, 0x0f, /* 10 */ 0x10, 0x11, 0x12, 0x13, 0x3c, 0x3d, 0x32, 0x26, /* 18 */ 0x18, 0x19, 0x3f, 0x27, 0x1c, 0x1d, 0x1e, 0x1f, /* 20 */ 0x40, 0x4f, 0x7f, 0x7b, 0x5b, 0x6c, 0x50, 0x7d, /* 28 */ 0x4d, 0x5d, 0x5c, 0x4e, 0x6b, 0x60, 0x4b, 0x61, /* 30 */ 0xf0, 0xf1, 0xf2, 0xf3, 0xf4, 0xf5, 0xf6, 0xf7, /* 38 */ 0xf8, 0xf9, 0x7a, 0x5e, 0x4c, 0x7e, 0x6e, 0x6f, /* 40 */ 0x7c, 0xc1, 0xc2, 0xc3, 0xc4, 0xc5, 0xc6, 0xc7, /* 48 */ 0xc8, 0xc9, 0xd1, 0xd2, 0xd3, 0xd4, 0xd5, 0xd6, /* 50 */ 0xd7, 0xd8, 0xd9, 0xe2, 0xe3, 0xe4, 0xe5, 0xe6, /* 58 */ 0xe7, 0xe8, 0xe9, 0x4a, 0xe0, 0x5a, 0x5f, 0x6d, /* 60 */ 0x79, 0x81, 0x82, 0x83, 0x84, 0x85, 0x86, 0x87, /* 68 */ 0x88, 0x89, 0x91, 0x92, 0x93, 0x94, 0x95, 0x96, /* 70 */ 0x97, 0x98, 0x99, 0xa2, 0xa3, 0xa4, 0xa5, 0xa6, /* 78 */ 0xa7, 0xa8, 0xa9, 0xc0, 0x6a, 0xd0, 0xa1, 0x07 /* EBCDIC to ASCII translation table*/ /* 0 1 2 3 4 5 6 7 */ /* 00 */ 0x00, 0x01, 0x02, 0x03, 0x2d, 0x09, 0x2d, 0x7f, /* 08 */ 0x2d, 0x2d, 0x2d, 0x0b, 0x0c, 0x0d, 0x0e, 0x0f, /* 10 */ 0x10, 0x11, 0x12, 0x13, 0x2d, 0x0a, 0x08, 0x2d, /* 18 */ 0x18, 0x19, 0x2d, 0x2d, 0x1c, 0x1d, 0x1e, 0x1f, /* 20 */ 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x0a, 0x17, 0x1b, /* 28 */ 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x05, 0x06, 0x07, /* 30 */ 0x2d, 0x2d, 0x16, 0x2d, 0x2d, 0x2d, 0x2d, 0x04, /* 38 */ 0x2d, 0x2d, 0x2d, 0x2d, 0x14, 0x15, 0x2d, 0x1a, /* 40 */ 0x20, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* 48 */ 0x2d, 0x2d, 0x5b, 0x2e, 0x3c, 0x28, 0x2b, 0x21, /* 50 */ 0x26, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* 58 */ 0x2d, 0x2d, 0x5d, 0x24, 0x2a, 0x29, 0x3b, 0x5e, /* 60 */ 0x2d, 0x2f, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* 68 */ 0x2d, 0x2d, 0x7c, 0x2c, 0x25, 0x5f, 0x3e, 0x3f, /* 70 */ 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* 78 */ 0x2d, 0x60, 0x3a, 0x23, 0x40, 0x27, 0x3d, 0x22, /* 80 */ 0x2d, 0x61, 0x62, 0x63, 0x64, 0x65, 0x66, 0x67, /* 88 */ 0x68, 0x69, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* 90 */ 0x2d, 0x6a, 0x6b, 0x6c, 0x6d, 0x6e, 0x6f, 0x70, /* 98 */ 0x71, 0x72, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* a0 */ 0x2d, 0x7e, 0x73, 0x74, 0x75, 0x76, 0x77, 0x78, /* a8 */ 0x79, 0x7a, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* b0 */ 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* b8 */ 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* c0 */ 0x7b, 0x41, 0x42, 0x43, 0x44, 0x45, 0x46, 0x47, /* c8 */ 0x48, 0x49, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* d0 */ 0x7d, 0x4a, 0x4b, 0x4c, 0x4d, 0x4e, 0x4f, 0x50, /* d8 */ 0x51, 0x52, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* e0 */ 0x5c, 0x2d, 0x53, 0x54, 0x55, 0x56, 0x57, 0x58, /* e8 */ 0x59, 0x5a, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* f0 */ 0x30, 0x31, 0x32, 0x33, 0x34, 0x35, 0x36, 0x37, /* f8 */ 0x38, 0x39, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d Instructions to install patch using "installpatch" -------------------------------------------------- 1. Become super-user. 2. Apply the patch by typing: //installpatch / where is the directory containing the patch and is the patch number. must be a full path name. Example: # /tmp/123456-01/installpatch /tmp/123456-01 3. If any errors are reported, see "Patch Installation Errors" in the Command Descriptions section below. Rebooting the system or restarting the application after a successful patch installation is usually necessary to utilize patch. NOTE: On client server machines the patch package is NOT applied to existing clients or to the client root template space. Therefore, when appropriate, ALL CLIENT MACHINES WILL NEED THE PATCH APPLIED DIRECTLY USING THIS SAME INSTALLPATCH METHOD ON THE CLIENT. See the next section for instructions for installing a patch on a client. Instructions for installing a patch on a diskless or dataless client -------------------------------------------------------------------- 1. Before applying the patch, the following command must be executed on the server to give the client read-only, root access to the exported /usr file system so that the client can execute the pkgadd command: share -F nfs -o ro,anon=0 /export/exec//usr The command: share -F nfs -o ro,root= \ /export/exec//usr accomplishes the same goal, but only gives root access to the client specified in the command. 2. Login to the client system and become super-user. 3. Continue with step 2 in the "Instructions to install patch using installpatch" section above. Instructions for backing out patch using "backoutpatch" ------------------------------------------------------- 1. Become super-user. 2. Change directory to /var/sadm/patch: cd /var/sadm/patch 3. Backout patch by typing: /backoutpatch where is the patch number. Example: # 123456-01/backoutpatch 123456-01 4. If any errors are reported, see "Patch Backout Errors" in the Command Descriptions section below. Instructions for identifying patches installed on system: ---------------------------------------------------------- Patch packets that have been installed can be identified by using the showrev command with the "-p" option: showrev -p Also note that installpatch has a similar "-p" option which will also just identify patches already installed. Command Descriptions -------------------- NAME installpatch - apply patch package to Solaris 2.x system backoutpatch - remove patch package, restore previously saved files SYNOPSIS installpatch [-udpV] [-S ] backoutpatch [-fV] [-S ] DESCRIPTION These installation and backout utilities apply only to Solaris 2.x associated patches. They do not apply to Solaris 1.x associated patches. These utilities are currently only provided with each patch package and are not included with the standard Solaris 2.x release software. OPTIONS installpatch: -u unconditional install, turns off file validation. Allows the patch to be applied even if some of the files to be patched have been modified since original installation. -d Don't back up the files to be patched. This means that the patch can't be backed out. -p Print a list of the patches currently applied -V Print script version number -S Specify an alternate service (e.g. Solaris_2.3) for patch package processing references. backoutpatch: -f force the backout regardless of whether the patch was superseded -V print version number only -S Specify an alternate service (e.g. Solaris_2.3) for patch package processing references. DIAGNOSTICS Patch Installation Errors: -------------------------- Error message: Patch has already been applied. Explanation and recommended action: This patch has already been applied to the system. If the patch has to be reapplied for some reason, backout the patch and then reapply it. Error message: This patch is obsoleted by patch which has already been applied to this system. Patch installation is aborted. Explanation and recommended action: Occasionally, a patch is replaced by a new patch which incorporates the bug fixes in the old patch and supplies additional fixes also. At this time, the earlier patch is no longer made available to users. The second patch is said to "obsolete" the first patch. However, it is possible that some users may still have the earlier patch and try to apply it to a system on which the later patch is already applied. If the obsoleted patch were allowed to be applied, the additional fixes supplied by the later patch would no longer be available, and the system would be left in an inconsistent state. This error message indicates that the user attempted to install an obsoleted patch. There is no need to apply this patch because the later patch has already supplied the fix. Error Message: None of the packages to patch are installed on this system. Explanation and recommended action: The original packages for this patch have not been installed and therefore the patch cannot be applied. The original packages need to be installed before applying the patch. Error message: This patch is not applicable to client systems. Explanation and recommended action: The patch is only applicable to servers and standalone machines. Attempting to apply this patch to a client system will have no effect on the system. Error message: The /usr/sbin/pkgadd command is not executable. Explanation and recommended action: The /usr/sbin/pkgadd command cannot be executed. The most likely cause of this is that installpatch is being run on a diskless or dataless client and the /usr file system was not exported with root access to the client. See the section above on "Instructions for installing a patch on a diskless or dataless client". Error message: packages are not proper patch packages. Explanation and recommended action: The patch directory supplied as an argument to installpatch did not contain the expected package format. Verify that the argument supplied to installpatch is correct. Error message: The following validation error was found: Explanation and recommended action: Before applying the patch, the patch application script verifies that the current versions of the files to be patched have the expected fcs checksums and attributes. If a file to be patched has been modified by the user, the user is notified of this fact. The user then has the opportunity to save the file and make a similar change to the patched version. For example, if the user has modified /etc/inet/inetd.conf and /etc/inet/inetd.conf is to be replaced by the patch, the user can save the locally modified /etc/inet/inetd.conf file and make the same modification to the new file after the patch is applied. After the user has noted all validation errors and taken the appropriate action for each one, the user should re-run installpatch using the "-u" (for "unconditional") option. This time, the patch installation will ignore validation errors and install the patch anyway. Error message: Insufficient space in /var/sadm/patch to save old files. Explanation and recommended action: There is insufficient space in the /var/sadm/patch directory to save old files. The user has two options for handling this problem: (1) generate additional disk space by deleting unneeded files, or (2) override the saving of the old files by using the "-d" (do not save) option when running installpatch. However if the user elects not to save the old versions of the files to be patched, backoutpatch CANNOT be used. One way to regain space on a system is to remove the save area for previously applied patches. Once the user has decided that it is unlikely that a patch will be backed out, the user can remove the files that were saved by installpatch. The following commands should be executed to remove the saved files for patch xxxxxx-yy: cd /var/sadm/patch/xxxxxx-yy rm -r save/* rm .oldfilessaved After these commands have been executed, patch xxxxxx-yy can no longer be backed out. Error message: Save of old files failed. Explanation and recommended action: Before applying the patch, the patch installation script uses cpio to save the old versions of the files to be patched. This error message means that the cpio failed. The output of the cpio would have been preceded this message. The user should take the appropriate action to correct the cpio failure. A common reason for failure will be insufficient disk space to save the old versions of the files. The user has two options for handling insufficient disk space: (1) generate additional disk space by deleting unneeded files, or (2) override the saving of the old files by using the "-d" option when running installpatch. However if the user elects not to save the old versions of the files to be patched, the patch CANNOT be backed out. Error message: Pkgadd of package failed with error code . See /tmp/log. for reason for failure. Explanation and recommended action: The installation of one of patch packages failed. Any previously installed packages in the patch should have been removed. See the log file for the reason for failure. Correct the problem and re-apply the patch. Patch Installation Messages: --------------------------- Note: the messages listed below are not necessarily considered errors as indicated in the explanations given. These messages are, however, recorded in the patch installation log for diagnostic reference. Message: Package not patched: PKG=SUNxxxx Original package not installed Explanation: One of the components of the patch would have patched a package that is not installed on your system. This is not necessarily an error. A Patch may fix a related bug for several packages. Example: suppose a patch fixes a bug in both the online-backup and fddi packages. If you had online-backup installed but didn't have fddi installed, you would get the message Package not patched: PKG=SUNWbf Original package not installed This message only indicates an error if you thought the package was installed on your system. If this is the case, take the necessary action to install the package, backout the patch (if it installed other packages) and re-install the patch. Message: Package not patched: PKG=SUNxxx ARCH=xxxxxxx VERSION=xxxxxxx Architecture mismatch Explanation: One of the components of the patch would have patched a package for an architecture different from your system. This is not necessarily an error. Any patch to one of the architecture specific packages may contain one element for each of the possible architectures. For example, Assume you are running on a sun4m. If you were to install a patch to package SUNWcar, you would see the following (or similar) messages: Package not patched: PKG=SUNWcar ARCH=sparc.sun4c VERSION=11.5.0,REV=2.0.18 Architecture mismatch Package not patched: PKG=SUNWcar ARCH=sparc.sun4d VERSION=11.5.0,REV=2.0.18 Architecture mismatch Package not patched: PKG=SUNWcar ARCH=sparc.sun4e VERSION=11.5.0,REV=2.0.18 Architecture mismatch Package not patched: PKG=SUNWcar ARCH=sparc.sun4 VERSION=11.5.0,REV=2.0.18 Architecture mismatch The only time these messages indicate an error condition is if installpatch does not correctly recognize your architecture. Message: Package not patched: PKG=SUNxxxx ARCH=xxxx VERSION=xxxxxxx Version mismatch Explanation: The version of software to which the patch is applied is not installed on your system. For example, if you were running Solaris 5.3, and you tried to install a patch against Solaris 5.2, you would see the following (or similar) message: Package not patched: PKG=SUNWcsu ARCH=sparc VERSION=10.0.2 Version mismatch This message does not necessarily indicate an error. If the version mismatch was for a package you needed patched, either get the correct patch version or install the correct package version. Then backout the patch (if necessary) and re-apply. Patch Backout Errors: --------------------- Error message: Patch has not been successfully applied to this system. Explanation and recommended action: The user has attempted to back out a patch that was never applied to this system. It is possible that the patch was applied, but that the patch directory /var/sadm/patch/ was deleted somehow. If this is the case, the patch cannot be backed out. The user may have to restore the original files from the initial installation CD. Error message: This patch was obsoleted by patch $1. Patches must be backed out in the order in which they were installed. Patch backout aborted. Explanation and recommended action: The obsoleted contents of an older patch rev that apparently still exists under /var/sadm/patch should never be restored out of sequence. This could undermine the integrity of the more current patch rev installed and the restoration of the files it has saved. Error message: Patch was installed without backing up the original files. It cannot be backed out. Explanation and recommended action: Either the -d option of installpatch was set when the patch was applied, or the save area of the patch was deleted to regain space. As a result, the original files are not saved and backoutpatch cannot be used. The original files can only be recovered from the original installation CD. Error message: pkgrm of package failed return code . See /var/sadm/patch//log for reason for failure. Explanation and recommended action: The removal of one of patch packages failed. See the log file for the reason for failure. Correct the problem and run the backout script again. Error message: Restore of old files failed. Explanation and recommended action: The backout script uses the cpio command to restore the previous versions of the files that were patched. The output of the cpio command should have preceded this message. The user should take the appropriate action to correct the cpio failure. KNOWN PROBLEMS: On client server machines the patch package is NOT applied to existing clients or to the client root template space. Therefore, when appropriate, ALL CLIENT MACHINES WILL NEED THE PATCH APPLIED DIRECTLY USING THIS SAME INSTALLPATCH METHOD ON THE CLIENT. See instructions above for applying patches to a client. A bug affecting a package utility (eg. pkgadd, pkgrm, pkgchk) could affect the reliability of installpatch or backoutpatch which uses package utilities to install and backout the patch package. It is recommended that any patch that fixes package utility problems be reviewed and, if necessary, applied before other patches are applied. Such existing patches are: 100901 Solaris 2.1 101122 Solaris 2.2 101331 Solaris 2.3 SEE ALSO pkgadd, pkgchk, pkgrm, pkginfo, showrev