XWB*1.1*16 (4054)    BUILD (9.6)

Name Value
NAME XWB*1.1*16
DATE DISTRIBUTED 2001-11-20 00:00:00
PACKAGE FILE LINK RPC BROKER
REQUIRED BUILD
  • XWB*1.1*10
    ACTION:   Don't install, leave global
  • XWB*1.1*15
    ACTION:   Don't install, leave global
  • XU*8.0*215
    ACTION:   Don't install, leave global
TYPE SINGLE PACKAGE
DESCRIPTION OF ENHANCEMENTS
NOIS: WCO-0300-50643
                        
       Want KIDS to INHIBIT LOGONs during the install? YES//
                              
       No Options or Protocols need to be placed out-of-order.
       Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO
                                                                       ==

   8.  If the routines were unmapped as part of step 3, the mapped set
       should be rebuilt once the installation has run to completion. 

   9.  Restart the Broker Listener on the Server:
  The calls to RTL were remove from logging the broker code. If Response Time 
         a.  Log into your M server
         b.  Enter the following at the M prompt:

             >D STRT^XWBTCP(Listener port)
             (Typically, the Listener port is 9200)

============================================================================

  Logging is on, then the RPC will still be logged.

  Worked with the NVS to use the correct call to see that Broker connection
  got registered as client server so they all connections from one IP address
  could share Cache one licenses.
  
  A change was made to check the IP address of the PEER and to use that if
  different than the IP address in the header.  This allows the use of NAT
      XWBTCPC
  translation.

NOIS: CLL-0301-40678
      JAC-0301-70277
      XWBTCPC
   If an application Newed the XWBOS variable and then experienced an error,
   it would cause a second error in the error module of the Broker.  This 
   has been fixed by setting the value of XWBOS in the error trap module.

NOIS: KAN-0201-40992
  Under Cache 3.2 error trapping conditions, the return of control wouldn't go 
      XWBTCPL
   If a connection was made to the RPC Broker listener port that failed to 
   send the correct information, this could cause the listener to fail to 
   detect other connection requests.  This has been fixed by changing the 
   timeout on the read and resetting the port if this happens.

Routine Summary
The following routines are included in this patch.  The second line of each
of these routines now looks like:
 ;;1.1;RPC BROKER;<patchlist>;Mar 28, 1997
  to the correct routine, resulting in a run-away job. Fixed by being explicit 

                 Checksum
Routine         Old       New      2nd Line
XWBBRK        5912545   5552318    **2,4,10,16**
XWBTCPC       7568523   7379419    **2,5,4,6,9,16**
XWBTCPL       9128997  10414009    **1,7,9,15,16**

List of preceding patches: 10, 15
Sites should use CHECK^XTSUMBLD to verify checksums.

  about the routine to return to.
=========================================================================
Installation:

   1.  During the installation, do not run any RPC-Broker-based Client/Server
       software (e.g., CPRS, PCMM, BCMA).  No Broker-based client/server 
       software should be running while installing this patch on the 
       server.  You can identify these jobs by checking the system status 
       and verifying if any XWBTCPC routines are running (i.e., Broker 
       Handler).  If you find any of these jobs running on the system,  
       notify users to logoff or FORCEX the jobs.  Active users may get 
                        
       NOSOURCE or CLOBBER errors.  
 
   2.  Stop the Broker Listener on the server.  Do this by first 
       checking the system status, then verifying if the XWBTCPL 
       routine is running (i.e., Broker Listener).  If you find this 
       routine running on your system, STOP IT.  To stop the Broker 
       Listener, do the following: 
 
           a.  Log into your M server.                   
           b.  Enter the following command at the M prompt: 
  When a READ or WRITE error occurs, the error trap code was trying to send 
 
               >D STOP^XWBTCP(Listener port) 
               (Typically, the Listener port is 9200) 

   3.  Stop any users that are using Broker applications. This applies
       to any job in XWBTCPC or in CPRS.
       
   4.  Broker routines are not usually mapped on systems that allow mapping.
       So, you will probably not have to disable mapping.

  an error message to the client. This caused an error, which resulted in a 
   5.  Use the Kernel Option 'INSTALL/CHECK MESSAGE' located on the 
       PackMan menu. This option will load the KIDS package onto your 
       system.

   6.  The patch has now been loaded into a Transport global on your
       system. Now you need to use KIDS to install the Transport global.
       On the KIDS menu, under the 'Installation' menu, use the following
       options:

          Verify Checksums in Transport Global
  second error being logged.
          Print Transport Global
          Compare Transport Global to Current System
          Backup a Transport Global

   7.  On the KIDS Installation menu, use the option Install Package(s).
       Respond to the prompts as follows:
       
       Select INSTALL NAME:  XWB*1.1*16
                             ==========
                             
TRACK PACKAGE NATIONALLY YES
BUILD COMPONENTS
  • ENTRIES:
    • XWBTCPL
      ACTION:   SEND TO SITE
      CHECKSUM:   B37040375
    • XWBTCPC
      ACTION:   SEND TO SITE
      CHECKSUM:   B36640281
    • XWBBRK
      ACTION:   SEND TO SITE
      CHECKSUM:   B33425977