x

To access these settings, double-click E-mail SMTP Server in the navigation pane.

This chart describes the settings on the E-mail SMTP Server page. The settings are saved in the odin.cfg file.

When you have completed your entries, optionally click the Send Test E-mail button to test your connection, then click Save.

Parameter	Description
smtp_host	Enter the IP address of the SMTP e-mail server using the notation that is supported for your IP version (for example, for IPv4 use base 256 standard dot notation; when IPv6 is supported on a platform, and enabled, you can use either 256 standard dot notation or IPv6 notation.)
sender_email	Enter the sender e-mail address that appears in the From field in e-mails. Note: If e-mail send operations fail, verify that the smtp host is active and/or that a virus scanner is not blocking edachkup.

x

By customizing event routing, you can launch a procedure or send e-mail based on server events.

1. From the Workspace menu, select Configuration/Monitor.
2. From the navigation pane, right-click Event Routing and select Customize.

   The Customize Event Routing page opens.

3. Click Customize New Event Routing.

   The Customize New Event Routing page opens.

   

4. From the Type drop-down menu, select a message type. The choices are Error, Information, Warning, and Any.
5. Enter a criteria in the Filter field or select a predefined one from the drop-down menu.

   

6. From the EDAPRINT drop-down menu, select Yes if you want to write the selected event message to the server log.

   In z/OS, the selected server messages can be also written to the z/OS system log by selecting Yes from the JESLOG drop-down menu, as shown in the following image.

   

7. Optionally, enter an e-mail address to send an e-mail when the event occurs.
8. Optionally, enter a procedure to execute in the Procedure field, including the application name, for example, utility/movefiles.
9. Click Add.

   The event is added to the Customize Event Routing Page.

   

10. Click Save and Restart Server.

x

E-mail notifications from event routing include lines from the edaprint log file in the e-mail body. This provides information about the events occurring on the server before the triggered event. The number of edaprint lines included is set using the logging_email_edaprint parameter.

Top of page

x

To access these settings, double-click License in the navigation pane.

This chart describes the settings on the License Management page. The settings are saved in the edaserv.cfg file.

When you have completed your entries, click Save and Restart Server.

Parameter	Description
license	Enter the license number (required for the type of server you are using).
license_active_report	Enter the license number for WebFOCUS Active Technologies.
license_rstat	Enter the license number for the RStat scoring feature.
site_code	Enter the site code number (required for support calls).
license for XBRL options	Enter the license number for the XBRL feature.

x

Users that want to output Arabic characters in PDF or PostScript formats can now select the Times New Roman font.

x

Users that want to output Thai characters in PDF or PostScript formats can now select the Tahoma font.

x

To access these settings, double-click NLS in the navigation pane.

This chart describes the settings on the NLS Configuration Wizard. NLS settings are saved in the nlscfg.err file.

Complete the configuration, then click Save and Restart Server. The server creates the necessary transcoding, sorting, and monocasing tables for the selected code page.

