Datos Generales:

UK DDMMYY DDMMCCYY

US MMDDYY MMDDCCYY

International YYMMDD CCYYMMDD

No A decimal point cannot be used when entering data in a numeric Data Item.

Yes A decimal point must be used when entering data into a numeric Data Item.

Optional The use of a decimal point in a numeric Data Item is optional. If no decimal point is used, the value entered will be treated as a whole number.

Japanese Char Set Support

Check this check box to enable the use of Developer features specific to the handling of Japanese Character Sets. For example, the Japanese-specific edit types EDIT;K and EDIT;W are only available if the Japanese Char Set Support check box is checked. Checking this check box when MCP is the only host selected in the Target Host field enforces SOK/EOK Support. See SOK/EOK Support for further information.

Use Kanji Edit Type

Use these fields to specify the default CLEAR.WHEN characters for the Business Segment. These values are used in systems using a Kanji character set on MCP based or OS 2200 based hosts only. The options are:

CCSVersion support

Check this check box to specify CCSVersion support for the Business Segment. CCsversion enables you to specify a collating sequence (other than the default

sequence) for the alphanumeric fields stored on your database. For ClearPath MCP this ensures that all text comparisons and sort sequences use the same collating sequence as the DMSII database. For UNIX operating systems this ensures that all text

comparisons use the same collating sequence as the ORACLE database, and sorts use the collating sequence specified by the local environment.

This option only applies to ClearPath MCP and UNIX operating system based hosts. If you have defined a different target host, you can still set this option, but it is ignored during generate or at runtime.

You can override this option in the Systems directory using the Ignore National Items check box on the:

• Default DASDL Business Segment Options for ClearPath MCP

• Environment Business Segment Options for the UNIX Operating System

Note: CCSVersion support cannot be set if Japanese Char Set Support is set.

National Item Default

This field applies to ClearPath MCP and UNIX operating system target hosts only.

Value Description

None No CLEAR.WHEN character is defined.

A Define a CLEAR.WHEN character for an MCP based system. S Define a CLEAR.WHEN character for an OS 2200 based system. CLW Char If A or S is selected, key in the 2 byte character to be used.

If you select the Yes radio button, all the alpha Data Items in the Business Segment that have the Default National Item attribute are National Items.

If you select the No radio button, alpha Data Items with the Default National Item attribute are non-National Items.

This option can be overridden for Ispecs, Reports, and individual Data Items.

National Items use the CCsversion collating sequence specified by the CCsversion field on either:

• Default DASDL Business Segment Options for ClearPath MCP

• Environment Business Segment Options for the UNIX Operating System

Note: When the target host is a UNIX operating system, care must be taken when applying the National Item attribute to Data Items used as Ordinates in Profiles. Each Profile maps to an index within the database. Defining an item as a National Item can increase its length within an index, by a factor of two or more. This could cause ORACLE error 01450-Maximum key length exceeded.

This error is due to an ORACLE restriction that an index cannot exceed roughly one- half (minus some overhead) the available data space in a data block. The data block size is specified at the creation of the database in the initialization file and cannot be changed. If this limit occur you can either remove the National Item attribute or recreate the database with a larger data block size.

Foreground

Select a foreground color for the Business Segment, when displayed in a character screen, from the drop-down list. Available colors are Red, Blue, Ebony (black), Magenta, Cyan, White, Yellow, and Green. The default is Ebony.

Background

Select a background color for the Business Segment, when displayed in a character screen, from the drop-down list. Available colors are Red, Blue, Ebony (black), Magenta, Cyan, White, Yellow, and Green. The default is White.

Suppress Zeros

Check this check box to suppress leading zeros for numeric Data Items in Ispec screen layouts. This option does not apply to Data Items in Reports and Usage Inquiry Items. Suppressed zeros result in non-significant zeros being replaced by spaces on output, and leading spaces changed to zeros on input. If a separator character is also specified, leading separators are also changed to spaces.

Full Suppression

Check this check box if you want a zero numeric value to be displayed as spaces in Ispec screen layouts. This option does not apply to Data Items in Reports and Usage Inquiry Items.

The Suppress Zeros check box must also be checked if you want to select Full Suppression.

Left Fill Numerics

Check this check box to require Developer Test users to enter numeric values from the left of their fields instead of the right.

Integrity

Check this check box to indicate that Ispec, Report, and Profile dataset locking is to occur automatically. This ensures processing integrity and fully synchronized recovery. The default is no integrity.

Note: Setting Integrity may have a major impact on the performance of your system. See Integrity for more information before setting this check box.

Convert to Uppercase

Check this check box to specify that input to alphanumeric fields is to be converted to uppercase.

Preserve Session Data

Check this check box to specify that data held in GLB.WORK is to be retained when the session terminates.

If the Preserve Session Data check box is checked, the values in GLB.WORK will be preserved. When you restore the database, GLB.WORK will contain the data it had before the termination.

This check box is not checked by default. This means that if a transaction terminates on an ABORT; command, the values in GLB.WORK are lost and the transaction cannot be recovered.

Note: In the current release of the UNIX runtime environment, the setting of this check box is ignored.

Warning

You must bring down the application when generating a system where the Preserve session data option has been changed.

DC; sets GLB.CENTURY

