Set Up the PLIDEMO Enterprise Server Instance

Provides instructions that guide you through the creation and configuration of the PLIDEMO enterprise server instance.

Attention: You might encounter an ESCWA Sign On dialog box as you perform the steps required to create, configure, start, or stop an enterprise server instance from the Server Explorer. If you do, ensure that the Server requires credentials, Use specific server credentials, or Server is secured , and the Store credentials boxes are unchecked, and then click OK. Also, if prompted to disable password recovery, click No.

Start the Server Explorer

The Server Explorer view is visible by default when using the Team Developer perspective, and appears as a tab on the same level as the Application Explorer view. However, if it is not visible:

In Eclipse, click Window > Show View > Other > Micro Focus > Server Explorer, and then click Open.

Start Enterprise Server Common Web Administration (ESCWA)

From the Eclipse Server Explorer, right-click the Local [localhost:10086] node, and then select Open Administration Page from the context menu.
ESCWA starts in your default browser.

Create the PLIDEMO enterprise server instance

In ESCWA, click Native.
In the navigation pane, click Directory Servers > Default.
Click * New.
This opens the New Region dialog box.
In the Name field, type PLIDEMO.
In the Description field, type a meaningful description, such as JCL server for tutorial.
Ensure that 64-Bit Working Mode is checked.
Ensure that MSS Enabled is checked.
Clear the Create TN3270 listener check box.
Click Save.
This adds the PLIDEMO region to the Directory Servers > Default list in the left pane.

Define the PLIJCLDEMO environment variable

In the left pane, select the PLIDEMO region.
The General Properties page is displayed.
In the Configuration Information field, type the following:
```
[ES-Environment]
PLIJCLDEMO=eclipse-workspace-path\PLIJCLdemo
```
Where eclipse-workspace-path is the full path to your Eclipse workspace.
Click Apply.

Enable and configure JES

In the Region Features section of the General Properties page, check JES Enabled.
Click Apply.
This displays the JES menu option.
Click JES.
This displays the JES Configuration page.
In the JES Program Path field, type $PLIJCLDEMO\PLIJCLbuild.bin.
This directory contains the executable .dll files that are run by your JCL jobs.
In the System Catalog field, type $PLIJCLDEMO\CATALOG.DAT.
This is the path and name of the system catalog, which holds the details of data files, their attributes, and locations. If the catalog file does not exist, it is created with the name given when the JCL is submitted.
In the Default Allocated Dataset Location field, type $PLIJCLDEMO.
This is the default directory where new data sets are created.
Click Apply.

Add the INIT1 initiator

Initiator (or batch initiator) is a Service Execution Process (SEP) for running JCL jobs. You can define initiators to start up automatically whenever the enterprise server is started, and you can also create ones that last only for the current session. The following specifies one initiator to start automatically using ESCWA:

On the Jes Configuration page, click * New next to Initiators.
This opens the JES Initiator dialog box.
In the Name field, type INIT1.
In the Class field, type abcdefghijklmnopqrstuvwxyz0123456789.
Optionally, in the Description field, type a description for the initiator.
Click Save.

Enable and configure PL/I support

In ESCWA on the General Properties page for the PLIDEMO region, check PL/I Enabled.
Click Apply.
Click General > PL/I.
This opens the PL/I configuration page.
In the Codewatch Source Path(s) field, type $PLIJCLDEMO.
This is the project directory.
In the Codewatch STB Path(s) field, type $PLIJCLDEMO\PLIJCLbuild.bin.
This is the project output folder.
In the PL/I Configuration Directory field, type $PLIJCLDEMO.
This is the project directory.
Click Apply.