|
Previous Topic
Table Of Contents
Parent Topic
| |
June 30, 1996
- Changes to the way in which the run-time Effective Userid is determined for Web
transactions.
Prior to this change, the run-time Effective Userid for Web
transactions was always controlled by the RUNAUTH keyword. When RUNAUTH was
omitted, the default was equivalent to specification of RUNAUTH(NONE); even in cases where
the Client Userid had been solicited from the end user. Many customers felt this to be
counter-intuitive, and we agreed!
These changes cause the Shadow OS/390 Web Server to favor selection of the Client
Userid as the run-time Effective Userid whenever the Client Userid is available. See
Conditions Under Which a Client Userid is Required and How Effective Userid is Determined
for an explanation of how this facility now operates.
- National Language selection of ASCII/EBCDIC translation tables
A new
start-up option, ASCII_EBCDIC_MAPPING, now allows you to select the character
mappings used when the server performs ASCII/EBCDIC translation operations.
- Fixes to query variable parsing routines.
Formerly, if an inbound query
variable contained a plus sign, the server would incorrectly convert the plus sign to a
blank. For instance, if the value "+003" was sent, inbound in a query variable,
the transmitted value would arrive in the server as "%2B003", and the server
would convert this to " 003".
The server would convert the encoded plus sign, "%2B" to an ASCII plus sign, before
translating plus signs to blanks. This fix reverses the processing order.
Top
|