Sun Mainframe Transaction Processing Software, Release 7.2.0
Updated User Documentation

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


--------------------------------
Sun MTP 7.2.0p12   -   112271-12
--------------------------------

1. 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.
   
2. 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.
      
3. Enhancements to the kixdump utility resulted in the following new error
   messages (BugId 4825642):
   
   KIX4713I There is no transaction class information to dump for this region

     Description: Because there are no transactions classes defined for this 
     region in the Transaction Class Table (TXC), there is no transaction class 
     information to dump when the kixdump -r txc command is executed.

     Solution: Informational message; no user action is needed.

   KIX4714I There is no socket information to dump for this region

     Description: Because the region was not started with the unikixsock socket
     processor (kixstart -p option), there is no socket information to dump when
     the kixdump -r skt command is executed.

     Solution: Informational message; no user action is needed.


   KIX4715I There is no WebSphere MQ information to dump for this region

     Description: Because the region is not configured with WebSphere MQ, there 
     is no MQ information to dump when the kixdump -r mq command is executed.

     Solution: Informational message; no user action is needed.


   KIX4716E Invalid kixdump -r option %s

     Description: You specified an invalid option to the kixdump -r command.
     
     Solution: Refer to message KIX4717I for kixdump -r usage information.


   KIX4717I Usage: kixdump -r %s

     Description: This message always follows message KIX4716E and displays the
     usage of the kixdump -r command.

     Solution: Retry the command with a correct option.

   The following error message has changed:
   
     Old: KIX4702E Unable to dump structure %s to file %s

     New: KIX4702E Unable to dump %s information to file %s
   

--------------------------------
Sun MTP 7.2.0p11   -   112271-11
--------------------------------

No documentation updates


--------------------------------
Sun MTP 7.2.0p10   -   112271-10
--------------------------------

1. A fix to BugId 4884735 makes it a requirement to set the LD_LIBRARY_PATH
   environment variable before starting the Sun MTP region. The 
   LD_LIBRARY_PATH environment variable must include $UNIKIX/lib as one of
   the search paths. For example, in your region setup file:
   
     LD_LIBRARY_PATH=$UNIKIX/lib;export LD_LIBRARY_PATH

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


--------------------------------
Sun MTP 7.2.0p9    -   112271-09
--------------------------------
1. 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
   
       Changed to a warning type message: KIX3817W.

   b.  KIX3818E [%r] KIXBTCH is not set but the vct is configured for batch
   
       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 error 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.
         

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

   Note that the syntax of the kixsalvage command was incorrectly
   documented in the Sun MTP Reference Guide (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 Micro Focus 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.
     
     
     ------------------------------------------------------------------------
     
3. 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
        

4. 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 following fatal error message:

   KIX1228F -m option is only used for line, record or recordv format
  
5. Sun MTP now returns an error to the calling program, if an attempt is
made to write to an ESDS file that is larger than 4 gigabytes. (BugId 4753426) 

   If the ESDS file is 4 gigabytes in size or greater, INVREQ is set and 
   RESP2 is set to 1.
   
6. 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.


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


8. A fix to BugId 4834342, which improved recovery processing, 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.


--------------------------------
Sun MTP 7.2.0p8    -   112271-08
--------------------------------
1. 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.
      
2. 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 0000 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.
      
3. 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

         
4. 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.
         
5. 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 on the screen and written to
   the unikixmain.log file. 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. To find out where the snapshot file was written, look for
   the message in the unikixmain.log file.
   
   Make sure to send the snapshot file to your authorized Sun service
   provider for analysis. 

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


   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.

   KIX6754D -o <filename> parameter is only valid with -r parameter 

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



--------------------------------
Sun MTP 7.2.0p7    -   112271-07
--------------------------------

1. The following sections in Appendix A of the Sun MTP Software Configuration
Guide 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

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

3. The documentation for the EXEC CICS INQUIRE TASK command (documented 
in the updated_user_doc.txt file for patch 112476-01) and for 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 - tast 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 the sequence number that identifies the task, 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 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.

    
4. The Sun MTP Installation Guide for Release 7.2.0 contains errors in 
Chapter 5, Verifying the Installation (BugId 4789453). It states that 
there are two versions of the Primer application: the COBOL version 
is located in $UNIKIX/test/primer/cobol, and the C version is located 
in $UNIKIX/test/primer/C. This is incorrect. Both versions are located 
in $UNIKIX/test/primer. 

The document also incorrectly states that the kixprimer script, which is 
used to set the environment for running the sample applications, is 
located in each of of respective directories. The kixprimer script is 
actually located in $UNIKIX/bin. You can execute this script from the 
$UNIKIX/bin directory to set the environment for both the COBOL and C 
sample applications.

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

6. 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 intrapartion 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.
     
7. If double-byte character set support (DBCS) was enabled for the
region, and the following error message was written to the unikixmain.err 
file:

   KIX3656E [cvlwrupr] mblen failed, return code = -1 , errno = 88

running the kixclt utility on your COBOL application programs and
recompiling them should eliminate the problem. (BugId 4782622 and 4772318)


 
--------------------------------
Sun MTP 7.2.0p6    -   112271-06
--------------------------------

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). See also #3 in the section
   Sun MTP 7.2.0p4.1 for information about the -A and the -B options
   to unikixmain.

