Creating an integration server-specific environment file

An integration server-specific environment file can be used instead of the default integration node environment file when you restart the integration server.

Before you begin

Complete the steps in Customizing the integration node JCL

About this task

This task forms an optional step of the larger task of creating an integration node on z/OS.

By default, an integration node has a single environment file (ENVFILE), which is created from BIPBPROF by submitting BIPGEN. The main integration node address space and any integration server address spaces use this environment file.

You might find it necessary to have an integration server-specific environment file. In this situation, when the integration server is restarted, the integration server address space uses the specific environment file and not the default integration node environment file.

Procedure

  1. Review the BIPBPROF member.
    If you define parameters that are required by the integration node and all integration server address spaces, you can configure BIPBPROF to use these parameters.
  2. Copy BIPEPROF and rename the copy of the file to be the same as the integration server label in the component data set, by using the following rule.

    The name must equal the last eight characters of the integration server label. Any characters that are not valid for a STEPNAME are replaced with the @ character.

    Furthermore, if the first character of a STEPNAME is not an alphabetic character, that character is replaced with an A. (For more information about characters that you can use, see Administration in z/OS.)

    For example, an integration server address space with the label MyExecutionGroup, has an integration server-specific profile called IONGROUP.

  3. Customize the renamed BIPEPROF file to include any environment variable settings that are specific to the integration server.
  4. Update BIPGEN by adding a step at the end for the new integration server-specific profile; for example: 
    //BIPEG01 EXEC PROC=BIPEGEN,EG=IONGROUP
  5. Submit member BIPGEN to re-create the default integration node environment file, and to create the new integration server-specific environment file.
    Review the job output and make sure that the environment file in the output contains the parameters that you expect.

    If you change BIPBPROF, or the renamed BIPEPROF file, or system-wide parameters, you must submit BIPGEN again to pick up the changes.

What to do next

If you require multiple integration server-specific files, complete the following steps:
  1. Create an integration server-specific profile for each file, following the naming rules that are specified in step 2.
  2. Add extra steps to the end of BIPGEN, giving each step a different name, and specifying the correct eight-character integration server label.
  3. Resubmit BIPGEN to create all the environment files.