Sun Mainframe Transaction Processing Software, Release 8.0.0
Updated User Documentation

This file contains updates to the user documentation
released with MTP 8.0.0. If there are no documentation
updates for a patch release, it is so noted.

--------------------------------
MTP 8.0.0p8    -   112750-08
--------------------------------
1. As a result of the enhancements to kixcontrol made in this patch release, 
   the documentation of the utility has changed. (BugId 4773956) The following
   replaces the description of the kixcontrol utility in the Sun MTP Reference 
   Guide.
     
   The kixcontrol utility is used to dynamically turn dumps and traces on and
   off. It provides options that also allow you to limit the scope of the
   trace to a transaction, terminal, program, dataset, or command.The 
   specialized trace options are designed to be used with the guidance of 
   support personnel to diagnose problems.
   
   Format:
   
   kixcontrol [-E] [-d {y|n}] [-T <transid>] [-R <termid>] [-P <program>] 
   [-F <dataset>] [-C <command>] [-A] [-N] [-S] [-h]
   
   -E            This option is to be used only under the direction of
                 technical support personnel.
                
   -d {y|n}      Enables or disables the generation of a formatted application
                 dump file. The <string> values are:
                
                    y: Generates a formatted application file when the runtime
                       system detects an error, when a program uses the EXEC
                       CICS ABEND command without a HANDLE ABEND command, or 
                       when errors, such as an out-of-storage condition, occur.
                       Default.
                    n: Does not generate a formatted application dump file.
                  
   -T <transid>  Traces only CICS API commands running in a specified
                 transaction.
                  
   -R <termid>   Traces only CICS API commands running on a specified terminal.
    
   -P <program>  Traces only CICS API commands running in a specified program.
    
   -F <dataset>  Traces only CICS API commands accessing a specified dataset.
    
   -C <command>  Traces only a specified CICS API command. 
    
   -A            Enables all CICS API tracing to the debug file.
    
   -N            Disables CICS API tracing.
    
   -S            Displays the current API trace settings.

   -h            Shows a detailed help screen with all of the possible CICS
                 commands that can be traced.
     
   The following are new error messages that relate to this enhancement:
      
     KIX4750E Transid must be between 1 and 4 characters long

       Description: The transaction ID specified with the kixcontrol -T option 
       must be one to four characters long.

       Solution: Resubmit the kixcontrol -T command with a transaction ID of the 
       correct length.

     KIX4751E Termid must be between 1 and 4 characters long

       Description: The terminal ID specified with the kixcontrol -R option  
       must be one to four characters long.

       Solution: Resubmit the kixcontrol -R command with a terminal ID of the 
       correct length.

     KIX4752E Program must be between 1 and 8 characters long

       Description: The program name specified with the kixcontrol -P option 
       must be one to eight characters long.

       Solution: Resubmit the kixcontrol -P command with a program name of the 
       correct length.

     KIX4753E Dataset must be between 1 and 8 characters long

       Description: The dataset name specified with the kixcontrol -F option 
       must be one to eight characters long.

       Solution: Resubmit the kixcontrol -F command with a dataset name of 
       the correct length.

     KIX4754E Command must be between 1 and 16 characters long

       Description: The CICS command specified with the kixcontrol -C option 
       must be one to sixteen characters long.

       Solution: Resubmit the kixcontrol -C command with a CICS command of 
       the correct length.

     KIX4755E Command %s is not supported

       Description: The CICS command specified with the kixcontrol -C option is 
       not supported by Sun MTP.

       Solution: Refer to the Sun MTP Developer's Guide for descriptions of
       all the supported CICS commands. You can also type the kixcontrol -h 
       command to see a list of supported CICS commands. Resubmit the command
       with a valid CICS command.

     KIX4756E Command %s is not a recognized CICS command

       Description: The command specified with the kixcontrol -C option is 
       not a CICS command.

       Solution: Refer to the Sun MTP Developer's Guide for descriptions 
       of all the supported CICS commands. You can also type the kixcontrol -h 
       command to see a list of supported CICS commands. Resubmit the command
       with a valid CICS command.

     KIX4757E Options -A and -N are mutually exclusive

       Description: The -A and -N options to the kixcontrol command cannot 
       be used together. The -A option enables all CICS API tracing, and the 
       -N option disables all CICS API tracing.
       
       Solution: Resubmit the kixcontrol command using either -A or -N.

     KIX4758E You cannot specify -A or -N options, with either of -T, -R, -P, 
     -C, or -F options

       Description: If you execute the kixcontrol command with either the 
       -A (enable all CICS API tracing) or the -N option (disable all CICS 
       API tracing), you may not specify the -T, -R, -P, -C, or -F options. 
       The -T, -R, -P, -C, or -F options are used to refine, or narrow, the 
       scope of the tracing.
       
       Solution: Resubmit the kixcontrol command with the correct options.

     KIX4759I All debug tracing has now been turned off

       Description: This message is issued after the kixcontrol -N command 
       is executed. It indicates that all debug tracing has been turned off 
       for the region.
       
       Solution: Informational message; no user action is needed.


--------------------------------
MTP 8.0.0p7    -   112750-07
--------------------------------
1. Sun MTP has been enhanced to support the use of TN3270 clients and 
   IBM 3270 terminals with source debuggers (Animator, CodeWatch, and 
   C language) to debug online programs. Refer to the Sun Mainframe 
   Transaction Processing Software Supplement for Debugging Online Programs 
   (part number 817-5679-10), which is included in the $UNIKIX/doc directory 
   of this patch release.(BugId 4933962)
   
2. Previously, the Debug Facility (CEDF) screens did not correctly display
   BMS extended attributes or DBCS characters on some 3270-type clients. 
   As a result of a fix to BugId 4860956, these attributes are now correctly 
   displayed. Refer to the Sun MTP Developer's Guide for information about 
   the supported BMS extended attributes.
   
   Note - If you are using the Sun MTP J3270 terminal emulator for debugging, 
   you must use a minimum patch level of 4 of Sun MTP J3270, Release 8.0.
   
3. If you are using or plan to use SSL (secure socket layer) functionality,
   follow these directions. Some information in the documentation is no longer
   valid. (BugId 4967428)
    
   - To acquire the SSL libraries, contact your Sun service provider to request
     the Sun-supported SSL libraries. (This replaces information in Chapter 1
     of the Sun MTP Installation Guide.)
     
   The following are new procedures for configuring a region for SSL clients. 
   (This replaces information in Chapter 11 of the Sun MTP Configuration Guide.)
   
   To Configure a Region to Accept SSL Requests
   
   1. Determine the listening port for the TCP/IP socket listener process, 
      unikixsock. You will need to use the -p <port-number> option to unikixmain 
      when starting the region to start the unikixsock listener process. 
      
   2. Determine the listening port for the SSL listener process, unikixssl. 
   
   3. Install the SSL libraries. 
   
   4. Set up the certificate databases. 
   
   5. Create or update the unikixrc.cfg file with the SSL entries. 
   
   6. Ensure that the installed SSL library directory is specified in the 
      LD_LIBRARY_PATH environment variable in your region's setup file. 
      
   7. Add the $UNIKIX/lib directory to the LD_LIBRARY_PATH environment variable
      so that unikixssl can access the SSL user exit library (libkxsslxit.so).
   
   To Start the Region and the SSL Server
   
   1. Make sure you have the appropriate values in the unikixrc.cfg file. 
   
   2. Source your region environment. 
   
      Make sure that the LD_LIBRARY_PATH environment variable contains the 
      installed SSL library directory and $UNIKIX/lib. 
      
   3. Start the region.
   
      You must specify the -p option on the unikixmain (kixstart) command to 
      start the socket listener. The port number must match the 
      SslServer*Sockport value in the unikixrc.cfg file. 
      
      You can optionally specify the -h option (to specify a host to which 
      the socket listener is bound). If you use the -h option, its value must 
      match the SslServer*Sockhost value in the unikixrc.cfg file. Refer to 
      the Sun Mainframe Transaction Processing Software Reference Guide for 
      information about the -h option.
      
      Refer to the Sun Mainframe Transaction Processing Software Developer's 
      Guide for information about using SSL.

4. A fix to BugId 4656934 changes how Sun MTP stores path names to VSAM files. 
   Now, the full path name to a VSAM file is stored in its file control block.
   This change means that if you are using Sun MBM, C-ISAM, or other clients
   to access VSAM files, you are not required to set an environment variable,
   such as KIXDATA, to point to the location of VSAM files. However, you must 
   still set a variable to point to the location of these files before starting
   the region.
   
   As a result of this fix, there are two new Sun MTP error messages:
   
   KIX0860I Dataset %s Path %s Opened
   
     Description: This message prints the dataset name along with the full path
     name of each dataset opened at region startup.
   
     Solution: Informational message, no user action is needed.
   
   KIX0861W %s environment variable mismatch between batch and MTP

     Description: The process (such as Sun MBM or C-ISAM) is trying to access a
     VSAM file that is located in the directory contained in the specified 
     environment variable (%s). The value of this environment variable does not
     match the value of the same environment variable that was defined when the
     region was started. The value of the environment variable defined at region
     startup will be used for processing.
     
     Solution: Do not set the environment variable in your client application
     environment, or make sure it matches the environment variable defined for 
     the region.
     
   The text of the following error messages has changed:
   
   KIX0426E
     Old: Releasing of dataset %14.14s failed
     New: Releasing of dataset %8.8s failed
     
   KIX0694E
     Old: Data set %14.14s could not be opened
     New: Data set %8.8s could not be opened
     
   KIX0695E
     Old: Dataset %14.14s specified as deferred open
     New: Dataset %8.8s specified as deferred open
     
   KIX0678E
     Old: Activity count error on cluster %8.8s, override status to deferred 
          open
     New: Activity count error on cluster %s, override status to deferred open
   

5. This release changes the behavior of socket client connections. The socket
   protocol specifies that the socket client connect and then send the initial
   socket message. If this initial send is never done, the socket remains in
   unikixsock's control forever, or until the socket client disconnects. This
   can cause the region to behave abnormally.

   The socket client behavior can be modified by setting the following new 
   environment variable before starting the Sun MTP region:

     KIXSOCKET_TIMEOUT=<n>  
    
   where <n> is a value in seconds and specifies the amount of time
   to wait for the socket data before disconnecting the client. For example:
   
     KIXSOCKET_TIMEOUT=10;export KIXSOCKET_TIMEOUT
   
6. Previously, the kixbms utility incorrectly generated the placement of the 
   named attribute fields in COBOL and PL/I copybooks. (BugId 4956681)

   For example, you might have coded your programs (PLI and COBOL) that address
   map attribute field names to compensate for this:

     MAP-ATTR OF MAP-FIELDI
        
   Now, if you regenerate the map copybook using kixbms, you will also need to
   change your program reference to map attribute fields. For example, you
   would have to change the above example to:
     
     MAP-ATTR OF MAP-FIELDO

   If you do not use the above style of qualified data-name referencing of 
   map attribute field names in PL/I or COBOL programs, regenerating a map
   copybook should not require any programming changes.


7. Some enhancements to the kixdump utility for support personnel resulted in 
   the following change to an error message (BugId 4825642):
   
     Old: KIX4702E Unable to dump structure %s to file %s
     New: KIX4702E Unable to dump %s information to file %s
   

8. A fix to BugId 4776795, which related to an unclear error message, resulted 
   in a change to the following error message:

   Old: KIX0390E [%r] UNIX error returned from getpwnam = %d
   New: KIX0390E [%r] UNIX error returned from %s = %d
   
   Description: The specified function was unable to read the entries in the 
   password file. The value of the %s variable is either the getpwnam function 
   or the getspnam function. The value in the %d variable provides additional 
   information. 
   
   Solution: Contact your operating system administrator.
   
9. A fix to BugId 4786532, which related to authenticating a UNIX user ID and
   password for a TN3270 client, resulted in the following new error message:
   
   KIX0396E [%r] Can't authenticate %.14s; no password from getpwnam/getspnam

     Description: Sun MTP is attempting to authenticate a UNIX user ID with the
     password supplied, but is unable to obtain that user ID's password with 
     the getpwnam or getspnam functions.
     
     Solution: This is an internal Sun MTP error. Contact your authorized
     service provider.


10. Documentation Errata (BugId 4945340)

    - Sun MTP Installation Guide - The Installation Guide for Release 8.0.0 
      stated, "If you are using Java(tm) programs, you must install the Java 
      Development Kit (JDK[tm]) and Server Express." This is incorrect. Server 
      Express is not required if your region does not use COBOL programs.
     
    - Sun MTP Administrator's Guide - In Chapter 1, the section "Sun MTP J3270
      Terminal Emulator Client" should state that the Sun MTP J3270 client
      can work on all modern Windows systems (such as Windows 2000, Windows ME),
      as well as Solaris, and any other platform that has a Java runtime
      environment (JRE).
     
