PRODWWW parameter group

Specifies the national language table set that Data Virtualization uses when performing ASCII to EBCDIC and EBCDIC to ASCII conversions. This is the default conversion to be used by Web transaction processing for single-byte character sets and can be overridden selectively, as needed.

Specifies the default character decoding scheme to be used by Data Virtualization when handling in-bound ASCII to EBCDIC conversions.

Use ISO-8859-1 for most European languages. This setting specifies a single-byte character set (SBCS) conversion algorithm.

Use ISO-8859-9 for the Turkish (TUR) language. This setting specifies a single-byte character set (SBCS) conversion algorithm, but should only be used when ASCIIEBCDICMAPPING is set to TUR.

Use SHIFT-JIS (x-jis) for Japanese double-byte character set (DBCS) handling. This setting should normally be preferred over ISO-2022-JP because most browsers appear to process SHIFT-JIS more automatically and robustly than for ISO-2022-JP. Use this setting with ASCIIEBCDICMAPPING set to either JPX, JPL, or JPE.

Use ISO-2022-JP for Japanese double-byte character set (DBCS) handling. Use this setting with ASCIIEBCDICMAPPING set to either JPX, JPL, or JPE.

Use UTF-8 to nominate UTF-8 encoded Unicode output in conjunction with any ASCIIEBCDICMAPPING setting.

Specifies the default character encoding scheme to be used by Data Virtualization when handling out-bound EBCDIC to ASCII conversions.

Use ISO-8859-1 for most European languages. This setting specifies a single-byte character set (SBCS) conversion algorithm.

Use ISO-8859-9 for the Turkish (TUR) language. This setting specifies a single-byte character set (SBCS) conversion algorithm, but should only be used when ASCIIEBCDICMAPPING is set to TUR.

Use SHIFT-JIS (x-jis) for Japanese double-byte character set (DBCS) handling. This setting should normally be preferred over ISO-2022-JP because most browsers appear to process SHIFT-JIS more automatically and robustly than for ISO-2022-JP. Use this setting with ASCIIEBCDICMAPPING set to either JPX, JPL, or JPE.

Use ISO-2022-JP for Japanese double-byte character set (DBCS) handling. Use this setting with ASCIIEBCDICMAPPING set to either JPX, JPL, or JPE.

Use UTF-8 to nominate UTF-8 encoded Unicode output in conjunction with any ASCIIEBCDICMAPPING setting.

When set to a non-zero value, WWW transaction threads unconditionally pause before issuing close for each HTTP session. Its use is intended primarily for system engineering purposes, but may be required for some network configurations.

Specifies support for file post data processing. It must be set to YES to enable processing multipart/form-data.

Specifies the maximum size transaction a file post supports. Size is rounded up to the next 4 KB boundary.

Specifies use of dataspaces for post file data. It is used to store large files in a dataspace. The dataspace parameters control the sizes.

Sets the default GLVSTATE.$TRACE value for Web transaction programs. If set to NO, tracing of individual Automated State Management Facility (ASMF) operation is not performed unless request. If set to YES, all ASMF operations are traced.

Can be used to prevent the server from sending HTTP/1.1 version responses. If set to NO, the server generates HTTP/1.0 responses.

Can be used to set the HTTP response processing mode under which each new Web transaction begins operation. We strongly recommend you use the default value for this parameter unless needed to maintain operational compatibility with older versions of the Server.

Specifies whether all the known unicode conversion must be loaded at startup or only the ones defined in IN00. In z/OS 1.7 and higher, even if a conversion is not defined in the conversion image, z/OS loads it dynamically at run time. Because Data Virtualization is trying to load all the known conversions and z/OS loads them that makes the storage used by Unicode services unnecessarily large.