Parameter	Description
CODE_PAGE	Is the code page of the data sources accessed by the server. Select a code page from the drop-down list of supported code pages, including Unicode. The default value is 137 for Windows and UNIX, and 37 for IBM i (formerly known as i5/OS) and z/OS.
LANG	Controls the default value of the code page, and the language of server error messages if available in translation. Choose a language name or abbreviation from the drop-down list. The default value is AMENGLISH (American English) on all platforms. An asterisk to the right of a language, for example, French*, means that the server is localized for that language. Translated server error messages (for example, FOCnnn through FOCnnnnn) are available and the Web Console is fully displayed in that language once you configure and restart the server. For related information, see How to Add a Dynamic Language Switch to the Web Console Menu Bar. If you choose a language without an asterisk, the server messages and console appear in English. If you would like the messages and console to appear in a language for which the server has not been localized, you can provide translation yourself. To localize the console, translate the file wceng.lng and rename it to wcXXX.lng where 'XXX' is the three-letter language code for the server. For error messages, translate all or any relevant *.err files and append the same three-letter language code to it. All files are located in the \home\nls folder. For related information, see How to Create a Localized Version of the Web Console Manually.
CURRENCY	Enter a one-byte character or hexadecimal value that identifies a currency symbol. Examples of one-byte characters are: € for euro ¥ for yen $ for U.S. dollar £ for British pound sterling You can use any other single character to designate the currency symbol. Examples of a hexadecimal value on code page 137 are: 0x80 for euro 0x24 for dollar sign
DATEOUTPUT	Selecting Localized from the drop-down menu will provide dates in a localized format.
Customize code page conversion tables	Select this check box to display a list of code pages and descriptions for the possible data sources accessed by the server or the client code page. Several code pages are always selected by default and cannot be deselected. These are: 37 --IBM MF United States 137 --U.S. English/Western Europe (Latin 1) 437 --U.S. English 1047 --IBM MF Open Systems (Latin 1) 1252 --Windows Latin; 65001 --Unicode (UTF-8) 650001 Unicode (UTF-8) 650002 Unicode (UTF-EBCDIC) Other code pages may also be selected by default, depending on the LANG attribute chosen. The NLS Configuration Wizard creates conversion tables for these code pages to make them available for subsequent conversion. Select any additional code pages for which you want tables to be created. For example, if you want to designate a particular code page to be generated in synonyms for flat (fixed) files or VSAM files, you must already have created a code page conversion table using the Customize code page conversion table option during NLS configuration.
Recreate FOCUS system files	Check this box if you wish to load FOCUS internal files in the server code page (as defined in the CODE_PAGE field).
Recreate FOCUS sample files	Check this box if you wish to load the sample files (which are delivered with your software) in the server code page (as defined in the CODE_PAGE field).
TSGU command	TSGU is a utility program to configure NLS settings. It is usually not required, but in the following cases it must be executed manually. To create PDFXTBL. When TYPE 1 fonts should be included in PDF format file, the TYPE 1 font transcoding table must be generated using the following syntax: PDFX {font-name} To create PDFYTBL. When Unicode fonts should be used in PDF format file, the special font information tables (PDFYTBL) must be generated using the following syntax: KTBL {pdfy-name}

x

When you configure the server for NLS:

1. Choose a language with an asterisk (*) from the LANG drop-down list. The asterisk indicates that the localized version of the Web Console is available for that language.
2. Click the Save and Restart button.
3. When the server restarts, the Web Console is displayed in the selected language.

   If you selected a Western European language when configuring the code page, the associated group of Western European languages, as well as English, are available on a menu to the left of the Help option.

4. To toggle among these languages, simply select the one you want from this menu.

In this example, Spanish has been chosen from the menu so the Web Console, as well as any translated error messages, are displayed in the selected language.

x

Follow this procedure to localize a language that does not have an asterisk next to its name in the LANG drop-down list. This will enable users to see both the Web Console and the Data Management Console in the localized language.

When adding a localized language, the following files must be created for each language. These files are located in the EDAHOME\nls directory (for example, c:\ibi\srv77\home\nls).

Each file contains the list of strings that are used in specific product areas.

Area	String
Web Console	wc***.lng
Synonym Editor	nt***.lng
Data Management Console	wc***.lng and dm***.lng

where:

***

Represents the 3-letter language abbreviation code for the new language you will be translating.

To localize the files listed in the chart, complete the following steps:

1. Identify the abbreviation code of the new language. To obtain a list of available codes, run the ? LANG SET command as a procedure. The column LANGAB (Language Abbreviation) shows the 3-letter (***) codes.
2. Copy the three component files that have the English strings and rename them using the new language code. (The English versions of the files use the 'eng' language abbreviation code.)
3. Translate the files with the new language abbreviation codes. To do so, open each component file in a Text Editor and proceed with the translation using the following guidelines:
   • Translate the strings on the right side of the "=" sign. (The left side of the = sign contains the string numbers; do not change these values.)
   • Some strings contain multiple variables (placeholders), such as %s/%s. Be especially careful to place these strings in context within your translation.

     For example, in the string:

     4040 = Create Synonym for %s %s

     %s %s represents the table name for which you are creating a synonym. In some languages, the table name may be identified in the beginning or the middle of the sentence, therefore the variable must be placed accordingly.

