Sun Mainframe Transaction Processing Software, Release 8.1.0
Updated User Documentation

This file contains updates to the user documentation
released with MTP 8.1.0. 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.

Important Operating Information

The format of the Sun MTP recovery file has changed in Release 8.1.0. 
If you are upgrading from a release earlier than Sun MTP 8.1.0, and you are 
planning to use the same $KIXSYS directory, you must delete the recovery file 
or move it out of the $KIXSYS directory. This will enable Sun MTP to create a 
new recovery file for the region at startup.

--------------------------------
MTP 8.1.0p2    -   120076-02
--------------------------------
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 to CR 6291187, which related to problems with Model 4 and 5 screen
   sizes, resulted in the following documentation changes:

   In the Sun MTP Reference Guide, in the section "xxxunikix - Specify a
   Client Keyboard," the syntax for the xxxunikix command shows an input
   parameter referred to as <parameter2>. This parameter and its description
   are not valid. 

2. A fix to CR 6230490, which fixed a problem where Sun MTP could ignore a
   "suspended" state of predefined terminals and printers, resulted in two new
   error messages.

   KIX3033E Preset userid %s for termID %s is suspended, cannot sign on

     Description: The specified user ID, which has been predefined for this
     terminal, is suspended in the Sign-on Table (SNT). This state renders the
     terminal unusable.

     Solution: To allow the terminal to connect, change the value of the 
     Suspended field in the SNT to N.

   KIX3034E Preset userid %s for printer %s is suspended, printer unavailable 

     Description: The specified user ID, which has been predefined for this
     printer, is suspended in the SNT. No transactions can be started at this
     device.	

     Solution: To allow transactions to be started at this printer, change the 
     value of the Suspended field in the SNT to N.

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

   When Sun MTP processes SNA 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
    automatcially 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.

4. 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.
 
5. Fixes to CR 6288197 and 6294643, 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.   

6. A fix to CR 6342774, which relates to the fix made in patch 1 for the Solaris
   ftok() function, resulted in a new error message.

   KIX3816I $KIXSYS/MTP_IPCKEY file exists and key is already in use. Key must
   be unique among regions.

     Description: This message indicates that the key file associated with the
     region you are trying to start is not unique.

     Solution: Contact your authorized service provider for assistance in 
     resolving this problem.

7. 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 as 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
     the replacement transaction processor 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.

9. A fix to CR 6358065 resulted in a new error message, which indicates if a
   user's account has expired. Previously, it was not clear whether the user's
   password or account had expired.

   KIX0542E Account expired for Userid %s  - consult Security Administrator

     Description: The account for the specified user ID has expired.

     Solution: You cannot correct this failure. Contact your security
     administrator who can take the appropriate action, such as reactivating 
     your account.
     
     There is a corresponding fix for Sun MSF (CR 6358029) that provides a
     new Sun MSF error message. Refer to  the Sun MSF 1.1.0, patch 1 patch 
     notes, which are located in the file <MSF-home>/docs/updated_user_doc.txt.

10. The following documentation was missing for the kixfile -p output message.
    (CR 6340258)

    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.
   
11. 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.


Enhancements

1. Sun MTP supports additional arguments for the EXEC CICS INQUIRE 
   API. (CR 6303553)

   EXEC CICS INQUIRE FILE
   EXEC CICS INQUIRE DATASET (provided for backward compatibility; DATASET is
     synonymous with FILE)

     DSNAME(data-area) - Returns the 44-character name of the VSAM dataset
     associated with the FILE definition in the format <environment-variable>
     <dataset-name>. For example, $VSAMDATA/ACCTFIL

     EMPTYSTATUS(cvda) - Full word binary field into which is returned the
     EMPTYREQ or NOEMPTYREQ value, depending on the value that was set by a
     previous SET FILE command. If there was no previous SET FILE command,
     NOEMPTYREQ is returned by default.

     REMOTENAME(data-area) - Returns the 8-character name by which the file
     is known in the region named in the REMOTESYSTEM option of its FILE 
     definition.

   EXEC CICS INQUIRE SYSTEM

     RELEASE(data-area) - Returns the 4-character field 0810. Because this 
     argument has been deprecated in CICS, this returned value will not change.

   EXEC CICS INQUIRE TERMINAL

     NETNAME(data-area) - Returns the 8-character network name of the terminal
     that is the object of the INQUIRE command.

     REMOTESYSTEM(data-area) - Returns the 4-character name of the connection.


