OpenMake Meister

Defining z/OS TGTs using ISPF

Through the ISPF panels, Developers can define their Targets to be included in the Project, according to the release level (Search Path). The Setup Build Panel (Option 1 from the main menu) allows for the display of the Projects that have been created, and displays the list of Search Paths that have been defined to be included in each Project.

From the main ISPF Panel, the Setup Build option is available.  Before entering the Setup Build panel, you will be required to define your "High level Qualifier" data set name.  When you create a TGT, a new data set will automatically be allocated using your "High Level Qualifier" and appending ".TGT". The new TGT will be saved as a member in the new TGT data set. Alternatively, you can specify a fully qualified data set name for where your TGT should be saved.

Once you have entered your "High Level Qualifier", you can enter "1" at the Command Line to display the Setup Build panel.

Before creating a Target, you must define your Project and Search Path information. This information will be saved the next time you enter this panel.  To display the list of Project and Search Paths, first display and select a Project by entering a "/" at the "to choose" field as shown below.

COMMAND  ===>

   Build Highlevel:  JDOE143.Payroll

      Project  --->                 / / to choose

      Search Path  --->       _ / to choose                   

This will provide you a list of the Projects.  Select the Project by entering an "S" next to the Project Name.  Once you have selected your Project, enter a "/" at the "to choose" field for the Search Path List and select your Search Path by entering an "S" next to the Search Path name.

Once you have selected your Project and Search Path, you are ready to (A)dd, (C)opy,  (D)elete, (E)dit, (B)uild or Build (All) Targets.  By entering the correct letter, you can add and modify your Targets.  You can also build from this panel by entering a "B" for (B)uild next to the Target you wish to build, or by entering the word "All" next to any of the Targets.  "All" will cause all Targets to be compiled.  If you are defined as a "User" and a Project has not been defined for your application, contact your Administrator.  You can use the "Manage User" screen from the Web Client to see the list of Administrators. 

If you are an Administrator, you must define the Project and Search Paths prior to developers adding Targets to Projects.

Below are the steps for creating a Target from the Target Detail Screen of the ISPF Interface:

1.  To define your High-Level qualifier, use the main ISPF Panel, and enter your High Level qualifier of your working data set. For example, jdoe142.acctpay.  If your LAN ID is different from your mainframe ID, enter your LAN ID. This will allow you to log your build results to the Knowledgebase Server.

2.  To navigate to the Setup Build ISPF Panel enter option 1.  Select your Project and your Search Path.

3.  To name your Target, enter the name of your Target.  For example:

LOAD(hiworld)

4.   A Target Definition File Name must be associated to your Target.  To associate a Target Definition File Name to your Target, enter the name of your Target Definition File.  You can specify a fully qualified name, or enter TGT(<module name).  For example: 

TGT(acctpay1)

5.  To indicate that your Target is for the z/OS platform, choose the z/OS Operating System.

6.  To indicate what type of a load module is to be created, choose the Build Type.

7.  To use an Intermediate Directory during your compile and link process, enter the name of the Intermediate Directory This name should be a relative path to a data set based on your High Level qualifier.  All of the intermediate files such as .obj will be placed here.  For example, when the High Level qualifier is jdoe143.acctpay and the Intermediate Directory is defined as objs,  the hiworld.o (intermediate file) will be placed in the  johndoe143.acctpay.OBJ data set.   If the Build Type does not use Intermediate Directories, this field will be ignored.  If an Intermediate Directory is not used, then the intermediate files will be placed in the same directory as the Target. In our example where the Target is load(hiworld), the Intermediate Targets would be written to the "jdoe143.acctpay.LOAD" data set.

8.  To use additional Compile and Link Flags, select Edit Flag Details option.

9.  To define the dependency information to your Target, add your dependencies information.  The dependencies should be the high level source code that is used to create your program, such as: COBOL(hiworld)  and not COPYBOOK(hiworld).  The header files and copybooks will be added as dependencies by OOMLOM's scanning functionality.  OOMLOM has scanners for the following programming languages: C, C++, COBOL, PROC, PROCOBOL, Assembler, and PLI .  Be sure to hit enter after each dependency in order to save the dependency information.