CAPITULO IV: RESULTADOS Y DISCUSIÓN
4.2. Resultados explicativos
Ispecs are the building blocks of your system. There are two types: Components and Events. An Ispec usually consists of a screen definition and its associated logic, but before you can define these, you must add the Ispec to your Business Segment using the Model Directory and specify some basic information about it. For a discussion of the uses of Events, and recommendations for coding them, see Use of Memo Components Versus Events and Rationalizing Event Data Item Names.
Adding an Ispec is described below. To modify, delete, move or copy an Ispec, follow the instructions for modifying, deleting, moving and copying an Element described earlier in this section.
To add an Ispec using the Model Directory:
1. Click on the Business Segment or Activity to which you are adding the new Ispec. 2. Select Component or Event from the Add menu. The Ispec Options dialog box is
displayed.
3. Fill in the available fields. Not all fields are available for both types of Ispec. The fields and expected input are described below.
4. Click on the OK button to complete the process of adding the Ispec, or click on the Next button to add another Ispec.
After defining an Ispec you would specify the Data Items that belong to it. See Defining Data Items for instructions on defining Data Items.
The fields in the Ispec Options dialog box are:
Name
Identifier for the Ispec.
The name must begin with an alphabetic character and cannot contain a hyphen (-). If you wish to modify an Ispec name that has been loaded from a host and contains a hyphen, you must remove the hyphen to conform with current naming rules. Use the Name Validation check box on the Design Audit dialog box to identify Ispec names containing unsupported characters.
This field is alphanumeric. If Long Names are allowed for the Model, the name can be up to 30 characters. If Long Names are not allowed, the name cannot exceed five characters.
Review Naming Elements: Reserved Words before naming a new Ispec.
Notes:
• For MCP based Systems, using a name that is the same as an entrypoint implemented in an Enterprise Application Environment library (such as
LINCSUPPORT) will cause the COBOL syntax error ILLEGAL DUPLICATE NAME when you generate the System. If this occurs, you must rename the Ispec.
• Ensure that the report names, global logic names and data item names must not use the format <ispec>-REC. This conflicts with an internal naming system. Using the format <ispec>-REC for report names, global logic names and data item names results in a generate failure.
Description
A short description of the Ispec.
Author
Your name to identify you as the author of the Ispec, for use in listings.
Alphanumeric, maximum length 20 characters. No validation is performed on the value in this field.
Type
Type of Ispec. For an Event Ispec, Type is defined as Event. For a Component, the options are:
Notes:
• Although there are no functional differences between a Usage-Input Event and a Usage-Input Memo Component, it is preferable to specify such an Ispec as a Usage-Input Memo Component for reasons of technical accuracy.
Type Description
Standard A Component that requires a single Ordinate. Default for a Component. Table A Component that stores low-volume, frequently-accessed data, such as
a code table.
Memo A Component with no Ordinate, used to store data of a memorandum nature.
Direct A Component that uses a key for direct access to the data, saving on the number of Input/Output operations. It has a single numeric Ordinate with a maximum of eight digits.
• If changing a Component to an Event, make sure the Component does not contain any Data Items used in Report Frames. If the Component does contain any Data Items used in Report Frames, when you select Event from the Type field and click OK an error is given.
Current Size
This read-only field displays the current size of the Ispec, measured in bytes.
Usage
The options for Ispec Usage are:
Acctmth Not Entered
Check this check box if you wish to prevent users from changing the accounting month (on line 1 of System Ispecs).
The value of the accounting month is stored in the ACTMTH System Data Item.
Auto Recall Capable
Check this check box if you want to enable all data values for a Component record based on a specified Ordinate value to be recalled to the screen. You must have an Ordinate for this feature to be selected.
Auto Entry Capable
Check this check box to allow Ispecs to be updated with an Automatic Entry from another Ispec or through terminal input.
Ispecs receiving internal Automatic Entries must be Usage Input-Output or Usage Output, while external Automatic Entry Ispecs must be Usage Input-Output or Usage Input.
Refresh Screen
Check this check box to specify that an Ispec screen is to be refreshed after a transaction has been successfully processed.
Usage Description
I-O Input/Output. Values are entered from a screen and stored in the Repository.
Input Values are entered from a screen. Output Values are stored in the Repository.
If you choose to refresh the screen, Pre-Screen Logic is performed and the Ispec screen is displayed with fields cleared of entries except for those pre-filled by the Pre- Screen Logic. If you choose not to refresh the screen, and no RECALL; command is executed, the Select a Screen dialog (in Developer Test) or the Ispec Selection screen (in the deployed system) is displayed instead.
If you want to display a different Ispec screen, use the RECALL; Logic command. The Refresh Screen check box is disabled if the Ispec is defined as Usage Output.
Allow Purge
The Allow Purge check box applies only to Components with an Ordinate (i.e. Standard, Table, and Automaint Memo Components).
Check this check box to allow users of your generated system to physically delete records for the Component using the standard Ispec screen. When the record is displayed on the screen, an entry of PUR in the Maint field causes a physical delete.
External Only Ispec
The External Only Ispec check box applies only to Ispecs with Usage Input. Check this check box to define the format of Ispecs targeted by an AUTO.ENTRY; EXTERNAL; statement.
Checking the External Only Ispec check box automatically sets the Auto Entry Capable option.
Note that Developer Test does not support external Auto Entries and sets GLB.STATUS to NODB. Developer Test rejects a DETERMINE; or LOOK.UP; reference to an Ispec defined as External Only with the error message “ispecname external only, cannot be read”.
Accept OLTP Trans.
Check this check box to specify that the Ispec is able to accept OLTP transactions. The Ispec will only receive transactions if you have:
• Checked the Enable OLTP check box in the Business Segment OLTP Options dialog box.
• Specified a service name in the Ispec OLTP dialog box of the Generate Set used to generate the System.
The OLTP Reply check box is automatically checked when you check the Accept OLTP Transaction check box. These options can also be used independently of each other.
OLTP Reply
Check this check box to enable the Ispec to reply to OLTP transactions. An Ispec buffer definition is also generated for definition to OLTP.
The OLTP Reply check box is automatically checked when you check the Accept OLTP Transaction check box. These options can also be used independently of each other.
Note: COPY.FROM Ispecs cannot accept OLTP transactions.
Copy from line # and to line #
Use these fields to key in a starting line number and ending line number in order to specify which lines are to be repeated in a COPY.FROM Ispec.
COPY.FROM Ispecs cannot have Automatic Entry or REPEAT.FROM capabilities. Numeric, maximum length 2 digits, value must be in the range of 2 through 23.
Note: These fields are disabled for Big Buffer Ispecs. For Big Buffer Ispecs, values are updated as the COPY.FROM items are manipulated in the Data Item List.
Max Copies
Use this field to specify the maximum number of times a group of lines (defined by the Copy from line # and the Copy to line # fields) are to be repeated in a COPY.FROM Ispec being added.
Numeric, maximum length 2 digits, value cannot be greater than 23. For Big Buffer Ispecs:
Numeric, maximum length 4 digits, value cannot be greater than 9999
Note: These fields must be completed to enable the display attributes for Copy.From Lines to be set in the Screen Data Items - Display Attributes dialog box.
Big Buffer Enable
Check this check box to indicate that this is a Big Buffer Ispec.
Note: Use of the trace facility with Big Buffer enabled Ispecs may have an adverse performance impact, due to their greater size compared to regular Ispecs. The larger amount of data involved also results in increased space requirements for the log file.
Maximum Size
Use this field to specify the maximum size in bytes, if this is a Big Buffer Ispec. Numeric, value cannot be greater than 65000.
The maximum allowable size for a Big Buffer Ispec is dependant upon to the
characteristics of each target host. The following table lists the maximum size, in bytes, for a Big Buffer Ispec.
Caution
A Big Buffer Ispec can only be reverted to a regular Ispec if all of its Data Items (other than System Data Items) are removed.
This means that once checked, the Big Buffer Enable check box is disabled until all Data Items are removed from the Ispec, even if none of these Data Items are positioned outside the regular Ispec buffer
MCP OS 2200 Windows UNIX
Online Distributed Transaction
Processing (OLTP) 65000 65000 65000 64900 External Automatic Entry
(HUB) 2000 2000 65000 64900
Non-Formatted Input/Output (NOF), Intelligent Terminal Interface
45000 65000 Not
applicable Not applicable Non-Formatted Input/Output
(NOF), Programmatic Interface
65000 65000 65000 64900
Graphical Interface Workbench
16000
Remote Access Server (RATL) protocol must be used
16000
Use of Remote Access Server (RATL) protocol is recommended, as other protocols are not supported
Web Enabler 16000 16000 16000 16000
Notes:
• Developer Test
Developer Test only supports Big Buffer Ispecs that are equal to, or less than 32737 bytes in size.
In addition, if you are using Enterprise Application Workbench to test forms in a Developer Test session using INFOConnect, only Big Buffer Ispecs that are equal to, or less than, 1987 bytes are supported. You can avoid this limitation by using Developer Test's Remote Access Server (RATL protocol) instead of INFOConnect. • Web Enabler
Web Enabler does not show full Big Buffer fields when using Netscape browser. Web Enabler does not show 4095 character Big Buffer fields on Windows 95, Windows 98, or Macintosh.
Foreground
Select a foreground color for the Ispec from the drop-down list. Available colors are Red, Blue, Ebony (black), Magenta, Cyan, White, Yellow, and Green.
A value of Default means that the settings specified in the Foreground Color field on the Business Segment Options dialog box will be used. The default foreground color for a Business Segment is Ebony.
Background
Select a background color for the Ispec from the drop-down list. Available colors are Red, Blue, Ebony (black), Magenta, Cyan, White, Yellow, and Green.
A value of Default means that the settings specified in the Background Color field on the Business Segment Options dialog box will be used. The default background color for a Business Segment is White.
Integrity
Enter Y in this field if you want Developer to lock the dataset when the Ispec is updated. This ensures processing integrity and a fully synchronized recovery.
Setting Integrity to Y may have a major impact on the performance of your system. See Integrity for more information before setting this field.
Automaint Profile
The Automaint Profile field applies only to Memo Components.
Use this field to specify the name of the Profile for an Automaint Memo Component. The Automaint Profile spans the Data Items used as Ordinates for a Component.
If the Long Names option is enabled, you must create a Profile before you specify it as an Automaint Profile in a Memo Component. In the Profile Options dialog box you must uncheck the Duplicates Allowed check box. If you do not create a Profile, Developer will return an error message informing you that the Profile does not exist.
The following conditions must be met for the Automaint Profile field to be completed:
• The value in the Usage field must be Output or I-O (Input/Output). • The Ispec type must be Memo Component.
• The Profile that you specify in this field must not have the Duplicates Allowed
field selected.
• The name must not start with a number or a minus symbol (-). Alphanumeric, maximum length 9 characters.
Setting the Edit Type: The edit type of an Automaint Profile Ordinate must be the same in all the Ispecs in which it is used. The exception to this is where the edit type is one of the numerical types: Number, Signed, Credit, + or -. These do not have to be the same, but cannot be used with the edit types Alpha or Date.
Changing Automaint Profile Ordinates: If you change a Data Item to an
Automaint Profile Ordinate, instances of that Data Item where the edit type differs will have the edit, length, and decimal attributes changed to those of the Automaint Profile Ordinate. This also occurs if you change the edit type of a Data Item that is used in the
Same As field of an Automaint Profile Ordinate.
Primary Profile
The Primary Profile field applies only to OS 2200 based Memo Components. This field is enabled only for Memo Components with Usage Input/Output or Usage Output. Use this field to set up the primary keys of the RDMS table for a Memo Component. Enter the name of an existing unconditional Profile over the Component. If you do not specify a Profile, the first unconditional Profile (in alphabetical order) over the
Component is used. If no Profile exists over the Component, GLB_DTIME is used.
Default Cursor Field
Use the field Default Cursor Field to specify where the cursor is to be positioned when the Ispec is redisplayed in Developer Test. This setting may be overridden with the CURSOR; logic command.
The default value of spaces positions the cursor in the first entry field. To specify another field, key in the data display name associated with the Data Item where the cursor is to be positioned when the Ispec is accessed.
Binary Numerics
This option is available when OS 2200 is the only target host type selected. Use it to format numeric Data Items using RDMS binary numeric formats and save storage space on the host.
Use the Binary Numerics field to set the default format of numeric Data Items contained in the Ispec, overriding any default specified in the Business Segment. The options are:
Value Description
N Binary numerics are not used. Y Binary numerics are used.
I Binary numerics are not used. All numerics are formatted as DECIMAL. D Default. Use the setting in the Business Segment Options dialog box.
National Item
This field applies to ClearPath MCP and UNIX operating system target hosts only. If you select:
• Yes, all the alpha Data Items in the Ispec with the Default National Item attribute are National Items.
• No, alpha Data Items with the Default National Item attribute are non-National Items.
• Default, alpha Data Items with the Default National Item attribute inherit the setting from the Business Segment dialog box.
For Events, this field is set to Default and cannot be changed. This option can be overridden for 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.
Database Path
Use the Database Path field to specify the location of the Developer Test database. Use the Browse buttons or key in the path (drive and directory) for the database location. 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 hostname 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).
Subsystem
The Subsystem field applies only to Systems for MCP based hosts.
Use the Subsystem field to allocate an Ispec to a Subsystem. Select the appropriate Subsystem from the drop-down list.
Note: In Developer, the Subsystem for each Ispec can be specified in two places. It can be specified in the Ispec Options dialog, and also in each Generate Set. The two settings are completely independent of one another. This means you can have two Generate Sets with Ispecs allocated to different Subsystems in each Generate Set.
In All Subsystems
The In All Subsystems field applies only to Systems for MCP based hosts.
Checking the In All Subsystems check box allocates the Ispec to all Subsystems. The Subsystem field is disabled when this check box is selected.
Limits
The following table contains a summary of the limits for Ispecs for each target host. It