Sun Mainframe Transaction Processing Software Configuration Guide

This chapter describes how to start and stop Sun MTP, as well as how to start a local client. It includes the following topics:

• Starting the Sun MTP Server
• Starting a Local Client
• Executing a Transaction
• Shutting Down Sun MTP
• Client Connections

To run an application, first start the server, then the clients. The Sun MTP Server waits for transactions entered by the clients at terminals.

---

Starting the Sun MTP Server

The unikixmain command, which starts the Sun MTP main server process, has many options. Some important options are as follows:

• You must use the -Q option if you are using the local client.
• If your transactions make extensive use of shared memory or if you forced all temporary storage to shared memory with the unikixmain -T option, use the
  -S option to increase the size of the shared memory area to at least 2 MBytes. If you do not, messages are written to the unikixmain.log file, indicating that dynamic shared memory segments have been allocated. If the number of allocated segments reaches the maximum allowed, the system can come to a halt.
• By default, Sun MTP starts with semaphores. You can override the default with the -j option which enables mutexes (mutual exclusion locks). Mutexes can improve performance under certain conditions.

Refer to the Sun Mainframe Transaction Processing Software Reference Guide for the unikixmain options.

1. Source your region's setup file.

See Defining a Region's Environment.

2. Type the unikixmain command and its options at the command prompt.

Or, use the kixstart shell script with any of the unikixmain options.The kixstart script passes the options to the unikixmain command.

After unikixmain starts, it disassociates itself from the terminal that started it so that the terminal is available for other uses.

---

Starting a Local Client

You can execute transactions from a variety of clients. This procedure describes how to connect to an active region using the local client.

1. Log in to your host as a user.

2. Set your environment by sourcing the appropriate setup file.

Your environment might have already been set when you logged on, if the variables were set in a .profile or .login file.

3. Start the Sun MTP client process.

For example, to start the client from an X term with a 101-key keyboard, type:

$ xtermunikix unikix

4. When a new window with the Sun MTP copyright screen is displayed, press any key to clear the screen.

The source for the copyright screen is $UNIKIX/lib/logofile.

Refer to the Sun Mainframe Transaction Processing Software Reference Guide for information about the startup shell scripts. See also Chapter 8 for information about starting a client with an xxxunikix shell script, such as xtermunikix, that sets up your terminal with the correct keyboard type.

If the client fails to start, use a text editor to view the unikixmain.log file located in the $KIXSYS directory. Read the error messages to determine the cause of the failure. Also refer to the Sun Mainframe Transaction Processing Software Troubleshooting and Tuning Guide.

---

Executing a Transaction

After you successfully connect to a region and clear the copyright screen, you are ready to submit transactions.

1. Press any key to clear the copyright screen.

2. On a blank screen, type a transaction identifier in the upper left corner.

3. Press the Enter key, not the Return key, to send the transaction to Sun MTP.

For example, to display the Table Manager, type CTBL and press Enter.

---

Shutting Down Sun MTP

This section describes the methods for shutting down the region and individual user sessions. Refer to Chapters 7 and 8 in the Sun Mainframe Transaction Processing Software Administrator's Guide for information about using built-in security or an external security manager to limit access to these methods.

Shut down the system in the following order:

1. Application users' sessions

2. Sun MTP region (Sun MTP server)

3. Any TN3270 connections

Shutting Down a User Session

There are several transactions you can use to shut down a session at a terminal. Your screen must have enough clear entry space for the transaction identifier and its parameter. If the screen is full, press the Clear key to clear the screen, then type the transaction.

Method 1

Type either:

CSSF GOODNIGHT

CSSF LOGOFF

These are the standard transactions used to end Sun MTP sessions.

Method 2

Type:

CSMT SHUT,NO

The NO parameter indicates not to shut down the Sun MTP server along with the user's session, even if the user is the last one still connected.

Shutting Down the Sun MTP Server

There are four ways to perform an orderly shutdown of the Sun MTP server. The first three work within the Sun MTP environment. The last method uses a shell script. Limit access to these methods to prevent users from accidentally shutting down the server.

Before using any method to shut down the region, perform the following actions to ensure that all user sessions are terminated cleanly:

1. Invoke the CEMT PERFORM SHUTDOWN transaction to place the system in the SHUT state.

Users are no longer allowed to start new transactions.

2. With the system in the SHUT state, invoke the CEMT INQ TASK ALL transaction to determine the state of logged-on user sessions.

3. After all users have completed their transactions, shut down Sun MTP.

For more information about the CEMT transaction, refer to the Sun Mainframe Transaction Processing Software Administrator's Guide.

Shutting Down the Region From Within Sun MTP

There are three methods of shutting down the region from within Sun MTP. The first two methods use system transactions. If the screen is full, press the Clear key to clear the screen, then type the transaction. The third method uses the Development System main menu.

Method 1

Type:

CSMT SHUT,YES

CSMT SHUT is the same transaction used to shut down a user session. The YES parameter shuts down the region along with the user's session, even if other users are still connected.

Method 2

Type:

CEMT PERFORM SHUTDOWN IMMEDIATE

CEMT PERFORM SHUTDOWN is the transaction used to put the system into the SHUT state. The IMMEDIATE parameter shuts down Sun MTP immediately. All user sessions, including that of the user who issued the transaction, are shut down.

Method 3

1. On the Development System main menu, press the PF3 key to begin the shut down process.

2. Press PF3 again when prompted to confirm the request. Be aware that with Sun MTP built-in security, there is no security checking to prevent any user with access to the CMNU transaction from shutting down the region with this method.

Shutting Down the Region Using kixstop

Use the kixstop utility to shut down the region at the command line. To use kixstop, at least one client must be available. When you invoke kixstop at the command prompt, it starts a terminal handler that issues a CEMT PERFORM SHUTDOWN transaction. This transaction allows the region to quiesce before shutting it down in an orderly manner.

Using the -i option to kixstop causes the program to issue a CSMT SHUT,YES transaction, which shuts down the system immediately. The immediate shutdown does not allow transactions to terminate normally, causing them to be rolled back.

If transaction security is in force and you have secured the CEMT or CSMT transactions, only a user with security access can run kixstop. For more information about transaction security, refer to the Sun Mainframe Transaction Processing Software Administrator's Guide.

---

Client Connections

TABLE 3-1 briefly describes the connections to Sun MTP from local and remote systems and the supported connections to other remote systems. It also lists the server and client processes required for each type of connection.

The Sun Mainframe Transaction Processing Software Reference Guide contains descriptions of the Sun MTP client and server processes.

Sun Mainframe Transaction Processing Software Configuration Guide

816-5328-11

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