The CNF Statement

The CNF statement specifies configuration information. An IPL file contains only one CNF statement, which must occupy the first line of the file.

Overview of the CNF statement

The CNF statement has the following format:

CNF: numparts,numdevs,numtasks,numofiles,progerr,traceflag,ofilesflag,datefrmt,dfrmtsep, strtJulday,endJulday
CNF: begins the CNF statement.
numparts: is the number of partitions. The only valid value is 1. You must specify the value for this parameter.
numdevs: is the number of device definition lines that follow. You must specify a value for this parameter. For more information on device definition lines, please refer to the subsection on DEV Statement.
numtasks: is the number of tasks in this partition. The only valid value is 1. You must specify the value for this parameter.
numofiles: is the number of available open file table entries. Valid values cannot exceed two less than the maximum number of files per task, which is specified by the operating system. You must specify a value for this parameter.

Each open file and each program in memory uses one file table entry. Thoroughbred Basic public programs in memory do not use file table entries.

progerr: is the program to run to manage automatic escape and error processing. A valid value is the name of such a program. The default is no name, which means no automatic processing.

You can specify the CUTERR program, which is provided with Thoroughbred Basic. This program prevents escapes or errors from placing the user in Thoroughbred Basic Console Mode.

If the program name is preceded by a . (period) Thoroughbred Basic will CALL the program rather than RUN the program. For more information on the CALL and RUN directives please refer to the appropriate Thoroughbred Basic Language Reference.

For more information on escape and error processing, please refer to the chapter on Program Control in the Thoroughbred Basic Developer Guide. For more information on Thoroughbred Basic Console Mode, please refer to the Thoroughbred Basic Developer Guide.

traceflag: is the trace/console mode flag for automatic escape and error processing. This parameter is ignored unless an automatic escape and error processing routine is specified for the progerr parameter. Valid values are:

0 allows for “T” and “C” responses. This is the default.

1 disallows “T” and “C” responses.

ofilesflag: Enables or disables the open files caching and file sharing features. Valid values are:

0 open files caching is disabled; file sharing is enabled. This is the default.

1 open files caching is disabled; file sharing is enabled.

2 open files caching is enabled; file sharing is enabled.

3 open files caching is enabled; file sharing is disabled.

4 open files caching is disabled; file sharing is disabled.

When enabled, the open files caching feature allows files to remain opened by the operating system even though a Thoroughbred Basic program has issued a CLOSE directive. This can save time spent closing and opening files in complex file systems but increases the load on operating system resources.

The file-sharing feature is only for Microsoft Windows operating systems. When enabled, extra steps are taken to ensure that files can be shared with other systems using mapped drives. This is accomplished by flushing the local data cache after each update. Disabling this feature when mapped drives are not used will improve performance.

This setting can be overridden on individual DEV statements. The settings are displayed using the DUMP IPLDEVS “OPTIONS=Y” directive.

datefrmt: is the date format. Valid values are:

M for MMDDYY. This is the default.

D for DDMMYY.

Y for YYMMDD.

MM is short for month, DD is short for day, and YY is short for year.

dfrmtsep: is the date format separator, which is used to separate the MM, DD, and YY components of the datefrmt clause. Valid values are any character except for the null character. The / (slash) character is the default.
strtJulday: is the starting Julian day, which you can use to set daylight savings time. Thoroughbred Basic recognizes the daylight savings time parameters specified in the TZ environment variable. If you prefer, you can set daylight savings time with the strtJulday and endJulday parameters. This parameter has the following format:

Julianday[:hour]

Julianday: is an integer that specifies the Julian day.
hour: is an integer that specifies the hour of the day. The default is 2.
endJulday: is the ending Julian day, which you can use to set daylight savings time. This parameter has the following format:

Julianday[:hour]

Julianday: is an integer that specifies the Julian day.
hour: is an integer that specifies the hour of the day. The default is 2.

Note: Allows daylight savings time arguments on CNF records to be reversed for countries south of the Equator, where the end date is before the start date.

Examples of the CNF statement

CNF 1,11,1,60,CUTERR,0,0,D,.

This example specifies DDMMYY as the date format and . (period) as the character that separates date components. For example, January 30, 1995 will be formatted as 30.01.95.

CNF 1,11,1,60,CUTERR,0,0,,,90:3,300

This example sets the start of daylight savings time to the 90th Julian day at 3:00 A.M. and the end of daylight savings time to the 300th Julian day at 2:00 A.M.

From the Customization and Tuning Guide: System Files, version 8.9.1. Open this page in the PDF