You must provide the following specifications to the Manage Packages and Plans tool to enable it to generate a valid BIND PACKAGE script command:
- Collection name
- You can specify any name you choose, and add one or more packages to that collection. HCOSS creates the collection the first time you execute a package that you specify to be stored in the collection.
- Library name
- The name of a library containing extracted DBRMs.
- DBRM libraries are located under
localHCOSSFiles\DBRMDataSets, where
localHCOSSFiles represents the value of the
Local HCOSS Directory HCOSS option.
- When you compile your application using the SQL(DBRMLIB) directive without specifying a DBRM name, HCOSS puts all DBRMs into a default library directory named DBRMLIB.
- If, when you compile, you specify a value for the DBRMLIB directive, the library directory name is the same as the value you specify.
- The Manage Packages and Plans tool provides you with a list of the available libraries from which to select.
- Each library contains one DBRM for each source code member.
- Each DBRM contains the extracted EXEC SQL statements from a single source member.
- Member name
- The name of the DBRM from which you want to create the package. This is the program ID of the source code member from which the DBRM was extracted. If there is more than one DBRM in the specified library, you can select from a list of available members.
- Default qualifier
- The name of a schema to use as the default qualifier for this package. (Optional)
- Action
- The action you want to take with regard to this package and the collection. If this package doesn't already exist in the collection, you can click
Add to add it. If it does exist in the collection, you can click
Replace to replace the current package version with an updated DBRM member, or you can replace a specific version by specifying the version identifier for the package that you want to replace and clicking
Replace Version. HCOSS generates a new version for the package when you generate the DBRM.
