Browse Prior Art Database

Designation of Invocation Parameters During Batch Registration

IP.com Disclosure Number: IPCOM000120356D
Original Publication Date: 1991-Apr-01
Included in the Prior Art Database: 2005-Apr-02
Document File: 1 page(s) / 42K

Publishing Venue

IBM

Related People

Bell, LK: AUTHOR [+4]

Abstract

This article describes a method for an OS/2* Office to provide invocation parameters for an appication when it is registered through the OS/2 Office batch registration program.

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

Designation of Invocation Parameters During Batch Registration

      This article describes a method for an OS/2* Office to
provide invocation parameters for an appication when it is registered
through the OS/2 Office batch registration program.

      Because invocation parameters are not typically understood by
the average user, online OS/2 Office registration of applications
requiring invocation parameters is conducive to user error.  This
problem is magnified whenever multiple users require registration of
such an application on numerous workstations.

      File-based applications can be invoked with several parameters
supported by OS/2 Office, or with any of its own parameters. OS/2
Office will provide a class keyword, HANDLERPARMS, that can be used
to identify which static and substitution parameters the application
being registered can be invoked with. The parameters are stored with
the registered class where they can quickly be retrieved by the OS/2
Office platform when the application is invoked.

      Each substitution parameter is provided with a set of double
colons.  Each parameter is separated by a space. Each parameter whose
value can contain a space should have double quotes around the double
colons. Non-substitution parameters are positioned where the
application expects them.  For example, HANDLERPARMS="::fn::"
"::cn::" /o=d:2; indicates that a file name, class name, and the
static parameter "/o=d:2" will be provided to the application...