11. Documentation Errata (BugId 4962042)

    In the Developer's Guide, the section "Performing Fast Writes From a Batch
    Program" should contain the following corrected text.

    You can also set the environment in the JCL using the Sun MBM EBMSYSCMD 
    statement as follows. You must then translate the JCL.

       //*EBMSYSCMD setenv FAST_UNIKIXVSAM ACCT1:ACCT2
       

12. The Sun MTP Developer's Guide does not provide adequate information on the
    response codes for the EXEC CICS CHANGE PASSWORD, EXEC CICS SIGNON, and
    EXEC CICS VERIFY PASSWORD commands (BugId 4969463).

    For EXEC CICS CHANGE PASSWORD, the response codes are as follows:

Condition     RESP2    Reason
-----------------------------------------------------------------------------
NOTAUTH       2        Current password is wrong.
NOTAUTH       19       Current password is suspended and ESMREASON is set 
                       to 901.
NOTAUTH       4        New password is greater than the maximum length;
                       ESMREASON is set to 902.
NOTAUTH       4        New password is less than the minimum length; ESMREASON
                       is set to 903.
NOTAUTH       4        New password value is identical to the old password
                       value; ESMREASON is set to 904.
NOTAUTH       4        New password is equal to the user ID; or it is all 
                       blanks; or the new password's format is unacceptable 
                       (non-numeric or non-alphabetic).
USERIDERR     8        User ID is invalid.
INVREQ        10       No terminal is associated with the task.

    For EXEC CICS SIGNON, the response codes are as follows:

Condition     RESP2    Reason
-----------------------------------------------------------------------------
NOTAUTH       2        Current password is wrong.
NOTAUTH       3        Current password has expired.
NOTAUTH       19       Current password is suspended.
NOTAUTH       4        New password is greater than the maximum length; new
                       password is less than the minimum length; new password 
                       value is identical to the old password value; new
                       password is all blanks; or the new password's format is 
                       unacceptable (non-numeric or non-alphabetic).
USERIDERR     8        User ID is invalid.
INVREQ        9        The terminal is already signed on.
INVREQ        10       No terminal is associated with the task.

    For EXEC CICS VERIFY PASSWORD, the response codes are as follows:

Condition     RESP2    Reason
-----------------------------------------------------------------------------
NOTAUTH       2        Current password is wrong.
NOTAUTH       3        Current password has expired.
NOTAUTH       19       Current password is suspended; ESMREASON is set to 901.
USERIDERR     8        User ID is invalid.
INVREQ        10       No terminal is associated with the task.


--------------------------------
MTP 8.0.0p6    -   112750-06
--------------------------------

1. When you execute the kixinstall utility, a check is now performed to ensure 
   that you are using a compatible version of the Solaris operating system 
   (BugId 4881866). If the version of Solaris is earlier than release 8, 
   the following message is displayed:
   
     FATAL - The minimum release supported by MTP is Solaris 8, exiting ...

2. Sun MTP requires the C language package provided by the OS vendor to be 
   installed. On Solaris, the package is typically /opt/SUNWspro. If there is 
   no C compiler, or if the C compiler reference in the PATH (current 
   environment) is /usr/ucb/cc, the kixinstall process will terminate. Make 
   sure that the reference to the compiler is properly set in your PATH. 
   (BugId 4836765) For example:
    
    PATH=/opt/SUNWspro/bin:$UNIKIX/local/bin:$UNIKIX/bin:$PATH;export PATH
    
3. Previously, the kixbms utility did not correctly handle maps containing the
   OUTLINE or SOSI extended attributes. (BugId 4891192)
   
   As a result of this fix, you must recompile the maps with the kixbms utility
   if they contain OUTLINE or SOSI extended attributes. 

4. Support for Micro Focus sequential files greater than 2 gigabytes in size.

   To enable the use of Micro Focus sequential files that are greater than 
   2 gigabytes in size, you must refer to the Server Express documentation for 
   file handler configuration information. 
   
5. In the Sun MTP Installation Guide, in Chapter 3, Step 6 in the section 
   "To Create a Setup File" should be changed to show the correct directory 
   for the $COBCPY environment variable. It should show the copybook 
   directory as cpylib (not copylib). (BugId 4899265)
   
6. The documentation does not state clearly that Micro Focus COBOL must be
   run in 32-bit mode to interface with Sun MTP (BugId 4888923).
   
   The Sun MTP Release Notes must state that COBOL must be run in 32-bit mode. 
   
   The Sun MTP Installation Guide requires the following changes:
   
   In Chapter 3, in the section "To Create a Setup File," Step 6 should be
   changed to show the addition of the environment variable COBMODE=32, to 
   indicate that COBOL must run in 32-bit mode.
   
   Also in Chapter 3, in the section "To Prepare Your Environment," Step 5
   should contain the following substeps:
   
      d. Verify that the COBOL working mode is 32-bit by typing the following 
         command:
         
           $ $COBDIR/bin/cobmode
           
         The following output should be displayed:
         
           Effective Default Working Mode: 32 bit 
         
      e. If your working mode is not 32-bit, you must either add the COBMODE
         environment variable to your region setup file, or execute the
         cobmode command. For example:
          
           To set the environment variable:
           
             COBMODE=32;export COBMODE
             
           To execute the cobmode command:  
         
             $ $COBDIR/bin/cobmode -s 32
           
         Note: Adding the COBMODE variable to your region setup file is the
         preferred method.
         
7. You can now use the COBOL Oracle sample application with ORACLE 9.2 32-bit,
   when 32-bit and 64-bit are installed. (BugId 4839469)
   
   Note: If both the 64-bit and 32-bit Oracle clients are installed, the 
   default COBOL pre-compiler "procob" is 64-bit. Oracle also provides a 
   32-bit version of the pre-compiler "procob32". "procob32" is the required
   pre-compiler for Sun MTP and Sun MBM. 
     
8. As a result of a fix to BugId 4933341, which prevents unauthorized access
   to VSAM files by Sun MBM batch jobs after a region restart, there are two 
   new error messages. This fix requires that you use Sun MBM 10.0.0 patch 7.
   
   KIX7600F [%r] Invalid transaction server identifier: previous id=%d, 
   current id=%d

     Description: This message is issued if a process attempts to access a 
     VSAM file, but the Sun MTP transaction server that is processing the 
     request is different from the transaction server that was assigned to
     serve the request. The message indicates that the transaction server 
     has died and a new transaction server was started in its place. The
     message also contains the process IDs of the previous and current 
     transaction servers.
   
     Cause: This situation can happen if the MTP region restarts while a 
     Sun MBM job that accesses VSAM files is running. The running job might 
     have additional steps that attempt to reuse the address space owned by 
     the previous transaction server.

     Solution: If the process is not a Sun MBM job, restart the process.
     If the process is a Sun MBM job, cancel the job and restart it.

   KIX7601F [%r] VSAM access denied for this process as associated transaction 
   server has been restarted

     Description: This message is issued if a process attempts to access 
     VSAM files after the transaction server that was associated with 
     its execution has died. The request for VSAM file access is rejected to 
     prevent data corruption, and the process is aborted.

     Solution: Restart the process to ensure that a new transaction server is 
     assigned to the process requesting VSAM access. The new transaction
     server will grant the access request.
     
9. A fix that addresses the possibility of running out of virtual memory 
   resulted in a new environment variable, KIX_PGMTXN_MODE, which can be set 
   to the value TXSERIES. This setting closes any C language application shared
   objects when the transaction ends. Note that this environment variable
   only affects C programs that are defined as type K in the Processing
   Program Table (PPT). (BugId 4952183)
   
   Also as a result of this fix, error message KIX5004I has been changed to 
   show the value of the KIX_PGM_MODE and KIX_PGMTXN_MODE variables. One of the
   following messages will be displayed if either of the variables is set:
   
     KIX5004I KIX_PGM_MODE is set to TXSERIES
      
       This message indicates a new copy of the C program (shared object) will 
       be loaded every time the program is executed, regardless if it is a new
       task or by the same task.
       
     KIX5004I KIX_PGMTXN_MODE is set to TXSERIES
     
       This message indicates that C programs (shared objects) will be released
       after every task.

10. The following enhancement has been made to kixsnap (BugId 4894389).

     The kixsnap utility will also execute the Sun MBM ebmsnap utility, if the
     the Sun MTP region is associated with a Sun MBM node.

11. A fix to BugId 4891345 resulted in the following new information:

    - A dataset that is defined as remote in the File Control Table (FCT) 
      will not be counted as an alias. A remote dataset contains a
      value in the SysID field on the Remote Characteristics screen of the
      FCT.
     
    - A dataset whose Filename field is blank in the FCT is not counted as an
      alias.

12. If you are using Sun MTP and Sun MBM together, and you find it necessary
    to completely restore the region's $KIXSYS directory from a backup, you
    must also resynchronize the subsystem and region so that they can 
    reconnect. After performing the restore, follow this procedure:
    
      a. Shut down the MTP region.
      b. In Sun MBM, start BAM.
      c. On the BAM main menu, choose option 3, Applications & Subsystems.
      d. On the Applications & Subsystems menu, choose option 4, Update a 
         Subsystem.
      e. Enter the number of the subsystem to update.
      f. On the Update menu, choose option 2, Change MTP Region.
      g. Type the path name of the $KIXSYS directory and press Return. If the 
         screen already displays the correct path name, just press Return.
      h. When the confirmation screen is displayed, press Return.
      i. Exit BAM.
      j. Restart the Sun MTP region. 
      
    The description for error message KIX1143E has been expanded to explain
    this situation. (BugId 4943259)
    
    KIX1143E This MTP system is not configured to connect to MBM 

      Description: This message indicates that the region cannot connect to a 
      Sun MBM subsystem. 

      Cause: This message can be issued for several reasons: 
       - No subsystem is configured for this region 
       - The $KIXSYS value is incorrect, for example, if you renamed the 
         $KIXSYS directory or relocated it 
       - You deleted the $KIXSYS directory and restored it from a backup, 
         which changed the inode of the $KIXSYS directory

      Solution: If the subsystem does not exist, create it in Sun MBM using BAM.
      If the subsystem does exist, but the $KIXSYS value has changed, you must 
      update the subsystem configuration by using BAM to change the Sun MTP 
      region. Refer to the Sun Mainframe Batch Manager Software Configuration 
      Guide for the procedures to create a subsystem and to change the Sun MTP 
      region.

13. A fix to BugId 4855655 resulted in two new informational messages, which 
    are written to the unikixmain.log file when the signal handler for a
    unikixtran process starts.
   
    KIX3821I Caught signal: signal=%d, code=%d, address=%s, sender pid=%d, 
    sender userid=%s

      Description: The signal handler process has caught a signal and this 
      message reports information about the sender of the signal.
     
      Solution: Informational message; no user action is needed.

    KIX3822I Sender process: pid=%d, ppid=%d, userid=%s, euserid=%s, name=%s

      Description: This message is only issued after message 3821I, if the 
      Sun MTP process has permission to get information about the sender 
      process. This message reports process information based on the process ID
      (pid value) reported in message 3821I.
     
      Solution: Informational message; no user action is needed.

    
14. If your Sun MTP region is configured to use WebSphere MQ and the Sun
    Mainframe Security Facility (Sun MSF), be aware that MQ requires that the 
    region user ID have permissions to access the queues, and therefore,
    permission to start the MQ trigger transaction. (BugId 4848441)
    
    For example, using the SecAdmin tool, run the following commands to
    create the resources and add them to the resource domain:
    
      crs,KIX_ATTACH_TRANS,KMQ1,MQ triggered Cobol transaction
      crs,KIX_ATTACH_TRANS,MQJV,MQ triggered JMS transaction
      ard,KIX_ATTACH_TRANS,KMQ1,MTPadminTransactions
      ard,KIX_ATTACH_TRANS,MQJV,MTPadminTransactions
      commit

