Unit Testing the Batch Application

The first thing you need to do is check that the Bankdemo application is executing correctly.

To execute the JCL, you need to run the application in an instance of the Micro Focus Enterprise Server (sometimes abbreviated to Enterprise Server). This demonstration includes a pre-configured enterprise server instance called Bankdemo which you need to import in Enterprise Server and start before you execute the Bankdemo application.

Important: You need Enterprise Developer or Enterprise Developer for z Systems to execute the application as running applications is not supported in Enterprise Developer Connect.

Importing the Bankdemo server

To import the definition of the Bankdemo logical server (LSER):

  1. Click the Server Explorer tab in the upper left pane of the IDE.

    If the tab is not visible, click Window > Show View > Other. Select Micro Focus > Server Explorer and then click OK.

  2. In Server Explorer, right-click Local [localhost:86] and click Open Administration Page.
    Note: On versions of Windows Vista or later, if you experience issues connecting to localhost, connect to 127.0.0.1 instead.
  3. Click Import in the left upper corner of Enterprise Server Administration.
  4. On the Import server information page and under Recent directories click the directory for the BANKDEMO server.

    IMPORTBANKDEMOSERVERIMG-low.png

    This adds the path to the Selected source directory containing server data to restore field.

  5. Click Next three times, and then click OK to import the BANKDEMO server.
  6. The system returns to the main Enterprise Server Administration page.

    You can see the Bankdemo server appears in the list of servers. You need to start it before you can execute the online Bankdemo application.

    GUID-042A356F-11CB-414D-A52D-086F4AAFA0B1-low.png

Associate the Bankdemo Enterprise Server with your project

Ensure your application is associated with the BankDemo server:

  1. In Server Explorer, right-click Local, and click Refresh to show the BankDemo server.
  2. Right-click the BANKDEMO server, point to Associate with project, then select BankDemo.

    GUID-34BA259A-B14C-438D-B49F-689F58D90A92-low.png

Configure the IDE settings for Enterprise Server

Configure the IDE to start the associated BankDemo server automatically as follows:

  1. Click Window > Preferences.
  2. Expand Micro Focus, and click Enterprise Server.
  3. Set the following options on this page to Always in order to enable the IDE to start or stop the associated server, and to enable dynamic debugging, for when it is not enabled in the server:
    • Automatically start the associated server - this ensures the IDE will start the server if it is not running when you execute the application.
    • Automatically stop servers started by Eclipse when closing Eclipse - this enables the IDE to stop servers when you close Eclipse.
    • Automatically enable dynamic debugging - this ensures the IDE will check whether the server has dynamic debugging enabled and, if it is not, will enable it when you start debugging.
  4. Click OK.

Starting the Bankdemo Enterprise Server and Showing the Server Log

These are the steps to start the server manually, and are included for completeness. You do not have to start the server manually, as you have configured the IDE to start the server automatically.

  1. In Server Explorer, right-click BANKDEMO, then click Start.
    Note: You might receive an Enterprise Server Sign On dialog prompting you to provide connection details for the BANKDEMO server. This is a standard security dialog. Click OK without specifying any sign on details. Also, you may skip enabling password recovery.

    You may receive a Windows Security Alert blocking the MF Communications process. Click Allow access.

    You can check the Console view to ensure that the BANKDEMO server has started successfully.

  2. Right-click the BANKDEMO server in Server Explorer, and click Show Console Log.

    Check the Console view as it now shows the messages from the server log:

    GUID-2D863AC8-3E57-4F6E-AB27-29CCCD8A118F-low.png

  3. Right-click the BANKDEMO server again, and then click Refresh to see that the server has started.

    After several seconds, the server status on the Enterprise Server Administration page also changes to Started. You are now ready to execute the JCL.

Executing JCL

The JCL provided in your demo causes the COBOL application to read a file, sort the data and produce a report. The .jcl file, ZBNKSTMT.jcl, is in the Sources > jcl folder of the project. To submit this job:

  1. In the Application Explorer view, expand the jcl folder.
  2. Right-click the .jcl file and select Submit JCL to associated Server.
    Note: If you have not started the Bankdemo server yet, since you configured the IDE to start the server automatically, you receive a notification that the server will be started. Click Yes to confirm this.

    Check the Console view in the Eclipse IDE to see that this job has been submitted.

    JCL submission

  3. Click one of the links to show the spool details for the job.

You now need to check the results of submitting the job.

Viewing the Catalog and the Spool

You can open the catalog and the spool directly from within the IDE.

To view the catalog:

  1. In Server Explorer, right-click the BANKDEMO server and click Show Catalog.

    This opens the catalog.

  2. Click List to view all file entries in the catalog.

    GUID-ECA58CEC-2E61-413B-9BA9-836B14BFDA8B-low.png

  3. Click a file name (for example, EBC.BNKACC) to preview the contents of the file.

To view the spool:

  1. In Server Explorer, right-click the BANKDEMO server, and click Show Spool.

    GUID-F992E754-1014-4CED-8F95-1205B35F8626-low.png

    This shows the spool with the Complete button selected to see a list of all jobs in the completed queue. Your job is the last in the list.

  2. Check the check box next to your job, and click Display.

    This opens a page with a variety of information for the job progress, showing return condition code (COND) of 0000:

    GUID-EA0E974D-5450-4B42-88E4-63C9AFBBA947-low.png

    In the details, there are:

    • Two SYSOUT results (one for the Extract and one for the SORT). Click these to see the details:

      GUID-660498E4-4A3E-48CA-87D8-DE90ABE8E94D-low.png

      Again, if you cannot see your SYSOUT files, click Printed on the Spool page.

    • To return to the previous page, press the backspace key.
    • The PRINTOUT which is the final printed results created by your job. Click PRINTOUT to see the results:

      GUID-32666439-E1CD-4277-95E8-3A9FFE302A61-low.png

You can now start to look at how to run the online application.