Rational Developer for System z


< Previous | Next >

Lesson 4: Creating the property group to associate with Project C, z/OS subprojects GAM0VMM and GAM0VSI

This lesson will walk you through the steps in creating the final property group for the Global Auto Mart sample.

To create the property group to associate with the z/OS® subprojects GAM0VMM and GAM0VSI:

  1. Make sure you are in the z/OS Projects or Enterprise Development perspective and are connected to the host system.
  2. Open the Property Group Manager view, expand the host system, and right click on the property group you just created, COBOL Interface Compile.
  3. Select Copy. In the dialog box that appears, change the name to COBOL Compile, and click OK. The Property Group Editor will open.
  4. Open the COBOL tab at the bottom of the Property Group Editor, and select Runtime Environments from the left panel of options.
  5. In addition to the checkbox marked CICS, put a mark the DB2 checkbox . This sets the property group to use both DB2® and CICS®.
  6. Now, select Procedures and Steps from the left panel of options.
  7. Expand the procedure, ELAXFCOC, and select the step, COBOL, that appears.
  8. Scroll down to edit the COBOL Compile Step Options.
  9. Check to make sure the data sets listed in Listing Output Data Set, Debug Data Set, Object Deck Data Set, and Copy Libraries are correct.
  10. In the Database Request Module text field, enter your *.AUTOMART.DBRM partitioned data set.
  11. Work with the Database Administrator to determine the best method for binding the module to a database package and access plan. You can either in-line the JCL or use a bind file. If using the in-line JCL method, the SYSTSIN should look similar to the following code sample:
    //STEPLIB DD DISP=SHR,DSN=DB2.V8R1M0.SDSNLOAD 
    //*UNCOMMENT AND TAILOR THE FOLLOWING IF YOUR SYSTSIN STATEMENT**                 
    //*CONTAINS BIND INSTRUCTIONS:
    //SYSTSIN   DD  *
      DSN SYSTEM(DSN7)                   
      BIND PACKAGE(GAMPKG) -             
           MEMBER(GAM0VMM) -             
           QUALIFIER(GAMUSER) -          
           LIBRARY('CUST.GAM.DBRM') -    
           ACTION(REP) -                 
           ISOLATION(CS)   -             
           VALIDATE(RUN)  -              
           DYNAMICRULES(BIND)  -         
           ENCODING(EBCDIC) -            
           ENABLE(*)                     
           BIND PLAN(GAMPLAN) -          
           PKLIST(GAMPKG.*) -            
           ACT(REP) -                    
           RETAIN -                      
           VALIDATE(RUN) -               
           ISOLATION(CS) -               
           ENCODING(EBCDIC) -            
           ENABLE(*)                     
       END                               
    //* OR                 
    //*UNCOMMENT AND TAILOR THE FOLLOWING IF YOUR SYSTSIN STATEMENT**                 
    //*POINTS TO A DATA SET CONTAINING BIND INSTRUCTIONS                 
    //*//SYSTSIN DD DSN=USERID.BIND(MEMBER),DISP=SHR                 
    /*  
    Note: If the Bind Procedure needs a Steplib data set, it can be added to the top of the SYSTSIN instructions as demonstrated in the sample JCL.
    If you are using a bind file, create the bind file in a bind PDS and the SYSTSIN Instructions in the COBOL Properties should look similar to the following code sample:
    //*UNCOMMENT AND TAILOR THE FOLLOWING IF YOUR SYSTSIN STATEMENT**                 
    //*CONTAINS BIND INSTRUCTIONS:                 
    //*
    //SYSTSIN   DD  *                 
    //* DSN SYSTEM(YOURSYSTEM)                 
    //* BIND PLAN(YOURPLAN)                 
    //* END                 
    //*    OR                 
    //*UNCOMMENT AND TAILOR THE FOLLOWING IF YOUR SYSTSIN STATEMENT**                 
    //*POINTS TO A DATA SET CONTAINING BIND INSTRUCTIONS                 
    //SYSTSIN DD DSN=CUST.GAM.BIND(GAM0VMM),DISP=SHR 
    And the bind file should contain bind instructions that look like:
     TSOLIB ACTIVATE DA('DB2.V7R1M0.SDSNLOAD')
     ALLOC FI(DBRMLIB) SHR DA('CUST.GAM.DBRM')
     DSN SYSTEM(DSN7)                    
     BIND PACKAGE(GAMPKG) -
       OWNER(GAMUSER) -
       QUALIFIER(GAMUSER) -
       MEMBER(GAM0VMM) -    
       LIBRARY('CUST.GAM.DBRM') -
       ACTION(REP) -                        
       ISOLATION(CS)   -                     
       VALIDATE(RUN)  -                     
       DYNAMICRULES(BIND)  -                     
       ENCODING(EBCDIC) -                     
       ENABLE(*)  -
  12. Open the Link tab at the bottom of the Property Group Manager, and select the Procedures and Steps option from the left panel of options.
  13. Expand the ELAXFLINK procedure, and highlight the LINK step when it appears.
  14. Scroll down to the Link Step Options, and verify that any link libraries that are needed for the project are included in the Link Libraries text field.
  15. Finally, open the JCL tab at the bottom of the Property Group Manager. Ensure that the JCL Job Card is correctly configured for compiling on the host system and that the data set provided in the JCL Data Set text field is correct.
  16. Save the property group, and Close out of the Property Group Editor.
You should see this final property group added to the list of property groups in the Property Group Manager that are associated with the particular host system.
< Previous | Next >

Feedback