Specifies whether the Server automatically initiates periodic out-bound transmission of HTTP response message buffers to the client. If set to 0, all response data is collected in 32 KB buffers, and is transmitted to the client only when the transaction procedure issues an explicit FLUSH-TO-CLIENT request using SWSSEND(FLUSH), or when the transaction ends. A non-zero MAXCHAINEDBUFFERS value specifies that the number of concurrently-held 32 KB output buffers is monitored at each output event. Whenever the in-use buffer count reaches the MAXCHAINEDBUFFERS value, the server automatically issues an SWSSEND(FLUSH) request. Note that monitoring of the this threshold is only active when the current transaction is operating in NON-PARSED-HEADER (RESPMODE(NONE)) mode. This type of monitoring and intermediate flush-to-client operation is never active when a Web transaction is operating in SERVER-PARSED-HEADER (RESPMODE(SERVER) mode. We recommend that automatic threshold checking not be used, unless needed to maintain operational compatibility with an older release of the Server. Instead, use RESPMODE(NONE) and AUTOFLUSH(nnnn) keywords on an individual /*WWW header.

Exerts a limitation on the total number of 32k, out-bound HTTP response buffers which any single URL transaction may simultaneously hold in storage. As an HTTP response is being generated, data which is being buffered occupies 32 KB out-bound buffers, and is not normally transmitted until the transaction procedure ends. When a non-zero value is set, it limits the total number of 32 KB out-bound response buffers which may be concurrently held by a single Web transaction subtask. If this limit is exceeded, the Server generates a user ABEND X 722 with reason code 500 to cancel the transaction procedure. If this parameter is set to 0, the number of concurrently held output buffers is not monitored.

Sets a global limit on the total number of data bytes which may be output in response to any individual URL request. This limit operates strictly by monitoring the bytes, if any, which have already been transmitted as part of the HTTP response, plus the count of bytes currently buffered awaiting transmission. If this limit is exceeded the Server generates a user ABEND X 722 with REASON CODE 501, to cancel the entire transaction subtask If set to zero, no byte count limitation is imposed.

Controls whether the Server automatically generates an "Expires:" HTTP response header when a dynamically generated response, tailored by the HTML Extension Facility (HTX), has been buffered for output.

If this parameter is set to NO, the Server generates an "Expires:" response header (containing the current date and time) automatically, provided that no other "Expires:" response header was buffered for output while HTX file tailoring was underway (for example, by using the RESPONSE.ADDHEADER statement).

If his parameter is set to YES, the Server does not automatically generate "Expires:" HTTP response headers after HTX tailoring. Note that NO, the server’s default, may create problems when using a Web browser’s BACK key in conjunction with the POST request method.

Controls the size of the storage segment

obtained above the bar for use output buffers for the z/OS XML Systems Services parser. This size is specified in megabytes.

Controls the size of the storage segment obtained above the bar for use by the z/OS XML System Services parser. This size is specified in megabytes.

Specifies the name of the product as returned in an HTTP header field. To be suitable for this use, it should be a single token, which can contain dashes (-), but not embedded blanks or other special characters (see RFC2616). The string may contain a single slash (/) preceding a version number token, if you wish to include versioning information. However, if more than one slash is present, only the last is preserved. The server converts all invalid characters to dashes when this parameter is set. The server uses this value to form the "Server:" HTTP response header.

Controls whether or HTX parsing allows for short nested delimiters of the form <.>.

Specifies the prefix string used to recognize HTTP requests for access to the built-in, Data Virtualization Web Interface (SWI). The SWI implements most of the administrative and diagnostic facilities that are available to TSO/E users via the Server’s ISPF-based dialogs. The interface also provides access, via HTTP, to the Server, allowing developer SDKs and IDEs to communicate with the server.

The SWIURLNAME prefix string may be from 1 to 64 bytes in length. The characters you select for this prefix string should contain only byte values commonly used to form internet URLs. The string may contain letters, digits, underbar ("_") characters. The slash ("/") character must be the first character of the string, but must not be used as the final character of the string. The string must be at least 2 characters in length (for example, a single "/" is not valid).

If this parameter is set to one or more blanks, the SWI is not activated. HTTP-based access to the administrative and control facilities of the built-in SWI application is rejected. Specify a single blank during start-up for this parameter to appear as the final character of the string and requires that slash be specified for the first character of the value.

Finally, if you activate the SWI interface, supply the Server’s domain name, at start-up, via the OEHOSTDOMAIN parameter. When the OEHOSTDOMAIN parameter is set to its default value (a dot-notation format IP address) certain Web browsers may intermittently fail to return HTTP cookie information, which is required for proper operation of the SWI Facility.

To access the Data Virtualization Web Interface (SWI), you must direct HTTP requests to the domain:port being used by the Data Virtualization Server, and request the SWI URL. For example, if SWIURLNAME is set to /SWICNTL, the correct location is: http://domain:port/SWICNTL.

Is the global default value for each WWW rule definition’s SENDTRACE keyword. If set to YES, SENDTRACE(YES) is the assumed default for all WWW rules.

The global default value for each WWW rule definition’s PARSETRACE keyword. If set to YES, PARSETRACE(YES) is the assumed default for all WWW rules.