Browse Prior Art Database

Handling Posix Control Scripts in Office Systems/2 Environment

IP.com Disclosure Number: IPCOM000116652D
Original Publication Date: 1995-Oct-01
Included in the Prior Art Database: 2005-Mar-31
Document File: 4 page(s) / 110K

Publishing Venue

IBM

Related People

Ibanez, JG: AUTHOR [+3]

Abstract

In attempting to use the Portable Operating System Interface (POSIX) standard for installation in an OS/2* environment it was discovered that while the control scripts (a.k.a. user exits) are very useful, there may be problems if a control script is called multiple times during a single installation of multiple related products. Also some control scripts may be required during installation and others may not be required. Controlling the status and state of control script execution turned out to be very important.

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

Handling Posix Control Scripts in Office Systems/2 Environment

      In attempting to use the Portable Operating System Interface
(POSIX) standard for installation in an OS/2* environment it was
discovered that while the control scripts (a.k.a. user exits) are
very useful, there may be problems if a control script is called
multiple times during a single installation of multiple related
products.  Also some control scripts may be required during
installation and others may not be required.  Controlling the status
and state of control script execution turned out to be very
important.

      POSIX P1387.2/D13 refers to an on-going standards project that
is currently in a working draft.  Refer to "STANDARDS PROJECT' Draft
Standard for Information Technology - Portable Operating System
Interface (POSIX) System Administration - Part 2: Software
Administration, P1387.2/D13 April 1994.

      To solve the above problem it is necessary to be able to query
and change the status of control scripts.  This can be done by using
the Application Programming Interfaces (APIs) CIChangeScriptStatus
and CIQueryScriptStatus.
  CIChangeScriptStatus - Changes the execution status of POSIX
  control scripts within the INDEX/INFO files of POSIX.
  APIRET CIChangeScriptStatus(TAG *pTag,
                 enum CS_TYPE eScriptType,
                 SHORT *sNewResult,
                 SHORT *sRequired
                );

 PARAMETERS
  PTAG       Pointer to a tag of the product, subproduct or fileset
              which contains the control script you are interested
in.
              The first matching kind of control script that is found
for
              the tag given will be used by the API.  That is, if the
              product or subproduct does not explicitly contain that
              type of control script, but one or more of it's
contained
              filesets do, the first matching script found in the
              contained fileset list will be used.
  ESCRIPTYPE   The type of control script you checkinstall, request,
                pre install, postinstall, configure, verify,
unconfigure,
                preremove, and postremove.
  SNEWRESULT   The new result that you want to set for the
                script.  Valid values are:
               -1                  Do not change the result status.
               NO_RESULT           Indicate that the scripts has
                                    not been run.
               SUCCESS             Indicate that the script has
                                    not been run successfully.
               FAILURE    ...