Or, use this sample to see how to allocate a new event
procedure set offline, under TSO. (This event becomes immediately accessible from the ISPF
panel without restarting the server subsystem.)
When the transaction is first accessed, no query variables are sent inbound with the
request. Instead of processing the SQL statement, the EXECSQL processor transmits the
input form. The end user completes the form and presses the submit button. The form runs
the same /*EXECSQL rule using the same URL value, except this time, query variables are
sent inbound.
Because query variables are sent with the request, the EXECSQL processor executes the
SQL statement. The result set data is automatically formatted into an HTML table and sent
back to the end user.
Example 2
This example transmits the URL "/NEON/SQLEXEC3",
which is processed in exactly the same way as the first one; it uses an input form and
automatic output formatting. However, in this example, the input form solicits the user to
key an entire SQL statement. That statement is the one executed.
Example 3
This example transmits the URL "/NEON/SQLEXEC4",
which performs approximately the same function as the first sample, except it uses the
OUTPUTFORMAT parameter to specify a file in which the DB2 result data is inserted.
Gateway Filter Rule
The distributed rule in WWW.SWSCNTL is an application-dependant example of a
REXX-Language logon Gateway Filter rule that handles HTML form-based MVS logons. Use the
URL /swscntl/menu to access this sample application.
Start-up Parameters for Shared and Cached
When new /*FILE rules are accessed for the first time, a server start-up parameter
allows all previously unseen files to be made globally-shared dynamically. If you do not
want this support, you can explicitly specify which datasets are to be shared or cached.
The start-up parameters, which control file sharing, can be viewed at /SWSCNTL/PARMS.
Cookie Demonstration Application
Click the following button to open the supplied cookie demonstration application in a
separate window.