0557W 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. The Sun Mainframe Transaction Processing Developer's Guide for Release 7.2.0 
incorrectly stated that the COMMAREA parameter of the EXEC CICS ADDRESS command 
was not supported. The COMMAREA parameter is, in fact, supported.(BugID 4754923)

4. Table 3.1 in the Sun Mainframe Transaction Processing Administrator's Guide 
did not include descriptions for the last two fields of the ASCII VSAM catalog 
format. (BugID 4750737) Those fields are defined as follows:

1st flag - Batch Read-locking field

Y - Lock VSAM records when READ is issued for this file from batch.
N - Do not lock VSAM records when READ is issued for this file from batch.

2nd flag - Reuse Allowed field

Y - Reuse is allowed for this file
N - Reuse is not allowed for this file

5. The size of the Filename field in the Intrapartition & Extrapartition 
screens of the Destination Control Table has been changed to accept only 
10 characters. (BugID 4657804)

6. Documentation did not include information about compiling C++ programs. 
   (BugID 4767661). The following is the documentation.

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.0
                 acct00.c
        ld -G -o acct00.so acct00.o

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

--------------------------------
Sun MTP 7.2.0p5    -   112271-05
--------------------------------

1. Transactional Support for MQSeries
-------------------------------------

Sun MTP has been enchanced to allow MQSeries updates to be synchronized with
Sun MTP SYNCPOINT/ROLLBACK.

When the user executes the following command:

EXEC CICS SYNCPOINT

Changes done in the transaction for MQSeries are committed.


When the user executes the following command:

EXEC CICS SYNCPOINT ROLLBACK

Changes done in the transaction for MQSeries are rolled back.


When the user completes the transaction, an implicit SYNCPOINT is done 
by Sun MTP that commits all the changes done to MQSeries.

With this feature, the user can synchronize updates to MQSeries with VSAM and
databases such as ORACLE and SYBASE.

Limitations :

1. MQSeries server and the Sun MTP region must be on the same host.
2. Transactional support cannot be used with the trigger mechanism.

The Third Party Packages screen in the kixinstall configuration utility 
now has the option:

        MQSeries with transactional support

If the user chooses this option, transactional support is provided for 
MQSeries resources.

MQSeries applications can be used within MTP without trigger mechanism.

If the applications know the MQSeries Queue Manager name and Queue name, 
and the applications do not need transactional support, the user can choose 
the MQSeries option.

2. kixclt Changes for C Language Transactions
----------------------------------------------

The kixclt changes apply to the following data types:

Data type                   Usage                Comments


Character String            Data-area (R)        Translator was prefixing
variable                                         the name of the variable
                                                 with &

                                                 Now it does not prefix it
                                                 with &

Structure or                Data-area (R)        Translator was prefixing
union                                            the name of the variable
                                                 with &

                                                 Now it does not prefix it
                                                 with &

Array (of                   Data-area (R)        Translator was prefixing
Anything)                                        the name of the variable
                                                 with &

                                                 Now it does not prefix it
                                                 with &

Array (of                   Data-area (R)        Translator was prefixing
Anything)                                        the name of the variable
                                                 with &

                                                 Now it does not prefix it
                                                 with &

Retranslate the source files and test them before putting them into production.



--------------------------------
Sun MTP 7.2.0p4.1  -   112686-01
--------------------------------

1. Support for files greater than 2 gigabytes in size.

   If using mfrcd record format for input or output with unikixbld
   and files are greater thatn 2 GB, Server Express Cobol must be used.
   Please refer to the "File Handler Configuration" section in the
   Server Express "Programmer's Guide for File Handling" and read about
   the handler configuration file. This configuration file must
   contain, at a minimum, the following statements :

        [XFH-DEFAULT]
        FILEMAXSIZE=8

   Depending on your application, this file may contain other
   statements.

   In the region setup file, define the EXTFH environment variable,
   which specifies the location of the handler configuration file.

2. Support for the OUTLINE paramater in BMS maps.

