Setting z/OS build options for a stored procedure

Developer for z/OS® stores build options in property groups. To set build options for a stored procedure, create a property group, specify the build options, and associate the property group with the stored procedure.

Before you begin

For more information about creating property groups and associating them with a resource, such as a stored procedure, see the related topics.

The Developer for z/OS build procedures include two JCL procedures that support the build of stored procedures:

  • ELAXFSP: Registers the stored procedure to Db2® by running the CREATE PROCEDURE statement.
  • ELAXFSQL: Runs SQL statements in batch. These SQL statements add rows to the system tables SYSIBM.SYSROUTINES_SRC and SYSIBM.SYSROUTINES_OPTS.

The systems programmer must configure these JCL procedures to point to the Db2 RUNLIB. For more information about configuring JCL procedures, see ELAXF* remote build procedures in the Host Configuration Guide.

Procedure:

  1. Create a property group for the remote system to which you are connected.
  2. Edit the property group and specify the following categories and properties.
    Category Page Property Value
    JCL Job Card and Data Set JCL Job Card and Data Set JCL job card Specify JCL required at your site for submitting data access jobs. If you do not know which JCL statements to add to this field, ask your systems programmer.
    JCL Job Card and Data Set Data set for generated JCL Specify the name of the data set to contain generated JCL. You can drag a partitioned data set name from the Remote Systems view, z/OS Projects view, or Remote z/OS Search results view and drop it in the field. Click Check Data Set to check that the data set specified in this field exists on the remote system.
    COBOL or PL/I Runtime Environments Db2 Select this check box.
    Routine development Select this check box.
    Subsystem ID Type the name of the Db2 subsystem to which you are connected. If you do not know the subsystem name for your Db2 connection, contact your Db2 administrator. The subsystem name is used to register a stored procedure to Db2 and to update the SYSIBM.SYSROUTINES_SRC and SYSIBM.SYSROUTINES_OPTS system tables.COBOL
    Procedures and Steps Procedures and steps table Enable the compilation procedure (ELAXFCOC for COBOL or ELAXFPL1 for PL/I). To open step options, double-click the step name (COBOL or PLI).
    Step options

    Listing output data set: The name of the listing data set used for the compilation. The listing data set should be a partitioned data set. This data set is used to make up a SYSPRINT card for the compilation.

    Object deck data set: The name of the object deck data set used for the compilation. The object deck data set should be a partitioned data set. This data set is used to make up a SYSLIN card for the compilation.

    SYSLIB: Specify libraries for resolving copybooks or include files. To add a library to this list, click Add. To reorder the list, click the Up and Down buttons. To delete a library from the list, select it and click Remove.

    Support Error Feedback: Select this check box to log errors generated by the compiler.

    Data set qualifier for compiler errors: Errors generated by the compiler are logged to a file that is named with this qualifier. This function is supported only if Support Error Feedback is enabled.

    SYSTSIN instructions: Type Db2 Plan instructions in this field. The field is echoed into the generated JCL. Currently, a sample is specified but commented out. You can uncomment the sample and make any necessary changes. Start the entry field with //SYSTSIN DD * followed by instructions or with a pointer to a data set containing the instructions.

    If you enter the bind instructions directly in the SYSTSIN instructions field, a bind statement for a user who is building a stored procedure on a Db2 subsystem that is called DSN8 might look like the following example:
    //SYSTSIN DD * DSN SYSTEM(DSN8) BIND PACKAGE(DSN8.<USERID>) MEMBER(<MEM>) VALIDATE(BIND) - OWNER(<USERID>) END //*
    The variables <USERID> and <MEM> resolve to the user's user ID and the name of the partitioned data set member for the stored procedure source. They are valid in the property group entry fields, but not in a data set that contains bind instructions. For more information about using variables in property groups, see the related topics.
    Link Options Procedures and Steps Procedures and steps table Enable the compilation procedure (ELAXFLNK). To open step options, double-click the step name (LINK).
    Step options

    Link libraries: The names of the libraries to link your code with. Separate multiple libraries with spaces.

    Use specified link instructions: Select this check box to pass link instructions to the linkage editor. Selecting this check box activates the text-entry pane, where you can enter the link instructions.

    Load module location: The data set where your load module must be placed after the link step.
  3. Associate the property group with your data development project.