Previous Topic
Table Of Contents
Parent Topic
Next Topic

October '98 to October '99 Release Notes

Features Added After July 1999 Release 4.1

The following has been added after the July 1999 release:

• Server Code Errors. A list of Server Error Codes describing the various error conditions which can be encountered during the processing of a URL was added.

• Supported SMF Fields. Displays a list of supported SMF fields to enable Shadow OS/390 Web Server’s SMF recording. See the appendix for more information.

• @TYPE. The new keyword can be contained between the SQLBINDCOL BEGIN and SQLBINDCOL END statements. These keywords are substituted with the proper values for each ENABLED field in the Data Map. See Data Mapping, Generate RPC for more information.

• Fetch and Release Restrictions for custom written PL/I programs. Do not use FETCH or RELEASE statements if SSL is used for encryption of session data. This is due to the language environment restrictions for VM and MVS.

• WWW.PASSWORD and WWW.EFFECTIVEUSERID. These two variables were added.

• "GLVSTATE". The server now intercepts and specially handles all variables which have names beginning with the characters, "GLVSTATE.". Variables which begin with this stem name are handled by the Automatic State Management Facility and cannot be used for other purposes.

• Data Mapping. The Edit Map panel selection is no longer available. Temporary maps are no longer necessary. The Data Mapping section has been updated with miscellaneous other changes.

• Shadow ADABAS Server. Documentation was added on the Shadow ADABAS Server.

• Secure Socket Layer. The documentation was updated to to include such items as the OEM key and configuring TCP/IP ports, as well as adding more information on the SSL utilities ISPF panels.

• AutoHTML. The documentation was updated with more screen shots and step-by-step instructions.

• Trace Browse Archival Facility. Additional screen shots and instructions were added.

API and High Level Language Changes

• SWSSET and the High Level Language equivalent.  Several run-time environmental options were added, including language codes.

• SWSCONCT and the High Level Language equivalent. This concatenates multiple ddnames of previously allocated datasets.

• SWSDECON and the High Level Language equivalent. This de-concatenate a single ddname that was concatenated using SWSCONCT.

• Validating a Userid and Password. More information was added.

• SWSECURE, The Operation Argument. The PI function is no longer supported. References to it were removed.

• SWS_ERROR. This is a new return value on high level languages when a parameter validation or run-time error was encountered. Error information is available using the SWSERROR function.

• SWS_ENVIRONMENT_ERROR. This return value on high level languages occurs when the request cannot be processed because of a run-time environmental error, such as, invoking the API service outside of a Web transaction procedure or from outside the server's address space.  Use the server's wrap-around trace to obtain diagnostic information.