Previous Topic Table Of Contents Parent Topic Next Topic |  | # New for This Release ## January 17, 1997 ### Support of TSO/E Using the Out-board TSO Server Facility Because the Shadow OS/390 Web Server does not operate as a Terminal Monitor Program (TMP), it was formerly difficult or impossible to directly invoke TSO command procedures as part of a Web transaction. This version of Shadow OS/390 Web Server supports the use of out-board TSO server address spaces. If configured for TSO Server support, the Shadow OS/390 Web Server will now start and monitor up to 30, separate TSO address spaces. Web transactions can now be created which schedule a TSO command procedure into the first available out-board TSO server. The output from TSO command procedures is then intercepted, optionally re-formatted, and output to create the Web transaction response. Inclusion of this facility allows customers to create Web transactions which incorporate the facilities of ISPF/PDF, perform many types of catalog and dataset operations, and submit and monitor the progress of batch jobs. For information about this important new enhancement, refer to Using TSO/E for Web Transaction Processing. ### Easier Output Interface from Shadow/REXX Web transaction procedures written using Shadow/REXX may now use the `ADDRESS SWSSEND` host command environment to output information to a Web client. This new interface allows you to directly write string or binary data for outbound transmission directly to the host command environment; thus, bypassing more complex built-in function calls. The addition of this interface will simplify coding of Shadow/REXX procedures and make them easier to create, debug, or update. See Shadow/REXX Interface for Web Data Output and The SWSSEND Host Command Environment for information on using this new facility. ### Overrides for Global Shadow/REXX Execution Limits Shadow/REXX procedures, running as Web transaction processors, operate with pre-allocated areas for the REXX external data queue and working storage. The number of pre-allocated queue entries, and the amount of working storage were formerly set, for all transactions by system-wide start-up parameters. Because the size of these pre-allocated areas was set by a system-wide parameter, many sites found it necessary to set extraordinarily large values for in order to allow a few, high-overhead transactions to be run. This version of the Server allows you to override these system-wide specifications on a rule-by-rule basis. Now you may specify overrides for the Shadow/REXX working storage size, or the number of entries to be allocated within the external data queue. The system-wide parameter which specifies the default size of Shadow/REXX working storage is `SEFSIZE`. The default specification used by the server is 256K, unless changed in the start-up procedure. Using the WORKSIZE( ) keyword, you may now override this specification for an individual WWW rule. The system-wide parameter which specifies the default entry count for the Shadow/REXX external data queue is `SEFMAXQUEUEE`. Using the QUEUESIZE( ) keyword, you may now override this specification for an individual WWW rule. ### Variable Web Transaction Dispatching Priority The new DPTRY( ) keyword allows you to alter the MVS dispatching priority of a Web transaction subtask, relative to other subtasks within the system, on a rule-by-rule bases. Using the DPRTY keyword you may now fine-tune the performance characteristics of an individual Web transaction, or group of Web transactions. This allows you to configure high-resource-utilization tasks so that they do not hog system resources and impede the operation of other in-flight transaction activity. ### URL Name Space Extended to 128 Characters The Server will now process URL values up to 128 characters in length. Formerly, the Server limited URL values to 50 bytes. See Supported URL Values and Event Procedure Criterion for information about this change. ## Prior Release Notes October 17, 1996 September 9, 1996 June 30, 1996 Top