15. As a result of improvements that relate to running COBOL Animator in a Sun
    Cluster environment, there are several new error messages. (BugId 4934678)
    
    KIX5104E Unable to suspend PMF monitoring for process %d. Reason: waitpid() 
    failed errno=%d
    
      Description: The transaction processor was not able to suspend PMF 
      monitoring in order to activate the Micro Focus COBOL Animator.

      Cause: The specified system call failed with the specified error number.
      
      Solution: Look up the UNIX error number (errno) in the system table to
      determine the kind of error that occurred, and the appropriate 
      corrective action.

    KIX5105E Unable to suspend PMF monitoring for process %d. Reason: exited 
    with status %d
    
      Description: The transaction processor was unable to suspend PMF 
      monitoring in order to activate the Micro Focus COBOL Animator. The 
      exit status is displayed.

      Solution: An additional message should be displayed indicating the 
      reason for the failure.

    KIX5106E Unable to suspend PMF monitoring for process %d. Reason: exited 
    with signal %d

      Description: The transaction processor was unable to suspend PMF 
      monitoring in order to activate the Micro Focus COBOL Animator.

      Cause: The Animator utility exited with the specified signal.

      Solution: Try again. If the problem persists, contact your authorized 
      service provider.

    KIX5107E Unable to suspend PMF monitoring for process %d. Reason: exec(%s) 
    failed errno=%d

      Description: The transaction processor was unable to suspend PMF 
      monitoring in order to activate the Micro Focus COBOL Animator.

      Cause: The Animator utility specified in the %s variable could not be
      executed.
      
      Solution: Look up the UNIX error number (errno) in the system table to
      determine the kind of error that occurred, and the appropriate 
      corrective action. For example, if errno=2, you must ensure that the
      specified utility exists.

    KIX5108E Unable to suspend PMF monitoring for process %d. Reason: fork() 
    failed errno=%d

      Description: The transaction processor was unable to suspend PMF 
      monitoring in order to activate the Micro Focus COBOL Animator.

      Cause: The fork() system call failed with the specified error number.

      Solution: Look up the UNIX error number (errno) in the system table to
      determine the kind of error that occurred, and the appropriate 
      corrective action.

16. The kixsecure utility has been removed from the product. The function it
    provided is handled in a different way. Therefore, ignore steps 17 and 20 
    in the procedure "To Build the Sun MTP Executables" in Chapter 3 of the
    Sun MTP Installation Guide. (BugId 4727184)
    