4. Save the translated file in EDAHOME\nls directory (c:\ibi\srv77\home\nls) using an encoding system that is compatible with the language's default code page. To check the default code page, run the ? LANG SET command as a procedure. The column CODEPG (Code Page) shows the code page.
5. Once the new language files exist, you can add the localized language to the Dynamic Language Switch menu by including the ADDLANG parameter in the nlscfg.err file.

   To edit the nlscfg.err file, on the Reporting Server Console menu bar choose Workspace, then Configuration. In the navigation pane, click Configuration Files, Miscellaneous, then select NLS.

   The nlscfg.err file opens in the text editor. Add the following line of code

   ADDLANG=language_name                

   where:

   language_name

   Is the language abbreviation code (LANGAB) or language name (LANGNM) from the ? LANG SET table.

6. To test the new language, configure the WebFOCUS Reporting Server for NLS and select the language you just translated as the LANG=value.
7. Save and restart the Server. When the Server restarts, the localized language option will be available on the Dynamic Language Switch pull-down menu.
8. Choose the desired language and verify that all menus and options are translated and functioning.

Note: For your convenience, two reference charts that contain the output generated by the ? LANG SET command are included in this document. For details, see Language and Default Code Pages for Windows and UNIX or Language and Default Code Pages for IBM i and z/OS.

Top of page

Example: Localizing the Web Console Into Finnish

For this example, assume that the server is running on Windows and the NLS setting is CODE_PAGE=137 LANG=AMENGLISH).

Follow these steps:

1. The wceng.lng file contains the original English strings for the Web Console. Copy and rename the file wcfin.lng.
2. Translate wcfin.lng into Finnish and save it as Latin1(ISO8859-1) in the c:\ibi\srv77\home\nls directory.
3. From the Reporting Server Console menu bar choose Workspace, then Configuration. In the navigation pane, click Configuration Files, Miscellaneous, then select NLS.

   The nlscfg.err file opens in the text editor. Add the following line of code:

   ADDLANG=FINNISH

4. Click the Save and Restart button for the changes to take effect.
5. To apply the Finnish translation, choose FINNISH from the dynamic language switch drop-down list on the Web Console menu bar.

x

This chart provides information generated by the ? LANG SET command from the Windows and UNIX platforms.

Language Code	Language Name	Language Abbreviation	Language ID	Code Page
001	AMENGLISH	AME	en	437
001	ENGLISH	ENG	en	437
020	ARABIC	ARB	ar	1256
10351	B-PORTUGUESE	BRA	br	137
420	CZECH	CZE	cs	1250
045	DANISH	DAN	da	137
031	DUTCH	DUT	nl	137
372	ESTONIAN	EST	et	923
358	FINNISH	FIN	fi	137
033	FRENCH	FRE	fr	137
033	FRENCH	FRE	fc	137
049	GERMAN	GER	de	137
049	GERMAN	GER	at	137
030	GREEK	GRE	el	1253
972	HEBREW	HEB	iw	916
036	HUNGARIAN	HUN	hu	1250
039	ITALIAN	ITA	it	137
081	JAPANESE	JPN	ja	942
081	JAPANESE-EUC	JPE	je	10942
082	KOREAN	KOR	ko	949
371	LATVIAN	LVA	lv	1257
370	LITHUANIAN	LTU	lt	1257
047	NORWEGIAN	NOR	no	137
048	POLISH	POL	pl	1250
351	PORTUGUESE	POR	pt	137
040	ROMANIAN	ROM	ro	1250
007	RUSSIAN	RUS	ru	1251
085	S-CHINESE	PRC	zh	946
034	SPANISH	SPA	es	137
046	SWEDISH	SWE	sv	137
086	T-CHINESE	ROC	tw	10948
066	THAI	THA	th	874
090	TURKISH	TUR	tr	920
044	UKENGLISH	UKE	uk	137
800	UNICODE	UCS	uc	65001

x

This chart provides information generated by the ? LANG SET command from the IBM i and z/OS platforms.

