Tailoring the CMS Pipelines Runtime Library

The version of CMS Pipelines included in the Runtime Library distribution can be tailored in several ways. Three "styles" are provided:

Each style defines its own defaults for a number of "configuration variables", such as the format of information produced when a pipeline stalls.

The user can define a default style and can also set the individual configuration variables. This pipeline sets the style to FPL:

'PIPE literal STYLE FPL | configure | console'
This pipeline overrides the default style to set the "stallaction" to "Jeremy":
'PIPE literal STALLACTION JEREMY | configure | console'
This command sets the style to "DMS" (the VM/ESA style), with one override that specifies that no external message repository is to be used:
'PIPE literal REPOSITORY - | literal STYLE DMS | configure | console'
(In such a case, the English-language message texts built into the runtime module are used. If you require messages in other languages, see the discussion of NLS considerations.)

The installation can change the default style or individual configuration variables by including in the CMS system profile (SYSPROF EXEC) a pipeline similar to those shown above.

Although modifying the PIPELINE MODULE from the Runtime Library is not recommended, an installation can choose to set the style by modifying the MODULE rather than by overriding the style via the SYSPROF EXEC. The default style is determined by a byte immediately following the copyright notice; a value of x'01' specifies the DMS style; a value of x'02', the PIP style; a value of x'03', the FPL style. Thus, this pipeline will change the style from PIP to FPL:

'PIPE',
   '< PIPELINE MODULE A |',
   'change x60F2F0F8F302 x60F2F0F8F303 |',             /* Style FPL. */
   '> PIPELINE MODULE A'

Melinda Varian / Office of Computing and Information Technology / Princeton University / melinda.varian@me.com
November 10, 1997