[ Bottom of Page | Previous Page | Next Page | Table of Contents | Index ]
This panel contains settings for configuring the Client daemon to communicate with CICS Servers. The panel has these tabs:
To configure a new CICS® server, select New Server from the Tools pulldown, or from the toolbar.
Select the default CICS server from the drop-down
list.
This value specifies
the size of the transmission buffers in which application data or
terminal data flows.
Enter a number of kilobytes, in the
range 4 through 32. The default is 32 KB. If you enter a value
outside the permitted range, the Configuration Tool warns you. If
the value entered is too low, it substitutes the minimum. If the value
entered is too high, it substitutes the maximum. If a non-numeric
value is present in the configuration file, it substitutes the minimum
value.
This value specifies the size of the transmission buffers in which application or terminal data will flow. The value should be large enough to cater for the largest possible COMMAREA or terminal input/output area (TIOA) to be used. The maximum COMMAREA size might be less than the Maximum buffer size, because certain protocols have an overhead of 512 bytes.
Leave this setting at the default unless the CICS Transaction Gateway is running on a machine that is short of memory.
Enter a character string of between 1 and 4 characters. The default is EXIT.
The string, when entered at a terminal emulator at any time and place where a transaction name can be entered, causes the terminal emulator to terminate. The string must not contain any blank characters.
The string is case-sensitive. If a terminal emulator has uppercase translation in its CICS terminal definition, enter this string in uppercase.
Enter a value in the range 1 through 256. The default is 10. If you enter a value outside the permitted range, the Configuration Tool warns you. If the value entered is too low, it substitutes the minimum. If the value entered is too high, it substitutes the maximum. If a non-numeric value is present in the configuration file, it substitutes the minimum value.
This value specifies the maximum number of servers that can be accessed concurrently from the client.
Enter a value as follows:
Product | Minimum | Maximum | Default |
---|---|---|---|
CICS Transaction Gateway | 1 | 10,000 | 256 |
This value specifies the maximum number of concurrent requests that might be executing on the Client daemon, where an item is one of:
It is used to detect runaway conditions where an application could, in error, submit an excessive number of requests to a server. The actual limit might be less than this setting if other operating system limits (for example, memory constraint or communication sessions), come into effect.
CICS Transaction Gateway Desktop Edition: The maximum value for this parameter is 32.
The specified string is a command specific to the operating system under which the CICS Transaction Gateway is running. When a request to print is received, the Client daemon generates a temporary print file with a unique name.
Enter a character string, from 1 to 256 characters long.
The parameter string is appended with the temporary file name, and the resultant command executed. This allows, for example, print requests to be copied to a file, directed to a local printer, formatted for inclusion into documentation, and other similar actions.
Windows® operating system: A command file might be necessary to act as an interface between the syntax of the invocation command defined here, and more general operating system syntax. For example, if the desired final command was COPY printfile LPT2, a simple command file would be required to reorder the parameters. It is the responsibility of the Print command to delete the temporary print file after it has finished processing it.
You can specify only a local executable in this field. UNC paths of the type \\User1\Share\Notepad.exe do not work, due to the system limitations of running executables that are installed on one machine on a different machine.
On UNIX® and Linux® operating systems: Use a shell script with the Print command (for example, lpr) followed by the command to delete (rm).
See also the Print file description for more information.
Enter a character string, 1 to 256 characters long.
This option applies only if you make no entry in the Print command setting.
The specified string identifies a file to which output from print requests received at the Client daemon is directed. Each print request is appended to the end of the current file.
On the Windows operating system: If both this setting and Print command are omitted, the default action is to direct the print data to LPT1.
This setting acts only as a default. The terminal and print emulators provide options to override this value.
Enter a value indicating a Coded Character Set Identifier (CCSID) to override your local code page identifier.
Use this setting if your platform has been updated for euro support, and the CICS Server has euro support. For example, for Latin-1 countries, use a CCSID value of 858 to indicate that the code page 850 includes euro support. For code page 1252, specify a CCSID value of 5348.
Note:Enter a number between 1 and 3600, to specify the time in seconds between attempts by the Client daemon to reconnect to a server. The default is 60 seconds.
When the Client daemon becomes aware that a server to which it was connected is no longer active, it attempts to reconnect to the server one second after it becomes inactive. If it fails it keeps trying, at the interval specified here.
Set the interval to 0 (zero) to disable automatic re-connection attempts.
Select this check box to enable the display of pop-up messages at startup.
To enable pop-ups you must configure the Windows service "ctgservice" to interact with the desktop.
From the Windows Service Control Manager open ctgservice, in the Log On section, and check the tick box Allow service to interact with desktop.
Pop-ups can not be used with Remote Desktop Services
The default is that pop-ups are not enabled.
Select this check box if you want the CICS Transaction Gateway to call the Windows operating system OEM code page function to get the code page identifier (for example, 850). If the workstation is euro-enabled, code page 850 is mapped to 858 within the client to indicate to the CICS Server that the euro symbol can be used.
If you do not select this check box, the CICS Transaction Gateway uses the Windows operating system ACP function to get the ASCII identifier (for example 1252). Use this to provide appropriate conversions for Latin-1, Japanese, Korean and Simplified Chinese systems. If the workstation is euro enabled, code page 1252 is mapped to code page 5348.
For more information on code pages and data conversion, refer to the Data Conversion appendix in your CICS Clients Administration book.
Select this check box to log server connection and disconnection events.
Enter the name of the log file to be used for problem diagnosis, the default file name is cicscli.log.
When
the logfile parameter is defined without a directory the log file
is created in the:
On Windows: "IBM\CICS Transaction
Gateway" subdirectory, that exists in the Windows common
application data directory.
On UNIX and Linux:
/var/cicscli directory.
Clear this check box to send information messages to a separate log.
By default, information messages are logged to the Error and warning log file; clear the Use the same file for information messages check box to enable the Information log file field.
Enter the name of the file to which information messages will be logged.
By default, information messages are logged to the Error and warning log file; clear the Use the same file for information messages field, and then complete this field, to change the destination.
When the logfile information parameter
is defined without a directory the log file is created in the:
On
Windows: "IBM\CICS Transaction Gateway" subdirectory,
that exists in the Windows common application data
directory.
On UNIX and Linux: /var/cicscli
directory.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C)Copyright IBM Corporation, 1999, 2010. All rights reserved. Legal