Rational Developer for System z

Bidirectional considerations

SCLM textual files can have content in different bidirectional formats, for example, COBOL files might be in a Visual format, while JAVA is usually Logical. ASCII and XML (text files) can be either visual or logical etc. In general, SCLM member bidirectional format can be different from bidirectional format used by the SCLM Developer Toolkit client.

As a user of SCLM Developer Toolkit, you are responsible for providing the correct client bidirectional format for files that are used. You can do this by using Bidirectional Preferences page and the configuration files. Once this is complete, each file transfer between the SCLM server and client will include bidirectional conversions whenever client and host bidirectional format are different. Incorrect bidirectional format specifications can cause bidirectional data corruption and loss. To activate bidirectional functionality in the SCLM Developer Toolkit client, select the Bidirectional enabled check box on the Bidirectional settings of the SCLM Preferences page.

It is possible to associate with each Language its default host and client bidirectional formats. SCLM languages that have no bidirectional format associated, are assumed to be in a default project level bidirectional format, which is Visual LTR if not defined explicitly.

It is possible to change project default bidirectional format and associate with each SCLM Language persistent host format, which is saved in a host configuration file. Persistent client bidirectional format may also be specified for each SCLM Language and saved in client preferences. Client format of each SCLM member is derived based on correspondent SCLM Language host and client bidirectional format and may be overridden for any populated file using special Bidirectional Attributes dialog.

A checkbox is added in the bidirectional settings dialog to allow adding bidirectional markers to local logical files, the use of bidirectional markers is explained in the next paragraph

Languages bidirectional format should be defined in a SITE.conf, or in a project.conf file, where project is the name of the project being configured.

Here is an example of the bidirectional properties added to SITE.conf file:

*                                                                                                                   
* ---------------- SITE SPECIFIC BIDI OPTIONS ------------------                                                         
*                                                                                                                   
*                                                                                                                   
* BiDi Language default properties                                                                                  
BIDIPROP=LANG=*     TextOrient=LTR TextType=Visual  SymetricSwap=Off NumericSwap=Off                                

Bidi settings specified in SITE.CONF can be overridden for specific project in a project level configuration files:

* BiDi Language default properties                                                    
BIDIPROP=LANG=*     TextOrient=LTR TextType=Visual  SymetricSwap=On  NumericSwap=Off 
BIDIPROP=LANG=JAVA  TextOrient=RTL TextType= Logical SymetricSwap=On  NumericSwap=Off  
BIDIPROP=LANG=COBOL TextOrient=RTL TextType= Visual SymetricSwap=Off NumericSwap=Off  

In order to have correct code page conversion you must also to specify correct code pages in Translate.conf file.

* -------------------- CODEPAGE SECTION ----------------------
* IBM-1047 is the default EBCDIC codepage used.
* IBM-424 is the default EBCDIC codepage used for Hebrew.
* IBM-420 is the default EBCDIC codepage used for Arabic .
*
CODEPAGE ASCII = UTF-8
CODEPAGE EBCDIC = IBM-424

In addition to host default language level definitions in SCLM host configuration files described above, you can specify client bidirectional format using the Bi-directional Settings Page. Be sure to select the Bidirectional Enabled check box.

Initially you can only change the DEFAULT local format. Specific languages format can be specified after your SCLM project has been populated, using the New button. You can also access the Update bidirectional preferences for new languages dialog from various stages of SCLM development, including populate, import etc.

It is important to understand that default settings specified in this dialog are saved in preferences and have a permanent global effect. You are allowed to change Type, Orientation, and Symmetric and Numeric swapping for Arabic language. Use the Allow Markers insertion checkbox to switch between standard Logical and Smart Logical bidi formats. Smart Logical format allows correct display of host visual data on Windows clients, and editing it with System z® LPEX. System z LPEX editor allows visual editing of bidirectional data through a special visual line, that becomes available by selecting the Alt =.

Use of other editors for Smart Logical data is strongly discouraged.

It is important that the correct parser is associated with each language. This parser controls the correct handling of complex bidi language dependent expressions.

Once LANGUAGE level bidirectional format is defined, you can use the Bidirectional Attributes dialog to view current Host and Local bidirectional format for a selected file and override it. Selections made in this dialog will only affect the currently populated files. To access this dialog from within the SCLM View, right click and select Bidirectional Settings Dialog.... To access this dialog from within the Package Explorer, right click and select Team>Bidirectional Settings Dialog.... Alternatively, you can use the Bidirectional Options button available from some of the SCLM functions.


Feedback