3. Enhancements to DBCS support.

   a. Changes to unikixmain options.

      The unikixmain command has been changed to only accept a single byte 
      conversion table in the -A option. The -B option has been modified to 
      accept a double byte conversion table.

      The new usage is:
	
	-A <single byte conversion table> 
	-B <double byte conversion table>

	The single byte conversion table is a 256-byte file representing 
	EBCDIC to ASCII conversion of characters 0x00 thru 0xff.

	The double byte conversion table is a 131072 byte file representing
	EBCDIC to ASCII conversion of characters 0x00 0x00 thru 0xff 0xff.

	-B continues to specify that DBCS is ON.

	Table names               language               size

        IBM-290toJIS-Roman.table   Japanese              SBCS
        IBM-1027toJIS-Roman.table   Japanese             SBCS


  b. Support for dtterm

     The xxxunikix command now supports dttermunikix.
     
     The dtterm.key file is shipped in $UNIKIX/lib.
     
     3270 Function	Keyboard Legend
     UP			Up arrow
     DOWN		Down arrow
     LEFT		Left arrow
     LEFT		Backspace
     RIGHT		Right arrow
     TAB		Tab
     BTAB		Shift - Tab
     ERAEOF		Page Down
     ERAINP		Page Up
     INSMODE		Insert
     DEL		Delete
     ENTER		Keypad Enter
     CLEAR		Keypad add (+)
     RESET		Keypad subtract (-)
     REFRESH		Control - lower case L
     PF1 through PF10	F1 through F10
     PA1		Keypad divide (/)
     PA2		Keypad multiply (j)
     PRINT		End 



--------------------------------
Sun MTP 7.2.0p4    -   112271-04
--------------------------------

1. Support for Secure Sockets Layer (SSL) clients using Network 
   Security Services software (version 3.4). Refer to the PDF 
   file ssl.pdf in the doc directory.

2. Support for Oracle 9i.

3. KIX2925F: Process %s is not built using thread library on Solaris

   Description: The specified process was not built using the thread library.

   Solution: If the process is supplied by Sun MTP, contact your authorized Sun 
   service provider with the information. If the process was created by the
   user, for example, using the C-ISAM library, then the user must create 
   the executables with the thread library. Alternatively the user can disable
   the -j option during startup, but this might affect performance

--------------------------------
Sun MTP 7.2.0p3    -   112271-03
--------------------------------

No documentation updates



--------------------------------
Sun MTP 7.2.0p2    -   112476-01
--------------------------------

1. Support for a Sybase C-only version of user exits. The 
kixinstall utility has been enhanced to include the C user 
exit module for Sybase. The module name is $UNIKIX/src/
rdbms/kxsybase.cp.

2. Enhancement to the kixinstall utility to allow a user to 
specify compiler/linker options that will be used when 
compiling/linking user objects into the Sun MTP executables. 
This allows a user, for example, to specify the -misalign 
compiler option, which allows single-byte packed structures.

3. Support for the INQUIRE TASK CICS command:

The EXEC CICS INQUIRE TASK API with the following options is 
supported. Unsupported options are listed at the end of this 
summary.

INQUIRE TASK(...)
        [FACILITY(...)]
        [FACILITYTYPE(...)]
        [PROCESSID(...)]
        [RUNSTATUS(...)]
        [STARTCODE(...)]
        [TRANSACTION(...)]
        [USERID(...)]

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:

TASK - task was initiated by another task

TERM - task was initiated from a terminal

DEST - tast was initiated by a destination trigger level

RUNSTATUS - Returns a CVDA value indicating whether the task 
is running. The only supported value is RUNNING.

PROCESSID - Returns a 32-bit binary value indicating the 
process id of the process (MTP unikixtran) running the 
transaction associated with the task.

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 - 32-bit binary value indicating the task identifier.

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.

Unsupported parameters:

UOWSTATE
TCLASS

4. Support for the AT and AFTER parameters of the START CICS 
command:

The EXEC CICS START command now supports the AFTER and AT 
parameters

AFTER - Along with one or more of the HOURS, MINUTES, and 
SECONDS arguments, specifies the interval of time that must 
elapse before the new tast is started. For C/C++ programs, 
this option must be used instead of INTERVAL. 

AFTER HOURS(0) is the default.

AT - Along with one or more of the HOURS, MINUTES, and 
SECONDS arguments, specifies the time when the new task is 
to start. For C/C++ programs, this option must be used 
instead of TIME.

HOURS - A 32-bit binary value indicating the number of 
hours. The value must be in the range 0 through 99.

MINUTES - A 32-bit binary value indicating the number of 
minutes. The value must be in the range 0 through 59 if 
HOURS or SECONDS is also specified, or in the range 0 
through 5999 otherwise.

SECONDS - A 32-bit binary value indicating the number of 
seconds. The value must be in the range 0 through 59 if 
HOURS or MINUTES is also specified, or in the range 0 
through 359999 otherwise.

5. Support for the APPLID parameter of the EXEC CICS INQUIRE 
SYSTEM command:

The INQUIRE SYSTEM [APPLID(data-area)] parameter is now 
supported. APPLID will return an 8-character string that is 
the value of the Application Name field in the System 
Initialization Table (SIT).


--------------------------------
Sun MTP 7.2.0p1    -   112271-02
--------------------------------

No documentation updates

