Rocket® Visual COBOL® (formerly a product of Micro Focus or formerly a product of Open Text) documentation, created before Rocket Software acquired certain products from OpenText, may include outdated references to "Micro Focus" or "OpenText", both of which are trademarks of OpenText or its affiliates. Rocket Software is not affiliated with Micro Focus or OpenText and has since rebranded these products as Rocket® products. You may also encounter outdated links in this documentation. If you do, please contact Rocket Support (support@rocketsoftware.com) for assistance.
To Add a Package to an Enterprise Server Instance
Restriction: This topic applies only when the Enterprise Server feature is enabled.
- On the Enterprise Server Administration screen, click Edit to the left of the server to which you want to add the package.
- Click the Packages tab and then click Add.
- Specify a name for the package in Name.
- Choose a status from the list in Status.
- If the entry point that exposes this service is in a library that has a different name than the package itself, specify the name of the library in Module Package. Include the extension; library files have the extension .lbr or .dll
- Specify a full pathname for the interface definition table (IDT) in IDT.
- Check IDT Remains Resident if you want the IDT to be loaded into the repository while the service is running. This can help performance if the service is frequently used and there are no constraints on shared memory.
- Specify a full pathname for the executable file in Package Path. If you have set the COBPATH environment variable at enterprise server level in Configuration Information in the Add Server or Edit Server page, you must specify $COBPATH here, to add the value set at enterprise level to the search path for this package.
- Ignore Configuration Information; this field is not used.
- Specify a text description of the package in Description (optional).
- Click Add.
Note: For each service execution, COBPATH is changed dynamically based on the path of the
associated package. Idle SEPs inherit their COBPATH setting from the environment or
from the configuration of the enterprise server. There are various tools that enable
you to verify this depending on the OS.
The execution of a service overrides COBPATH for the duration of that service after which the value of COBPATH is restored.
The value of COBPATH is not displayed on the Environment Space page within ESMAC (to display the page, click ES Monitor & Control in the details of the running server and then click Env.Vars.). This is because ESMAC is a service and is subject to these same rules but has no configurable package.