SAS/AF Software: Class Dictionary

390 Operating Environments

While SAS/AF Version 7 software does not support build-time development of FRAME entries in the CMS or OS/390 environments, you can port applications developed in other desktop environments to a mainframe. This section describes

development tips that you can use when developing applications that you port to CMS or OS/390
host-specific behavior for SAS/AF visual components running on programmed symbol graphics devices (such as 32xx terminals)
host-specific behavior for SAS/AF visual components running on vector graphics devices (such as 31xx terminals)

Note that while a component or control may display properly, some associated methods may not work in the mainframe operating environment. For example, the _setCursorShape method enables the user to set the cursor shape used when the cursor moves over a visual control. On programmed symbol graphics devices, terminal buffering prevents SAS/AF from detecting cursor movement unless the ENTER key or a PF key is pressed.

Development Tips

When you develop a frame for use in a mainframe environment, it is recommended that you port the frame to the target platform to view the frame using the same display that your users will use. The sizing of visual components on a frame can be affected by the host environment due to differences in the system fonts between the development and run-time environments. Currently, font sizes can vary depending on the display device used. Known font sizes for mainframe devices include 9x12, 9x16, 9x14, 8x14, and 6x12 font sizes. In addition, you may want to leave scrollbars turned on for your frames to ensure that all users will be able to see the entire layout.

It is also important to test a SAS/AF application on all display devices used by your mainframe users. You may find that applications developed with many different types of graphical components may not work well on programmed symbol devices but will work correctly on vector graphics devices.

Also, keep in mind the following restrictions when developing frame-based applications for use in a mainframe environment:

Text and graphic alignment may differ between the build-time environment and the mainframe run-time environment. Since programmed symbol devices use a fixed font that must be aligned to a cell boundary, objects placed on a frame in a build-time environment that does not have that restriction may appear differently at run-time.
Certain events or functions that are supported in other environments do not work in OS/390 or CMS, including mouse movement, drag and drop, double-clicking, selecting either mouse button 2 or 3, and others.
Some 3270 display devices have a very limited color selection. When a color such as gray is displayed on a terminal that must choose, for instance, between black or white, some visual objects on the frame may not appear or may disappear into the background of the frame.
Once a SAS window has entered a "wait for input" state, the user must respond before output or updates to other windows can occur.

Host-Specific Behavior for SAS/AF Classes on Programmed Symbol Graphics Devices

This section describes the expected behavior and use of SAS/AF visual classes running on CMS or OS/390 and displayed on a terminal that supports programmed symbol graphics (such as 32xx terminals). The following table contains a list of SAS/AF classes that are either not implemented or exhibit different behavior on CMS and OS/390 operating systems than in other desktop environments.

Component
Behavior

Combo Box Control The combo box displays but its text may display outside of the region. The first item in the list is initially displayed. (In other operating systems, the combo box is intially empty.)

Command Push Button This component may not appear recognizable; a user may have to position the cursor slightly outside of the component's region and press Enter to activate the component.

Container Box This component does not display all four sides of its region.

Control Object This component may not appear recognizable. The control responds when a user positions the cursor on the control object and then presses ENTER.

Critical Success Factor This component may not appear recognizable and is not usable.

Data Form Since pop-up menus are not available, commands such as right, left, forward, and backward must be executed using function keys. Earmarks will not work and text may be truncated.

Data Table (Table Editor) Editing is not supported in the data table or table editor classes since programmed symbol graphics devices do not support the graphic text input required by the table editor.
It is recommended that your applications use FSVIEW for table editing functionality.

Extended Input Field The extended input field restricts the length of its displayed text.

Extended Text Entry Immendiate feedback is not supported in the extended text entry (or ETE). Users cannot enter text directly into the control, but rather must do so through a dialog displayed by the host environment for text entry. (See the issues for Input Field below.)

Graphics The graphic object requires specific settings to display properly with programmed symbol graphics devices.

Graphics Text In some instances, the first and/or last characters of the text string may be truncated.

Hotspot This component is not supported on this device.

Image This component is not supported on this device.

Image Icon This component is not supported on this device.

Input Field This component displays as its alternate definition, the Text Entry component. This alternative adds two (2) characters of padding so that the input field may expand by two characters from its build-time position. In addition, text truncation can occur.
It is recommended that you allow for additional space above, below, and on both sides of an input field when designing an application that is portable to devices on a mainframe.

