Browse Prior Art Database

Dynamic Parameter Setting for CICS* Web Interface

IP.com Disclosure Number: IPCOM000123667D
Original Publication Date: 1999-Mar-01
Included in the Prior Art Database: 2005-Apr-05
Document File: 2 page(s) / 55K

Publishing Venue

IBM

Related People

Harris, R: AUTHOR

Abstract

The CICS TS for OS/390 Release 2 has a component (Ref 1) that provides access to CICS through a Web Browser. The first thing that happens to a flow from the browser is that it is pumped into a SINGLE defined program, the analyzer, to set various parameters (such as the Server Program, the Transaction to run, Code Page Conversion, Security etc).

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 57% of the total text.

Dynamic Parameter Setting for CICS* Web Interface

   The CICS TS for OS/390 Release 2 has a component (Ref 1)
that provides access to CICS through a Web Browser.  The first thing
that happens to a flow from the browser is that it is pumped into a
SINGLE defined program, the analyzer, to set various parameters (such
as the Server Program, the Transaction to run, Code Page Conversion,
Security etc).

   There can only be one analyzer present, and it has to be
hard coded to set the various processing parameters.  Thus, it is a
complex and difficult task for a user to look at all the possible
flows from the browser, separate them, and set the processing
parameters accordingly.

   The solution described here uses &key = value settings
within the URL in a defined place according to the Web Interface
standards to permit the setting of the analyser processing
parameters dynamically in the URL instead of statically (and with
great difficulty) in the analyser.

   Thus the standard URL for CICS usage is something like:
  HTTP://dns:ip/convert/transaction/serverprogram/ parms (1)
  (see Ref 1) - parms are variable input to the serverprogram.

   This can collapse to:
  HTTP://dns:ip/&/parms  (2)  (in a case where all defaults
  would apply)
  or to:
  HTTP://dns:ip/&KS=A/parms  (3)  (to the case where a defined
  set of options apply).
  as opposed to:
  HTTP://dns:ip/&KS=B/parms  (4) (for a different set of
  processing parms).

   Examples (3) and (4) show th...