Language Code	Language Name	Language Abbreviation	Language ID	Code Page
001	AMENGLISH	AME	en	37
001	ENGLISH	ENG	en	37
020	ARABIC	ARB	ar	420
10351	B-PORTUGUESE	BRA	br	37
420	CZECH	CZE	cz	870
045	DANISH	DAN	da	277
031	DUTCH	DUT	nl	37
372	ESTONIAN	EST	et	1112
358	FINNISH	FIN	fi	278
033	FRENCH	FRE	fr	297
033	FRENCH	FRE	fc	297
049	GERMAN	GER	de	273
049	GERMAN-500	GE5	at	500
030	GREEK	GRE	el	875
972	HEBREW	HEB	iw	424
036	HUNGARIAN	HUN	hu	870
039	ITALIAN	ITA	it	280
081	JAPANESE	JPN	ja	939
10081	JAPANESE-930	JPK	jk	930
082	KOREAN	KOR	ko	933
371	LATVIAN	LVA	lv	1112
370	LITHUANIAN	LTU	lt	1112
047	NORWEGIAN	NOR	no	277
048	POLISH	POL	pl	870
351	PORTUGUESE	POR	pt	37
040	ROMANIAN	ROM	ro	870
007	RUSSIAN	RUS	ru	1025
085	S-CHINESE	PRC	zh	935
042	SLOVAK	SVK	sk	870
034	SPANISH	SPA	es	284
046	SWEDISH	SWE	sv	278
086	T-CHINESE	ROC	tw	937
066	THAI	THA	th	838
090	TURKISH	TUR	tr	1026
044	UKENGLISH	UKE	uk	285
800	UNICODE	UCS	uc	65002

x

To access these settings, double-click Profile Settings in the navigation pane.

This chart describes the parameter settings on the Profile Settings pane. These settings are saved in the edaserv.cfg file.

When you have completed your entries, click Save.

Parameter	Description
profile parameter	By passing parameters to profiles, you can submit different session parameters at different connection times. When this parameter is activated, any unresolved variables are prompted for during your initial logon to the Web Console. Available settings are y and n. If the server, user, or group profiles contain any unresolved variables, set the profile parameter keyword to y. The default setting is n.
group_profile	To control the execution of group profiles during logon, choose: All. All group profiles for the connecting user are executed in alphabetic order. Select. If the user exists in more than one group, the Web Console prompts for a group or groups and executes the associated profiles in ascending order. Primary. Only the primary group profile for the connecting user is executed. (This is the default setting.)
profile_ no_domain *	In the Windows Server, to control whether the domain name is included in or excluded from a user profile name, choose: n to add the domain name to the profile name (for example, user ibi/edaport becomes ibi_edaport.prf). N is the default value. y to omit the domain name from the profile name (for example, user ibi/edaport becomes edaport.prf). This setting is required for compatibility with earlier releases of the Server. Note: The y setting can be safely employed if a single domain is in use and there are no local user IDs that could interfere with domain IDs. If there is potential for interference between local user IDs and domain IDs that are connected to the server, the n setting is required to ensure that each user has a unique profile name. Note that server must be restarted when this parameter is changed.

TABLE FILE CAR
PRINT CAR
ON TABLE HOLD AS FOCCACHE/myfile
END

TABLE FILE FOCCACHE/myfile
PRINT * 
END

x

To access these settings, double-click Application Settings in the navigation pane.

This chart describes the parameter settings on the Application Settings page. These settings are saved in the edaserv.cfg file.

When you have completed your entries, click Save and Restart Server.

Parameter	Description
foccache_dir	Defines the location of the foccache directory. The default is edatemp/foccache/....
foccache_ maxage	Defines the maximum number of minutes that a foccache directory will last. The default is 180 minutes. 0 means unlimited (that is, the directory will be remain active as long as the session lasts or the server is running).
nested_app	Selecting y from the drop-down menu enables nested applications.
homeapps	If nested_app is set to y, homeapps defines the location of the home application root directory. With homeapps defined, each connected user will see a My Home applications folder on the Application tree. Users can create new applications (home applications) in this folder. These applications will be visible and available only to the connected user and the server administrator. The user will have full access to his home applications. Note: Only available with a DataMigrator or Managed Reporting license.

x