Input Field Label This component displays as its alternate definition, the Text Entry component. This alternative adds two (2) characters of padding so that the input field may expand by two characters from its build-time position. In addition, the label text may be truncated.
It is recommended that you allow for additional space above, below, and on both sides of an input field label when designing an application that is portable to devices on a mainframe.

Organizational Chart This component is not supported on this device.

Process Flow Diagram (PFD) This component is not supported on this device.

Push Button Text in the push button region may be truncated if you do not allow for extra space. You may need to add one or more extra blank characters.

SAS/GRAPH Output The component does not display properly on this device.

Tab Layout Object The tab layout does not support selection of a tab other than the first tab on this device. It is therefore unusable.

Toolbar Since the Image component is not supported, toolbars defined with image and text elements do not display or function properly.

Video Player This component is not supported on this device.

Work Area This component does not work as designed since it relies on pop-up menus and drag-and-drop functionality. It is possible, however, to implement a scheme that uses method calls driven by objects that display correctly, such as a push button.

Component	Behavior
Combo Box Control	The combo box displays but its text may display outside of the region. The first item in the list is initially displayed. (In other operating systems, the combo box is intially empty.)
Command Push Button	This component may not appear recognizable; a user may have to position the cursor slightly outside of the component's region and press Enter to activate the component.
Container Box	This component does not display all four sides of its region.
Control Object	This component may not appear recognizable. The control responds when a user positions the cursor on the control object and then presses ENTER.
Critical Success Factor	This component may not appear recognizable and is not usable.
Data Form	Since pop-up menus are not available, commands such as right, left, forward, and backward must be executed using function keys. Earmarks will not work and text may be truncated.
Data Table (Table Editor)	Editing is not supported in the data table or table editor classes since programmed symbol graphics devices do not support the graphic text input required by the table editor. It is recommended that your applications use FSVIEW for table editing functionality.
Extended Input Field	The extended input field restricts the length of its displayed text.
Extended Text Entry	Immendiate feedback is not supported in the extended text entry (or ETE). Users cannot enter text directly into the control, but rather must do so through a dialog displayed by the host environment for text entry. (See the issues for Input Field below.)
Graphics	The graphic object requires specific settings to display properly with programmed symbol graphics devices.
Graphics Text	In some instances, the first and/or last characters of the text string may be truncated.
Hotspot	This component is not supported on this device.
Image	This component is not supported on this device.
Image Icon	This component is not supported on this device.
Input Field	This component displays as its alternate definition, the Text Entry component. This alternative adds two (2) characters of padding so that the input field may expand by two characters from its build-time position. In addition, text truncation can occur. It is recommended that you allow for additional space above, below, and on both sides of an input field when designing an application that is portable to devices on a mainframe.
Input Field Label	This component displays as its alternate definition, the Text Entry component. This alternative adds two (2) characters of padding so that the input field may expand by two characters from its build-time position. In addition, the label text may be truncated. It is recommended that you allow for additional space above, below, and on both sides of an input field label when designing an application that is portable to devices on a mainframe.
Organizational Chart	This component is not supported on this device.
Process Flow Diagram (PFD)	This component is not supported on this device.
Push Button	Text in the push button region may be truncated if you do not allow for extra space. You may need to add one or more extra blank characters.
SAS/GRAPH Output	The component does not display properly on this device.
Tab Layout Object	The tab layout does not support selection of a tab other than the first tab on this device. It is therefore unusable.
Toolbar	Since the Image component is not supported, toolbars defined with image and text elements do not display or function properly.
Video Player	This component is not supported on this device.
Work Area	This component does not work as designed since it relies on pop-up menus and drag-and-drop functionality. It is possible, however, to implement a scheme that uses method calls driven by objects that display correctly, such as a push button.

Host-Specific Behavior for SAS/AF Classes on Vector Graphics Devices

This section describes the expected behavior and use of SAS/AF visual classes running on CMS or OS/390 and displayed on a terminal that supports vector graphics (such as 31xx terminals). The following table contains a list of SAS/AF classes that are either not implemented or exhibit different behavior on CMS and OS/390 operating systems than in other desktop environments.

Component
Behavior

Check Box Control The check box displays but its associated text label may display outside of the region.

Combo Box Control The combo box displays but its text may display outside of the region. The first item in the list is initially displayed. (In other operating systems, the combo box is intially empty.)

Data Form Since pop-up menus are not available, commands such as right, left, forward, and backward must be executed using function keys. Earmarks will not work.

