Patch Name: PHNE_7785 Patch Description: s700 9.X OTS C.04.03 cumulative mega patch Creation Date: 96/07/15 Post Date: 96/07/26 Hardware Platforms - OS Releases: s700: 9.01 9.03 9.05 9.07 Products: OTS/9000 C.04.03 Filesets: OTS-KRN,A.B9.00.00 OTS-RUN,A.B9.00.00 OTS-SES-PRG,A.B9.00.00 APLI-PRG,A.B9.00.00 ROSE-PRG,A.B9.00.00 XTI-PRG,A.B9.00.00 Automatic Reboot?: Yes Status: General Release Critical: Yes PHNE_7785: PANIC PHNE_7391: PANIC PHNE_6721: PANIC PHNE_6237: PANIC PHNE_5693: PANIC PHNE_5367: PANIC PHNE_5116: PANIC Path Name: /hp-ux_patches/s700/9.X/PHNE_7785 Symptoms: PHNE_7785: 1. After installing patch PHNE_7391, OTS is brought up, end-system hellos were sent out correctly. But after any OTS connection to a remote system was initiated, the end-system hellos would not get sent out any more. PHNE_7391: 1. The XTI traces mix up the information for internal and external calls when XTI_TRACE=xio. 2. The files OTSconfigSAP and OTSconfigSBN are created by otsstart with global write permission. 3. Additional Funtionality: As an enhancement to OTS it now supports configuration of alternate physical addresses in dest entries associated with CONS/X.25 subnetworks. This is provided via dest_alt_phys_address lines in ots_dests. It is also supported via -a options in the otsaddes command. Otsdeles and otsshowes were also changed to support the alternate physical address functionality. Additionally the parameter snet_ises in the ots_subnets file can now be set to a value of 0. This is for FDDI and LAN. With it set to 0 no end system hellos will be generated. PHNE_6721: 1. In an MSDSG configuration NODE(A) <----> NODE(B) <---> NODE(C) Where: NODE(A) is configured as LAN only NODE(B) is configured as an MSDSG relay node and is configured both for X.25 CONS and LAN. NODE(C) is configured for X.25 CONS. When NODE(A) initiates a connection with NODE(C) via MSDSG on NODE(B), sometimes NODE(B) will panic when the connection disconnects. Apparently this problem is limited to situations where NODE(B) is running High Perf X.25. It doesn't seem to happen with Classic X.25. 2. User sees files with names of the form Saannnnn accumulate in /usr/spool/sockets/osi. Where: aa is a string of two alphabetic characters which may be either upper or lower case. nnnnn is a process id number. These files are created by FTAM. 3. OTS osidiag "WAN X.25 Tests" display inappropriate NSAP information. When "Connect" is selected, the test displays "x25_calling_nsap" and "x25_called_nsap" values which were choosen by osidiag, but are unlikely to be used in the test. The NSAPs should be set by the user when a "ISO 8878 Encoding" test is run. 4. A ROSE application which calls ap_rcv could go into an infinite loop. 5. A ROSE application which sends data larger than 65500 bytes will get truncated packets on the receiving side. 6. A XTI application calling t_look receives back a value of 0, even when there is data to be received. 7. User will see a 'Data segmentation fault' panic with the following procedures on the stack. OsiDwBind OsiTpiBindReq Trs_Tpi_down Osxwuput 8. A ROSE application will core-dump if a NULL ubuf pointer is used on a ROSE API call. PHNE_6237: 1. XTI applications will not be able to do a t_connect() on the same file descriptor after doing a t_rcvdis(), if they do not pass a NULL pointer as the second argument to t_rcvdis. The t_errno returned by t_rcvdis will be TSYSERR. 2. When ap_get_env(AP_LIB_AVAIL) is called, it returns error code AP_NOSET, indicating that the ap_lib_avail is not set. User expects it to return the default value of the ap_lib_avail. 3. When TPDUs with bad length values are received, an ack for that PDU is sent. 4. The "FTAM Test Cases" in osidiag do not work if FTAM is D.04.00 or greater. The FTAM tests in osidiag fail with the log message: "(FC_FAILED) Flow Control operations failed because the OSI Shared Memory Manager is not accessible." 5. A panic occurs when OTS receives an unsupported osiping packet from another system. 6. The defect report described it as "OSIADMIN reports error: get_x25_dev_status: ioctl failed. errno=223" If you have high-performance X.25 (Streams X.25), and you have 2 or more X.25 cards, you can't do "Start X.25", "Stop X.25" "Test Connectivity" or "View Configuration" in osiadmin. You get an error displayed to the screen "get_x25_dev_status: ioctl failed. errno=223". Also, if you have high-performance X.25, 1 or more X.25 cards, and you start OTS from osiadmin you will get this error displayed to the screen "Making sure links are running... check_links: Status of /dev/x25_0 - not up after 30 seconds. Couldn't start all links, starting OTS anyway!" 7. When running the osidiag transport loopback test through Streams X.25 CONS through a TRANSPAC network with a NULL packet address in the X.25 configuration file, the calling NSAP is corrupted. The subnet address shows up at the beginning portion of the NSAP. PHNE_6036: 1. APLI initiator sends out multiple association requests to a responder. The responder sometimes sends back negative responses and closes the endpoints. The initiator would receive user abort requests instead of the negative responses. PHNE_5693: 1. In using the High-Performance X.25 (streams-based), after a shutdown 0, then an inet 2, x25init panics the system with a trap 15. This has been isolated to OTS C.04.03. 2. When OTS is installed on a 9.0x system and configured for either LAN or FDDI, netstat -i displays garbage information. 3. The FTAM process ftam_resp will get hung-up when the system is overloaded, because OTS receive Negative Connect Confirms. 4. The FTAM process ftam_resp core dumps because OTS C.04.03 kernel code incorrectly reuses streams device minor numbers. Other applications which use the session API could core dump, hang, abort, etc. 5. The ACSE/Presentation and Rose Interface (APRI) causes a system panic when an Association-Release Response (A_RELEASE_RSP) does not supply any user data. 6. ROSE sends multiple headers for a single RO_RESULT_REQ during multiple ap_snd() when sending more than 16K of data at a time. 7. System panics when OTS is started on a Series 800 with HP-UX 9.04 that does not have the kernel patch PHKL_3658 to fix a malloc problem. PHNE_5367: The following symptoms were first fixed in PHNE_5367: 1. Calls to various session API functions with API tracing enabled could result in core dumping the application. 2. Enhancement requested to allow changeable RCI table size. This patch provides a minimal fix by providing an adb-abl variable (clns_rci_size)which, if modified prior to starting OTS, will cause a different RCI table to be allocated. 3. Enhancement requested to allow changeable high-water mark in flow control module. This patch provides a minimal fix by providing an adb-abl variable (fcm_hi_wat_mk) which can be used to minimize the data queued in the upper write queue. 4. Under wrong circumstances, the OTS daemon (otsamd) may core dump when an RFC1006 or Streams/X.25 connection is released. 5. Problem related to osidiag tracing fix for streams X.25. 6. CR TPDU is encoded with NO_CHKSUM when tpcons_tp4_chksum is set. Problems occur when running with X.25/CONS and affect upper layer applications' ability to request checksum, e.g. FTAM, APLI, Session. 7. Increased the limit on cons_max_ndsu to 10240. 8. otsstat reports the following for a link although the link is up: ## OP_REF[E:8862 ERR:110 M:10 F:0] ## registration failed An OSI application, e.g. FTAM, may also encounter problems. 9. IOP problem between HP APRI and an Italian OSI vendor. HP APRI sent a pres-req field in a CPA PPDU in response to an incoming CP PPDU in which the pres-req field is absent. 10.System reports a data segment violation and panics with OsiTpi on the stack when running XTI applications. 11.IOP problem between HP OTS and BULL dpx2 on TP4 over X.25 CONS. 12.ACK timer algorithm has problem and slow down the performances. 13.Issues with accuracy of OTS timer calculations. PHNE_5116: The following symptoms were first fixed in PHNE_5116: 1. Panic occurs when three or more CLNS subnets (X.25 or LAN) are configured, and no more than one CONS subnet is configured. This defect only exists on OTS version C.04.03. 2. Under stressful or memory constrained conditions, a bad pointer value is generated in the OTS kernel, which may result in a panic at various locations. 3. OTS incorrectly accepts parameters in the CC TPDU which it doesn't actually support, resulting in an eventual Transport disconnect. Mostly occurs with DEC Alpha OSI stacks which support a new version of Transport protocol. 4. RFC1006 will not interoperate with other implementations when the TSAP length is greater than a certain length. 5. A minor memory leak occurs when using RFC1006; may not be noticeable under most circumstances. 6. This defect only occurs with OTS C.04.03. It affects any customers configuring OTS as an MSDSG (CONS-CLNS gateway). 7. File osi.h contains #ifdef statements that don't comply with ANSI C guidelines. Defect Description: PHNE_7785: 1. The end-system hello timers stopped functioning after any connection was initiated. Since these timers were not popping, nothing were sent out. The problem has been fixed. PHNE_7391: 1. A global variable used to trace the nesting level was not being incremented correctly. 2. The umask is set to 0 by otsstart. PHNE_6721: 1. A missing call to create a trace header in the module tr4sub.c is resulting in memory corruption of OTS data structures. The nature of the panic depends on which data structure gets corrupted and when the corrupt data is accessed. This only happens when the MSDSG relay function is operating and is associated only with disconnect processing. The code has been modified to create the necessary trace header so that the memory corruption does not occur. 2. FTAM cannot determine whether or not it is safe to delete files of the form Saannnnn in /usr/spool/sockets/osi. Apparently, this can only be safely done by OTS during stack startup. OTS now removes these files. 3. OTS osidiag initialized the NSAPs even though they are unlikely to be used, and all values set are displayed. With this patch osidiag does not initialize the NSAPs. 4. ap_rcv() calls a decoding routine in the ROSE library to decode an incoming ROSE result indication. But the decoder returns a negative data length, which causes ap_rcv() to loop. ap_rcv() will now check for a valid data length. 5. The ROSE library does not correctly encoded the length field if it requires more than 2 bytes. The fix is to correctly encode a length requiring more than 2 bytes. 6. The t_look() routine issues an ioctl to the streams head. In later 9.X releases, the streams code has been changed to check this pointer before looking for available data and just return 0. The fix is to pass a valid pointer to the ioctl. 7. A context data structure managed by OTS is not being removed from a list of registered contexts when an internal condition requests that an unbind operation take place. The context is released to free memory and eventually reused for another purpose. Traversals of the registration list containing the bogus context eventually trip over the 'corrupted' entry and a data segmentation fault results. 8. The ROSE library tried to dereference the pointer without first checking it, hence the core-dump. The fix is to ensure it not NULL before dereferencing. PHNE_6237: 1. This error is caused because t_rcvdis() does not call the TI_XTI_CLEAR_EVENT ioctl when a NULL pointer is passed to the t_rcvdis() routine as the second argument. When this ioctl is not called, the xtimod module's max and min queue sizes are set to 1 and 2 respectively causing all further putmsg() calls to fail. Thus the t_connect() call that follows the t_rcvdis() fails with a t_errno=TSYSERR. Fix is to call TI_XTI_CLEAR_EVENT ioctl. This problem does not exist on 10.X. 2. This error is caused because the ap_lib_avail is not set when ap_init_env() is called. The ap_lib_avail is always readable and has a default value which is supposed to be set by ap_init_env(). There is no code in ap_init_env() to set the ap_lib_avail. The fix is to add necessary code into ap_init_env(). The defect is also present in 10.x and the fix will be available in C.05.02. 3. The processing of invalid length PDUs happens after the YR-TU-NR and other TPDU-NR counters have been incremented. Therefore the initiator does not retransmit the bad length PDU causing problems with incomplete data received by the application. 4. The OTS command osidiag needed to be relinked with the latest libraries from FTAM. In this version of OTS the libraries are linked in, in future releases of OTS (based upon HP-UX 10.X) the shared libraries of FTAM are used. 5. OTS panics upon receiving CLNP echo request and CLNP echo reply packets from the osiping command. The fix is to check for CLNP type 30 and type 31 and drop these packet types. 6. The problem was that the ioctl call X25_RD_IFSTATE was not implemented in high-performance X.25 (Streams X.25) and a different mechanism for verfying the status of X.25 had to be used. 7. The problem was that the streams X.25 low access module copies the subaddress into the calling address field assuming the subaddress contains both the x121 address and subaddress. The 8878 standards were not used in the OTS configuration file. Hence OTS stack used the calling address, which contained only the subaddress in this case, as the NSAP. PHNE_6036: 1. After the negative response is sent out, an association indication comes in; OTS stack queues the request to the same endpoint. Then ap_close comes down. OTS sends out the user abort request. This patch is for a site specific feature and it does not apply to other customers. The feature needs to be explicitly activated. Installing this patch without activating the feature is the same as PHNE_5693. Hence if PHNE_5693 has been installed, there is no need to put on this patch. PHNE_5693: 1. In using the High-Performance X.25 (streams-based), after a shutdown 0, then an inet 2, x25init panics the system with a trap 15. This is an internal error in OTS C.04.03. 2. An internal error in OTS caused netstat -i to display garbage information. 3. When the system is overloaded, we receive Negative Connect Confirms from the responder. 4. The C.04.03 version of the OTS kernel code incorrectly reuses streams device minor numbers. This causes various session API application level processes to dump core, hang, abort, etc. 5. With this fix the system does not panic what an Association-Release Response (A_RELEASE_RSP) does not supply any user data. 6. ROSE sends multiple headers for a single RO_RESULT_REQ during multiple ap_snd() when sending more than 16K of data at a time. 7. The fix takes care of a NULL pointer when MALLOC fails to get any memory for OTS. Added a check to ensure the elment pointer is valid before dereferencing it. PHNE_5367: 1. Session library API tracing problem. 2. Enhancement requested to allow changeable RCI table size. 3. Enhancement requested to allow changeable high-water mark in flow control module. 4. OTS daemon crashes with RFC1006 or Streams/X.25. 5. Problem related to osidiag tracing fix for streams X.25. 6. Modified the flag associated with TPCONS_TP4_CHKSUM. 7. Increased the limit on cons_max_ndsu to 10240. 8. otsstat hot site fixes. 9. IOP problem between HP APRI and an Italian OSI vendor. 10.TPI panic fix. 11.IOP problem between HP OTS and BULL dpx2 on TP4 over X.25 CONS. 12.Problem with "slow start" transmission algorithm. 13.Issues with accuracy of OTS timer calculations. PHNE_5116: 1. Panic occurs when three or more CLNS subnets (X.25 or LAN) are configured, and no more than one CONS subnet is configured. This defect only exists on OTS version C.04.03. 2. Under stressful or memory constrained conditions, a bad pointer value is generated in the OTS kernel, which may result in a panic at various locations. 3. OTS incorrectly accepts parameters in the CC TPDU which it doesn't actually support, resulting in an eventual Transport disconnect. Mostly occurs with DEC Alpha OSI stacks which support a new version of Transport protocol. 4. RFC1006 will not interoperate with other implementations when the TSAP length is greater than a certain length. 5. A minor memory leak occurs when using RFC1006; may not be noticeable under most circumstances. 6. This defect only occurs with OTS C.04.03. It affects any customers configuring OTS as an MSDSG (CONS-CLNS gateway). 7. File osi.h contains #ifdef statements that don't comply with ANSI C guidelines. SR: 1653157958 5003275693 5003304972 1653154666 4701318337 1653130492 1653131524 4701286138 5000712505 1653119024 1653114678 1653108522 5000710764 1653122515 5003242958 1653122127 1653122028 1653124404 1653124602 1653122044 1653122036 1653140459 1653148783 4701302406 5000713602 5003272658 1653157875 1653160416 Patch Files: /etc/net/osi/ots/bin2conf /etc/net/osi/ots/conf2bin /usr/lib/libapli.a /usr/lib/libapli.sl /etc/conf/libotsam.a /usr/lib/libotss.a /usr/lib/libotss.sl /usr/lib/librose.a /usr/lib/librose.sl /usr/lib/libxti.a /usr/lib/libxti.sl /usr/include/osi.h /usr/lib/osiadmin/osiadminx /usr/bin/osiconfchk /usr/lib/nls/C/osiconfchk.cat /usr/lib/osiconf/osiconfx /usr/lib/nls/C/osidiag.cat /usr/lib/osidiag/osidiagx /usr/bin/otsaddes /usr/man/man1m.Z/otsaddes.1m /etc/otsamd /usr/bin/otsdeles /usr/man/man1m.Z/otsdeles.1m /usr/bin/otsshowes /usr/man/man1m.Z/otsshowes.1m /usr/bin/otsstart /etc/net/osi/ots/otstrans /etc/net/osi/ots/OTShardconf what(1) Output: /etc/net/osi/ots/bin2conf: OTS: C.04.03 $Date: 94/06/28 11:38:40 $ ics.c PATCH C.04.03 (PHNE_7390/PHNE_7391) cv_tbl.c PATCH C.04.03 (PHNE_7390/PHNE_7391) /etc/net/osi/ots/conf2bin: OTS: C.04.03 $Date: 94/06/28 11:38:40 $ ics.c PATCH C.04.03 (PHNE_7390/PHNE_7391) cv_tbl.c PATCH C.04.03 (PHNE_7390/PHNE_7391) /usr/lib/libapli.a: OTS: C.04.03 $Date: 94/06/28 11:38:40 $ al_rcv.c PATCH C.04.03 (PHNE_6720/PHNE_6721) al_snd.c PATCH C.04.03 (PHNE_5692/PHNE_5693) al_env_utl.c PATCH C.04.03 (PHNE_6236/PHNE_6237) /usr/lib/libapli.sl: OTS: C.04.03 $Date: 94/06/28 11:38:40 $ al_rcv.c PATCH C.04.03 (PHNE_6720/PHNE_6721) al_snd.c PATCH C.04.03 (PHNE_5692/PHNE_5693) al_env_utl.c PATCH C.04.03 (PHNE_6236/PHNE_6237) /etc/conf/libotsam.a: FILESET OTS-KRN: libotsam.a: Revision: C.04.03 e2iadm.c PATCH C.04.03 (PHNE_7390/PHNE_7391) e2icstz.c PATCH C.04.03 (PHNE_7390/PHNE_7391) e2isub.c PATCH C.04.03 (PHNE_7784/PHNE_7785) genmai2.c PATCH C.04.03 (PHNE_5692/PHNE_5693) genmain.c PATCH C.04.03 (PHNE_6720/PHNE_6721) netcstz.c PATCH C.04.03 (PHNE_7390/PHNE_7391) netmai2.c PATCH C.04.03 (PHNE_7390/PHNE_7391) netmain.c PATCH C.04.03 (PHNE_7390/PHNE_7391) pstsub1.c PATCH C.04.03 (PHNE_5366/PHNE_5367) pstsub2.c PATCH C.04.03 (PHNE_5366/PHNE_5367) sescstz.c PATCH C.04.03 (PHNE_5115/PHNE_5116) tr4cstz.c PATCH C.04.03 (PHNE_5115/PHNE_5116) tr4mai2.c PATCH C.04.03 (PHNE_6236/PHNE_6237) tr4main.c PATCH C.04.03 (PHNE_5366/PHNE_5367) tr4sub.c PATCH C.04.03 (PHNE_6720/PHNE_6721) trscod.c PATCH C.04.03 (PHNE_5366/PHNE_5367) trsdec.c PATCH C.04.03 (PHNE_6236/PHNE_6237) trsmai2.c PATCH C.04.03 (PHNE_5366/PHNE_5367) trsmain.c PATCH C.04.03 (PHNE_5366/PHNE_5367) trssub.c PATCH C.04.03 (PHNE_5366/PHNE_5367) strosxint.c PATCH C.04.03 (PHNE_5692/PHNE_5693) strosxmem.c PATCH C.04.03 (PHNE_7390/PHNE_7391) strosxopi.c PATCH C.04.03 (PHNE_6035/PHNE_6036) strosxos.c PATCH C.04.03 (PHNE_6720/PHNE_6721) strosxtool.c PATCH C.04.03 (PHNE_5692/PHNE_5693) strosxtpi.c PATCH C.04.03 (PHNE_7784/PHNE_7785) hp_osxlan.c PATCH C.04.03 (PHNE_5692/PHNE_5693) hp_osxfcmod.c PATCH C.04.03 (PHNE_5366/PHNE_5367) hp_osxfcutil.c PATCH C.04.03 (PHNE_5366/PHNE_5367) faimem.c PATCH C.04.03 (PHNE_5115/PHNE_5116) sx25_lam.c PATCH C.04.03 (PHNE_7390/PHNE_7391) strosxrK6.c PATCH C.04.03 (PHNE_6236/PHNE_6237) /usr/lib/libotss.a: admlib.c PATCH_C.04.03 (PHNE_5366/PHNE_5367) $Revisi on: 9.11 $Date: 92/10/13 16:44:34 $ OTS: C.04.03 $Date: 94/06/28 11:38:40 $ mbxlib.c PATCH_C.04.03 (PHNE_5692/PHNE_5693)$Revisio n: 9.5 $Date: 93/04/29 10:32:15 $ /usr/lib/libotss.sl: admlib.c PATCH_C.04.03 (PHNE_5366/PHNE_5367) $Revisi on: 9.11 $Date: 92/10/13 16:44:34 $ OTS: C.04.03 $Date: 94/06/28 11:38:40 $ mbxlib.c PATCH_C.04.03 (PHNE_5692/PHNE_5693)$Revisio n: 9.5 $Date: 93/04/29 10:32:15 $ /usr/lib/librose.a: ro_encode.c PATCH C.04.03 (PHNE_6720/PHNE_6721) ro_func.c PATCH C.04.03 (PHNE_6720/PHNE_6721) OTS: C.04.03 $Date: 94/06/28 11:38:40 $ ro_util.c PATCH C.04.03 (PHNE_6720/PHNE_6721) /usr/lib/librose.sl: ro_encode.c PATCH C.04.03 (PHNE_6720/PHNE_6721) ro_func.c PATCH C.04.03 (PHNE_6720/PHNE_6721) OTS: C.04.03 $Date: 94/06/28 11:38:40 $ ro_util.c PATCH C.04.03 (PHNE_6720/PHNE_6721) /usr/lib/libxti.a: OTS: C.04.03 $Date: 94/06/28 11:38:40 $ tlook.c PATCH C.04.03 (PHNE_6720/PHNE_6721) trcvdis.c PATCH C.04.03 (PHNE_6236/PHNE_6237) api_macros.h PATCH C.04.03 (PHNE_7390/PHNE_7391) /usr/lib/libxti.sl: OTS: C.04.03 $Date: 94/06/28 11:38:40 $ tlook.c PATCH C.04.03 (PHNE_6720/PHNE_6721) trcvdis.c PATCH C.04.03 (PHNE_6236/PHNE_6237) api_macros.h PATCH C.04.03 (PHNE_7390/PHNE_7391) /usr/include/osi.h: OSI Library header file $Revision: 9.3 $ $Date: 95/0 1/05 15:00:26 $ /usr/lib/osiadmin/osiadminx: OTS: C.04.03 $Date: 94/06/28 11:38:40 $ osiadmin.c $Revision: 5.0 $ $Date: 93/04/14 16:48:31 $ osifuncs.c $Revision: 5.3 $ $Date: 93/06/07 10:42:38 $ osiutils.c PATCH_C.04.03 (PHNE_6236/PHNE_6237) $Revi sion: 5.0.1.3 $ $Date: 95/11/13 10:38:19 $ osi_fedit.c $Revision: 5.0 $ $Date: 93/04/14 16:48:2 3 $ /usr/bin/osiconfchk: OTS: C.04.03 $Date: 94/06/28 11:38:40 $ confcheck.c PATCH C.04.03 (PHNE_5366/PHNE_5367) chk_strnge.c PATCH C.04.03 (PHNE_7390/PHNE_7391) structures.c PATCH C.04.03 (PHNE_7390/PHNE_7391) find_line.c PATCH C.04.03 (PHNE_7390/PHNE_7391) add_parms.c PATCH C.04.03 (PHNE_7390/PHNE_7391) /usr/lib/nls/C/osiconfchk.cat: osiconfchk.cat PATCH_C.04.03 (PHNE_7390/PHNE_7391) /usr/lib/osiconf/osiconfx: OTS: C.04.03 $Date: 94/06/28 11:38:40 $ structures.c PATCH C.04.03 (PHNE_7390/PHNE_7391) /usr/lib/nls/C/osidiag.cat: OTS: C.04.03 osidiag.cat PATCH_C.04.03 (PHNE_7390/PHNE_7391) /usr/lib/osidiag/osidiagx: HP92453-02A.09.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 71.3 $ addtype.c 2.3 Released: 3/13/88 pdu.c 2.1 Released: 10/4/87 fpdu.c 2.3 Released: 3/13/88 apdu.c 2.2 Released: 3/13/88 apdu.c 2.2 Released: 3/13/88 fpdu.c 2.3 Released: 3/13/88 vd.c 2.3 Released: 8/1/88 directory.c 2.3 Released: 3/13/88 file.c 2.1 Released: 10/4/87 bit.c PATCH C.04.03 (PHNE_6720/PHNE_6721) OTS: C.04.03 $Date: 94/06/28 11:38:40 $ FTAM: D.04.00 95/05/23 s800 libmapftam.a MMS: B.00.03 $Date: 94/01/07 11:33:56 $ MAP30: C.04.03 $Date: 94/07/06 10:48:49 $ CMIS/CMIP_version_1.6 @(#) sbm.h, revision 3.0 890801 SYN_body.c CMIS/CMIP_version_1.6.1 sbmlib.c, revision 1.0 890801 sbmlib.h, revision 3.0 890801 sbm.h, revision 3.0 890801 sbmprv.c, revision 1.0 890801 sbmlib.h, revision 3.0 890801 sbm.h, revision 3.0 890801 /usr/bin/otsaddes: OTS: C.04.03 otsaddes PATCH C.04.03 (PHNE_7390/PHNE_7391) /usr/man/man1m.Z/otsaddes.1m: None /etc/otsamd: strmxdrK6.c PATCH_C.04.03 (PHNE_5366/PHNE_5367) $Rev ision: 1.1.109.8 $ $Date: 95/04/06 10:59:37 $ OTS: C.04.03 $Date: 94/10/03 16:13:04 $ /usr/bin/otsdeles: OTS: C.04.03 otsdeles PATCH C.04.03 (PHNE_7390/PHNE_7391) /usr/man/man1m.Z/otsdeles.1m: None /usr/bin/otsshowes: OTS: C.04.03 otsshowes PATCH C.04.03 (PHNE_7390/PHNE_7391) /usr/man/man1m.Z/otsshowes.1m: None /usr/bin/otsstart: OTS: C.04.03 otsstart PATCH C.04.03 (PHNE_7390/PHNE_7391) /etc/net/osi/ots/otstrans: OTS: C.04.03 $Date: 94/06/28 11:38:40 $ genlib.c PATCH C.04.03 (PHNE_7390/PHNE_7391) ics.c PATCH C.04.03 (PHNE_7390/PHNE_7391) cv_tbl.c PATCH C.04.03 (PHNE_7390/PHNE_7391) routelib.c PATCH C.04.03 (PHNE_7390/PHNE_7391) /etc/net/osi/ots/OTShardconf: OTS: C.04.03 OTShardconf PATCH C.04.03 (PHNE_7390/PHNE_7391) sum(1) Output: 15835 264 /etc/net/osi/ots/bin2conf 27432 280 /etc/net/osi/ots/conf2bin 1457 1122 /usr/lib/libapli.a 12922 1184 /usr/lib/libapli.sl 3771 2888 /etc/conf/libotsam.a 62105 992 /usr/lib/libotss.a 50666 992 /usr/lib/libotss.sl 29821 96 /usr/lib/librose.a 13173 112 /usr/lib/librose.sl 27638 293 /usr/lib/libxti.a 11108 256 /usr/lib/libxti.sl 49236 91 /usr/include/osi.h 21765 921 /usr/lib/osiadmin/osiadminx 34990 592 /usr/bin/osiconfchk 14380 32 /usr/lib/nls/C/osiconfchk.cat 7712 1697 /usr/lib/osiconf/osiconfx 43001 690 /usr/lib/nls/C/osidiag.cat 30576 3573 /usr/lib/osidiag/osidiagx 25721 33 /usr/bin/otsaddes 18826 7 /usr/man/man1m.Z/otsaddes.1m 46873 28 /usr/bin/otsshowes 39350 2 /usr/man/man1m.Z/otsshowes.1m 28650 30 /usr/bin/otsstart 45613 576 /etc/net/osi/ots/otstrans 48926 6 /etc/net/osi/ots/OTShardconf 36648 764 /etc/otsamd 54585 14 /usr/bin/otsdeles 28955 3 /usr/man/man1m.Z/otsdeles.1m Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: Must be OTS release C.04.03 Supersedes: PHNE_5116 PHNE_5367 PHNE_5693 PHNE_6036 PHNE_6237 PHNE_6721 PHNE_7391 Equivalent Patches: PHNE_7784: s800: 9.00 9.04 Patch Package Size: 8850 Kbytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Copy the patch to your /tmp directory and unshar it: cd /tmp cp patch_source/PHNE_7785 . sh PHNE_7785 3. Become root and run update: /etc/update [-r [kernel_gen_file]] -s \ /tmp/PHNE_7785.updt PHNE_7785 Update moves the original software to /system/PHNE_7785/orig. Keep this file to recover from any potential problems. You should move the .text file to /system/PHNE_7785 for future reference. To put this patch on a magnetic tape and update from the tape drive, use dd: dd if=PHNE_7785.updt of=/dev/rmt/0m bs=2048 Special Installation Instructions: None