Browse Prior Art Database

Changing Configuration Files Under Program Control

IP.com Disclosure Number: IPCOM000102253D
Original Publication Date: 1990-Nov-01
Included in the Prior Art Database: 2005-Mar-17
Document File: 1 page(s) / 25K

Publishing Venue

IBM

Related People

Schaefer, GH: AUTHOR [+2]

Abstract

Previous Batch Configurations allowed a user to create a configuration file from a prototype configuration file, but would not allow the user to change an existing configuration file. In an environment where users are added and removed from the network, it is required to change the configuration of each workstation to support peer-to-peer communications.

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

Changing Configuration Files Under Program Control

       Previous Batch Configurations allowed a user to create a
configuration file from a prototype configuration file, but would not
allow the user to change an existing configuration file.  In an
environment where users are added and removed from the network, it is
required to change the configuration of each workstation to support
peer-to-peer communications.

      This disclosure provides a method for changing the end-user
workstation configuration file.

      When selecting the configuration filename to be changed,
support an optional parameter which identifies that the configuration
file already exists, and it should be modified, but not created new.
In this environment, the prototype should be ignored since it is only
used for creating new configuration files.

      Example of change workstation configuration file function:
   FNM P1 1  /* Change configuration file P1 and */
   /* ignore the prototype (indicated by 1) */.