C H A P T E R 1

Development System

The Sun MTP Development System enables you to execute the Table Manager, File Manager, Record Editor, and the Screen Generation Utility (SGU) from a single menu. It also provides tools to compile application programs, assemble BMS macros, edit source files, and execute file commands and utilities.

This chapter contains the following topics:

Starting the Development System

Development System Main Menu

Development System Restrictions

Sun MTP Standards

Starting the Development System

If you are locally connected to an executing Sun MTP region and the terminal displays a blank transaction screen, type the CMNU transaction to start the Development System.

If you are remotely connected through a 3270 terminal or TN3270 emulator, you cannot use CMNU. You can only use one of the transactions that directly accesses a part of the Development System; for example, use CTBL to open the Table Manager.

Development System Main Menu

The Development System main menu is the interface you use to select one of the available tools. FIGURE 1-1 shows the Development System main menu.

FIGURE 1-1 Development System Main Menu

Screen shot showing the Development System main menu.

Press a function key to open the tool you want to use.

TABLE 1-1 Development System Function Keys
Function Key	Action
PF1	Starts the File Editor. See Chapter 2.
PF2	Enables you to perform these UNIX file functions: browse, copy, concatenate, delete, print, rename, and search. See Chapter 3.
PF3	Shuts down the Sun MTP client and the Sun MTP server. When prompted for confirmation, press the PF3 key again to shut down the region.
PF4	Used to compile and assemble COBOL programs, Liant Open PL/I programs, and BMS maps. These functions are described in Chapter 5.
PF5	Terminates the menu system so that you can use the terminal to enter transaction identifiers.
PF6	Opens the Table Manager. The tables contain your application's resource definitions. You can type the `CTBL` transaction identifier on a blank transaction screen to bypass the Development System main menu and start Table Manager. Refer to the Sun Mainframe Transaction Processing Software Reference Guide for information about Table Manager.
PF7	Opens the File Manager, which displays the VSAM catalog. The catalog defines your application's VSAM files. You can bypass the Development System main menu and start File Manager by typing the `CFMS` transaction identifier on a blank transaction screen. Refer to the Sun Mainframe Transaction Processing Software Administrator's Guide for the procedures to use File Manager.
PF8	Starts the Record Editor. You can bypass the Development System main menu and start the Record Editor by typing the `CRED` transaction identifier on a blank transaction screen. Refer to the Sun Mainframe Transaction Processing Software Administrator's Guide.
PF9	Starts the Screen Generation Utility (SGU). You can bypass the Development System main menu and start the SGU by typing the `CSGU` transaction identifier on a blank transaction screen. See Chapter 9.
PF10	Enters the command mode, which permits the entry of any UNIX command from the prompt except `unikix`. If you type `unikix`, an error message is displayed indicating that the Sun MTP client is already active at the terminal. To return to the Development System, press Ctrl-d. If you changed the current directory or set additional environment variables while operating in the command mode, these changes are lost after you press Ctrl-d. Therefore, do not use this option to set environment variables for other Sun MTP utilities. If you need to set an environment variable, shut down the region, set the environment variable, then restart the region.

Development System Restrictions

Sun MTP development capabilities rely heavily on process and character-based services provided by the operating system. Because these services are generally incompatible with the method of access and terminal devices that are used in an IBM SNA network, some development functions are restricted when working on a Sun MTP region from a 3270 device or from a routed terminal.

IBM 3270 devices and routed terminals cannot be used as the developer's terminal. You can use them to test a program being developed and to validate the program against the real network and terminal.

Users of 3270 devices that are directly connected to UNIX systems cannot execute the CMNU and CSGU transactions. In addition, users of routed terminals cannot execute the CEMT, CTBL, CFMS, CMNU, CRED, and CSGU transactions. Refer to the Sun Mainframe Transaction Processing Software Administrator's Guide for information about the system transactions.

Sun MTP Standards

This section describes the Sun MTP standards for:

Screen Formats

Function Keys

Data Validation

File Identifiers

The standards of your user applications might be different.

Screen Formats

All data entry screens have four areas.

TABLE 1-2 Screen Formats
Screen Area	Description
Header area (line 1)	Identifies the current screen and contains the current date and time.
Detail area (lines 2 through 20)	Contains menus, data entry screens, and file selection areas.
Response area (line 21)	Normally has underscores (_) across the entire line. When certain operations are performed, such as writing data to disk, this line displays a highlighted message indicating any error conditions. It also can indicate status of the operation.
Function Key Description area (lines 22 through 24)	Lists the available function keys for the screen and the operation performed when a function key is pressed.

FIGURE 1-2 Sun MTP Screen Formats--Example

Screen shot of a typical data entry screen showing the four screen areas: header area, detail area, response area, and function key description area.

Function Keys

The following function keys perform the specified operations on Sun MTP screens.

TABLE 1-3 Standard Function Keys
Function Key	Action
PF3	Returns to the previous screen. If you changed data on a screen and press this key before saving the changes to disk, this warning is displayed: Table has been modified. Press PF3 if modification is only temporary. Either press PF3 to confirm that you do not want to save the changes or press any other key to perform another operation
Enter	Modifies the data for the entries currently displayed. You can modify the contents of a screen by typing over the unprotected values and pressing this key. Data is modified only if all fields pass their associated validation tests.
Clear	Clears the screen so you can type a new transaction.
Reset	Resets the system after an operator error, such as typing text in a numeric field.

Refer to the Sun Mainframe Transaction Processing Software Configuration Guide for keyboard mapping information.

Data Validation

You can type both uppercase and lowercase characters into any data field. Under most conditions, lowercase characters are converted to uppercase. Some data fields accept lowercase characters as valid data. Normally, fields that relate to CICS commands are converted to uppercase; other fields are left as typed. For example, dataset names are converted to uppercase and file names remain as they are typed.

During data validation, any fields containing invalid data are highlighted. The cursor is in the first field containing the erroneous data and the following message is displayed in the response area:

Data in field invalid/required

File Identifiers

File identifiers have two parts:

A directory or environment variable that specifies one or more directories

A file name that is the last component of the file identifier

When entering a file identifier, you must conform to the specifications described in the following table:

TABLE 1-4 File Identifiers
File Identifier	Description
Directory	Absolute directory names used in Sun MTP cannot exceed 50 characters. You can use an environment variable preceded by a dollar sign ( $ ) to replace any portion of a path name. For example, the following lines are valid and designate the same directory: `mtp/mtp8/finance/sys` `$KIXSYS` The `$` symbol expands the `KIXSYS` environment variable to its complete value.
Environment variable	Name of a directory or file, or a value; 1 to 14 characters. By convention, environment variables are in uppercase.
File name	Sun MTP file names are 1 to 14 characters, including any extension.