Sun Mainframe Transaction Processing Software, Release 8.0.1
Updated User Documentation

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

Note: The acronym CR followed by a number stands for Change Request.

--------------------------------
MTP 8.0.1p9    -   117629-09
--------------------------------
Important Operating Information

This patch release has qualified Sun MTP with the DB2 UDB, Version 8.2 64-bit
server with the 32-bit client. (CR 6335284)

Fixed Problems

1. A fix was made to the kixfile utility to correct a problem where the second
   option (-r or -X) was ignored if the first option failed to change the
   dataset status. (CR 6313699) 

   As a result of this fix, a new option (-i) has been added to the kixfile
   utility, and there are several new error messages. The -i option and error
   messages are documented below. Refer to the Sun MTP Reference Guide
   for descriptions of the other options.

   kixfile Syntax

   kixfile {-f|o|b|l|d Y|N [-r Y|N|C] [-i] [-X VSTIME]} <dataset-name>
   kixfile {-p|-c [-X VSTIME]} <dataset-name>

   -i Indicates to kixfile to ignore the current status of the dataset when 
      setting a status, and to set the recovery status (-r), if it is specified.
      No error messages are issued about the dataset status. 

   For example, if the current status of the dataset is batch access only, 
   and the following command is executed:
     kixfile bY -rY DATA12
   A -2 error code is returned and the message KIX9153E is issued, because the
   dataset status is already set to batch access. Furthermore, recovery is not
   set on the file. However, if you use the new -i option as follows:
     kixfile bY -rY -i DATA12
   Recovery is activated for the dataset. A 0 return code indicates that the 
   command was successful, and no error message is issued.

   Note: If a code other than -2 or 0 is returned, the kixfile command
   is terminated abnormally and none of the command options are completed
   successfully.

   Error Messages

   KIX4911E kixfile: Mutually exclusive options were specified

     Description: Options that cannot be used together were specified on the
     kixfile command line.

     Solution: Correct the incorrect command line and resubmit the batch job.
     Refer to the Sun MTP Software Reference Guide for information about the
     kixfile syntax and usage.

   KIX4912E kixfile: Illegal combination of options were specified

     Description: The combination of options specified on the kixfile command 
     line cannot be used together. For example, if you specify the -p and
     the -r options on the same command, this message is issued.

     Solution: Correct the incorrect command line and resubmit the batch job.
     Refer to the Sun MTP Software Reference Guide for information about the
     kixfile syntax and usage.

   KIX4913I kixfile:  Recovery set to %s for dataset %8.8s

     Description: The recovery status for the specified dataset has been set to 
     the displayed value.

     Solution: Informational message; no user action is required.

   KIX4914E kixfile: No options were specified

     Description: No options were specified on the kixfile command line.

     Solution: Refer to the Sun MTP Software Reference Guide for information
     about the kixfile syntax and usage.

   KIX4915I Command Line: %s

     Description: Displays the kixfile command line. This message only appears 
     if the command contains a syntax error.

     Solution: Check for other messages that identify the syntax error. Refer to
     the Sun MTP Software Reference Guide for information about the kixfile 
     syntax and usage.

   KIX4916E kixfile: Option cannot be a stand-alone option

     Description:	An option, such as -r, -i, or -X, that must be used in
     conjunction with another option, has been used alone.

     Solution:	 Correct the incorrect command line and resubmit the batch job.
     Refer to the Sun MTP Software Reference Guide for information about the
     kixfile syntax and usage.

   KIX4917E kixfile: Invalid argument specified %s

     Description: One of the options on the command line uses an incorrect
     argument, which is displayed in the message.

     Solution: Examine the command line to locate the invalid argument. Correct 
     the incorrect command line and resubmit the batch job. Refer to the Sun MTP
     Software Reference Guide for information about the kixfile syntax and 
     usage.

   KIX9140E kixfile must be started as a batch job

     Description: The kixfile utility must be invoked from a script file
     submitted to Sun MTP as a standard batch job or as a Sun MBM batch job. 
     It cannot be executed from a command prompt.
     
     Solution: Refer to the Sun MTP Software Reference Guide for information
     about the kixfile usage.

   KIX9141E kixfile cannot establish signal handlers

     Description: An internal Sun MTP error occurred within the kixfile utility.
	
     Solution: Report this error to your authorized service provider.

   KIX9142E The dataset specified, %s, cannot be an alternate index

     Description: The dataset specified on the kixfile command line and shown
     in the error message is an alternate index. 

     Solution: The dataset specified must be the primary dataset of the cluster.
     Refer to the Sun MTP Software Reference Guide for information about the
     kixfile syntax and usage.

   KIX9143E kixfile: Invalid dataset specified %s

     Description: An invalid dataset name was specified on the kixfile command 
     line.

     Solution: Ensure that the dataset specified is valid for this region.
     Verify that the dataset name is spelled correctly and that the dataset is
     properly defined in the File Control Table (FCT) and VSAM catalog.

   KIX9144E kixfile: Dataset %s is disabled

     Description: The dataset specified on the kixfile command line is either
     disabled for batch access, or another process has it locked for exclusive
     control.

     Solution: Contact your Sun MTP administrator to determine the availability 
     of the dataset.

   KIX9145E kixfile: Unexpected error %d
	
     Description: An unexpected error occurred during the execution of the
     kixfile utility.

     Solution: Report this error to your authorized service provider.

   KIX9146E kixfile: Operation failed on dataset %s, see unikixmain.log for 
   more information
	
     Description: The kixfile utility encountered an error and cannot continue.
     This message is preceded by other messages in the unikixmain.log file that
     provide additional details about the problem.

     Solution: Examine the messages in the log file to determine the cause of
     the problem. Refer to the Sun MTP Software Reference Guide for more 
     information about the kixfile utility.

   KIX9147E kixfile: Dataset %s is already closed
	
     Description: The kixfile utility encountered a "close file" option (-f y)
     for a dataset that is already closed. If the command line contained an -r
     or -X option, those options are not processed.
     
     Solution: If you want to change the recovery state or display statistics
     on the dataset, edit the command line to add the -i option. Refer to the 
     Sun MTP Software Reference Guide for more information about the kixfile
     utility.

   KIX9148E kixfile: Dataset %s is already open

     Description: The kixfile utility encountered an "open file" option (-f n)
     for a dataset that is already open. If the command line contained an -r or
     -X option, those options are not processed.
	
     Solution: If you want to change the recovery state or display statistics
     on the dataset, edit the command line to add the -i option. Refer to the 
     Sun MTP Software Reference Guide for more information about the kixfile
     utility.
	
   KIX9149E kixfile: Process lock is not set for this batch job
	
     Description: The kixfile utility encountered an "unlock file" option (-l n)
     for a dataset that is not locked. If the command line contained an -r or
     -X option, those options are not processed.

     Solution: If you want to change the recovery state or display statistics
     on the dataset, edit the command line to add the -i option. Refer to the 
     Sun MTP Software Reference Guide for more information about the kixfile
     utility.

   KIX9150E kixfile: Process lock is already set for this batch job

     Description: The kixfile utility encountered a "lock file"	option (-l y)
     for a dataset that is already locked. If the command line contained an -r
     or -X option, those options are not processed.

     Solution: If you want to change the recovery state or display statistics
     on the dataset, edit the command line to add the -i option. Refer to the 
     Sun MTP Software Reference Guide for more information about the kixfile
     utility.

   KIX9151E kixfile: Read only for online is already set for this dataset %s

     Description: The kixfile utility encountered a "read only for online"
     option (-o y) for a dataset that is already set to "read only for online".
     If the command line contained an -r or -X option, those options are not 
     processed.

     Solution: If you want to change the recovery state or display statistics
     on the dataset, edit the command line to add the -i option. Refer to the 
     Sun MTP Software Reference Guide for more information about the kixfile
     utility.

   KIX9152E kixfile: Read/write for online is already set for this dataset %s

     Description: The kixfile utility encountered a "read/write for online"
     option (-o n) for a dataset that is already set to "read/write for online".
     If the command line contained an -r or -X option, those options are not 
     processed.

     Solution: If you want to change the recovery state or display statistics
     on the dataset, edit the command line to add the -i option. Refer to the 
     Sun MTP Software Reference Guide for more information about the kixfile
     utility.

   KIX9153E kixfile: Exclusive batch access is already set for this dataset %s

     Description: The kixfile utility encountered an "exclusive batch access"
     option (-b y) for a dataset that is already set to "exclusive batch 
     access". If the command line contained an -r or -X option, those options
     not processed.

     Solution: If you want to change the recovery state or display statistics
     on the dataset, edit the command line to add the -i option. Refer to the 
     Sun MTP Software Reference Guide for more information about the kixfile
     utility.

   KIX9154E kixfile: Batch and online access is already set for this dataset %s

     Description: The kixfile utility encountered a "batch and online access"
     option (-b n) for a dataset that is already set to "batch and online 
     access". If the command line contained an -r or -X option, those options
     are not processed.

     Solution: If you want to change the recovery state or display statistics
     on the dataset, edit the command line to add the -i option. Refer to the 
     Sun MTP Software Reference Guide for more information about the kixfile
     utility.

   KIX9155E kixfile: Read only permission is already set for this dataset %s

     Description: The kixfile utility encountered a "read only permission" 
     option (-d y) for a dataset that is already set to "read only permission".
     If the command line contained an -r or -X option, those options are not 
     processed.

     Solution: If you want to change the recovery state or display statistics
     on the dataset, edit the command line to add the -i option. Refer to the 
     Sun MTP Software Reference Guide for more information about the kixfile
     utility.

   KIX9156E kixfile: Original read/write permission is already set for this 
   dataset %s

     Description: The kixfile utility encountered an "original read/write
     permission" option (-d n) for a dataset that is already set to "original 
     read/write permission". If the command line contained an -r or  -X option,
     those options are not processed.

     Solution: If you want to change the recovery state or display statistics
     on the dataset, edit the command line to add the -i option. Refer to the 
     Sun MTP Software Reference Guide for more information about the kixfile
     utility.
	
   KIX9157I Usage: kixfile {-f|o|b|l|d Y|N} [-r Y|N|C ] [-i] [-X VSTIME] dataset
           or     kixfile {-p|-c [-X VSTIME] dataset
           the -f|o|b|l|d options are mutually exclusive
           the -r and -i options can only be used with one of the -f|o|b|l|d 
           options
	
     Description: This message is displayed when the kixfile utility encounters
     a syntax error.

     Solution: Check the error messages for the offending command and compare it
     to the usage message. Correct the command and resubmit the batch job. Refer 
     to the Sun MTP Software Reference Guide for more information about the 
     kixfile utility.

2. A fix to CR 6313250, which corrected deadlock problems that might occur
   during VSAM recovery, resulted in two new error messages:

   KIX1333W The recovery processor detected a deadlock during rollback, and is
   waiting for the offending transaction to detect this deadlock and abend.

     Description: During rollback on behalf of a failed transaction, the
     recovery processor detected a potential deadlock with an active transaction
     while attempting to acquire a resource, such a VSAM buffer. The recovery
     processor cannot react to this deadlock by backing out, as an active
     transaction could, therefore, it waits for the active transaction
     involved in its deadlock to detect it. When the active transaction
     detects the deadlock, it releases its buffer locks, which allows the
     recovery processor to continue its rollback processing on behalf of the
     original failed transaction.

     Solution: No user action is required at this time. If a high number of
     this type of deadlock occur, it might be necessary to investigate the
     cause.

   KIX1343E Transaction processor is terminating because of an error during
   commit.

     Description: An error occurred while the transaction is attempting to 
     commit its VSAM updates by flushing buffers. This error is typically
     preceded by a message that provides details of the error, such as KIX1334E.
     The transaction processor executing the transaction terminates with an exit
     status of 99. The Sun MTP main server process detects that exit, and
     rolls back the transaction.

     Solution: Examine the log file for other error messages preceding this
     error, and if necessary, take action based on those messages. Resubmit
     the abended transaction, if needed.

3. The following information was missing in the Sun MTP Reference Guide for the
   kixfile -p output message. (CR 2133757)

   The output message format for the recovery option should be:
     [RECOVOFF|RECOVON|CACHE+RECOVOFF]
   
   The keyword table should contain the following description for the
   CACHE+RECOVOFF keyword:
      Indicates that cache writes were specified for the dataset, and therefore,
      recovery is off. Refer to the Sun MTP Administrator's Guide for
      information about using cache writes with VSAM datasets.

4. The following information is a correction to the procedure "To Modify the
   Conversion Table File" in Chapter 11 of the Sun MTP Administrator's Guide.
   The module kxsyscnvtbl.c was missing from the command line. (CR 6341257)

   The correct command line in step 4 is: 

     4. Compile and link a new version of kixmakecnv:
        $ cc -o kixmakecnv kixmakecnv.c kxcnvtbl.c kxsyscnvtbl.c

--------------------------------
MTP 8.0.1p8    -   117629-08
--------------------------------
Important Operating Information

   Sun Mainframe Security Facility, Release 1.1.0 is now supported on MTP 8.0.1,
   with a minimum patch level of 8. Refer to the document "Sun Mainframe
   Transaction Processing Software Supplement for Sun Mainframe Security 
   Facility" for detailed information about this support, as well as operating 
   limitations.
   This document is located in the $UNIKIX/doc directory, and is named
   819-4890-10.pdf. (CR 6297118)

Known Problem

   If the Sun MTP region is running with semaphores, which is the default gating
   mechanism, and the region is configured with the Sun MTP high availability 
   data service for Sun Cluster, ensure that the following properties are set
   as described below, because an additional retry might occur. (CR 6349160)

   - The Sun Cluster Retry_count standard property must be set to a value of 2 
     (the default) or greater.
   - The PMF_Retry_Count extension property must be set to a value of 2 (the
     default) or greater.

   Refer to your Sun Cluster documentation for information on modifying 
   properties.

   If your region is running with mutexes, this problem does not affect you.
 
Fixed Problems

1. A fix to CR 6316125 resulted in the following documentation.

   When Sun MTP processes terminals that are to be autologged on, a default 
   20 millisecond (ms) delay ensures that each terminal is logged in properly. 
   If you want to increase the delay, set the KIX_SNACONNECTDELAY environment
   variable to a higher number. For example, if a 50 ms delay is desired, set
   KIX_SNACONNECTDELAY=50. Increase the delay value only if the default delay 
   of 20 ms is not sufficient and the region is experiencing problems with the
   terminal autologon sequence.

   New error message: 

   KIX0639I [%r] KIX_SNACONNECTDELAY cannot be less than 20. Setting to 20
   milliseconds. 

    Description: When Sun MTP processes terminals that are to be autologged on, 
    a default 20 millisecond (ms) delay ensures that each terminal is logged in
    properly.	If you tried to change this default value by setting the
    KIX_SNACONNECTDELAY	variable to a value less than 20 ms, Sun MTP 
    automatically enforces the 20 ms minimum. You can set KIX_SNACONNECTDELAY 
    to a value greater than 20 ms.

    Solution: Informational message; no user action is needed.

2. A fix to CR 6307393, which related to how the unikixbld utility handled an
   empty input file, resulted in the following new error message.

   KIX1940I Empty input sequential file specified for unikixbld with 
   '-p noreuse'.
   No processing performed

     Description: A unikixbld job using the '-p noreuse' option was executed to
     rebuild a VSAM dataset, and the input sequential file was empty. No
     processing has been performed on the VSAM dataset

     Solution: Informational message; no user action is needed.
 
3. Fixes to CR 6288197 and 2130567, which related to the handling of EBCDIC data
   from certain types of SNA clients, resulted in the following documentation.

   The Device field in the Terminal Control Table (TCT) 3270 Devices screen now
   supports a new value, RAWSNADV, which denotes a raw SNA device. When RAWSNADV
   is specified, Sun MTP handles requests from the client in the following way: 

	a. The first three bytes of an incoming datastream (which normally
       contain an AID key and cursor address) are ignored. 

	b. Block ASCII <-> EBCDIC conversion is performed when a datastream is
       sent to or received from the client. However, 3270 special orders and
       code are not subjected to special processing. They are simply converted
       and passed along.   


--------------------------------
MTP 8.0.1p7    -   117629-07
--------------------------------
Known Problem

Sun Mainframe Security Facility (Sun MSF) security server encounters an SQL
error when attempting to suspend a principal (CR 4968068)

This error occurs because the underlying RDBMS permissions for the 
"adapterUser" are missing. The user corresponding to the "adapterUser" must be
granted "update" permission to the "suspendedflag" column of the "Users" table.
The "grant" SQL can be done manually by an authorized database user using the
RDBMS product's tool. For example:

	grant update (suspendedflag) on Users to msf_user;

where:

suspendedflag: column name
Users: table name
msf_user: user name


Fixed Problems

1.  A fix to CR 6291187, which enables the xtermunikix shell script to
open a model 5 (132x87) window correctly, resulted in the following
documentation changes:

In the Sun MTP Reference Guide, Chapter 2 System Utilities, page 55
"xxxunikix - Specify a Client Keyboard".

    * Ignore the [Parameter 2] from the command line.

    * Ignore the paragraph describing Parameter 2.


--------------------------------
MTP 8.0.1p6    -   117629-06
--------------------------------
1. A fix to CR 6240120 resulted in a modified procedure for rebuilding the
   Sun MTP executables. This fix corrects a problem that prevented the use
   of customer-defined security user exits. The following procedure
   replaces the procedure in Chapter 11 of the Sun MTP Administrator's 
   Guide.

   o To Create a New Security User Exit Routine

   1. Change to the $UNIKIX/src/security directory.

   2. Copy the $UNIKIX/src/security/kxsec_exitsTMPL.c file to kxsec_exits.c.

   3. Using the editor of your choice, make the necessary changes to the
      $UNIKIX/src/security/kxsec_exits.c file.

   4. Create the user object file.

      $ make kxsec_exits.o

   5. If you are finished using the customizing tools and are ready to rebuild
      the required Sun MTP executables:

      a. Change to the $UNIKIX/src directory.

      b. Execute the following command:
         $ make security

         This command uses the makefile generated by kixinstall to build all the
         Sun MTP executables, as well as the executables that call the security
         user exit code.

      You have now changed the default security user exit routines.

2. A fix to CR 5065245, which relates to preset security, resulted in the
   following documentation changes.

   - The EXEC CICS SIGNON command now supports the following RESP2 value:
     INVREQ  11  This task's terminal has preset security.

   - The EXEC CICS SIGNOFF command now supports the following RES2 value:
     INVREQ  3  This task's terminal has preset security.

   - There are three new error messages:

     KIX3030E TermID %4.4s has preset security, sign on/off not allowed

       Description: An attempt to sign on or off has occurred on this
       terminal, and it has been denied. 

       Cause: In the 3270 Devices portion of the Terminal Control Table
       (TCT), this terminal has been configured with a user ID (OpUser ID
       field), which disallows sign on or off.

       Solution: Remove the user ID from the TCT entry, if user sign on or
       sign off is required for this device.

     KIX3031W Preset userid %8.8s for termID %4.4s not defined in SNT,
     default used

       Description: The user ID configured for this terminal in the 3270
       Devices portion of the TCT (OpUser ID field) has not been defined in
       the Sign-On Table (SNT). If you are using basic Sun MTP security, the
       OpUser ID defined in the TCT has been overridden with spaces and the
       default security key of 1 has been set. If you are using an external
       security manager (ESM), the OpUser ID defined in the TCT has been
       overridden with the KIXSECDFLTUSER value and its permissions have been
       set for this terminal.

       Solution: You must define the user ID in the SNT. Otherwise, the
       security profile for the default user is used.

     KIX3032W Preset userid %8.8s for printer %4.4s not defined in SNT,
     default used

       Description: The user ID configured for this printer in the UNIX
       Printers portion of the TCT (OpUser ID field) has not been defined in
       the SNT. If you are using basic Sun MTP security, the OpUser ID
       defined in the TCT has been overridden with spaces and the default
       security key of 1 has been set. If you are using an external security
       manager (ESM), the OpUser ID defined in the TCT has been overridden
       with the KIXSECDFLTUSER value and its permissions have been set for
       this printer.

       Solution: You must define the user ID in the SNT. Otherwise, the
       security profile for the default user is used.

3. CR 6244323, which related to the importing of duplicate operator names
   into the Sign-On Table (SNT), has been fixed.

   The Sign-On Table (SNT) allows you to import an snt.lst file that has 
   duplicate operator names (Operator Name field). Previously, you could enter
   duplicate operator names into the table, and export a table containing
   duplicates, but you could not import the .lst file back into the table.

   Note - The CSSN transaction uses the operator name and password to log users
   in to the region. As a result of this change, only the first occurrence of 
   the operator name is validated. Therefore, if your SNT contains duplicate 
   operator names, it is preferable to use the CESN transaction to log in. 
   The CESN transaction uses the User ID field and password to authenticate 
   the user.

4. CR 6260089, which related to terminal disconnects or timeouts sometimes 
   causing a transaction server to hang, has been fixed. As a result, a new 
   error message has been added.

   KIX3823E %s received the following signal %d at %s

     Description: The unikixmain server process has detected that the failed
     transaction processor handled the indicated signal number at the indicated
     date and time.

     Solution: Examine other log messages, which contain information about the
     signal and indicate whether administrative action is needed.

   Additionally, error messages KIX821 and KIX3822 were changed from I 
   (informational) type messages to E (error) type messages.

5. A fix to CR6249492 resulted in several new error messages. This fix
   corrects a problem where data passed to a STARTed transaction running on
   a terminal was not deleted if the STARTed transaction aborted.

KIX1850E The data associated with the START could not be removed: tranid
= <%4.4s>, termid = <%4.4s>

    Description: This message displays the transaction ID and terminal
    ID for the transaction invoked by the EXEC CICS START command. Sun
    MTP has detected that this transaction has either terminated
    abnormally before completing its RETRIEVE, or it has not done its
    RETRIEVE. When this situation occurs, Sun MTP attempts to delete the
    data associated with the START transaction. An error was encountered
    during this START data cleanup processing.

    Solution: This is an internal Sun MTP error. Run the kixsnap utility
    to take a snapshot and send this information to your authorized
    service provider.

KIX1851E Unexpected recoverable START encountered in cleanup
processing:tranid =<%4.4s>, termid = <%4.4s>, reqid = <%4.4s>

    Description: Sun MTP has detected that a STARTed transaction has
    either terminated abnormally before completing its RETRIEVE, or the
    STARTed transaction has not done its RETRIEVE. Furthermore, Sun MTP
    determined that the STARTed transaction is recoverable. Recoverable
    STARTs are not candidates for cleanup and Sun MTP should not have
    been performing cleanup processing for recoverable STARTs. The
    transaction ID, terminal ID, and request ID are displayed.

    Solution: This is an internal Sun MTP error. Run the kixsnap utility
    to take a snapshot and send this information to your authorized
    service provider.

KIX2531E Printer %.8s at %s disconnected with reason code %2.2d

    Description: A TN printer has disconnected because bad data was sent
    to it. The LU Name of the printer and the host name to which the
    printer is connected are displayed.

    Solution: Collect TN message traces for the region and send them to
    your authorized service provider for analysis. If your region is not
    configured for message tracing, you can update your configuration
    and try to reproduce the problem. Shut down the region. Update the
    $KIXSYS/unikixrc.cfg file to turn on message tracing. Restart the
    region. Then resubmit the transaction to capture the traces.

KIX2532E Printer %.8s at %s disconnected

    Description: A TN printer has disconnected for an external reason,
    such as a hardware failure. The LU Name of the printer and the host
    name to which the printer is connected are displayed.

    Solution: Try to determine why Sun MTP lost contact with the
    printer. You might have to contact your system administrator and
    provide the LU name of the printer and the host name in order to
    resolve the problem.

--------------------------------
MTP 8.0.1p5    -   117629-05
--------------------------------
None

--------------------------------
MTP 8.0.1p4    -   117629-04
--------------------------------
1. MTP now supports Oracle 10g (CR 5107829).

2. MTP now supports LU Type1 (SCS) printers (CR 5021365). In the Sun MTP
   environment, communication between the region and the LU Type 1 printer is
   managed by the TN3270 server.

   LU Type 1 printers are supported for data sent on the EXEC CICS SEND command.
   If you attempt to use other SEND commands, such as EXEC CICS SEND MAP or 
   EXEC CICS SEND TEXT, the output might be unintelligible.

   To Configure an LU Type 1 Printer

   1. Configure the TN3270 server. Refer to the MTP Configuration Guide for
      instructions on configuring the TN3270 server.

   2. Using a local client or TN3270 client, display the Standard Tables menu 
      by typing CTBL on a blank transaction screen, then pressing PF4.

   3. Open the TCT by pressing PF8, then press PF9 to display the 3270 Devices
      screen.

   4. On the 3270 Devices screen, press PF4 to display the Insert screen.

   5. Type values in the following fields for each printer you are defining:

     a. In the Term ID field, type the four-character identifier of the printer.
        This is the name of the printer as it is known to the application. It
        must be a unique name.

     b. In the LU Name field, type the logical unit name.

     c. In the Device field, type the value SCSPRINT. No other value is allowed.

   6. Press Enter to insert and validate the entry or entries.
      The Auto Log and In Svc fields are automatically filled in with Y(es).

   7. Press PF3 to return to the TCT menu.

   8. Press PF2 to save the changes to the disk.

   9. Press PF3 to exit the TCT.

  10. Exit Table Manager and restart the region so that your changes take 
      effect.

3. A fix to CR 4992004, which related to an unexpected region shutdown, resulted
   in a change to the text of error message KIX6694E. The changed error message 
   and description are as follows:

   KIX6694E Orphaned message found for terminal %s pid %d, discarded

    Description: Sun MTP has discarded an input message, typically a transaction
    request, sent by the specified terminal. The PID in the error message is the
    process ID of the terminal handler at the time the request was submitted.

    Cause: The terminal was disconnected after submitting the request, but 
    before Sun MTP could process the request and return a reply. If the terminal
    does not reconnect, if the terminal reconnects as a different identifier, or
    if the terminal reconnects through a terminal handler different from the one
    the terminal had originally connected through, Sun MTP discards the original
    terminal transaction request. New transaction requests from the reconnected
    terminal are processed.

    Solution:  Resubmit the transaction request.
     
4. The kixsnap utility has been enhanced to capture additional diagnostic 
   information.
   As a result, the utility takes longer to run. Please wait for the message
   that is displayed showing the name of the snapshot file to ensure that the
   kixsnap data collection has finished. (CR 6190308)

5. A debugging enhancement, which must be used under the direction of
   your authorized service provider, resulted in several new error
   messages. (CR 4650747)
      
    KIX3820E core file directory: %s
    
      Description: This message, which is written to the unikixmain.err file, 
      identifies the directory where the UNIX core file was written.
      
      Solution: Examine the core file to determine the cause of the problem, 
      or provide the file to your authorized service provider.
      
    KIX4719I Debug option to create user application core files is set
    
      Description: This message indicates that core files will be generated 
      under certain conditions when this debug option is set.
      
      Solution: Informational message; no user action needed.

--------------------------------
MTP 8.0.1p3    -   117629-03
--------------------------------
1. The internal sort utility sortx now sorts files greater than 2 gigabytes
   in size (BugId 5085758). If you are using Sun MBM with Sun MTP, and
   you are using sortx with files larger than 2 Gbytes, you must also upgrade 
   to Sun MBM, release 10.0.1 patch 3.
   
2. MTP 8.0.1 now supports Liant Open PL/I 7.4.8 with Oracle 9.x.


  
--------------------------------
MTP 8.0.1p2    -   117629-02
--------------------------------
1. The following kixview documentation replaces the description in the
   Sun MTP Reference Guide, which was incomplete (BugId 4950784).
   
   The kixview program displays the contents of a file in a dump format with 
   the hexadecimal representation of the contents on the left side of the
   display and the text contents on the right side of the display. kixview 
   can display both ASCII and EBCDIC files. For EBCDIC files, kixview converts
   the bytes into ASCII before displaying the file.
   
   Format:
   
   kixview [-e|-E] [-A conversion-table] <file1>, [<file2>, <filen>]

   where:
   
   -e|-E                  Specifies that the input files are EBCDIC files.
   -A <conversion-table>  Specifies the EBCDIC to ASCII conversion table to use.
                          If you are viewing EBCDIC files and do not specify a
                          conversion table, the default conversion table is 
                          used (IBM-1047 to ISO8859-1).
   <file1> [<file2>]      Identifies the names or full path names of the files.
                          If you are supplying multiple file names and
                          incorrectly type a file name, or type the name of a
                          non-existent file, kixview issues an error message 
                          and displays the next file in the list.

   To navigate within the file, position the cursor in either the hex or text
   display area. Then use the following keys to move the cursor:
   
   Key           Action
   j             Moves the cursor down one line.
   k             Moves the cursor up one line.
   l             Moves the cursor one character to the right.
   h             Moves the cursor one character to the left.
   Ctrl-f        Scrolls down by a full screen.
   Ctrl-b        Scrolls up by a full screen.
   Ctrl-d        Scrolls down by half a screen.
   Ctrl-u        Scrolls up by half a screen.
   L             Moves the cursor to the beginning of the last line on the
                  screen.
   H             Moves the cursor to the beginning of the first line on the
                  screen.
   ^             Moves the cursor to the beginning of the current line.
   $             Moves the cursor to the end of the current line.
   #             Moves the cursor to the beginning of the other screen
                  area. For example, if the cursor is in the hex area, it 
                  moves to the beginning of the text area. 
   %             Moves the cursor to the end of the other screen area. For
                  example, if the cursor is in the hex area, it moves to the
                  end of the text area.
   B             Moves the cursor to the first position in the file.
   G             Moves the cursor to the last position in the file.
   g             Displays the prompt File Position (hex). Type the hex value 
                  of the file position and press Return. The line containing 
                  the value is moved to the top of the screen.
   /             Displays the prompt (A)scii or (H)ex. Type the search pattern
                  and press Return. kixview searches forward in the file, and
                  moves the line containing the next instance of the value to
                  the top of the screen.
   ?             Displays the prompt (A)scii or (H)ex. Type the search pattern
                  and press Return. kixview searches backward in the file, and
                  moves the line containing the next instance of the value to
                  the top of the screen.
   n             Searches forward for the next instance of the search pattern.
   N             Searches backward for the next instance of the search pattern.
   Ctrl-L        Refreshes the screen display.
   e             Displays the prompt Edit File. Type the name of another file 
                  to view and press Return. You can specify only one file name.
   q             Quits kixview and returns to the command prompt.

   Note - When viewing EBCDIC files, kixview converts the input ASCII pattern 
          into EBCDIC before matching it with characters in the file.

2. The following message has been modified for clarity (BugId 5077890)

   KIX0462I Sign-on transaction CSSN/CESN cancelled
   
     Description: This message is displayed if you terminate either the CSSN 
     or the CESN transaction.
     
     Solution: Informational message; no user action is needed.

3. A fix to BugId 5078396 changed the size of the terminal buffer from 
   7,000 bytes per user to 32,000 bytes per user. The description for the
   following error message has changed:
   
   KIX0401T TIOA overflow 
   
     Description: The application attempted to send too much data to a
     terminal. The maximum amount of data that can be sent is 32,000 bytes.
     
     Solution: Modify your application program so that no more than 32,000
     bytes of data per SEND request is sent to a terminal.
   
--------------------------------
MTP 8.0.1p1    -   117629-01
--------------------------------
None
