|
DataMuseum.dkPresents historical artifacts from the history of: Rational R1000/400 |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about Rational R1000/400 Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - download
Length: 2267 (0x8db) Types: TextFile Notes: R1k Text-file segment
└─⟦8527c1e9b⟧ Bits:30000544 8mm tape, Rational 1000, Arrival backup of disks in PAM's R1000 └─ ⟦cfc2e13cd⟧ »Space Info Vol 2« └─⟦905d778f2⟧ └─⟦this⟧
procedure Design_Facilities (Default_Activity : String := "!Machine.Release.Current.Activity"; Local_Pdls : String := "!Machine.Initialization.Local.Design_Facility_Configuration"; Site_Pdls : String := "!Machine.Initialization.Site.Design_Facility_Configuration"); pragma Loaded_Main; -- -- This procedure registers all Design Facility customization named in -- either Local_Pdls or Site_Pdls. These files are composed of lines, -- each of which describes a PDL which is to be initialized upon machine -- reboot. -- -- The format of these files accomodates the management of local and -- site-specific adaptations of Rational's standard Design Facility -- products. -- -- The lines may contain 1, 2, 4 or 5 fields, where a "field" is a -- sequence of non-blank characters, delimited by blanks. The field -- format is: -- -- <PROGRAM CONTEXT> <ACTIVITY> <TARGET KEY NAME> <PDL NUMBER> <FILE CONTEXT> -- -- PROGRAM CONTEXT, field 1, denotes a context where a subsystem named -- PDL_Definition is to be found. If the context begins with "!", -- the field is taken literally as an Environment pathname. If not, -- the field is resolved in the context of !Tools.Design.Release. -- -- ACTIVITY, field 2, denotes an activity to be used to find an entry -- for the PDL_Definition subsystem (resolved as described above). -- If this field is not present, it is defaulted to -- !Machine.Release.Current.Activity -- -- TARGET KEY NAME, field 3, is used as the symbolic name of the target key to -- be used for this PDL. -- -- PDL NUMBER, field 4, is used as the PDL "number" as defined by -- !Tools.Design.Pdl.Pdl_Ids -- -- FILE CONTEXT, field 5, is the context in which the three "customization -- files" are to be found. If not present, the context is defaulted -- to the "Units" directory of the load view selected by the -- PDL_Definition subsystem and the activity given in the second -- field. -- -- Note that if the third field is present, the intent must be to -- create a "new" PDL with a different symbolic target key. Thus, -- the fourth field is required to avoid someone changing the target -- key but "overwriting" an existing PDL number. -- --|Prerequisite Teamwork_Interface --|Wait