--------------------------------
MTP 8.1.0p1    -   120076-01
--------------------------------

Important Operating Information

1. Sun MTP 8.1.0, with a minimum patch level of 1, is now supported on the
   Solaris(tm) 8 Operating System (OS). The following features of Sun MTP 8.1.0
   are not supported on Solaris 8 platforms:

   - Secure Socket Layer (SSL) clients

   An updated version of the kernel parameter information in the Sun MTP
   Configuration Guide can be found in the $UNIKIX/doc directory. The file is
   named kernelparams.pdf.

2. When an application abends, Sun MTP creates a dump file named <ttttnnnn>.prt, 
   where <tttt> is the abending transaction ID and <nnnn> is a sequence number. 
   If an abending transaction has a blank transaction ID, the default dump file 
   name is UNKN<nnnn>.prt. Sun MTP no longer names the default dump file 
   COBL<nnnn>.prt. (CR 4771261)

3. CR 6256162 was incorrectly documented as a known problem with ACUCOBOL-GT 
   in the Sun MTP 8.1.0 release notes. It is not a defect. Signal information is
   properly logged.

4. CR 6264805 - RRDS random reads (ACCESS MODE IS DYNAMIC or ACCESS MODE IS 
   RANDOM) fails was incorrectly documented as a known problem with ACUCOBOL-GT
   in the Sun MTP 8.1.0 release notes.

5. If you are using ACUCOBOL-GT, make sure to install the most current version
   of the software available from Acucorp.


Known Problems

1. On the Solaris 9 and 10 OS, a Sun MTP region with Sun MSF configured with an
   LDAP directory as a repository might fail to start. Note that this problem 
   also exists in the Sun MTP 8.1.0 release. (CR 6330673)

   This problem is caused by a known bug in the NSS libraries. (CR 6210080)

   To work around this problem, the superuser must configure the directories
   containing those NSS libraries as trusted directories using the "crle"
   command. For example:

     crle -u -s /usr/lib/mps
     crle -u -s /usr/lib/mps/secv1

2. The use of telnet sessions to debug ACUCOBOL-GT source programs is not 
   currently supported. Use an X Terminal for debugging. (CR 6319806)


Enhancements

1. Sun MTP now supports the DATAPOINTER option of the EXEC CICS FREEMAIN 
   command. (CR 6291818)

   The DATAPOINTER(ptr-value) option identifies the address of the main storage 
   to be released. This option specifies the pointer reference that was returned 
   by a GETMAIN command using the SET option. The length of storage released is 
   the length obtained by the GETMAIN. The DATAPOINTER and DATA options are
   mutually exclusive.

Fixed Problems

1. The following error message was inadvertently omitted from the Sun MTP 
   Message Guide:

   KIX4041I External Security: Invalid password constraints; %s

   Description: The password constraints (minimum and maximum length and format)
   returned from the external security manager are not recognized by Sun MTP.

     Solution: Contact your authorized service provider.