To access these settings, double-click Miscellaneous Settings in the navigation pane.

This chart describes the parameter settings on the Miscellaneous Settings page. These settings are saved in the edaserv.cfg file.

When you have completed your entries, click Save.

Parameter	Description
automatic_recovery	Determines whether the server will automatically recover crashed listeners and/or special services. The default is n.
transaction_coordination_mode	Selecting y, activates the iWay Transaction Coordinator. A Two-Phase Commit will be used when XA-Compliant databases participate in a transaction. The default is n.
tscom3_kill_delay1	Defines the time (in seconds) allowed for an agent to stop before soft kill is sent. The default is 16.
tscom3_kill_delay2	Defines the time (in seconds) allowed for a soft kill to work before a hard kill is sent. The default is 32.
seslog_max_lines	Defines the upper limit for the number of rows in a session log. When the limit is exceeded, only the latest records will be kept in the session log and the number of records will equal the limit. The default is 500.
stats_runningavg	Defines the time window for the calculation of running response time averages. The default is 600.
proxy_server	Defines a proxy server, which acts as an intermediary on requests for resources from other servers.
proxy_port	Defines the port number of the proxy server.
proxy_user	Defines a user ID for the proxy server.
proxy_password	Defines a password for the user ID connecting to the proxy server.
z/OS Specific Parameters
tmpalloc_primary tmpalloc_secondary	Allocation (in CYLs) for temporary Web Console files allocated by the HTTP listener. The default is 5 and 50, respectively.
submit_opt	Customizes the call of the IKJEFF10 exit when submitting jobs with the DYNAM SUBMIT command.
smf_recno	Defines the SMF record number that the server will use to record utilization statistics.
smf_subtype	Defines which pairs of SMF subtype records are cut. The options are: all - cut all records. This is the default. logon - cut logon/logoff subtype only. query - cut query begin/query end subtype only.
privatedd	Defines how server will handle allocations for duplicated ddnames (same ddname allocated both to IRUNJCL and from a customer application via DYNAM) and what the search strategy will be.

x

To change how the server calls the IKJEFF10 exit, set the submit_opt parameter as follows:

1. From the Web Console menu bar, select Workspace, then Configuration/Monitor.
2. In the navigation pane, double-click Miscellaneous Settings in the navigation pane.

   The Miscellaneous Settings page opens.

3. For the submit_opt option, assign a separate value (0 or 1) in each of the three drop-down lists. The default is 000.

   The first drop-down list enables the call to IKJEFF10 from DYNAM SUBMIT. By default, the call is disabled.

   0

   Does not call IKJEFF10. This is the default setting.

   1

   Calls IKJEFF10.

   The second drop-down list specifies that SUBMIT is to call IKJEFF10 in problem state, not in supervisor state. The IBM specification for IKJEFF10 requires supervisor state. If the version of IKJEFF10 in use at your site is capable of running in problem state, this option may be changed, thus allowing DYNAM SUBMIT to be used with IKJEFF10 when the server is not running APF-authorized. When you set:

   0

   Supervisor state is required for calling IKJEFF10. This is the default setting.

   1

   Supervisor state is not required to call IKJEFF10.

   The third drop-down list allows SUBMIT to continue in the event that an error occurs while processing an in-stream data set. In-stream data sets are created by the following statements in the job:

   //ddname DD *
   //ddname DD DATA
   /*XMIT
   //name XMIT
   /*DATASET

   If an error is found in one of the previous statements (for example, a syntax error in the DLM parameter), the SUBMIT operation is normally cancelled. This option allows submission of the job to continue, although in such a case the results are unpredictable since the JCL contained within the in-stream data set may be erroneously interpreted as part of the job being submitted.

   0

   Terminates SUBMIT on in-stream data set error. This is the default setting.

   1

   Does not terminate SUBMIT on in-stream data set error.

4. Click Save.

Your entries are registered in the edaserve.cfg file.

x

To migrate from a previous release:

1. From the Workspace menu, select Configuration/Monitor.
2. From the navigation pane, right-click Migrate and select Configure.

   The Migrate page opens.

   

3. Type the full path of the configuration instance directory (EDACONF).
4. Click Migrate.