| Sun Mainframe Transaction Processing Software Release Notes for AIX Platforms
|
    |
This chapter contains information about the documentation for this release. The topics are:
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. All features documented in these manuals are not available on AIX platforms. See Product Restrictions for a list of unsupported features.
TABLE 8-1 Sun MTP Documentation
|
Document Title
|
Contents
|
|
Sun Mainframe Transaction Processing Software Administrator's Guide
|
Instructions for:
- Managing VSAM datasets and recovery
- Using transaction classes
- Editing records
- Using the intersystem communications features
- Managing security, including use of Sun MSF
- Using Sun MTP accounting
- Integrating relational database management systems (RDBMS)
- Modifying user exits
- Customizing record processing routines
- Installing and configuring Sun MAT for monitoring resources
- Modifying shell scripts
Additional information
- Sun MTP system transactions and utilities
- Client processes Sun MTP supports
|
|
Sun Mainframe Transaction Processing Software Configuration Guide
|
Instructions for:
- Setting environment variables for a region
- Starting and stopping Sun MTP
- Defining resources for an application
- Configuring alternate resource definition
- Configuring UNIX terminals
- Configuring printers
- Configuring intersystem communications (ISC)
- Configuring a region to support remote clients
- Configuring a region to support RDBMS
- Configuring a region to support Sun MBM
Additional information
- Configuration guidelines
- Keyboard mapping
|
|
Sun Mainframe Transaction Processing Software Developer's Guide
|
Instructions for:
- Using the File Editor
- Using the UNIX File Utilities
- Compiling and using COBOL and C programs
- Assembling BMS maps
- Using the Screen Generation Utility (SGU)
- Using Sun MTP-provided facilities to access an RDBMS
- Using WebSphere MQ with Sun MTP
- Using the Sun MTP debug facility
- Using Sun MTP standard batch processing
- Using TCP/IP sockets
Additional information:
- Description of the Sun MTP Development System
- Compatibility with the CICS API
- Accessing VSAM datasets from C batch programs
|
|
Sun Mainframe Transaction Processing Software Installation Guide
|
Instructions for:
- Installing Sun MTP
- Running the kixinstall utility
- Migrating from earlier releases
- Running a sample application to verify installation
- Setting up the license file
|
|
Sun Mainframe Transaction Processing Software Message Guide
|
Listing of all error messages, along with descriptions and suggested remedial actions. The messages are grouped in the following categories:
- Sun MTP and ISC messages
- Sun MSF messages
- 3270 Client messages
- kxnrfs messages
|
|
Sun Mainframe Transaction Processing Software Troubleshooting and Tuning Guide
|
This document includes the following:
- Descriptions of common problems and solutions
- Suggestions for getting the best performance from your Sun MTP system
- Descriptions of the Sun MTP diagnostic tools
|
|
Sun Mainframe Transaction Processing Software Reference Guide
|
Descriptions of Sun MTP utilities and shell scripts with their options and parameters, grouped in these categories:
- System utilities
- Development utilities
- Application utilities
- Client utilities
- Server utilities
Detailed descriptions of each of the Sun MTP tables
|
|
Sun Mainframe Administration Tool User's Guide
|
Description of the Sun MAT user interface, windows, and datapoints
|
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:
|
Attribute
|
Description
|
|
REMOTENAME(transaction-name)
|
Identifies the transaction in the remote Sun MTP or CICS region. If REMOTENAME is not specified and REMOTESYSTEM is specified, Sun MTP assumes the local transaction ID. The transaction ID is one to four characters in length.
|
|
REMOTESYSTEM(system-name)
|
Identifies the remote Sun MTP or CICS system to which, if specified, Sun MTP will function ship the request. The four-character system name must be defined in the TCT-System Entries table.
|
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.
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:
|
Condition
|
RESP2
|
Reason
|
|
NOTAUTH
|
2
|
Current password is wrong.
|
|
NOTAUTH
|
19
|
Current password is suspended and ESMREASON is set to 901.
|
|
NOTAUTH
|
4
|
New password is greater than the maximum length; ESMREASON is set to 902.
|
|
NOTAUTH
|
4
|
New password is less than the minimum length; ESMREASON is set to 903.
|
|
NOTAUTH
|
4
|
New password value is identical to the old password value; ESMREASON is set to 904.
|
|
NOTAUTH
|
4
|
New password is equal to the user ID; or it is all blanks; or the new password's format is unacceptable (non-numeric or non-alphabetic).
|
|
USERIDERR
|
8
|
Current user ID is invalid.
|
|
INVREQ
|
10
|
No terminal is associated with the task.
|
For EXEC CICS SIGNON, the response codes are as follows:
|
Condition
|
RESP2
|
Reason
|
|
NOTAUTH
|
2
|
Current password is wrong.
|
|
NOTAUTH
|
3
|
Current password has expired.
|
|
NOTAUTH
|
19
|
Current password is suspended.
|
|
NOTAUTH
|
4
|
New password is greater than the maximum length; new password is less than the minimum length; new password value is identical to the old password value; new password is all blanks; or the new password's format is unacceptable (non-numeric or non-alphabetic).
|
|
USERIDERR
|
8
|
Current user ID is invalid.
|
|
INVREQ
|
9
|
The terminal is already signed on.
|
|
INVREQ
|
10
|
No terminal is associated with the task.
|
For EXEC CICS VERIFY PASSWORD, the response codes are as follows:
|
Condition
|
RESP2
|
Reason
|
|
NOTAUTH
|
2
|
Current password is wrong.
|
|
NOTAUTH
|
3
|
Current password has expired.
|
|
NOTAUTH
|
19
|
Current password is suspended and ESMREASON is set to 901.
|
|
USERIDERR
|
8
|
Current user ID is invalid.
|
|
INVREQ
|
10
|
No terminal is associated with the task.
|
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.
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:
|
Attribute
|
Description
|
|
REMOTENAME(transaction-name)
|
Identifies the transaction in the remote Sun MTP or CICS region. If REMOTENAME is not specified and REMOTESYSTEM is specified, Sun MTP assumes the local transaction ID. The transaction ID is one to four characters in length.
|
|
REMOTESYSTEM(system-name)
|
Identifies the remote Sun MTP or CICS system to which, if specified, Sun MTP will function ship the request. The four-character system name must be defined in the TCT-System Entries table.
|
| Sun Mainframe Transaction Processing Software Release Notes for AIX Platforms
|
817-5614-10
|
|
Copyright © 2004, Sun Microsystems, Inc. All rights reserved.