Sun Mainframe Transaction Processing Software Release Notes for Solaris Platforms

This chapter contains information about the documentation for this release. The topics are:

• Documentation
• Documentation Errata

Refer to the docs.sun.com web site for online versions of the documents, as well as any future updates or supplements that might be available.

---

Documentation

The Release 8.0.1 documents and their contents are listed below.

---

Documentation Errata

This section describes errors in the documentation.

Sun Mainframe Transaction Processing Software Administrator's Guide

Chapter 1, "Introduction"

Sun MTP J3270 Client

The section "Sun MTP J3270 Terminal Emulator Client" should state that the Sun MTP J3270 client can work on all modern Windows systems (such as Windows XP, Windows ME), as well as Solaris, AIX, and any other platform that has a Java runtime environment (JRE).

Chapter 2, "System Transactions"

CEDA Transaction

The REMOTENAME and REMOTESYSTEM attributes of the CEDA DEFINE TRANSACTION command are described incorrectly. The correct descriptions are as follows:

Chapter 10, "Accounting"

UNIX Accounting

The section "UNIX Accounting" does not apply to the Solaris operating environment. Refer to the Solaris documentation for information about operating system accounting.

User Journals

The last paragraph in the section "Setting Up User Journals" in Chapter 10 is incorrect. The following paragraph contains the correct information:

The kixjas utility can read journal files that contain only accounting records. For application-specific journal records, you must provide a utility to read the journal files. If the journal files contain a mix of Sun MTP records and application-specific records, you must also provide a utility to read the files. When writing your utility, refer to the Sun MTP accounting record formats described in Tables 10-5 and 10-6 in the Sun Mainframe Transaction Processing Software Administrator's Guide.

Sun Mainframe Transaction Processing Software Configuration Guide

Chapter 4, "Configuration Guidelines"

Shared Library Usage

In Chapter 4, the section "Shared Library Usage" requires the following sentence at the end of the section:

Sun MTP intercepts the errno 22 condition and outputs the error message KIX0208E.

VSAM Buffer Size

The section "Determining VSAM Buffer Size" is no longer valid.

Shared Memory

The following documentation replaces the example in the section "Where to Attach Sun MTP Shared Memory" in the "Configuration Guidelines" chapter of the Sun Mainframe Transaction Processing Software Configuration Guide. The incorrect example starts with the third paragraph, "For example, by setting ...," and ends with the kixdump output snippet.

Sun MTP has the following internal fixed default definitions:

• KXTHRESHOLD = 3.5M (00380000 )
• KXMAXCORE = .5M (00080000 )

unikixmain uses the internal default definitions, along with the -M tvalue and
-M cvalue options, to calculate the actual addresses shown in the kixdump -M report according to the following rules.

For -M tvalue (value can be a negative number):

If specified: Threshold = value + (ee000000 - KXMAXCORE - KXTHRESHOLD) otherwise: Threshold = (ee000000 - KXMAXCORE)

For -M cvalue:

If specified: Max Core = Threshold + value
otherwise: Max Core = Threshold + KXMAXCORE

Example 1: Neither the -M tvalue nor-M cvalue options are specified

The kixdump -M output displays the following:

Values of Shared Memory, Max Core, Threshold Memory

Address of Shared Memory    (ee000000 )

Address of Max Core         (ee000000 )

Address of Threshold Memory (edf80000 )

Example 2: A negative value for -M tvalue is specified, for example,
unikixmain -M t-16M.

The kixdump -M output displays the following:

Values of Shared Memory, Max Core, Threshold Memory

Address of Shared Memory    (ecc80000 )

Address of Max Core         (ecc80000 )

Address of Threshold Memory (ecc00000 )

Example 3: A positive value for -M tvalue is specified, for example,
unikixmain -M t16M.

The kixdump -M output displays the following:

Values of Shared Memory, Max Core, Threshold Memory

Address of Shared Memory    (eec80000 )

Address of Max Core         (eec80000 )

Address of Threshold Memory (eec00000 )

Example 4: A negative value is specified for -M tvalue and a positive value is specified for -M cvalue, for example, unikixmain -M t-32M -M c10M.

The kixdump -M output displays the following:

Values of Shared Memory, Max Core, Threshold Memory

Address of Shared Memory    (ec600000 )

Address of Max Core         (ec600000 )

Address of Threshold Memory (ebc00000 )

Example 5: Positive values are specified for both the -M tvalue and the -M cvalue options, for example, unikixmain -M t32M -M c10M.

The kixdump -M output displays the following:

Values of Shared Memory, Max Core, Threshold Memory

Address of Shared Memory    (f0600000 )

Address of Max Core         (f0600000 )

Address of Threshold Memory (efc00000 )

Chapter 11, "Configuring Sun MTP for Remote Clients"

The information in the section "Configuring a Region for SSL Clients" has changed. See Secure Socket Layer (SSL) Libraries for the correct information.

Chapter 13, "Configuring a Region to Work With an RDBMS"

The sections "Starting a Region With an RDBMS" and "Bypassing the RDBMS at Startup" might be confusing in the descriptions of the use of the -t option to unikixmain and the use of the KIXRDBMS_BYPASS environment variable. To clarify: There are no restrictions on the use of the KIXRDBMS_BYPASS variable with any of the unikixmain options.

Sun Mainframe Transaction Processing Software Developer's Guide

Chapter 4, "Compatibility With IBM CICS"

The documentation of the RESP2 codes for the EXEC CICS CHANGE PASSWORD, EXEC CICS SIGNON, and EXEC CICS VERIFY PASSWORD APIs was incomplete. The correct response codes are shown in the following tables.

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

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

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

Chapter 13, "Using the MQ-JMS Bridge"

The README.doc file for running the MQ-JMS sample application has changed. If you are using the MQ-JMS Bridge, make sure to follow the directions in the README.doc file located in the $UNIKIX/test/mq/jms directory, and not the directions shown in Code Example 13-3.

Chapter 14, "Online Debugging"

This chapter has been replaced with a new version, which contains information about support for using 3270-type terminals to debug online programs.

Chapter 15, "Batch Processing"

The section "Performing Fast Writes From a Batch Program" contains erroneous information.

• The code example showing the setenv statement should be replaced with the following statement in the macro job script:

SETPARM parms='FAST_UNIKIXVSAM=ACCT1:ACCT2'

• The paragraph starting "You can also set the environment in the JCL using ..." should be removed, as well as the example that follows it.

Chapter 16, "Accessing VSAM Files From External Programs"

The command shown in Step 3 in the procedure "Compiling the C Language Program" is incorrect. The correct command is:

$ cc input-filename.c -o output-filename $UNIKIX/lib/libbcisam.a -lcurses -lsocket

Sun Mainframe Transaction Processing Software Installation Guide

Chapter 1, "Introduction to Sun MTP"

Software Requirements

The section "Software Requirements" incorrectly stated, "If you are using Java programs, you must install the Java Development Kit (JDK) and Server Express." Server Express is not required if your region does not use COBOL programs.

SSL Libraries

See Secure Socket Layer (SSL) Libraries for information that has changed in the Sun Mainframe Transaction Processing Software Installation Guide.

Sun Mainframe Transaction Processing Software Reference Guide

Chapter 2, "System Utilities"

dfhusdup Utility

In the description of the dfhusdup utility, the REMOTENAME and REMOTESYSTEM attributes of the DEFINE TRANSACTION command are incorrect. The correct descriptions are as follows:

Sun Mainframe Transaction Processing Software Release Notes for Solaris Platforms

817-5613-10

Copyright © 2004, Sun Microsystems, Inc. All rights reserved.