17. Due to an enhancement to the Sun MTP application dump facility, additional
    diagnostic information is included in the .prt file that is created when
    a transaction aborts: memory (local and shared) acquired by means of an 
    EXEC CICS GETMAIN call; the program stack in reverse order, displaying the
    program name, working storage, and COMMAREA (if present). (BugId 4912207)
    
    As a result of this enhancement, the documentation on the application
    dump facility in Chapter 13 of the Sun MTP Troubleshooting and Tuning Guide
    has changed. The changes are as follows:
    
    a. In the section "Application Dump Facility", in the list of items
       contained in the formatted dump file, add the following bullet item:

       - Program stack in reverse order.

    b. The unikixmain -D commands in the section "Enabling and Disabling the 
       Dump Facility" are incorrect. They should be unikixmain -D dy to enable 
       the dump facility and unikixmain -D dn to disable the dump facility.
         
    c. Add the following information at the end of the section "Enabling and 
       Disabling the Dump Facility":

         To enable the dumping of shared memory acquired by means of an 
         EXEC CICS GETMAIN call, you must set the environment variable 
         KIXGETMAINDMP. For example:

           KIXGETMAINDMP=1;export KIXGETMAINDMP

    d. In the section "Dump File Output" replace the first bullet item 
       ("The dump file displays..) with the following:

       - Working storage will be displayed for each program in the stack.
        
       - The COMMAREA will be displayed for programs that have been linked via
         an EXEC CICS LINK call.
        
       - The GETMAIN SHARED segments represent a region-wide list of memory 
         acquired by means of an EXEC CICS GETMAIN SHARED call.
        
       - The GETMAIN LOCAL segments represent a list of local memory acquired 
         by the transaction process by means of an EXEC CICS GETMAIN call.
        
    e. Replace CODE EXAMPLE 13-1, Dump File--COBOL, with the following:

--------------------------------------------------------------------------
10/29/2003  11:21:32.000  unikixtran0 Formatted Dump File

EXEC CICS ABEND called with ABCODE(NEST)

Transaction: NST9 has abended in Program: NESTABC
Failure occurred in Sun MTP code
CICS Command Level Trace:
      Function ABEND            CID# 00000086 Incomplete
      Function LINK             CID# 00000091 Condition Successful
      Function GETMAIN          CID# 00000090 Condition Successful
      Function GETMAIN          CID# 00000085 Condition Successful

Current address on heap     (36dd48)
Address of Shared Memory    (ee000000)
Address of Max Core         (ee000000)
Address of Threshold Memory (edf80000)

******************  Exec Interface Block   ******************
EIBTIME   0112131c              EIBSYNC   00
EIBDATE   0103302c              EIBFREE   00
EIBTRNID  NST9                  EIBRECV   00
EIBTASKN  0000002c              EIBSEND   00
EIBTRMID  C000                  EIBATT    00
DFHEIGDI  0000                  EIBEOC    00
EIBCPOSN  0004                  EIBFMH    00
EIBCALEN  0009                  EIBCOMPL  00
EIBAID    27                    EIBSIG    00
EIBFN     0e0c                  EIBCONF   00
EIBRCODE  000000000000          EIBERR    00
EIBDS                           EIBERRCD  00000000
EIBREQID                        EIBSYNRB  20
EIBRSRCE                        EIBNODAT  00
EIBRESP   00000000
EIBRESP2  00000000

*********************************   CWA   ********************************
No Common Work Area present

*********************************   TCTUA   ******************************
TCTUA LENGTH = 255
ee201ee0 00000000  20202020 20202020 20202020 20202020  *                *
ee201ef0 00000010  20202020 20202020 20202020 20202020  *                *
ee201f00 00000020  20202020 20202020 20202020 20202020  *                *
ee201f10 00000030  20202020 20202020 20202020 20202020  *                *
ee201f20 00000040  20202020 20202020 20202020 20202020  *                *
ee201f30 00000050  20202020 20202020 20202020 20202020  *                *
ee201f40 00000060  20202020 20202020 20202020 20202020  *                *
ee201f50 00000070  20202020 20202020 20202020 20202020  *                *
ee201f60 00000080  20202020 20202020 20202020 20202020  *                *
ee201f70 00000090  20202020 20202020 20202020 20202020  *                *
ee201f80 000000a0  20202020 20202020 20202020 20202020  *                *
ee201f90 000000b0  20202020 20202020 20202020 20202020  *                *
ee201fa0 000000c0  20202020 20202020 20202020 20202020  *                *
ee201fb0 000000d0  20202020 20202020 20202020 20202020  *                *
ee201fc0 000000e0  20202020 20202020 20202020 20202020  *                *
ee201fd0 000000f0  20202020 20202020 20202020 202020    *                *

*********************   GETMAIN SHARED MEMORY   **************************

LENGTH=10
ee1ff7c0 00000000  73737373 73737373 7373               *ssssssssss      *

*********************   GETMAIN SHARED MEMORY   **************************

LENGTH=10
ee1ff760 00000000  73737373 73737373 7373               *ssssssssss      *

**********************   GETMAIN LOCAL MEMORY   **************************

LENGTH=10
3656c8 00000000  6C6C6C6C 6C6C6C6C 6C6C                 *llllllllll      *

**********************   GETMAIN LOCAL MEMORY   **************************

LENGTH=10
364ae0 00000000  6C6C6C6C 6C6C6C6C 6C6C                 *llllllllll      *

******************************  PROGRAM STACK **************************

PROGRAM: NESTABC
WORKING STORAGE
36bcf0 00000000  20202020 20202020                      *                *

PROGRAM: NEST2L
WORKING STORAGE
36b390 00000000  20202020 20202020 4E455354 324C2020    *        NEST2L  *
36b3a0 00000010  20202020 20202020                      *                *

COMMAREA
COMMAREA LENGTH: 9
368e38 00000000  4E455354 354C2020 20                   *NEST5L          *

PROGRAM: NEST5L
WORKING STORAGE
3669f8 00000000  20202020 20202020 0000000A 20202020    *        ....    *

COMMAREA
COMMAREA LENGTH: 9
365cd0 00000000  4E455354 394C2020 20                   *NEST9L          *

PROGRAM: NEST9L
WORKING STORAGE
3669f8 00000000  20202020 20202020 0000000A 20202020    *        ....    *

COMMAREA
No commarea present

----------------------------------------------------------------------------
        

--------------------------------
MTP 8.0.0p5    -   112750-05
--------------------------------

1. A system performance enhancement (BugId 4881814) changes how Java(tm) 
   support is enabled for a region. Now, you must explicitly set the 
   following environment variable before starting the region. For example, 
   in your region setup file set:
    
       KIX_ENABLE_JAVA=YES;export KIX_ENABLE_JAVA

   The environment variable KIX_ENABLE_JAVA enables the use of Java programs 
   in the region. Setting it to YES causes the Java Virtual Machine (JVM) to 
   be loaded into the transaction processors.
    
   The old environment variable KIX_DISABLE_JVM should no longer be used. If
   it is set, it will be ignored.
    
2. Previously, unikixbld would build without error a VSAM dataset that had
   duplicates not allowed specified in the File Control Table (FCT) for 
   the alternate key dataset, even when duplicate alternate keys existed 
   in the input data. (BugId 4837179)

   Now, unikixbld recognizes the duplicate condition, stops the build, and
   writes error messages to the unikixmain.err file.

   For example:

------------------------------------------------------------------------------

04/08/2003 11:48:39 unikixbld0  :KIX9169E Duplicate alt key VSAM dataset:ACCTIX
   altkey dataset:ALT3
58 58 58 58 58 58 58 58 58 34 41 41 41 41 41 41   'XXXXXXXXX4AAAAAA'
41                                                'A...............'

41 41 41 41 41 41 41 41 41 30                     'AAAAAAAAA0......'

04/08/2003 11:48:39 unikixbld0  :KIX1169E [build] Build failed for VSAM Alternat
e Index
04/08/2003 11:48:39 unikixbld0  :KIX9169E Duplicate alt key VSAM dataset:ACCTIX
   altkey dataset:ALT2
47 52 45 45 4E 46 49 45 4C 44 20 20 31 30 30 30   'GREENFIELD..1000'
32                                                '2...............'

47 52 45 45 4E 46 49 45 4C                        'GREENFIEL.......'

04/08/2003 11:48:39 unikixbld0  :KIX1169E [build] Build failed for VSAM Alternat
e Index
-------------------------------------------------------------------------------

   A new message indicates the error condition:

     KIX9169E Duplicate alt key VSAM dataset:%s altkey dataset:%s
   
     Description: The specified VSAM dataset and the specified alternate
     dataset have duplicate alternate keys. The information that follows
     this error is a hex dump of the primary key and the corresponding
     alternate key that caused the error.
     
     Solution: Choose the action that best meets your needs:
       - Remove the duplicate records from the input and execute unikixbld 
         again.
         
       - If duplicates are required, change the file attributes in the FCT 
         and execute unikixbld again.

     
3. A fix to BugId 4826311, which solved a problem related to system
    transactions terminating unexpectedly, resulted in the following new 
    error message.

   KIX0434E [%r] UNIX wait() command was interrupted by signal %s
   
     Description: The transaction processor was interrupted by signal %s 
     while waiting for a child process to end. The transaction processor 
     was then aborted.
     
     Solution: Rerun the aborted transaction.


4. Fixes to BugIds 4860253 and 4860259 resulted in the following change to
   the heading of the NRFS report. An example of this report is shown in
   Code Example 6-1 in the Sun MTP Configuration Guide. The new heading is:
   
     Native Recovery File System for Sun MTP created by version <n.n.n>
     
   where <n.n.n> is a valid Sun MTP release. 

5. A fix to BugId 4840937 resulted in the following new error messages:

   KIX2608E :esipc: [%r] Socket Connection table FULL
   
     Description: Internal error.
   
     Solution: Send this error message and the corresponding kixsnap output
     to your authorized Sun service provider.
   
   KIX2609E :esipc: [%r] Malloc failure for Socket Connection table entry
   
     Description: Internal error.
   
     Solution: Send this error message and the corresponding kixsnap output
     to your authorized Sun service provider.
     
6. The following documentation replaces the example in the section "Where to
   Attach Sun MTP Shared Memory" in the "Configuration Guidelines" chapter of
   the Sun MTP Configuration Guide. (BugId 4850647) The incorrect example
   starts with the third paragraph, "For example, by setting ...," and ends
   with the kixdump output snippet.
   
   Sun MTP has the following internal fixed default definitions:
      KXTHRESHOLD = 3.5M (00380000 )
      KXMAXCORE   =  .5M (00080000 )

   unikixmain uses the internal default definitions, along with the -M t<value> 
   and -M c<value> arguments, to calculate the actual addresses shown in the 
   kixdump -M report according to the following rules. 
   
   Note - The -M t<value> is the specified threshold value; and the -M c<value> 
   is the specified max core value.

     For -M t<value>  (<value> can be a negative number)
      If specified: Threshold = <value> + (ee000000 - KXMAXCORE - KXTHRESHOLD)
      otherwise   : Threshold = (ee000000 - KXMAXCORE)

     For -M c<value>
     If specified: Max Core = Threshold + <value>
     otherwise   : Max Core = Threshold + KXMAXCORE

   Example 1: Neither the -M t<value> nor -M c<value> options are specified

     The kixdump -M output displays the following:
     -------------------------------------------------------- 
     Values of Shared Memory, Max Core, Threshold Memory
     Address of Shared Memory    (ee000000 )
     Address of Max Core         (ee000000 )
     Address of Threshold Memory (edf80000 )

   Example 2: A negative value for -M t<value> is specified. For example,
   unikixmain -M t-16M
   
     The kixdump -M output displays the following:
     -------------------------------------------------------- 
     Values of Shared Memory, Max Core, Threshold Memory
     Address of Shared Memory    (ecc80000 )
     Address of Max Core         (ecc80000 )
     Address of Threshold Memory (ecc00000 )

   Example 3: A positive value for -M t<value> is specified. For example,
   unikixmain -M t16M
   
     The kixdump -M output displays the following:
     -------------------------------------------------------- 
     Values of Shared Memory, Max Core, Threshold Memory
     Address of Shared Memory    (eec80000 )
     Address of Max Core         (eec80000 )
     Address of Threshold Memory (eec00000 )

   Example 4: A negative value is specified for -M t<value> and a positive
   value is specified for -M c<value>. For example, unikixmain -M t-32M -M c10M
   
     The kixdump -M output displays the following:
     -------------------------------------------------------- 
     Values of Shared Memory, Max Core, Threshold Memory
     Address of Shared Memory    (ec600000 )
     Address of Max Core         (ec600000 )
     Address of Threshold Memory (ebc00000 )

   Example 5: Positive values are specified for both the -M t<value> and 
   the -M c<value> options. For example, unikixmain -M t32M -M c10M
   
     The kixdump -M output displays the following:
     -------------------------------------------------------- 
     Values of Shared Memory, Max Core, Threshold Memory
     Address of Shared Memory    (f0600000 )
     Address of Max Core         (f0600000 )
     Address of Threshold Memory (efc00000 )

7. The documentation for CEDA DEFINE TRANSACTION in the MTP Administrator's
   Guide and for dfhusdup DEFINE TRANSACTION in the MTP Reference Guide
   incorrectly list the TASKREQKEY attribute keyword. This keyword should be
   TASKREQ. Also, the description for this keyword belongs in the main list 
   of DEFINE TRANSACTION attributes, not grouped with the MTP-specific
   attributes. (BugId 4800912)
   
8. The Release Notes for Sun MTP 8.0.0 contains confusing and incorrect
   information about the LD_LIBRARY_PATH environment variable. It should
   state that the LD_LIBRARY_PATH environment variable must include
   $UNIKIX/lib, otherwise the region will not start. (BugId 4873506)
   
9. For the Liant PL/I CodeWatch debugger to function correctly, the
   unikixtran executable must be located in either the $UNIKIX/local/bin 
   or the $UNIKIX/bin directory. (BugId 4881027)

10. In the Sun MTP Installation Guide, the following step should be added to 
    the procedure "To Prepare Your Environment" in the section "Building the 
    Sun MTP System Software." (BugId 4796258)

     6. Make sure that your path points to the Sun One C compiler. 

        At the command prompt, type:
         $ which cc

        If the command returns a directory path that points to a non-Sun 
        C compiler, such as UCB (Berkeley) or GNU, you must add the location 
        of the Sun One C compiler to the beginning of your $PATH statement.
       
11. The sections "Starting a Region With an RDBMS" and "Bypassing the RDBMS
    at Startup" in the Sun MTP Configuration Guide might be confusing in the 
    descriptions of the use of the -t option to unikixmain and the use of the
    KIXRDBMS_BYPASS environment variable. To clarify: There are no
    restrictions on the use of the KIXRDBMS_BYPASS variable with any of the
    unikixmain options. (BugId 4882940)
    
12. The section "UNIX Accounting" in the Sun MTP Administrator's Guide
    should be ignored. The information contained in it does not apply to
    the Solaris(tm) operating environment (BugId 4835208). Refer to the
    Solaris documentation for information about operating system accounting.
    
13. A fix to BugId 4872797, which related to the allocation of a tenth 
    user shared memory segment, resulted in the following documentation
    changes.
    
    Two changed error messages:
    
    KIX0210I [%r] Acquired %x (hex) bytes of shared memory (segment %d of 
    maximum %d )
    
      This message has been changed so that the %r variable displays 
      either "Sys" or "Usr", depending on whether the Sun MTP system or the 
      user application acquired the shared memory.

    KIX0208E [%r] memadr=%x ,memsz=%x
    
      This message has been changed where 'memsz' indicates the size of the 
      failed shared memory attach.

      The new description and solution are as follows:
      
      Description: Unable to initially attach or subsequently reattach the 
      shared memory segment of size 'memsz' at address 'memadr'. The %r 
      variable displays	either 'kxgetsm1' for the initial attach or 
      'kxgetsm2' for a subsequent reattach failure.

      Solution: There is a possible internal conflict between shared library 
      attaching and shared memory attaching, or there is some other internal 
      problem. Contact your authorized Sun service provider.

    In Chapter 4 in the Sun MTP Configuration Guide, the section "Shared 
    Library Usage" requires the following sentence at the end of the section:

      Sun MTP intercepts the errno 22 condition and outputs the error message
      KIX0208E.
          
14. A fix to BugId 4895329, which related to running Micro Focus Animator in
    a Sun Cluster environment, resulted in the following new error messages:
    
    KIX5100E  Failure to suspend PMF monitoring errno=%d
    
      Description: This message might be issued when attempting to run the 
      COBOL Animator in the Sun Cluster environment. It indicates that the 
      monitoring of the transaction process by the Sun Cluster Process 
      Monitoring Facility (PMF) could not be suspended in preparation for 
      animating the application program.
        
      Solution: Use the UNIX error number to determine the kind of error that
      occurred, and the appropriate corrective action. After performing the 
      corrective action, try animating the program again.

    KIX5102E SETUID failure errno %d
      
      Description: This message is issued when an attempt to run the COBOL
      Animator in a Sun Cluster environment fails.
      
      Cause: The process that sets the COBOL animation environment for the
      Sun Cluster environment must run as privileged user.
      
      Solution: Refer to the "Sun Mainframe Transaction Processing Software
      High Availability Data Service for Sun Cluster" document for information 
      about configuring your system to use COBOL Animator in the Sun Cluster 
      environment.

    KIX5103E System call failure errno %d
    
      Description: The UNIX system call used to suspend the PMF monitoring
      failed.

      Solution: Use the UNIX error number to determine the kind of error that
      occurred, and the appropriate corrective action. After performing the 
      corrective action, try animating the program again.


--------------------------------
MTP 8.0.0p4    -   112750-04
--------------------------------

1. The -M t<value> and -M c<value> options to the unikixmain command were
   incorrectly documented in the Sun MTP Configuration Guide, Message Guide,
   Reference Guide, and Troubleshooting and Tuning Guide. The correct usage 
   of the options require a space between the -M and the following argument. 
   For example:

     unikixmain -M t-1024M -M c10M 
     
2. If you are upgrading from an earlier release, you must recompile all C
    language programs that use the EXEC CICS INQUIRE TDQUEUE command. 
    (BugId 4861660)

3. An enhancement to control the initialization of static and external 
   variables for C language shared objects has resulted in the following
   documentation changes. (BugID 4851978)
   
   - A new environment variable, KIX_PGM_MODE, has been added. If KIX_PGM_MODE
     is set to KIX_PGM_MODE=TXSERIES, C programs (shared objects) will get 
     an inital image every time the program is invoked.
     
     If the C programs do not initialize the external and static variables 
     in the programs, use of this environment variable causes Sun MTP to
     load a fresh copy of the program each time it is invoked. 

     Note: Setting this environment variable might cause performance 
     degradation.
     
   - If you use the CEDA transaction or dfhusdup utility to define program
     resources, you can now use the RESIDENT option, which is implemented 
     only for C programs in the following way:
     
     If RESIDENT is set to YES, the shared object (program) remains attached 
     to the process.
     
     If RESIDENT is set to NO, every time the program is invoked, the shared 
     object is removed and opened.
     
     Note: This implementation of the RESIDENT option is unique to Sun MTP.
     It is different from the implementation on the mainframe or the
     implementation in TxSeries on open systems.
     
     For example, use the CEDA transaction to define program ABCD01 as non-
     resident:
     
       CEDA DEFINE GROUP(PAYROLL) PROGRAM(ABCD01) RESIDENT(NO)

   - A new message has been added:
   
     KIX5004I KIX_PGM_MODE=TXSERIES is set

       Description: The Sun MTP administrator has set the KIX_PGM_MODE 
       environment variable.
       
       Solution: Informational message; no user action is needed. 


4. Changes for BugId 4723916 resulted in two changed error messages and
   one new error message.

   Changed messages:

   a.  KIX3817E [%r] KIXBTCH directory does not exist %s
       has been changed to a warning type message: KIX3817W.

   b.  KIX3818E [%r] KIXBTCH is not set but the vct is configured for batch
       has been changed to a warning type message and VCT has been capitalized.
       A description of the message has also been added and the solution has
       been modified.
  
       KIX3818W [%r] KIXBTCH is not set but the VCT is configured for batch

         Description: The VCT contains a value for the number of batch jobs, 
         but the KIXBTCH environment variable has not been set. The region
         starts, but you will not be able to run Sun MTP batch jobs that
         are executed out of the $KIXBTCH directory.

         Solution: If you want to execute batch jobs, shut down the region,
         set the KIXBTCH environment variable in your setup file, source the
         setup file, and restart the region. If you do not plan to run batch
         jobs, open the VCT and change the value for the number of batch jobs 
         to zero, save the VCT, shut down and restart the region.

   New message:

       KIX3819W [%r] KIXBTCH directory time interval is invalid

         Description: The time interval set in the KIXBTCH environment
         variable uses an invalid format.

         Solution: Set the time interval correctly. Refer to the Sun
         Mainframe Transaction Processing Software Developer's Guide for
         information about configuring the batch environment.


5. The following security enhancement has been added to Sun MTP. (Bug 4777498)

   The RDBMS password in the System Initialization Table (SIT) will now be
   encrypted when you save the table to the disk. This ensures that users
   that have read permission to the sit.tbl file will not be able to view
   the database password.
   
   Note: Sun MTP will continue to support the old format of the table until
   the next major release of the software.
      

6. Improvements to Sun MTP recovery processing resulted in the following
   new error messages. (BugId 4829004 and 4788739)

   KIX5000E Resources held by unikixmain

     Description: Internal error.
     
     Solution: Contact your authorized Sun service provider.
     
   KIX5001E Transaction did not complete shutdown in %d seconds, killing all
   processes
   
     Description: During force shutdown or panic shutdown of the region, no
     transaction processors completed their tasks for up to the specified
     number of seconds. Therefore, the system killed all the processess.
     
     Solution: Contact your authorized Sun service provider.


7. The following error messages were corrected to omit unnecessary 
   capitalization. (BugId 4767251)

   KIX2587E TCT allocation failed due to all TCTs being previously assigned
   KIX2588E TCT allocation failed ErrorCode:%d

        
8. If an attempt is made to write to an ESDS file that is larger than 
   4 gigabytes, Sun MTP now returns an error to the calling program. 
   (BugId 4753426) 

   If the ESDS file is 4 gigabytes in size or greater, INVREQ is set and 
   RESP2 is set to 1.


9. The unikixbld utility has been enhanced to support all the 
   features of the record format for the mfrcdv format. (BugId 4791348) 

   unikixbld supports the mfrcdv format for the following:
     - multiple input files with the -m option (merge)
     - multiple output files
     - replace/reuse arguments 
        
   unikixbld no longer issues the fatal error message:

     KIX1228F -m option is only used for line, record or recordv format
  

10. A fix to BugId 4834342 resulted in the following new error messages.

    KIX5002I MTP process %s has not yet initialized

      Description: Process %s has not yet indicated that it has completed its
      initialization.

      Cause: Sun MTP expects the process %s to complete initalization very
      quickly. If this does not happen, multiple messages are printed at 
      certain time intervals and finally, the system is brought down. If the
      process is unikixrcv, these messages might appear with the KIX0773I
      messages until the crash recovery is completed.
     
      Solution: Informational message; no user action is needed.
 

    KIX5003E System shutdown flag is set, will not continue region startup

      Description: During startup, the system panic stop was set. Region
      startup is being stopped.
     
      Cause: This might occur because kixclean was executed.
     
      Solution: Make sure that multiple people are not trying to bring up 
      or shut down the region at the same time.

11. A fix to BugId 4799514 resulted in the following new error messages.  
    These messages provide information about terminals that cannot be logged 
    in to a region.

    KIX4901E %s - Terminal allocation failed for luname=%.8s, luname already
    allocated
   
      Description: A user tried to log in to the region using an LU name that
      has been assigned.
     
      Solution: Make sure to use a unique LU name.

    KIX4902E %s - Terminal allocation failed for luname=%.8s, termid=%.4s,
    luname already allocated
     
      Description: A user tried to log in to the region using an LU name that
      has been assigned.
     
      Solution: Make sure to use a unique LU name.

    KIX4903E %s - Terminal allocation failed for luname=%.8s, all terminals 
    are already allocated
   
      Description: A user tried to log in to the region but could not, because 
      all TCT entries are currently allocated.
     
      Cause: The maximum number of users, as specified in the VCT, has been
      reached.
     
      Solution: If your license permits, increase the number of users in the
      VCT and restart the region. Otherwise, you might need a license that
      allows a larger number of users.

    KIX4904E %s - Terminal allocation failed for luname=%.8s, termid=%.4s, all
    terminals are already allocated
   
      Description: A user tried to log in to the region but could not, because 
      all TCT entries are currently allocated.
     
      Cause: The maximum number of users, as specified in the VCT, has been
      reached.
     
      Solution: If your license permits, increase the number of users in the
      VCT and restart the region. Otherwise, you might need a license that
      allows a larger number of users.
     
12. The Configuration Utility (kixinstall) has been changed to enable the user
    to select client or server libraries when selecting MQ. (BugID 4854499)
    
    Now, on the Third Party Packages screen, if you select option 1, MQSeries,
    you are prompted to choose either client or server libraries.


13. A fix to BugId 4868780 resulted in the following new error message:

    KIX5005E MTP process type %s did not initialize, killing process id %d 
    and aborting the region

      Description: Process %s did not notify unikixmain that it had completed
      its initialization in the allotted time. 
      
      Cause: This might be caused if the process is in a loop or has aborted.

      Solution: Contact your authorized Sun service provider and provide the
      dump files.
      
14. There is a known problem with the Native Recovery File System (NRFS), which
    uses a raw file system for recovery (BugID 4860253). The NRFS feature is
    also being reevaluated under a variety of conditions for its usefulness 
    in the Sun MTP environment. Until this investigation and bug fix are
    complete, you must use the standard recovery file method rather than NRFS.
    Refer to the Sun MTP Configuration Guide for information about configuring
    for recovery.
    
    A future patch note will provide more information about the future
    direction of the NRFS feature.


--------------------------------
MTP 8.0.0p3    -   112750-03
--------------------------------

1. Sun MTP has been enhanced to include a new unikixmain (kixstart) 
startup option (BugId 4781305). The option is implemented as follows:

   -O TDINTRA=[NOEMPTY|EMPTY]
   
   Specifies whether recoverable intrapartition TD queues are to be 
   discarded at region startup. If the option is not specified, 
   the default is NOEMPTY.
   
   Valid arguments are:
   
     EMPTY - Indicates to discard the queues.
     
     NOEMPTY - Indicates that the records on the queues are to be 
     retained. This is the default.
   
   Three error messages have been added as part of this enhancement.

   KIX0730F Invalid -O option keyword: %s
   
     Description: An invalid keyword was specified on the command line.
   
     Solution: Resubmit the command using a valid keyword. Currently 
     TDINTRA is the only valid keyword.
     
   KIX0731F Invalid -O option usage: -O TDINTRA=[NOEMPTY|EMPTY]
   
     Description: There is a syntax error in the -O TDINTRA=<value> 
     option.
     
     Solution: Resubmit the command using the correct syntax, which 
     is displayed in the error message.
     
   KIX0732F Invalid value: %s for -O option keyword: %s
   
     Description: An invalid value was supplied to the -O option keyword.
     
     Solution: Resubmit the command using a valid value to the specified
     keyword. The supported values for the TDINTRA keyword are NOEMPTY 
     and EMPTY.
     
2. An enhancement to increase the limit on the number of shared buffers
that can be configured for a region (BugId 4790880), resulted in the
following changes to the documentation.

   - The VSAM Configuration Table (VCT) field for the number of shared
     buffers now allows users to enter a 6-digit value.
     
   - In the Sun MTP Administrator's Guide, Table 1-2, Sun MTP Resource 
     Definition Limits, indicated that the limit for VSAM buffers is 9,999.
     With this enhancement, the limit is now 999,999.
     
   - In the Sun MTP Configuration Guide, Table 4-4, VSAM Buffer Size Values,
     the sentence starting "Exceeding 256 buffers can adversely affect
     performance ...," should be deleted. With this enhancement, setting a
     higher number of VSAM buffers can significantly improve performance
     depending on your configuration.

3. Enhancements made to format the kixdump -v output (BugId 4738528) 
resulted in the following changes and additions to error messages.

   Changed messages:

   KIX0329E Unable to create trace file: %s, errno = %d

   has been changed to:

   KIX0329E Unable to create dump file: %s, errno = %d



   KIX0332I Trace dump directory is: %s

   has been changed to:

   KIX0332I Dump directory is: %s


   New messages:

   KIX4700E Dump file write error: fd = %d, errno = %d

     Description: Unable to write out dump file information for the file 
     descriptor referenced in message KIX4701I.

     Solution: Contact your authorized Sun service provider if this 
     continues to be a problem.


   KIX4701I ABORT dump written to file: %s, fd = %d

     Description: Informational message indicating that an internal dump 
     was written to file %s.

     Solution: You might need to provide this file to your authorized Sun
     service provider for troubleshooting if you continue to experience
     problems.
     
4. The kixsalvage utility has been enhanced to include a -T option, which 
   will dump records from all segments of a spanned VSAM file in parallel. 
   (BugId 4687385) 

   Note that the syntax of the kixsalvage command was incorrectly
   documented in the documentation (BugId 4824441).
    
   The corrected documentation is as follows:
   
   The kixsalvage utility scans and dumps all salvageable data from a 
   corrupted VSAM file to a new file or files. By default, the data is 
   written out in the Sun MTP recordv format. Refer to Chapter 3 in the Sun 
   MTP Administrator's Guide for a definition of the recordv format. As an
   alternative, use the -c option to specify the Micro Focus variable record
   output format. In both cases, you must sort the output file(s).

    kixsalvage [-s] [-v] datasetname
    
    kixsalvage [-2 | -c] [-T | -l size] [-v] [-r] [[-o outputfile]...]
               datasetname
      
    where:
    
    -2          Writes a 2-byte record header instead of the default 4-byte 
                record header. This option is incompatible with the -c option.
        
    -c          Writes the output file in the COBOL variable record format.
    
    -l size     Indicates the maximum length, in bytes, for an output file. 
                You can modify the size with G, K, and M, indicating GB, KB, 
                and MB, respectively. If you specify a value that is too
                small, you might end up with too many output files or exceed 
                the number of allowed output files.
                
                Note: The -l option is ignored if the -T option is used.
                
    -s          Performs a scan only to display the number of blocks and
                records that are salvageable. This enables you to determine 
                the number and size of output files that are required. 
                Use this information to determine if the file is worth 
                salvaging.
                
    -v          Activates the verbose flag. With the verbose flag set, the 
                program writes a line of data to the screen for each record 
                that is salvaged.
                
    -r          Converts the data to machine format. Only for use on reverse-
                byte systems.
                
    -T          Dumps all the file's data segments in parallel. When using the
                -T option, you must specify an output file (-o option) for each
                segment of the spanned file. If the count of output files is 
                not correct, kixsalvage terminates with an error. See Example 4
                below.
                
                Note: Do not use the -T option with the -l option.
                
    -o outputfile  Identifies the output file name(s); up to eight names. 
                   - If an output file name is not supplied on the command 
                   line, kixsalvage uses the name of the input dataset and
                   appends the suffix .slvgnnn. See Example 1 below.
                   - If an output file name is supplied on the command line,
                   kixsalvage uses that name.
                   - If kixsalvage has to generate additional output files, 
                   it adds the .slvgnnn suffix to the additional files. See
                   Example 2 below.
                   - If the -l option is used, and the number of output files
                   specified on the command line cannot hold the salvaged data,
                   kixsalvage generates additional files using the name of 
                   the last output file specified and appends the .slvgnnn
                   suffix to these additional files. See Example 3 below.
                   
                   Note: The format of the suffix is *.slvgnnn, where nnn is 
                   a 3-digit value from 000-999.
                    
    datasetname  Indicates the file name of the dataset to salvage. This 
                 parameter is required.
    
  Command-Line Examples
    
  The following command-line examples show how kixsalvage generates its
  output files:
  
     Example 1:
     
     kixsalvage ACCTFILE
     
     This command does not use either the -o or -l options. The kixsalvage
     utility generates the following output file using the dataset name:
     
       ACCTFIL.slvg000
       
     -------------------------------------------------------------------------
     Example 2:
     
     kixsalvage -l1M ACCTFIL
     
     This command does not use the -o option. The kixsalvage utility generates
     the following output files to hold the number of one-megabyte files 
     needed to dump the entire dataset:
     
       ACCTFIL.slvg000
       ACCTFIL.slvg001
       ACCTFIL.slvg002
       ACCTFIL.slvg003
       
     -------------------------------------------------------------------------
     Example 3:
     
     kixsalvage -l1M -oHIC1 -oHIC2 ACCTFIL
     
     This command does not have enough user-specified files to accommodate the
     number of one-megabyte files needed to dump the entire dataset. Therefore,
     the following output files are generated:
     
       HIC1
       HIC2
       HIC2.slvg000
       HIC2.slvg001
       
     -------------------------------------------------------------------------
     Example 4:
     
     kixsalvage -T -o /p1/HIC -o /p2/HIC \
                   -o /p3/HIC -o /p4/HIC \
                   -o /p5/HIC -o /p6/HIC \
                   -o /p7/HIC -o /p8/HIC \
                   ACCTFIL
                   
     This command illustrates the use of the -T option. In this example, the
     ACCTFIL dataset is a very large eight-segment spanned file. Each output
     file is directed to a different directory, which can be on a different
     disk or file system, as follows:
     
        /p1/HIC
        /p2/HIC
        /p3/HIC
        /p4/HIC
        /p5/HIC
        /p6/HIC
        /p7/HIC
        /p8/HIC
     
     When using the -T option, each segment of the spanned file is processed 
     by a separate process, which enhances performance.
     
     
     ------------------------------------------------------------------------


6. A fix to BugId 4790681 resulted in the following changes to the
description of the EXEC CICS ASKTIME command in the Sun MTP Developer's
Guide.

   a. The general description of the command should be as follows:
   
      ASKTIME updates the fields EIBDATE and EIBTIME in the EXEC interface 
      block with the current date and time. ABSTIME returns a double word 
      value that is the time, in milliseconds, since 00:00:00.000 hours on
      January 1, 1900 rounded to the nearest hundredth of a second.
   
   b. The following statement should be removed because it refers to
      non-Sun platforms:

        "On some platforms, the three least significant digits of this value
         (the milliseconds) are always zero."
    
      With the corrected code, the three digits might be zero but it will be
      because that is the time when the code executed, or as the result of
      rounding.
   
   c. The description of the COBOL ABSTIME specification was incorrectly
      documented as PIC S9(18) COMP-3. It should be PIC S9(15) COMP-3.


7. Fixes for BugId 4754207 resulted in changes to the README.doc file for
running the MQ-JMS sample application. If you are using the MQ-JMS Bridge, 
make sure to follow the directions in the README.doc file located in 
the $UNIKIX/test/mq/jms directory, and not the directions shown in Code 
Example 13-3 in the Sun MTP Developer's Guide.


8. A fix to BugId 4788700 related to VSAM recovery, resulted is a new error
message.

       KIX0774F Recovery server failed; commit/rollback no longer functional
       
         Description: The unikixrcv process has terminated unexpectedly. The
         region will be terminated immediately, and will need to be restarted 
         to roll back all in-flight transaction updates.
         
         Solution: Investigate what caused the unikixrcv process to terminate,
         and contact your authorized Sun service provider if a software error
         seems to be involved. Restart the region to roll back all updates
         for in-flight transactions.

9. The name and format of the kixsnap utility output has changed. 
(BugId 4800991) These changes affect the description of the kixsnap utility
in the Sun MTP Reference Guide. Note that the kixsnap command itself has not
changed.

   To ensure that the output of the kixsnap command contains all relevant
   information about the region, run the kixsnap command as the user ID of
   the user that started the region.
   
   The kixsnap utility now generates a file in one of the following formats,
   depending on the compression utility it finds on your system:
   
     snapshot.<mmdd_hhmmss>.zip
     snapshot.<mmdd_hhmmss>.tar.gz
     snapshot.<mmdd_hhmmss>.tar.Z
     
   When you execute the kixsnap command, a message indicating the location
   and name of the snapshot file is displayed. For example:
   
     $ kixsnap
     Writing snapshot to /users/payroll/sys/debugkix/snapshot.0226_083312.zip
   
   Note: When a system crash occurs, the kixsnap utility is executed
   automatically. However, it might not be able to display the directory and
   file name. You can search for the file in the $KIXSYS/debugkix directory, 
   the $KIXSYS directory, or in the directory specified in the KIXSNAPDIR
   environment variable, if you set that variable for your region.
   
   Make sure to send the snapshot file to your authorized Sun service
   provider for analysis. 

10. Fixes for BugId 4778121 and 4778124 for Sun MTP, caused the following 
changes to the Sun Mainframe Administration Tool User's Guide.

   Chapter 8, Resources Tab - Table 8-7, Language Types
   - In the Language column, PL1 has been changed to PL/I.
   - Two new language types can be displayed:
     - Batch - A Sun MTP-initiated batch program
     - Table - An application data table that can be the target of an
               EXEC CICS LOAD request


11. Information on CEMT INQUIRE display screens is missing from the Sun MTP
Administrator's Guide (BugId 4804283).

   - When executing the CEMT INQ transaction for tasks, such as 
     CEMT INQ TASK ALL, the User Status Table is displayed. 
     It contains the following fields:

     TrmID: Indicates the terminal identifier associated with the task
            (transaction. If blank, the transaction is not associated with 
            a terminal.
            
     Task#: Identifies the task number. Each task is assigned a unique 
            sequential number when it enters the system.
            
     TranID: Identifies the transaction.
     
     FacID: Identifies the facility. This is the terminal identifier for
            terminal-initiated tasks or the transaction identifier of the
            initiating transaction for asynchronously started tasks or
            triggered tasks.
            
     Init: Indicates the initiation type. One of the following values is
           displayed:
             E: Terminal
             T: Start
             D: Trigger (transient data queue)
             C: Remote system connection
             
     St: Indicates the current status of the task. One of the following
         values is displayed:
             RQ: On ready queue
             WB: Waiting for I/O buffer
             WR: Waiting for resource
             VI: VSAM idle
             ST: Executing status request
             ID: Idle
             EQ: On event queue
             IN: Connection to remote system in service
             OU: Connection to remote system out of service
             
     Request: Identifies the CICS command being executed
     
     File/Rsrc: Indicates the name of the file or resource being requested.
     
     RCD: Indicates the physical record number being requested.

   - When executing the CEMT INQ transaction for transient data queues, 
     such as CEMT INQ TDQUEUE ALL, the Destination Control Table information 
     screen is displayed. It contains the following fields:

     Queue: Indicates the name of the queue.
     
     Type: Indicates the queue type. One of the following values is displayed:
            EXTRA: Extrapartition queue
            INTRA: Intrapartition queue
            REMOTE: Remote queue
            
     Open: For extrapartition queues, indicates if the queue is open. Values
           are:
            Y: Queue is open.
            N: Queue is closed.
            
     Enabled: For all types of queues, indicates if the queue is enabled. 
              Values are:
               Y: Queue is enabled.
               N: Queue is disabled.
            
     Trigger: Indicates one of the following:
               Trigger level for intrapartition queues
               0 (zero) for other queues
            
     TranId: Indicates one of the following:
              ID of the transaction associated with an intrapartition queue
              Blank for other queues
            
     Term: Indicates one of the following:
            Name of the terminal associated with an intrapartition queue
            Blank for other queues


12. Enhancements to the kixdump utility, which is for customer support
purposes only, resulted in the following error messages. (BugId 4800956)

   KIX4702E Unable to dump structure %s to file %s

     Description: kixdump was unable to dump the specified structure 
     to file %s.
     
     Solution: Look for previous messages that might indicate the cause.

   KIX4703I Structure dump written to file: %s

     Description: The specified file contains the dump of the structure
     or structures requested in the kixdump command.
     
     Solution: Informational message. No user action is needed.

   KIX4704E -E and -r options are mutually exclusive 

     Description: When using the kixdump utility, you cannot use 
     the -E option with the -r option.
     
     Solution: Resubmit the command using the correct syntax.

   KIX4705E File is incompatible. kixsformat is version %d, file %s is 
   version %d

     Description: The kixsformat utility cannot format the specified file.
     
     Cause: The version of Sun MTP used to dump the file and the version
     of the kixsformat utility are incompatible.
     
     Solution: Use a version of the kixsformat utility that matches the 
     version of Sun MTP that was used to produce the file.


   KIX4706E File %s is not a structure dump

     Description: The file you are trying to format is not a dump file
     created by a Sun MTP utility.
     
     Solution: You can only use the kixsformat utility with dump files
     created by Sun MTP utilities. The kixsformat utility should only be 
     used under the direction of your authorized Sun service provider who 
     can guide you in producing a dump file.

   KIX4707E Error reading file %s, errno = %d

     Description: The system read command failed when reading the file %s.
     
     Solution: Check the UNIX errno table for the specified error number
     to determine the cause of the read failure.


   KIX4708E Invalid parameter, Usage: kixsformat <filename>

     Description: You used an incorrect parameter in the kixsformat
     command. The correct command format is shown in the message.
     
     Solution: Resubmit the kixsformat command with the name of the
     dump file as the only parameter.


   KIX4709E Unrecognized structure %s

     Description: You tried to dump an unknown structure as specified in
     the %s variable.
     
     Solution: Contact your authorized Sun service provider.


   KIX4710E Error writing structure dump header, errno = %d

     Description: The system write command failed when writing the header 
     record to the disk.
     
     Solution: Check the UNIX errno table for the specified error number
     to determine the cause of the write failure.


   KIX4711E %r Error writing structure dump, errno = %d

     Description: The system write command failed when writing a memory
     structure to the disk.
     
     Solution: Check the UNIX errno table for the specified error number
     to determine the cause of the read failure.


   KIX4712W File %s is an incorrect length %d, file length should be %d

     Description: The file size does not match its header information.
     The formatted output might contain unreliable data.
     
     Solution: Review the output to determine its accuracy. You might need
     to dump the file again.


13. Errata in the Sun MTP Administrator's Guide.
     
   - In Chapter 3, in the section "KSDS Files," the formula for calculating 
     the size of a KSDS index file should contain the following additional
     statement in step 3 for clarification:
     
     Round up the result of ((total number of records) / (number of records 
     per block)).
     
   - Code example 11-7, which shows a portion of the socket user exit, 
     contains an error. The third line from the bottom is:
     
     return(-1_;
     
     It should be:
     
     return(-1); 
     
   - In Chapter 11, the section "Security User Exit Routines" states that 
     you can write your own security exits by modifying the kxsec_exits.c 
     source file. Do not use this file, because remaking it could result in 
     a security breach. Instead, use the file kxsec_exitsTMPL.c to create 
     your own security user exits.
   
   - In Chapter 9, the section "To Set Up the Sybase Database" contains an 
     error in the computer-user dialog in Step 3. The line:
     
     isql> sp_changedowner superadmin
     
     should be:
     
     isql> sp_changedbowner superadmin
     
   - The following errors were found in the Glossary:
   
     The definition for entry-sequenced dataset (ESDS) should be: A
     variable-length VSAM file that contains data records in entry-
     sequential order.
     
     The definition for relative record dataset (RRDS) should be: A 
     VSAM dataset whose records are retrieved by the number of the 
     position they occupy in the dataset.
     
     In the Virtual Storage Access Method (VSAM) entry, RSDS should be RRDS.
     
     There are multiple entries for the term transaction routing.
     
     The definition for BMS should also indicate that it is an acronym 
     for basic mapping support.
     
14. Errata in the Sun MTP Configuration Guide.

   - In Chapter 4, "Determining Where to Attach Shared Memory," the fifth
     paragraph incorrectly shows the shared memory address. It should be
     "virtual address 0xEE000000 ..."
     
   - The following errors were found in the Glossary:
   
     The definition for entry-sequenced dataset (ESDS) should be: A
     variable-length VSAM file that contains data records in entry-
     sequential order.
     
     The definition for relative record dataset (RRDS) should be: A 
     VSAM dataset whose records are retrieved by the number of the 
     position they occupy in the dataset.
     
     In the Virtual Storage Access Method (VSAM) entry, RSDS should be RRDS.
     
     There are multiple entries for the term transaction routing.
     
     The definition for BMS should also indicate that it is an acronym 
     for basic mapping support.
     
15. Errata in the Sun MTP Developer's Guide.

   - The INQUIRE TRANCLASS syntax is missing a right bracket. The correct 
     syntax is as follows: 

            INQUIRE TRANCLASS(8-char data-value) 
            [MAXACTIVE(data-area)|ACTIVE(data-area)] 
            QUEUED(data-area) 

   - The ISSUE CONFIRMATION syntax is missing a left bracket. The correct 
     syntax is as follows: 

            ISSUE CONFIRMATION [CONVID(char-4)] [STATE(cvda)] 
            
   - In the syntax for SEND MAP, the MAPONLY option is missing a left bracket.
     It should be enclosed in brackets as follows: [MAPONLY].
     
   - The syntax and description for the SET TRANCLASS command contain errors.
     The correct syntax is as follows:

            SET TRANCLASS(8-char data value) MAXACTIVE(data-area) 
            [[USE](8-char target class name)]

      In the description, the USE option should be shown as:

            [USE](8-char target class name)

      The description is correct. However, it should include additional
      information. The complete description for [USE] should be:

        The transaction class from or to which transaction processors are
        reassigned. If not specified, KIXDFLT class is used. The [USE] keyword 
        is optional; the 8-character target class name can be used alone. This
        option is a Sun MTP extension to the API.

   - In the VERIFY PASSWORD syntax, 8 char should be char-8.
   
   - In Chapter 8, the last sentence of the section "Adding JVM Startup Options"
     incorrectly contained quotation marks. It should read as follows: 

         For example, you cannot specify -Djava.class.path=... or
         -Djava.library.path=.... 
         
   - Code Example 13-4 contains some extraneous right parentheses. A correct
     code example is as follows:
     
        * Declare a trigger queue and process for UNIKIXMQ2
        INITQ(UNIKIX.TRIGGER.QUEUE)                  + 
        TRIGGER                                      + 
        TRIGDATA('Trig data from UNIKIXMQ2')         + 
        TRIGTYPE(FIRST)                              + 
        PROCESS(KMQ2.TRIGGER.PROC) 
        
        DEFINE PROCESS('KMQ2.TRIGGER.PROC') REPLACE  + 
               DESCR('Invoke KMQ2 transaction')      + 
               ENVRDATA('Some environment for KQM2') + 
               USERDATA('Some data for KQM2')        + 
               APPLTYPE(CICS)                        + 
               APPLCID('KMQ2')
               
   - In Chapter 15, in the section "Using dfhusdup to Define and Report
     Resources," the second example should be separated into two boxes as
     follows:
     
      ----------------------------------------------------------- 
      |dfhusdup USD=READWRITE PAGESIZE=50 CMDFILE=load > loadout| 
      ----------------------------------------------------------- 
      The contents of the file load are: 
      ----------------------------------------------------------- 
      |*Resource definitions for Sales Department               | 
      |INITIALIZE                                               | 
      |.....                                                    | 
      ----------------------------------------------------------- 
      
16. Errata in the Sun MTP Message Guide.

   - Errors and clarifications in Chapter 1:   
   
     - The solutions for error messages 0127E and 0166E should be: 
     
         Contact your authorized Sun service provider.   
         
     - The description for error message 0416T should be: 
     
         The %s indicates the program that encountered the problem.   
         
     - The solution for error message 1245I should be: 
     
         If the process was aborted for other than a user request (where 
         %d is the value 15), contact your authorized Sun service provider 
         with logs.   
         
     - Error message 1584I should be: 
     
         1584I CEMT transaction terminated ShrLib = %s.   
         
     - In the description for error message 2326E, the word "progress" 
       should be "process."    
       
     - In the descriptions or solutions to error messages 2352E, 2353E, 
       2355E, 2370E, 2371E, and 2372E, the term "LU62" should be "LU6.2."
       
     - Error message 8602E should be: 
     
         8602E Job terminating abnormally with shutdown=%s interrupt=%s.   
         
     - Error message 8604E should be: 
     
         8604E Mismatch of buffers = %d.   
         
     - Error message 8606E should be: 
     
         8606E FastOpen Allocate failed = %d.
         
     - Error message 8623E should be: 
     
         8623E ERROR -- kixfocus child died. Exit code %d Signal %d.   
         
     - In the description for error message 9006I,  /O  should be  I/O.    
     
   - In Chapter 3, the error messages use the substitution symbols {0}, {1},
     {2}, and so on, rather than the symbols (such as %d or %s) used in other
     messages. The values of these symbols are message-specific.


--------------------------------
MTP 8.0.0p2    -   112750-02
--------------------------------

1. The Release Notes contained question marks rather than the appropriate text 
for the description of the kixbms -A enhancement (BugId 4783941). The first 
sentence of the "kixbms" section on page 10 of the Sun MTP Software Release
Notes (part number 816-5335-10) should be as follows:

A new option has been added to support the XINIT option of the DFHMDF macro.

2. The following sections in Appendix A of the Sun MTP Software Configuration 
Guide (Revenue Release version) incorrectly identify the keypad multiply key 
as a lowercase j (j). The correct symbol is the asterisk (*). (BugId 4778203)

NCD-101 Key Keyboards
VT-type Keyboards
Sun Keyboards
Default X Keyboards
Desktop Terminal Keyboards 

3. The following restriction applies when using a Sybase database (BugId 
4783228).

  A Sun MTP region connecting to a Sybase database can only provide Sybase
  interface support for either COBOL or C. If you need to access a Sybase 
  database from both C and COBOL programs, you must create two regions, 
  one for C and one for COBOL.

4. Added support for the INPUTMSG and INPUTMSGLEN options to the EXEC CICS 
RETURN command. These options are supported only when the TRANSID and IMMEDIATE 
options are also specified in the RETURN command. Other uses of the INPUTMSG 
and INPUTMSGLEN options have not been validated. (BugId 4769267)

  INPUTMSG(data-area) - The data to be passed to the transaction identified
  in the TRANSID option.
  
  INPUTMSGLEN(data-value) - Indicates the length of the data in INPUTMSG.

5. Added support for the EXEC CICS INQUIRE TSQUEUE command. Not all options are 
supported. The kixclt translator issues warning messages for unsupported 
options. (BugID 4769270)

  - The supported options are:

    LOCATION(cvda) - Returns a value indicating where the temporary storage 
    queue is located. A value of AUXILIARY means that the queue is in 
    permanent storage. A value of MAIN means that the queue is in main memory.
  
    NUMITEMS(data-area) - Gives the count of the number of items in the queue.
  
    RECOVSTATUS(cvda) - Returns the recovery status. A value of RECOVERABLE 
    means the queue is recoverable. A value of NOTRECOVERABLE means the queue 
    is not recoverable.
  
    TSQUEUE(data-value) - An 8-character name of the queue.
    
    START - Starts the browse operation.
    
    AT(data-value) - Used with the START option to identify the name of the
    resource that is the starting point for the browse operation.
    
    NEXT - Retrieves the next resource.
    
    END - Stops the browse operation.
  
  - If you are using Sun MTP Secure and an external security manager, note
    the following addition to Table 8-4 in the Sun MTP Administrator's 
    Guide. The TSQUEUE resource is subject to security checking. Therefore,
    it should be added to the table in the Resource Name column. The 
    EXEC CICS INQUIRE TSQUEUE command should be added to the Command
    column of the table, and Read should be added to the Permissions
    column.
  

6. Added support for options to the EXEC CICS INQUIRE TDQUEUE command. 
(BugId 4769346)

  In addition to the currently supported options, the following options are
  now supported:

  ATIFACILITY(cvda) - Supported for intrapartition TDQs only. Returns a value
  indicating whether a terminal is associated with the queue. The value
  NOTERMINAL means there is no terminal associated with the queue. The value
  TERMINAL means there is a terminal associated with the queue. The value
  NOTAPPLIC means that the queue is not an intrapartition queue.
  
  ATITERMID(data-area) - Supported for intrapartition TDQs only. If a 
  terminal is associated with the queue, returns the terminal's 4-character
  name. Otherwise, it returns blanks. The terminal name is defined in the
  Intrapartition Destinations screen of the Sun MTP Destination Control 
  Table (DCT). 
  
  INDIRECTNAME(data-area) - Sun MTP always returns blanks.
  
  IOTYPE(cvda) - Supported for extrapartition TDQs only. Returns a value
  indicating the queue's I/O type. The value INPUT means input. The value 
  OUTPUT means output. The value NOTAPPLIC means the queue is not an
  extrapartition queue.
  
  RECORDFORMAT(cvda) - Supported for extrapartition TDQs only. Returns a 
  value indicating whether the queue has fixed or variable-length records. 
  The value FIXED means fixed-length records. The value VARIABLE means
  variable-length records. The value NOTAPPLIC means the queue is not an
  extrapartition queue.
  
  RECORDLENGTH(data-area) - Supported for extrapartition TDQs only. 
  Returns the record length in bytes for queues with fixed-length records, 
  and the maximum record length for queues with variable-length records.
  
  RECOVSTATUS(cvda) - Supported for intrapartition TDQs only. Returns a 
  value indicating the recovery type. The value LOGICAL means the queue is
  recoverable. The value NOTRECOVERABLE means the queue is not recoverable.
  The value NOTAPPLIC means the queue is not an intrapartition queue.
  
  REMOTENAME(data-area) - Supported for remote TDQs only. Returns the
  4-character name of the remote queue. This is the value of the RmtName 
  field in the Remote Destinations screen of the DCT. If a remote queue 
  is not defined, blanks are returned.
  
  REMOTESYSTEM(data-area) - Supported for remote TDQs only. Returns the
  4-character name of the system where the remote queue is located. This 
  is the value of the SysID field in the Remote Destinations screen of the
  Destination Control Table (DCT). Note that the remote system must also be
  defined in the System Entries portion of the Terminal Control Table (TCT).
  
  The following option is not supported:
  
    RDBACK


7. The documentation for the EXEC CICS INQUIRE TASK and the 
EXEC CICS INQUIRE TASK LIST command (documented in the Sun MTP Developer's 
Guide) contains errors (BugId 4787620). The corrected documentation is as 
follows:

  INQUIRE TASK(data-value)
        [FACILITY(data-area)]
        [FACILITYTYPE(cvda)]
        [PROCESSID(data-area)]
        [RUNSTATUS(cvda)]
        [STARTCODE(data-area)]
        [TRANSACTION(data-area)]
        [USERID(data-area)]

  This command retrieves information about a specified user 
  task. User tasks are those associated with user-defined 
  transactions or with MTP-supplied transactions that are 
  usually invoked by an operator.

  FACILITY - Returns a 4-character string representing the 
  name of the facility associated with the named task. If the 
  task was initiated from a terminal, the name of the terminal 
  is returned. If the task was initiated by a destination 
  trigger level, the name of the associated transient data 
  queue is returned. Otherwise, a null value is returned.

  FACILITYTYPE - Returns a CVDA value indicating the type of 
  facility that initiated the task. Possible values are:

    DEST - task was initiated by a destination trigger level
    
    TASK - task was initiated by another task

    TERM - task was initiated from a terminal

  PROCESSID - Returns a 32-bit binary value indicating the 
  process id of the process (unikixtran) running the 
  transaction associated with the task. Sun MTP-specific option.
 
  RUNSTATUS - Returns a CVDA value indicating whether the task 
  is running. The only supported value is RUNNING.

  STARTCODE - Returns a 2-character string indicating how the 
  task was started. Possible values are:

    D  - DPL request. Program cannot issue I/O requests against 
         its principal facility, nor issue any syncpoint requests.
    DS - DPL request. Same as above, except program can issue 
         syncpoint requests.
    QD - Transient data trigger level
    S  - START command without data
    SD - START command with data
    TD - Terminal input
    QB - Batch request

  TASK - Specifies a task number, in 4-byte packed-decimal format.

  TRANSACTION - Returns a 4-character string containing the 
  name of the transaction (if any) associated with the task. 
  Blanks are returned if there is no associated transaction.

  USERID - An 8-character string identifying the user 
  currently associated with the task.

  The TASKIDERR condition occurs if the specified task cannot 
  be found.


  INQUIRE TASK LIST LISTSIZE(fullword binary data-area)
        [RUNNING]
        [SUSPENDED]
        [SET(pointer)]

  The INQUIRE TASK LIST command returns a list of user tasks as defined 
  to the system. Task states must be specified explicitly.
  
  LISTSIZE - Returns a fullword binary field giving the number of tasks 
  in the categories you included in your inquiry. Required parameter.
  
  RUNNING - Lists only tasks that are actually running (not suspended).
  This includes the issuing task.
  
  SUSPENDED - Lists only tasks that are currently suspended (tasks waiting
  for some event or condition). This excludes the issuing task.
  
  SET - Address of a list of 4-byte packed-decimal task numbers. Each entry 
  in the list identifies a task in one of the requested categories. If 
  there are no tasks in the requested categories, the SET pointer contains 
  a null value.
  
  Note: If neither RUNNING nor SUSPENDED is supplied in the command, all
  tasks are included in the task list.

8. A new environment variable is available for configuring the properties of
the Java(tm) virtual machine (JVM(tm)) used by the unikixadmin daemon. The
tuning options described in this section apply to very large Sun MTP 
configurations. (BugId 4770645)

   Tuning the unikixadmin Daemon for Large Sun MTP Configurations
   
   In certain cases, it might be necessary to define properties to the
   Java virtual machine used by the unikixadmin daemon. Typically, this
   occurs when the administration framework is enabled for a large Sun MTP
   configuration. A large configuration is defined as one consisting of
   several thousand resources, such as 5,000 programs or maps and 10,000
   endpoints.
   
     Defining Properties to the unikixadmin JVM
     
     When it becomes necessary to configure the JVM to support a large
     overhead, the ADMIN_JVM_OPTIONS environment variable is used to
     propagate options to the JVM instance created by unikixadmin. JVM 
     command-line options normally supplied as part of the "java" command
     can be specified by means of the ADMIN_JVM_OPTIONS environment variable.
     Include this environment setting in your region's setup file. If you
     are using multiple objects, make sure to separate the options with
     a space. Each option must be enclosed in single quotes as shown in
     the following examples.
     
     For example, to increase the size of the memory space used to hold 
     Java objects, you must define the size of the Java heap using the 
     '-Xms<n>' and '-Xmx<n>' options. For example, if the size of the 
     Java object pool must be increased to a maximum of 512 MBytes, set 
     the ADMIN_JVM_OPTIONS environment variable as follows:
     
       export ADMIN_JVM_OPTIONS='-Xmx512m'
       
     Configuring the Cache Life Span
     
     The unikixadmin daemon maintains a cache representing the Sun MTP
     resources under management. By default, the cache has a life span of 
     one second. After the cache life span has expired, the cache is
     considered to be stale and a subsequent request for data results in
     a cache refresh. In large configurations, the cost of performing the 
     cache refresh might be expensive. In this case, it is a good idea to 
     increase the life span of the cache. Determine the cache life span in 
     the following way:
     
       1. Calculate the total number of resources in the region (maps,
          programs, terminals, transactions, and so on).
       2. Round up the figure to the next multiple of 5,000.
       3. Use one second for each 5,000 resources.
      
     For example, if the region has 2,000 programs and maps and 5,000
     terminals, set the cache life span to a value of two seconds. To
     set the cache life span, use the cache_lifespan property of the JVM in
     the ADMIN_JVM_OPTIONS environment variable as follows:
     
       export ADMIN_JVM_OPTIONS='-Dcache_lifespan=2'
       
9. In previous releases of the software, an ABORT.prt file would be created
if a region terminated abnormally. Now, if a region crashes, the unikixmain
process executes the kixsnap command automatically, which gathers trace
and dump information. All the information that was written to ABORT.prt is 
now written to the kixsnap snapshot files, and the ABORT.prt file is no
longer created. (BugId 4777171) This software change caused the following
error message to change:

    KIX0157F Writing abort dump to $KIXSYS/ABORT.prt

    has been changed to 

    KIX0157I Executing %s command

      Description: The Sun MTP region is executing the UNIX command
      executable or script specified in the %s variable.
      
      Solution: Informational message; no user action is needed.
      
10. This release provides support for the Oracle(r) 9.2.0 client, and allows
you to run the Oracle RDBMS on a C language-only platform. (BugId 4784573)

11. Changes to the COBOL and C Primer setup files resulted in the
following changes (BugId 4789466).

    Each primer directory ($UNIKIX/test/primer/cobol and $UNIKIX/test/primer/C)
    now contains its own kixprimer setup file, which sets the environment for
    the sample application.
    
    The section "Defining a Region's Environment" in Chapter 2 of the Sun MTP
    Configuration Guide states that the kixprimer setup script is located in 
    the $UNIKIX/bin directory. This sentence should be removed.
    
12. A fix to BugId 4787102 requires a documentation addition. When 
configuring terminals in the 3270 Devices portion of the Terminal 
Control Table, be aware that the Host Name and Port Number fields 
on the Host & Port screen are applicable only for terminals that 
access the region by means of the TPS PU4/5 server software 
(unikixtrin process). These fields are ignored for all other 
terminal definitions.

13. The unikixmain process has been enhanced to handle signals (BugId 4765627).
This resulted in a new error message:

    KIX3830E Received signal [s%] when system was in [%s] mode
    
      Description: The specified signal was received when the system was
      in the specified mode. The modes are as follows:
      
         ABORT - Indicates that the region was in shut immediate mode.
         
         NORMAL, BATCH, QUIESCE, SHUT - Indicates the region mode.
         
         TRANS CLEANUP, MESSAGE CLEANUP, BUFFER CLEANUP, ROLLBACK - These
         modes indicate whether unikixmain was doing cleanup work for an
         aborted transaction processor.
         
       Solution: No user action is needed.

14. Enhancements to Sun MTP product resulted in the following new and 
changed error messages.

    New error messages:
       
    KIX7561I Killing process %d
     
      Description: The kixhashut utility is killing the specified process.
       
      Solution: Informational message; no user action is needed.
       
    KIX7562I Removing IPC %d %d 

      Description: The kixhashut utility is removing IPC [m|s|q] 
      <IPC id number>.
       
      Solution: Informational message; no user action is needed
       
    KIX7563I System shutdown was %s within normal shut down period

      Description: If %s is COMPLETED, then the region completed the
      transactions and the region is coming down. If %s is NOT COMPLETED, 
      some transactions are still being executed; they will be aborted.
       
      Solution: Informational message; no user action is needed

    KIX7564I System shutdown completed, check and release system resources 

      Description: The time allocated for the region to come down has 
      expired. Now force kill the process and remove any remaining 
      processes and IPC resources.
    
      Solution: Informational message; no user action is needed
       
   The following error message has changed:
    
    KIX8602E Job terminating abnormally with shutdown=%s interrupt=%s system=%s

      Description: The job was terminated with one or more of the following
      conditions being TRUE:

        shutdown=TRUE, if the region was brought down immediately or it 
        went into a panic state
          
        interrupt=TRUE, if a signal was sent to terminate the job
          
        system=TRUE if region was stopped.
        
       Solution: Internal error or operator-requested termination.
       
     KIX7504E kixdump did not have permission to send signal to unikixmain
     process, pid number [%d]

       Description: The user who executed kixdump did not have permission to
       find out if the unikixmain process exists.

       Solution: The kixdump utility must be submitted by a user who has
       the privileges to send a signal to the unikixmain process of the
       region. 
       
15. In previous releases of Sun MTP, the kixstop command did not properly
adhere to the normal shutdown and immediate (panic) shutdown process.
(Bug Id 4809230)

With this fix, any command to bring down the region normally (kixstop, 
CEMT PERFORM SHUT, and PF3 on the main menu) will wait for all  
transactions to complete before bringing down the region. If there is a 
long-running transaction or a conversational transaction, the region will
wait until these transactions are finished. At this point, the only way 
to bring down the region is to execute the kixclean command.

If you want the old functionality of either kixstop (which forced the region to
stop by aborting running transactions), CEMT PERFORM SHUT, or PF3
(where these commands immediately shut down the region), you must use one of
the following commands:
   - kixstop -i
   - CSMT SHUT,YES
   - CEMT PERFORM SHUT IMMEDIATE
   
As a result of this fix, the following sections in the Sun MTP Administrator's
Guide and Configuration Guide are no longer accurate.

   In the Administrator's Guide, in Chapter 2: 
   
   - In the section "CSMT," the description of the CSMT SHUT,YES transaction
     should be "Shuts down the region and forces all the users to log off.
     Active transactions are rolled back."
     
   - In the section "Setting the System State," the CEMT SET SYSTEM SHUT
     and CEMT SET SYSTEM SHUT IMMEDIATE transactions are not implemented.
   
   In the Configuration Guide, in Chapter 3:
   
   - In the section "Shutting Down the Sun MTP Server," the description of 
     step 1 ("Invoke the CEMT PERFORM SHUTDOWN transaction ..."), should be
     "Transactions that are active will be allowed to complete normally. 
     No new transactions are allowed to be submitted. No new users can 
     log in."


--------------------------------
MTP 8.0.0p1    -   112750-01
--------------------------------

1. Added support for the KEYLENGTH(data-area) and KEYPOSITION(data-area) 
   parameters to the EXEC CICS INQUIRE FILE command. (BugId 4744167)

2. New error message (BugId 4751419)

KIX0557W Both "-A" and "-B" specified in MTP startup parameters. Possible 
conflict.

Description: Warning message indicating that you used both the -A and -B 
             options to unikixmain (or kixstart) when starting the region.

Cause: When a DBCS conversion table file is specified at region startup 
       (using -B), the first 256 entries in the file represent the single-byte
       character set (SBCS) conversion characters. Therefore, if you also 
       specify the -A option, the SBCS conversion table built from the DBCS
       file will be overwritten. This can cause a mismatch between the 
       double-byte and single-byte character sets.

Solution: Do not use both the -A and -B options when starting a region.

3. Documentation did not include information about compiling C++ programs. 
   (BugId 4767661)

The Sun MTP application run unit is built using the C compiler and loader. If 
an application program is written in C++, you must use the C++ compiler (usually
the CC command), and the required loader to build shared objects that can be
loaded by the transaction servers. The include files provided in the 
$UNIKIX/src/CICS_structures directory are the same for C++ programs.

For example, to build a C++ shared object from the acct00.ccs program, execute 
the following commands:

        kixclt acct00.ccs
        CC -Bdynamic -Kpic -c -Xt -I$UNIKIX/src/CICS_structures -o acct00.o
                 acct00.c
        ld -G -o acct00.so acct00.o

4. Improved error messages to provide information about a region's classpath 
   and library path settings. (BugId 4627246)

KIX0539I has been changed to write the following types of messages to the 
unikixmain.log file:

10/16/2002 10:25:37 unikixtran0 :KIX0539I Java ClassPath has these entries:
10/16/2002 10:25:37 unikixtran0 :   /pkgs/MTP8.0.0/lib/dfjcics.jar
10/16/2002 10:25:37 unikixtran0 :   /pkgs/MTP8.0.0/lib/transMQJMS.jar
10/16/2002 10:25:37 unikixtran0 :   /pkgs/MTP8.0.0/lib/transutil.jar
10/16/2002 10:25:37 unikixtran0 :   /opt/mqm/java/lib/com.ibm.mqjms.jar
10/16/2002 10:25:37 unikixtran0 :   /opt/mqm/java/lib/com.ibm.mq.jar
10/16/2002 10:25:37 unikixtran0 :   /opt/mqm/java/lib/jms.jar

KIX0540I has been changed to write the following types of messages to the 
unikixmain.log file:

10/16/2002 10:25:37 unikixtran0 :KIX0540I Java LibPath has these entries:
10/16/2002 10:25:37 unikixtran0 :   /pkgs/MTP8.0.0/lib
10/16/2002 10:25:37 unikixtran0 :   /opt/mqm/java/lib

5. If you want to write your own security exits, as documented in the Sun 
Mainframe Transaction Processing Software Administrator's Guide, you must use
the source file kxsec_exitsTMPL.c, not kxsec_exits.c. Using (and remaking) the
kxsec_exits.c file (which is the one the documentation says to modify) can 
cause unpredictable errors, and might cause a security breach. (BugID 4760779)

6. Fix to BugId 4753378 removes the restriction described in the Release Notes 
for Release 8.0.0 in the section "User ID Restriction for Batch Jobs With an
ESM Enabled", which contained information about 'kixfile' and 'unikixbld'
requiring KIXSECDFLTUSER to have resource permissions to run.

7. Fix to BugId 4758504 eliminates the known problem on the CBCH transaction 
that was described in the README file that shipped with Release 8.0.0.

8. Fix to BugId 4768957 eliminates the known problem related to unikixstrt 
permissions that was described in the README file that shipped with 
Release 8.0.0. Follow the procedures in the Sun Mainframe Transaction 
Processing Software Installation Guide for setting the permissions on 
unikixstrt.

9. Change to software changes how resource names are prefixed when using 
Sun MTP Secure and an external security manager. (BugId 4763941)

Previously, the application name configured in the System Initialization Table
(SIT), was used as the prefix on all ESM resource access check calls. Because
this approach was incompatible with how CICS prefixes resource names with its 
ESM (RACF), customers with existing CICS/RACF-prefixed resource names would
not be able to directly migrate to MTP Secure (ESM). The change made in this
fix uses the UNIX user ID that started the region as the prefix and adds a "."
to it to form the resource name prefix.

10. If your region contains .lst files for the SNT, PCT, PPT, and FCT that were 
created with versions of Sun MTP prior to this release, AND you do not use 
groups, do not import the .lst files into this release. To ensure that your
.lst files work with this release, do either of the following:

 - In the Table Manager, open each of these tables and export them using
 this release of the software.
        
 OR
        
 - Open each of the existing .lst files (snt.lst, pct.lst, ppt.lst,fct.lst) 
 in a text editor. Locate the group name field. If it does not contain a 
 group name, type at least one space between the back-to-back commas. Do this
 for each entry. Then save the .lst file. Examples are as follows:
        
 In the snt.lst file, the group field is the fourth from the left:
 aaabco,aaabco,abc,,F~YkoiqvotH_\,8000000000000000,0f0f3f,hi ,D,88,,X,11984,N
 Correct it to:
 aaabco,aaabco,abc, ,F~YkoiqvotH_\,8000000000000000,0f0f3f,hi ,D,88,,X,11984,N

 In the fct.lst file, the group field is the eighth from the left:
 TEMPSTG,TEMPSTG,KIXSYS,VSAM,KSDS,C,V,,Y,N,N,,0,0,
 Correct it to:
 TEMPSTG,TEMPSTG,KIXSYS,VSAM,KSDS,C,V, ,Y,N,N,,0,0,

 In the pct.lst file, the group field is the 11th from the left:
 BATCH000,,CBCH,0,1,DEF,N,0,,,,Y,,KIXDFLT
 Correct it to:
 BATCH000,,CBCH,0,1,DEF,N,0,,, ,Y,,KIXDFLT 

 In the ppt.lst file, the group field is the sixth from the left:
 BATCH000,B,,,,,,,F,
 Correct it to:
 BATCH000,B,,,, ,,,F,

(BugId 4744995, and duplicate bug 4744609)

11. Fix to BugId 4738818 resulted in improving two existing error messages and 
adding two new messages to better inform the user about possible problems when
attempting to display a mapset.

  KIX0404T Map set %s unable to load from disk.
  
   Description: Sun MTP was unable to load the physical mapset specified by
   the CICS command from disk.
  
   Solution: Ensure the KIXMAPS environment variable is correct, and check
   that the file is on disk and is not empty.
  
  KIX0405T Map set %s not found in PPT.
  
   Description: The mapset specified in the CICS command does not have an
   entry in the Processing Program Table (PPT).
  
   Solution: Define the mapset in the PPT.
  
  KIX0438T Map set %s is currently disabled.
  
   Description: The mapset specified in the CICS command has been 
   disabled.
  
   Solution: Enable the mapset using the system transaction 
   CEMT SET PROGRAM <mapset> ENABLED.
  
  KIX0439T Map set %s user not authorized to load this map
  
   Description: External security is active and the
   current user does not have the required permissions to load the 
   specified mapset.
  
   Solution: If you want this user to be able to access the mapset, 
   grant the user the required permissions.

12. Fixes to the kixcnvtbl80 utility resulted in the following documentation 
changes. (BugId 4776256)

  Installation Guide - Migrating Tables (page 36)

   To Convert Tables

     Remove step 2 (Delete unikix.dir and its contents, if it exists.)
     Remove step 3 (Delete rdo.dir and its contents, if it exists.)
     Remove step 6 (Re-apply unikix or rdo changes)

    kixcnvtbl80 will now convert the unikix.dir and rdo.dir subdirectories
    automatically if they exist, so the above steps are not necessary.

  Reference Guide - kixcnvtbl80 - Convert Tables (page 22)

   Remove the following lines:
     kixcnvtbl80 creates the $KIXSYS/unikix.dir and $KIXSYS/rdo.dir 
     if they do not already exist.

   This no longer occurs. Those directories are created automatically
   when the region starts, so kixcnvtbl80 does not need to do it.
    