2. A fix for CR 4871215 has resulted in the following new error messages. This
   fix solves the problem where multiple $KIXSYS directories could have the same
   key value because the Solaris ftok() function does not guarantee a unique 
   return key.

   KIX7750E System call stat() returned error for %s

     Description: The stat(path, buff) function encountered an error with the 
     path parameter.

     Solution: Check for another message that provides additional details on the
     UNIX error encountered. If you need additional assistance, contact your
     authorized service provider.

   KIX7753E System call stat() returned error for %s file located in %s
      
     Description: The stat(path, buff) function returned an error for the file
     and path specified.

     Solution: Check for another message that provides additional details on the
     UNIX error encountered. If you need additional assistance, contact your
     authorized service provider.

   KIX7754E System call fopen() returned error for file %s located in %s
      
     Description: Unable to open .ipcinfo file located in the specified path.
      
     Solution: The region starts and runs properly, but system cleanup might be
     degraded if information could not be written to this file. Contact your
     authorized service provider.

   KIX7755E %s file contents invalid. Check contents for valid key between 1 and
   16,777,215

     Description: The $KIXSYS/MTP_IPCKEY file, which the user created and
     populated with a user-defined key, contains an invalid key.

     Solution: Inspect the file and replace the invalid key with a valid key.
     Contact your authorized service provider before editing this file. 

   KIX7756E Unexpected error, %d, returned from kxGetIPCKey()
       
     Description: An unexpected internal error was returned from the function
     kxGetIPCKey()
       
     Solution: This is an internal error. Contact your authorized service 
     provider.

   KIX7757W [%r] No KXDYVSM shared memory segment found for process

     Description: The system shared memory segment KXDYVSM address could not be
     found. Possible memory corruption has occurred.

     Cause: The process has attached to shared memory, but subsequent access has
     lost addressability to the shared memory segment.

     Solution: This is an internal error. Contact your authorized service 
     provider.

   KIX7758E [%r] No kxsm0 structure found for process
       
     Description: The system shared memory segment KXDYVSM was found and the
     kxdva_buffer structure was found, but the kxsm0 structure address could
     not be found.

     Solution: This is an internal error. Contact your authorized service 
     provider.

   KIX7759W [%r] Error getting $KIXSYS. Unable to read/write ipc info to file
       
     Description: $KIXSYS is not set or could not be found in the environment.
       
     Solution: Ensure that $KIXSYS is set. If problems persist, contact your
     authorized service provider.

   KIX7760W [%r] %s system call failed, errno = %d
       
     Description: The specifed system call failed with the UNIX errno specified.
       
     Solution: Contact your authorized service provider.

   KIX7761E [%r] No kxdva_buffer structure found for process
       
     Description: The system shared memory segment KXDYVSM address was found,
     but the kxdva_buffer structure address could not be found.

     Solution: This is an internal error. Contact your authorized service
     provider.     

3. A fix to CR 6249492 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 trace information and send it to your authorized 
     service provider for analysis. You can collect trace information from 
     your TN3270 client or from the region. Refer to the TN client documentation
     for information on collecting client traces. If you want to collect TN 
     trace messages from your region, and the region is not configured for 
     message tracing, you can update your configuration and try to reproduce 
     the problem.
     You must recycle the region for configuration updates to take effect. Refer
     to the Sun MTP Configuration Guide for TN server configuration for message
     tracing.

   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.

4. CR 6259037 - Passing parameters to an ACUCOBOL-GT standard batch program 
   fails, which was documented as a known problem in the Sun MTP 8.1.0 release
   notes, has been fixed.

5. CR 6235179 - ACUCOBOL-GT standard batch read with an alternate key fails
   was documented as a known problem in the Sun MTP 8.1.0 release notes. This
   was an ACUCOBOL-GT defect and it has been fixed.

6. A fix to CR 6285520, which related to the integration of Sun MTP with Sun MSF
   configured with an LDAP directory, resulted in the following operating
   information.

   If the following error message is issued:

      unikixstrt  :KIX4007E External Security: ld.so.1: unikixstrt: fatal: 
      /usr/lib/mps/secv1/(some NSS shared-object): open failed: No such file 
      or directory

      It indicates one of the following problems:

      - If your operating system is Solaris 8, the /usr/lib/mps/secv1 path name 
      is not valid. The path name to the NSS libraries must be added to the
      LD_LIBRARY_PATH environment variable in your region setup file.

      - If your operating system is Solaris 9 or 10, the NSS libraries have not 
      been properly installed where they belong at /usr/lib/mps/secv1. Contact
      your system administrator for assistance.

   See also item 1 under "Known Problems" listed above.