Data Table (Table Editor) Editing is not supported in the data table or table editor classes since vector graphics devices do not support the graphic text input required by the table editor. By default, grid lines do not display in the table. To view grid lines, the data table's grid line color must be set to any color other than Background or Secondary.

Extended Text Entry Immendiate feedback is not supported in the extended text entry (or ETE). Users cannot enter text directly into the control, but rather must do so through a dialog displayed by the host environment for text entry. (See the issues for Input Field below.)

Graphic Text Control The graphic text is displayed using the DMS font; other fonts are not supported for CMS and OS/390 environments.

Image This component is not supported on this device.

Image Icon This component is not supported on this device.

Input Field This component displays as its alternate definition, the Text Entry component. This alternative adds two (2) characters of padding so that the input field may expand by two characters from its build-time position. In addition, text truncation can occur.
It is recommended that you allow for additional space above, below, and on both sides of an input field when designing an application that is portable to vector graphics devices on a mainframe.

Input Field Label This component displays as its alternate definition, the Text Entry component. This alternative adds two (2) characters of padding so that the input field may expand by two characters from its build-time position. In addition, the label text may be truncated.
It is recommended that you allow for additional space above, below, and on both sides of an input field label when designing an application that is portable to vector graphics devices on a mainframe.

Organizational Chart This component is not supported on this device.

Process Flow Diagram (PFD) This component is not supported on this device.

Push Button Text in the push button region may be truncated if you do not allow for extra space. You may need to add one or more extra blank characters.

Push Button Control The push button control is displayed using the DMS font; other fonts are not supported for vector graphics devices using CMS or OS/390.

Radio Box Control The radio box control displays, but its title does not display. Borders for radio box controls are also unsupported in CMS and OS/390.

Toolbar Since the Image component is not supported, toolbars defined with image and text elements do not display or function on vector graphics devices using CMS or OS/390.

Video Player This component is not supported on this device.

Work Area This component does not work as designed since it relies on pop-up menus and drag-and-drop functionality. It is possible, however, to implement a scheme that uses method calls driven by objects that display correctly, such as a push button.

Component	Behavior
Check Box Control	The check box displays but its associated text label may display outside of the region.
Combo Box Control	The combo box displays but its text may display outside of the region. The first item in the list is initially displayed. (In other operating systems, the combo box is intially empty.)
Data Form	Since pop-up menus are not available, commands such as right, left, forward, and backward must be executed using function keys. Earmarks will not work.
Data Table (Table Editor)	Editing is not supported in the data table or table editor classes since vector graphics devices do not support the graphic text input required by the table editor. By default, grid lines do not display in the table. To view grid lines, the data table's grid line color must be set to any color other than Background or Secondary.
Extended Text Entry	Immendiate feedback is not supported in the extended text entry (or ETE). Users cannot enter text directly into the control, but rather must do so through a dialog displayed by the host environment for text entry. (See the issues for Input Field below.)
Graphic Text Control	The graphic text is displayed using the DMS font; other fonts are not supported for CMS and OS/390 environments.
Image	This component is not supported on this device.
Image Icon	This component is not supported on this device.
Input Field	This component displays as its alternate definition, the Text Entry component. This alternative adds two (2) characters of padding so that the input field may expand by two characters from its build-time position. In addition, text truncation can occur. It is recommended that you allow for additional space above, below, and on both sides of an input field when designing an application that is portable to vector graphics devices on a mainframe.
Input Field Label	This component displays as its alternate definition, the Text Entry component. This alternative adds two (2) characters of padding so that the input field may expand by two characters from its build-time position. In addition, the label text may be truncated. It is recommended that you allow for additional space above, below, and on both sides of an input field label when designing an application that is portable to vector graphics devices on a mainframe.
Organizational Chart	This component is not supported on this device.
Process Flow Diagram (PFD)	This component is not supported on this device.
Push Button	Text in the push button region may be truncated if you do not allow for extra space. You may need to add one or more extra blank characters.
Push Button Control	The push button control is displayed using the DMS font; other fonts are not supported for vector graphics devices using CMS or OS/390.
Radio Box Control	The radio box control displays, but its title does not display. Borders for radio box controls are also unsupported in CMS and OS/390.
Toolbar	Since the Image component is not supported, toolbars defined with image and text elements do not display or function on vector graphics devices using CMS or OS/390.
Video Player	This component is not supported on this device.
Work Area	This component does not work as designed since it relies on pop-up menus and drag-and-drop functionality. It is possible, however, to implement a scheme that uses method calls driven by objects that display correctly, such as a push button.

Chapter Contents
Previous
Next
Top of Page