Check this check box to specify that GLB.CENTURY and GLB.DC-CC are to be set by a DATE.CONVERT; command.

If this check box is not checked, GLB.CENTURY is not set by DATE.CONVERT; (but GLB.DC-CC is). GLB.CENTURY can still be read by DATE.CONVERT; to determine the century of the input date.

The default for this check box, regardless of whether this attribute is specified in the loaded file or not, is:

• Checked for pre-LDA 2.1 Business Models.

• Not checked for Business Models for LDA 2.1 and later.

Allow Field Truncations

Check this check box to specify that the visible length of screen and Report Frame fields is to be truncated when the length of the field is greater than the screen space available. If the check box is not checked, all fields must be displayed at full length on the screen.

The default is to allow field truncation.

The following types of fields may not be truncated in any case: • Ordinate fields

• Kanji fields

• Fields with the CLEAR.WHEN attribute set

Fields inserted from a painted Global Logic may not overlap any Ispec fields at all. For other fields, the minimum screen length is one character plus a character for each delimiter and video attribute character.

Two Phase Commit

Check this check box to use the Two-Phase Commit process for database updating that occurs with external Automatic Entries.

The Two-Phase Commit process works like this:

1. Initiating System sends a request for the Automatic Entry.

2. Receiving System performs the required processing, but does not commit the transaction.

3. Sending System sends a confirmation message. 4. Receiving System commits its transaction. 5. Sending System commits its transaction.

With Two-Phase Commit, the sending and receiving systems are able to roll back to a synchronized point if both have not successfully completed their related transactions. The default is not to use Two-Phase Commit.

System Uses ROC

Check this check box if you want the Report Output Control (ROC) facility to manage the output from all Reports.

This check box is ignored for UNIX and OS 2200 based Systems as these hosts always use ROC. By default the System Uses ROC check box is checked.

Def Bounds Checking

Check this check box to set bounds checking by the complex MOVE; command. Error checking code is generated to check POSITION; and LENGTH; parameters for

consistency. On error, GLB.STATUS is set to *****.

If the check box is unchecked, a check for errors does not occur. This means that if a complex MOVE; is performed that is out of bounds of the receiving Data Item, the Data Item may contain unpredictable results.

You can get significant performance improvements if you do not set bounds checking, and the default for this field is not selected.

Extend Report Recovery

Check this check box to specify that Reports that fail three times are to store their recovery information. You can then rerun failed Reports after you have fixed the problem that caused the failure.

If this check box is unchecked, Reports are limited to two attempts at recovery before they are aborted.

This check box is unchecked by default.

Extended Logic Line

Check this check box to extend the allowable line length in logic to 240 characters. For short name repositories this means that you can enter a line of 240 characters. For long name repositories this means that when the long names are converted to short names, the line can be greater than 72 characters.

If this check box is not checked the standard 72 character line length applies.

Unchecking the Extended Line Logic check box: You should not uncheck this check box once extended lines of logic have been entered. The lines do not become invalid, and you are able to edit the lines to change the logic or to reduce them to 72 characters or less. You are not able to add extra characters to the line. If the check box is unchecked and the Model is extracted, the extended lines are truncated to 72 characters.

Allow Big Buffers

Check this check box to allow Big Buffer Ispecs within the Business Segment.

Developer Test Options

Click the Developer Test Options button to specify the paths to your Developer Test system.

In the Developer Test Options dialog box displayed, specify the directory paths for the

Database, Event Set, Transaction Log and Reorganization files.

Note: If you do not specify the directory paths, the default paths for these files are used. If you are running more than one Developer Test session, and find that the data displayed is not the data for the current session, specify the database directory path (in the Database field) in each Developer installation.

Use the Browse buttons or key in the path (drive and directory) to define where the parts of the Runtime system are to be located. To set up a database path on another server (for example when using multi-user runtime databases), you should use the Uniform Naming Convention (UNC). The basic format of the UNC is:

\\servername\sharename

where servername is the host name of a network file server or the name of a machine on the network, and sharename is the name of a networked or shared directory. In a Novell environment, sharename is the Novell volume name.

If you use drive letters, the letters must be taken from the machine on which the Developer Server is running (for example, your local machine in single user mode). Checking the Map Library Names for CALL statements check box specifies that when Developer Test encounters a CALL statement, it will map the specified library name to ‘rcall’. This applies when Developer Test is emulating the CALL statement locally. It is ignored when the CALL statement is processed remotely on the host.

Host Specific Options

Click on the Host Specific Options button if your target host is MCP or OS 2200 to define information specific to these hosts. The required fields are described below.

Primary GSDs/DADs FTU Translatable: This option is available when MCP is the only target host type selected.

Check this check box to enable Global Setup Data Items, data display items, screen layouts, and Teach screens to be translated through the Forms Translation Utility (FTU).

Suppress Delimiters: This option is valid when OS 2200 is the only target host type selected.

Binary Numeric: This option is available when OS 2200 is the only target host type selected.

Use the Binary Numerics field to select values from the System and Event drop- down lists. These values define the default format of numeric Data Items in the Business Segment.

Use the System drop-down list to specify a system-wide format for numeric Data Items. Select one of the following options:

Use the Event drop-down list to specify a format for numeric Data Items belonging only to Event tables. This value overrides the System field value for Event tables (unless D is selected). Select one of the following options: